{"text_format":"3","workbook":"xlsx","n_sheets":2,"sheets":["DOORS v.1.0 CURRENT_Nov2025","DOORS v.1.0 Superseded_Nov2025"],"not_rendered":{"defined_names":2},"read":"whole","date_system":"1900"}

{"sheet":"DOORS v.1.0 CURRENT_Nov2025","index":0,"n_rows":31680,"n_cols":12,"rows_kept":4500,"cut":true,"bounds":{"rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0}}
[{"$nulls":9},"EARM"]
["ECSS Source Reference","DOORS Project","ECSS Req. Identifier","Type","IE PUID","RCM Version","ECSS Change Status","Original requirement","Text of Note of Original requirement","4. Applicability\n(A/M/D/N)","5. Modified or New requirement\n(full text)","6. Justification\n(only in case of M, D or N in colum 4)"]
["ECSS-E-AS-50-21C Rev. 2","ECSS - Current v1.0","4a","Requirement","ECSS-E-AS-50-21_1520001",3,"Normative Change","CCSDS 131.0-B-5, TM Synchronization and Channel Coding, Issue 5 (September 2023) shall apply as written with the following amendments listed in Table 4‑1."]
["ECSS-E-AS-50-22C Rev.1","ECSS - Current v1.0","4a","Requirement","ECSS-E-AS-50-22_1530001",2,"Normative Change","CCSDS 132.0-B-3, TM Space Data Link Protocol, Issue 3, October 2021 shall apply with the following amendments listed in Table 4‑1."]
["ECSS-E-AS-50-23C Rev.1","ECSS - Current v1.0","4a","Requirement","ECSS-E-AS-50-23_1540001",2,"Normative Change","CCSDS 732.0-B-4, AOS Space Data Link Protocol, Issue 4, October 2021 shall apply with the following amendments listed in Table 4‑1."]
["ECSS-E-AS-50-24C Rev.1","ECSS - Current v1.0","4a","Requirement","ECSS-E-AS-50-24_1550001",2,"Normative Change","CCSDS 231.0-B-4, TC Synchronization and Channel Coding, Issue 4, July 2021 shall apply with the following modifications listed in Table 4‑1."]
["ECSS-E-AS-50-25C Rev.1","ECSS - Current v1.0","4a","Requirement","ECSS-E-AS-50-25_1560001",2,"Normative Change","CCSDS 232.0-B-4, TC Space Data Link Protocol, Issue 4, October 2021 shall apply with the following modifications listed in Table 4‑1."]
["ECSS-E-AS-50-26C","ECSS - Current v1.0","4a","Requirement","ECSS-E-AS-50-26_1570001",1,"Created","CCSDS 232.1-B-2, Communications Operation Procedure-1, Issue 2, September 2010 shall apply with the following modifications listed in Table 4‑1."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.1a","Requirement","ECSS-E-ST-10-02_0740001",1,"Unchanged","The verification process shall demonstrate that the deliverable product meets the specified customer requirements and is capable of sustaining its operational role through:\n1.\tVerification planning;\n2.\tVerification execution and reporting;\n3.\tVerification control and close-out."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.1a","Requirement","ECSS-E-ST-10-02_0740002",2,"Normative Change","The supplier shall identify any constraints on the verification process arising from both the  verification objectives and the requirements defined by the customer as needing verification.","NOTE \tFor example, ground segment characteristics, launch service, envisaged end to end tests involving several suppliers. The usual general objectives are listed in clause 4.1.1 “Verification objectives”.\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.1b","Requirement","ECSS-E-ST-10-02_0740003",2,"Normative Change","The requirements specified in 5.2.1a shall always include those of the technical specification."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.1c","Requirement","ECSS-E-ST-10-02_0740004",2,"Normative Change","The supplier shall define the verification approach by conducting the following steps:\n1.\tIdentify and agree with the customer the set of requirements to be subject of the verification process.\n2.\tSelect the methods and the levels of verification, the associated model philosophy and the verification tools.\n3.\tIdentify the stages and events in which the verification is implemented."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.1d","Requirement","ECSS-E-ST-10-02_0740005",1,"Unchanged","The verification approach shall be defined by the supplier in the Verification Plan (VP) for approval by the customer prior to implementation."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.1e","Requirement","ECSS-E-ST-10-02_0740006",1,"Unchanged","For each requirement to be verified, the verification strategy shall be defined in terms of the combination of the selected verification methods for the different verification levels at the applicable verification stages, in the initial issue of the Verification Control Document (VCD) also called verification matrix (see Annex B), for approval by the customer."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.1a","Requirement","ECSS-E-ST-10-02_0740007",1,"Unchanged","Verification shall be accomplished by one or more of the following verification methods:\n1.\ttest (including demonstration);\n2.\tanalysis (including similarity);\n3.\treview­of­design;\n4.\tinspection."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.1b","Requirement","ECSS-E-ST-10-02_0740008",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.1c","Requirement","ECSS-E-ST-10-02_0740009",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.1d","Requirement","ECSS-E-ST-10-02_0740010",1,"Unchanged","For each requirement verified only by analysis or review-of-design, a risk assessment (part of the VP) shall be conducted to determine the level (major/minor) of the impact of this requirement on the mission."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.1e","Requirement","ECSS-E-ST-10-02_0740011",2,"Normative Change","For each case where the risk assessment performed as a result of 5.2.2.1d identifies the impact of the requirement as being major, risk mitigation planning shall be defined and reported as part of the Verification Plan."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.2a","Requirement","ECSS-E-ST-10-02_0740012",1,"Unchanged","Verification by test shall consist of measuring product performance and functions under representative simulated environments."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.2b","Requirement","ECSS-E-ST-10-02_0740013",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.2c","Requirement","ECSS-E-ST-10-02_0740014",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.2d","Requirement","ECSS-E-ST-10-02_0740015",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.2e","Requirement","ECSS-E-ST-10-02_0740016",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.2f","Requirement","ECSS-E-ST-10-02_0740017",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.2g","Requirement","ECSS-E-ST-10-02_0740018",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.3a","Requirement","ECSS-E-ST-10-02_0740019",1,"Unchanged","Verification by analysis shall consist of performing theoretical or empirical evaluation using techniques agreed with the Customer.","NOTE \tTechniques comprise systematic, statistical and qualitative design analysis, modelling and computational simulation.\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.3b","Requirement","ECSS-E-ST-10-02_0740020",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.3c","Requirement","ECSS-E-ST-10-02_0740021",2,"Normative Change","Analysis to demonstrate qualification of a product by similarity with an already qualified product shall fulfil the following criteria:\n1.\tThe already qualified product was not qualified by similarity.\n2.\tThe product to be verified belongs to category A or to category B (defined in Table 5-1) but no testing is required to achieve qualification.","NOTE \tImplicitly the product to be verified cannot belong to categories C and D equipment (defined in Table 5-1).\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.3d","Requirement","ECSS-E-ST-10-02_0740022",2,"Normative Change","Similarity analysis shall define differences that can dictate additional verification activities."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.3e","Requirement","ECSS-E-ST-10-02_0740023",1,"Unchanged","An analysis programme shall be defined in the Verification Plan (VP)."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.3f","Requirement","ECSS-E-ST-10-02_0740024",1,"Unchanged","An analysis programme shall be applicable to qualification and in-orbit stages only."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.4a","Requirement","ECSS-E-ST-10-02_0740025",1,"Unchanged","Verification by Review-of design (ROD) shall consist of using approved records or evidence that unambiguously show that the requirement is met.","NOTE \tExamples of such approved records are design documents and reports, technical descriptions, and engineering drawings.\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.4b","Requirement","ECSS-E-ST-10-02_0740026",1,"Unchanged","A review-of-design programme shall be defined in the Verification Plan (VP)."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.4c","Requirement","ECSS-E-ST-10-02_0740027",1,"Unchanged","A review-of-design programme shall only be applicable in the qualification stage or in the in-orbit stage. "]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.5a","Requirement","ECSS-E-ST-10-02_0740028",1,"Unchanged","Verification by inspection shall consist of visual determination of physical characteristics. ","NOTE \tPhysical characteristics include constructional features, hardware conformance to document drawing or workmanship requirements, physical conditions, software source code conformance with coding standards. \n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.2.5b","Requirement","ECSS-E-ST-10-02_0740029",1,"Unchanged","An inspection programme shall be defined in the Verification Plan (VP)."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.3a","Requirement","ECSS-E-ST-10-02_0740030",2,"Normative Change","Verification shall be accomplished through the verification levels in conformance with those defined with the Annex A Verification Plan DRD.","NOTE \tUsual levels are defined in 4.2.3.\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.3b","Requirement","ECSS-E-ST-10-02_0740031",1,"Unchanged","When a requirement is fully verified at lower level, the traceability to lower level verification evidence shall be identified."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.3c","Requirement","ECSS-E-ST-10-02_0740032",1,"Unchanged","Formal close-out of qualification and acceptance at lower levels shall be performed prior to close-out at higher level."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.4.1a","Requirement","ECSS-E-ST-10-02_0740033",2,"Normative Change","The Verification Plan shall state which verification activities are to be accomplished in each of relevant verification stages."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.4.1b","Requirement","ECSS-E-ST-10-02_0740034",1,"Unchanged","Qualification, acceptance and pre-launch stages shall be completed before launch."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.4.1c","Requirement","ECSS-E-ST-10-02_0740035",1,"Unchanged","When the verification programme includes an in-orbit stage, the verification shall not rely only on in-orbit activities."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.4.1d","Requirement","ECSS-E-ST-10-02_0740036",1,"Unchanged","When the verification programme includes a post landing stage, the verification shall not rely only on in-orbit activities or post landing activities."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.4.2a","Requirement","ECSS-E-ST-10-02_0740037",2,"Normative Change","In the qualification stage the supplier shall demonstrate that the design, including margins, meets the applicable requirements."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.4.2b","Requirement","ECSS-E-ST-10-02_0740038",1,"Unchanged","Qualification shall be carried-out on hardware and software which is representative of the end item configuration in terms of design, materials, tooling and methods."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.4.2c","Requirement","ECSS-E-ST-10-02_0740039",1,"Unchanged","The qualification programme shall be prepared considering the product category according to heritage as defined in Table 5-1."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.4.2d","Requirement","ECSS-E-ST-10-02_0740190",1,"Created","For product categories A, B and C, the supplier shall state the qualification status at the EQSR (Equipment Qualification Status Review)."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.4.3.1a","Requirement","ECSS-E-ST-10-02_0740040",2,"Normative Change","In the stage the verification shall demonstrate that the product meets specified margins with the agreed deviations and waivers, and it is free of defects when delivered by the supplier."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.4.3.1b","Requirement","ECSS-E-ST-10-02_0740041",2,"Normative Change","Acceptance shall be carried-out on the product which is declared as the acceptance article with a defined configuration of hardware and software."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.4.3.2a","Requirement","ECSS-E-ST-10-02_0740042",1,"Unchanged","The acceptance article shall be manufactured in agreement with the qualified design."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.4.3.2b","Requirement","ECSS-E-ST-10-02_0740043",1,"Unchanged","The acceptance article shall perform as the qualified product."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.4.4a","Requirement","ECSS-E-ST-10-02_0740044",1,"Unchanged","In the pre-launch stage the verification shall demonstrate that the product is properly configured for launch activities and early operations."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.4.4b","Requirement","ECSS-E-ST-10-02_0740045",1,"Unchanged","In the pre-launch stage the verification shall confirm that the product is capable of functioning as planned during launch and early operations."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.4.5a","Requirement","ECSS-E-ST-10-02_0740046",2,"Normative Change","In the in-orbit stage the verification shall address the minimum set of requirements that cannot be verified on ground."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.4.5b","Requirement","ECSS-E-ST-10-02_0740047",1,"Unchanged","In the in-orbit stage the verification shall supplement/confirm ground verification by providing operating conditions which cannot be fully or cost effectively duplicated or simulated on ground."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.4.5c","Requirement","ECSS-E-ST-10-02_0740048",1,"Unchanged","In the in-orbit stage the verification shall characterize the system under operational conditions especially for the aspects that cannot be determined before the launch."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.4.5d","Requirement","ECSS-E-ST-10-02_0740049",1,"Informative Change","In the in-orbit stage the verification shall confirm that the space and ground elements are compatible with each other.","NOTE \tThe working arrangement between the elements suppliers (e.g. satellite, ground segment) and the final customer defines the share of responsibilities for preparing, conducting and reporting the in orbit - commissioning activities. The completion of this stage allows declaring readiness for routine operations (Phase E2-exploitation).\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.4.5e","Requirement","ECSS-E-ST-10-02_0740050",2,"Deleted","<<deleted>> "]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.4.6a","Requirement","ECSS-E-ST-10-02_0740051",1,"Unchanged","The verification in the post-landing stage shall address the product integrity and performance after the mission."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.4.6b","Requirement","ECSS-E-ST-10-02_0740052",1,"Unchanged","In case the product is intended to be re-launched the verification shall address:\n1.\ta health check, at periodical intervals agreed with the customer, during storage periods; \n2.\tthe product performance after modification, repair or replacement;\n3.\tthe readiness for reuse."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.5a","Requirement","ECSS-E-ST-10-02_0740053",1,"Unchanged","The model philosophy shall be defined as part of the overall verification planning."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.6.1a","Requirement","ECSS-E-ST-10-02_0740054",1,"Unchanged","Tools to be used to support the implementation of the verification process shall be identified."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.6.1b","Requirement","ECSS-E-ST-10-02_0740055",2,"Normative Change","All verification tools shall be validated and maintained for their intended use."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.6.1c","Requirement","ECSS-E-ST-10-02_0740056",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.6.1d","Requirement","ECSS-E-ST-10-02_0740057",1,"Unchanged","Formal verification procedures shall be established and applied to tools which are specified as deliverable items."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.6.2a","Requirement","ECSS-E-ST-10-02_0740058",1,"Unchanged","All ground support equipment (GSE) shall be verified under expected environmental conditions and operational constraints."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.6.2b","Requirement","ECSS-E-ST-10-02_0740059",2,"Normative Change","The compatibility of the interfaces of the ground support equipment (GSE) with flight products and facilities shall be verified."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.6.2c","Requirement","ECSS-E-ST-10-02_0740060",1,"Unchanged","The prevention of damage on the flight product due to ground support equipment (GSE) failure shall be verified.","NOTE \tFor hazards to personnel, flight hardware, facilities and environments related to GSE, see ECSS-Q-ST-40.\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.6.2d","Requirement","ECSS-E-ST-10-02_0740061",1,"Unchanged","Ground support equipment (GSE) that is modified or used in a new application shall be re-verified or re-validated."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.6.3a","Requirement","ECSS-E-ST-10-02_0740062",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.6.3b","Requirement","ECSS-E-ST-10-02_0740063",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.6.4a","Requirement","ECSS-E-ST-10-02_0740064",1,"Unchanged","Simulators shall be verified to demonstrate that the simulator characteristics are representative of the simulated product to the extent required for the verification to be supported."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.6.5a","Requirement","ECSS-E-ST-10-02_0740065",1,"Unchanged","Suitability of previously validated analytical software tools shall be assessed for the intended application."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.6.5b","Requirement","ECSS-E-ST-10-02_0740066",1,"Unchanged","Non-validated analytical software tools shall be subjected to a validation process prior to their use."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.6.6a","Requirement","ECSS-E-ST-10-02_0740067",1,"Unchanged","The capability of the integration and test facilities and test tools to perform their intended function in terms of performance and calibration shall be verified as part of the overall integration and test process.","NOTE \tSee ECSS-Q-ST-20-07 for test facilities.\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.7a","Requirement","ECSS-E-ST-10-02_0740068",1,"Unchanged","The verification process shall be phased with the project life cycle, in accordance with ECSS-M-ST-10."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.7b","Requirement","ECSS-E-ST-10-02_0740069",2,"Normative Change","Verification planning to assess feasibility and support development planning shall start during phase A."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.7c","Requirement","ECSS-E-ST-10-02_0740070",1,"Unchanged","The preliminary verification planning shall cover all products and requirements by the end of phase B."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.7d","Requirement","ECSS-E-ST-10-02_0740071",1,"Unchanged","Verification planning shall be completed by the end of Phase C.","NOTE \tCovering all verification stages e.g. pre-launch, in-orbit (including commissioning) and post landing.\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.7e","Requirement","ECSS-E-ST-10-02_0740072",1,"Informative Change","Verification execution and reporting shall be incrementally carried out through the project life cycle starting from phase C.","NOTE \tThe majority of verification execution is undertaken during phase D, however verification by analysis and review of design (and potentially for long lead items) starts in phase C.\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.7f","Requirement","ECSS-E-ST-10-02_0740073",1,"Unchanged","Verification control shall start with the initial issue of the verification control document (VCD) during phase B."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.7g","Requirement","ECSS-E-ST-10-02_0740074",2,"Normative Change","The supplier shall provide the Verification close out status for each product at the end of each stage to the customer for approval. ","NOTE \tE.g. qualification close out status at the end of the qualification stage during the Qualification Review (QR).\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.8.1a","Requirement","ECSS-E-ST-10-02_0740075",1,"Informative Change","The supplier shall provide a Verification plan (VP) for the reviews as agreed with the customer ","NOTE \tSee ECSS-E-ST-10 Table A-1 for review deliverables.\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.8.1b","Requirement","ECSS-E-ST-10-02_0740076",1,"Unchanged","The contents of the Verification plan (VP) shall be in conformance with the DRD in Annex A."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.8.2a","Requirement","ECSS-E-ST-10-02_0740077",1,"Informative Change","The supplier shall provide a Verification Control Document (VCD) for the reviews as agreed with the customer ","NOTE \tSee ECSS-E-ST-10 Table A-1 for review deliverables.\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.8.2b","Requirement","ECSS-E-ST-10-02_0740078",2,"Normative Change","The Verification Control Document (VCD) shall be in conformance with the DRD in Annex B."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.8.3a","Requirement","ECSS-E-ST-10-02_0740079",2,"Normative Change","The supplier shall provide the AIT Plan for the reviews as agreed with the customer ","NOTE \tSee ECSS-E-ST-10 Table A-1 for review deliverables.\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.2.8.3b","Requirement","ECSS-E-ST-10-02_0740080",2,"Normative Change","The AIT plan shall be in accordance with the DRD in ECSS-E-ST-10-03 Annex A."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.1a","Requirement","ECSS-E-ST-10-02_0740081",2,"Normative Change","The supplier shall identify those responsible for the implementation of the verification activities."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.1b","Requirement","ECSS-E-ST-10-02_0740082",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.1c","Requirement","ECSS-E-ST-10-02_0740083",1,"Unchanged","When nonconformity is detected during the verification process, a Nonconformance Report (NCR), in conformance with Annex A of ECSS-Q-ST-10-09, shall be raised and processed according to ECSS-Q-ST-20."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.1d","Requirement","ECSS-E-ST-10-02_0740084",2,"Normative Change","The verification results shall be recorded by the supplier in verification reports and provided to the Verification Control Board (VCB) for review."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.1a","Requirement","ECSS-E-ST-10-02_0740085",2,"Normative Change","The test report for each test verification task as identified in the VP or AIT Plan shall be submitted to the Verification Control Board (VCB) after the test completion, within the time frame agreed with the customer."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.1b","Requirement","ECSS-E-ST-10-02_0740086",2,"Normative Change","The supplier shall provide Test reports for the reviews in conformance with the DRD in Annex C."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.1c","Requirement","ECSS-E-ST-10-02_0740087",2,"Normative Change","The supplier shall provide the Test reports for the reviews as agreed with the customer ","NOTE \tSee ECSS-E-ST-10 Table A-1 for review deliverables. \n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.1d","Requirement","ECSS-E-ST-10-02_0740088",2,"Normative Change","A Test report shall be provided for each Test verification task as identified in the VP or AIT Plan."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.2a","Requirement","ECSS-E-ST-10-02_0740089",2,"Normative Change","The Analysis report for each analysis verification task identified in the Verification Plan shall be submitted to the Verification Control Board (VCB) after analysis completion, within the time frame agreed with the customer."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.2b","Requirement","ECSS-E-ST-10-02_0740090",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.2c","Requirement","ECSS-E-ST-10-02_0740091",2,"Normative Change","The supplier shall provide an Analysis report for the reviews as agreed with the customer.","NOTE\t1\tSee ECSS-E-ST-10 Table A-1 for review deliverables.\nNOTE\t2\tFor each discipline specific analysis reports is covered in the respective ECSS standard. A generic guideline for the content of an Analysis Report is given in Annex S of ECSS-E-ST-10.\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.2d","Requirement","ECSS-E-ST-10-02_0740092",2,"Normative Change","An Analysis report shall be provided for each Analysis verification task identified in the Verification Plan."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.3a","Requirement","ECSS-E-ST-10-02_0740093",2,"Normative Change","The Review-of-design report shall be submitted for each Review-of-design verification task identified in the Verification Plan to the Verification Control Board (VCB) after the Review-of-Design completion, within the time frame agreed with the customer."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.3b","Requirement","ECSS-E-ST-10-02_0740094",2,"Normative Change","The supplier shall provide the Review-of-design report in conformance with the DRD in Annex D."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.3c","Requirement","ECSS-E-ST-10-02_0740095",2,"Normative Change","The supplier shall provide a Review-of-design for the reviews as agreed with the customer ","NOTE \tSee ECSS-E-ST-10 Table A-1 for review deliverables.\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.3d","Requirement","ECSS-E-ST-10-02_0740096",2,"Normative Change","A Review-of-design report shall be provided for each Review-of-design verification task identified in the Verification Plan."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.4a","Requirement","ECSS-E-ST-10-02_0740097",2,"Normative Change","The Inspection report shall be submitted for each Inspection verification task identified in the Verification Plan to the Verification Control Board (VCB) after the inspection completion, within the time frame agreed with the customer."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.4b","Requirement","ECSS-E-ST-10-02_0740098",2,"Normative Change","The supplier shall provide the Inspection report in conformance with the DRD in Annex E."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.4c","Requirement","ECSS-E-ST-10-02_0740099",2,"Normative Change","The supplier shall provide an Inspection report  for the reviews as agreed with the customer","NOTE \tSee ECSS-E-ST-10 Table A-1 for review deliverables.\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.4d","Requirement","ECSS-E-ST-10-02_0740100",2,"Normative Change","An Inspection report shall be provided for each Inspection verification task identified in the Verification Plan."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.5a","Requirement","ECSS-E-ST-10-02_0740101",2,"Normative Change","The supplier shall prepare a Verification report when more than one of the defined verification methods are utilized to verify a requirement or a specific set of requirements."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.5b","Requirement","ECSS-E-ST-10-02_0740102",2,"Normative Change","The supplier shall provide the Verification report in conformance with the DRD in Annex F."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.5c","Requirement","ECSS-E-ST-10-02_0740103",2,"Normative Change","The Verification report shall be submitted to the Verification Control Board (VCB) after the completion of the last contributing verification activities, within the time frame agreed with the customer."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.5d","Requirement","ECSS-E-ST-10-02_0740104",2,"Normative Change","The supplier shall provide a Verification report for the reviews as agreed with the customer ","NOTE \tSee ECSS-E-ST-10 Table A-1 for review deliverables.\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.6a","Requirement","ECSS-E-ST-10-02_0740105",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.6b","Requirement","ECSS-E-ST-10-02_0740106",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.6c","Requirement","ECSS-E-ST-10-02_0740107",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.6d","Requirement","ECSS-E-ST-10-02_0740108",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.3.2.6e","Requirement","ECSS-E-ST-10-02_0740109",1,"Informative Change","The rules for the analysis, inspection and review of design shall be defined in writing before their execution.","NOTE\t1\tFor example, analysis, inspection or review of design procedures.\nNOTE\t2\tThe rules for Test are as detailed in ECSS-E-ST-10-03.\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.4.1a","Requirement","ECSS-E-ST-10-02_0740110",1,"Unchanged","The implementation of the verification process shall be monitored by the Verification Control Board (VCB)."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.4.1b","Requirement","ECSS-E-ST-10-02_0740111",2,"Normative Change","The supplier shall provide a computer based verification database to support the verification process control."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.4.1c","Requirement","ECSS-E-ST-10-02_0740112",2,"Normative Change","The supplier shall deliver the verification database to the customer in an electronic form to be agreed with the customer."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.4.1d","Requirement","ECSS-E-ST-10-02_0740113",2,"Normative Change","The supplier shall capture and provide verification close-out evidence in the verification database for those customers requirements agreed to be verified."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.4.2a","Requirement","ECSS-E-ST-10-02_0740114",2,"Normative Change","A Verification Control Board (VCB) shall be established by the supplier and invite the participation of the customer, to assess the achievements and status of the verification process.","NOTE \tThe VCB is set-up in relation to the complexity and the extents of the verification activities. \n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.4.2b","Requirement","ECSS-E-ST-10-02_0740115",1,"Unchanged","The verification process shall be considered completed when the Verification Control Board (VCB) confirms that:\n1.\t documented evidence is recorded in the VCD, \n2.\tidentified requirements have been verified \n3.\tassociated product verification objectives are reached"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.4.2c","Requirement","ECSS-E-ST-10-02_0740116",2,"Normative Change","The conclusions of the VCB shall be submitted for approval to the customer."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.4.2d","Requirement","ECSS-E-ST-10-02_0740117",2,"Normative Change","The supplier’s Verification Control Board (VCB) representative shall support the VCB in the assessment of the verification status with a periodicity agreed with the customer.","NOTE \tThe results of the VCB are at least presented on the occasions of project reviews as defined in ECSS-M-ST-10.\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.4.2e","Requirement","ECSS-E-ST-10-02_0740118",2,"Normative Change","The supplier's VCB representative shall ensure the Verification Control Board (VCB) endorses the final issue of the Verification Control Document (VCD)."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.4.2f","Requirement","ECSS-E-ST-10-02_0740191",1,"Created","The supplier's VCB representative shall ensure the Verification Control Board (VCB) includes participation of Engineering and Quality Assurance representatives within its members."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.4.2g","Requirement","ECSS-E-ST-10-02_0740192",1,"Created","The supplier's VCB representative shall ensure that for VCBs related to qualification the QA representative acts as the board chair."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.4.3a","Requirement","ECSS-E-ST-10-02_0740119",2,"Normative Change","The extent of the re-verification to be performed shall be determined by Supplier and agreed with the customer, in the following cases:\n1.\tfailure and repair as decided by Nonconformance Review Board (NRB);\n2.\tunplanned disassembly or demating;\n3.\trefurbishment, maintenance or design changes;\n4.\tchanges of requirements after initial verification;\n5.\tlong duration storage in case of storage duration in excess to the qualified storage duration;\n6.\tflight use of qualification hardware."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.4.3b","Requirement","ECSS-E-ST-10-02_0740120",1,"Unchanged","The Verification Control Document (VCD) shall be updated by the supplier to record as open, those requirements subject to re-verification until this is performed and closeout agreed by the customer."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.4.4.1a","Requirement","ECSS-E-ST-10-02_0740121",1,"Unchanged","The content of the completed Verification Control Document (VCD) shall be in conformance with the DRD in Annex B."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.4.4.1b","Requirement","ECSS-E-ST-10-02_0740122",2,"Normative Change","The supplier shall update the Verification database after approval of a report in line with the timescale agreed with the customer and stated in the Verification Plan."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.4.4.1c","Requirement","ECSS-E-ST-10-02_0740123",1,"Unchanged","The intermediate issues of the Verification Control Document (VCD), reflecting the current status of the verification database, shall be made available to the Verification Control Board (VCB) upon request."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.4.4.1d","Requirement","ECSS-E-ST-10-02_0740124",1,"Informative Change","The intermediate issues of the Verification Control Document (VCD), reflecting the current verification and compliance status, shall be delivered at each formal review as agreed with the customer","NOTE \tSee ECSS-E-ST-10 Table A-1 for review deliverables.\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.4.4.1e","Requirement","ECSS-E-ST-10-02_0740125",1,"Unchanged","The final issue of the Verification Control Document (VCD) shall be submitted to the Verification Control Board (VCB) after the approval of the last report, within the time frame agreed with the customer."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","5.4.4.2a","Requirement","ECSS-E-ST-10-02_0740126",1,"Unchanged","The supplier shall make available to the customer for consultation the evidences mentioned in the VCD in addition to the deliverable reports."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","A.2.1<1>a","Requirement","ECSS-E-ST-10-02_0740127",1,"Unchanged","The VP shall contain a description of the purpose, objective, content and the reason prompting its preparation. "]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","A.2.1<1>b","Requirement","ECSS-E-ST-10-02_0740128",1,"Unchanged","Open issues, assumptions and constraints relevant to this document shall be stated and described."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","A.2.1<2>a","Requirement","ECSS-E-ST-10-02_0740129",1,"Unchanged","The VP shall list the applicable and reference documents in support to the generation of the document."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","A.2.1<3>a","Requirement","ECSS-E-ST-10-02_0740130",1,"Unchanged","The VP shall list the applicable dictionary or glossary and the meaning of specific terms or abbreviations utilized in the document."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","A.2.1<4>a","Requirement","ECSS-E-ST-10-02_0740131",1,"Unchanged","The VP shall briefly describe the subject of the verification process."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","A.2.1<5>a","Requirement","ECSS-E-ST-10-02_0740132",1,"Unchanged","The VP shall describe the basic verification concepts and definitions (methods, levels and stages)."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","A.2.1<6>a","Requirement","ECSS-E-ST-10-02_0740133",1,"Unchanged","The VP shall describe the selected models and the associated model philosophy, product matrix."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","A.2.1<7>a","Requirement","ECSS-E-ST-10-02_0740134",1,"Unchanged","The VP shall describe the selected combination of the different verification methods at the applicable verification levels and stages, in general and for each requirement type/group (including software). "]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","A.2.1<7>b","Requirement","ECSS-E-ST-10-02_0740135",1,"Unchanged","The allocation of the requirements to the specific verification tasks shall be given."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","A.2.1<8>a","Requirement","ECSS-E-ST-10-02_0740136",1,"Unchanged","The VP shall document the verification activities and associated planning in the applicable verification stages. "]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","A.2.1<8>b","Recommendation","ECSS-E-ST-10-02_0740194",1,"Created","Analysis, review­of­design, inspection and test programmes should be detailed through dedicated activity sheets, or through reference to the AIT Plan. "]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","A.2.1<9>a","Requirement","ECSS-E-ST-10-02_0740138",1,"Unchanged","The VP shall describe high level definitions of the verification tools to be used, such as S/W facilities, special tools, simulators, analytical tools. "]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","A.2.1<10>a","Requirement","ECSS-E-ST-10-02_0740139",1,"Unchanged","The VP shall describe the proposed methodology to be utilized for verification monitoring and control including the use of a verification data base."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","A.2.1<11>a","Requirement","ECSS-E-ST-10-02_0740140",1,"Unchanged","The VP shall list the involved verification documents and describe their content."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","A.2.1<12>a","Requirement","ECSS-E-ST-10-02_0740141",1,"Unchanged","The VP shall describe the responsibility and management tools applicable to the described verification process. "]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","A.2.1<12>b","Requirement","ECSS-E-ST-10-02_0740142",1,"Unchanged","It shall describe the responsibilities within the project team, the relation to product assurance, quality control and configuration control (including anomaly handling and change control) as well as the responsibility sharing with external partners. "]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","A.2.1<12>c","Requirement","ECSS-E-ST-10-02_0740143",1,"Unchanged","The relevant reviews shall be planned and responsibilities described."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","A.2.2a","Permission","ECSS-E-ST-10-02_0740195",1,"Created","The Verification Plan may be combined with the AIT Plan in one single AIV Plan.","NOTE \tIn this case VP and AIT plans do not exist anymore as single entities.\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","B.2.1<1>a","Requirement","ECSS-E-ST-10-02_0740145",1,"Unchanged","The VCD shall contain a description of the purpose, objective, content and the reason prompting its preparation. "]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","B.2.1<1>b","Requirement","ECSS-E-ST-10-02_0740146",1,"Unchanged","Open issues, assumptions and constraints relevant to this document shall be stated and described."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","B.2.1<1>c","Requirement","ECSS-E-ST-10-02_0740147",1,"Unchanged","The VCD content shall be phased with the product life-cycle such that the initial issue contains the verification matrix, intermediate issues cover the planned on-ground verifications and their executions evidence (in particular for qualification and acceptance completion), the in-orbit and post landing activities; final issue provides evidence of the close-out of the overall verification process."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","B.2.1<2>a","Requirement","ECSS-E-ST-10-02_0740148",1,"Unchanged","The VCD shall list the applicable and reference documents in support to the generation of the document."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","B.2.1<3>a","Requirement","ECSS-E-ST-10-02_0740149",1,"Unchanged","The VCD shall list the applicable dictionary or glossary and the meaning of specific terms or abbreviations utilized in the document. "]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","B.2.1<4>a","Requirement","ECSS-E-ST-10-02_0740150",1,"Unchanged","The VCD shall describe the verification control approach applied to the product, the involved documentation and the computerized tool used to support the process."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","B.2.1<4>b","Requirement","ECSS-E-ST-10-02_0740151",1,"Unchanged","The VCD shall include the requirements to be verified (with reference to the specifications involved), call up the verification methods, levels and stages definitions and explain the verification close­out criteria.."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","B.2.1<5>a","Requirement","ECSS-E-ST-10-02_0740152",1,"Unchanged","Each issue of the VCD shall summarize the current Verification Close-out status."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","B.2.1<6>a","Requirement","ECSS-E-ST-10-02_0740153",1,"Unchanged","The VCD shall collect in the form of a matrix, for each requirement, the following  verification information:\n1.\tRequirement identifier,\n2.\tRequirement text\n3.\ttraceability between requirement,\n4.\tLevels and stages of verification,\n5.\tmethods, \n6.\tlink to the relevant section of the verification plan and any planning document, \n7.\tReferences to any documentation that demonstrates compliance to the requirements,\n8.\tStatus of Compliance (yes, no, partial),\n9.\tClose-out status (open / closed),\n10.\tReasons of the close-out status,","NOTE\t1\tto item 6 For example, test specification.\nNOTE\t2\tto item 7: For example, report, analysis, waivers, RFD, NCR, NRB, customer closeout records.\n"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","B.2.1<6>b","Requirement","ECSS-E-ST-10-02_0740154",1,"Unchanged","The initial issue of the VCD shall contain a verification matrix limited to: \n1.\tRequirement identifier,\n2.\tRequirement text,\n3.\ttraceability between requirement,\n4.\tLevels and stages of verification,\n5.\tmethods, \n6.\tlink to the relevant section of the verification plan."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","C.2.1<1>a","Requirement","ECSS-E-ST-10-02_0740155",2,"Normative Change","The Test Report shall contain a description of the purpose, objective, content and the reason prompting its preparation. "]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","C.2.1<1>b","Requirement","ECSS-E-ST-10-02_0740156",1,"Unchanged","Open issues, assumptions and constraints relevant to this document shall be stated and described."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","C.2.1<2>a","Requirement","ECSS-E-ST-10-02_0740157",2,"Normative Change","The Test Report shall list the applicable and reference documents in support to the generation of the document."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","C.2.1<2>b","Requirement","ECSS-E-ST-10-02_0740193",1,"Created","The Test Report shall include as applicable reference documents the corresponding test procedure and test specification as specified in the DRDs in ECSS-E-ST-10-03."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","C.2.1<3>a","Requirement","ECSS-E-ST-10-02_0740158",2,"Normative Change","The Test Report shall list the applicable dictionary or glossary and the meaning of specific terms or abbreviations utilized in the document"]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","C.2.1<4>a","Requirement","ECSS-E-ST-10-02_0740159",2,"Normative Change","The Test Report shall contain the test results with supporting data (including the test execution dates, the as run procedure, and the test facility results). "]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","C.2.1<4>b","Requirement","ECSS-E-ST-10-02_0740160",2,"Normative Change","The Test Report shall contain the analysis of test data and the relevant assessment."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","C.2.1<4>c","Requirement","ECSS-E-ST-10-02_0740161",2,"Normative Change","The Test Report shall provide a synthesis of the test results."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","C.2.1<5>a","Requirement","ECSS-E-ST-10-02_0740162",2,"Normative Change","The Test Report shall include the list of deviations to the test procedure, the nonconformance including failures and the problems."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","C.2.1<6>a","Requirement","ECSS-E-ST-10-02_0740163",2,"Normative Change","The Test Report shall summarize:\n1.\tthe test results, including:\n(a)\tthe list of the requirements to be verified (in correlation with the VCD), \n(b)\ttraceability to used documentation, \n(c)\tconformance or deviation including references and signature and date),\n2.\tthe comparison with the requirements and \n3.\tthe verification close-out judgment. "]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","C.2.1<6>b","Requirement","ECSS-E-ST-10-02_0740164",1,"Unchanged","Open issues shall be clearly stated and described."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","C.2.1<6>c","Requirement","ECSS-E-ST-10-02_0740165",1,"Unchanged","Separate test analyses shall be cross-referenced."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","D.2.1<1>a","Requirement","ECSS-E-ST-10-02_0740166",2,"Normative Change","The Review-of-Design Report shall contain a description of the purpose, objective, content and the reason prompting its preparation. "]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","D.2.1<1>b","Requirement","ECSS-E-ST-10-02_0740167",1,"Unchanged","Open issues, assumptions and constraints relevant to this document shall be stated and described."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","D.2.1<2>a","Requirement","ECSS-E-ST-10-02_0740168",2,"Normative Change","The Review-of-Design Report shall list the applicable and reference documents in support to the generation of the document."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","D.2.1<3>a","Requirement","ECSS-E-ST-10-02_0740169",2,"Normative Change","The Review-of-Design Report shall list the applicable dictionary or glossary and the meaning of specific terms or abbreviations utilized in the document with the relevant meaning."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","D.2.1<4>a","Requirement","ECSS-E-ST-10-02_0740170",2,"Normative Change","The Review-of-Design Report shall describe the review-of-design activity in terms of method and procedures used."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","D.2.1<5>a","Requirement","ECSS-E-ST-10-02_0740171",2,"Normative Change","The Review-of-Design Report shall summarize \n1.\tthe review-of-design results, including \n(a)\tthe list of the requirements to be verified (in correlation with the VCD), \n(b)\ttraceability to used documentation, \n(c)\tconformance or deviation including references and signature and date, \n2.\tthe comparison with the requirements and \n3.\tthe verification close-out judgment. "]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","D.2.1<5>b","Requirement","ECSS-E-ST-10-02_0740172",1,"Unchanged","Open issues shall be clearly stated and described."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","E.2.1<1>a","Requirement","ECSS-E-ST-10-02_0740173",2,"Normative Change","The Inspection Report shall contain a description of the purpose, objective, content and the reason prompting its preparation. "]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","E.2.1<1>b","Requirement","ECSS-E-ST-10-02_0740174",1,"Unchanged","Open issues, assumptions and constraints relevant to this document shall be stated and described."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","E.2.1<2>a","Requirement","ECSS-E-ST-10-02_0740175",2,"Normative Change","The Inspection Report shall list the applicable and reference documents in support to the generation of the document."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","E.2.1<3>a","Requirement","ECSS-E-ST-10-02_0740176",2,"Normative Change","The Inspection Report shall list the applicable dictionary or glossary and the meaning of specific terms or abbreviations utilized in the document with the relevant meaning."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","E.2.1<4>a","Requirement","ECSS-E-ST-10-02_0740177",2,"Normative Change","The Inspection Report shall describe the product configuration data of the inspected item."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","E.2.1<5>a","Requirement","ECSS-E-ST-10-02_0740178",2,"Normative Change","The Inspection Report shall summarize the: \n1.\tinspection results, including:\n(a)\tthe list of the requirements to be verified (in correlation with the VCD), \n(b)\ttraceability to used documentation, \n(c)\tinspection event location and date, \n(d)\texpected finding, \n(e)\tconformance or deviation including proper references and signature and date, \n2.\tcomparison with the requirements, and \n3.\tverification close-out judgement. "]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","E.2.1<5>b","Requirement","ECSS-E-ST-10-02_0740179",1,"Unchanged","Open issues shall be clearly stated and described."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","F.2.1<1>a","Requirement","ECSS-E-ST-10-02_0740180",2,"Normative Change","The Verification Report shall contain a description of the purpose, objective, content and the reason prompting its preparation. "]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","F.2.1<1>b","Requirement","ECSS-E-ST-10-02_0740181",1,"Unchanged","Open issues, assumptions and constraints relevant to this document shall be stated and described."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","F.2.1<2>a","Requirement","ECSS-E-ST-10-02_0740182",2,"Normative Change","The Verification Report shall list the applicable and reference documents in support to the generation of the document."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","F.2.1<3>a","Requirement","ECSS-E-ST-10-02_0740183",2,"Normative Change","The Verification Report shall list the applicable dictionary or glossary and the meaning of specific terms or abbreviations utilized in the document with the relevant meaning Verification subject."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","F.2.1<4>a","Requirement","ECSS-E-ST-10-02_0740184",2,"Normative Change","The Verification Report shall describe the verification approach, the associated problems and results with reference to the relevant test, analysis, review­of­design and inspection reports."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","F.2.1<4>b","Requirement","ECSS-E-ST-10-02_0740185",2,"Normative Change","The Verification Report shall identify the deviations from the verification plan."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","F.2.1<5>a","Requirement","ECSS-E-ST-10-02_0740186",2,"Normative Change","The Verification Report shall list the requirements to be verified (in correlation with the VCD)."]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","F.2.1<5>b","Requirement","ECSS-E-ST-10-02_0740187",2,"Normative Change","The Verification Report shall summarize verification results, the comparison with the requirements and the verification close­out judgement. "]
["ECSS-E-ST-10-02C Rev.1","ECSS - Current v1.0","F.2.1<5>c","Requirement","ECSS-E-ST-10-02_0740188",1,"Unchanged","Open issues shall be clearly stated and described."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.1a","Requirement","ECSS-E-ST-10-03_0750001",1,"Informative Change","A coherent test programme shall be established, encompassing each verification stage and level to implement the verification by testing.","NOTE\t1\tThe testing programme is performed incrementally at different product decomposition levels.\nNOTE\t2\tRefer to clause 3.1 for determining the type of item for which the test programme is defined (i.e. space segment equipment or space segment element) and to ECSS-S-ST-00-01 Glossary of terms.\nNOTE\t3\tThe number and type of testing levels depends upon the complexity of the project and on its characteristics in accordance with the Verification programme (see ECSS-E-ST-10-02).\nNOTE\t4\tThe test programme documentation is defined in 4.3.3.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.1b","Requirement","ECSS-E-ST-10-03_0750002",1,"Unchanged","The customer and the supplier shall agree the need to treat a space segment element as a space segment equipment.","NOTE \tThis is typically the case for small instrument. \n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.1c","Requirement","ECSS-E-ST-10-03_0750003",2,"Normative Change","AIT Plan and test specifications shall be derived from the product requirements, verification plan and verification control document (VCD).","NOTE \tVerification plan and VCD are defined in ECSS-E-ST-10-02.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.1d","Requirement","ECSS-E-ST-10-03_0750004",2,"Normative Change","Test procedures shall be derived from test specifications and AIT Plan."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.1e","Requirement","ECSS-E-ST-10-03_0750005",1,"Unchanged","Test programme and its implementation shall be in conformance with safety requirements of ECSS-Q-ST-40 and ECSS-Q-ST-20-07."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.2a","Requirement","ECSS-E-ST-10-03_0750006",1,"Unchanged","Development test of a product shall be completed prior to the start of its formal qualification testing.","NOTE\t\tDevelopment tests are conducted over a range of operating conditions that can exceed the design range.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.2b","Requirement","ECSS-E-ST-10-03_0750007",1,"Unchanged","Development tests shall not be conducted on qualification or flight models or parts of it."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.2c","Requirement","ECSS-E-ST-10-03_0750008",1,"Unchanged","Records of test configuration, test results and other pertinent data shall be maintained.","NOTE \tThis kind of information can be used for investigation when failure occurs during the qualification and acceptance, or for other investigations.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.1a","Requirement","ECSS-E-ST-10-03_0750009",1,"Unchanged","The supplier shall assign clear responsibility for the implementation of the test programme."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.1b","Requirement","ECSS-E-ST-10-03_0750010",1,"Unchanged","The customer, or its duly appointed representative, shall have the right to participate to all test phases."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.2.1a","Requirement","ECSS-E-ST-10-03_0750011",1,"Unchanged","The test programme shall be decomposed in blocks.","NOTE \tThe general test programme is reviewed at the CDR as per ECSS-M-ST-10.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.2.1b","Requirement","ECSS-E-ST-10-03_0750012",1,"Unchanged","The definition of the blocks of requirement 4.3.2.1a shall be agreed between the customer and supplier.","NOTE\t 1\tTest block definition depends mainly on the item under test, the facility and the contractual agreement. A test block can include one or more tests. For equipment, usually one test block covers the full test programme.\nNOTE\t2\tTypical test blocks for space segment elements are:\n·\tIntegration\n·\tAlignment\n·\tLeak/proof pressure\n·\tMechanical (Static load test, sinusoidal, acoustic, random, modal survey, shock)\n·\tEMC conducted\n·\tEMC radiated/auto-compatibility/RF\n·\tThermal (TB/TV test)\n·\tFunctional and performance test\n·\tFinal preparation\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.2.1c","Requirement","ECSS-E-ST-10-03_0750013",1,"Unchanged","Each test block shall include the following formal reviews:\n1.\ttest readiness review (TRR);\n2.\tpost test review(s) (PTR); \n3.\ttest review board (TRB).","NOTE\t1\tTRRs from several blocks can be combined, TRRs can also be combined with a PTR of the previous block.\nNOTE\t2\tDepending on the nature of the test, the customer can decide to establish additional key-points between formal reviews. Typical examples are transition between level and axes in vibration tests and transition between test phases in TV/TB tests.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.2.2a","Requirement","ECSS-E-ST-10-03_0750014",1,"Unchanged","A TRR shall be held before the start of the test activity to verify that all conditions allow to proceed with the test."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.2.2b","Requirement","ECSS-E-ST-10-03_0750015",2,"Normative Change","The TRR shall address the following topics:\n1.\ttest documentation availability and suitability, including: \n(a)\tapproved AIT Plan,\n(b)\tapproved test specification,\n(c)\ttest predictions (when relevant),\n(d)\tapproved test procedures (including contingency and emergency procedures),\n(e)\tapproved measurement point plan,\n(f)\tapproved test facility readiness report,\n(g)\tapproved test schedule, and\n(h)\tacceptance data package of lower level items.\n2.\titem under test configuration;\n3.\ttest configuration/set-up;\n4.\tinspection status report of KIP, MIP, or both;\n5.\ttest facility, environmental conditions, test instrumentations, calibration, maintenance status; \n6.\tcleanliness condition, hazard and safety;\n7.\tground support equipment (GSE) and infrastructures;\n8.\tstatus of nonconformances that affect the item under test, its associated GSE, or the test facility;\n9.\twaivers status, and deviations;\n10.\tpersonnel qualification and availability;\n11.\tresults from test rehearsal using the test facility with or without the item under test, when relevant;\n12.\ttest pass/fail criteria completeness;\n13.\tassignment of responsibilities;\n14.\ttest schedule.","NOTE\t1\tFor 4.3.2.2b.1(f), the content of the facility readiness report is defined in ECSS-Q-ST-20-07.\nNOTE\t2\tThe level of details according to which each topic is addressed, is different for the general test programme TRR than for each block test TRR. \n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.2.2c","Requirement","ECSS-E-ST-10-03_0750016",1,"Unchanged","The following parties shall participate to the TRR:\n1.\tthe chairperson, who is the product assurance manager of the authority responsible for the test;\n2.\tproduct assurance from all involved parties;\n3.\tproject engineer from all involved parties;\n4.\tAIT from all involved parties;\n5.\tspecialists, when necessary from all involved parties; \n6.\tfacility representative;\n7.\tother as relevant.","NOTE \tFor example launcher authority for tests related to launcher interface or other company representative that will take over the responsibility of the hardware after delivery.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.2.2d","Requirement","ECSS-E-ST-10-03_0750017",1,"Unchanged","All the open points shall be clearly identified and actions assigned with closure date before the execution of the test."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.2.2e","Requirement","ECSS-E-ST-10-03_0750018",1,"Unchanged","The output of the TRR shall be a decision to proceed with the test or not. "]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.2.3a","Requirement","ECSS-E-ST-10-03_0750019",1,"Unchanged","A PTR shall be held in order to formally declare the test completed and allow the release of the item under test and test facility for further activity.","NOTE \tThe release of the test facility includes the breaking of the test configuration.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.2.3b","Requirement","ECSS-E-ST-10-03_0750020",2,"Normative Change","The PTR shall address the following topics:\n1.\tverification that all test data were acquired, recorded, and archived in conformance with the test specification and test procedure requirements;\n2.\tverification that the process for test anomalies and NCRs, raised during the test, was initiated, and all needed inspection, test data and test configuration were acquired;\n3.\tconfirmation that tests were performed according to the AIT Plan, the test specification and the test procedures, with the exceptions of what is covered by agreed procedure variations or NCRs or Open Works;\n4.\tstatus of compliance of the item under test to the relevant requirement;\n5.\tpost test status of GSE;\n6.\tpost item under test configuration based on inspection and cleanliness report;\n7.\tidentification of the open points with assignment of actions for their closure, as well as lessons learned drawn."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.2.3c","Requirement","ECSS-E-ST-10-03_0750021",1,"Unchanged","The following parties shall participate to the PTR:\n1.\tproduct assurance;\n2.\tproject engineer;\n3.\tAIT;\n4.\tfacility representative;\n5.\tother, including specialist, as relevant.","NOTE \tFor example launcher authority for tests related to launcher interface or other company representative that will take over the responsibility of the hardware after delivery. \n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.2.4a","Requirement","ECSS-E-ST-10-03_0750022",1,"Unchanged","A TRB shall be held to review all results and conclude on the test completeness and achievement of objectives."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.2.4b","Requirement","ECSS-E-ST-10-03_0750023",2,"Normative Change","The TRB shall address the following topics:\n1.\ttest documentation availability, including: \n(a)\ttest report as per ECSS-E-ST-10-02 Annex C, \n(b)\tfacility report when relevant, \n(c)\tinspection report including cleanliness report,\n(d)\tlist of NCRs, \n(e)\tcopy of NCRs raised during test with the related NRB minutes of meeting, and associated request(s) for waiver, and\n(f)\tlist of procedure deviations.\n2.\tcompliance with the test specification, and variations to the AIT Plan;\n3.\tstatus of compliance of the item under test to the relevant requirement;\n4.\tpost test status of GSE;\n5.\tpost item under test configuration based on inspection and cleanliness report;\n6.\treview of all still open NCRs raised during test in order to assess that there is no impact on the test objectives achievement;\n7.\tlessons learned to be drawn."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.2.4c","Requirement","ECSS-E-ST-10-03_0750024",2,"Normative Change","The following parties shall participate to the TRB:\n1.\tproduct assurance;\n2.\tproject engineer;\n3.\tfacility representative;\n4.\tother, including specialist, as relevant.","NOTE \tFor example AIT, in support of project engineering, or launcher authority for tests related to launcher interface or other company representative that will take over the responsibility of the hardware after delivery.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.3.2a","Requirement","ECSS-E-ST-10-03_0750025",2,"Normative Change","The supplier shall establish the AIT Plan in conformance with the DRD in Annex A.","NOTE \tAt space segment equipment level, the AIT Plan can be called test plan.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.3.2b","Requirement","ECSS-E-ST-10-03_0750026",2,"Normative Change","The agreed AIT Plan shall be available, at the latest, for the TRR of the test programme."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.3.2c","Requirement","ECSS-E-ST-10-03_0750027",1,"Unchanged","The way the requirement 4.3.3.2b is achieved shall be agreed between the customer and the supplier."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.3.3a","Requirement","ECSS-E-ST-10-03_0750028",1,"Unchanged","The supplier shall establish the test specification in conformance with the DRD in Annex B."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.3.3b","Requirement","ECSS-E-ST-10-03_0750029",1,"Unchanged","The agreed test specification shall be available at the relevant test block TRR and on time to allow procedure preparation."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.3.3c","Requirement","ECSS-E-ST-10-03_0750030",1,"Unchanged","The way the requirement 4.3.3.3b is achieved shall be agreed between the customer and the supplier."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.3.4a","Requirement","ECSS-E-ST-10-03_0750031",1,"Unchanged","The supplier shall establish the test procedure in conformance with the DRD in Annex C."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.3.4b","Requirement","ECSS-E-ST-10-03_0750032",1,"Unchanged","The test procedure, derived from the agreed test specification, shall be available at the relevant test block TRR."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.3.4c","Requirement","ECSS-E-ST-10-03_0750033",1,"Unchanged","The way the requirement 4.3.3.4b is achieved shall be agreed between the customer and the supplier."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.3.5a","Requirement","ECSS-E-ST-10-03_0750034",1,"Unchanged","The supplier shall establish the test report in conformance with the DRD in Annex C of ECSS-E-ST-10-02.","NOTE \tThe test report describes test execution, results and conclusions in the light of the test requirements. It contains the test description and the test results including the as-run test procedures, the considerations and conclusions with particular emphasis on the close-out of the relevant verification requirements including any deviation.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.3.5b","Requirement","ECSS-E-ST-10-03_0750035",1,"Unchanged","The test report shall be available prior to the TRB."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.4a","Requirement","ECSS-E-ST-10-03_0750036",1,"Unchanged","Any failure or anomaly during testing shall be recorded."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.4b","Requirement","ECSS-E-ST-10-03_0750037",1,"Unchanged","All nonconformances shall be managed in conformance with ECSS-Q-ST-10-09."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.4c","Requirement","ECSS-E-ST-10-03_0750038",1,"Unchanged","The NRB shall decide on the necessity and extent of any retest activity in order to demonstrate the correctness of the disposition made."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.5a","Requirement","ECSS-E-ST-10-03_0750039",1,"Unchanged","Test measurements and the environmental conditions shall be recorded for subsequent evaluation."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.5b","Requirement","ECSS-E-ST-10-03_0750040",1,"Unchanged","A database of parameters shall be established for trend analysis."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.3.5c","Requirement","ECSS-E-ST-10-03_0750041",2,"Normative Change","Trend analysis shall be performed using test data acquired across sequences of tests."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.4.1a","Requirement","ECSS-E-ST-10-03_0750042",2,"Normative Change","The TSPE shall establish the required test conditions."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.4.1b","Requirement","ECSS-E-ST-10-03_0750043",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.4.1c","Requirement","ECSS-E-ST-10-03_0750044",2,"Normative Change","If an item is tested in conditions different from the ones in which it is expected to operate, then the test levels and durations shall account for the possible differences in behaviour. ","NOTE \tIn this case, the test levels and durations are modified based on analyses. For example to prevent effects of convective heat transfer that can reduce temperature differences. \n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.4.1d","Requirement","ECSS-E-ST-10-03_0750045",1,"Unchanged","Cleanliness and contamination control for test programmes shall conform to ECSS-Q-ST-70-01."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.4.1e","Requirement","ECSS-E-ST-10-03_0750046",1,"Unchanged","The quality and safety management system used to operate and maintain test facility(ies) shall be recognized by the customer.","NOTE \tAs example, in accordance to quality and safety management system requirements from ECSS-Q-ST-20-07.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.4.1f","Requirement","ECSS-E-ST-10-03_0750047",1,"Unchanged","Test facilities, tools and instrumentation shall not prevent to fulfil the tests objectives."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.4.1g","Requirement","ECSS-E-ST-10-03_0750048",1,"Unchanged","The EGSE or other support systems of the item under test shall:\n1.\tnot jeopardize the results of tests; \n2.\tbe immune to signals used for susceptibility tests;\n3.\tbe designed to comply with the applicable legislation, including safety (e.g. EC Directives)."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.4.1h","Requirement","ECSS-E-ST-10-03_0750049",2,"Normative Change","The combination of test set-up, test levels, test durations, and operational modes shall not create conditions that can:\n1.\tinduce failures of the item under test, \n2.\tlead to rejection of adequate item under test, or\n3.\tcreate hazardous conditions."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.4.2a","Requirement","ECSS-E-ST-10-03_0750050",2,"Normative Change","The test input tolerances bands shall be agreed by the customer and specified in the TSPE."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.4.2b","Requirement","ECSS-E-ST-10-03_0750051",2,"Normative Change","For the purpose of 4.4.2a, test input tolerances shall account for the uncertainty budget and confidence level of the measurement instrument(s) and test equipment used to control and monitor the test parameters.","NOTE\t1\tJCGM 100 series, EA-4/16 and EA-4/02 guidelines and ISO/IEC 17025 general requirements can be used to build up the measurement uncertainty budgets.\nNOTE\t2\tThe test input tolerances specified in Table 4‑1 are the allowable ranges within which the test parameters, as measured, can vary.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.4.2c","Requirement","ECSS-E-ST-10-03_0750052",2,"Normative Change","Quantitative requirements demonstrated by measured values shall account for associated uncertainties, and be compared with the specified test values."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.4.2d","Requirement","ECSS-E-ST-10-03_0750053",2,"Normative Change","The test input tolerances specified in Table 4‑1 shall be applied to the specified test values."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.4.2e","Requirement","ECSS-E-ST-10-03_0750054",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.4.3a","Requirement","ECSS-E-ST-10-03_0750055",2,"Normative Change","The allowable measurement uncertainties shall be agreed by the customer and specified in the TSPE.","NOTE\t1\tThis is important for the selection of the test facility, test instrumentation and GSE.\nNOTE\t2\tTable 4‑2 provides typical values from test centers.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.4.3b","Requirement","ECSS-E-ST-10-03_0750056",2,"Normative Change","The measurement uncertainty shall be demonstrated based on approved calibration procedures, with traceability to international measurement standards. "]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.4.3c","Requirement","ECSS-E-ST-10-03_0750057",1,"Unchanged","All test instrumentation shall be within the normal calibration period at the time of the test."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.4.3d","Requirement","ECSS-E-ST-10-03_0750058",1,"Unchanged","Any anomaly of test instrumentation, detected at the first calibration sequence after the test, shall be reported."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.4.3e","Requirement","ECSS-E-ST-10-03_0750059",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.5.1a","Requirement","ECSS-E-ST-10-03_0750060",1,"Unchanged","The test programme shall be defined taking into account the agreed model philosophy.","NOTE \tThe model philosophy, including model definition, is detailed in ECSS-E-HB-10-02.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.5.1b","Requirement","ECSS-E-ST-10-03_0750061",1,"Unchanged","When preparing the overall test programme of a space segment element tests linked to compatibility with ground and launch segment shall also be included.","NOTE \tThis covers in particular the system validation test.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.5.2a","Requirement","ECSS-E-ST-10-03_0750062",1,"Unchanged","Qualification testing shall be performed to provide evidence that the space segment element or equipment performs in accordance with its specifications in the intended environments with the specified qualification margins.","NOTE\t1\tThe Qualification test programme requirements are defined in ECSS-E-ST-10-02 requirement 5.2.4.2b. and 5.2.4.2c.\nNOTE\t2\tThis evidence is used, further to analysis as relevant, to provide via verification reports (defined in ECSS-E-ST-10-02 Annex F) the elements for the close-out of the VCD (defined in ECSS-E-ST-10-02 Annex B).\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.5.2b","Requirement","ECSS-E-ST-10-03_0750063",1,"Unchanged","Qualification testing shall be conducted on dedicated qualification models except when using protoflight approach."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.5.2c","Requirement","ECSS-E-ST-10-03_0750064",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.5.2d","Requirement","ECSS-E-ST-10-03_0750065",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.5.2e","Requirement","ECSS-E-ST-10-03_0750066",2,"Normative Change","In case destructive tests are needed (e.g. Burst test), a representative model different from the QM shall be used or the test be performed at the end of the qualification programme. ","NOTE \tThis model can be simplified but needs to fully represent the function tested.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.5.2f","Requirement","ECSS-E-ST-10-03_0750067",1,"Unchanged","The qualification test levels and durations shall be as specified in Table 5‑2 for space segment equipment and in Table 6‑2 for space segment element.","NOTE \tThe test durations identified in Table 5‑2 and Table 6‑2 are the minimum values.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.5.3a","Requirement","ECSS-E-ST-10-03_0750068",1,"Unchanged","Acceptance testing shall be performed to provide evidence that the space segment element or equipment performs in accordance with the specifications in the intended environments with the specified acceptance margins.","NOTE \tThis evidence is used, further to analysis as relevant, to provide via verification reports (defined in ECSS-E-ST-10-02 Annex F) the elements for the close-out of the VCD (defined in ECSS-E-ST-10-02 Annex B).\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.5.3b","Requirement","ECSS-E-ST-10-03_0750069",1,"Unchanged","Acceptance testing shall be performed on each flight product, except the one used as Protoflight, to assure freedom from workmanship defects and flawed materials in conformance with ECSS-E-ST-10-02."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.5.3c","Requirement","ECSS-E-ST-10-03_0750070",1,"Informative Change","The acceptance programme shall be performed, after a qualification programme has been completed (as per clause 4.5.2 or clause 4.5.4). "]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.5.3d","Requirement","ECSS-E-ST-10-03_0750071",1,"Unchanged","The acceptance test levels and durations shall be as specified in Table 5‑4 for space segment equipment, and in Table 6‑4 for space segment element levels.","NOTE \tThe test durations identified in Table 5‑4 and Table 6‑4 are the minimum values.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.5.4.2a","Requirement","ECSS-E-ST-10-03_0750072",1,"Unchanged","Protoflight testing shall be performed on the first flight model to provide evidence that the space segment element or equipment performs in accordance with the specifications in the intended environments with the specified qualification margins and to confirm its readiness for delivery and subsequent usage, being free from workmanship defects and flawed materials.","NOTE \tThis evidence is used, in addition to analysis as relevant, to provide via verification reports (defined in ECSS-E-ST-10-02 Annex F) the elements for the close-out of the VCD (defined in ECSS-E-ST-10-02 Annex B).\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.5.4.2b","Requirement","ECSS-E-ST-10-03_0750073",1,"Unchanged","In case destructive tests are needed (e.g. Burst test), a representative model different from the PFM shall be used. ","NOTE \tThis model can be simplified but needs to fully represent the function tested.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.5.4.2c","Requirement","ECSS-E-ST-10-03_0750074",1,"Unchanged","The protoflight test levels and durations shall be as specified in Table 5‑6 for space segment equipment and in Table 6‑6 for space segment element levels.","NOTE\t1\tThe general approach is to select:\n                      · test levels: as qualification levels;\n                      · test durations: as acceptance durations.\nNOTE\t2\tThe test durations identified in Table 5‑6 and Table 6‑6 are the minimum values."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.6.2a","Requirement","ECSS-E-ST-10-03_0750075",2,"Normative Change","The configuration control board (CCB), as per ECSS-M-ST-40, shall convene to evaluate and decide the extent of the qualification sequence of tests to be repeated."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.6.3a","Requirement","ECSS-E-ST-10-03_0750076",1,"Unchanged","The supplier shall identify the testing requirements during storage and post-storage.","NOTE \tThese requirements can be presented in the user manual. \n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.6.3b","Requirement","ECSS-E-ST-10-03_0750077",1,"Unchanged","Periodic tests shall be assessed and performed with a frequency accounting for:\n1.\tspace segment equipment degradation, and\n2.\tspecific personnel know-how maintenance. "]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.6.3c","Requirement","ECSS-E-ST-10-03_0750078",1,"Unchanged","Storage configuration shall be agreed with the customer in particular for the deployable mechanisms. ","NOTE \tIf deployable mechanisms are stored assembled with the space segment elements, the flight tension can be reduced.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.6.3d","Requirement","ECSS-E-ST-10-03_0750079",1,"Unchanged","The periodic tests during storage shall cover: \n1.\toverall functional test,\n2.\ttesting of the rotating parts,\n3.\tpower consumption measurement,\n4.\tTT&C space segment subsystem through tests caps (space segment element switched ON),\n5.\ttesting of the propulsion space segment subsystem pressure through the telemetry,\n6.\tvisual inspection of the separately stored space segment equipment in a suitable clean work area,\n7.\tcontamination tests on the contamination probes.","NOTE \tExample of age sensitive space segment equipment: Travelling wave tubes (TWTs), batteries and special lubricated mechanisms valves and motors. \n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.6.3e","Requirement","ECSS-E-ST-10-03_0750080",1,"Unchanged","Any additional test to the one listed in 4.6.3d shall be identified for customer approval."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.6.3f","Requirement","ECSS-E-ST-10-03_0750081",1,"Unchanged","The storage procedure shall be submitted to the customer for approval."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.6.3g","Recommendation","ECSS-E-ST-10-03_0750453",1,"Unchanged","Solar array(s) should be stored in a gaseous Nitrogen environment.","NOTE \tThis recommendation is also relevant for the solar panels integrated with the photovoltaic assembly, during any transportation phase, and during any long term storage phase after a successful solar panel DRB (Delivery Review Board). \n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.6.3h","Requirement","ECSS-E-ST-10-03_0750468",1,"Created","The electrical functional and performance test as specified in 5.5.1.1l shall be repeated at the end of the storage, for a storage period longer than 2 years, before flight."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.6.3i","Requirement","ECSS-E-ST-10-03_0750469",1,"Created","For final Storage periods longer than 6 months and shorter than 2 years, the electrical functional and performance test as specified in 5.5.1.1l shall be repeated, however it can be performed without the Flasher."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.6.4a","Requirement","ECSS-E-ST-10-03_0750083",1,"Unchanged","Space segment element or equipment to be re-flown shall be re-tested before the new flight in accordance with the verification programme and acceptance criteria defined for the new mission."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.6.4b","Requirement","ECSS-E-ST-10-03_0750084",2,"Normative Change","High level (system or space segment element) functional testing shall be performed in preference to individual low level tests.","NOTE \tPost-landing testing is performed on space products to be recovered at the end of mission and on products which are re-flown.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.6.5a","Requirement","ECSS-E-ST-10-03_0750085",1,"Unchanged","Use of qualification space segment element or equipment shall not be allowed unless agreed by the customer."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.6.5b","Requirement","ECSS-E-ST-10-03_0750086",1,"Unchanged","Additional testing of qualification space segment element or equipment subsequently selected for flight shall be compatible with the residual life.","NOTE \tThis is done when the customer considers the risk acceptable.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","4.6.5c","Requirement","ECSS-E-ST-10-03_0750087",1,"Informative Change","In case of refurbishment or disassembly the qualification space segment element or equipment shall be subjected to an acceptance re-testing to be agreed with the customer.","NOTE \tThe extent of the acceptance testing depends on the item past history and on the extent of the modification.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.1a","Requirement","ECSS-E-ST-10-03_0750088",1,"Unchanged","The test baseline and sequencing shall be tailored to the specific space segment equipment type for each project. ","NOTE \tThe types of space segment equipment are uniformly listed at the end of Table 5‑1, Table 5‑3, and Table 5‑5.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.1b","Requirement","ECSS-E-ST-10-03_0750089",1,"Unchanged","Where space segment equipment falls into two or more types, the combination of all required tests specified for each type shall be applied.","NOTE \tFor example: A star sensor can be considered to fit both “electronic space segment equipment” and “optical space segment equipment” types, therefore, an EMC test is conducted since it is applicable for electronic space segment equipment, even though there is no requirement for optical space segment equipment. \n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.1c","Requirement","ECSS-E-ST-10-03_0750090",2,"Normative Change","The sequence of tests, as specified in Figure 5‑1, shall be performed, taking into account tests’ applicability, as defined for qualification in Table 5‑1, for acceptance in Table 5‑3, for protoflight in Table 5‑5.","NOTE \tThis sequence reflects the principle “Test like you fly”. It is based on a combination of:\n·\tthe order in which the environments are encountered during flight, and\n·\tthe capability to identify defects as early as possible in the test sequence.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.1d","Requirement","ECSS-E-ST-10-03_0750091",1,"Unchanged","Any unusual or unexpected behaviour shall be evaluated to determine the existence of any trend potentially leading to anomaly or failure situation."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.1e","Requirement","ECSS-E-ST-10-03_0750092",2,"Normative Change","PT and FFT shall be performed at the beginning and at the end of the test programme under room conditions as defined for clean rooms.","NOTE \tThose tests provide the criteria for judging the integrity of the space segment equipment thought the overall test programme. The results of both tests should be identical within the test tolerances.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.1f","Requirement","ECSS-E-ST-10-03_0750093",1,"Unchanged","RFT shall be performed before and after each environmental test block as well as before and after transportation.","NOTE \tThis test allows verifying the integrity of the space segment equipment.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.1g","Requirement","ECSS-E-ST-10-03_0750094",1,"Unchanged","PT, FFT or RFT, as relevant, shall be performed:\n1.\tduring thermal test(s), or\n2.\twhen the space segment equipment is expected to be operational under another type of imposed environment. ","NOTE \tThe test definition corresponds to the expected operation of the item when the environment is being imposed.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.1h","Requirement","ECSS-E-ST-10-03_0750095",1,"Unchanged","Space segment equipment, if operated during ascent and descent, shall be powered and configured in the corresponding operating mode during the environmental tests and parameters monitored to detect intermittent or persistent failures during the test."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.1i","Requirement","ECSS-E-ST-10-03_0750096",1,"Unchanged","Any space segment equipment pressurized during ascent shall be tested as specified in ECSS-E-ST-32-02 clause 5.4.4, and verified for internal pressure decay."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.1j","Requirement","ECSS-E-ST-10-03_0750097",1,"Unchanged","Adjustable protection functions shall be tested."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.2a","Requirement","ECSS-E-ST-10-03_0750098",1,"Unchanged","The space segment equipment qualification test baseline shall consist of the tests specified in Table 5‑1 in line with requirement 5.1b, according to the type of the space segment equipment."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.3a","Requirement","ECSS-E-ST-10-03_0750099",1,"Unchanged","The space segment equipment acceptance test baseline shall consist of the tests specified in Table 5‑3 in line with requirement 5.1b, according to the type of the space segment equipment."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.4a","Requirement","ECSS-E-ST-10-03_0750100",1,"Unchanged","The space segment equipment Protoflight test baseline shall consist of the tests specified in Table 5‑5 in line with requirement 5.1b, according to the type of the space segment equipment."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.4b","Requirement","ECSS-E-ST-10-03_0750101",1,"Unchanged","The following qualification tests shall be performed on a dedicated model and never on the Protoflight Model:\n1.\tlife test \n2.\tburst pressure test, \n3.\tESD. "]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.1a","Requirement","ECSS-E-ST-10-03_0750102",1,"Unchanged","Functional tests shall verify the complete function of the space segment equipment, under the specified operating and environment conditions and in all operational modes."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.1b","Requirement","ECSS-E-ST-10-03_0750103",1,"Unchanged","Performance tests shall verify that the space segment equipment performances, under the specified environment, are compliant with the performances specification."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.1c","Permission","ECSS-E-ST-10-03_0750454",1,"Unchanged","Functional and performance test may be combined as single test depending on their complexity and time duration.","NOTE \tIn this case the test is called functional and performance test.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.1d","Requirement","ECSS-E-ST-10-03_0750105",1,"Unchanged","In case of internal redundancy, functional tests shall be performed on both chains taking into account the type of redundancy (e.g. hot or cold)."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.1e","Requirement","ECSS-E-ST-10-03_0750106",1,"Unchanged","In case of cross-strapped configurations, requirements for testing shall be agreed with the customer."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.1f","Requirement","ECSS-E-ST-10-03_0750107",1,"Unchanged","Test parameters shall be varied throughout their specification ranges and the sequences expected in flight operation."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.1g","Requirement","ECSS-E-ST-10-03_0750108",1,"Unchanged","Electrical tests shall include application of expected voltages, impedance, frequencies, pulses, and wave forms at the electrical interface of the space segment equipment, including all redundant circuits if any.","NOTE \tFor antennas the electrical interface is understood to include the far field radiation pattern.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.1h","Requirement","ECSS-E-ST-10-03_0750109",1,"Unchanged","Electrical test shall include the measurement of the electrical properties at the interfaces as specified in the ICD.","NOTE \tFor example, power consumption, inrush current, signal characteristics, response time, expected voltages, impedances frequencies, pulses and waves forms characteristic at the interfaces, including redundant circuits if any.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.1i","Requirement","ECSS-E-ST-10-03_0750110",1,"Unchanged","Fault voltage tolerance of interface circuit shall be tested to ensure absence of failure propagation risks."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.1j","Requirement","ECSS-E-ST-10-03_0750111",1,"Unchanged","When accessible, protection functions shall be tested.","NOTE \tExample of protection function are over-voltage, and over-current.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.1k","Requirement","ECSS-E-ST-10-03_0750112",1,"Unchanged","When protection function have the capability to be overwritten, the overwrite function shall be tested."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.1l","Requirement","ECSS-E-ST-10-03_0750113",2,"Normative Change","For the solar panels and solar array, the electrical functional and performance tests shall include flasher test, Electroluminescence/Photoluminescence, by-pass, blocking diodes and EEE parts electrical health check, insulation, continuity and visual inspection; with the test definition and conditions of the electrical health checks specified in clause 5.5.3 of ECSS-E-ST-20-08, except for:\n1.\tinsulation resistance where the test is applied to sections and not to individual strings\n2.\tinsulation test is not be performed between temperature sensor and sections.\n3.\tblocking diode test is required at panel level and recommended at solar array level and space segment element level.","NOTE\t1\tThe electrical functional and performance tests as listed above can be replaced by a validated alternative method to be agreed by the customer. \nNOTE\t2\tFor the solar array (i.e. at solar array level and space segment element level), the flasher test can be replaced by a combination of detailed measurements of transfer harness resistance, detailed checks of the continuity of the circuits, plus a detailed assessment of the electroluminescence/ photoluminescence results.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.1m","Requirement","ECSS-E-ST-10-03_0750114",2,"Normative Change","Functional tests of mechanisms and actuators shall include application of torque, load and motion as specified."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.1n","Requirement","ECSS-E-ST-10-03_0750115",1,"Unchanged","When relevant, internal alignment shall be verified as part of the functional test."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.2a","Requirement","ECSS-E-ST-10-03_0750116",1,"Unchanged","If the space segment equipment can be exposed to humidity level above 65 % during its life time then a humidity qualification test shall be performed.","NOTE \tMore information on humidity effects can be found in ECSS-Q-ST-70-01.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.2b","Requirement","ECSS-E-ST-10-03_0750117",2,"Normative Change","For qualification humidity test the space segment equipment shall be installed in the chamber and tested in accordance with the following processes and steps:\n1.\tPretest conditions. Keep the chamber temperature at room conditions with uncontrolled humidity.\n2.\tCycle 1. Perform the following process:\n(a)\tIncrease the temperature to +35 °C over a one hour period.\n(b)\tIncrease the humidity to not less than 95 % over a one hour period with the temperature maintained at +35 °C.\n(c)\tHold the conditions 5.5.1.2b.2(a) and 5.5.1.2b.2(b) for two hours.\n(d)\tReduced the temperature to +2 °C over a two hour period with the relative humidity stabilized at not less than 95 %.\n(e)\tHold conditions 5.5.1.2b.2(d) for two hours.\n3.\tCycle 2. Repeat the foregoing cycle but increase the temperature from +2 C to +35 °C over a two hour period (moisture is not added to the chamber until +35 °C is reached).\n4.\tCycle 3. Perform the following process:\n(a)\tIncrease the chamber temperature to +35 °C over a two hour period without adding any moisture to the chamber.\n(b)\tDry the test component with air at room temperature and 50 % maximum relative humidity by blowing air through the chamber for six hours.\n(c)\tSet the volume of air used per minute equal to one to three times the test chamber volume.","NOTE \tA suitable container can be used in place of the test chamber for drying the test component.\n1.\tCycle 4. Perform the following process:\n(a)\tPlace the space segment equipment in the test chamber and increase the temperature to +35 °C.\n(b)\tIncrease the relative humidity to 90 % over a one hour period.\n(c)\tMaintain conditions 5.5.1.2b.5(a) and 5.5.1.2b.5(b) for at least one hour. \n(d)\tReduce the temperature to +2 °C over a one hour period with the relative humidity stabilized at 90 %.\n(e)\tMaintain conditions 5.5.1.2b.5(d) for at least one hour.\n(f)\tFollow the drying cycle (Cycle 3).\n2.\tCheck the space segment equipment prior to the test and at the end of Cycle 3 (within 2 h after the drying) and visually inspect for deterioration or damage. \n3.\tTest the space segment equipment functionally during the Cycle 4 period of stability (i.e. following the 1 h-period after reaching +35 °C and 90 % relative humidity conditions).\n4.\tInspect the space segment equipment visually for deterioration or damage after removal from the chamber.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.3a","Requirement","ECSS-E-ST-10-03_0750118",1,"Unchanged","The life test for space segment equipment qualification shall be designed to demonstrate the ability of the space segment equipment to withstand the maximum operating time and the maximum number of predicted operational cycles during the “product lifetime” by providing the required performance at the end of life.","NOTE \tThis test is performed on life-limited space segment equipment or part of it.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.3b","Requirement","ECSS-E-ST-10-03_0750119",1,"Informative Change","The space segment equipment shall be set up to operate under the environmental conditions expected during actual operation.","NOTE \tEnvironments include e.g. ground conditions, temperature conditions, mission pressure or space, vacuum conditions, and various combinations of these.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.3c","Requirement","ECSS-E-ST-10-03_0750120",1,"Unchanged","If the launch impacts the lifetime, test simulating the launch constraints shall be performed prior the lifetime test to ensure proper mechanical setting.","NOTE \tExamples of launch constraints are vibration, shock.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.3d","Requirement","ECSS-E-ST-10-03_0750121",1,"Unchanged","The space segment equipment shall be either selected at random from production lot or be the qualification space segment equipment."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.3e","Requirement","ECSS-E-ST-10-03_0750122",1,"Unchanged","The demonstration of the lifetime shall be performed in the expected environment, using the sum of the predicted nominal ground cycle and the in-orbit cycle plus the qualification margins.","NOTE\t1\tFor space segment equipment having a relatively low percentage duty cycle, it can be acceptable to compress the operational duty cycle to reduce the total test duration.\nNOTE\t2\tFor space segment equipment that operate continuously in orbit, or at very high duty cycles, accelerated test techniques can be employed pending demonstration that this leads to realistic results and approval by the customer.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.3f","Requirement","ECSS-E-ST-10-03_0750123",1,"Unchanged","Performances shall be monitored continuously or at regular intervals."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.3g","Requirement","ECSS-E-ST-10-03_0750124",1,"Unchanged","All the components of an actuation chain shall be submitted to the same number of actuations.","NOTE \tExamples of such components are motors, bearing, and gears.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.1.4a","Requirement","ECSS-E-ST-10-03_0750125",1,"Unchanged","The total operating time and temperature for electrical space segment equipment burn-in, shall be agreed with the customer.","NOTE\t1\tThose parameters depend on the type of space segment equipment and of the level of test performed at components / subassembly level.\nNOTE\t2\tThe time of operation in thermal testing is part of the burn in time.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.1a","Requirement","ECSS-E-ST-10-03_0750126",2,"Normative Change","The following physical properties of space segment equipment shall be determined using tools and techniques that conform to the maximum allowable uncertainty:\n1.\tDimensions and structural interfaces; \n2.\tMass;\n3.\tCentre of gravity with respect to a given coordinate system for three mutually perpendicular axes;\n4.\tMoment of inertia with respect to the given coordinate system.","NOTE \tFor space segment equipment with simple shapes, the centre of gravity location and momenta of inertia can be determined by calculation.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.1b","Requirement","ECSS-E-ST-10-03_0750127",1,"Unchanged","The space segment equipment shall be in launch configuration, unless this configuration cannot be reproduced on ground."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.2a","Requirement","ECSS-E-ST-10-03_0750128",1,"Unchanged","The space segment equipment shall be mounted to a test fixture through its normal mounting points."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.2b","Requirement","ECSS-E-ST-10-03_0750129",1,"Unchanged","When a centrifuge is used, it shall be ensured that the length of the arm (measured to the geometric centre of the space segment equipment) is at least five times the dimension of the space segment equipment measured along the arm.","NOTE \tThis is to ensure uniform force distribution on the space segment equipment. \n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.3a","Requirement","ECSS-E-ST-10-03_0750130",1,"Unchanged","Random vibration tests shall be conducted in launch configuration for all axes."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.3b","Requirement","ECSS-E-ST-10-03_0750131",1,"Unchanged","The induced cross axis accelerations at the attachment points shall be limited to the maximum test levels specified for the cross axis."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.3c","Requirement","ECSS-E-ST-10-03_0750132",1,"Unchanged","In order to evaluate the space segment equipment integrity a resonance search shall be performed before and after the random vibration test."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.3d","Requirement","ECSS-E-ST-10-03_0750133",1,"Unchanged","The success criteria for the resonance search shall be:\n1.\tless than 5 % in frequency shift, for modes with an effective mass greater than 10 %;\n2.\tless than 20 % in amplitude shift, for modes with an effective mass greater than 10 %."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.3e","Requirement","ECSS-E-ST-10-03_0750134",1,"Unchanged","Detailed visual checks shall be carried out when functional tests are not performed."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.3f","Requirement","ECSS-E-ST-10-03_0750135",1,"Unchanged","For space segment equipment which is designed to be re-flown, the qualification test duration per axis shall be in conformance with Table 5‑2 plus 50 seconds per additional flight."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.4a","Requirement","ECSS-E-ST-10-03_0750136",1,"Unchanged","Acoustic tests shall be conducted in a reverberating chamber, with the space segment equipment in launch configuration mounted on a test fixture simulating the dynamic flight mounting conditions.","NOTE \tAcoustic tests are often but not always conducted on space segment equipment with large surfaces which are likely to be susceptible to acoustic noise excitations, e.g. solar arrays, antennas; for this type of space segment equipment random vibration testing is not performed.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.4b","Requirement","ECSS-E-ST-10-03_0750137",1,"Unchanged","The space segment equipment and the test fixture shall be decoupled from chamber floor and wall structure born vibration."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.4c","Requirement","ECSS-E-ST-10-03_0750138",1,"Unchanged","In order to evaluate the space segment equipment integrity a low level acoustic run (-8 dB the qualification level) shall be performed before and after the acoustic qualification run by determining resonant frequencies."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.4d","Requirement","ECSS-E-ST-10-03_0750139",1,"Unchanged","The success criteria for the resonance search shall be:\n1.\tless than 5 % in frequency shift, for modes with an effective mass greater than 10 %;\n2.\tless than 40 % in amplitude shift, for modes with an effective mass greater than 10 %."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.4e","Requirement","ECSS-E-ST-10-03_0750140",1,"Unchanged","For space segment equipment which is designed to be re-flown, the qualification test duration shall be in conformance with Table 5‑2 plus 50 seconds per additional flight. "]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.5a","Requirement","ECSS-E-ST-10-03_0750141",1,"Unchanged","Sinusoidal tests shall be conducted in the launch configurations for all axes."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.5b","Requirement","ECSS-E-ST-10-03_0750142",1,"Unchanged","A resonance search shall be performed before and after the sinusoidal vibration test to determine resonance frequencies to evaluate the space segment equipment integrity."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.5c","Requirement","ECSS-E-ST-10-03_0750143",1,"Unchanged","The success criteria for the resonance search shall be:\n1.\tless than 5 % in frequency shift, for modes with an effective mass greater than 10 %;\n2.\tless than 20 % in amplitude shift, for modes with an effective mass greater than 10 %."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.5d","Requirement","ECSS-E-ST-10-03_0750144",1,"Unchanged","Detailed visual checks shall be carried out prior and after test to check for visual damage."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.5e","Requirement","ECSS-E-ST-10-03_0750145",1,"Unchanged","The induced cross axis excitation shall be monitored to check that the response in the cross axis does not exceed the specification."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.6a","Requirement","ECSS-E-ST-10-03_0750146",1,"Informative Change","Shock tests shall be conducted in the item under test configuration relevant to the event where the shock is produced.","NOTE \tThe shock tests demonstrate the ability of the space segment equipment to withstand the shocks encountered during the lifetime, e.g.: fairing separation, space segment equipment separation, booster burn out, apogee boost motor ignition, solar arrays and antennas deployment, shocks from landing of reusable space segment elements.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.6b","Requirement","ECSS-E-ST-10-03_0750147",1,"Unchanged","Equipment powered during the event where the shock is produced, shall be powered during the test."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.6c","Requirement","ECSS-E-ST-10-03_0750148",1,"Unchanged","The equipment shall be mounted to a fixture using its normal mounting points."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.6d","Requirement","ECSS-E-ST-10-03_0750149",1,"Unchanged","The selected test method shall achieve the specified Shock Response Spectrum with a representative transient, comparable in shape and duration to the expected in-flight shock."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.6e","Permission","ECSS-E-ST-10-03_0750455",1,"Unchanged","To reduce the number of shock activations, axes and directions may be combined, provided the required environment is created. "]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.6f","Requirement","ECSS-E-ST-10-03_0750151",1,"Unchanged","Detailed visual checks shall be carried out."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.6g","Requirement","ECSS-E-ST-10-03_0750152",1,"Unchanged","Hardware integrity shall be verified after the test.","NOTE \tThis is performed through several ways, like performance test, low level sinusoidal vibration pre and post test, modal survey, alignment.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.6h","Requirement","ECSS-E-ST-10-03_0750153",1,"Unchanged","The induced cross axis excitation shall be monitored to check that the response in the cross axis do not exceed the specification."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.6i","Requirement","ECSS-E-ST-10-03_0750154",1,"Unchanged","The homogeneity of the shock around the equipment under test shall be monitored by at least one pair of sensors mounted at opposite corners of the equipment."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.7a","Requirement","ECSS-E-ST-10-03_0750155",1,"Unchanged","The measurements of the space segment equipment interface dynamic forces and torques shall be performed."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.7b","Requirement","ECSS-E-ST-10-03_0750156",1,"Unchanged","The space segment equipment shall be in its nominal operational configuration similar to the on-orbit operational conditions."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.7c","Requirement","ECSS-E-ST-10-03_0750471",1,"Unchanged","The time signals of the measurements shall be recorded.","NOTE \tFor example in a machine readable format.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.7d","Requirement","ECSS-E-ST-10-03_0750472",1,"Unchanged","The background noise shall be measured, including each individual contribution from EGSE, MGSE, FGSE.","NOTE \tExample of FGSE: pumps.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.7e","Requirement","ECSS-E-ST-10-03_0750473",1,"Unchanged","If necessary, for the purpose of the test, mitigation actions shall be taken to reduce the background noise.","NOTE \tBackground noise can be due to the external environment (e.g. road, sea, wind, people around, other ongoing activities/tests), facilities (e.g. air conditioning, lights), MGSE, EGSE, FGSE (e.g. pumps). Background noise can be different depending on the time (night/day, presence of other activities).\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.8a","Requirement","ECSS-E-ST-10-03_0750157",2,"Normative Change","The performance parameters shall be measured when subjected to the specified micro-vibration environment."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.8b","Requirement","ECSS-E-ST-10-03_0750158",1,"Unchanged","The space segment shall be in its nominal operational configuration similar to the on-orbit operational conditions."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.8c","Requirement","ECSS-E-ST-10-03_0750474",1,"Unchanged","The time signals of the measurements of the performance parameters and of the applied micro-vibration environment shall be recorded.","NOTE \tFor example in a machine readable format.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.8d","Requirement","ECSS-E-ST-10-03_0750475",1,"Unchanged","The background noise shall be measured, including each individual contribution from EGSE, MGSE, FGSE.","NOTE \tExample of FGSE: pumps.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.2.8e","Requirement","ECSS-E-ST-10-03_0750476",1,"Unchanged","If necessary, for the purpose of the test, mitigation actions shall be taken to reduce the background noise.","NOTE \tBackground noise can be due to the external environment (e.g. road, sea, wind, people around, other ongoing activities/tests), facilities (e.g. air conditioning, lights), MGSE, EGSE, FGSE (e.g. pumps). Background noise can be different depending on the time (night/day, presence of other activities).\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.3.1a","Requirement","ECSS-E-ST-10-03_0750159",2,"Normative Change","Leak tests shall be performed only on sealed or pressurized space segment equipment, sensitive to loss of pressure or vacuum, or which contain hazardous substances."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.3.1b","Requirement","ECSS-E-ST-10-03_0750160",1,"Unchanged","The leak test shall demonstrate the ability of sealed or pressurized space segment equipment to conform to the leak rates stated in the specifications."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.3.1c","Requirement","ECSS-E-ST-10-03_0750161",2,"Normative Change","The leak test method employed shall have sensitivity and uncertainty consistent with the space segment equipment specified maximum allowable leak rate."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.3.1d","Requirement","ECSS-E-ST-10-03_0750162",1,"Unchanged","The sensitivity of the leak test, in particular, shall be quantitatively less than the minimum leak rate to be detected by a factor of at least two to ensure reliability of measurements."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.3.1e","Requirement","ECSS-E-ST-10-03_0750163",1,"Unchanged","Leak tests shall be performed prior to and following the completion of space segment equipment thermal and mechanical tests."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.3.1f","Requirement","ECSS-E-ST-10-03_0750164",1,"Unchanged","Leak tests shall be conducted prior to and following proof pressure tests."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.3.1g","Requirement","ECSS-E-ST-10-03_0750165",1,"Unchanged","When temperature potentially affects the sealing materials or surfaces, an evaluation of the hardware design and operational characteristics shall be performed and, if technically warranted, the leak test conducted at the minimum and maximum qualification or acceptance temperature limits for respectively qualification or acceptance test."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.3.1h","Requirement","ECSS-E-ST-10-03_0750166",2,"Normative Change","If seals are dependent upon differential pressure for proper sealing, leak tests shall also be performed with the space segment equipment pressurized at the maximum and the minimum differential pressure expected in operation. ","NOTE \tThis can be the case for valves.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.3.1i","Requirement","ECSS-E-ST-10-03_0750477",1,"Unchanged","If the containment of hazardous fluids requires a design providing a double, redundant seal, the leak test shall be performed in two steps, testing separately the two seals."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.3.2a","Requirement","ECSS-E-ST-10-03_0750167",2,"Normative Change","The proof pressure qualification test shall be performed to demonstrate that the equipment meets the specified requirements after having been submitted to the proof pressure.","NOTE \tOne of the requirements for pressurized hardware can be maximum leak rate that is tested in a subsequent leak test.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.3.2b","Requirement","ECSS-E-ST-10-03_0750168",2,"Normative Change","The proof pressure acceptance test shall be performed to demonstrate that the equipment meets the specified requirements after having been submitted to the proof pressure.. ","NOTE \tOne of the requirements for pressurized hardware can be maximum leak rate that is tested in a subsequent leak test.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.3.2c","Requirement","ECSS-E-ST-10-03_0750169",1,"Unchanged","The influence of temperature on test validity shall be in conformance with ECSS-E-ST-32-02 requirements 5.4.1c and 5.5.1b."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.3.3a","Requirement","ECSS-E-ST-10-03_0750170",1,"Unchanged","Pressure cycling test shall be performed in conformance with ECSS-E-ST-32-02 clause 5.4.5."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.3.3b","Requirement","ECSS-E-ST-10-03_0750171",1,"Unchanged","The influence of temperature on test validity shall be taken into account by applying ECSS-E-ST-32-02 requirement 5.4.1c."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.3.4a","Requirement","ECSS-E-ST-10-03_0750172",1,"Unchanged","The influence of temperature on test validity shall be taken into account by applying ECSS-E-ST-32-02 requirement 5.4.1c."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.3.4b","Requirement","ECSS-E-ST-10-03_0750173",1,"Unchanged","After burst pressure, no space segment equipment or any of its parts shall be used for further qualification activities or as flight hardware."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.3.5a","Requirement","ECSS-E-ST-10-03_0750174",1,"Unchanged","Burst test shall be performed in conformance with ECSS-E-ST-32-02 clause 5.4.7."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.1a","Requirement","ECSS-E-ST-10-03_0750175",2,"Normative Change","Both thermal vacuum test and thermal test at mission pressure shall be performed for space segment equipment that operate under a non-vacuum environment after having been exposed to vacuum.","NOTE\t1\tFor example, in the case of a planetary mission within an atmosphere, the space segment equipment is tested in vacuum and in the mission atmosphere pressure.\nNOTE\t2\tAt space segment equipment level, the version C of ECSS-E-ST-10-03 does not consider a thermal test at room pressure (also called \"thermal cycling\", by example, in US standards and in the version A of ECSS-E-ST-10-03).\nNOTE\t3\tAt space segment equipment level, clause 5.5.4.4 of ECSS-E-HB-10-03 gives guidelines for assessment of alternative thermal testing approaches using room pressure temperature cycling tests.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.1b","Requirement","ECSS-E-ST-10-03_0750176",2,"Normative Change","Thermal balance phase(s), if required, shall be included in the thermal vacuum test or in the thermal test at a pressure value corresponding to the type of mission.","NOTE \tE.g. for very dissipative equipment, equipment with important temperature differences at vacuum conditions, Earth atmospheric pressure, space station pressure or Mars pressure.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.1c","Requirement","ECSS-E-ST-10-03_0750177",1,"Unchanged","All space segment equipment temperatures shall refer to the temperature reference point."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.1d","Requirement","ECSS-E-ST-10-03_0750178",1,"Unchanged","The space segment equipment temperatures shall be defined for the following conditions:\n1.\tminimum and maximum operating qualification and acceptance;\n2.\tminimum and maximum non-operating qualification, and acceptance;\n3.\tminimum switch ON and maximum (as relevant)."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.1e","Requirement","ECSS-E-ST-10-03_0750179",1,"Unchanged","The test level shall take into account the test tolerances as specified in Table 4‑1."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.1f","Requirement","ECSS-E-ST-10-03_0750180",1,"Unchanged","The temperature rate of change shall be lower than 20 K per minute."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.1g","Requirement","ECSS-E-ST-10-03_0750181",2,"Normative Change","Functional test shall only start after a dwell time greater or equal to 2 hours, except for solar arrays, see Table 5‑2, Table 5‑4, Table 5‑6 for plateau duration."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.1h","Requirement","ECSS-E-ST-10-03_0750182",1,"Unchanged","Test profile, test configuration, number of cycles, extreme temperatures, temperature rate of change, stability criteria, dwell time duration, tests to be performed and success criteria shall be defined in the test specification."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.1i","Requirement","ECSS-E-ST-10-03_0750183",1,"Unchanged","The test profile shall include a non operating cycle."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.1j","Requirement","ECSS-E-ST-10-03_0750184",1,"Unchanged","The space segment equipment shall be subjected to functional test before and after the thermal test."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.1k","Requirement","ECSS-E-ST-10-03_0750185",1,"Unchanged","Functional tests shall be performed as a minimum at hot and cold operating temperatures.","NOTE \tTest during transition are subjected to case by case decision.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.1l","Requirement","ECSS-E-ST-10-03_0750186",2,"Normative Change","Equipment switch on capabilities shall be demonstrated at minimum switch-on temperature and at maximum switch-on temperature."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.1m","Requirement","ECSS-E-ST-10-03_0750187",1,"Unchanged","In case of internal redundancy, thermal tests shall be performed on both chains taking into account the type of redundancy (e.g. hot or cold)."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.1n","Requirement","ECSS-E-ST-10-03_0750188",1,"Unchanged","In case of cross-strapped configurations, requirements for testing shall be agreed with the customer."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.1o","Requirement","ECSS-E-ST-10-03_0750189",1,"Unchanged","The space segment equipment operative configuration during the test shall be the most severe one in the power time domain and from the power consumption point of view."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.1p","Requirement","ECSS-E-ST-10-03_0750190",1,"Informative Change","Monitoring for corona shall be conducted during chamber pressure reduction for space segment equipment that are critical with regard to corona effect.","NOTE \tFor thermal test at mission pressure, this is justified by the fact that atmospheric pressure can be lower than Earth atmospheric pressure.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.1q","Requirement","ECSS-E-ST-10-03_0750191",1,"Unchanged","Test methods and test set-up shall be defined according to the thermal environment characteristics, the TCS thermal design and the space segment equipment itself."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.1r","Requirement","ECSS-E-ST-10-03_0750192",1,"Unchanged","The test set-up shall ensure appropriate orientation for space segment equipment containing two phases heat transport equipment (e.g. heat pipe).","NOTE \tThis means that the two phases heat transport equipment is horizontal or works in reflux mode.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.1s","Requirement","ECSS-E-ST-10-03_0750478",1,"Unchanged","Outside the functional and performance tests of the required test profile, the equipment shall be continuously powered on, when compatible with test profile, and parameters monitored to detect intermittent or persistent defects."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.2a","Requirement","ECSS-E-ST-10-03_0750193",1,"Unchanged","Thermal vacuum testing shall be performed for space segment equipment whose operation occurs in space vacuum environment at any time of its lifetime."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.2b","Requirement","ECSS-E-ST-10-03_0750194",1,"Unchanged","Space segment equipment shall be tested at a pressure of 10-5 hPa or less."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.2c","Requirement","ECSS-E-ST-10-03_0750195",1,"Unchanged","Conditions and test set-up shall be such as to avoid contamination of the equipment."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.2d","Recommendation","ECSS-E-ST-10-03_0750456",1,"Unchanged","In line with requirement 5.5.4.2c the test profile should start with a maximum non-operating temperature."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.2e","Requirement","ECSS-E-ST-10-03_0750197",1,"Unchanged","For solar array, continuity and insulation resistance shall be monitored during the test as per ECSS-E-ST-20-08 requirements 5.5.3.11.2 f and g."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.3a","Requirement","ECSS-E-ST-10-03_0750198",2,"Normative Change","Test approach with thermal test at mission pressure without vacuum test shall be selected only for space segment equipment that operates under a non-vacuum environment during their entire lifetime.","NOTE \tIn assessing this, depressurisation failure should be considered.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.3b","Requirement","ECSS-E-ST-10-03_0750199",2,"Normative Change","Pressure value shall be as per type of mission.","NOTE \tE.g. Earth atmospheric pressure, space station pressure, Mars pressure.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.3c","Requirement","ECSS-E-ST-10-03_0750200",1,"Unchanged","Climatic conditions shall be such as to avoid condensation on the item under test."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.4.3d","Requirement","ECSS-E-ST-10-03_0750201",2,"Normative Change","The space segment equipment shall be mounted in a temperature chamber if the atmospheric mission pressure is near the Earth atmospheric pressure and in a pressure chamber with temperature control capability or in a vacuum chamber with pressure and temperature control capabilities if the atmospheric mission pressure is different from the Earth atmospheric pressure."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.5.1a","Requirement","ECSS-E-ST-10-03_0750202",1,"Unchanged","The EMC test shall be performed in conformance with ECSS-E-ST-20-07 clause 5."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.5.1b","Requirement","ECSS-E-ST-10-03_0750203",1,"Unchanged","For acceptance stage, the space segment equipment shall be subjected to the following tests, as per ECSS-E-ST-20-07:\n1.\tbonding verification;\n2.\tpower lines isolation;\n3.\tinrush current;\n4.\tconducted emission time domain (ripple and spikes) on power lines in the operating mode, which produces maximum emissions;\n5.\tconducted emission frequency domain on power lines in the operating mode, which produces maximum emissions."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.5.1c","Requirement","ECSS-E-ST-10-03_0750204",1,"Unchanged","For RF space segment equipment sniff or spray test shall be performed at one or several frequencies used by the space segment equipment under test or in mission critical receive bands."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.5.1d","Recommendation","ECSS-E-ST-10-03_0750457",1,"Unchanged","Sniff or spray test should be performed with a guide to coax transitions at a controlled distance."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.5.2a","Requirement","ECSS-E-ST-10-03_0750206",1,"Unchanged","The magnetic test shall be performed in conformance with ECSS-E-ST-20-07 clause 4.2.5 and 5.4.5."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.5.3a","Requirement","ECSS-E-ST-10-03_0750207",1,"Unchanged","The ESD test on space segment equipment shall be performed in conformance with ECSS-E-ST-20-07 clause 5.4.12."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.5.4a","Requirement","ECSS-E-ST-10-03_0750208",1,"Unchanged","The passive intermodulation test shall be performed in conformance with ECSS‐E‐ST‐20."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.5.5a","Requirement","ECSS-E-ST-10-03_0750209",2,"Normative Change","The multipactor test shall be performed in conformance with ECSS‐E‐ST-20-01."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.5.6a","Requirement","ECSS-E-ST-10-03_0750210",1,"Unchanged","Corona and arc discharge test shall be performed for space segment equipment exposed to the critical low pressure atmosphere according to relevant Paschen curves during its lifetime.","NOTE \tDemonstration of margin for corona and arc discharges effect is mainly achieved by analysis, and by component/ sub assembly or development model level test. During space segment element qualification programme, it is unlikely that margin can be applied (i.e. on voltage or output power for RF), the test is then limited to a go/nogo test.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.6.1.1a","Requirement","ECSS-E-ST-10-03_0750211",2,"Normative Change","During the audible noise test the space segment equipment sound power level transmitted via airborne shall be measured."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.6.1.1b","Requirement","ECSS-E-ST-10-03_0750212",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.6.1.1c","Requirement","ECSS-E-ST-10-03_0750213",2,"Normative Change","The noise level and exposure time shall be measured for each operational mode of the space segment equipment."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.6.1.2a","Requirement","ECSS-E-ST-10-03_0750214",2,"Normative Change","The space segment equipment sound power measurements shall be performed in accordance with ISO 3740:2019."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.6.1.2b","Requirement","ECSS-E-ST-10-03_0750215",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.6.1.3a","Requirement","ECSS-E-ST-10-03_0750216",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","5.5.6.1.3b","Requirement","ECSS-E-ST-10-03_0750217",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.1a","Permission","ECSS-E-ST-10-03_0750458",1,"Informative Change","When it is not feasible to test a space segment element as a single entity, it may be tested separately as several space segment elements or space segment equipment.","NOTE\t1\tFor example, when it is not feasible due to its size, which can exceed the capacity of a test facility.\nNOTE\t2\tFor example, a test on a space segment element can be split into a service module test and a payload module test.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.1b","Requirement","ECSS-E-ST-10-03_0750219",2,"Normative Change","The effects of item(s), which are interacting on the space segment element level, but which are not present during tests, shall be included with the support of simulators.","NOTE \tSimulators can be fluid, mechanical, thermal, electrical item(s) or software.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.1c","Requirement","ECSS-E-ST-10-03_0750220",1,"Unchanged","The test baseline shall be tailored for each project."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.1d","Requirement","ECSS-E-ST-10-03_0750221",2,"Normative Change","The sequence of tests shall be agreed by the customer depending on the nature of the space segment element and how performances are tested.","NOTE\t1\tFor Infrared instrument or satellite including IR instrument the TV test is the one that allows performance verification, in this case it is often the last test performed.\nNOTE\t2\tFor RF radiometer the performance are verified in anechoic chamber, in this case the auto compatibility / Radiated EMC is often one of the last tests performed.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.1e","Recommendation","ECSS-E-ST-10-03_0750459",1,"Informative Change","For space segment element undergoing a PFM approach, the equipment that are part of it, should be acceptance tested.","NOTE \tThis implies that the equipment design is already qualified.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.1f","Requirement","ECSS-E-ST-10-03_0750223",1,"Unchanged","Any unusual or unexpected behaviour shall be evaluated to determine the existence of any trend potentially leading to anomaly or failure situation."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.1g","Requirement","ECSS-E-ST-10-03_0750224",1,"Unchanged","Visual inspections shall be performed before and after each test."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.2a","Requirement","ECSS-E-ST-10-03_0750225",1,"Unchanged","When a full Qualification model is developed for a space segment elements qualification the test baseline shall consist of the tests specified in Table 6‑1.","NOTE \tOther special tests can be performed depending upon the project characteristics and product lifetime cycle.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.3a","Requirement","ECSS-E-ST-10-03_0750226",1,"Unchanged","For space segment elements where full qualification has been obtained on another model(s), the Flight Model(s) acceptance test baseline shall consist of the tests specified in Table 6‑3."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.4a","Requirement","ECSS-E-ST-10-03_0750227",1,"Unchanged","The space segment elements Proto-qualification test baseline shall consist of the tests specified in Table 6‑5.","NOTE \tOther special tests can be performed depending upon the project characteristics and product lifetime cycle.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.4b","Requirement","ECSS-E-ST-10-03_0750228",2,"Normative Change","When part of the qualification is obtained on other model(s), then the PFM shall be tested in accordance with Table 6‑3 for the relevant type(s) of test.","NOTE \tFor example, if mechanical qualification is obtained on a STM then the PFM is tested, for mechanical aspects, in accordance with the acceptance requirements.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.1a","Requirement","ECSS-E-ST-10-03_0750229",1,"Unchanged","The measurements, conducted either in a suitable optical alignment facility or in normal clean room with adequate measurement system, shall be performed throughout space segment element test campaign; and as a minimum, at the start and at the end of the environmental test campaign.","NOTE \tAlignment verification is repeated to track any degradation or to ensure that variation of space segment equipment alignment in relationship with the reference axes remain within the specified limits.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.1a","Requirement","ECSS-E-ST-10-03_0750230",1,"Unchanged","The FFT shall be performed in order to verify that the space segment element functions in conformance with the specification requirements in all operational modes, including back-up modes, and transients."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.1b","Requirement","ECSS-E-ST-10-03_0750231",1,"Unchanged","The RFT content shall be agreed with the customer."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.1c","Requirement","ECSS-E-ST-10-03_0750232",2,"Normative Change","Functional tests shall be performed, under room conditions as defined for clean rooms, at the beginning and at the end of the test programme providing the criteria for judging the integrity of the space segment element thought the overall test programme.","NOTE \tThe results of both tests should be identical within the test tolerances.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.1d","Requirement","ECSS-E-ST-10-03_0750233",1,"Unchanged","Additional tests (PT, FFT or RFT as relevant) shall be performed during the thermal test.","NOTE \tThe space segment element is expected to be operative under these conditions.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.1e","Requirement","ECSS-E-ST-10-03_0750234",1,"Unchanged","Additional functional tests to be performed before and after each environmental exposure and transport(s) shall be agreed with the customer.","NOTE \tThose tests are limited to RFT to provide the criteria for judging successful survival of the space segment.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.1f","Recommendation","ECSS-E-ST-10-03_0750460",2,"Normative Change","The FFT activities should follow the expected mission sequence, properly involving the interested functions, with the space segment element correct configuration for the particular mission phase."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.1g","Requirement","ECSS-E-ST-10-03_0750236",1,"Unchanged","If an on-board or an EGSE software update is needed during the test campaign, the step at which the software is loaded, as well as the level of retesting, shall be agreed with the customer."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.2a","Requirement","ECSS-E-ST-10-03_0750237",1,"Informative Change","The mechanical functions of the space segment element shall be tested under the specified operating conditions as a major input to verify that they conform to the specified performance.","NOTE\t1\tTest is complemented by analysis and test at equipment level to take into account other design parameters that cannot be tested at space segment element level and the effect of the environment simulation (zero G device).\nNOTE\t2\tExamples of such mechanical functions are mechanisms, deployable device, valves and other mechanical devices.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.2b","Requirement","ECSS-E-ST-10-03_0750238",1,"Unchanged","For all mechanical operations that can be disturbed by Earth’s gravity field, suitable ground support fixtures shall be employed to enable operation and evaluation of the devices."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.2c","Requirement","ECSS-E-ST-10-03_0750239",1,"Unchanged","If, for test limitation reason, the function cannot be tested at space segment element level, alternative verification method, that can include test at a lower level, shall be proposed for customer approval."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.2d","Requirement","ECSS-E-ST-10-03_0750240",1,"Unchanged","Mechanical functional verification shall be performed prior and subsequent to environmental test campaign."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.3a","Requirement","ECSS-E-ST-10-03_0750241",1,"Unchanged","Electrical functional tests shall verify that the electrical functions of the space segment element can be performed under the specified operating conditions with the specified performance."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.3b","Requirement","ECSS-E-ST-10-03_0750242",2,"Normative Change","The following protection functions shall be tested:\n1.\tinter-locks, if any;\n2.\toverriding capabilities of protection functions."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.3c","Requirement","ECSS-E-ST-10-03_0750243",1,"Unchanged","During the electrical functional tests, all components shall be operated, including redundant space segment equipment and paths, taking into account the type of redundancy (e.g. hot or cold).","NOTE \tPyrotechnic devices are replaced by simulators that can be energized and monitored.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.3d","Requirement","ECSS-E-ST-10-03_0750244",1,"Unchanged","For cross-strapped configurations, requirements for testing shall be agreed with the customer."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.3e","Requirement","ECSS-E-ST-10-03_0750245",1,"Unchanged","All TM/TC shall be tested with the actual data base used for operations."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.3f","Requirement","ECSS-E-ST-10-03_0750246",1,"Unchanged","It shall be verified that autonomous functions are performed when the defined conditions, for which they are designed, are present."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.3g","Requirement","ECSS-E-ST-10-03_0750247",1,"Unchanged","Any triggering of an autonomous action not in line with the conditions for which they are designed shall be tracked as an anomaly."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.3h","Requirement","ECSS-E-ST-10-03_0750248",1,"Unchanged","Autonomous lockout or shutdown sequences shall be verified to ensure that they do not adversely affect other system operations during or subsequent to the intended lockout or shutdown."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.3i","Requirement","ECSS-E-ST-10-03_0750249",1,"Unchanged","For non-regulated bus, one subset of functional tests, which is subject to agreement between customer and supplier, shall be run at both the minimum and maximum bus voltage level."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.3j","Requirement","ECSS-E-ST-10-03_0750250",1,"Unchanged","The electrical functional verification shall ensure that no function other than the intended function is activated and no spurious signals or effects are present.","NOTE \tFor example, an LCL trip-off does not affect any other distributed line.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.3k","Permission","ECSS-E-ST-10-03_0750461",1,"Unchanged","Actual tests of pyrotechnic devices may be conducted at space segment equipment or component levels."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.2.3l","Requirement","ECSS-E-ST-10-03_0750252",1,"Unchanged","The space segment element communication links shall be tested in a representative operational way.","NOTE \tThis includes test of cross strapping and all redundancies. It also includes the TM/TC if the frequency used can lead to interference. It can be combined with the RF auto-compatibility test. The RF auto-compatibility test is part of the overall electromagnetic auto-compatibility defined in clause 6.5.5.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.3a","Requirement","ECSS-E-ST-10-03_0750253",1,"Unchanged","Performance tests shall verify that the space segment element provide the specified performances for the required function.","NOTE \tPerformance tests are mainly defined for payload. At satellite level performances are mostly checked at payload or subsystem level.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.3b","Requirement","ECSS-E-ST-10-03_0750254",1,"Unchanged","For cross-strapped configuration, requirements for performance tests shall be agreed with the customer."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.3c","Requirement","ECSS-E-ST-10-03_0750255",1,"Unchanged","Performance tests shall be performed under the necessary environmental conditions that allow performances to be achieved."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.3d","Requirement","ECSS-E-ST-10-03_0750256",1,"Unchanged","Performance tests shall be performed after the end of the environmental test programme."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.4a","Requirement","ECSS-E-ST-10-03_0750257",1,"Unchanged","Mission tests shall include simulation of mission cases in nominal situations on the space segment element for the critical and main operations of the entire mission profile, within the constraints of what can be simulated on ground, with the events occurring in the actual flight sequence.","NOTE \tFor example: final count-down, launch, ascent, separation, switch-on, early orbital operations, apogee motor operations, commissioning, mission operations, manoeuvres and return operations.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.4b","Requirement","ECSS-E-ST-10-03_0750258",1,"Unchanged","Mission tests shall include simulation of mission cases in contingency situations on the space segment element for the critical and main contingency operations of the entire mission profile, within the constraints of what can be simulated on ground.","NOTE \tThe critical and main contingency operations are for example those: \n·\twhen the space segment element is or could be in danger, \n·\twhich are time critical, \n·\tto recover from a safe mode, \n·\tto reconfigure the space segment element after a major failure.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.4c","Requirement","ECSS-E-ST-10-03_0750259",1,"Unchanged","To reduce the risk of error accumulation during mission test, the space segment element shall be kept uninterrupted ON according to the test profile, to be agreed with the customer, in terms of modes, modes transition and modes duration.","NOTE \tThe definition of the mission test takes into account the typical mission scenario, able to completely exercise all modes and transitions and all software functions under an interrupted operational environment.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.4d","Requirement","ECSS-E-ST-10-03_0750260",1,"Unchanged","The mission tests on the space segment element shall be run with the final flight software configured as for flight."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.5a","Requirement","ECSS-E-ST-10-03_0750261",1,"Unchanged","The polarity test shall cover all functional chains and equipment sensitive to polarity errors.","NOTE \tPolarity test is not limited to AOCS space segment equipment. For examples solar array drive mechanism.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.5b","Requirement","ECSS-E-ST-10-03_0750262",2,"Normative Change","Polarity tests shall be performed, with the validated final software installed, in all critical modes, on all chains from sensor to actuator, with the space segment element in its final flight configuration. ","NOTE \tA mode is deemed critical for polarity testing in case a polarity error in this mode would not be recoverable and lead to mission loss or severe degradation of mission performance.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.5c","Requirement","ECSS-E-ST-10-03_0750263",1,"Unchanged","During the polarity test the AOCS shall be operated in the mode where the chain is used in the control loop."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.5d","Requirement","ECSS-E-ST-10-03_0750264",1,"Unchanged","The polarity test shall be one of the last tests before shipment to the launch site."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.5e","Requirement","ECSS-E-ST-10-03_0750479",1,"Unchanged","In addition to requirement 6.5.1.5b, for non-critical modes, polarity tests shall be performed in one of the following two ways: \n1.\tidentical to critical mode, or\n2.\tby individual tests on sensors and actuators combined with the final version of the SW components relevant for overall polarity, demonstrating the validity of the end-to-end polarity by a synthesis of all these tests."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.6a","Requirement","ECSS-E-ST-10-03_0750265",2,"Normative Change","The interface between the space segment element and the launcher shall be tested, using space segment elements or subset of them representative of the interfaces to be tested, under realistic conditions, to verify the related system requirements.","NOTE \tThese tests cover the mechanical, electrical and data interfaces (e.g. clamp-band release test, space segment element-launcher fit check).\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.6b","Requirement","ECSS-E-ST-10-03_0750266",2,"Normative Change","The interface between the space segment element and the launch facility shall be verified before actual space segment element operation."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.1.6c","Requirement","ECSS-E-ST-10-03_0750267",1,"Unchanged","The test to be executed and approach shall be covered in the contractual documentation between space segment element authority and launch segment authority (e.g. ICD, or user manual)."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.1a","Requirement","ECSS-E-ST-10-03_0750268",1,"Unchanged","The physical properties measurement shall include:\n1.\tMass\n2.\tCentre of Gravity\n3.\tMoment of Inertia"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.1b","Requirement","ECSS-E-ST-10-03_0750269",1,"Unchanged","Physical properties shall be measured for the launch and orbit insertion configurations, and atmospheric entry when relevant.","NOTE \tDepending upon the mission profile other configurations can be used.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.1c","Requirement","ECSS-E-ST-10-03_0750270",1,"Unchanged","The tolerances shall be the minimum values specified in either Table 4‑1 or in the launcher user’s manual.","NOTE \tLaunch configuration balance requirements are stated in the launcher user’s manual.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.1d","Permission","ECSS-E-ST-10-03_0750462",2,"Normative Change","For a large space segment element, the physical properties may be calculated using data from equipment individual measurements providing the final results meet the specified maximum allowable uncertainty."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.1e","Requirement","ECSS-E-ST-10-03_0750272",1,"Unchanged","Spin balance tests shall be used for spin stabilized systems."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.1f","Requirement","ECSS-E-ST-10-03_0750273",1,"Unchanged","If spin balance tests are performed with an empty tank, a correlation with the analytical model (tank full) shall be performed.","NOTE \tOperational spin balance requirements vary widely depending on the mission profile and rate of spin; therefore, specific balance requirements and procedures are stated in the space segment element specifications.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.2a","Requirement","ECSS-E-ST-10-03_0750274",1,"Unchanged","The modal survey shall be conducted on a structural representative model in conformance with ECSS-E-ST-32-11."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.3a","Requirement","ECSS-E-ST-10-03_0750275",2,"Normative Change","Boundary conditions, in the static load test, shall be demonstrated to be representative of flight boundary constraints or alternatively test forces on boundary constraints be measured."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.3b","Requirement","ECSS-E-ST-10-03_0750276",2,"Normative Change","When a dummy structure is used in the static load test, it shall be demonstrated that it is representative in terms of stiffness and as far as the constraints imposed by the replaced flight component are concerned."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.4a","Requirement","ECSS-E-ST-10-03_0750277",1,"Unchanged","Spin tests shall be conducted in spin operation configuration."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.4b","Permission","ECSS-E-ST-10-03_0750463",1,"Unchanged","When the appendage size prevents requirement 6.5.2.4a to be met alternative configuration may be considered."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.4c","Requirement","ECSS-E-ST-10-03_0750279",1,"Unchanged","Propellant tanks shall be at least mass and stiffness representative during spin testing.","NOTE \tSimulated propellant can be used.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.5a","Requirement","ECSS-E-ST-10-03_0750280",2,"Normative Change","Transient and sine burst tests shall be conducted in launch configuration.","NOTE \tTransient test reproduces launch events (coming from launcher data) in time domain on a shaker.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.5b","Requirement","ECSS-E-ST-10-03_0750281",2,"Normative Change","Propellant storage tanks shall be at least mass and stiffness representative during transient and sine burst tests.","NOTE \tSimulated propellant can be used. Empty tank testing needs to be considered case by case.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.5c","Requirement","ECSS-E-ST-10-03_0750282",2,"Normative Change","The internal pressure decay due to the leakage shall be verified for pressurized space segment equipment being part of the space segment element under test."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.5d","Requirement","ECSS-E-ST-10-03_0750283",1,"Unchanged","Space segment element equipped with apogee or retro motors shall be tested for the vibration environment generated by the motor if\n1.\tthe environment is not enveloped by the launch boost environment; or\n2.\tthe configuration during the apogee or retro motor burn is different from the launch configuration."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.5e","Requirement","ECSS-E-ST-10-03_0750284",2,"Normative Change","A resonance search shall be performed before and after the transient and sine burst tests to determine resonance frequencies to evaluate the product integrity."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.5f","Requirement","ECSS-E-ST-10-03_0750285",1,"Unchanged","The success criteria for the resonance search shall be:\n1.\tless than 5 % in frequency shift, for modes with an effective mass greater than 10 %;\n2.\tless than 20 % in amplitude shift, for modes with an effective mass greater than 10 %."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.5g","Requirement","ECSS-E-ST-10-03_0750286",2,"Normative Change","For the transient test, the excitation signals shall be derived from the space segment element and launcher loads coupled dynamic analysis (LCDA).","NOTE \tAlthough transient test methods are fairly advanced, a number of problems with respect to uncertainties resulting from the analytical process on the test input functions and statistical variations are still to be resolved. Transient tests can relatively easily replace longitudinal tests, but experience is very limited in lateral testing.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.6a","Requirement","ECSS-E-ST-10-03_0750287",2,"Normative Change","Acoustic tests shall be conducted with the space segment element in launch configuration mounted on a test fixture."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.6b","Requirement","ECSS-E-ST-10-03_0750288",1,"Unchanged","The test fixture shall be decoupled from the chamber."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.6c","Requirement","ECSS-E-ST-10-03_0750289",1,"Unchanged","Propellant tanks shall be at least mass and stiffness representative during acoustic testing.","NOTE \tSimulated propellant can be used.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.6d","Requirement","ECSS-E-ST-10-03_0750290",1,"Unchanged","The internal pressure decay shall be verified for pressurized space segment equipment being part of the space segment element under test."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.6e","Requirement","ECSS-E-ST-10-03_0750291",1,"Unchanged","Space segment equipment, within the space segment element, which operate during launch, shall be operated and monitored during the test."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.6f","Requirement","ECSS-E-ST-10-03_0750292",1,"Unchanged","In case the launch configuration introduces specific acoustic loads, the test set up shall be representative of the launch configuration.","NOTE \tExamples are: several space segment elements attached to a common structure during launch, presence of test standing waves between opposite wall.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.6g","Requirement","ECSS-E-ST-10-03_0750293",1,"Unchanged","In order to evaluate the product integrity a low level acoustic run shall be performed before and after the acoustic run for determining resonant frequencies.","NOTE \tTypical value for the low level acoustic is -8 dB the qualification level.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.6h","Requirement","ECSS-E-ST-10-03_0750294",1,"Unchanged","The success criteria for the resonance search shall be:\n1.\tless than 5 % in frequency shift, for modes with an effective mass greater than 10 %;\n2.\tless than 40 % in amplitude shift, for modes with an effective mass greater than 10 %."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.7a","Requirement","ECSS-E-ST-10-03_0750295",1,"Unchanged","Random vibration tests shall be conducted in launch configuration for all axes."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.7b","Requirement","ECSS-E-ST-10-03_0750296",1,"Unchanged","Random excitations shall cover the three mutually orthogonal directions, one being parallel to the thrust axis."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.7c","Requirement","ECSS-E-ST-10-03_0750297",1,"Unchanged","Propellant tanks shall be at least mass and stiffness representative during random testing.","NOTE \tSimulated propellant can be used.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.7d","Requirement","ECSS-E-ST-10-03_0750298",1,"Unchanged","The internal pressure decay shall be verified for pressurized space segment equipment being part of the space segment element under test."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.7e","Requirement","ECSS-E-ST-10-03_0750299",1,"Unchanged","Space segment element equipped with apogee or retro motors shall be tested for the vibration environment generated by the motor if\n1.\tthe environment is not enveloped by the launch boost environment; or\n2.\tthe configuration during the apogee or retro motor burn is different from the launch configuration."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.7f","Requirement","ECSS-E-ST-10-03_0750300",1,"Unchanged","Notching criteria and implementation shall be approved by the customer and, if relevant, by the launcher authority."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.7g","Requirement","ECSS-E-ST-10-03_0750301",1,"Unchanged","The induced cross axis accelerations at the attachment points shall be limited to the maximum test levels specified for the cross axis. "]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.7h","Requirement","ECSS-E-ST-10-03_0750302",1,"Unchanged","Space segment equipment, being part of the space segment element, that operates during launch shall be operated and monitored during the test."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.7i","Requirement","ECSS-E-ST-10-03_0750303",1,"Unchanged","In order to evaluate the space segment element integrity a resonance search shall be performed before and after the random vibration test by determining resonant frequencies."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.7j","Requirement","ECSS-E-ST-10-03_0750304",1,"Unchanged","The success criteria for the resonance search shall be:\n1.\tless than 5 % in frequency shift, for modes with an effective mass greater than 10 %;\n2.\tless than 20 % in amplitude shift, for modes with an effective mass greater than 10 %."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.7k","Requirement","ECSS-E-ST-10-03_0750305",1,"Unchanged","For space segment element which is designed to be re-flown, the qualification test duration per axis shall be in conformance with Table 6‑2 plus 50 seconds per additional flight."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.8a","Requirement","ECSS-E-ST-10-03_0750306",1,"Unchanged","Sinusoidal vibration tests shall be conducted in launch configuration for the three mutually orthogonal directions, one being parallel to the thrust axis."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.8b","Requirement","ECSS-E-ST-10-03_0750307",1,"Unchanged","Propellant storage tanks shall be at least mass and stiffness representative during sinusoidal vibration test.","NOTE \tSimulated propellant can be used.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.8c","Requirement","ECSS-E-ST-10-03_0750308",1,"Unchanged","The internal pressure decay shall be verified for pressurized space segment equipment being part of the space segment element under test."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.8d","Requirement","ECSS-E-ST-10-03_0750309",1,"Unchanged","Notching criteria and implementation shall be approved by the customer and, if relevant, by the launcher authority."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.8e","Requirement","ECSS-E-ST-10-03_0750310",1,"Unchanged","Space segment element equipped with apogee or retro motors shall be tested for the vibration environment generated by the motor if\n1.\tthe environment is not enveloped by the launch boost environment; or\n2.\tthe configuration during the apogee or retro motor burn is different from the launch configuration."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.8f","Requirement","ECSS-E-ST-10-03_0750311",1,"Unchanged","Automatic protection measures shall be implemented during the test to prohibit excessive resonance build-up leading to hardware damage.","NOTE \tThis is achieved for example by means of abort and notch accelerometers control.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.8g","Requirement","ECSS-E-ST-10-03_0750312",1,"Unchanged","A resonance search shall be performed before and after the sinusoidal vibration tests to determine resonance frequencies to evaluate the product integrity and to compare the resonance frequency distribution with that of the mathematical model or modal survey.","NOTE\t1\tAny significant shift in resonance frequencies from those analytically determined is an indication of improper assembly or materials defects.\nNOTE\t2\tThis resonance search can be used to update the Finite Element Model in case of design modification w.r.t. the previously tested model.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.8h","Requirement","ECSS-E-ST-10-03_0750313",1,"Unchanged","The success criteria for the resonance search shall be:\n1.\tless than 5 % in frequency shift, for modes with an effective mass greater than 10 %;\n2.\tless than 20 % in amplitude shift, for modes with an effective mass greater than 10 %."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.9a","Requirement","ECSS-E-ST-10-03_0750314",1,"Unchanged","During shock tests the space segment element shall be in an operating mode representative of launch, ascent phases or configuration relevant during the shock actuation."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.9b","Requirement","ECSS-E-ST-10-03_0750315",1,"Unchanged","The shock test shall yield the necessary data to pronounce the qualification of the space segment element.","NOTE\t\tThe qualification is commonly achieved at equipment level, by comparing the flight shock environment with the equipment qualification status (including the qualification margin). The space segment element shock test also allows, where relevant, to justify the omission of equipment level shock testing.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.9c","Requirement","ECSS-E-ST-10-03_0750316",1,"Unchanged","Separation shock tests shall be conducted by actuating the release devices and then verifying the separation."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.9d","Requirement","ECSS-E-ST-10-03_0750317",1,"Unchanged","Shocks induced by release or latching of appendages shall be tested by actuating the relevant devices and then verifying for correct functionality."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.9e","Requirement","ECSS-E-ST-10-03_0750318",1,"Unchanged","Shock sources that induce a shock response spectrum at any space segment equipment location that is within 6 dB of the envelope of the shock response spectra from all shock sources shall be considered as significant shock source."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.9f","Requirement","ECSS-E-ST-10-03_0750319",1,"Unchanged","Significant shock-producing devices or events, including those from sources not installed on the space segment element under test, shall be activated, simulated or demonstrated on representative hardware, and shock levels measured.","NOTE \tAs an example, pyro valves are not activated at space segment element level but tested on representative panels with shock levels measured at sensitive locations.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.9g","Requirement","ECSS-E-ST-10-03_0750320",1,"Unchanged","Activation of both primary and redundant devices inducing shock shall be carried out in the same sequence as they are intended to be operated."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.9h","Requirement","ECSS-E-ST-10-03_0750321",1,"Unchanged","Space segment equipment operating during the shock phases shall be operated during the test, and the main functional parameters monitored."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.9i","Requirement","ECSS-E-ST-10-03_0750322",1,"Unchanged","Space segment equipment not operating during the shock that can be damaged by shock, shall be monitored for input confirmation."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.10a","Requirement","ECSS-E-ST-10-03_0750323",2,"Normative Change","During performance test on a space segment element, the effect of each potential source of micro-vibration shall be tested separately by comparing tests with and without perturbation.","NOTE\t1\tcombined effects of several contributors can also be tested.\nNOTE\t2\tEffect of a source of micro-vibrations can also depend on the operating mode (e.g. reaction wheel speed) and/or test configuration (e.g. gravity orientation effect).\nNOTE\t3\tSusceptibility of the space segment element performance can also depend on the operating mode (e.g. integration time).\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.10b","Requirement","ECSS-E-ST-10-03_0750480",1,"Unchanged","The time signals of the measurements of the performance parameters as well as from the applied micro-vibration environment shall be recorded."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.10c","Requirement","ECSS-E-ST-10-03_0750481",1,"Unchanged","The background noise shall be measured, including each individual contribution from EGSE, MGSE, FGSE.","NOTE \tExample of FGSE: pumps.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.10d","Requirement","ECSS-E-ST-10-03_0750482",1,"Unchanged","If necessary, for the purpose of the test, mitigation actions shall be taken to reduce the background noise.","NOTE \tBackground noise can be due to the external environment (e.g. road, sea, wind, people around, other ongoing activities/tests), facilities (e.g. air conditioning, lights), MGSE, EGSE, FGSE (e.g. pumps). Background noise can be different depending on the time (night/day, presence of other activities).\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.11a","Requirement","ECSS-E-ST-10-03_0750483",1,"Unchanged","The micro-vibration environment induced by all activated disturbers during space segment element operation shall be measured, one by one.","NOTE\t1\tCombined effects of several contributors can be also measured. \nNOTE\t2\tEffect of a source of micro-vibrations can also depend on the operating mode (e.g. reaction wheel speed) and/or test configuration (e.g. gravity orientation effect).\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.11b","Requirement","ECSS-E-ST-10-03_0750484",1,"Unchanged","The time signals of the measurements shall be recorded."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.11c","Requirement","ECSS-E-ST-10-03_0750485",1,"Unchanged","The background noise shall be measured, including each individual contribution from EGSE, MGSE, FGSE.","NOTE \tExample of FGSE: pumps.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.2.11d","Requirement","ECSS-E-ST-10-03_0750486",1,"Unchanged","If necessary, for the purpose of the test, mitigation actions shall be taken to reduce the background noise.","NOTE \tBackground noise can be due to the external environment (e.g. road, sea, wind, people around, other ongoing activities/tests), facilities (e.g. air conditioning, lights), MGSE, EGSE, FGSE (e.g. pumps). Background noise can be different depending on the time (night/day, presence of other activities).\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.3.1a","Requirement","ECSS-E-ST-10-03_0750324",1,"Unchanged","The proof pressure test shall be performed before the environment tests."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.3.1b","Requirement","ECSS-E-ST-10-03_0750325",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.3.1c","Requirement","ECSS-E-ST-10-03_0750326",1,"Unchanged","Requirements of ECSS-E-ST-32-02 clauses 5.4.1 and 5.4.2 for qualification and protoflight, and clauses 5.5.1 and 5.5.2 for acceptance shall be applied for proof pressure tests."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.3.2a","Requirement","ECSS-E-ST-10-03_0750327",1,"Unchanged","Requirements of ECSS-E-ST-32-02 clauses 5.4.1 and 5.4.5 shall be applied for pressure cycling tests."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.3.3a","Requirement","ECSS-E-ST-10-03_0750328",2,"Normative Change","The design burst pressure tests shall be conducted by exposing the space segment element in the flight configuration.","NOTE \tThe model used can be a qualification or a structural model provided all pressure sensitive components are representative of the flight hardware. \n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.3.3b","Requirement","ECSS-E-ST-10-03_0750329",1,"Unchanged","The pumping capability of the test facility shall maintain the pressure within the specified limits at all times."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.3.3c","Requirement","ECSS-E-ST-10-03_0750330",1,"Unchanged","Requirements of ECSS-E-ST-32-02 clauses 5.4.1 and 5.4.6 shall be applied for design burst pressure tests."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.3.4a","Requirement","ECSS-E-ST-10-03_0750331",1,"Unchanged","All lines, joints and fittings shall be checked for leaks, on the fully assembled configuration of the space segment element."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.3.4b","Requirement","ECSS-E-ST-10-03_0750332",1,"Unchanged","When the fully assembled configuration precludes accessibility to perform requirement 6.5.3.4a, leak tests shall be conducted on a configuration to be agreed with the customer."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.3.4c","Requirement","ECSS-E-ST-10-03_0750333",1,"Unchanged","The method for checking leaks shall be selected according to the requirements to be met."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.1a","Requirement","ECSS-E-ST-10-03_0750334",2,"Normative Change","Both thermal vacuum test and thermal test at mission pressure shall be performed for space segment elements that operate under a non-vacuum environment after having been exposed to vacuum.","NOTE \tAt space segment element level, the version C of ECSS-E-ST-10-03 does not consider a thermal test at room pressure (also called \"thermal cycling\", by example, in US standards and in the version A of ECSS-E-ST-10-03).\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.1b","Requirement","ECSS-E-ST-10-03_0750335",1,"Unchanged","Test profile, test configuration, number of cycles, extreme temperatures, temperature rate of change, stability criteria, cycles and plateau duration, functional and performance tests to be performed and success criteria shall be defined in the test specification.","NOTE \tIt is not mandatory to include the solar array or large appendages in a space segment element thermal vacuum test. If it is however included, precautions should be taken to avoid overstress.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.1c","Requirement","ECSS-E-ST-10-03_0750336",1,"Unchanged","A reduced functional test shall be performed prior the closing of the chamber to validate the test configuration."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.1d","Requirement","ECSS-E-ST-10-03_0750337",1,"Unchanged","The sequence of functional tests shall be defined in the test specification such that all space segment equipment are tested."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.1e","Recommendation","ECSS-E-ST-10-03_0750464",1,"Unchanged","The most severe operative configuration should be tested with regard to the power time domain, the power consumption and the thermal dissipation point of view."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.1f","Requirement","ECSS-E-ST-10-03_0750339",1,"Unchanged","The equipment power ON/OFF status, throughout the test (including transitions), shall be defined in the test specification."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.1g","Requirement","ECSS-E-ST-10-03_0750340",1,"Unchanged","Functional tests shall be performed as a minimum at hot and cold plateaux.","NOTE \tMechanical functional test can be part of the functional test, pending on configuration or test set-up constraint\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.1h","Requirement","ECSS-E-ST-10-03_0750341",1,"Unchanged","Equipment switch on capabilities shall be demonstrated."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.1i","Requirement","ECSS-E-ST-10-03_0750342",1,"Unchanged","In case of redundancy, thermal tests shall be performed on both chains taking into account the type of redundancy (e.g. hot or cold)."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.1j","Requirement","ECSS-E-ST-10-03_0750343",1,"Unchanged","In case of cross-strapped configurations, requirements for testing shall be agreed with the customer."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.1k","Requirement","ECSS-E-ST-10-03_0750344",1,"Informative Change","Monitoring for corona shall be conducted during chamber pressure reduction for space segment equipment that are critical with regards to corona effect.","NOTE \tFor thermal test at mission pressure, this is justified by the fact that atmospheric pressure can be lower than Earth atmospheric pressure.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.1l","Requirement","ECSS-E-ST-10-03_0750345",1,"Unchanged","The temperatures of all the space segment equipment shall be monitored to ensure that the space segment equipment are not damaged during test."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.1m","Requirement","ECSS-E-ST-10-03_0750346",1,"Unchanged","Equipment temperatures within the space segment elements shall refer to the equipment temperature reference points."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.1n","Requirement","ECSS-E-ST-10-03_0750347",1,"Unchanged","Test methods and test set up shall be defined according to the thermal environment characteristics, the TCS thermal design, the space segment element itself and the need for thermal balance phases."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.1o","Requirement","ECSS-E-ST-10-03_0750348",1,"Unchanged","The rate of temperature change during cooling, and heating shall be the same as those projected for the mission, but not exceed them."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.1p","Requirement","ECSS-E-ST-10-03_0750349",1,"Unchanged","The test set-up and test modes shall be selected, in order to achieve the specified test temperatures within the specified stability and duration."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.1q","Requirement","ECSS-E-ST-10-03_0750350",1,"Unchanged","The test set-up shall ensure appropriate orientation for space segment elements containing two phase heat transport device (e.g. heat pipes)."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.2a","Requirement","ECSS-E-ST-10-03_0750351",1,"Unchanged","The set-up shall ensure that outgassing does not contaminate the space segment element."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.2b","Requirement","ECSS-E-ST-10-03_0750352",1,"Unchanged","The pressure during the test shall be maintained ≤ 10-5 hPa."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.3a","Requirement","ECSS-E-ST-10-03_0750353",2,"Normative Change","Test approach with thermal test at mission pressure without vacuum test shall be selected only for space segment elements that operate under a non-vacuum environment during their entire lifetime. ","NOTE \tIn assessing this, depressurisation failure should be considered. \n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.3b","Requirement","ECSS-E-ST-10-03_0750354",2,"Normative Change","Pressure value shall be as per type of mission. ","NOTE \te.g.. Earth atmospheric pressure, Mars pressure, Space Station pressure \n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.3c","Requirement","ECSS-E-ST-10-03_0750355",1,"Unchanged","Climatic conditions shall be such as to avoid condensation on the item under test."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.3d","Requirement","ECSS-E-ST-10-03_0750356",2,"Normative Change","The space segment element shall be mounted in a temperature chamber if the atmospheric mission pressure is near the Earth atmospheric pressure and in a pressure chamber with temperature control capability or in a vacuum chamber with pressure and temperature control capabilities if the atmospheric mission pressure is different from the Earth atmospheric pressure."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.4.4a","Requirement","ECSS-E-ST-10-03_0750357",1,"Unchanged","The thermal balance test shall be performed in conformance with ECSS-E-ST-31 clause 4.5.3."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.5.2.1a","Requirement","ECSS-E-ST-10-03_0750358",1,"Unchanged","The space segment element shall be subjected to EMC tests, specified in the ECSS-E-ST-20-07 clause 5.3 and in conformance with the Annex A of ECSS-E-ST-20."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.5.2.1b","Requirement","ECSS-E-ST-10-03_0750359",1,"Unchanged","When performing space segment element EMC test the compatibility tests with carrier or carried space segment elements shall also be included."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.5.2.2a","Requirement","ECSS-E-ST-10-03_0750360",1,"Unchanged","The space segment element shall be subjected to EMC tests, specified in the ECSS-E-ST-20-07 clause 5.4 and in conformance with the Annex A of ECSS-E-ST-20."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.5.3a","Requirement","ECSS-E-ST-10-03_0750361",1,"Unchanged","When performing space segment element EMC auto compatibility test the following EMC requirements shall be included:\n1.\tuse the most critical and sensitive operational modes, as defined by analysis;\n2.\tperform the auto-compatibility test in an anechoic chamber;\n3.\toperate the RF links in free space condition (i.e. no antenna cap, no coaxial or wave guide connection);\n4.\tdo not use radiated susceptibility tests for auto-compatibility demonstration purpose."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.5.4a","Requirement","ECSS-E-ST-10-03_0750362",1,"Unchanged","If results of PIM analysis show that PIM can be present, the space segment element shall be subjected to passive intermodulation tests.","NOTE \tFor PIM analysis refer to ECSS-E-ST-20 clause 7.4.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.5.4b","Requirement","ECSS-E-ST-10-03_0750363",1,"Unchanged","The operational configuration(s) for the PIM test shall conform to ECSS-E-ST-20 clause 7.4.","NOTE \tE.g. power level, temperature level.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.5.5a","Requirement","ECSS-E-ST-10-03_0750364",1,"Unchanged","The magnetic field measurement shall be performed in a dedicated facility featuring Earth field compensation."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.6.1a","Requirement","ECSS-E-ST-10-03_0750365",1,"Unchanged","The aero-thermodynamic tests shall be performed on dedicated scaled models in wind tunnels for different conditions.","NOTE\t1\tE.g. hot and cold hypersonic, low supersonic and subsonic.\nNOTE\t2\tThe aero-thermodynamic test verifies the aerodynamic and thermal loads on the space segment element performing atmospheric entry.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.7.1a","Requirement","ECSS-E-ST-10-03_0750366",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.7.1b","Requirement","ECSS-E-ST-10-03_0750367",2,"Normative Change",">>deleted>>"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.7.1c","Requirement","ECSS-E-ST-10-03_0750368",2,"Normative Change","The vibroacoustic noise measurements shall be performed in nominal emission conditions for each disturbance source one by one.","NOTE\t1\tCombined effects of several contributors can also be measured.\nNOTE\t2 \tEffect of a source of micro-vibrations can also depend on the operating mode (e.g. reaction wheel speed) and/or test configuration (e.g. gravity orientation effect).\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.7.1d","Requirement","ECSS-E-ST-10-03_0750487",1,"Unchanged","The time signals of the measurement shall be recorded."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.7.1e","Requirement","ECSS-E-ST-10-03_0750488",1,"Unchanged","The background noise shall be measured, including each individual contribution from EGSE, MGSE, FGSE.","NOTE \tExample of FGSE: pumps.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.7.1f","Requirement","ECSS-E-ST-10-03_0750489",1,"Unchanged","If necessary, for the purpose of the test, mitigation actions shall be taken to reduce the background noise."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.7.2a","Requirement","ECSS-E-ST-10-03_0750369",1,"Unchanged","The HFE tests shall be performed to demonstrate accessibility for man-machine interface usability and crew operability in a flight like environment by a representative population, using simulator or mock up.","NOTE \tThe test verifies requirements related to human factor engineering.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.7.3a","Requirement","ECSS-E-ST-10-03_0750370",1,"Unchanged","A toxic gas test shall be performed in thermal chamber to verify that the flight hardware does not produce toxic vapours that can build up to harmful levels for the crew in the closed loop life support system."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.7.3b","Requirement","ECSS-E-ST-10-03_0750371",1,"Unchanged","The item under test shall be heated and maintained in temperature conditions, while the emitted gasses and vapours are detected."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.7.3c","Requirement","ECSS-E-ST-10-03_0750372",1,"Unchanged","Toxic gas markers shall be used on the basis of the materials composing the item under test."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.7.4a","Requirement","ECSS-E-ST-10-03_0750373",1,"Unchanged","An audible noise test shall be performed to verify that the flight hardware does not produce audible noise levels that are detrimental to the crew health and safety."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.7.4b","Requirement","ECSS-E-ST-10-03_0750374",1,"Unchanged","Measured values shall not be higher than NC 50. "]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.7.4c","Requirement","ECSS-E-ST-10-03_0750375",1,"Unchanged","After a background noise measurement, the noise emission during space segment element operation shall be measured in the worst case emission conditions for qualification and in normal operation condition for acceptance."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.7.4d","Requirement","ECSS-E-ST-10-03_0750376",1,"Unchanged","Noise levels shall limit crew noise exposure to a 24-hour equivalent of 65 A-weighted decibel (dBA)."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","6.5.7.4e","Requirement","ECSS-E-ST-10-03_0750377",1,"Unchanged","Cabin reverberation time (T60) shall not exceed 0,5 second +/- 0,1 second at 500 Hz (Octave centre frequency)."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","7a","Requirement","ECSS-E-ST-10-03_0750378",1,"Unchanged","Pre-launch tests shall confirm that all elements needed for the launch, including their interfaces are verified, and that their parameters are within the specified limits.","NOTE\t1\tElements needed for the launch are: Launch segment element, space segment element and associated GSE.\nNOTE\t2\tFor space segment element, the set of parameters checked as part of pre-launch testing is a sub set of those used during AIT. The definition of this sub set is subject to agreement with the customer.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","7b","Requirement","ECSS-E-ST-10-03_0750379",1,"Unchanged","Pre-launch tests results shall result in the authorizing the next pre-launch activities to be carried out.","NOTE \tFor example leak test is performed to authorize fuelling.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","7c","Requirement","ECSS-E-ST-10-03_0750380",1,"Unchanged","The procedures to be executed during the launch campaign shall be rehearsed before the start of the launch campaign.","NOTE \tThis means that procedure used in pre-launch activities have been rehearsed, at least once during AIT.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","7d","Requirement","ECSS-E-ST-10-03_0750381",1,"Unchanged","The impact of any change on the EGSE shall be evaluated and the rehearsal repeated if it is so derived from the evaluation."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","7e","Requirement","ECSS-E-ST-10-03_0750382",1,"Unchanged","Pre-launch functional tests shall be performed to verify that no damage or performance degradation of the space segment element and its constituents has occurred during shipment or handling.","NOTE \tVerification of redundancy is included.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","7f","Requirement","ECSS-E-ST-10-03_0750383",1,"Unchanged","When a space segment element is not transported fully assembled or is subsequently disabled, the final assembly at launch site shall be retested.","NOTE \tFor example batteries, solar array. The level of retesting is subject to agreement with the customer.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","7g","Requirement","ECSS-E-ST-10-03_0750384",1,"Unchanged","The pre-launch functional test shall include a verification of electrical power interfaces and command and control functions as well as, when relevant, of radio frequency interference."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","7h","Requirement","ECSS-E-ST-10-03_0750385",1,"Unchanged","Circuit continuity, insulation and absence of stray energy shall be checked, at the level of the safe and arm plug connector, prior to connection the flight pyro arm plug."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","7i","Requirement","ECSS-E-ST-10-03_0750386",1,"Unchanged","If the pyro connections are planned in the launch facility, circuit continuity, insulation shall be checked, at the level of the safe and arm plug connector, prior to connection."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","7j","Requirement","ECSS-E-ST-10-03_0750387",1,"Unchanged","For crewed mission, final crew interface verification in all operational configurations shall be performed."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","A.2.1<1>a","Requirement","ECSS-E-ST-10-03_0750388",2,"Normative Change","The AIT Plan shall contain a description of the purpose, objective, content and the reason prompting its preparation."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","A.2.1<1>b","Requirement","ECSS-E-ST-10-03_0750389",1,"Unchanged","Any open issue, assumption and constraint relevant to this document shall be stated and described."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","A.2.1<2>a","Requirement","ECSS-E-ST-10-03_0750390",2,"Normative Change","The AIT Plan shall list the applicable and reference documents in support to the generation of the document."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","A.2.1<3>a","Requirement","ECSS-E-ST-10-03_0750391",2,"Normative Change","The AIT Plan shall list the applicable dictionary or glossary and the meaning of specific terms or abbreviations utilized in the document."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","A.2.1<4>a","Requirement","ECSS-E-ST-10-03_0750392",2,"Normative Change","The AIT Plan shall briefly describe the selected models and their built status with reference to the verification plan (see ECSS-E-ST-10-02)."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","A.2.1<5>a","Requirement","ECSS-E-ST-10-03_0750393",2,"Normative Change","The AIT Plan shall document the AIT activities and associated planning."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","A.2.1<5>b","Requirement","ECSS-E-ST-10-03_0750394",2,"Normative Change","The AIT Plan shall include test matrix(ces) that link the various tests with the test specifications, test procedures, test blocks and hardware model."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","A.2.1<5>c","Recommendation","ECSS-E-ST-10-03_0750465",2,"Normative Change","c.\tAssembly, integration and test programmes including inspections, should be detailed through dedicated activity sheets."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","A.2.1<5>d","Requirement","ECSS-E-ST-10-03_0750396",1,"Unchanged","Activity sheets shall include descriptions of the activity including the tools and GSE to be used, the expected duration of the activity, and the relevant safety or operational constraints."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","A.2.1<5>e","Recommendation","ECSS-E-ST-10-03_0750466",2,"Normative Change","e.\tThe sequencing of activities should be presented as flow charts."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","A.2.1<6>a","Requirement","ECSS-E-ST-10-03_0750398",2,"Normative Change","The AIT Plan shall list and describe the GSE, test software and AIT facilities to be used."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","A.2.1<6>b","Requirement","ECSS-E-ST-10-03_0750399",2,"Normative Change","The AIT Plan shall describe the logistics and list the major transportations."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","A.2.1<7>a","Requirement","ECSS-E-ST-10-03_0750400",2,"Normative Change","The AIT Plan shall describe the AIT documents to be produced and their content."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","A.2.1<8>a","Requirement","ECSS-E-ST-10-03_0750401",2,"Normative Change","The AIT Plan shall describe the responsibility and management tools applicable to the described AIT process with reference to ECSS-E-ST-10-02."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","A.2.1<8>b","Requirement","ECSS-E-ST-10-03_0750402",2,"Normative Change","The AIT Plan shall describe the responsibilities within the project team, the relation to product assurance, quality control and configuration control (tasks with respect to AIT) as well as the responsibility sharing with external partners.","NOTE \tTasks with respect to AIT include for example, anomaly handling, change control, safety, and cleanliness.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","A.2.1<8>c","Requirement","ECSS-E-ST-10-03_0750403",1,"Unchanged","The planned reviews and the identified responsibilities shall be stated."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","A.2.1<9>a","Requirement","ECSS-E-ST-10-03_0750404",2,"Normative Change","The AIT Plan shall provide the AIT schedule as reference."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","B.2.1<1>a","Requirement","ECSS-E-ST-10-03_0750405",1,"Unchanged","The TSPE shall contain a description of the purpose, objective, content and the reason prompting its preparation."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","B.2.1<1>b","Requirement","ECSS-E-ST-10-03_0750406",1,"Unchanged","Any open issue, assumption and constraint relevant to this document shall be stated and described."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","B.2.1<2>a","Requirement","ECSS-E-ST-10-03_0750407",1,"Unchanged","The TSPE shall list the applicable and reference documents in support to the generation of the document."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","B.2.1<3>a","Requirement","ECSS-E-ST-10-03_0750408",1,"Unchanged","The TSPE shall list the applicable dictionary or glossary and the meaning of specific terms or abbreviations utilized in the document."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","B.2.1<4>a","Requirement","ECSS-E-ST-10-03_0750409",1,"Unchanged","The TSPE shall list the requirements to be verified (extracted from the VCD) in the specific test and provides traceability where in the test the requirement is covered."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","B.2.1<5>a","Requirement","ECSS-E-ST-10-03_0750410",1,"Unchanged","The TSPE shall summarize the approach to the test activity and the associated requirements as well as the prerequisites to start the test."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","B.2.1<6>a","Requirement","ECSS-E-ST-10-03_0750411",1,"Unchanged","The TSPE shall summarize the configuration of the item under test, the test set-up, the necessary GSE, the test tools, the test conditions and the applicable constraints."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","B.2.1<7>a","Requirement","ECSS-E-ST-10-03_0750412",2,"Normative Change","The TSPE shall describe the applicable test facility requirements together with the instrumentation and measurement uncertainties, data acquisition and test space segment equipment to be used."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","B.2.1<8>a","Requirement","ECSS-E-ST-10-03_0750413",1,"Unchanged","The TSPE shall describe the test activity flow and the associated requirements."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","B.2.1<8>b","Requirement","ECSS-E-ST-10-03_0750414",1,"Unchanged","When constraints are identified on activities sequence, the TSPE shall specify them including necessary timely information between test steps."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","B.2.1<9>a","Requirement","ECSS-E-ST-10-03_0750415",2,"Normative Change","The TSPE shall list the test pass/fail criteria in relation to the inputs and output."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","B.2.1<9>b","Requirement","ECSS-E-ST-10-03_0750416",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","B.2.1<10>a","Requirement","ECSS-E-ST-10-03_0750417",1,"Unchanged","The TSPE shall list the requirements for the involved documentation, including test procedure, test report and PA and QA records."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","B.2.1<11>a","Requirement","ECSS-E-ST-10-03_0750418",1,"Unchanged","The TSPE shall describe the overall test responsibilities, participants to be involved and the schedule outline.","NOTE \tParticipation list is often limited to organisation and not individual name.\n"]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","C.2.1<1>a","Requirement","ECSS-E-ST-10-03_0750419",1,"Unchanged","The TPRO shall contain a description of the purpose, objective, content and the reason prompting its preparation."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","C.2.1<1>b","Requirement","ECSS-E-ST-10-03_0750420",1,"Unchanged","Any open issue, assumption and constraint relevant to this document shall be stated and described."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","C.2.1<2>a","Requirement","ECSS-E-ST-10-03_0750421",1,"Unchanged","The TPRO shall list the applicable and reference documents in support to the generation of the document."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","C.2.1<3>a","Requirement","ECSS-E-ST-10-03_0750422",1,"Unchanged","The TPRO shall list the applicable dictionary or glossary and the meaning of specific terms or abbreviations utilized in the document."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","C.2.1<4>a","Requirement","ECSS-E-ST-10-03_0750423",1,"Unchanged","The TPRO shall provide a mapping matrix to the TSPE giving traceability towards the test requirement."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","C.2.1<5>a","Requirement","ECSS-E-ST-10-03_0750424",1,"Unchanged","The TPRO shall describe the item under test configuration, including any reference to the relevant test configuration list, and any deviation from the specified standard."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","C.2.1<5>b","Requirement","ECSS-E-ST-10-03_0750425",1,"Unchanged","The software version of the item under test shall be identified."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","C.2.1<6>a","Requirement","ECSS-E-ST-10-03_0750426",1,"Unchanged","The TPRO shall describe the test set-up to be used."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","C.2.1<7>a","Requirement","ECSS-E-ST-10-03_0750427",1,"Unchanged","The TPRO shall identify the GSE and test tools to be used in the test activity including test script(s), test software and database(s) versioning number."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","C.2.1<8>a","Requirement","ECSS-E-ST-10-03_0750428",2,"Normative Change","The TPRO shall identify the test instrumentation, with measurement uncertainties, to be used, including fixtures."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","C.2.1<9>a","Requirement","ECSS-E-ST-10-03_0750429",1,"Unchanged","The TPRO shall identify the applicable test facility and any data handling system."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","C.2.1<10>a","Requirement","ECSS-E-ST-10-03_0750430",1,"Unchanged","The TPRO shall list the applicable standards, the applicable test conditions, in terms of levels, duration and tolerances, and the test data acquisition and reduction."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","C.2.1<11>a","Requirement","ECSS-E-ST-10-03_0750431",1,"Unchanged","The TPRO shall describe how the applicable documentation is used to support the test activity."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","C.2.1<12>a","Requirement","ECSS-E-ST-10-03_0750432",1,"Unchanged","The TPRO shall list the allocation of responsibilities and resources."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","C.2.1<13>a","Requirement","ECSS-E-ST-10-03_0750433",1,"Unchanged","The TPRO shall identify special, safety and hazard conditions, operational constraints, rules for test management relating to changes in procedure, failures, reporting and signing off procedure."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","C.2.1<13>b","Requirement","ECSS-E-ST-10-03_0750434",1,"Unchanged","The TPRO shall describe QA and PA aspects applicable to the test."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","C.2.1<13>c","Requirement","ECSS-E-ST-10-03_0750435",2,"Normative Change","The TPRO shall contain a placeholder for identifying:\n1.\tprocedure variations, together with justification, and\n2.\tanomalies."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","C.2.1<14>a","Requirement","ECSS-E-ST-10-03_0750436",1,"Unchanged","The TPRO shall provide detailed instructions, including expected results, with tolerances, pass/fail criteria, and identification of specific steps to be witnessed by QA personnel."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","C.2.1<14>b","Permission","ECSS-E-ST-10-03_0750467",2,"Normative Change","b.\tThe step-by-step instructions may be organized in specific tables."]
["ECSS-E-ST-10-03C Rev.1","ECSS - Current v1.0","C.2.1<14>c","Requirement","ECSS-E-ST-10-03_0750438",1,"Unchanged","When the procedure is automated, the listing of the automated procedure shall be documented to a level allowing consistency check with the TPRO and the TPSE."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","4.2.1a","Requirement","ECSS-E-ST-10-04_0760001",1,"Unchanged","Gravity effects shall be included in all orbit determination and orbit prediction processes, and in attitude determination and prediction processes for Earth and planetary orbiters."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","4.2.1b","Requirement","ECSS-E-ST-10-04_0760002",2,"Normative Change","The inclusion of different gravity sources, their associated model details, and corresponding model truncation errors shall be compliant with the requirements on orbit and/or attitude determination accuracy, and be at least of the same perturbation order as considered perturbing accelerations due to non-gravitational effects. "]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","4.2.1c","Requirement","ECSS-E-ST-10-04_0760003",1,"Informative Change","The retained accuracy level of a gravity model shall be compliant with the accuracy of the position and orientation of the central body.","NOTE \tHarmonic coefficients can lead to resonance effects, if they have a degree or order close to some integer multiple of the ground track repeat cycle. For orbits that are known to be repetitive, it is then recommendable to include discrete resonant harmonics of degrees that normally fall outside the truncated expansion series.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","4.2.2a","Requirement","ECSS-E-ST-10-04_0760004",2,"Normative Change","For Earth orbits a gravity model shall be applied that fulfills the following: \n1.\tThe model is a global and static model\n2.\tThe model is based on Grace or GOCE data\n3.\tThe model is published at: \t\nhttp://icgem.gfz-potsdam.de/tom_longtime\n4.\tThe model is described by spherical harmonic coefficients up to at least degree and order of 70.","NOTE\t1\tFor example the EIGEN-GLO4C model [RN.1] fulfills given requirements. It has a spatial resolution in latitude and longitude of 1° ´ 1° (corresponding to degree ´ order = 360 ´ 360).\nNOTE\t2\tFor other planetary environments no standard gravity model exists. Some information for Jupiter is provided in [RD.148].\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","4.2.2b","Requirement","ECSS-E-ST-10-04_0760005",1,"Unchanged","Data on gravitational effects from tides and on Earth orientation parameters shall be obtained from the International Earth Rotation Service IERS given in [RN.2]."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","4.2.2c","Requirement","ECSS-E-ST-10-04_0760006",2,"Normative Change","For third body gravitational perturbations the Development Ephemerides data on planets (DE-430) and the Lunar Ephemerides data (LE-430), both given in [RN.3], shall be used."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","4.2.2d","Requirement","ECSS-E-ST-10-04_0760007",2,"Normative Change","For planetary mass values the 2010 standards of the International Earth Rotation Services IERS, as described in IERS Technical Note 36 [RN.2], shall be used."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","5.2.1a","Requirement","ECSS-E-ST-10-04_0760008",2,"Normative Change","IGRF-12 [RN.29] shall be used as the Internal Geomagnetic Field Model.","NOTE \tAs a stand-alone model, the inputs required of the IGRF-12 are either position in geodetic coordinates, according to the reference ‘World Geodetic Service 84’ standard ellipsoid, or position in a geocentric system, with respect to the centre of the Earth and for which the reference Earth radius is 6 371,2 km. The coordinates are therefore geodetic or geocentric latitude in decimal degrees, longitude (same in both coordinate systems), altitude in km above the reference ellipsoid, or distance in km from the centre of the Earth. Time is input in decimal years, e.g. 2 007,5. It is recommended that geocentric data are used, to avoid errors or confusion in respect of the reference ellipsoid. \n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","5.2.1b","Requirement","ECSS-E-ST-10-04_0760009",1,"Informative Change","If a different model is an inherent part of a specific space environment model, then that specific geomagnetic field model shall be used. ","NOTE \tAn example is the AE8 and AP8 radiation flux / belt models (see Clause 9)\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","5.2.1.1a","Requirement","ECSS-E-ST-10-04_0760010",2,"Normative Change","For times in the past and in the future, IGRF-12 shall be used, in association with its secular variations.","NOTE\t1\tIGRF-12 and future versions contain revisions of models of earlier epochs.\nNOTE\t2\tBeyond 5 years from the assumed epoch (2015), the precision of the model is considerably reduced. IGRF-13 is expected to be issued for the epoch 2020, and can be used post 2019.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","5.2.2a","Requirement","ECSS-E-ST-10-04_0760011",2,"Informative Change","For modelling the average characteristics of the terrestrial magnetic field and its variation according to geomagnetic and solar activity, one of the following two external magnetic field models shall be used:\n1.\tAlexeev et al 2001, [RN.30] \n2.\tTsyganenko 1996 [RN.31] ","NOTE\t1\tThese models are suitable for assessment of the mean and range of magnetic field strength; for estimation of B and L coordinates (but not for input to radiation belt models created with different field models); and in calculation of geomagnetic shielding of cosmic rays and solar particles.\nNOTE\t2\tRecently, external field models have been created (e.g. Tsyganenko 2001 [RD.98], 2004 [RD.99]) that are used in research environments for dynamic modelling of field variations, e.g. substorm development. These have the capacity to represent more accurately the instantaneous magnetic field, but are not given here as standards because the definition of inputs to the models is not reasonably achievable in an engineering environment.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","5.3a","Recommendation","ECSS-E-ST-10-04_0760128",2,"Normative Change","While the IGRF-12 model should normally be used for internal fields, a low­fidelity dipole model, using aligned, eccentric or tilted dipoles as appropriate, can be sufficient for some engineering applications."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","5.3b","Permission","ECSS-E-ST-10-04_0760129",1,"Informative Change","For the external field, the recent Tsyganenko 2001 [RD.98] and 2004 [RD.99] models may be used instead of the reference models defined in clause 5.2.2.","NOTE \tMost engineering applications do not need the external­source model augmentation of these later Tsyganenko models. These are only useful for certain scientific magnetospheric missions, for instance if data on high latitude or high altitude variability of the fields with respect to local time and solar­geomagnetic activity was important. \n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","6.2.1a","Requirement","ECSS-E-ST-10-04_0760014",1,"Unchanged","The values in Table 6-2 shall be used for the electromagnetic radiation. "]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","6.2.1b","Requirement","ECSS-E-ST-10-04_0760015",2,"Normative Change","The solar spectrum shall be approximated by a black body curve with a characteristic temperature of 5 778 K. "]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","6.2.1c","Requirement","ECSS-E-ST-10-04_0760016",1,"Unchanged","A space sink temperature of 3 K shall be used."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","6.2.2a","Requirement","ECSS-E-ST-10-04_0760017",1,"Informative Change","For daily and 81-day averaged values of F10.7, S10.7 and M10.7 the values given in Table A-1 shall be used.","NOTE\t1\tAp is only weakly correlated with the solar activity indices. It has a seasonal variation and is higher at the equinoxes.\nNOTE\t2\t81 days corresponds to 3 solar rotations and 81 day averaged values are used as input for atmosphere models.\nNOTE\t3\tAlternative daily and 81-day average values and forecast methods are available [ISO 27852:2016]. Their values can be more appropriate depending on the use-case.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","6.2.2b","Requirement","ECSS-E-ST-10-04_0760018",1,"Unchanged","For fixed index values, the numbers given in Table 6-3 for low, moderate and high solar and geomagnetic activities shall be used: \n1.\tThe long­term values are averaged values for periods longer than 27 days.\n2.\tThe long-term values apply as well for periods of 1 week or longer.\n3.\tThe short-term values are daily values. "]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","6.2.2c","Requirement","ECSS-E-ST-10-04_0760019",1,"Unchanged","The temporal evolution in ap shown in Table 6-4 shall be used to describe the worst case fluctuations during successive three-hour intervals for a total duration of 24 hours. "]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","6.2.2d","Requirement","ECSS-E-ST-10-04_0760020",1,"Unchanged","The ap values of Table 6-4 shall be used together with the relevant (low, moderate or high) long term averaged values of F10.7, S10.7 and M10.7 given in Table 6-3."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","6.2.3a","Permission","ECSS-E-ST-10-04_0760021",2,"Normative Change","For design purposes the “worst-case” activity values given in Table 6-3 may be used. ","NOTE \tThese can be the high or low values, depending on the effect to be studied. \n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","6.2.3b","Requirement","ECSS-E-ST-10-04_0760022",1,"Unchanged","All worst-case values shall be used without any additional margin."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","6.2.3c","Requirement","ECSS-E-ST-10-04_0760023",2,"Normative Change","The values given in Table A-1 shall be used:\n1.\tfor applications that require a realistic sequence of index values for future predictions, for example orbital calculations using index-driven atmospheric models; \n2.\tfor a given specific phase of the respective solar activity cycle."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","6.2.3d","Requirement","ECSS-E-ST-10-04_0760024",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","7.2.1.1a","Requirement","ECSS-E-ST-10-04_0760025",2,"Normative Change","The NRLMSISE-00 model [RN.4] shall be used for calculating the neutral temperature, the total density and the detailed composition of the atmosphere."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","7.2.1.1b","Permission","ECSS-E-ST-10-04_0760026",2,"Normative Change","The JB-2006 model [RN.5] or JB-2008 model [RN.39] may be used for calculating the total atmospheric density above an altitude of 120 km."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","7.2.1.1c","Requirement","ECSS-E-ST-10-04_0760027",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","7.2.1.2a","Requirement","ECSS-E-ST-10-04_0760028",1,"Unchanged","The NRLMSISE-00 model for species densities shall not be mixed with the JB-2006 model for total density."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","7.2.1.2b","Requirement","ECSS-E-ST-10-04_0760029",1,"Unchanged","For worst case high results and analysis periods not exceeding 1 week high daily short-term values given in Table 6-3 shall be used as input for daily activity together with the high long-term values for the 81-day average activity. "]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","7.2.1.2c","Requirement","ECSS-E-ST-10-04_0760030",1,"Unchanged","For analysis periods longer than 1 week the long term activities given in Table 6-3 shall be used as input for both, the daily and the 81-day averaged values."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","7.2.1.2d","Requirement","ECSS-E-ST-10-04_0760031",1,"Unchanged","For analysis periods longer than 1 week and conditions specified in 6.2.3c, the daily and 81-day averaged solar activities given in Table A-1 shall be used."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","7.2.1.2e","Requirement","ECSS-E-ST-10-04_0760032",1,"Informative Change","Short-term daily high solar activity values shall not be used together with low or moderate long-term solar activity values.","NOTE\t1\tBoth models can only predict large scale and slow variations, on the order of 1 000 km (given by the highest harmonic component) and 3 hours. Spacecraft can encounter density variations with smaller temporal and spatial scales partly since they are in motion (for example, +100% or -50% in 30 s), and partly because smaller-scale disturbances certainly occur during periods of disturbed geomagnetic activity.\nNOTE\t2\tReference values for the key indices needed as inputs for the atmosphere models are given in Clause 6. \nNOTE\t3\tThe F10.7 81-day average activity can also be estimated by averaging three successive monthly predicted values. \nNOTE\t4\tInformation on density model uncertainties can be found in G.5 and in [RN.4] and [RN.5].\nNOTE\t5\tFor high activities the atmosphere models only give realistic results if high short term values are combined with high 81-day averaged values.\nNOTE\t6\tHigh Ap values can be used with low, moderate or high solar activities.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","7.2.2a","Requirement","ECSS-E-ST-10-04_0760033",2,"Normative Change","The HWM07 model [RN.40] shall be used."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","7.2.2b","Requirement","ECSS-E-ST-10-04_0760034",2,"Normative Change","High daily short-term values shall be used as worst-case for the daily activity but the 81-day average activity not exceeding the high long-term value. ","NOTE\t1\tReference values for the key Indices needed as inputs for the wind model are given in Clause 6.\nNOTE\t2\tThe F10.7 81-day average activity can also be estimated by averaging three successive monthly predicted values as given in Clause 6.\nNOTE\t3\tThe use of the HWM93 model at high geomagnetic latitudes and for disturbed geomagnetic periods necessitates caution.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","7.2.2c","Permission","ECSS-E-ST-10-04_0760131",1,"Created","As an alternative to the model specified in 7.2.2a, the HWM93 model [RN.6] may be used."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","7.2.3a","Requirement","ECSS-E-ST-10-04_0760035",2,"Normative Change","For the Martian Atmosphere, the Martian Climate Database [RN.7] shall be used.","NOTE\t1\tNo specific models are imposed for the other planets and their satellites.\nNOTE\t2\tInternational Reference Atmospheres have been adopted for Mars (MIRA) and Venus (VIRA). There have also been major advances in the case of the atmospheres of Jupiter, Saturn, Neptune and Titan. This is a matter of ongoing work. Considerable work has also been performed for the atmosphere of Mercury. \nNOTE\t3\tAdditional information on Planetary Atmospheres is provided in Annex G.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","8.2.1a","Requirement","ECSS-E-ST-10-04_0760036",2,"Normative Change","Applicable plasma regions that can be encountered shall be identified according to the spacecraft location or orbit as follows:\n1.\tThe ionosphere for altitudes between 60 km and 2 000 km.\n2.\tThe auroral charging environment for orbital inclinations above 50 degrees for altitudes above 80 km and below 2 000 km.\n3.\tThe plasmasphere for altitudes above 2 000 km (approximately L=1,3 at the equator) and below L=7. \n4.\tThe outer magnetosphere for all L values above L=3 and within the magnetopause as defined in clause 5, (including the geostationary regime). \n5.\tThe magnetosheath for locations outside of the magnetopause as defined in clause 5 and within the bow shock.\n6.\tThe solar wind for locations outside of the magnetopause and bow shock.\n7.\tThe magnetotail and distant magnetosheath for locations within the bow shock but more than 30 RE from the Earth in the anti-Sunward direction.\n8.\tPlanetary plasma environments for regions within the planetary bow shock, or planetary magnetopause, or planetary ionopause, whichever of these are present.","NOTE\t1\tSee Annex E.5 for definition of L (L-shell).\nNOTE\t2\tSome typical orbits and regions encountered are described in Annex H\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","8.2.1b","Requirement","ECSS-E-ST-10-04_0760037",1,"Unchanged","Applicable environments for each region shall be characterised according to the models specified in 8.2.2 to 8.2.6."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","8.2.2a","Requirement","ECSS-E-ST-10-04_0760038",2,"Normative Change","For the ionospheric environment, the International Reference Ionosphere 2016 (IRI-2016) [RN.9], shall be used. "]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","8.2.2b","Requirement","ECSS-E-ST-10-04_0760039",2,"Normative Change","Inputs to the IRI-2016 model, shall be: \n1.\tchoice of geographic or geomagnetic coordinates; \n2.\tlatitude; \n3.\tlongitude; \n4.\tdate; \n5.\tlocal or universal time; \n6.\taltitude (start and end of range and step size)."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","8.2.2c","Requirement","ECSS-E-ST-10-04_0760040",2,"Normative Change","Other inputs shall be the default solar and geomagnetic index values for dates up to 2018 or later periods if available from www.irimodel.org. ","NOTE \tThis means that Sunspot number Rz12, IG12 (see 6.1.2.3.2), F10.7 and ap data are taken from default files. \n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","8.2.2d","Requirement","ECSS-E-ST-10-04_0760041",2,"Normative Change","For future dates not covered by the default files, for F10.7 and ap the activity indices defined in clause 6 and corresponding values for IG12 and Rz12 shall be used. ","NOTE \tInformation on the accuracy of the IRI-2016 model and typical ionospheric density profiles are given in Annex H.3.1\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","8.2.3a","Requirement","ECSS-E-ST-10-04_0760042",2,"Normative Change","For auroral charging assessment, the following worst­case electron distribution function shall be used.\n1.\tFor E £17,44 keV: \n \n2.\tFor E > 17,44:\n \nwhere\nf(v)\tis the distribution function in sec3 m-6\nN0\tis the density in m-3 \nme\tis the electron mass in kg\nkT0\tis the thermal energy in J \nE0\tis in J \nE \tis energy in J\nand parameters of the worst case environment are:\nN0\t= 1,13E6 m-3\nkT0\t= 3,96 keV\nE0\t= 17,44 keV","NOTE \tThis comes from [RD.7] and is based on work described in [RD.8]. Unfortunately, it is printed in [RD.7] with a typographical error.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","8.2.3b","Requirement","ECSS-E-ST-10-04_0760043",1,"Informative Change","For worst case auroral charging assessments, a thermal ion density of 125 cm-3 and temperature 0,2 eV shall be used. ","NOTE \tThis low ion density comes from a severe charging case seen on the DMSP spacecraft by [RD.9]. Measuring ionospheric thermal ion density during a strong charging event is potentially prone to errors because of the way the charged satellite alters ion trajectories, so there is a high degree of uncertainty in this measurement but there is currently no better information.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","8.2.3c","Permission","ECSS-E-ST-10-04_0760132",1,"Created","A Maxwellian fit to the auroral electron distribution specified in 8.2.3a may be used with temperature 11 keV and density 1.1e7 m-3 [RD.167]."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","8.2.3d","Requirement","ECSS-E-ST-10-04_0760133",1,"Created","The worst case environments specified in 8.2.3a, 8.2.3b and 8.2.3c shall be applied for 10s."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","8.2.4a","Recommendation","ECSS-E-ST-10-04_0760044",2,"Normative Change","The plasma parameters representing the terrestrial plasmasphere should be taken from the Global Core Plasma Model (GCPM) [RN.8], version 2.4. ","NOTE\t1\tProfiles of typical plasmasphere densities versus altitude are given in Annex H.3.3. \nNOTE\t2\tOutputs are densities of electrons, protons, helium ions and oxygen ions. Input parameters are: time, geocentric radial distance, solar magnetic local time, solar magnetic latitude and Kp index.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","8.2.4b","Requirement","ECSS-E-ST-10-04_0760045",2,"Normative Change","For spacecraft charging assessments, Kp=9 shall be used to represent a worst case situation.","NOTE \tThis is because the plasmasphere is a moderating influence on spacecraft charging, and so the worst case is considered to be when the plasmasphere is small which occurs when geomagnetic activity is high.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","8.2.4c","Permission","ECSS-E-ST-10-04_0760134",1,"Created","As an alternative to the model specified in 8.2.4a, the IRI-Plas model may be used [RD.166]."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","8.2.5a","Requirement","ECSS-E-ST-10-04_0760046",1,"Informative Change","For assessment of surface charging, the worst­case environment listed in Table 8-1 shall be used as input to a spacecraft charging simulation or calculation, applicable to the outer magnetosphere environment. ","NOTE\t1\tThis is a dynamic region in terms of plasma density and temperature and for most engineering purposes, worst­case environments are the most important consideration. See Annex H.3.4 for typical plasma parameters in this region. \nNOTE\t2\tSee Annex H.3.4 for some other worst-case environments.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","8.2.6a","Requirement","ECSS-E-ST-10-04_0760047",1,"Unchanged","For calculation of engineering effects due to the solar wind, a flowing Maxwellian distribution shall be used, with density and temperature given in Table 8-2."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","8.2.6b","Requirement","ECSS-E-ST-10-04_0760048",1,"Informative Change","Spacecraft in L1 and L2 shall be considered to experience the same mean and range of plasma parameters in the solar wind as at the Earth.","NOTE \tBecause the solar wind flows through the near-Earth interplanetary medium with negligible modification (unless it encounters the bow shock), the mean and range of plasma density and temperature can be considered spatially uniform in the vicinity of 1AU. However, variations in plasma at the Earth are seen at L1 and L2 between approximately 30 and 90 minutes earlier or later, respectively.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","8.2.6c","Requirement","ECSS-E-ST-10-04_0760049",1,"Unchanged","A r-2 variation shall be used to map the mean and range of solar wind density to other locations in the heliosphere in the ecliptic plane, where r is heliocentric distance. "]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","8.2.6d","Requirement","ECSS-E-ST-10-04_0760050",1,"Unchanged","A r-0,64 variation shall be used to map the mean and range of the electron temperature to other locations in the heliosphere in the ecliptic plane."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","8.2.6e","Requirement","ECSS-E-ST-10-04_0760051",1,"Unchanged","The ion temperature and composition shall be assumed to be the same as near the Earth."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.1.1a","Requirement","ECSS-E-ST-10-04_0760052",1,"Informative Change","For Earth orbits other than those addressed in 9.2.1.2, the standard models of the radiation belt energetic particle fluxes shall be the AE-8 and AP-8 models for electrons [RN.10] and protons [RN.11].","NOTE\tThese models are based on long term dataset averages and are most appropriate for long term cumulative effects on missions of more than 6 months duration. Statistical variation and uncertainties can be significant and are presented in Annex I.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.1.1b","Requirement","ECSS-E-ST-10-04_0760053",1,"Unchanged","They shall be used together with the geomagnetic field models shown in Table 9-1. "]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.1.1c","Requirement","ECSS-E-ST-10-04_0760054",1,"Unchanged","The version of the model, i.e. solar maximum/minimum that is commensurate with the solar activity levels (MIN or MAX), of the mission phase shall be used. "]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.1.1d","Requirement","ECSS-E-ST-10-04_0760055",2,"Normative Change","The dates of Minima and Maxima that shall be used for solar cycles 1 to 24 and the algorithm for forecasting future Minima and Maxima are presented in Annex B.1 and Table B-2.","NOTE\tAs it is difficult to define the % of solar MIN and MAX to apply for missions not scheduled in Max or Min periods, a more conservative analysis can be obtained for all periods using AE8MAX for electron fluxes and AP8MIN for proton fluxes.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.1.1e","Requirement","ECSS-E-ST-10-04_0760056",1,"Informative Change","For analysis of the South Atlantic Anomaly (SAA), the drift of the SAA due to geomagnetic field evolution shall be included. ","NOTE \tThe translation of the orbit locations eastward in longitude 0,3° per year since 1960 prior to accessing the models provides a first approximation to this drift. [RD.14].\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.1.2.1a","Requirement","ECSS-E-ST-10-04_0760057",2,"Normative Change","For electron fluxes at altitudes within 500 km of geostationary orbits (35 786 km) the standard model for Earth radiation belt energetic electrons shall be the IGE-2006 average model.","NOTE \tIGE-2006 model was previously called POLE [RN.12] and Annex B.2.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.1.2.1b","Requirement","ECSS-E-ST-10-04_0760058",2,"Normative Change","For conservative analysis, the IGE-2006 upper case model shall be used.","NOTE \tInformation on model development and uncertainties can be found in [RN.33].\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.1.2.1c","Requirement","ECSS-E-ST-10-04_0760059",1,"Unchanged","The mission duration parameter used with the IGE2006 model shall be rounded up to the nearest integral year."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.1.2.1d","Requirement","ECSS-E-ST-10-04_0760060",1,"Unchanged","For trapped proton fluxes in geostationary orbit, the trapped proton models (AP-8) specified in 9.2.1.1 shall be used."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.1.2.2a","Requirement","ECSS-E-ST-10-04_0760061",2,"Normative Change","For electron fluxes in GPS orbits (circular, 20 200 km ± 500 km altitude; 55° Inclination) the standard model for Earth radiation belt energetic electrons shall be the ONERA MEOv2 average model (Annex B.3, [RN.13])."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.1.2.2b","Requirement","ECSS-E-ST-10-04_0760062",1,"Unchanged","For conservative analysis, the upper case MEOv2 model shall be used."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.1.2.2c","Requirement","ECSS-E-ST-10-04_0760063",1,"Unchanged","The mission duration parameter used with the MEOv2 model shall be rounded up to the nearest integral year."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.1.2.2d","Requirement","ECSS-E-ST-10-04_0760064",1,"Unchanged","Extrapolation of the flux spectrum from the MEOv2 model to higher energies shall use the orbit averaged spectral form provided by AE-8 MAX."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.1.2.2e","Requirement","ECSS-E-ST-10-04_0760065",1,"Unchanged","For trapped proton fluxes, the trapped proton models (AP-8) specified in 9.2.1.1 shall be used."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.1.2.2f","Permission","ECSS-E-ST-10-04_0760130",2,"Normative Change","For trapped electron fluxes at altitudes between 20 500 km and 24 000 km and the Inclination range of 55° ± 5°, either the AE-8 or the MEOv2 model may be used.","NOTE \tIf used above 20 500 km altitude the MEOv2 model can provide conservative results. More information on this model is given in Annex I.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.1.3a","Requirement","ECSS-E-ST-10-04_0760067",2,"Normative Change","For Earth orbits, except the one in 9.2.1.3c, the FLUMIC V3 model [RN.14] (Annex B.4) shall be used. ","NOTE\t1\tThese electron belt models are also appropriate for short-term (from 1 day to 1 month) worst-case cumulative radiation effect analyses.\nNOTE\t2\tFor a conservative assessment with FLUMIC V3, 21 March 2005 corresponding to 0.219 ‘fraction of year’ and 0.802 ‘fraction of solar cycle’ can be assumed.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.1.3b","Permission","ECSS-E-ST-10-04_0760135",1,"Created","For geostationary orbits, the NASA worst case model (Annex B.5) may be used."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.1.3c","Requirement","ECSS-E-ST-10-04_0760136",1,"Created","For GNSS orbits, the MOBE-DIC model (Annex B.10) shall be used."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.1.3d","Requirement","ECSS-E-ST-10-04_0760137",1,"Created","The highest flux reported by the models during the mission shall be used."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.2.1a","Requirement","ECSS-E-ST-10-04_0760068",1,"Informative Change","Fluxes and fluences of solar energetic particles shall be assumed to be isotropic.","NOTE \tAnisotropic distributions do exist in near-Earth space due to geomagnetic shielding (see clause 9.2.4) and in the early stages of a SPE, where particles arrive along interplanetary field lines. The direction of the interplanetary magnetic field can be variable and not along the Earth-Sun direction. An isotropic distribution is assumed due to a lack of knowledge for specific events.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.2.2a","Requirement","ECSS-E-ST-10-04_0760069",2,"Normative Change","Proton fluence spectra from Solar Particle Events integrated over mission durations (of 1 year or more) shall be derived using the ESP model [RN.15] described in Annex B.6."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.2.2b","Requirement","ECSS-E-ST-10-04_0760070",1,"Informative Change","For mission durations shorter than 1 year, the fluences for one year shall be used [RN.15].","NOTE \tFor mission durations shorter than 1 year, this results in a conservative fluence estimate.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.2.2c","Requirement","ECSS-E-ST-10-04_0760071",1,"Unchanged","When using the model to calculate fluences for mission durations longer than 1 solar cycle (11 years), the model shall be used with the total number of years of high solar activity during the mission."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.2.2d","Requirement","ECSS-E-ST-10-04_0760072",1,"Informative Change","For interplanetary missions, the results of the solar particle models shall be scaled by a factor calculated as the mean value over the mission of: r-2 for r<1AU [RN.16] and 1 for r>1AU, where r is in units of AU. ","NOTE \tBeyond 1 AU using a factor of 1 corresponds to a conservative estimate of the maximum coefficient recommended in [RN.16].\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.2.2e","Requirement","ECSS-E-ST-10-04_0760138",1,"Created","For calculations of geomagnetic shielding all ions shall be treated based on CREME96 ionization states."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.2.2f","Requirement","ECSS-E-ST-10-04_0760139",1,"Created","If CREME96 specified in 9.2.2.2e does not provide ionization states the ions shall be treated as half ionised."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.2.2g","Permission","ECSS-E-ST-10-04_0760140",1,"Created","Electron fluence from Solar Particle Events (SPEs) integrated over mission durations, of 6 months or more, may be derived using the IEM model [RD.150].","NOTE \tThis is considered only relevant for applications such as sensitive instrument background on interplanetary missions. The fluxes and energies provide a negligible contribution to cumulative effects compared to solar protons or trapped particle fluxes.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.2.3a","Requirement","ECSS-E-ST-10-04_0760073",2,"Normative Change","For solar particle fluxes (protons and other ions), either the CREME96 model [RN.18] (only available online) or Table B-10, Table B-11, and Table B-12 shall be used."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.2.3b","Requirement","ECSS-E-ST-10-04_0760074",2,"Normative Change","In Table B-10, Table B-11, and Table B-12 all ions shall be treated as fully ionised for geomagnetic shielding calculations.","NOTE \tIn cases where the instantaneous solar proton flux is required or as a function of time during an event, there are several large events that have been measured, their spectral fits are provided in Annex I.2.4.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.2.3c","Permission","ECSS-E-ST-10-04_0760141",1,"Created","For maximum SPE electron fluences, the IEM model [RD.150] may be used.","NOTE \tThis is considered only relevant for applications such as sensitive instrument background on interplanetary missions. The fluxes and energies provide a negligible contribution to cumulative effects compared to solar protons or trapped particle fluxes.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.3a","Requirement","ECSS-E-ST-10-04_0760075",2,"Normative Change","The ISO 15390:2004 Model [RN.19] of galactic cosmic rays shall be used for GCR flux calculations. ","NOTE \tAlthough cosmic ray fluxes increase gradually with heliocentric distance, it is a reasonable engineering approximation for current missions to assume uniformity throughout the heliosphere. \n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.4a","Requirement","ECSS-E-ST-10-04_0760076",2,"Normative Change","The minimum energies, i.e. cut-off energies, necessary for ions to penetrate to a geographic location shall be calculated with one of the following methods:\n1.\tStørmer’s theory [RN.20]\n2.\tMAGNETOCOSMICS [RN.21]\n3.\tThe method given by Smart and Shea in [RN.22]\n4.\tStassinopoulos & King: no geomagnetic shielding for McIlwain L-shells greater than 5 RE [RN.23]\n5.\tNo geomagnetic shielding for a conservative estimate."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.5a","Permission","ECSS-E-ST-10-04_0760142",1,"Created","To assess the atmospheric albedo neutron fluxes the models given in Annex I.7 may be used."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.6a","Requirement","ECSS-E-ST-10-04_0760077",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.6b","Requirement","ECSS-E-ST-10-04_0760078",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.7a","Requirement","ECSS-E-ST-10-04_0760143",1,"Created","The interplanetary environment shall apply for the energetic particle environment at L2 and the deep tail."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.2.7b","Recommendation","ECSS-E-ST-10-04_0760144",1,"Created","For specific cases, as X-ray optics and detectors, the population of medium energy charged particles should be evaluated. ","NOTE \tFurther information is provided in Annex I.7.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.3a","Requirement","ECSS-E-ST-10-04_0760079",1,"Unchanged","A specification of the expected radiation environment of a space system shall be established. "]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.3b","Requirement","ECSS-E-ST-10-04_0760080",2,"Informative Change","The specification of a mission environment shall include:\n1.\tMission­average proton and electron energy spectra from trapped radiation issued from the chosen models (according to mission orbit and time). \n2.\tThe fluence spectrum of solar protons for the complete mission with geomagnetic shielding applied.\n3.\tMaximum instantaneous energy spectra of trapped electrons, trapped protons and solar energetic protons (geomagnetically shielded) for the mission, for internal charging and sensor interference analysis.\n4.\tThe ion LET flux spectrum derived from the GCR flux spectra for the appropriate solar cycle phase, together with the worst 5 minute solar energetic particle LET spectrum, including:\n(a)\tContributions from all ions from Z = 1 to Z = 92. \n(b)\tGeomagnetic shielding. \n(c)\tMaterial shielding. If no justification is available for another value, 1 g cm-2 of aluminium shielding is used.\n5.\tThe ion LET fluence spectrum derived from the GCR fluence spectra for the appropriate solar cycle phase, together with the fluence spectra from a number of events at worst day CREME96 solar energetic particle LET spectrum, including:\n(a)\tContributions from all ions from Z = 1 to Z = 92. \n(b)\tGeomagnetic shielding. \n(c)\tMaterial shielding. If no justification is available for another value, 1 g cm-2 of aluminium shielding is used.\n6.\tOrbital time­behaviour of radiation­belt (if any), cosmic ray and solar energetic particle fluxes if the mission has a susceptibility to radiation background in sensors.\n7.\tAdditional contributions from on­board nuclear/radioactive sources.\n8.\tUncertainties of the radiation models as applied for the given mission."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.3c","Requirement","ECSS-E-ST-10-04_0760081",1,"Informative Change","The uncertainties in results from the models shall be included in the risk assessment."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.3d","Requirement","ECSS-E-ST-10-04_0760082",1,"Informative Change","The specification shall include the evolution of the mission orbit whether caused naturally or by deliberate orbit manoeuvres.","NOTE \tThis can have significant effects on radiation­belt exposure (e.g. due to natural perigee rise and apogee fall). \n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","9.3e","Requirement","ECSS-E-ST-10-04_0760083",1,"Informative Change","The effects of operations that result in geo­synchronization of the orbit shall be included in the assessment ","NOTE\t1\tFor example: geostationary, apogee longitude maintenance of near­synchronous HEO orbits. \nNOTE\t2\tIn such missions radiation belt exposures are not averaged out.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.1a","Requirement","ECSS-E-ST-10-04_0760084",2,"Normative Change","Impact risk assessments shall be performed for space debris and meteoroid populations."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.1b","Requirement","ECSS-E-ST-10-04_0760085",2,"Normative Change","The statistical flux models specified in 10.2.2 shall be used tailored for the specific mission parameters. "]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.1c","Requirement","ECSS-E-ST-10-04_0760086",1,"Unchanged","The directional and velocity distributions of the space debris and meteoroid fluxes shall be included in the impact risk assessment."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.2.1a","Requirement","ECSS-E-ST-10-04_0760087",2,"Normative Change","The space debris part of the MASTER-8 model [RN.26] shall be used for Earth orbits with perigee altitudes below 36 786 km. "]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.2.1b","Requirement","ECSS-E-ST-10-04_0760088",1,"Unchanged","The model shall be used for all mission durations. "]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.2.1c","Requirement","ECSS-E-ST-10-04_0760089",2,"Normative Change","The model shall be used for particle diameters from 1 µm to 100 m."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.2.1d","Requirement","ECSS-E-ST-10-04_0760090",2,"Normative Change","For conversion between mass and diameter the following shall be used:\n1.\tAn average density of 2,8 g cm-3.\n2.\tA spherical shape.","NOTE \tThe density of 2,8 g cm-3 represents the average density of space debris objects > 1mm. Additional information is given in Annex J.2.2.1.4.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.2.1e","Permission","ECSS-E-ST-10-04_0760145",1,"Created","Densities and shapes different from ones specified in requirement 10.2.2.1d may be included in specific cases."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.2.1f","Requirement","ECSS-E-ST-10-04_0760146",1,"Created","The MASTER-8 flux model [RN.26] shall be used together with the following input parameters: \n1.\tTimeframes between 1957 and 2066.\n2.\tThe size interval given in terms of diameter.\n3.\tCondensed population, with all sources included.\n4.\tThe model intrinsic future prediction.","NOTE\t1\tAccess points for the ESA MASTER-8 model and its patches are defined in Annex J.2.2.1, together with model characteristics, uncertainties, some general aspects and other space debris flux models.\nNOTE\t2\tTabulated reference values are provided in Annex J.5.\nNOTE\t3\tDue to the dynamic nature of the debris environment significant and abrupt increases of populations can occur.  \nNOTE\t4\tThe condensed population files combine all individual populations. This results in a reduced file size on the file system and saves computation time. Individual population files are still an option in MASTER-8 but are recommended to be used for special cases only.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.2.1g","Permission","ECSS-E-ST-10-04_0760147",1,"Created","Later versions of MASTER-8 or population files may be applied","NOTE \tFor details how to obtain later verisons, see Annex J.2.2.1.2.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.2.1h","Permission","ECSS-E-ST-10-04_0760148",1,"Created","For specific missions, the debris flux implemented in ORDEM 3.0 [RN.36] may be used for Earth altitudes below 40 000 km."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.2.1i","Requirement","ECSS-E-ST-10-04_0760149",1,"Created","For ORDEM 3.0 debris model the following shall be used:\n1.\tTime range from 2010 to 2035\n2.\tNominal flux (zero sigma)\n3.\tthe density model implemented in ORDEM 3.0\n4.\tparticle diameters  of 10 micron to over 1 m for altitudes below 34 000 km \n5.\tparticle diameters of 10 cm to over 1 m for altitudes from 34 000 to 40 000 km."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.2.1j","Permission","ECSS-E-ST-10-04_0760150",1,"Created","For Earth altitudes not covered by 10.2.2.1a or 10.2.2.1h space debris flux may be neglected."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.2.2a","Requirement","ECSS-E-ST-10-04_0760091",2,"Normative Change","The Grün model [RD.22] shall be used to determine near-Earth meteoroid environments. ","NOTE\t1\tIt gives the total average meteoroid flux (sporadic + stream average) in terms of the integral flux Fmet,0 as:\n \n\twhere\n\tFmet,0 \tis the unshielded isotropic interplanetary flux at 1 AU distance from the Sun. It gives the number of particles with mass m or larger per m2 per year impacting a single-sided randomly­tumbling flat plate. \n\tand\n\t \n\t \n\t \n\twith m in g\nNOTE\t2\tThe near-Earth environment includes Earth and Lunar orbits and the Lagrange points of the Sun-Earth and Earth-Moon systems.\nNOTE\t3\tTabulated reference values are provided in Table J-5.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.2.2b","Requirement","ECSS-E-ST-10-04_0760092",2,"Normative Change","The models specified in 10.2.2.2a and 10.2.2.2h shall be used for all mission durations. "]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.2.2c","Requirement","ECSS-E-ST-10-04_0760093",1,"Unchanged","For missions of less than 3 weeks duration the flux from the meteoroid stream model specified in 10.2.4.5 shall be added for the given mission period. "]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.2.2d","Requirement","ECSS-E-ST-10-04_0760094",2,"Normative Change","For conversion between mass and diameter and for impact damage assessments the following shall be used:\n1.\tA density of 2,5 g cm-3 for the Grün model and 1,0 g cm-3 for the MEMR2 model.\n2.\tA spherical shape."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.2.2e","Requirement","ECSS-E-ST-10-04_0760151",1,"Created","The meteoroid model given in 10.2.2.2a shall be used together with the normalised velocity distribution of meteoroids at 1 AU [RD.27] given in Table C-1."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.2.2f","Requirement","ECSS-E-ST-10-04_0760152",1,"Created","The velocity distribution in Table C-1 shall be adjusted to reflect the altitude dependence of the meteoroid model given in Annex C according to one of the procedures specified in Annex C.1.5.1.","NOTE \tThe velocity correction which is used to increase the flux with decreasing distance from the Earth is used to adjust the velocity distribution which is then re-binned accordingly.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.2.2g","Requirement","ECSS-E-ST-10-04_0760153",1,"Created","For Earth and Lunar orbits, the unshielded flux Fmet,0 specified in 10.2.2.2a shall be modified to account for the gravitational attraction as specified in Annex C.1.5.2.","NOTE \tThis enhances the meteoroid flux in the Earth proximity.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.2.2h","Permission","ECSS-E-ST-10-04_0760154",1,"Created","For specific missions, the MEM and LunarMEM models or the Divine-Staubach model may be used.","NOTE \tFor interplanetary orbits no reference model is specified. Available interplanetary meteoroid flux models are given in Annex J.2.1.5.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.2.2i","Requirement","ECSS-E-ST-10-04_0760155",1,"Created","The MEMR2 flux model [RN.37] shall be used with the following input parameters:\n1.\tMass range 10-6 - 10 g\n2.\tConstant particle density of 1 g/cm3"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.2.2j","Requirement","ECSS-E-ST-10-04_0760156",1,"Created","For lunar environments the MEMR2 flux model [RN.37] shall be used with the following input parameters:\n1.\tRadius up to 66000 km from the Moon\n2.\tMass range 10-6 - 10 g\n3.\tConstant particle density of 1 g/cm3"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.2.2k","Requirement","ECSS-E-ST-10-04_0760157",1,"Created","The Divine-Staubach model [RD.108] shall be used with following input parameters:\n1.\tMass range 10-12 g to 1 g.\n2.\tInherent velocity distribution model.\n3.\tParticle density equal to:\n(a)\t2,0 g/cm3 for m < 10-6 g\n(b)\t1,0 g/cm3 for 10-6 g < m < 10-2 g\n(c)\t0,5 g/cm3 for 10-2 g < m"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.3a","Requirement","ECSS-E-ST-10-04_0760095",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.4.1a","Requirement","ECSS-E-ST-10-04_0760096",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.4.2a","Requirement","ECSS-E-ST-10-04_0760098",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.4.3a","Requirement","ECSS-E-ST-10-04_0760099",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.4.4a","Requirement","ECSS-E-ST-10-04_0760100",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.4.4b","Requirement","ECSS-E-ST-10-04_0760101",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.4.5a","Requirement","ECSS-E-ST-10-04_0760102",1,"Unchanged","For the calculation of meteoroid stream fluxes, the meteor stream parameters given in Table C-2 shall be used together with the flux calculation procedure given in Annex C.1.4.2 and C.1.4.3."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.4.5b","Requirement","ECSS-E-ST-10-04_0760103",1,"Unchanged","For each meteoroid stream the specific particle velocity shall be considered."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.4.5c","Requirement","ECSS-E-ST-10-04_0760104",1,"Informative Change","For meteoroid stream particles a mass density of 1,0 g cm-3 shall be used.","NOTE \tThis meteoroid stream model is also implemented in MASTER-2005\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.5a","Requirement","ECSS-E-ST-10-04_0760105",2,"Normative Change","For the translation of flux F into number of impacts N, a linear increase of N with exposed area and with exposure time shall be used, as follows:\n \nWhere:\nN \tis the number of impacts;\nF\tis the particulate flux per unit time and unit area;\nA \tis the total exposed area;\nT \tis the exposure time."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.5b","Requirement","ECSS-E-ST-10-04_0760107",1,"Unchanged","Impact risk analyses based on the number of impacts N shall be conducted through the application of Poisson statistics."]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.5c","Requirement","ECSS-E-ST-10-04_0760108",2,"Normative Change","The probability Pn of exactly n impacts occurring in the corresponding time interval shall be determined according to the expression: \n","NOTE \tAdditional information on the conduct of impact risk assessments is provided in Annex [RD.91].\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.5d","Permission","ECSS-E-ST-10-04_0760158",1,"Created","Simplified assessments may be performed with an average velocity and a constant impact angle of 45 degrees from the surface normal.","NOTE \tTypical average impact velocity for space debris in LEO is 10 km/s, 5 km/s for space debris in GEO and of 20 km/s for meteoroids.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","10.2.6a","Requirement","ECSS-E-ST-10-04_0760110",2,"Normative Change","For a nominal assessment of the space debris and meteoroid populations in the near-Earth environment the nominal flux models shall be applied without additional margin or uncertainty factors.","NOTE \tThe flux models given in 10.2.2 and 10.2.3 were developed as best estimates rather than as conservative ones. Information on the model uncertainties is given in Annex J.2.3.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","11.2a","Recommendation","ECSS-E-ST-10-04_0760111",2,"Normative Change","The evaluation of contamination levels on sensitive items should include the interaction with the following space environment components:\n1.\tAtmospheric density at altitudes below 250 km\n2.\tAtomic oxygen at altitudes below 400 km\n3.\tUV radiation\n4.\tEM and particle radiation.","NOTE \tSynergistic effects are indicated in Table 11-1.\n"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","11.2b","Requirement","ECSS-E-ST-10-04_0760112",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","11.2c","Requirement","ECSS-E-ST-10-04_0760113",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-04C Rev.1","ECSS - Current v1.0","11.2d","Requirement","ECSS-E-ST-10-04_0760114",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","7.2.1a","Requirement","ECSS-E-ST-10-06_0770001",1,"Created","Technical requirements shall be formulated as defined in clause 8.\n    ","NOTE The DRD for the TS is shown in Annex A."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","7.2.1b","Requirement","ECSS-E-ST-10-06_0770002",1,"Created","The specification shall be identifiable, referable and related to a product or a system."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","7.2.2a","Requirement","ECSS-E-ST-10-06_0770003",1,"Created","An entity shall be identified to be responsible for the specification."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","7.2.2b","Requirement","ECSS-E-ST-10-06_0770004",1,"Created","The responsible entity of the specification shall define the content and format of the attributes listed in clause 8."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","7.2.3a","Requirement","ECSS-E-ST-10-06_0770005",1,"Created","The technical requirements shall be grouped.\n    ","NOTE Grouping can be either by type or in accordance with the different situations of the product life cycle."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","7.2.3b","Requirement","ECSS-E-ST-10-06_0770006",1,"Created","Each technical requirement shall be separately stated."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","7.2.3c","Requirement","ECSS-E-ST-10-06_0770007",1,"Created","Abbreviated terms used in requirements shall be defined in a dedicated section of the specification."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","7.2.3d","Requirement","ECSS-E-ST-10-06_0770008",1,"Created","The technical requirements shall be consistent (e.g. not in conflict with the other requirements within the specification)."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","7.2.3e","Requirement","ECSS-E-ST-10-06_0770009",1,"Created","The technical requirements shall not be in conflict with the other requirements contained in business agreement documents."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","7.2.4a","Requirement","ECSS-E-ST-10-06_0770010",1,"Created","The specification shall be complete in terms of applicable requirements and reference to applicable documents."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","7.2.4b","Requirement","ECSS-E-ST-10-06_0770011",1,"Created","A technical requirement shall not call for more than one technical requirement in an applicable referred document."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","7.2.4c","Requirement","ECSS-E-ST-10-06_0770012",1,"Created","The link to an applicable document shall be stated in the technical requirements."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","7.2.4d","Requirement","ECSS-E-ST-10-06_0770013",1,"Created","The reference number of the applicable documents cited in the specification shall contain the revision identifier."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","7.2.5a","Requirement","ECSS-E-ST-10-06_0770014",1,"Created","The specification shall be under configuration management."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","7.2.6a","Requirement","ECSS-E-ST-10-06_0770015",1,"Created","The specification shall be established to be readily exchanged according to the established access policy and rights."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","7.2.7a","Requirement","ECSS-E-ST-10-06_0770016",1,"Created","If a clause is stated to be informative or descriptive, then this clause shall not contain any requirement or recommendation."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","7.2.8a","Requirement","ECSS-E-ST-10-06_0770017",1,"Created","Technical requirements specifications shall only include technical requirements and exclude requirements such as cost, methods of payment, quantity required, time or place of delivery."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.2.1a","Requirement","ECSS-E-ST-10-06_0770018",1,"Created","Each technical requirement shall be described in quantifiable terms."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.2.1b","Requirement","ECSS-E-ST-10-06_0770019",1,"Created","If necessary to remove possible ambiguities of a given performance requirement the method used to determine the required performance shall be indicated in the requirement itself."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.2.2a","Recommendation","ECSS-E-ST-10-06_0770055",1,"Created","Each technical requirement should be justified."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.2.2b","Requirement","ECSS-E-ST-10-06_0770021",1,"Created","The entity responsible of the technical requirement shall be identified."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.2.2c","Requirement","ECSS-E-ST-10-06_0770022",1,"Created","The entity responsible of the specification shall define what part of the justification shall be included in the specification as informative material.\n    ","NOTE The justification of every technical requirement, as well as the entity responsible of the technical requirement, can be collected and recorded in a requirement justification file (see ECSS-E-ST-10 Annex O)."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.2.3a","Requirement","ECSS-E-ST-10-06_0770023",1,"Created","Each technical requirement shall be under configuration management."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.2.3b","Requirement","ECSS-E-ST-10-06_0770024",1,"Created","All technical requirements shall be backwards-traceable."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.2.3c","Requirement","ECSS-E-ST-10-06_0770025",1,"Created","All technical requirements shall be forward-traceable.\n    ","NOTE 1 A technical requirement is traceable when it is possible to trace the history, application, or location of a requirement by means of recorded identification.\nNOTE 2 The backward traceability is the process to trace back the source of each requirement to the requirement from which it derives.\nNOTE 3 The forward traceability is the process to establish that each level requirement is implemented at the appropriate phase of the design and that all requirements are implemented."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.2.4a","Requirement","ECSS-E-ST-10-06_0770026",1,"Created","The technical requirements shall be unambiguous."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.2.5a","Requirement","ECSS-E-ST-10-06_0770027",1,"Created","Each technical requirement shall be unique."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.2.6a","Requirement","ECSS-E-ST-10-06_0770028",1,"Created","A technical requirement shall be identified in relation to the relevant function, product or system."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.2.6b","Requirement","ECSS-E-ST-10-06_0770029",1,"Created","A unique identifier shall be assigned to each technical requirement."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.2.6c","Recommendation","ECSS-E-ST-10-06_0770056",1,"Created","The unique identifier should reflect the type of the technical requirement."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.2.6d","Recommendation","ECSS-E-ST-10-06_0770057",1,"Created","The unique identifier should reflect the life profile situation.\n    ","NOTE In general a technical requirement is identified by, for example, a character or a string of characters, a number, or a name tag or hypertext."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.2.7a","Requirement","ECSS-E-ST-10-06_0770032",1,"Created","Each technical requirement shall be separately stated.\n    ","NOTE Technical requirements are single or separately stated when they are not the combination of two or more technical requirements."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.2.8a","Requirement","ECSS-E-ST-10-06_0770033",1,"Created","A technical requirement shall be self-contained.\n    ","NOTE A technical requirement is self-contained when it is complete and does not require additional data or explanation to express the need."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.2.9a","Requirement","ECSS-E-ST-10-06_0770034",1,"Created","A technical requirement shall be verifiable using one or more approved verification methods.\n    ","NOTE A technical requirement is verifiable when the means to evaluate if the proposed solution meets the requirement are known."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.2.9b","Requirement","ECSS-E-ST-10-06_0770035",1,"Created","Verification of technical requirements shall be performed in conformance with ECSS-E-ST-10-02."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.2.10a","Requirement","ECSS-E-ST-10-06_0770036",1,"Created","The tolerance shall be specified for each parameter/variable.\n    ","NOTE The technical requirement tolerance is a range of values within which the conformity to the requirement is accepted."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.3.1a","Recommendation","ECSS-E-ST-10-06_0770058",1,"Created","Technical requirements should be stated in performance or “what-is-necessary” terms, as opposed to telling a supplier “how to” perform a task, unless the exact steps in performance of the task are essential to ensure the proper functioning of the product."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.3.1b","Recommendation","ECSS-E-ST-10-06_0770059",1,"Created","Technical requirements should be expressed in a positive way, as a complete sentence (with a verb and a noun)."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.3.2a","Requirement","ECSS-E-ST-10-06_0770039",1,"Created","The verbal form “shall” shall be used whenever a provision is a requirement."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.3.2b","Requirement","ECSS-E-ST-10-06_0770040",1,"Created","The verbal form “should” shall be used whenever a provision is a recommendation."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.3.2c","Requirement","ECSS-E-ST-10-06_0770041",1,"Created","The verbal form “may” shall be used whenever a provision is a permission."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.3.2d","Requirement","ECSS-E-ST-10-06_0770042",1,"Created","The verbal form “can” shall be used to indicate possibility or capability."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","8.3.3a","Requirement","ECSS-E-ST-10-06_0770043",1,"Created","List of terms that shall not be used in a TS requirement\n    1. “and/or”,\n    2. “etc.”,\n    3. “goal”,\n    4. “shall be included but not limited to”,\n    5. “relevant”,\n    6. “necessary”,\n    7. “appropriate”,\n    8. “as far as possible”,\n    9. “optimize”,\n    10. “minimize”,\n    11. “maximize”,\n    12. “typical”,\n    13. “rapid”,\n    14. “user-friendly”,\n    15. “easy”,\n    16. “sufficient”,\n    17. “enough”,\n    18. “suitable”,\n    19. “satisfactory”,\n    20. “adequate”,\n    21. “quick”,\n    22. “first rate”,\n    23. “best possible”,\n    24. “great”,\n    25. “small”,\n    26. “large”, and\n    27. “state of the art”."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","A.2.1<1>a","Requirement","ECSS-E-ST-10-06_0770044",1,"Created","The TS shall contain a description of the purpose, objective, content and the reason prompting its preparation."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","A.2.1<2>a","Requirement","ECSS-E-ST-10-06_0770045",1,"Created","The TS shall list the applicable and reference documents in support of the generation of the document."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","A.2.1<3>a","Requirement","ECSS-E-ST-10-06_0770046",1,"Created","The TS shall present the main elements that characterize the user’s need for developing the product as a background for those requirements that are defined in detail in the dedicated section."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","A.2.1<3>b","Requirement","ECSS-E-ST-10-06_0770047",1,"Created","The TS shall put the product into perspective with other related products. "]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","A.2.1<3>c","Recommendation","ECSS-E-ST-10-06_0770060",1,"Created","If the product is independent and totally self-contained, i.e. able to match the final user’s need, it should be so stated here. "]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","A.2.1<3>d","Requirement","ECSS-E-ST-10-06_0770049",1,"Created","If the TS defines a product that is a component of a higher tier system, the TS shall recall the related needs of that larger system and shall describe the identified interfaces between that system and the product.\n    ","NOTE A non-exhaustive checklist of general questions that should be answered at the early stages of the TS is: \n        · What is the product supposed to do? It is fundamental but critically important to make sure that every actor has a complete understanding of what the product has to do.\n        · Who is going to use this product? It is important to indicate who is going to use the product, why they are going to use it and for what it is going to be used."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","A.2.1<4>a","Requirement","ECSS-E-ST-10-06_0770050",1,"Created","The technical specification shall describe the concept, the expected product architecture and the functioning principles on which it is based."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","A.2.1<5>a","Requirement","ECSS-E-ST-10-06_0770051",1,"Created","The TS shall list and describe the different chronological situations of the product’s life profile. \n    ","NOTE 1 For a spacecraft, the life profile includes:\n        · AIT related life events\n        · transportation to launching area;\n        · conditioning and tests;\n        · installation on launcher;\n        · pre-launch phase;\n        · launching phase;\n        · self transfer to its operating position;\n        · in-orbit functioning;\n        · end-of-life (e.g. de-orbitation).\nNOTE 2 An identifier can be associated with each situation in order to be able to link each requirement to at least one situation in which it applies. Such an approach enables sorting and filtering of the requirements per situation."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","A.2.1<6>a","Requirement","ECSS-E-ST-10-06_0770052",1,"Created","The TS shall describe the different environments and constraints for each situation in the life profile that the product is expected to encounter.\n    ","NOTE An identifier can be associated with each product environment in order to be able to link each requirement to at least the worst environment to which it applies. Such an approach enables sorting and filtering the requirements per environment."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","A.2.1<7>a","Requirement","ECSS-E-ST-10-06_0770053",1,"Created","The TS shall list all the technical requirements necessary for the product to satisfy the user’s needs.\n    ","NOTE Interfaces requirements can be rolled-out of the TS in form an interface requirement document (IRD), see ECSS-E-ST-10 Annex M."]
["ECSS-E-ST-10-06C","ECSS - Current v1.0","A.2.1<7>b","Requirement","ECSS-E-ST-10-06_0770054",1,"Created","The technical requirements shall be expressed according to ECSS-E-ST-10-06 clauses 7 and 8. \n    ","NOTE For instance, for all TS and for each requirement, the following characteristics have been selected:\n        · identifiability;\n        · performance and methods used to determine it;\n        · configuration management;\n        · traceability;\n        · tolerance\n        · verification"]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.2.1a","Requirement","ECSS-E-ST-10-09_0230001",1,"Created","The responsibility for the task of system-level definition of the coordinate systems and their inter-relationships, applicable to the whole product tree and to be used throughout the lifetime a project, shall be identified.\n    ","NOTE 1 See ECSS-M-ST-10, subclause 4.3.4 and 5.3 and Annex B of this document for product tree. See also ECSS-S-ST-00-01 for the definition of product tree.\nNOTE 2 The product tree includes the space segment, the launcher, the ground segment and associated processors, the user segment, operations, and the engineering tools and models such as simulators, emulators and test benches."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.2.2a","Requirement","ECSS-E-ST-10-09_0230002",1,"Created","The Coordinate Systems Document (CSD) shall be produced in conformance with Annex A.\n    ","NOTE The CSD is intended for reviews."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.2.2b","Requirement","ECSS-E-ST-10-09_0230003",1,"Created","The CSD shall identify the specified coordinate systems and time scales used throughout the project, by two or more subsystems or organisations, together with their inter-relationships (in a parametric form).\n    ","NOTE Subsystems (or organisations) are free to make specifications within their area of responsibility, so long as the specific (internal) coordinate system or time scale is not used by another subsystem (or organisation)."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.2.2c","Requirement","ECSS-E-ST-10-09_0230004",1,"Created","For a spacecraft project, a preliminary version of the CSD shall be produced before the end of phase A."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.2.2d","Requirement","ECSS-E-ST-10-09_0230005",1,"Created","The CSD (and related database) shall be put under configuration control at the beginning of phase B."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.2.2e","Requirement","ECSS-E-ST-10-09_0230006",1,"Created","At each phase of the project, the coordinate systems and their inter-relationships shall be re-examined."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.2.2f","Requirement","ECSS-E-ST-10-09_0230007",1,"Created","The CSD shall include the new coordinate systems and transformations following the progress of the project development.\n    ","NOTE During the project, new details and elements are defined (e.g. equipment, methods and algorithms)."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.2.3a","Requirement","ECSS-E-ST-10-09_0230008",1,"Created","The elements, which need coordinate systems, shall be identified.\n    ","NOTE This involves iterative analysis of the functional and product trees as well as the interfaces, at each phase. "]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.2.3b","Requirement","ECSS-E-ST-10-09_0230009",1,"Created","Each identified element of the system shall have its coordinate systems defined."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.2.3c","Requirement","ECSS-E-ST-10-09_0230010",1,"Created","A transformation chain structure shall be built to link coordinate systems used by two or more subsystems \n    ","NOTE See Annex B for guidelines and examples."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.2.3d","Requirement","ECSS-E-ST-10-09_0230011",1,"Created","The nominal value, in numeric or parametric form, of the transformation between two coordinate systems shall be specified."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.3.1a","Requirement","ECSS-E-ST-10-09_0230012",1,"Created","Applicable parts of the international standards and conventions listed in Annex C shall be selected and specified in the CSD.\n    ","NOTE Such organisations maintain, for example, definitions of certain reference coordinate systems, and of time. "]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.3.1b","Requirement","ECSS-E-ST-10-09_0230013",1,"Created","Applicable non compliant external conventions shall be converted into the project’s convention."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.3.1c","Requirement","ECSS-E-ST-10-09_0230014",1,"Created","The conversion of 5.3.1b shall be specified."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.3.2a","Requirement","ECSS-E-ST-10-09_0230015",1,"Created","A coordinate system shall be identified by a unique descriptive name."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.3.2b","Recommendation","ECSS-E-ST-10-09_0230093",1,"Created","Recognised international names should not be used if the exact definition is not followed.\n    ","NOTE E.g. the name “Pseudo True of Date” can be used if the conventional definition of ToD is not strictly followed."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.3.2c","Requirement","ECSS-E-ST-10-09_0230017",1,"Created","A unique mnemonic shall be derived from the descriptive name of the coordinate system."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.3.2d","Requirement","ECSS-E-ST-10-09_0230018",1,"Created","The transformation from one coordinate system to another shall be identified by a unique name, which also indicates the direction of the transformation."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.3.2e","Requirement","ECSS-E-ST-10-09_0230019",1,"Created","The convention for naming coordinate systems and transformations shall be specified."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.3.2f","Requirement","ECSS-E-ST-10-09_0230020",1,"Created","The notation convention shall be specified."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.3.2g","Requirement","ECSS-E-ST-10-09_0230021",1,"Created","Sign conventions shall be identified and defined.\n    ","NOTE E.g. rotation around an axis."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.3.3a","Requirement","ECSS-E-ST-10-09_0230022",1,"Created","A figure shall show the relationship of a coordinate system with equipment, spacecraft or mission."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.3.3b","Requirement","ECSS-E-ST-10-09_0230023",1,"Created","The origin and axes of a coordinate frame shall be identified in figures using the reference mnemonic as indicated in 5.3.2c."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.3.3c","Recommendation","ECSS-E-ST-10-09_0230094",1,"Created","A figure should show the relationship of a coordinate system to at least one other already defined coordinate system, once the first has been defined."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.3.3d","Recommendation","ECSS-E-ST-10-09_0230095",1,"Created","If two or more rotations are used in a transformation between coordinate systems, they should be indicated on the figure with intermediate rotation axes."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.3.3e","Requirement","ECSS-E-ST-10-09_0230026",1,"Created","Symbols used within illustrations, figures and supporting diagrams shall be defined."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.3.3f","Requirement","ECSS-E-ST-10-09_0230027",1,"Created","In an engineering drawing, the applicable projection system shall be indicated.\n    ","NOTE The projection system is generally European or American."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.3.3g","Requirement","ECSS-E-ST-10-09_0230028",1,"Created","In a 3D figure, the axes above, within and below a plane shall be differentiated.\n    ","NOTE 1 An axis pointing out of the plane of the paper can be depicted by a circle with a dot in it; an axis pointing into the paper by a circle with a cross.\nNOTE 2 Shadowing and dotted lines can be used in 3D figures."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.1a","Requirement","ECSS-E-ST-10-09_0230029",1,"Created","The origin of the frame shall be specified."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.1b","Requirement","ECSS-E-ST-10-09_0230030",1,"Created","The derivation of the origin of a frame from reference points shall be defined."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.1c","Requirement","ECSS-E-ST-10-09_0230031",1,"Created","The derivation of the axes of a frame from reference directions shall be defined."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.1d","Requirement","ECSS-E-ST-10-09_0230032",1,"Created","The axes of a frame shall be orthogonal."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.1e","Requirement","ECSS-E-ST-10-09_0230033",1,"Created","The orientation of the axes of a frame shall be defined according to the right hand rule.\n    ","NOTE 1 Sometimes left handed frames cannot be avoided, because of imported off-the-shelf equipment. \nNOTE 2 E.g. raw measurements or actuator commands may be given in a left handed frame."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.1f","Requirement","ECSS-E-ST-10-09_0230034",1,"Created","Any imported left handed frame shall be specified."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.1g","Requirement","ECSS-E-ST-10-09_0230035",1,"Created","Any left handed frame shall be associated with a system reference right handed frame with the related transformation, for project development use.\n    ","NOTE This avoids a “change of sign” in the software without a change of variable."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.1h","Requirement","ECSS-E-ST-10-09_0230036",1,"Created","The epoch of an inertial frame shall be defined."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.2a","Requirement","ECSS-E-ST-10-09_0230037",1,"Created","If a coordinate system is time dependent, then its time scale shall be defined."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.2b","Requirement","ECSS-E-ST-10-09_0230038",1,"Created","The position of a point shall be definable by a set of coordinates with respect to a selected frame."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.3a","Requirement","ECSS-E-ST-10-09_0230039",1,"Created","Dimensionless quantities shall be explicitly denoted as such."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.3b","Requirement","ECSS-E-ST-10-09_0230040",1,"Created","The units or physical dimensions of all non-dimensionless parameters, including angles, shall be defined.\n    ","NOTE E.g. Units for angles include radians and degrees."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.4a","Requirement","ECSS-E-ST-10-09_0230041",1,"Created","The unit of time shall be defined."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.4b","Requirement","ECSS-E-ST-10-09_0230042",1,"Created","The relationship between all time scales used shall be defined.\n    ","NOTE E.g. The relationship between local clocks on a group of spacecraft and UTC on Earth."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.5a","Requirement","ECSS-E-ST-10-09_0230043",1,"Created","The frame for a mechanical system shall be related to its material structure definition."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.5b","Requirement","ECSS-E-ST-10-09_0230044",1,"Created","For alignment, integration and test purposes, the origin and axes of the coordinate systems shall be defined using physical and accessible points, including marks and targets."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.5c","Requirement","ECSS-E-ST-10-09_0230045",1,"Created","The process of constructing the origin and axes of a mechanical reference frame using the physical points shall be specified."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.5d","Requirement","ECSS-E-ST-10-09_0230046",1,"Created","The mathematical relationship between the coordinate system and physical points, as used in 5.4.5c above, shall be defined."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.5e","Requirement","ECSS-E-ST-10-09_0230047",1,"Created","The spacecraft interface frame w.r.t. its launcher adapter shall be specified.\n    ","NOTE 1 This frame often coincides with the spacecraft mechanical reference frame.\nNOTE 2 The spacecraft mechanical reference frame, defined in the CSD, can be replicated in the MICD."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.5f","Recommendation","ECSS-E-ST-10-09_0230096",1,"Created","The mechanical reference frames for the spacecraft, adapter and launch vehicle should be parallel and have the same positive direction.\n    ","NOTE This is sometimes not possible because clocking the satellite inside the launcher can impose an angle around the vertical axis of the launcher."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.6a","Requirement","ECSS-E-ST-10-09_0230049",1,"Created","The specification of geodetic/planetocentric coordinates shall include the parameters of the ellipsoid used, direction and origin of longitude, and definition of the North Pole."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.7a","Requirement","ECSS-E-ST-10-09_0230050",1,"Created","Any parameterisaton of a position or direction vector shall be specified mathematically."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.7b","Requirement","ECSS-E-ST-10-09_0230051",1,"Created","Permitted parameterisations of a coordinate system shall be specified in the CSD."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.8a","Requirement","ECSS-E-ST-10-09_0230052",1,"Created","A transformation between coordinate systems shall be decomposed into a translational transformation and a rotational transformation, in a given order."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.8b","Requirement","ECSS-E-ST-10-09_0230053",1,"Created","The order of decomposition of a transformation between coordinate systems shall be the same throughout a project."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.8c","Requirement","ECSS-E-ST-10-09_0230054",1,"Created","If rotation is composed of three elementary rotations, the order of rotations shall be specified."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.8d","Recommendation","ECSS-E-ST-10-09_0230097",1,"Created","Positive angles about an axis should be defined in a right handed sense."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.8e","Requirement","ECSS-E-ST-10-09_0230056",1,"Created","Any left handed rotation convention shall be highlighted in the CSD."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.8f","Requirement","ECSS-E-ST-10-09_0230057",1,"Created","An elementary rotation shall be defined by a rotation axis and an angle."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.8g","Requirement","ECSS-E-ST-10-09_0230058",1,"Created","If the rotation is represented by a quaternion, the order and mathematical definition of the quaternion parameters shall be specified in the CSD.\n    ","NOTE E.g. possibilities for the parameter order and the scalar part of a quaternion representation include:\n\t1. [q0, q1, q2, q3], with q0 = cos(F/2)\n\t2. [q1, q2, q3, q4], with q1 = cos(F/2)\n\t3. [q1, q2, q3, q4], with q4 = cos(F/2)"]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.8h","Requirement","ECSS-E-ST-10-09_0230059",1,"Created","The rotation error quaternion shall be expressed with a positive scalar part.\n    ","NOTE This constrains the rotation angle to  ."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.8i","Requirement","ECSS-E-ST-10-09_0230060",1,"Created","Any parameterisation of a rotation shall be specified as a matrix in terms of the parameters."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.8j","Requirement","ECSS-E-ST-10-09_0230061",1,"Created","If the rotation is represented by a 3x3 matrix, each matrix element shall be defined."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.9a","Requirement","ECSS-E-ST-10-09_0230062",1,"Created","A transformation between coordinate systems shall be defined in the parent coordinate system in three ways: verbally, mathematically and graphically.\n    ","NOTE E.g. see Table B-1 and Table B-2 in Annex B."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.9b","Requirement","ECSS-E-ST-10-09_0230063",1,"Created","Any simplification of a transformation shall be specified, as well as its assumptions and validity."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.9c","Requirement","ECSS-E-ST-10-09_0230064",1,"Created","The mathematical expression of the transformation between coordinate systems shall define the vector used for the translation, the method used for the rotation, and the order of the transformation."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.9d","Requirement","ECSS-E-ST-10-09_0230065",1,"Created","The rows and columns of a transformation matrix shall be identified."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.9e","Requirement","ECSS-E-ST-10-09_0230066",1,"Created","The transformation between coordinate systems shall be defined by a mathematical expression relating the coordinates of a point in one frame with its coordinates in the other frame."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.9f","Requirement","ECSS-E-ST-10-09_0230067",1,"Created","The numerical values of the elements of a rotation matrix shall be consistent with the precision required by the users of the data."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.9g","Requirement","ECSS-E-ST-10-09_0230068",1,"Created","Any alternative representation of a rotation between coordinate systems shall be specified in its matrix representation.\n    ","NOTE 1 Typical ways to represent a rotation include direction cosine matrix, elementary Euler rotations and quaternions.\nNOTE 2 Quaternion multiplication is sometimes preferred to matrix multiplication, when combining rotations in software calculations.\nNOTE 3 The uncertainty of transformed quantities is not the transformation of the uncertainties. See [3] for pointing errors and [4] for measurement errors."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.9h","Requirement","ECSS-E-ST-10-09_0230069",1,"Created","The time dependency of a transformation between coordinate systems shall be defined.\n    ","NOTE The transformation from ICRS to a spacecraft CoM coordinate frame can entail relativistic models."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","5.4.9i","Requirement","ECSS-E-ST-10-09_0230070",1,"Created","For time dependent transformations the method of interpolation shall be specified.\n    ","NOTE E.g. Inter-sample value of a quaternion."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","A.2.1<1>a","Requirement","ECSS-E-ST-10-09_0230071",1,"Created","The CSD shall describe the purpose, objective and the reason prompting its preparation (e.g. programme, project and phase)."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","A.2.1<2>a","Requirement","ECSS-E-ST-10-09_0230072",1,"Created","The CSD shall list the applicable and reference documents supporting the generation of the document."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","A.2.1<3>a","Requirement","ECSS-E-ST-10-09_0230073",1,"Created","The CSD shall specify the international conventions used within the project for coordinate systems and transformations."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","A.2.1<3>b","Requirement","ECSS-E-ST-10-09_0230074",1,"Created","The CSD shall define the naming, notation and acronym rules for coordinate systems, as well as for transformations."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","A.2.1<3>c","Requirement","ECSS-E-ST-10-09_0230075",1,"Created","The CSD shall define notation conventions for the transfer of coordinates and transformation data."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","A.2.1<4>a","Requirement","ECSS-E-ST-10-09_0230076",1,"Created","The CSD shall specify the units pertaining to the coordinate systems and parameterisations used within the project."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","A.2.1<5>a","Requirement","ECSS-E-ST-10-09_0230077",1,"Created","The CSD shall specify the time standards used within the project and shall specify the relationship between them."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","A.2.1<6>a","Requirement","ECSS-E-ST-10-09_0230078",1,"Created","The CSD shall present the overview of the various coordinate systems. "]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","A.2.1<6>b","Requirement","ECSS-E-ST-10-09_0230079",1,"Created","The overview shall contain a brief description of at least the following coordinate systems, if applicable:\n    1. Inertial Coordinate Systems\n    2. Orbital Coordinate Systems\n    3. Launcher Coordinate Systems\n    4. Satellite-fixed Coordinate System (generic platform and payload)\n    5. Body-fixed Rotation (planet) Coordinate Systems \n    6. Topocentric Coordinate Systems \n    7. Test facility Coordinate Systems\n    8. Simulator Coordinate Systems\n    9. Processing / Product Coordinate Systems"]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","A.2.1<6>c","Requirement","ECSS-E-ST-10-09_0230080",1,"Created","The description shall refer to the theory and conventions applied in between the various coordinate systems (e.g. precession, nutation, polar motion)."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","A.2.1<7>a","Requirement","ECSS-E-ST-10-09_0230081",1,"Created","The CSD shall describe all parameterisations used within a coordinate system (e.g. azimuth, elevation), including the applicable type of coordinate systems where this parameterisation is allowed."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","A.2.1<7>b","Requirement","ECSS-E-ST-10-09_0230082",1,"Created","The CSD shall describe all parameterisations used within a transformation (e.g. quaternions, Euler angles), including the applicable type of coordinate systems where this parameterisation is allowed."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","A.2.1<8>a","Requirement","ECSS-E-ST-10-09_0230083",1,"Created","The CSD shall describe in a graphical representation the top-level chain of transformations for the project."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","A.2.1<8>b","Requirement","ECSS-E-ST-10-09_0230084",1,"Created","The diagram of <8a> shall include any additional constraints between coordinate systems, as well as measurements."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","A.2.1<8>c","Requirement","ECSS-E-ST-10-09_0230085",1,"Created","The CSD shall describe in a graphical representation the lower level chains of transformations. "]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","A.2.1<8>d","Requirement","ECSS-E-ST-10-09_0230086",1,"Created","Each individual coordinate system, identified in <9> below, shall be graphically represented. "]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","A.2.1<8>e","Requirement","ECSS-E-ST-10-09_0230087",1,"Created","These diagrams shall contain any additional constraints between coordinate systems, as well as measurements."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","A.2.1<9>a","Requirement","ECSS-E-ST-10-09_0230088",1,"Created","The CSD shall give the detailed description of all Coordinate Systems used in the project."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","A.2.1<9>b","Requirement","ECSS-E-ST-10-09_0230089",1,"Created","The transformation between coordinate systems shall be defined in the one that is the parent coordinate system."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","A.2.1<9>c","Requirement","ECSS-E-ST-10-09_0230090",1,"Created","Parameterisations within a coordinate system shall be identified and specified.\n    ","NOTE E.g. right ascension and declination."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","A.2.1<9>d","Requirement","ECSS-E-ST-10-09_0230091",1,"Created","The parameterisation of a transformation shall be identified and specified.\n    ","NOTE E.g. quaternions."]
["ECSS-E-ST-10-09C","ECSS - Current v1.0","A.2.1<9>e","Requirement","ECSS-E-ST-10-09_0230092",1,"Created","Any source document for a coordinate system shall be identified in the CSD."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.2.1.1a","Requirement","ECSS-E-ST-10-11_0780001",1,"Created","The HFE parameters listed in 4.2.1.2 to 4.2.1.6 shall be characterised during design, development and assessment of space projects that includes presence of humans in the loop."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.2.1.2a","Requirement","ECSS-E-ST-10-11_0780002",1,"Created","The following key HFE interrelated parameters shall be characterized in defining a human-machine system:\n    1. Users populations,\n    2. Operations or tasks,\n    3. Organisational environments,\n    4. Physical and psycho-physiological environments."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.2.1.3a","Requirement","ECSS-E-ST-10-11_0780003",1,"Created","A user population for the different roles to be played in the human-machine system shall be defined."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.2.1.3b","Requirement","ECSS-E-ST-10-11_0780004",1,"Created","The characteristics of the intended user population shall be defined in terms of:\n    1. Knowledge,\n    2. Skill,\n    3. Experience,\n    4. Education,\n    5. Psycho-Physical attributes,\n    6. Habits,\n    7. Preference and capabilities (including different nationality etc.), and\n    8. Level of Certification."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.2.1.4a","Requirement","ECSS-E-ST-10-11_0780005",1,"Created","The characteristics of a task of the human-machine system shall be characterised in terms of:\n    1. Objectives,\n    2. Availability of Resources,\n    3. Human functions,\n    4. Type (e.g. in case of tasks: cognitive, physical, automated … e.g. in case of operations: autonomous, maintenance, guided, proximity), \n    5. Complexity (e.g. when fast reaction are needed, multiple users are involved, uncertainties may occur, collaboration with autonomous or semi-autonomous systems), \n    6. Mission or life criticality, and\n    7. Plans and Schedules."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.2.1.5a","Requirement","ECSS-E-ST-10-11_0780006",1,"Created","Organisational environment shall be characterised in establishing the users’ roles within the system."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.2.1.5b","Requirement","ECSS-E-ST-10-11_0780007",1,"Created","The organisational environment shall include:\n    1. users roles,\n    2. crew size and compositions, and\n    3. share of control between users."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.2.1.6a","Requirement","ECSS-E-ST-10-11_0780008",1,"Created","Physical environment shall be characterised in terms of:\n    1. Gravity,\n    2. Illumination, ambient light and colours,\n    3. Radiation (of cosmic origin and manmade sources),\n    4. Contamination (e.g. trace-gasses, microbiological, and particles),\n    5. “Comfort box” (temperature and humidity),\n    6. Air composition, ventilation and pressure,\n    7. Noise,\n    8. Vibration,\n    9. Acceleration,\n    10. Day-Night cycle, and\n    11. Environmental Hazard (e.g. electromagnetic fields, sharp corners)."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.2.1.6b","Requirement","ECSS-E-ST-10-11_0780009",1,"Created","The following space related items that can impact on the psycho-physiological state of the users shall be characterised:\n    1. Habitable volumes and confined environment,\n    2. Privacy and personal items,\n    3. Aesthetics, colours and local “1-g” orientation,\n    4. Mission type and duration,\n    5. Communications capabilities (private medical conferences; family contacts voice, television programs or movies),\n    6. Distance from Earth,\n    7. Autonomy and control policies,\n    8. Safe haven or emergency escape system,\n    9. Food and diet,\n    10. Leisure,\n    11. Crew size and composition,\n    12. Medical and psychological supervision,\n    13. Social monotony,\n    14. Sensory deprivation, and\n    15. Sleep and circadian rhythm."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.2.2a","Requirement","ECSS-E-ST-10-11_0780010",1,"Created","Context of use analysis shall be performed "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.2.2b","Requirement","ECSS-E-ST-10-11_0780011",1,"Created","Existing reports on previous systems and missions (if available) shall be used."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.2.2c","Requirement","ECSS-E-ST-10-11_0780012",1,"Created","The context of use shall be defined in terms of:\n    1. Tasks that the users have to perform,\n    2. Overall goal of the system, and\n    3. Implication on health and safety."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.2.2d","Requirement","ECSS-E-ST-10-11_0780013",1,"Created","The set of potential exceptions and anomalies shall be identified."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.3.1a","Requirement","ECSS-E-ST-10-11_0780014",1,"Created","The HFE practices shall be applied from the beginning of the project in the design of all systems and their related missions, during all system mission phases when human beings are involved."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.3.2a","Requirement","ECSS-E-ST-10-11_0780015",1,"Created","Throughout the project the HFE shall:\n    1. be responsible for establishing and updating of the users’ roles,\n    2. be responsible for the definition, maintenance and verification of system human related requirements,\n    3. support and approve establishing and updating of users manuals, operations nomenclature and procedures,\n    4. support and approve definition, design, development and assessment of the required Crew Systems,\n    5. support and approve definition, design, development and assessment of the required Human Computer Interface software,\n    6. support and approve definition, design, development and assessment of the required Training Materials."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.3.3a","Requirement","ECSS-E-ST-10-11_0780016",1,"Created","The operations nomenclature shall be univocally defined not later than phase B of the program in cooperation with the engineering development and kept under configuration control. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.3.3b","Requirement","ECSS-E-ST-10-11_0780017",1,"Created","Operations nomenclature shall assign operationally relevant terminology to hardware, HMI and database items. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.3.4a","Requirement","ECSS-E-ST-10-11_0780018",1,"Created","The user manual shall provide all the design and operational information for the space segment that is used by the ground segment and the operations team to prepare for and implement mission operations."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.3.4b","Requirement","ECSS-E-ST-10-11_0780019",1,"Created","The user manual shall be developed in parallel with the development of the project; starting from PDR."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.3.4c","Requirement","ECSS-E-ST-10-11_0780020",1,"Created","The user manual shall follow project review cycles, and be kept under configuration control."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.3.4d","Requirement","ECSS-E-ST-10-11_0780021",1,"Created","The user manual shall include the description of all interfaces, operating modes and their constraints, telemetry, resources, and associated procedures for both nominal and contingency operations, and detailed requirements for ground mission-specific processes needed during operations.\n    NOTE This manual forms the basis for many operation products."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.3.4e","Requirement","ECSS-E-ST-10-11_0780022",1,"Created","The user manual shall include the operational schematics. \n    NOTE Operational schematics can be represented by drawings depicting information about the functional design of equipment with respect to power, plumbing, signal flow, location and range of sensors and destination of their measurements, relays, valves, fans, and other operating systems. New formats taking advantage of model based design can be used."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.3.5a","Requirement","ECSS-E-ST-10-11_0780023",1,"Created","The approach for basic, mission specific and incremental or on the job training shall be characterised in the early phases of the program."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.3.5b","Requirement","ECSS-E-ST-10-11_0780024",1,"Created","The system design and development planning process shall establish cooperation between training development and engineering development. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.3.5c","Requirement","ECSS-E-ST-10-11_0780025",1,"Created","The training approach shall be characterised for all users."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.3.5d","Requirement","ECSS-E-ST-10-11_0780026",1,"Created","Training facilities and organisation shall be defined not later than the system design phase of the program.\n    NOTE 1 This to identify and utilise design and development products and by-products that can be useful in the training program. \n    NOTE 2 This according to the users established roles and within the system selected mission."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.3.5e","Requirement","ECSS-E-ST-10-11_0780027",1,"Created","The schedule of the system design and development shall include training models design and development and crew training system development and implementation."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.3.6a","Requirement","ECSS-E-ST-10-11_0780028",1,"Created","Mission phases shall be defined prior to the establishment of the HFE, requirements. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.3.6b","Requirement","ECSS-E-ST-10-11_0780029",1,"Created","Crew and ground personnel roles shall be:\n    1. defined in the feasibility phase, \n    2. their tasks established in the system design phase."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.3.7a","Requirement","ECSS-E-ST-10-11_0780030",1,"Created","HFE requirements related to each mission phase shall be defined in project feasibility phase and kept up to date following the increase of details generated in the development of the project.\n    NOTE For project phases and planning, see ECSS-M-ST-10."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.4.1.2a","Requirement","ECSS-E-ST-10-11_0780031",1,"Created","The adoption of a HCD approach shall be characterised by the implementation and maintenance of the following:\n    1. user and task requirements,\n    2. allocation of functions between users and technology (operation analyses),\n    3. requirements iterations with all stakeholders,\n    4. involvement of users, their representatives, or both, in continuous evaluation of the design solutions, by means of the utilisation of simulations or mock-ups (either physical or virtual), and \n    5. multi-disciplinary design that includes experts of the various human aspects of the design, and subject matter experts."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.4.1.3a","Requirement","ECSS-E-ST-10-11_0780032",1,"Created","The incorporation of the human centred design into the overall project structure shall be initiated during the feasibility phase.\n    NOTE To avoid risk of late and costly redesign or incorrect human integration. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.4.2a","Requirement","ECSS-E-ST-10-11_0780033",1,"Created","A human-centred design process plan that specifies how the human-centred activities fit into the overall system development process shall be prepared in conformance with Annex A and included as part of the overall system engineering plan."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.4.2b","Requirement","ECSS-E-ST-10-11_0780034",1,"Created","During project planning, the capability to interact with and incorporate stakeholder feedback shall be provided."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.4.2c","Requirement","ECSS-E-ST-10-11_0780035",1,"Created","The plan shall include the activity for the identification of complex or critical tasks and related scenarios definition."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.4.3.2a","Requirement","ECSS-E-ST-10-11_0780036",1,"Created","The human-centred design activities shall:\n    1. support and approve the operations activities and perform task analysis,\n    2. specify the user populations and organisational requirements,\n    3. produce design solutions with related rationales that can be evaluated by the stakeholders,\n    4. evaluate designs against operation scenarios and related key HFE requirements,\n    5. iteratively evaluate designs."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.4.3.3a","Requirement","ECSS-E-ST-10-11_0780037",1,"Created","The human activities linked with the operations of the other parts of the system shall be defined. \n    NOTE This activity is called TA. The TA takes into account the context of use."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.4.3.3b","Requirement","ECSS-E-ST-10-11_0780038",1,"Created","To provide for the allocation of functions to the crews the TA shall be developed during phase A when human in the loop is foreseen."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.4.3.3c","Requirement","ECSS-E-ST-10-11_0780039",1,"Created","The TA shall be maintained throughout all project and utilisation phases."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.4.3.4a","Requirement","ECSS-E-ST-10-11_0780040",1,"Created","User populations and organisational requirements shall be specified and fed into the system requirements for the subsequent phases. \n    NOTE These requirements are derived from the specified context of use (preliminary TA)."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.4.3.5a","Requirement","ECSS-E-ST-10-11_0780041",1,"Created","Simulations, models and mock-ups (either physical or virtual) representing design solutions shall be used by the design team to communicate with all stakeholders."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.4.3.5b","Requirement","ECSS-E-ST-10-11_0780042",1,"Created","Design solutions shall be integrated into a representative context of use."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.4.3.5c","Requirement","ECSS-E-ST-10-11_0780043",1,"Created","The fidelity level of the design solution shall be compatible with the assessment objective."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.4.3.5d","Requirement","ECSS-E-ST-10-11_0780044",1,"Created","Constraints imposed by the fidelity level shall be communicated to the evaluators."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.4.3.6a","Requirement","ECSS-E-ST-10-11_0780045",1,"Created","Overall objectives of design evaluations shall be established in accord with the stakeholders."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.4.3.6b","Requirement","ECSS-E-ST-10-11_0780046",1,"Created","User’s evaluation criteria shall be established during phase A."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.4.3.6c","Requirement","ECSS-E-ST-10-11_0780047",1,"Created","Design evaluation, as specified in 4.4.3.6e, shall take place at all stages of the system life cycle.\n    NOTE The objective is to allow each project phase evaluation to be performed with the utilisation of dedicated prototypes of the required fidelity."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.4.3.6d","Requirement","ECSS-E-ST-10-11_0780048",1,"Created","Design evaluations shall be organised into Evaluation Events"]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.4.3.6e","Requirement","ECSS-E-ST-10-11_0780049",1,"Created","An evaluation plan (part of human-centred design process plan) shall contain the following:\n    1. Task goals,\n    2. What part of the system is being evaluated, how and when,\n    3. How the evaluation is performed and the related procedures,\n    4. How to select, prepare, or both, the test operators and test evaluators, and\n    5. How the results are evaluated and documented."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.4.3.6f","Requirement","ECSS-E-ST-10-11_0780050",1,"Created","Evaluation events shall produce an evaluation report to be made available to all stakeholders.\n    NOTE For example crew Station Review."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.4.3.6g","Requirement","ECSS-E-ST-10-11_0780051",1,"Created","Evaluation reports shall reflect the consensus of the group of test operators and test evaluators."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.4.3.6h","Requirement","ECSS-E-ST-10-11_0780052",1,"Created","Evaluations with prototypes (including virtual representation/ modelling) shall be used to guarantee user’s safety and at the same time demonstrate effectiveness and efficiency of the design."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.5.1a","Requirement","ECSS-E-ST-10-11_0780053",1,"Created","The Space System design shall use the anthropometric and biomechanics characteristics of the user population as defined for each part that foresees human involvement.\n    NOTE See also European Committee for standardization CEN: EN 1005-4 “Safety of machinery - Human physical performance - Part 4: Evaluation of working postures and movements in relation to machinery (17 February 2005)."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.5.2a","Requirement","ECSS-E-ST-10-11_0780054",1,"Created","To perform the required anthropometric analyses when only configuration CAD data are available an electronic mannequin shall be used.\n    NOTE For detailed data and characteristics (n. of degrees of freedom), limb dimensions and joints characteristics) of the electronic mannequin refer to Document in Annex E - (this is for both IVA and EVA)."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.5.2b","Requirement","ECSS-E-ST-10-11_0780055",1,"Created","When the electronic mannequin is used for EVA or for IVA activities analysis where a dedicated suit is worn by the crew member, suit limitations to human movements and its encumbrances shall be characterized. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.5.2c","Requirement","ECSS-E-ST-10-11_0780056",1,"Created","The electronic mannequin shall be used during in-flight maintenance procedure development and validation. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.5.3a","Requirement","ECSS-E-ST-10-11_0780057",1,"Created","The Space System design that foresees the presence of the human in the loop shall analyse human physical performances and impacts that can be caused by fatigue or by adverse environmental conditions."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.5.4a","Requirement","ECSS-E-ST-10-11_0780058",1,"Created","The space system design that foresees the presence of the human in the loop shall characterise human cognitive performances and impacts that can be caused by cognitive fatigue, and by adverse environmental conditions or both."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.5.4b","Requirement","ECSS-E-ST-10-11_0780059",1,"Created","Normal daily activity and rest pattern (work/rest cycle) shall be scheduled.\n    NOTE 1 The humans are allowed to adjust the pattern specified in b according to their momentary needs. \n    NOTE 2 The scheduling of sleep is taking into account the: \n        · circadian rhythm disturbances,\n        · uncomfortable sleeping positions (microgravity),\n        · headward redistribution of fluids (e.g. blood), and\n        · space sickness/space adaptation syndrome. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.5.4c","Requirement","ECSS-E-ST-10-11_0780060",1,"Created","During space flights, measures shall be recorded on the sleep, alertness, fatigue, and cognitive performance of each crew member.\n    NOTE For an assessment of these effects on system and crew operations design, see Hancock, P.A. & Desmond, P.A. (ed.) (2001). Stress, Workload and Fatigue. Mahwah, New Jersey, Lawrence Erlbaum Associates."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.6.1a","Requirement","ECSS-E-ST-10-11_0780061",1,"Created","The design of human-machine systems shall conform to the HCD process detailed in clause 4.4."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.6.2a","Requirement","ECSS-E-ST-10-11_0780062",1,"Created","Functional high level human in the loop requirements shall be established for PRR within the system technical specification in conformance with ECSS-E-ST-10-06. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.6.2b","Requirement","ECSS-E-ST-10-11_0780063",1,"Created","Final HFE requirements shall be established for SRR within the final system technical specification in conformance with ECSS-E-ST-10-06.\n    NOTE Instead of developing new requirements, the adoption of existing standards or document is a good practice. The list of standards and other documentation in Annex E can be used as reference."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.6.2c","Requirement","ECSS-E-ST-10-11_0780064",1,"Created","HFE evaluation points, (e.g. Crew Station Reviews), shall be identified and inserted into the project design and development process and linked to the project reviews.\n    NOTE Details about project phases and reviews are provided in ECSS-M-ST-10."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.6.3a","Requirement","ECSS-E-ST-10-11_0780065",1,"Created","The following safety related issues shall be characterised for on-board activities:\n    1. Mechanical Safety,\n    2. Electrical Safety,\n    3. Environmental Safety,\n    4. Operational Safety, and\n    5. Psycho-physiological Safety. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.6.3b","Requirement","ECSS-E-ST-10-11_0780066",1,"Created","Safety shall also characterise all mission related ground activities and possible cumulative effects on the users. \n    NOTE The General processes for hazard and safety analyses and control plans are listed in ECSS-Q-ST-40."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.6.4a","Requirement","ECSS-E-ST-10-11_0780067",1,"Created","To achieve the most effective overall system design, the following factors shall be characterised:\n    1. Anthropometrical characteristics of user population, \n    2. Human capabilities and skill, \n    3. Environment,\n    4. Tasks complexity and constraints and inherent or collateral physical stress that can be generated, and \n    5. Machine capabilities and autonomy level."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.6.4b","Requirement","ECSS-E-ST-10-11_0780068",1,"Created","Human-machine interface design shall provide:\n    1. Visual, audio or tactile cues and information on interface characteristics and task performance,\n    2. Interface customisation, and\n    3. Identification of safety related controls."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.6.5a","Requirement","ECSS-E-ST-10-11_0780069",1,"Created","To create an environment that supports and maintains human health, safety and well-being all relevant functions and resources shall be provided as specified in ECSS-E-ST-34."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.6.5b","Requirement","ECSS-E-ST-10-11_0780070",1,"Created","To create an environment that supports and maintains a positive psycho-sociological attitude of the on-board crew both as an individual and as group specific functions shall be identified according to the mission profile and resources and implemented. \n    NOTE To create an environment able to support human presence on-board it is important to define the habitability and aesthetic requirements according to the mission profile and resources. For social aspects family teleconferences are a good solution."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.6.6a","Requirement","ECSS-E-ST-10-11_0780071",1,"Created","To achieve the most effective overall system design, the following factors shall be characterised:\n    1. Human capabilities and knowledge profiles and boundaries,\n    2. Environment,\n    3. Tasks complexity and constraints and inherent or collateral stress that can be generated, and \n    4. Machine capabilities and autonomy level."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.6.6b","Requirement","ECSS-E-ST-10-11_0780072",1,"Created","The fit between human cognitive abilities and limitations for safety related data and controls shall be characterised.\n    NOTE Traditional aspects of software ergonomics are included in this clause and in clause 4.6.7."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.6.7a","Requirement","ECSS-E-ST-10-11_0780073",1,"Created","The job design shall identify working hours, off-duty hours and rest days."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.6.7b","Requirement","ECSS-E-ST-10-11_0780074",1,"Created","Physical exercise shall be counted as working hours.\n    NOTE 1 It is important that the design and development activities take into consideration the organisational environment aspects.\n    NOTE 2 For example when the design and development concerns a complete Human Space System, the existing organisation’s socio-technical characteristics of the infrastructure (e.g. Launch Facilities, Astronaut Training Centre, Ground Stations etc.) that is going to support the utilisation of the system itself it is important to be taken into consideration."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.2a","Requirement","ECSS-E-ST-10-11_0780075",1,"Created","The habitable pressurised environment design shall include:\n    1. living areas organisation,\n    2. human related equipment arrangement, and\n    3. harmonisation of compartments and crew stations."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.2b","Requirement","ECSS-E-ST-10-11_0780076",1,"Created","Additional items see from 4.7.3 up to 4.7.9 shall be present to complete the various living areas including, traffic flow and translation paths, hatches and doors."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.3a","Requirement","ECSS-E-ST-10-11_0780077",1,"Created","Labels and cues (i.e. location, orientation, identification, logistics and instructions) shall be provided for crewmembers to identify, interpret, follow procedures, or avoid hazards."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.3b","Requirement","ECSS-E-ST-10-11_0780078",1,"Created","Labels and cues shall be provided as memory aids for the user. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.3c","Requirement","ECSS-E-ST-10-11_0780079",1,"Created","The information conveyed by the label and cues shall be univocal and coherent and compliant with operations nomenclature."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.3d","Requirement","ECSS-E-ST-10-11_0780080",1,"Created","Labels and cues shall be provided in all spacecraft areas regardless if crew operations (either nominal or contingency) are performed."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.4a","Requirement","ECSS-E-ST-10-11_0780081",1,"Created","Architecture complements specified in 4.7.4c shall be provided for all elements being part of a mission infrastructure that foresee the presence of human crew either in the pressurised or un-pressurised parts.\n    NOTE Architecture complements functions are provided according to the mission and functions of the human infrastructure."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.4b","Requirement","ECSS-E-ST-10-11_0780082",1,"Created","It shall be demonstrated that the architecture complements include all items needed to complete the internal layout to make it habitable and suited for human utilisation."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.4c","Requirement","ECSS-E-ST-10-11_0780083",1,"Created","The following architecture complements shall be included in the design of a pressurised spacecraft or habitat according to its mission duration and related constraints.\n    1. Mobility Aids: provided to support human movements.\n    2. Panels and Partitions: provided for flexibility in the organisation of the living areas.\n        NOTE For an orbital or habitation environment: to cover all volumes that are not considered primary living areas, to avoid free objects to drift in areas where their recovery by the on-board crew might be difficult.\n    3. Aesthetic complements and different colours schemes.\n    4. Crew restraint: provided for all pressurised and un-pressurised environments to restrain or support the crew member in their activities.\n    5. Mechanical restraint for loose objects: provided to enable the crew member to attach equipments and other loose items for task execution.\n    6. Ambient illumination, provided to support human presence both inside and outside the pressurised areas.\n        NOTE 1 It is important that ambient illumination is in line with the pressurised environment local orientation scheme.\n        NOTE 2 It is important that ambient illumination is designed accordingly with the pressurised area functions.\n    7. Complements for protection of the crew (e.g. radiation, touch temperature, hazardous atmosphere, sharp edges)."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.5a","Requirement","ECSS-E-ST-10-11_0780084",1,"Created","Crew stations shall be identified either inside or outside of a pressurised spacecraft according to its mission objectives, duration and related constraints. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.5b","Requirement","ECSS-E-ST-10-11_0780085",1,"Created","Components and provisions shall be provided for areas defined as crew station according to the mission environments and the function(s) of the crew station itself.\n    NOTE 1 An analysis is the prime tool to show compliance to this requirement.\n    NOTE 2 Typical components of a crew station are the following: \n        · Tools,\n        · Illumination: compatible with the foreseen station activities and the ambient illumination of the area where the station is located,\n        · Crew restrains and mobility aids,\n        · Other fixed and portable restraints, and\n        · Systems for access and/or interaction to information."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.5c","Requirement","ECSS-E-ST-10-11_0780086",1,"Created","Crew station layouts shall use the human body preferred posture according to the mission environment (0-g for on-orbit) as starting posture for operations connected to the station itself. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.5d","Requirement","ECSS-E-ST-10-11_0780087",1,"Created","Crew station layouts shall be designed to take advantage of the human body preferred attitudes and movement capabilities made possible by the specific mission environment."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.5e","Requirement","ECSS-E-ST-10-11_0780088",1,"Created","Environment respecting the requirements for human presence as per 4.2.1.6 shall be provided."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.6a","Requirement","ECSS-E-ST-10-11_0780089",1,"Created","All places where it is foreseen that the crew operates either for nominal or non nominal operations (maintenance) for periods exceeding one hour, or 30 minutes if the related task is recurrent, shall be defined as work station."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.6b","Requirement","ECSS-E-ST-10-11_0780090",1,"Created","Work station shall be either outfitted with equipment (including lights) and tools (including restrains) to support the foreseen crew activities or shall be provided with the necessary restraints and hook points to enable their outfitting."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.6c","Requirement","ECSS-E-ST-10-11_0780091",1,"Created","Analyses shall be performed and included into the design documentation to decide which of the below listed workstation shall be implemented and with which characteristics. \n    1. Element control and communication work station,\n    2. Maintenance and servicing work station,\n    3. Payload work station, and\n    4. Windows work station."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.7a","Requirement","ECSS-E-ST-10-11_0780092",1,"Created","Off duty station shall be implemented in one of the following way:\n    1. outfitted with equipment (including lights) and supports (including restrains) to enable the foreseen crew activities, or\n    2. provided with restraints and hook points to enable their outfitting.\n        NOTE All locations where it is foreseen that the crew operates during their off duty periods for periods exceeding one hour, or 30 minutes if the related task is recurrent, can be defined off duty station."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.7b","Requirement","ECSS-E-ST-10-11_0780093",1,"Created","Analyses shall be performed and included into the design documentation to decide which of the below listed off duty workstations shall be implemented and with which characteristics.\n    1. Crew quarter and crew personal areas,\n    2. Galley/meeting centre,\n    3. Communication/leisure area/facility,\n    4. Body and teeth cleaning facility,\n    5. Toilet,\n    6. Shower,\n    7. Food preparation and storage facility, and\n    8. Washing facility."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.8a","Requirement","ECSS-E-ST-10-11_0780094",1,"Created","The physical exercise facility to maintain crew health and well being shall be classified as a duty station."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.9a","Requirement","ECSS-E-ST-10-11_0780095",1,"Created","It shall be demonstrated that medical facilities and provisions including capability to handle specific illness or injuries shall satisfy the need for the number of crew members, mission duration and related mission constraints. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.9b","Requirement","ECSS-E-ST-10-11_0780096",1,"Created","Analyses shall be performed and included into the design documentation to decide which of the below listed medical facilities and provisions shall be implemented and with which characteristics.\n    1. monitor and control crew health and well being,\n    2. monitor and treat one or more injured crew person,\n    3. monitor, isolate and treat one or more ill crew person,\n    4. quarantine one or more crew person, and\n    5. isolate/handle at least one or more deceased crew person."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.10a","Requirement","ECSS-E-ST-10-11_0780097",1,"Created","When for a manned space infrastructure it is foreseen to use the on-board crew outside the spacecraft either for nominal or not nominal operations an extra vehicular activity (EVA) suit shall be provided for each crew member operating outside the spacecraft."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.10b","Requirement","ECSS-E-ST-10-11_0780098",1,"Created","The limitation and constraint of the EVA suit shall be included in designing the spacecraft and habitat and its mission."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.10c","Requirement","ECSS-E-ST-10-11_0780099",1,"Created","For external operations, the work station and exclusions zones or primary and secondary translation path shall be defined."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.10d","Requirement","ECSS-E-ST-10-11_0780100",1,"Created","For external operations, following items shall be provided: \n    1. Crew and equipment restraints,\n    2. Crew and equipment mobility aids,\n    3. Illumination (both local and ambient), and\n    4. Labels and visual cues."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.10e","Requirement","ECSS-E-ST-10-11_0780101",1,"Created","Equipment, tools, restraints and mobility aids and any other systems that have to interface with the crew members wearing the EVA Suit shall be designed accordingly to their context of use."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.10f","Requirement","ECSS-E-ST-10-11_0780102",1,"Created","EVA Operations shall be defined analysing the impact of:\n    1. EVA suit design, \n    2. physiological constraints as specified in clause 4.5.\n    3. constraints related to airlock design (e.g. depressurization and re-pressurization performances), and\n    4. decompression sickness prevention."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.10g","Requirement","ECSS-E-ST-10-11_0780103",1,"Created","Analyses shall be performed and included into the design documentation to decide which of the below listed components shall be implemented and with which characteristics.\n    1. Tools and Equipment for external activities,\n    2. Airlock,\n    3. EVA Suit maintenance and servicing station,\n    4. Robotic support, and\n    5. Transportation system (Rovers)."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.7.10h","Requirement","ECSS-E-ST-10-11_0780104",1,"Created","When an EVA is supported by a robot, the EVA crew shall have a direct override capability on the robot operations."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.8a","Requirement","ECSS-E-ST-10-11_0780105",1,"Created","Context of use and task analysis shall determine the implementation for a given task. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.8b","Requirement","ECSS-E-ST-10-11_0780106",1,"Created","Informatics applications containing an interface to a user shall be analysed, developed and evaluated as per clauses 4.4 and 4.6.6 above.\n    NOTE Information and requirements concerning software implementation are provided e.g. in ECSS-E-ST-40 and ECSS-Q-ST-80. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.9.1a","Requirement","ECSS-E-ST-10-11_0780107",1,"Created","The Mission operations plan including Operations procedures shall be established after SRR in conformance with ECSS-E-ST-70."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.9.1b","Requirement","ECSS-E-ST-10-11_0780108",1,"Created","The requirements included in the document shall be applied independently from the selected procedure delivery media."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.9.1c","Requirement","ECSS-E-ST-10-11_0780109",1,"Created","A board of stakeholders shall define and control the process (including validation) and products through the procedures life cycle."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.9.1d","Requirement","ECSS-E-ST-10-11_0780110",1,"Created","Operations nomenclature shall be applicable to procedures and HMI development. \n    NOTE 1 For example it can include crew, safety, medical doctors and operations representatives. \n    NOTE 2 An example of procedure authoring guideline is the “Operations Data File Standards” (SSP 50253) established for the ISS Program.\n    NOTE 3 Apart from strictly manual instructions, a procedure can include dynamic elements, such as navigation buttons, data display fields, symbols, and/or command buttons.\n    NOTE 4 This clause 4.9.1 is applicable to mix initiative procedures (semi-automatic)."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.9.2a","Requirement","ECSS-E-ST-10-11_0780111",1,"Created","Cue cards shall be provided as reminder for tasks execution."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.9.2b","Requirement","ECSS-E-ST-10-11_0780112",1,"Created","Cue cards shall be consistent with the related procedure(s).\n    NOTE 1 Any suitable media can be used as cue card according to the context of use.\n    NOTE 2 Cue cards are essentials of a procedure especially used for often occurring tasks, which can need only a general guide through a task for the crew onboard for execution."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.9.3a","Requirement","ECSS-E-ST-10-11_0780113",1,"Created","Boundary conditions, scheduled procedures usage, flight rules, medical and safety regulations shall be reflected in a timeline. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.9.3b","Requirement","ECSS-E-ST-10-11_0780114",1,"Created","The timeline shall contain system and experiment operations, attitude and pointing, dataflow operations."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.9.3c","Requirement","ECSS-E-ST-10-11_0780115",1,"Created","All resources and boundary conditions shall be compatible with the work/rest cycles of the crew as defined according to clause 4.5.4."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.9.3d","Requirement","ECSS-E-ST-10-11_0780116",1,"Created","During the HFE process compatibility of the timelines (schedules) of the various teams (onboard, on ground) shall be demonstrated. \n    NOTE The timeline is the translation of requirements and constraints into a timely ordered, feasible sequence of events, which is executed and, if necessary, updated during the mission or flight increment."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.9.4a","Requirement","ECSS-E-ST-10-11_0780117",1,"Created","The design of the display products shall comply with the output of the task analysis. \n    NOTE For example task analysis will determine if the main use of a display is of supervisory character, or of low-level manual reconfiguration type. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.9.4b","Requirement","ECSS-E-ST-10-11_0780118",1,"Created","Clause 4.4 shall apply for display product development."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.9.4c","Requirement","ECSS-E-ST-10-11_0780119",1,"Created","Displays and procedure development shall be coordinated."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.9.4d","Requirement","ECSS-E-ST-10-11_0780120",1,"Created","The project specific operations nomenclature shall be used.\n    NOTE This includes labels, system messages, telemetry measurements and command names."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.9.4e","Requirement","ECSS-E-ST-10-11_0780121",1,"Created","It shall be provided capability to ground users to have real time access to (at least) the identical display set available on the space segment."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.9.4f","Requirement","ECSS-E-ST-10-11_0780122",1,"Created","A project specific display standard shall be developed prior the manufacturing of any displays.\n    NOTE 1 Instead of developing new standards, it is a good practice to adopt existing standards or documents.\n    NOTE 2 The display standard specifies a common ‘look and feel’ across the various display products to be developed. \n    NOTE 3 An example display standard is the “Display and Graphics Commonality Standards” (SSP 50313) established for the ISS Program."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.9.4g","Requirement","ECSS-E-ST-10-11_0780123",1,"Created","Symbol-set used for displays shall be common to that used for procedures and training material."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.9.5a","Requirement","ECSS-E-ST-10-11_0780124",1,"Created","Training objectives and requirements for ground and flight personnel shall be established and specified."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.9.5b","Requirement","ECSS-E-ST-10-11_0780125",1,"Created","Training requirements shall be developed in parallel with the design process."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.9.5c","Requirement","ECSS-E-ST-10-11_0780126",1,"Created","Training curriculum and related training models and simulators shall be specified.\n    NOTE These are specified based on the previously established training objectives and requirements. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.1.1a","Requirement","ECSS-E-ST-10-11_0780127",1,"Created","Stakeholders including users (or their representatives) shall assess the system being designed according to the human centred design approach."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.1.1b","Requirement","ECSS-E-ST-10-11_0780128",1,"Created","Continuous assessment (iterative process) shall be supported by techniques of rapid prototyping.\n    NOTE Sample of rapid prototyping techniques are artistic impressions, moulding techniques to produce physical models and finally virtual or augmented environments "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.1.1c","Requirement","ECSS-E-ST-10-11_0780129",1,"Created","A continuous assessment plan (part of human-centred design process plan) shall be established. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.1.1d","Requirement","ECSS-E-ST-10-11_0780130",1,"Created","The continuous assessment plan shall include the planned evaluation events (e.g. usability reviews).\n    NOTE The continuous assessment plan is normally implemented with the utilisation of concurrent design techniques and instruments (e.g. concurrent design facility)."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.1.1e","Requirement","ECSS-E-ST-10-11_0780131",1,"Created","The continuous assessment plan shall be maintained.\n    NOTE I.e. must include additional events not foreseen in the initial plan whenever a modification affecting the human vs. machine interfaces is being evaluated for implementation in the project. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.1.1f","Requirement","ECSS-E-ST-10-11_0780132",1,"Created","After each evaluation event a report shall be issued. \n    NOTE Models and techniques used for the continuous assessment are important to be compatible with each project phase and the related size of the project."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.1.1g","Requirement","ECSS-E-ST-10-11_0780133",1,"Created","The technique and the models used for the continuous assessment shall be analysed for their quality of representativeness before each assessment is made."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.1.1h","Requirement","ECSS-E-ST-10-11_0780134",1,"Created","HFE continuous assessment process test report shall be prepared in conformance with Annex C."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.1.1i","Requirement","ECSS-E-ST-10-11_0780135",1,"Created","The model used for the assessment shall be capable to be incrementally updated to represent the achieved definition of the system under evaluation. \n    NOTE This is aimed at avoiding project cost impact that can be caused by the implementation of the continuous assessment."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.1.2a","Requirement","ECSS-E-ST-10-11_0780136",1,"Created","Table 4-1 provides an overview of human factors principles and techniques and the technological design space, applied in different stages (analysis, design, implementation and maintenance) of the continuous evaluation process. Techniques in italics shall be done always, whereas the other elements are recommended for more complex and/or critical systems."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.2.1a","Requirement","ECSS-E-ST-10-11_0780137",1,"Created","Usability review for the human machine system operated by a user or users shall include:\n    1. Experts evaluation, and\n    2. Users’ evaluation."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.2.1b","Requirement","ECSS-E-ST-10-11_0780138",1,"Created","For complex and critical tasks human in the loop evaluation shall be conducted."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.2.2a","Requirement","ECSS-E-ST-10-11_0780139",1,"Created","HFE shall take part in every project design review of equipment or systems in which a crewmember can be exposed or is foreseen to operate. \n    NOTE As design maturity evolves these are called crew station reviews (at different levels: payload, system) because they are defined and held with crew participation. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.2.2b","Requirement","ECSS-E-ST-10-11_0780140",1,"Created","Project design reviews shall include functionality demonstrations and fit checks of all equipment (e.g. connectors), accessibility checks, and the operability (labelling, intermediate stowage) of the equipment to be used.\n    NOTE In order to ensure a hardware design which organically incorporates the HFE requirements, the very early instrument for implementation is the requirements reviews (PRR and SRR)."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.2.2c","Requirement","ECSS-E-ST-10-11_0780141",1,"Created","The specifications presented in the project design reviews shall show that all relevant HFE requirements have been incorporated."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.2.2d","Requirement","ECSS-E-ST-10-11_0780142",1,"Created","At PDR it shall be demonstrated that the design is compliant with HFE requirements. \n    NOTE As a minimum these aspects of the system and its components must be taken into account: \n    1. Size (e.g. distances of connectors, access space for hands and tools),\n    2. Shape (e.g. big corner radii, position of required handles, interface requirements to surrounding systems),\n    3. Draft User Manuals,\n    4. Operation nomenclature compliances,\n    5. Installation and test procedures for AIT processing,\n    6. Positions of displays, labels, connectors, switches and knobs,\n    7. Illumination,\n    8. Noise,\n    9. Design for hardware replacement, maintenance and servicing,\n    10. Safety, and\n    11. Fields of view."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.2.2e","Requirement","ECSS-E-ST-10-11_0780143",1,"Created","At CDR it shall be demonstrated that all HFE design requirements are implemented."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.2.2f","Requirement","ECSS-E-ST-10-11_0780144",1,"Created","The last Crew Station Review shall take place before or be connected with QR. \n    NOTE This is to also ensure multiple or interconnected functional performance requirements verification."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.2.3a","Requirement","ECSS-E-ST-10-11_0780145",1,"Created","The human-centred design process plan mentioned in 4.4.2 shall include Crew Station Reviews (CSR)."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.2.3b","Requirement","ECSS-E-ST-10-11_0780146",1,"Created","Every hardware and software item and their combination, with crew interfaces shall be subject of at least one CSR."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.2.3c","Requirement","ECSS-E-ST-10-11_0780147",1,"Created","The CSR shall include the crew foreseen to operate the equipment or a crew familiar with the operational environment."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.2.4a","Requirement","ECSS-E-ST-10-11_0780148",1,"Created","Whole System Simulations shall be included in the System Engineering Plan.\n    NOTE 1 In order to avoid so called “human errors” and regardless if Phase C/D and Phase E are in two separated contracts several Whole System Simulations must be held when the flight segment is operatively tested/verified with the ground segment and with the users that are operating them.\n    NOTE 2 The purpose of Whole System Simulations is also to verify achievement of high level human in the loop requirements together with timeline and other ops products feasibility considerations and communication verification"]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.3.1a","Requirement","ECSS-E-ST-10-11_0780149",1,"Created","An assessment of the fidelity of the tool representation shall be made."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.3.1b","Requirement","ECSS-E-ST-10-11_0780150",1,"Created","This assessment shall be used in the evaluation of the results."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.3.2a","Requirement","ECSS-E-ST-10-11_0780151",1,"Created","Utilisation of simulation tools (e.g. Virtual Reality - Virtual Environments (VR/VE) techniques, including Augmented Reality or Mixed Reality) shall be considered for analyses and assessment support in the Human Centred Design process plan."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.3.3a","Requirement","ECSS-E-ST-10-11_0780152",1,"Created","Hardware or software used for development testing shall be of representative fidelity for the part or aspect that is under test."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.3.3b","Requirement","ECSS-E-ST-10-11_0780153",1,"Created","All the related affecting environment characteristics that have influence on the test results shall be of representative fidelity. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.3.3c","Requirement","ECSS-E-ST-10-11_0780154",1,"Created","Fidelity of representation of equipment or operational tools and approaches under test and their related test environments shall be included in the test report."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.3.3d","Requirement","ECSS-E-ST-10-11_0780155",1,"Created","HFE test reports shall be prepared according to the DRD in Annex D. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.3.4a","Requirement","ECSS-E-ST-10-11_0780156",1,"Created","Development test of local human machine interfaces and equipment assembling shall be performed."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.3.4b","Requirement","ECSS-E-ST-10-11_0780157",1,"Created","According to the level of representativeness required by the characteristics of the task being tested either space analogues facilities (NBF and PF), or software simulations (e.g. test with an electronic mannequin) shall be used for development tests. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.3.4c","Requirement","ECSS-E-ST-10-11_0780158",1,"Created","For final development evaluation and qualification purposes tests which simulate the 0-g environment and limitations of IVA and EVA space suits shall be performed for:\n    1. Full human body action,\n    2. Handling of one or more of the following:\n        · Removable and portable entire units,\n        · Units with large volumes (≥0,03 m³),\n        · Units with unmanageable shape.\n    3. Operations within restricted areas/volumes,\n    4. Operations with time constraints under above circumstances."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.3.4d","Requirement","ECSS-E-ST-10-11_0780159",1,"Created","The selection of the space analogues environment shall be done between Neutral Buoyancy Facilities (NBF) and Parabolic Fights (PF).\n    NOTE 1 The choice is generally based on the capability of the environment used in representing the real utilisation environment, both in term of dimensions and crew task duration. PF are usually capable to provide representative “zero-g” environment for around 20 seconds (depending from the airplane characteristics and profile of the selected trajectory). Longer crew tasks that cannot be subdivided in elementary tasks are generally tested using the NBF.\n    NOTE 2 During NBF tests, it is important to consider the significantly increased movement resistance caused by the water on the crew members, and on voluminous and plate items that they can be used to operate."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.3.4e","Requirement","ECSS-E-ST-10-11_0780160",1,"Created","Data collection techniques used during NBF or PF tests shall include as a minimum video, still camera."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.3.4f","Requirement","ECSS-E-ST-10-11_0780161",1,"Created","HFE test reports shall be prepared in conformance with Annex D. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.3.5a","Requirement","ECSS-E-ST-10-11_0780162",1,"Created","A human-machine system assessment shall be documented in a consensus report.\n    NOTE A consensus report can address a specific part or the whole human machine system."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.3.5b","Requirement","ECSS-E-ST-10-11_0780163",1,"Created","The fidelity of the environment, simulators and products used shall be documented in the consensus report."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.10.3.5c","Requirement","ECSS-E-ST-10-11_0780164",1,"Created","Users or their nominated representatives shall sign-off a consensus report.\n    NOTE A minimum of three signatures is recommended. This report may include a minority comments. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.11.2.2a","Requirement","ECSS-E-ST-10-11_0780165",1,"Created","HFE analysis and simulation reports shall be prepared in conformance with Annex B."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.11.2.3a","Requirement","ECSS-E-ST-10-11_0780166",1,"Created","When DHM are use for verification purposes, a Digital Mock-Up shall be used in conjunction to represent the context of use and the environment."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.11.3.1a","Requirement","ECSS-E-ST-10-11_0780167",1,"Created","For testing on ground an assessment of the gravity effects shall be performed.\n    NOTE 1 Ground HFE Test with human subjects is considered representative only when effect of gravity have limited influence or when ground simulation using zero-gravity space analogue environments (NBF or PF) typical limitations (water resistance and buoyancy of objects and subjects for NBF and time limitations for the PF) have limited influence on the test objectives. \n    NOTE 2 NBF and PF test are considered ground HFE tests. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.11.3.2a","Requirement","ECSS-E-ST-10-11_0780168",1,"Created","HFE demonstrations shall be used as formal verification event for some HFE related requirements. They are of two types:\n    1. Not user population representative: too few test subjects for an ergonomic review, and\n    2. Not representative environment: the environment used for the demonstration is not representative of the real environment of use. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.11.3.2b","Requirement","ECSS-E-ST-10-11_0780169",1,"Created","HFE demonstrations shall be used only when there are available analyses, simulations or development tests that can be integrated into the results of the demonstration."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.11.3.2c","Requirement","ECSS-E-ST-10-11_0780170",1,"Created","The HFE demonstrations shall be used to verify conformity to the HFE requirements in terms of habitability, usability and maintainability of the human-machine system.\n    NOTE 1 Usability/Crew Work Station Reviews are normally used in the evaluation of the HFE Demonstration.\n    NOTE 2 The insertion of \"demonstration\" as a separate event is complementary to the verification method “demonstration” as defined in ECSS-E-ST-10-02."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","4.11.4a","Requirement","ECSS-E-ST-10-11_0780171",1,"Created","The system simulation events shall be used to close out high level human machine system requirements.\n    NOTE 1 The system simulation events can be used to close human in the loop requirements such as timeline feasibility considerations and communication verification. \n    NOTE 2 This is when a space human-machine system is tested in its full operational environment (using flight hardware, related supporting simulators, operations products, its ground segment, crew - if any - and operation personnel).\n    NOTE 3 Simulations on different levels are also used to train and certify the different teams (users) involved in a mission and to verify and validate their performance and interaction for a specific mission. This comprises especially operational communication and operational products (onboard and ground procedures, timeline, command databases, etc.) across the whole system or selected parts of it."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","A.2.1<1>a","Requirement","ECSS-E-ST-10-11_0780172",1,"Created","The HCD process plan shall contain a description of the purpose, objective, content and the reason of prompting its preparation. More specifically it shall identify the human in the loop roles that originate the need for such a plan."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","A.2.1<2>a","Requirement","ECSS-E-ST-10-11_0780173",1,"Created","The HCD process plan shall list the applicable and reference documents to support the generation of the document."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","A.2.1<3>a","Requirement","ECSS-E-ST-10-11_0780174",1,"Created","The HCD process plan shall include any additional definition, abbreviation or symbol used."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","A.2.1<4>a","Requirement","ECSS-E-ST-10-11_0780175",1,"Created","The HCD process plan shall complement the system plans identify the major steps for the integration of the human in the loop."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","A.2.1<4>b","Requirement","ECSS-E-ST-10-11_0780176",1,"Created","More specifically this plan shall specify how the following issues are approached and specify their relation especially regarding their schedule with the system development actions as detailed in the other system plans:\n    1. Definition of user populations\n    2. Identification of the organisational environment related to the system being developed.\n    3. Identification of Stakeholders.\n    4. Identifications of the operational concept, and associated communication and decision lines within the system. \n    5. List the results of the Human vs. Automated Trade-off (performed in the project feasibility phase) with the identification of the major tasks assigned to the human part of the system.\n    6. Among the tasks identified in 4. identification of complex or critical human tasks and related scenarios definition.\n    7. Definition of the physical and psycho-physiological environments.\n    8. Definition of the context of use for the various components of the system that foresees a human interaction.\n    9. Establishment of the evaluation approach and related continuous assessment plan and reviews with the identification of the schedule and content for the: \n        (a) Crew station reviews (CSR).\n        (b) System simulations.\n            NOTE At these events it is expected that the status of the planned HFE analysis and simulation and test reports are reviewed.\n    10. Define the flight Crew Systems (if any) design and development plan.\n    11. Establish the final Demonstrations and Verification Approach for the human in the loop related requirements.\n    12. Related to point 10. definition of the time frame for analytical /simulation and test verification.\n    13. Related to point 10. definition of the location(s) and responsibilities for verification implementation (either analytical or test)."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","A.2.2a","Requirement","ECSS-E-ST-10-11_0780177",1,"Created","The HCD process plan when part of the System Engineering Plan shall maintain its integrity and not be separated throughout the various different system plans."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","A.2.2b","Requirement","ECSS-E-ST-10-11_0780178",1,"Created","The HCD process plan shall consider all human in the loop issues for the space system project regardless if it concerns the space segment or its ground infrastructure."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","A.2.2c","Requirement","ECSS-E-ST-10-11_0780179",1,"Created","Any requirements contained in this standard intentionally not taken into account shall be rationalised in this plan."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","B.2.1<1>a","Requirement","ECSS-E-ST-10-11_0780180",1,"Created","The HFE analysis and simulation report shall contain a description of the scope, purpose, objective, content and the reason of prompting its preparation."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","B.2.1<2>a","Requirement","ECSS-E-ST-10-11_0780181",1,"Created","The HFE analysis and simulation report shall list the applicable and reference documents to support the generation of the document."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","B.2.1<3>a","Requirement","ECSS-E-ST-10-11_0780182",1,"Created","The HFE analysis and simulation report shall include any additional definition, abbreviation or symbol used."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","B.2.1<4>a","Requirement","ECSS-E-ST-10-11_0780183",1,"Created","The HFE analysis and simulation report shall contain the following elements:\n    1. Reference to the relevant requirements.\n    2. Description of the reason for and objectives of the analysis.\n    3. Identification of the user population and definition of their related characteristics that are applicable to the role the user(s) is (are) playing in the analysis and/or simulation.\n    4. Identification of the environments (e.g. physical, organisational, psycho-physiological) related to the part under analysis.\n    5. Identification of the context of use (scenario) for the object (e.g. interface, software) or activity under analysis.\n    6. Presentation of the analysis and simulation approach used.\n    7. Description of the applicable simulated test article and/or human/machine interface or activity.\n    8. List of input assumptions, e.g. operational status of simulated test objects.\n    9. Description of the input data used with reference to the source of the data.\n    10. Description of the analytical/simulation tools used and, if applicable, indication about nodal break down.\n    11. Assessment of the representativeness of the analysis/simulation related to the simulation tools hard/software used.\n    12. As far as hardware or software item of the system under development is used in the simulation the following issues shall be included:\n        (a) A list of the human interfaces taken into account.\n        (b) Description of applicable human interfaces with respect to physical characteristics (such as surface temperature, roughness, other tactile properties, sensitivity to mechanical loads), or to cognitive aspects (e.g. colours, type of menus).\n        (c) Description of the identified, possible, interrelating effects between physical and cognitive aspects.\n        (d) Description of the predictions made on the affecting properties towards the item and the human in the loop.\n        (e) Description of the results of a sensitivity analysis for the interface data, performed to assess the modelling and simulation uncertainties.\n    13. Description of the analysis and simulation performance with details on the analytical steps, performance evaluation criteria, pass/fail criteria.\n    14. Conclusions and recommendations with respect to the item technical baseline, its operations manual and related operation products.\n    15. Description and assessment of the impact on the baseline design of the item under analysis and on the handling and performance of the other related items that are part of the system or subsystem and that may be affected by the results of the analysis (this include for example training materials, ground infrastructures)."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","B.2.2a","Requirement","ECSS-E-ST-10-11_0780184",1,"Created","The HFE analysis and simulation report is applicable to the analyses and simulations presented for the verification process of human in the loop related requirements but it is suggested to use a very similar structure for the analyses and simulations performed during the development phase and reissue the same document with the proper conclusions as final verification report. "]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","C.2.1a","Requirement","ECSS-E-ST-10-11_0780185",1,"Created","The HFE continuous assessment process report shall be the primary tool to control the implementation of the HCD process plan."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","C.2.1b","Requirement","ECSS-E-ST-10-11_0780186",1,"Created","The HFE continuous assessment process report shall provide the information presented in the following clauses:"]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","C.2.1<1>a","Requirement","ECSS-E-ST-10-11_0780187",1,"Created","The HFE continuous assessment process report shall contain a description of the purpose, objective, content and the reason of prompting its preparation."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","C.2.1<2>a","Requirement","ECSS-E-ST-10-11_0780188",1,"Created","The HFE continuous assessment process report shall list the applicable and reference documents to support the generation of the document."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","C.2.1<3>a","Requirement","ECSS-E-ST-10-11_0780189",1,"Created","The HFE continuous assessment process report shall include any additional definition, abbreviation or symbol used."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","C.2.1<4>a","Requirement","ECSS-E-ST-10-11_0780190",1,"Created","The HFE continuous assessment process report shall include according to the stage of the project and the activities performed in the phase the item listed below.\n    1. Definition of user populations.\n    2. Identification of Stakeholders.\n    3. List of the reports prepared and under preparation and their status.\n    4. List the Crew Systems components being evaluated and how.\n    5. List of the analyses and simulation performed.\n    6. List of the tests performed, for the tests the following items shall be included:\n        (a) Description of the purpose of the test and of the equipment/software packages or operation item being tested.\n        (b) Test subjects characteristics (including the training performed). \n        (c) Test plan and procedures used.\n        (d) Representativeness of the test environment (both physical and psycho-physiological) and of the equipment/software (either subject of the test or for support) used for the test (representativeness analysis).\n        (e) Context of use for the items being tested.\n        (f) Definition of used depended and independent variables and their validity with respect to the objectives of the test and the pass/fail criteria.\n        (g) Definition of the methods used to collect the results.\n        (h) Definition of the methods used to analyse the results and their sensitivity to the aim of the test.\n        (i) Test implementation and discussion of the related validation results.\n    7. List the evaluation events performed in the period of the report.\n        (a) Crew station reviews (CSR),\n        (b) System simulations."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","C.2.2a","Requirement","ECSS-E-ST-10-11_0780191",1,"Created","The HFE continuous assessment process report is part of the documents prepared for the system project events. It shall be established once and then updated in the subsequent events."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","D.2.1<1>a","Requirement","ECSS-E-ST-10-11_0780192",1,"Created","The HFE test report shall contain a description of the purpose, objective, content and the reason of prompting its preparation."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","D.2.1<2>a","Requirement","ECSS-E-ST-10-11_0780193",1,"Created","The HFE test report shall list the applicable and reference documents to support the generation of the document."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","D.2.1<3>a","Requirement","ECSS-E-ST-10-11_0780194",1,"Created","The HFE test report shall include any additional definition, abbreviation or symbol used."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","D.2.1<4>a","Requirement","ECSS-E-ST-10-11_0780195",1,"Created","The HFE test report shall include according to the stage of the project and the test activities performed in the phase the item listed below:\n    1. Definition of user populations used for the test and their representativeness w.r.t. the real user population as described in the HCD process plan.\n    2. Identification of Stakeholders (or confirmation of those defined in the HCD process plan).\n    3. List the systems components being evaluated and how.\n    4. Assessment of differences between test hardware and design baseline (based on CIDL).\n    5. List of the applicable requirements being tested against the design solution or the design to be verified.\n    6. List and results of the support analyses and simulation performed to define the subject of the test.\n    7. Test plan (expected) with the definition of locations and responsibilities for test performance and timelines.\n    8. Test procedures for both test subjects and test conductors and evaluators.\n    9. Special provisions (if any) adopted to reduce the number of depended variables, i.e. test subject training, subjects selection etc.\n    10. Tools used to collect the results of the human testing (e.g. questionnaires, video) and the related data analysis instruments.\n    11. Test results including stakeholder consensus report."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","D.2.2a","Requirement","ECSS-E-ST-10-11_0780196",1,"Created","The HFE development test report can be used in the verification campaign as verification test report combined with some dedicated analysis, simulation or demonstration aimed at compensating for a used test item not necessarily identical to the final solution being adopted in the design to be verified."]
["ECSS-E-ST-10-11C","ECSS - Current v1.0","D.2.2b","Requirement","ECSS-E-ST-10-11_0780197",1,"Created","The HFE verification test report is part of the documents prepared for the system project test verification campaigns."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.2a","Requirement","ECSS-E-ST-10-12_0980001",1,"Created","The customer shall specify minimum RDMs (MRDMs) for the various radiation effects.\n    NOTE 1 The customer and supplier can agree to other margins to reflect conducted testing (e.g. supplier-performed lot acceptance tests, published tests on similar components) in specific cases and in accordance with the hardness assurance programme defined according to ECSS-Q-ST-60. These minimum RDMs can be established directly by the customer, or based on a proposal made by the supplier and approved by the customer.\n    NOTE 2 The margins for SEE are based on the consideration of acceptable risks and rates and are therefore involve system level considerations."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.2b","Requirement","ECSS-E-ST-10-12_0980002",1,"Created","The achieved RDM shall be established by analysis and a justification provided in the applicable radiation hardness assurance programme required by ECSS-Q-ST-60 for Class 1, 2 and 3 components.\n    NOTE For RDM, see Clause 5.1.1."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.2c","Requirement","ECSS-E-ST-10-12_0980003",1,"Created","The analysis specified in requirement 5.2b shall include the following elements, and the associated uncertainties and margins, either hidden or explicit:\n    1. Space radiation environment, evaluated as specified in clause 5.3.\n    2. Deposited dose, calculated as specified in clause 5.4, and including:\n        (a) Shielding and\n        (b) Calculation of effects parameters \n            NOTE For example, ionising dose, displacement dose, SEE rate, instrumental background, and biological effects.\n    3. Radiation effect behaviour of entities (including components, payloads, and humans), evaluated as specified in clause 5.5.\n        NOTE Hidden margins appear in many aspects of the hardness assurance process (see also the clauses of ECSS-Q-ST-60 relevant to “Radiation hardness”) and they can compensate for uncertainties in other elements of the assessment process. The hardness assurance plan can consider:\n            · Part type sensitivity evaluation.\n            · Lot-to-lot variation.\n            · Worst-case analysis\n            · Minimum considered radiation level (since dose-depth curves are often asymptotic to a dose value for thick shielding due to bremsstahlung or high energy protons, a minimum qualification dose can be specified)"]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.2d","Permission","ECSS-E-ST-10-12_0980161",1,"Created","For those elements in the design margin analysis, as specified in requirement 5.2c, that assume the following worst case conditions, their contribution to the design margin need not be applied:\n    1. For environment, those specified as worst-case in ECSS-E-ST-10-04, Clause 9. \n    2. For other than environment, those specified in clauses 5.4 and 5.5. "]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.2e","Requirement","ECSS-E-ST-10-12_0980005",1,"Created","It shall be ensured that the qualification process demonstrates that the RDMs meet the MRDMs for the design adopted.\n    NOTE With this objective, the minimum radiation design margins specified for the equipment are established based on the reliability and availability requirements, and on the methodologies adopted for calculating the radiation environment and effects."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.3a","Requirement","ECSS-E-ST-10-12_0980006",1,"Created","When using the AE-8 model for electrons at the worst-case longitude on geostationary orbit for long-term exposure (greater than 11 years), no additional margin shall be applied."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.3b","Requirement","ECSS-E-ST-10-12_0980007",1,"Created","When using the AE-8 model under conditions other than specified in requirement 5.3a, or using standard models of the particle environment other than AE-8, it shall be demonstrated that the achieved RDM includes the model uncertainties.\n    NOTE The model uncertainties are reported in the radiation environment specification as specified in ECSS-E-ST-10-04, clause 9.3."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.3c","Requirement","ECSS-E-ST-10-12_0980008",1,"Created","Where the radiation environment models are worst-case in the radiation environment specification, as specified in ECSS-E-ST-10-09 clause 9, no additional margin shall be applied."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.3d","Requirement","ECSS-E-ST-10-12_0980009",1,"Created","Where models are of a probabilistic nature, the level of risk to be used shall be agreed between customer and supplier and reported alongside the achieved RDM. \n    NOTE Examples of models of a probabilistic nature are statistical solar proton models. Examples of an acceptable level of risk are worst case and specific percentiles."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.3e","Permission","ECSS-E-ST-10-12_0980162",1,"Created","Where models are of a probabilistic nature further margin need not be applied if it is demonstrated that the intrinsic uncertainties in the instrument data underlying the model are included in the model’s probabilistic formulation.\n    NOTE Any margin associated with the environment prediction is strongly dependent on the available knowledge and is used to mitigate against the uncertainties in the environment. Experience with certain types of Earth orbit is extensive, giving rise to smaller margins, but uncertainties for others, and for example other planets, necessitate careful consideration of uncertainties."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.4a","Requirement","ECSS-E-ST-10-12_0980011",1,"Created","One of the three following methods shall be used to evaluate the deposited dose:\n    - abstract simple shielding such as planar or spherical shell geometry, as specified in clause 6.2.2.1;\n    - 3-D sector shielding, as specified in clause 6.2.3;\n    - 3-D physics-based Monte-Carlo analysis, as specified in clause 6.2.4.\n        NOTE They are ordered in increasing accuracy and rigour. "]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.4b","Requirement","ECSS-E-ST-10-12_0980012",1,"Created","In establishing the shielding contribution to a component’s RDM, and when the simulation models less than 70% of the equipment mass, then the model is conservative, and additional margin shall not be applied to doses computed in geometries with the 3-D sector shielding method specified in clause 6.2.3. \n    NOTE 1 This is true when approximate geometry models are used which are demonstrably conservative (e.g. lacking modelling of some units, harness, mass and fuel).\n    NOTE 2 3-D sector analysis methods (slant/solid or Norm/shell) for electron dose calculations are not always worst case. In one study a corrective factor of about 2 was needed for the Slant/Solid method and 3.4 for the Norm/Shell."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.4c","Requirement","ECSS-E-ST-10-12_0980013",1,"Created","In establishing the shielding contribution to a component’s RDM, and when 3-D physics-based Monte-Carlo analysis specified in clause 6.2.4 is used for electron-bremsstrahlung dominated environments, it shall be demonstrated that the achieved RDM includes the uncertainties (including the level of conservatism in the shielding and the systematic and statistical errors in the calculation).\n    NOTE 1 Examples of electron-bremsstrahlung dominated environments are geostationary and MEO orbits.\n    NOTE 2 When 3-D Monte-Carlo analysis is used for ion-nucleon shielding in heavily shielded situations (e.g. ISS and other manned missions) greater margins are used."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.5.1a","Requirement","ECSS-E-ST-10-12_0980014",1,"Created","It shall be demonstrated that the achieved RDM includes the uncertainties that arise in component susceptibility data from the radiation hardness assurance programme specified in ECSS-Q-ST-60 for Class 1, 2 and 3 components, including:\n    1. uncertainties in the results from irradiation: the beam characterization and dosimetry, and the subsequent statistical errors in the measured or derived results such as SEE cross-sections;\n    2. differences between the test circuit and the application circuit, such as bias conditions, opportunities for annealing or ELDRS;\n    3. differences in the radiation susceptibility of different components within the same batch, or within the collection of batches selected for testing;\n    4. differences between part batches or collection of batches, where errors arise from relating the results from component irradiations to devices employed in the final application;\n    5. the possible effects of packaging on low-energy proton beams (<30 MeV);\n        NOTE The reason is that this packaging can affect the penetration and energy (LET) of the particles. \n    6. the stated accuracy of the facility together with the uncertainties in requirement 5.5.1a.1, taking into account position, attenuation;\n        NOTE 1 In the absence of contemporaneous beam characterisation, quoted particle accelerator characteristics are assumed to be no better than 30 % accurate in beam intensity.\n        NOTE 2 For -ray sources such as 60Co, uncertainties in the total ionising dose delivered are typically better than 10 %.\n    7. the variations in performance within a device population, be determined by employing one or more of the following and in accordance with the radiation hardness assurance programme defined according to ECSS-Q-ST-60 for Class 1, 2 and 3 components:\n        (a) statistical techniques applied to test data;\n        (b) data from heritage information concerning the part;\n        (c) data from previous worst case analyses.\n            NOTE Such techniques are defined in the clauses of ECSS-Q-ST-60 relevant to “Radiation Hardness”."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.5.2a","Requirement","ECSS-E-ST-10-12_0980015",1,"Created","In assessment of a part’s total dose behaviour (ionizing and non-ionizing), the achieved RDM shall include the following items as part of the radiation hardness assurance process:\n    1. test conditions leading to worst-case,\n    2. lot-to-lot variability,\n    3. intra-lot variability,\n    4. worst-case analysis as specified in ECSS-Q-ST-30,\n    5. consistency of test results with respect to previous testing.\n        NOTE The main margin in radiation dose assessment is provided through the radiation hardness assurance plan. As specified in ECSS-Q-ST-60, a radiation hardness assurance plan is prepared, agreed and reviewed at all mission phases."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.5.2b","Requirement","ECSS-E-ST-10-12_0980016",1,"Created","If a device is sensitive to TNID, then this shall be included in the establishment of the achieved RDM."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.5.3.1a","Requirement","ECSS-E-ST-10-12_0980017",1,"Created","It shall be demonstrated that the equipment reliability requirements include the potential for large uncertainties in predicting SEE.\n    NOTE 1 For a rationale, see clause 5.1.3\n    NOTE 2 It is common practice in SEE evaluation to use worst-case environmental assumptions and perform worst-case analysis of system impacts. As indicated in clause 5.2, when such worst-case analysis is performed, additional margins are not applied.\n    NOTE 3 Prediction errors of a factor 10 are possible in some circumstances."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.5.3.1b","Requirement","ECSS-E-ST-10-12_0980018",1,"Created","Where the SEE calculation is based on an environment prediction which includes the confidence level for the environment not being exceeded, the confidence level shall be reported along with the statement of the achieved RDM for SEEs.\n    NOTE Some environmental models are statistical in nature, indicating the probability of conditions being exceeded. Such models are specified in ECSS-E-ST-10-04. "]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.5.3.1c","Requirement","ECSS-E-ST-10-12_0980019",1,"Created","Margin shall be guaranteed through application of the hardness assurance programme as specified in ECSS-Q-ST-60. "]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.5.3.2a","Requirement","ECSS-E-ST-10-12_0980020",1,"Created","In the case of destructive single event effect, the acceptable probability of component failure by the SEE mechanism, and the calculated probability of failure used to determine the achieved RDM, shall relate to performance of the component for the environment over the specified period of operation, rather than simply the worst-case environment condition. \n    NOTE 1 Worst-case conditions can correspond or not to actual operating environment.\n    NOTE 2 In many cases it can be demonstrated that environment contributions from non-worst-case conditions are negligible compared with the worst-case environment."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.5.3.2b","Permission","ECSS-E-ST-10-12_0980163",1,"Created","RDM analysis need not be performed for component destructive SEE if:\n    1. the threshold energy (for protons or neutrons) or threshold LET (for ions) for destructive SEE is greater than that identified as the immunity threshold in the radiation hardness assurance programme, or\n    2. the electrical operational conditions for a component have been derated to levels where the device is shown by testing not to suffer that particular SEE mechanism."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.5.4a","Requirement","ECSS-E-ST-10-12_0980022",1,"Created","The radiation metric used in the radiation design margin for sensor background calculations shall be agreed with the customer."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.5.4b","Requirement","ECSS-E-ST-10-12_0980023",1,"Created","The radiation metric used in the achieved RDM shall be chosen as representative of the sensor bandwidth critical to the mission objectives.\n    NOTE 1 It is highly dependent upon the sensor design and application. It can be provided by the customer in the equipment requirements.\n    NOTE 2 As with single event effects, the MRDM required can be dependent upon the phase of the mission, and local environment."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.5.4c","Requirement","ECSS-E-ST-10-12_0980024",1,"Created","Where the background has been simulated, a comparison between simulations and irradiation results for the sensor (or a representation of the sensor) shall be performed in order to gauge the level of error in the modelling process.\n    NOTE The uncertainties associated with the calculation of the background are very much dependent upon the sensor or instrument design and method for calculating detector background, including, where appropriate, the use of experimental data."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.5.5a","Requirement","ECSS-E-ST-10-12_0980025",1,"Created","The protection limits and predicted exposure used to determine the achieved RDM for biological effects shall be defined in terms of one or more of the following variables:\n    1. effective dose;\n    2. organ equivalent dose;\n    3. ambient dose equivalent;\n    4. directional dose equivalent;\n    5. personal dose equivalent.\n        NOTE 1 For requirements on radiation effects in biological material, see Clause 11. For background on limit exposure policies of the different Space Agencies, see ECSS-E-HB-10-12 Section 10.4.4.\n        NOTE 2 For interplanetary missions, exposure limits are not currently defined."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.6.2a","Requirement","ECSS-E-ST-10-12_0980026",1,"Created","Before PDR, a worst-case assessment of unit shielding shall be made (i.e. minimum shielding thickness)\n    NOTE Before PDR an accurate geometrical model of a satellite is not generally available. As a consequence it is not possible to estimate the dose level expected at a part and so the final achieved RDM cannot be accurately assessed. "]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.6.2b","Requirement","ECSS-E-ST-10-12_0980027",1,"Created","Other than the environmental margin, additional margin shall not be applied to the dose calculation at this stage."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.6.2c","Requirement","ECSS-E-ST-10-12_0980028",1,"Created","For parts whose achieved RDM determined from the worst-case assessment specified in requirement 5.6.2a and b falls below the MRDM specified in requirement 5.2a and where information is available, the worst case assessment shall be augmented by geometrical (sector-shielding) analysis. "]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.6.2d","Permission","ECSS-E-ST-10-12_0980164",1,"Created","The shielding analysis specified in requirement 5.6.2c may be iterated, improving the geometrical fidelity at each stage so as to converge on an RDM that meets or exceeds the MRDM.\n    NOTE The shielding analysis is based on evaluation of the basic spacecraft and unit geometries, with sufficient detail of major local spacecraft elements which can improve shielding. Monte-Carlo techniques can also be attempted at this stage. The achieved RDM is evaluated considering the environmental and shielding uncertainties and possible systematic conservatism."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.6.2e","Requirement","ECSS-E-ST-10-12_0980030",1,"Created","For parts whose achieved RDM, as determined from the assessment in requirements 5.6.2a, b and 5.6.2c, falls below the MRDM specified in requirement 5.2a shall be:\n    1. declared by the supplier to have failed to meet the specification, \n    2. reported to the customer, and\n    3. either replaced with a part that meets the MRDM or subjected to detailed testing and analysis procedures.\n        NOTE 1 The tests and analysis procedures are specified in the clauses of ECSS-Q-ST-60 relevant to “Radiation Hardness”.\n        NOTE 2 This analysis can be performed after PDR when more detail of the system geometry is available for more accurate shielding analyses."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.6.3a","Requirement","ECSS-E-ST-10-12_0980031",1,"Created","Before CDR, it shall be verified that the final radiation values, considering the uncertainties and conservatism in the environment, shielding and parts evaluation, are compatible with the specified project-specific overall and component-specific MRDM.\n    NOTE 1 The RHA process defines the reporting expected at this stage (normally radiation analysis, including shielding).\n    NOTE 2 For components that are non-compliant with the MRDM at this stage, detailed 3-D shielding calculations can be employed to improve the fidelity of the calculation of the radiation level, or as the basis of a supplier Request for Waiver on the MRDM. The methods employed can be full and detailed sectoring or full Monte-Carlo radiation transport analysis as specified in clause 6.2.4, including a geometrical analysis of the unit, its surroundings and the spacecraft structure."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","5.6.4a","Requirement","ECSS-E-ST-10-12_0980032",1,"Created","For radiation margin issues still open or identified after CDR, an analysis shall be performed to evaluate:\n    1. Potential solutions.\n    2. The functioning of the part in the context of a worst-case analysis.\n    3. The implications at sub-system and system level.\n        NOTE 1 Problems identified or remaining close to or after CDR can be expensive to rectify.\n        NOTE 2 The pass/fail criteria in testing can be unrelated, or not closely related, to functional failure. If a part’s parameter is out of spec after testing, it can be that the parameter is not important in the equipment worst-case analysis. "]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","6.2.1.1a","Requirement","ECSS-E-ST-10-12_0980033",1,"Created","A first-order estimate of the influence of shielding shall be made by determining the dose or particle fluence corresponding to the most lightly shielded part of the subsystem under evaluation using the simplified approaches specified in clause 6.2.2. "]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","6.2.1.1b","Permission","ECSS-E-ST-10-12_0980165",1,"Created","If the particle environment (including secondary as a result of additional shielding) behind that shielding is tolerable, further analysis need not be performed. \n    NOTE 1 Example of secondary radiation is bremsstrahlung.\n    NOTE 2 In some special circumstances (e.g. for galactic cosmic rays in high-Z materials) enhancement in radiation levels from secondary particles as a result of additional shielding can take place."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","6.2.1.1c","Requirement","ECSS-E-ST-10-12_0980035",1,"Created","In cases other than requirement 6.2.1.1b, one of the following analyses of the shielding shall be performed:\n    - a sector-analysis, as specified in clauses 6.2.2 and 6.2.3, or \n    - a detailed radiation transport simulation of the whole or a part of the spacecraft, as specified in clause 6.2.4. \n    - shielding analysis as part of a simultaneous complete analysis with all sensitive locations defined, irrespective of whether problems are apparent or not."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","6.2.1.2a","Requirement","ECSS-E-ST-10-12_0980036",1,"Created","The shielding analysis specified in clause 6.2.1.1 shall include \n    1. the secondary radiation effects in accordance with the mission types identified in Table 6-1.                                     \n    2. for specialised instrumentation agreed with the customer (such as astrophysics radiation detectors), all prompt and delayed radioactive emissions which have the potential to produce background signals.\n        NOTE This can be done either by including them in the calculations, or by demonstrating that the effect is negligible."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","6.2.2.1a","Requirement","ECSS-E-ST-10-12_0980037",1,"Created","For the first-order estimate of the influence of shielding, the analysis shall be performed as follows:\n    1. Assume that the influence of material type is negligible, and the different materials can be approximated to the equivalent mass of a single material type (such as aluminium) by a proportional change in density.\n    2. approximate the shielding geometry to one of the geometries shown in Table 6-2, as follows:\n        (a) Approximate a configuration with two opposing lightly shielded directions to the summed effects of two finite slab shown in Table 6-2.\n        (b) Approximate a configuration with a light shielding in one direction with heavy rear-side shielding to a semi-infinite planar geometry.\n        (c) Approximate a configuration with uniform shielding in all directions to the solid sphere.\n        (d) Approximate a configuration with a large cavity and uniform shielding in all directions (thickness < 0,5 cavity diameter) and no significant material local to the dose point to the spherical shell geometry.\n    3. Obtain the effect-versus-depth information (the so called “dose-depth curve” and/or comparable information for particle fluence or other radiation effects parameters as a function of shielding).\n    4. Assess the minimum shielding quantity provided by the spacecraft to be used in conjunction with the effect-versus-depth.\n    5. If the shielding conditions do represent a worst-case analysis, and the component, subsystem or system performs to within the specified RDM for those shielding conditions, consider the result of the analysis as acceptable.\n    6. In case other than requirement 6.2.2.1a.5, apply the detailed shielding calculation method specified in clause 6.2.2.2 or 6.2.3.\n        NOTE The first order approximation of the influence of shielding can result in an overestimation of the radiation effects, and a more detailed analysis can indeed show that the component, subsystem or system performs to within the specified RDM. This can be a worst-case estimation and so can indicate a requirement for more detailed analysis."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","6.2.2.2a","Requirement","ECSS-E-ST-10-12_0980038",1,"Created","For the second-order estimate of the influence of shielding, the analysis shall be performed by using the method in clause 6.2.2.1 and accounting for heterogeneous shielding by estimating the percentage of the overall solid angle (4p) subtended by the major elements of the configuration viewed from the shielded point.\n    NOTE The reason is that the sectoring method based on solid angles takes account of the fact that generally shielding around a point of interest is heterogeneous."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","6.2.3a","Requirement","ECSS-E-ST-10-12_0980039",1,"Created","For detailed sector shielding calculations, the following shall be done:\n    1. Assume that the influence of material type is negligible, and the different materials can be approximated to the equivalent mass of a single material type (such as aluminium) by a proportional change in density.\n    2. Agree with the customer the specific sector shielding calculation method to use.\n        NOTE A summary of possible methods to use is presented in ECSS-E-HB-10-12 Section 5.\n    3. If sectoring calculation is applied, assess if one of the following cases is present:\n        (a) Performance of graded shields, dose enhancement in a semiconductor die close to materials with high-Z elements, or high-Z packaging materials, or X-ray bremsstrahlung dose in a location shielded by tantalum.\n            NOTE 1 Examples of these elements are gold, hafnium, tungsten.\n            NOTE 2 The reason is that sector shielding approach does not consider the physics involved in these phenomena. For graded shields see ECSS-E-HB-10-12 Section 5.\n        (b) The calculation includes assessment of secondary hadron levels from materials with significantly different (atomic) mass number from the original target material. \n            NOTE 1 For example: Neutrons generated by high-energy proton interactions in lead.\n            NOTE 2 This is particularly important for neutron fluxes or cosmic-ray fragments in heavily shielded manned missions or in sensitive scientific instruments.\n    4. If the assessment specified in requirement 6.2.3a.3 is positive then either:\n        (a) analyse the case ensuring conservatism in the sector shielding evaluation, or\n        (b) perform the shielding calculation based on a radiation transport model in accordance with clause 6.2.4, which use the characteristics of the actual materials employed.\n    5. Use one of the following approaches for the calculation:\n        (a) Agree with the customer the method for the particular sector shielding evaluation, or\n        (b) use the “SLANT” approach for calculating the amount of material along a path, and the solid sphere geometry for production of the dose-depth or fluence-versus-depth curve, or\n        (c) use the “NORM” technique for estimating the amount of material along a path, and the spherical shell geometry for production of the dose-depth or fluence-versus-depth curve.\n            NOTE The transport model specified in clause 6.2.4 considers the actual materials employed. Such calculations can be performed using, for example, a finite-difference coupled electron-photon simulation or a Monte Carlo simulation for nuclear and electron-photon interactions.\n    6. Provide to the customer a description of the calculation techniques used, including the:\n        (a) description of the sector shielding simulation method used.\n        (b) number of directional rays sampled\n        (c) dose-depth geometry type.\n        (d) results of the calculations\n    7. For protons and heavier ions, use the projected particle range for the calculation of the attenuation of the particle flux.\n        NOTE In ground based mono-energetic irradiation, particle straggling can result in an underestimation of particle effects. Extrapolated ranged can be more appropriate.\n    8. For sector shielding calculations, use a minimum of 1800 rays evenly distributed over 4p steradians.\n        NOTE Sector shielding can be used to compute a shield distribution, rather than direct computation of radiation effects parameters. This can be a useful way of using shielding information for a number of subsequent analyses. Therefore it is important to ensure sufficient resolution of the shielding distribution (which is dependent upon the geometry and the specified precision). In such a situation, the considerations outlined above apply also for the subsequent analyses."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","6.2.4a","Requirement","ECSS-E-ST-10-12_0980040",1,"Created","For detailed radiation transport calculations, the following shall be done:\n    1. Use for the calculation the characteristics of the actual materials used in the final structure or subsystem, or by agreement with the customer alternative materials that have similar electromagnetic (electron-photon) and nuclear cross-sections.\n        NOTE Detailed radiation “transport” calculations provide a more accurate treatment of the radiation interaction processes in which the particle numbers, species, energy, and direction of propagation can change in a complex manner according to the Boltzmann transport equation. This type of calculation approach is used where aspects of the equipment or component performance and the influence of shielding cannot be adequately treated within a sector shielding analysis.\n    2. If undertaken, agree with the customer the level of physics simulation to use.\n        NOTE The objective is to ensure accurate treatment of the production of secondary particles which can affect the component, system or human, as well as the attenuation and scattering of the primary radiation (see ECSS-E-HB-10-12 Section 5.6).\n    3. Agree with the customer the number of dimensions (1-D. 2-D or 3-D) to use in the simulation.\n        NOTE The objective is to ensure that geometries are well represented and the analysis is conservative.\n    4. Use a number of primary particle simulations such that the statistical errors for the results used to infer component response are within the project’s design margins for the radiation shielding model.\n        NOTE Radiation simulations employing Monte Carlo models carry both statistical and systematic errors, the latter as a result of uncertainties in the physics models and geometry approximations."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","6.3.1a","Requirement","ECSS-E-ST-10-12_0980041",1,"Created","In implementing the different approaches in clause 6.2 the radiation shielding model shall include in the calculations the following geometry elements:\n    1. Parts packaging, as specified in clause 6.3.2.1.\n        NOTE Since it is the one that is the closest to the sensitive portion of the part (the die), the influence of packaging on the radiation received by the component can be important, especially for electrons or low-energy (up to a few 10’s MeV) protons.\n    2. Equipment, as specified in clause 6.3.2.2.\n    3. Spacecraft, as specified in clause 6.3.2.3.\n    4. Interfaces between spacecraft and (sub)system, as specified in clause 6.3.2.4.\n        NOTE Omission from the calculation of geometry elements normally leads to conservative calculations (higher radiation effect predictions), although some packaging and other materials near the die can enhance radiation levels in the die."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","6.3.2.1a","Requirement","ECSS-E-ST-10-12_0980042",1,"Created","The effect of the parts packaging in the radiation shielding model shall be assessed as follows:\n    1. Place the target point inside the package, located on top or inside the active region of the volume \n        NOTE The objective is to get the best possible estimate of the deposited dose at die level, the target point. The active region is typically a silicon chip.\n    2. For hybrid devices containing several sensitive dies, use one target point per die.\n        NOTE The reason is that the calculated dose level can vary significantly depending on the die location.\n    3. For situations where the total ionising dose from X-ray or g-ray fields is the largest contribution, assess the influence of local high-Z materials and include it in the calculations.\n        NOTE Example of high-Z materials are gold contacts or tungsten silicide layers and vias."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","6.3.2.2a","Requirement","ECSS-E-ST-10-12_0980043",1,"Created","The effect of the equipment in the radiation shielding model shall be assessed as follows:\n    1. Include in the equipment model (at least) the subsystem enclosure and printed circuit boards (PCBs), unless \n        (a) worst-case calculations in which they are excluded show the component can tolerate the environment to within the RDM, and \n        (b) it is demonstrated that the enclosure and PCB materials do not lead to radiation enhancement. \n    2. Either surround the target points by the actual parts package model, or use a worst case parts package.\n        NOTE Example of worst case parts package is an aluminium sphere with a thickness of 0,6 mm.\n    3. In order to get a better estimate of the radiation level, include in the model any passive element providing shielding to active elements.\n        NOTE Example of passive elements that can provide shielding are transformers, capacitors, and connectors."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","6.3.2.3a","Requirement","ECSS-E-ST-10-12_0980044",1,"Created","The effect of the spacecraft in the radiation shielding model shall be assessed as follows:\n    1. Include in the spacecraft radiation model a representation of the structure and the boxes for equipments. \n    2. Include in the model the material, as follows:\n        (a) Where the dominant material used in the spacecraft is aluminium, or material of similar Z, model the spacecraft as aluminium boxes of the thickness having the size of actual enclosures, containing a reduced density of aluminium to provide the equivalent mass of the actual contents. \n        (b) Otherwise, model the spacecraft with the precise material and contents as for the actual subsystem.\n    3. Approximate the walls of the satellite to those of an aluminium box providing the equivalent areal mass. \n    4. Assess the shielding afforded by the satellite structure for an internal subsystem either by:\n        (a) Using a worst-case calculation, and assuming normal incidence of radiation on each of the faces of the satellite box, or\n        (b) Perform a sector shielding analysis for each subsystem location to better determine the shielding distribution.\n    5. If the spacecraft surface includes honeycomb panels, for worst case calculations, either:\n        (a) Incorporate in the radiation model only the face-panels of the honeycomb, or \n        (b) Agree with the customer the model to use to include the actual geometry and materials."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","6.3.2.4a","Requirement","ECSS-E-ST-10-12_0980045",1,"Created","If the internal arrangement of (sub)systems are not be available when sectoring is made of the spacecraft geometry, \n    1. Specify the environment at (sub)system level in a way that the analysis of the (sub)system shielding and radiation effects can be made. \n    2. If the (sub)system has a box shape, either:\n        (a) Provide the dose or fluxes to each surface, or \n        (b) Mesh the surfaces and provide the values for each mesh element. \n            NOTE While useful for engineering purposes, it is important to recognise the uncertainties in this method. It can happen that the propagation directions of the radiation and possibly the type and energy of the radiation are not retained. Nevertheless, this is generally a conservative approach."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","6.3.2.4b","Requirement","ECSS-E-ST-10-12_0980046",1,"Created","In any case other than requirement 6.3.2.4a, the actual internal arrangements of (sub)systems shall be provided by the customer and used by the supplier.\n    NOTE The satellite geometry and subsystem geometry can be exchanged between contractors and customers using available geometry exchange formats or tools."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","7.2a","Requirement","ECSS-E-ST-10-12_0980047",1,"Created","The target material shall be reported with the TID units. \n    NOTE 1 For expressing TID effects in silicon, the units of dose commonly used are Gy(Si) or rad(Si).\n    NOTE 2 The reason of this requirement is that dose is dependent also on the target material."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","7.3a","Requirement","ECSS-E-ST-10-12_0980048",1,"Created","Total ionising dose effects shall be analysed for spacecraft and planetary-mission systems to be operated within any of the following radiation environments:\n    1. Trapped proton and electron belts\n        NOTE For example, terrestrial and other planetary belts, such as Jovian.\n    2. Solar protons\n    3. Secondary particles, except secondary neutrons\n        NOTE This includes bremsstrahlung from electrons, and protons generated in atmospheric showers in the planetary environment or within large spacecraft or planetary-lander structure.\n    4. Local sources of radiation.\n        NOTE For example, in close proximity to radioactive or nuclear-energy sources, e.g. RTGs generating g radiation."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","7.4a","Requirement","ECSS-E-ST-10-12_0980049",1,"Created","If one of the technologies identified in Table 7-1 is used in spacecraft and planetary-mission systems, the potential TID level and effects shall be analysed.\n    NOTE 1 Technologies in Table 7-1 are susceptible to TID. This is not exhaustive and other parameters can be important and result from worst-case analysis.\n    NOTE 2 As specified in Clauses 8, 9 and 10, calculation of cumulative damage due to non-ionising energy loss and single event effects and detector background is also mandatory for many of these components, such as those based on bipolar junction transistors or optoelectronics."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","7.5.1a","Requirement","ECSS-E-ST-10-12_0980050",1,"Created","The radiation damage assessment shall use the total ionising dose due to charged particles and X-rays, calculated as specified in clause 7.5.2. "]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","7.5.1b","Requirement","ECSS-E-ST-10-12_0980051",1,"Created","The influence of shielding in attenuating the primary particle environment and modification to its spectrum at the component location shall be analysed, including the effects of the component packaging, as specified in Clause 6."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","7.5.1c","Requirement","ECSS-E-ST-10-12_0980052",1,"Created","The influence of secondary particles on TID shall be analysed.\n    NOTE The analysis can conclude that their contribution is negligible compared with the residual primary radiation components. This secondary radiation is typically electron-induced bremsstrahlung but in some circumstances secondary protons, electrons and neutrons can also have an important contribution."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","7.5.1d","Requirement","ECSS-E-ST-10-12_0980053",1,"Created","For items in unshielded or lightly shielded locations, the energy spectrum at low energy shall be as specified in the radiation environment specification from ECSS-E-ST-10-04 clause 9.3."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","7.5.2a","Requirement","ECSS-E-ST-10-12_0980054",1,"Created","The calculation of the ionising dose in the target shall use the particle fluxes at the surface of the TID-sensitive elements of the component or material. \n    NOTE Methods for the related shielding calculation are specified in clause 6.2."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","7.5.2b","Requirement","ECSS-E-ST-10-12_0980055",1,"Created","At a point or in a finite volume, the dose shall be calculated as follows:\n    1. Calculate particle ionization energy as follows:\n        (a) Calculate charged particle ionisation restricted stopping power (or LET) in the material, or in the case of photons, mass energy absorption coefficients, or\n        (b) Calculate particle ionisation energy deposition in a volume where the radiation field suffers negligible change (either by attenuation or multiple scattering, traversing the volume) or extended volumes.\n            NOTE Monte-Carlo methods can be used for this purpose.\n    2. Use tabulations of dose versus flux and shielding information. \n        NOTE This is the case of SHIELDOSE and SHIELDOSE-2, based on Monte-Carlo calculation and energy loss functions."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","7.5.2c","Requirement","ECSS-E-ST-10-12_0980056",1,"Created","Analyse dose enhancement effects due to changes in material composition in the vicinity of, or within a target, as a result of using high-Z materials. \n    NOTE For more details on dose enhancement phenomena, see ECSS-E-HB-10-12, section 5.f."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","7.6a","Requirement","ECSS-E-ST-10-12_0980057",1,"Created","The use of component test data used in conjunction with total ionising dose results to predict degradation shall be agreed with the customer.\n    NOTE The objective is that these data are produced from irradiations performed using particles with sufficient energies to traverse the sensitive part of the device and doses defined through application of the methods defined in the clauses of ECSS-Q-ST-60 relevant to “Radiation hardness”. It is important that the testing conditions are appropriate to the final operating conditions, for example:\n        a. That the electrical and environmental test conditions (e.g. voltage bias, temperature) are equivalent to the expected operating environment for the device, or be such as to give rise to more severe TID effects.\n        b. That the time period over which the radiation dose is delivered is considered when comparing the dose received in the operational environment and under test conditions. Some bipolar devices (e.g. bipolar linear integrated circuits) exhibit greater radiation sensitivity when exposed to ionising radiation at lower TID rates, whilst others such as MOS-based devices suffer lower radiation effects if exposure takes place over a longer time.\n        c. That the irradiation by different radiation types is equivalent. For example, dose enhancement effects can be experienced in the shielded bremsstrahlung field in electron-rich orbits due to presence of high-Z materials close to sensitive volumes, whereas these are not represented in a proton or 60Co irradiation."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","7.7a","Requirement","ECSS-E-ST-10-12_0980058",1,"Created","The dose deposition from the source used to assess material degradation shall be calculated through application of the methods specified in clause 7.5.2. \n    NOTE Refer to ECSS-Q-ST-70-06 and ISO/DIS 15856 for further details."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","8.2a","Requirement","ECSS-E-ST-10-12_0980059",1,"Created","The displacement damage shall be expressed either by:\n    - Displacement damage equivalent particle fluence (DDEF) for mono-energetic spectra, \n        NOTE For example, damage induced as a function of fluence from 10 MeV protons, 1 MeV neutrons or 1 MeV electrons, identified by DDEF(particle, energy, material).\n    - The non-ionising energy loss (NIEL) dose or (total) non-ionising dose ((T)NID), i.e. the energy deposition in a material per unit mass by radiation through displacements.\n        NOTE 1 This is distinctly different to TID for which energy is deposited as ionisation and excitation. \n        NOTE 2 Units of TNID are Gy(material) or rad(material), but for space radiation effects analysis, MeV/g is more commonly used to avoid confusion with TID-related quantities."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","8.3a","Requirement","ECSS-E-ST-10-12_0980060",1,"Created","Displacement damage effects shall be analysed for spacecraft and planetary mission systems to be operated within any of the following radiation environments:\n    1. Trapped proton belts\n        NOTE For example, terrestrial and other planetary belts, such as Jovian.\n    2. Solar protons\n    3. Secondary protons and neutrons\n        NOTE They can be generated in atmospheric showers in the planetary environment or within the spacecraft or planetary-lander structure.\n    4. In close proximity to radioactive or nuclear-energy sources\n        NOTE For example, RTGs generating thermal or fission-spectrum neutrons.\n    5. Trapped electrons (when considering solar cell degradations and opto-electronic devices)."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","8.3b","Requirement","ECSS-E-ST-10-12_0980061",1,"Created","Displacement damage from cosmic ray primary and secondary radiation shall be treated as agreed with the customer.\n    NOTE It is normally neglected for effects in microelectronics, but it can be important for special or novel scientific instruments and sensors. While NIEL increases with atomic number of the projectile, the reducing fluence of ions with Z means that cosmic-ray heavy ion contribution to TNID is not normally significant."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","8.4a","Requirement","ECSS-E-ST-10-12_0980062",1,"Created","If one of the technologies identified in Table 8-1 is used in spacecraft and planetary-mission systems, the potential TNID level and effects shall be analysed.\n    NOTE As specified in Clauses 7, 9 and 10, calculation of total ionising dose effects and single event effects or detector background, including potential synergistic effects of DD and other effects, is also a requirement for many of these components."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","8.5.1a","Requirement","ECSS-E-ST-10-12_0980063",1,"Created","The radiation damage assessment shall use either the DDEF of mono-energetic protons, electrons, or neutrons calculated as specified in clause 8.5.2.1, or the TNID, calculated as specified in clause 8.5.2.2."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","8.5.1b","Requirement","ECSS-E-ST-10-12_0980064",1,"Created","The influence of shielding in attenuating the primary particle environment and modifying its spectrum shall be analysed.\n    NOTE Methods for the related shielding calculation are specified in clause 6.2."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","8.5.1c","Requirement","ECSS-E-ST-10-12_0980065",1,"Created","The influence of secondary protons, electrons and neutrons on displacement damage shall be analysed.\n    NOTE In many cases the analysis can conclude that their contribution is negligible, but in some circumstances secondary protons, electrons and neutrons can have an important contribution."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","8.5.2.1a","Requirement","ECSS-E-ST-10-12_0980066",1,"Created","DDEF shall be calculated from the environmental proton, electron or neutron spectra and the conversion factors for the device type being assessed as follows:\n    1. Divide the TNID from clause 8.5.2.2 by the NIEL value for the considered material and particle species at the energy required.\n        NOTE The reason is that the level of displacement damage observed per unit fluence is highly dependent upon the material and the particle energy and species.\n    2. Calculate the DDEF as a function of equivalent shielding thickness and for each particle (trapped protons and electrons, and solar protons) spectrum estimated for a specified mission.\n    3. Predict the decrease in performance of a component from tests performed on the component at those mono-energetic energies.\n        NOTE Typically 10 MeV proton fluences or 1 MeV electron equivalent fluence is used, these are defined based on NIEL values for the considered material and radiation environment specification. If no valid NIEL values are available in the open literature, they are determined following methodologies presented in [4] or [5]."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","8.5.2.1b","Requirement","ECSS-E-ST-10-12_0980067",1,"Created","The decrease in the component performance shall be calculated from experimental performance test data collected on the component at these mono-energetic energies."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","8.5.2.2a","Requirement","ECSS-E-ST-10-12_0980068",1,"Created","TNID shall be calculated by one of the following procedures:\n    1. If the NIEL as a function of energy, particle type and target material is known, calculate the TNID through the integration over energy of the NIEL function (multiplied by fluence) for each particle species on the target material.\n    2. Otherwise, calculate the NIEL as a function of energy for the material and particle type following a methodology agreed with the customer and calculate the TNID through the integration over energy of the NIEL function (multiplied by fluence) for each particle species on the target material.\n        NOTE Methodologies described by Jun et al or Messenger et al [4] [5] can be used for this purpose."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","8.5.2.2b","Requirement","ECSS-E-ST-10-12_0980069",1,"Created","Conversion from TNID to component parameter degradation shall be obtained by testing the component to different TNID levels."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","8.5.2.2c","Requirement","ECSS-E-ST-10-12_0980070",1,"Created","The same NIEL function shall be used in converting the test particle fluence to the test TNID in requirements 8.5.2.2a and 8.5.2.2b, and the calculation and approach shall be specified."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","8.6a","Requirement","ECSS-E-ST-10-12_0980071",1,"Created","Prediction of component degradation as a function of NIEL shall be performed by one of the following approaches:\n    1. Calculate the degradation from the total TNID damage predicted considering both elastic and inelastic processes, or\n    2. By using experimental degradation data for high energy protons, accepted by the customer.\n        NOTE 1 It is important that the testing conditions are appropriate to the final operating conditions, for example:\n            · That the component test data used in conjunction with radiation damage parameters to predict degradation are based on tests performed with particle species and energy that are representative of the environment, taking account of the appropriate NIEL conversion data.\n            · That contamination of the TNID effects data by TID effects are be minimised and taken into account.\n            · That the particle energies for the tests are sufficient to allow particles to traverse the sensitive part of the device.\n            · For solar cells, that normal incidence data are converted to represent the expected in-flight distribution (normally assumed isotropic - see ECSS-E-ST-10-04) and cover glass shielding effects.\n            · That mono-energetic particle tests are permitted provided there is a consistent one-to-one correspondence between the device degradation and TNID, or if the particle energy chosen for testing leads to worst-case degradation of the device.\n        NOTE 2 For guidelines on predicting component degradation as a function of NIEL, see ECSS-E-HB-10-12 Section 7.3."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.2a","Requirement","ECSS-E-ST-10-12_0980072",1,"Created","Single event effects shall be analysed for spacecraft and planetary-mission systems to be operated within any of the following radiation environments:\n    1. trapped proton belts (terrestrial and other planetary belts, such as Jovian);\n    2. solar protons and heavier ions;\n    3. galactic cosmic-ray protons and heavier ions;"]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.2b","Requirement","ECSS-E-ST-10-12_0980073",1,"Created","The mission environmental specifications shall define all the relevant environments to be analysed.\n    NOTE In some special circumstances, the following environments can also make an important contribution to SEE: \n        a. secondary protons and neutrons, which are generated in atmospheric showers in the planetary environment or within massive spacecraft or planetary-lander structures. \n        b. neutron environment in close proximity to radioactive or nuclear-energy sources, e.g. RTGs generating thermal or fission-spectrum neutrons."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.3a","Requirement","ECSS-E-ST-10-12_0980074",1,"Created","If one of the technologies identified in Table 9-1 is used in spacecraft and planetary-mission systems, the SEE probability and effects shall be analysed.\n    NOTE 1 As specified in Clauses 7, 8 and 10, the susceptibility of many of these components is also analysed for other radiation effects (such as total ionising dose and displacement damage).\n    NOTE 2 As technologies evolve and new phenomena are identified, it can be the case that this table does not fully represent the technologies and effects.\n    NOTE 3 Derating is employed in the RHA programme to ensure that the device operates in a manner so as to be insensitive to SEE effects."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.1.1a","Requirement","ECSS-E-ST-10-12_0980075",1,"Created","When predicting component SEE rates, the following shall be assessed:\n    1. The probability of SEE occurrence for the environments as specified in clause 9.2, using the methods specified in clause 9.4.1.2 to 9.4.1.8.\n        NOTE 1 More information on this method is available in ECSS-E-HB-10-12 Section 8.2.\n        NOTE 2 Total ionising dose induced in semiconductors can increase sensitivity to single event effects. Therefore, potential SEE/TID synergy can be important in special cases, both in estimating single event rate for the operating environment, as well as assessing the suitability of data collected from proton and ion beam irradiations. \n        NOTE 3 In some special cases, single event effect rates have been shown to vary significantly depending upon the angle of incidence of the incident particle, even for protons and neutrons.\n    2. The influence of shielding in attenuating the primary particle environment and modification to its spectrum, as specified in Clause 6.\n        NOTE The effects of the component packaging (as described in Clause 6.3) can be considered. "]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.1.2a","Requirement","ECSS-E-ST-10-12_0980076",1,"Created","The probability of single event transients, upsets, functional interrupts and multiple-cell upsets due to ions heavier than protons shall be determined as follows:\n    1. If the variation of the ion cross-section with LET is known, by using the Integrated RPP (IRPP) approach described in requirements 9.5.2a.1 and 9.5.2a.3.\n    2. Otherwise, using either of the following RPP methods:\n        (a) The incident particle differential LET spectrum, integrated over the integral chord-length distribution in the sensitive volume for which the energy deposition is above that corresponding to the experimentally-determined LET threshold of the device, and using the formulation of “Bradford” specified in requirement 9.5.2a.2(b).\n        (b) The differential chord-length distribution integrated over the incident particle integral LET spectrum, for which the LET corresponds to energy deposition above the experimentally-determined threshold of the device, and using the formulation of: “Bradford” or of “Pickel” or of “Blandford and Adams” specified in requirement 9.5.2a.2(b)."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.1.2b","Requirement","ECSS-E-ST-10-12_0980077",1,"Created","SEFI analysis shall \n    1. assess the range of internal operating modes employed in complex digital devices used by the intended application, and\n    2. use only test data which cover these modes."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.1.3a","Requirement","ECSS-E-ST-10-12_0980078",1,"Created","The probability of single event transients, upsets, functional interrupts and multiple-cell upsets due to protons or neutrons shall be determined as follows:\n    1. If the variation of the cross-section with particle energy is known, \n        (a) Calculate the probability by integration of the incident differential proton or neutron spectrum over the experimentally determined cross-section of the device as specified in clause 9.5.3.\n        (b) If experimental data from ion beam irradiations demonstrate that the threshold for SEU, MCU or SEFI for ions is less than 15 MeV×cm2/mg, agree with the customer if the device can be considered immune to proton and neutron SEE effects.\n            NOTE The immunity to proton/neutron SEE for devices with an LET threshold for ion SEE >15 MeV cm2/mg is an approximation. This assumption becomes inaccurate with the increasing inclusion of high-Z materials that give rise to nuclear reactions. The radiation hardness assurance programme resulting from application of ECSS-Q-ST-60 specifies the approach to be taken in special cases.\n    2. Otherwise, perform the following:\n        (a) determine the SEE rate from calculation of the energy-deposition spectrum from proton-nuclear or neutron-nuclear interactions within the representation of the sensitive volume, and \n        (b) integrate this spectrum with cross-section data from ion-beam irradiations as specified in clause 9.5.3, and\n        (c) analyse potential problems arising from use of the device, along with appropriate margins.\n            NOTE The reason is that this method is not as accurate as direct calculation based on proton data."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.1.3b","Requirement","ECSS-E-ST-10-12_0980079",1,"Created","SEFI analysis shall \n    1. assess the range of internal operating modes employed in complex digital devices used by the intended application, and\n    2. use only test data which cover these modes."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.1.4a","Requirement","ECSS-E-ST-10-12_0980080",1,"Created","For SEL and SESB experimental data shall be used to determine the LET threshold for susceptibility to SEL or SESB."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.1.4b","Requirement","ECSS-E-ST-10-12_0980081",1,"Created","Where experimental data indicate that the normal incidence LET threshold for susceptibility to single event latch-up or single event snapback for ions is ³60 MeV×cm2/mg, it shall be assumed that the device has negligible probability of SEL or SESB respectively to heavy ions, when subjected to the electrical and temperature conditions under which the device is operated in the test and intended application, as specified in clause 9.4.2."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.1.4c","Requirement","ECSS-E-ST-10-12_0980082",1,"Created","For devices with lower thresholds than those specified in requirement 9.4.1.4a, one of the following two methods shall be used:\n    1. Determine the probabilities for SEL and SESB due to heavy ions from the integration of the incident differential ion LET spectrum over the experimentally-determined cross-section of the device, as specified in clause 9.5.2. \n    2. worst case analysis based on experimental data.\n        NOTE Alternative testing methods (laser or proton irradiation), combined with a cross-section equivalent to the device surface can be used with worst case analysis."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.1.4d","Requirement","ECSS-E-ST-10-12_0980083",1,"Created","If a worst-case analysis is performed in accordance with requirement 9.4.1.4c.2, and the probability is unacceptable to the customer, the cross-section shall be determined experimentally."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.1.5a","Requirement","ECSS-E-ST-10-12_0980084",1,"Created","For SEL and SESB experimental data shall be used to determine the LET threshold for susceptibility to SEL or SESB."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.1.5b","Requirement","ECSS-E-ST-10-12_0980085",1,"Created","Where experimental data indicate that the LET threshold for susceptibility to single event latch-up or single event snapback for ions is ³15 MeV⋅cm2/mg, or proton or neutron data indicate that the energy threshold for proton/neutron SEE is ≥150 MeV, it shall be assumed that the device has negligible probability of SEL or SESB respectively for protons and neutrons. When subjected to the electrical and temperature conditions under which the device is operated in the test and intended application, as specified in clause 9.4.2.\n    NOTE 1 It is an assumption that devices with an LET threshold for ions >15 MeV cm2/mg are immune to SEL and SESB. This assumption becomes inaccurate with the increasing inclusion of high-Z materials that give rise to nuclear reactions. The radiation hardness assurance programme resulting from application of ECSS-Q-ST-60 specifies the approach to be taken in special cases.\n    NOTE 2 SEL cross sections can increase by a factor of four between 100 and 200 MeV and by a further factor of 1,5 to 500 MeV."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.1.5c","Requirement","ECSS-E-ST-10-12_0980086",1,"Created","For devices with lower thresholds that the ones specified in requirement 9.4.1.5a, the probabilities for SEL and SESB due to protons or neutrons shall be determined by one of the following methods:\n    1. by integration of the incident differential proton or neutron spectrum over the experimentally determined cross-section of the device, as specified in clause 9.5.3.\n    2. by worst case analysis.\n        NOTE Alternative testing methods (laser irradiation), combined with a cross-section equivalent to the device surface can be used with worst case analyses."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.1.6a","Requirement","ECSS-E-ST-10-12_0980087",1,"Created","For single event gate/dielectric rupture and single event burnout, experimental data shall be used to determine the electrical operational conditions of the device under which neither SEGR nor SEB occurs \n    NOTE ECSS-E-HB-10-12 Section 8.5.8 describes derating and mitigation techniques for defining electrical operational conditions."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.1.6b","Requirement","ECSS-E-ST-10-12_0980088",1,"Created","Where experimental data show that the threshold for single event gate/dielectric rupture or single event burnout in a device for ions is ³60 MeV×cm2/mg, it shall be assumed that the device has negligible probability of SEGR, SEDR or SEB respectively for operation in heavy-ion, proton and neutron fields, when it is subjected to the electrical and temperature conditions under which the device is operated in the test and intended application in accordance with clause 9.4.2."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.1.6c","Requirement","ECSS-E-ST-10-12_0980089",1,"Created","Where experimental data show that the threshold for SEGR, SEDR or SEB for ions is ³15 MeV×cm2/mg, or proton or neutron data indicate that the energy threshold for proton/neutron SEGR, SEDR or SEB is ³ 150 MeV, it shall be assumed that the device has negligible probability of SEGR, SEDR or SEB respectively when operated in either a proton or neutron field when it is subjected to the operating conditions or the test and application."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.1.6d","Requirement","ECSS-E-ST-10-12_0980090",1,"Created","In the case specified in requirement 9.4.1.6c, the device’s susceptibility to heavy-ion induced SEGR, SEDR and SEB shall be analysed."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.1.7a","Requirement","ECSS-E-ST-10-12_0980091",1,"Created","If SET is mitigated by circuit design, the effects of spurious pulses shall be minimized as follows:\n    1. Test the equipment performance under different filter conditions for SET and SED effects by propagating a perturbation signal in the final electrical design of the hardware itself to study its influence at the system level. \n        NOTE This approach is used when there is sufficient access to inject test pulses to the range of circuit nodes, or using a circuit simulation mode.\n    2. Use a circuit simulation model, and verify the accuracy of the different components in the circuit model for propagating large amplitude signals, up to the maximum amplitude expected from the SET/SED.\n        NOTE Typical applied amplitudes and signal durations are provided in ECSS-E-HB-10-12 Section 8.5.9 (Table 9) as a function of semiconductor family type. Note, however, that these are not the only devices to be tested for SET/SED."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.1.7b","Requirement","ECSS-E-ST-10-12_0980092",1,"Created","In case other than requirement 9.4.1.7a, the SET/SED rate shall be predicted using the same methods as for SEU, as specified in clause 9.4.1.2 and 9.4.1.3, including ion or proton test."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.1.8a","Requirement","ECSS-E-ST-10-12_0980093",1,"Created","The probability of single hard errors due to ions shall be determined by integration of the incident particle differential LET spectrum over the experimentally determined cross-section of the device, as a function of LET and angle of incidence."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.1.8b","Requirement","ECSS-E-ST-10-12_0980094",1,"Created","The probability of single hard errors due to protons and neutrons shall be determined by integration of the incident particle differential energy spectrum over the experimentally determined cross-section of the device, as a function of particle energy and angle of incidence.\n    NOTE ECSS-E-HB-10-12 Section 8.7.4 provides a description of SEHE and considerations that can be significant for the test procedure."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.2a","Requirement","ECSS-E-ST-10-12_0980095",1,"Created","Experimental data used to calculate single event rates shall cover a LET range (for heavy-ion induced SEEs) or energy range (for proton and neutron-induced effects) capable to ensure that:\n    1. The lower LET or energy is less than the threshold for the onset of the single event effect.\n        NOTE 1 The lower LET or energy threshold can require extensive testing to determine. For protons it is influenced by packaging, while for neutrons it can be in the region of thermal energies if Boron-10 is present.\n        NOTE 2 Lower LET or energy threshold for the testing is specified in the radiation hardness assurance programme under ECSS-Q-ST-60.\n    2. For heavy ions, the upper LET threshold corresponds either to: \n        (a) the maximum LET expected for the environment, \n        (b) the device LET saturation cross section,\n            NOTE Saturation is defined according to the radiation hardness assurance programme established under ECSS-Q-ST-60.\n        (c) 60 MeV×cm2/mg.\n    3. For nucleons, the maximum energy corresponds either to: \n        (a) the maximum energy for the predicted environment, or \n        (b) the device saturation cross section is in the range.\n            NOTE Saturation is defined according to the radiation hardness assurance programme established under ECSS-Q-ST-60.\n        (c) 150 MeV for all SEE phenomena."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.2b","Requirement","ECSS-E-ST-10-12_0980096",1,"Created","Cross section data shall be from tests where the test particle’s range in the material ensures it is able to penetrate the entire sensitive volume of the device.\n    NOTE The reason is that many modern devices (including power semiconductors) have significant vertical structure and very thick epitaxial layers and sufficient range of the incident test particle is required to adequately penetrate through the entire sensitive volume of the device."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.2c","Requirement","ECSS-E-ST-10-12_0980097",1,"Created","The experimental data used for device conditions shall be either those expected for operational conditions, or such that the experiment provide worse SEE-susceptibility data, as follows:\n    1. For SRAMs and DRAMs, SEU-dependent electrical conditions are voltage, clock frequency and refresh rate.\n    2. For SEL, tests are for the maximum power and maximum temperature conditions expected for space application.\n    3. For SEB, tests correspond to the minimum operating temperature for the application, as this corresponds to maximum SEB susceptibility of the device."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.4.2d","Requirement","ECSS-E-ST-10-12_0980098",1,"Created","For SEL, SEGR, and SEB, the potential inaccuracy of LET cross-section data obtained using obliquely incident heavy-ion beams shall be analysed and the results reported in accordance with the RHA programme established under ECSS-Q-ST-60.\n    NOTE 1 The reason is that the concepts of sensitive volume and effective LET are not strictly valid (see ECSS-E-HB-10-12 Section 8.6.1 to 8.6.3). \n    NOTE 2 SEHE cross-section can be a function of particle species and energy (i.e. not just LET) and angle of incidence (see ECSS-E-HB-10-12 Section 8.7.4). \n    NOTE 3 It is important that the ion track width of the particles used in the irradiations is sufficient to cover a significant fraction of the gate region.\n    NOTE 4 There are synergies between SEHE rates and cumulative dose (TID) as well as microdose effects. "]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.5.1a","Requirement","ECSS-E-ST-10-12_0980099",1,"Created","The assessment of single event effects and the suitability of the proposed hardware and mission design shall be performed as specified in Figure 9-1."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.5.2a","Requirement","ECSS-E-ST-10-12_0980100",1,"Created","Calculation of the ion contribution to SEE rates shall be performed as follows:\n    1. By using the LET spectra for cosmic rays and heavy ions from solar particle events given by the radiation environmental specification, obtain the cross section experimental curve giving at least LET threshold and saturation cross-section, or the Weibull parameters.\n    2. If using RPP approach:\n        (a) Assume that the sensitive volume is a parallelepiped of the same volume as the sensitive one.\n        (b) Calculate the error rate using one of the following formulae:            \n-\tBradford formula:\n \nwith    \n \n-\tPickel formula:\n \n\n-\tBlandford and Adams formula:\n \nwhere:\nA\t= total surface area of the SV;\nl, w and h\t= length, width and height of the SV;\ndF/d(LET) \t= differential ion flux spectrum expressed as a function of LET (shortened to “differential LET spectrum”);\nPCL(>D(LET))\t= integral chord length distribution, i.e. the probability of particles travelling through the sensitive region with a pathlength greater than D;\nLETMin \t= minimum LET to upset the cell (also referred to as the LET threshold);\nLETMax \t= maximum LET of the incident distribution (~105 MeV×cm2/g).\n                  \n    3. If using IRPP approach:\n        (a) Use the real sensitive volume for the integration.\n        (b) Calculate the error rate using the following formula:\n \n\n\nwith  \nwhere:\ndF/d(LET)\t=\tdifferential LET spectrum;\nPCL(>D(LET))\t=\tintegral chord length distribution;\ndsion/d(LET)\t=\tdifferential upset cross section;\nA\t=\ttotal surface area of the sensitive volume;\nS\t=\tsurface area of the sensitive volume in the plane of the semiconductor die;\nl, w and h\t=\tlength, width and height of the sensitive volume;\nDMax\t=\tmaximum length that can be encountered in the SV;\nLETMax\t=\tmaximum LET of the LET spectrum;\nLETi,Min\t=\tlower bin limit in the differential upset cross section dsion/d(LET);\nLETi,Max \t=\tupper bin limit in the differential upset cross section dsion/d(LET).\n            NOTE For a detailed discussion of the RPP and IRPP approaches, see ECSS-E-HB-10-12 Sections 8.5.2 to 8.5.4. References can be found in [6], [7], [8], [9] and [10]."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.5.3a","Requirement","ECSS-E-ST-10-12_0980101",1,"Created","Except in the case specified in requirement 9.5.3b, the proton or neutron contribution to error rate shall be calculated as follows:\n    1. Using the integral or differential energy spectra for protons or neutrons specified in the radiation environment specification, obtain:\n        (a) the cross-section experimental curve giving saturation, and \n        (b) two other cross section/energy points in the following ranges:\n            • For protons, in the energy range 10 MeV - 200 MeV.\n            • For neutrons, from thermal energies to 200 MeV.\n    2. Use one of the following formulas to calculate the SEE rates:\n        • From the environment proton or neutron fluxes and SEE cross sections:\n\to\tFrom the environment proton or neutron fluxes and SEE cross sections:\t\n\t\t \n\to\tBy considering the dependence of the angle of incidence, but assuming not azimuth angle dependence:\t\n\t\t \n\to\tBy simplifying the previous formula, by \n\t\t-\tdefining smax(E) as the value of s(E,q) at the angle q where the cross section maximises for that energy, and\n\t\t-\tIf the incident proton or neutron flux is anisotropic (and therefore cannot be approximated to an isotropic flux), approximate dF/dE to the angle-averaged incident flux if used in conjunction with the maximum cross section data, smax(E).\nwhere:\ndF/dE\t=\tdifferential proton or neutron flux spectrum as a function of energy;\nEMin\t=\tminimum energy of the differential energy neutron spectrum;\nEMax\t=\tmaximum energy of the differential energy spectrum;\nσnucleon(E) \t=\tproton or neutron SEE cross section as a function of energy.\n"]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","9.5.3b","Permission","ECSS-E-ST-10-12_0980166",1,"Created","If the heavy ion cross-section experimental curve exist, the proton or neutron contribution to error rate may be calculated as follows: \n    1. Obtain the proton cross-section curve by simulation and correlation with experimental data, using a simulation tool agreed with the customer.\n    2. Using the integral or differential energy spectra for protons or neutrons specified in the radiation environment specification, obtain two other cross section/energy points in the following ranges:\n        • For protons, in the energy range 10 MeV - 200 MeV.\n        • For neutrons, from thermal energies to 200 MeV.\n    3. Calculate the SSE rate, from ion-beam irradiations, by using the following formula:\n\t \n\nwhere:\n dF/dE, : EMin, EMax, and σnucleon(E) have the same meaning as in 9.5.3a2, and: \ndP/de(E,e)\t=\tdifferential energy deposition spectrum for protons/neutrons of energy E depositing energy e within the sensitive volume;\neC\t=\tcritical or threshold energy deposition for inducing SEE;\neMax\t=\tmaximum energy deposition defined for energy deposition spectrum;\nσion(LET) \t=\tSEE cross section for ions as a function of LET for normally incident ions;\nh\t=\theight of sensitive volume;\nr\t=\tmass density of semiconductor;\nssample\t=\tarea of cell sampled by proton/neutron simulation to obtain energy deposition spectrum.\n\n        NOTE Rational and discussion on the calculation of SEE rates of protons and neutrons can be found in Section 8.5.5 to 8.5.7."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.2a","Requirement","ECSS-E-ST-10-12_0980103",1,"Created","Radiation-induced backgrounds shall be analysed for spacecraft and planetary-missions where there is the potential for energy deposition events within the bandwidth of the sensor from the radiation environment, whether from a single event or accumulation of interaction of events. \n    NOTE Example of accumulation is from pile-up of pulses within the detector time-resolution, the cumulative effect of which exceeds the event detection threshold and results in a false event."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.2b","Requirement","ECSS-E-ST-10-12_0980104",1,"Created","The analysis specified in requirement 10.2a shall include all components of the environment that have the potential to affect the instrument, including secondary particles from the spacecraft structure and local planetary bodies, and man-made radiation sources \n    NOTE Example of man-made radiation sources are radioactive calibration sources, and radio-isotope thermoelectric generators."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.3a","Requirement","ECSS-E-ST-10-12_0980105",1,"Created","If one of the technologies or instruments identified in Table 10-1 is used in spacecraft or planetary-mission systems, the potential radiation-induced background effects shall analysed."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.3b","Requirement","ECSS-E-ST-10-12_0980106",1,"Created","The mechanisms shall be analysed by which the energetic radiation environment can deposit energy in the instrument so as to register as a sensor event. \n    NOTE The reason is that spacecraft scientific payloads are often unique."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.3c","Requirement","ECSS-E-ST-10-12_0980107",1,"Created","The analysis specified in requirement 10.3b shall include:\n    1. Events from prompt ionisation by primary particles and all prompt secondaries \n        NOTE For example, X-ray fluorescence.\n    2. The potential “pile-up” of such ionising events, within the temporal-resolution of the sensor, which results in higher-than-expected energy deposition.\n    3. Delayed ionisation effects from induced radioactivity.\n        NOTE As specified in Clauses 7, 8 and 9, calculation of susceptibility to other radiation effects (total ionising dose, displacement damage, and single event effects) is also normative."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.4.1a","Requirement","ECSS-E-ST-10-12_0980108",1,"Created","Radiation shielding calculations shall be performed to determine the radiation environment at the instrument after passing through the spacecraft structure. "]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.4.1b","Requirement","ECSS-E-ST-10-12_0980109",1,"Created","Background effects in instruments shall be analysed using:\n    1. calculations or simulations of the energy-deposition processes in sensitive volumes, or\n    2. results from particle accelerator irradiations of the instrument or its sensitive components, or\n    3. a combination of both of the requirements 10.4.1b.1 and 10.4.1b.2."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.4.1c","Requirement","ECSS-E-ST-10-12_0980110",1,"Created","Where experimental results from component tests are used, or simulations based on components of the instrument, one of the following shall be performed:\n    1. shielding calculations for the instrument, to determine the incident particle spectrum on the sensitive volume(s) of the instrument, or \n    2. an analysis demonstrating that instrument structure has a negligible perturbing effect on the radiation field."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.4.1d","Requirement","ECSS-E-ST-10-12_0980111",1,"Created","Where grazing-incidence mirrors are used, the calculation of the radiation environment at the sensitive volumes of the instrument shall include the effects of Firsov scattering and shallow angle multiple scattering of protons in the grazing-incidence mirrors.\n    NOTE See ECSS-E-HB-10-12 Section 9.4, for the reasons for including Firsov scattering in the simulation."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.4.2a","Requirement","ECSS-E-ST-10-12_0980112",1,"Created","The energy deposition spectrum by direct ionisation shall be calculated by one of the following methods:\n    1. By using the formula of Clause 10.4.9.1, if both of the following conditions are met:\n        (a) the sensitive volume of the sensor is so small that the incident particle spectrum changes by less than 10% in either intensity or energy after passing through the volume;\n        (b) the pathlength distribution changes by less than 10% as a result of multiple scattering.\n    2. By a radiation transport simulation agreed with the customer.\n        NOTE For guidelines, see ECSS-E-HB-10-12 Section 5.7."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.4.2b","Requirement","ECSS-E-ST-10-12_0980113",1,"Created","If method specified in requirement 10.4.2a.1 is used, the following shall be performed:\n    1. An estimation of the combined effects of the maximum change in energy, intensity and pathlength on the energy deposition, and \n    2. A demonstration that the error produced is within the accepted margins defined for the project."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.4.3a","Requirement","ECSS-E-ST-10-12_0980114",1,"Created","Prediction of energy deposition spectra initiated by nuclear interaction events shall be performed by a method agreed with the customer.\n    NOTE Prediction of energy deposition spectra initiated by nuclear interactions event are usually performed using detailed radiation transport simulations (see ECSS-E-HB-10-12 Section 5.7). However, where simplifications in the interactions and energy deposition processes permit, simplified analytical solutions are applied, provided the combined effects of the approximations produce an error within the accepted margins defined for the project."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.4.4a","Requirement","ECSS-E-ST-10-12_0980115",1,"Created","Nuclear interaction rates in the sensitive volume and surrounding materials (the radioactive decay products from which can affect the sensitive volume) shall be calculated by one of the following methods:\n    1. By using the formula of Clause 10.4.9.2 if all of the following conditions are met:\n        (a) the sensitive volume of the sensor and surrounding material producing background in the sensor are so small that the incident particle spectrum changes by less than 10% in either intensity of energy after passing through the volume;\n        (b) the pathlength distribution in the sensitive volume and surrounding material changes by less than 10% as a result of multiple scattering;\n        (c) the probability of secondary nuclear interactions is 10 times lower than the primary interaction rate.\n    2. By a radiation transport simulation agreed with the customer.\n        NOTE For guidelines, see ECSS-E-HB-10-12 Section 5.7."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.4.4b","Requirement","ECSS-E-ST-10-12_0980116",1,"Created","If method specified in requirement 10.4.4a.1 is used, the following shall be performed:\n    1. An estimation of the combined effects of the maximum change in energy, intensity and pathlength, and the influence of secondaries on the energy deposition, and \n    2. A demonstration that the error produced is within the accepted margins defined for the project. "]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.4.4c","Requirement","ECSS-E-ST-10-12_0980117",1,"Created","The nuclear interaction rate shall be convolved with relevant response function spectra to radioactive decay in the sensitive volume and surrounding materials, to determine the background count rate in the sensor."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.4.5a","Requirement","ECSS-E-ST-10-12_0980118",1,"Created","The analysis for the prediction of fluorescent X-ray interactions shall include the induced continuum and discrete X-ray emission spectrum from materials surrounding the X-ray detector."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.4.6a","Requirement","ECSS-E-ST-10-12_0980119",1,"Created","The method used for predicting the fluorescence or Cerenkov radiation production shall either:\n    - use a radiation transport calculation that includes Cerenkov and fluorescence physics models and the instrument shielding geometry, or \n    - use a simplified method capable to demonstrate that the level of error in the prediction is within the accepted margins defined for the project."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.4.6b","Requirement","ECSS-E-ST-10-12_0980120",1,"Created","The prediction shall assess the effects of:\n    1. Direct ionisation of the cathode or dynode of a PMT by a particle, or direct ionisation of the walls of a MCP, in either case producing secondary electrons.\n    2. Scintillation of optical components of the PMT/MCP.\n    3. Cerenkov radiation induced in any optical components of the instrument from particles above the Cerenkov threshold."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.4.7a","Requirement","ECSS-E-ST-10-12_0980121",1,"Created","The method adopted for predicting the influence of the radiation environment on gravity-wave interferometric experiments shall be agreed with the customer.\n    NOTE The method adopted for predicting the influence of the radiation environment on gravity-wave interferometric experiments is normally based on a detailed radiation transport calculation, or if a simplified approach is used, the level of error in the prediction is be estimated in order to ensure that it is within the accepted margins defined for the project."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.4.7b","Requirement","ECSS-E-ST-10-12_0980122",1,"Created","The prediction shall be used to assess the noise introduced into the instrument as a result of the incident radiation:\n    1. changing the charge of the free-floating test mass;\n    2. acting as a source of energy to change the thermal conditions of the cryogenically cooled test mass;\n    3. changing the critical temperature of superconducting materials."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.4.8a","Requirement","ECSS-E-ST-10-12_0980123",1,"Created","Experimental data from irradiations shall be used to validate prediction techniques."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.4.8b","Requirement","ECSS-E-ST-10-12_0980124",1,"Created","If experimental data are used in place of elements of the prediction process, the parameter-space covered by experiment shall ensure that the data can be interpolated to operational environment conditions within the error limits specified by the project.\n    NOTE 1 This is especially important in assessing the response of the instrument to the local radiation environment.\n    NOTE 2 Examples of parameter space covered by the experiment are incident particle species and energy, angle of incidence, flux (to allow for effects of pulse pile-up)."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.4.9.1a","Requirement","ECSS-E-ST-10-12_0980125",1,"Created","Under the conditions specified in requirement 10.4.2a.1, the energy deposition spectrum from direct ionization shall be calculated by using one of the following formulas:\n    1. From direct ionization, by one of the following formulas:\n        (a) Detailed calculation:\n\t \n        (b) Approximated calculation:\n\t \n\twhere\n\tdY/de(e)\t= energy deposition rate spectrum;\n\tA\t= total surface area of the SV or detector;\n\tdF/dE(E)\t= differential incident particle flux spectrum expressed as a function of energy, E;\n\tdPCL/dD(D)\t= differential chord length distribution through the sensitive volume for an isotropic distribution;\n\tdE/dx(E)\t= stopping power for particles of energy E;\n\tEmin\t= minimum energy for the incident particle spectrum;\n\tEmax\t= maximum energy of the incident particle spectrum.\n\tNOTE This expression assumes the incident particle spectrum on the detector is or can be approximated to a isotropic angular distribution. Furthermore, it is assumed that the change in the stopping power of the particle through the sensitive volume and any multiple scattering can be neglected.\n    2. For nucleon-nuclear collision-induced energy, by one of the following methods:\n        (a) If the dimensions of the detector volume are 10 times (or more) smaller than the ranges and mean-free paths of the incident particles, by using the following formula: \n \nwhere:\ndY/de(e), A, dF/dE(E), dPCL/dD(D), dE/dx(E), Emin, and Emax have the same meaning as in Clause 10.4.9.11, and:\nM\t=\tmass of sensitive volume;\nNA\t=\tAvogadro’s constant;\nW\t=\tatomic or molecular mass of the material making up the detector;\ns(E)\t=\tnuclear-interaction cross-section for the material as a whole due to incident particles of energy E;\ndP/de(E,e)\t=\tenergy deposition rate spectrum (or response function) for incident particles of energy E, and energy deposition, e .\n\n        (b) Otherwise, by applying radiation simulation tools agreed with the customer.\n            NOTE 1 Examples of such tools are Geant4, MCNPX, and FLUKA. More examples can be found in Table 2 of ECSS-E-HB-10-12.\n            NOTE 2 For a rational and detailed discussion on energy deposition spectrum from direct ionization calculation and nucleon-nuclear interactions, see ECSS-E-HB-10-12, Section 9.2."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","10.4.9.2a","Requirement","ECSS-E-ST-10-12_0980126",1,"Created","Under the conditions specified in requirement 10.4.4a.1, the nuclear interaction rates in the sensitive volume and surrounding material shall be calculated by the following formula:\n \nwhere:\nRi(t)\t= production rate for nuclide species i at time t;\nM\t= mass of detector;\nNA \t= Avogadro’s constant;\nW\t= atomic or molecular mass of the material making up the detector;\ndFj/dE(E,t)\t= differential incident flux spectrum expressed as a function of energy, E and time, t for particle species j (these are both primary and secondary particles);\nsj®i(E)\t= nuclear-interaction cross-section for the production of nuclide i in the detector material due to incident particle species j of energy E;\nEj,min\t= minimum energy for the incident particle spectrum, j;\nEj,max\t= maximum energy of the incident particle spectrum j.\n\n    NOTE For a rational and detailed description, see ECSS-E-HB-10-12, Section 9.5."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.2.1a","Requirement","ECSS-E-ST-10-12_0980127",1,"Created","The following basic parameters shall be used to measure the radiation environment:\n    1. The absorbed dose, D\n    2. The air kerma, K, \n    3. The fluence, F, and \n    4. The linear energy transfer, LET."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.2.2.1a","Requirement","ECSS-E-ST-10-12_0980128",1,"Created","The following protection quantities shall be used when relating the basic physical parameters to biological systems:\n    1. The mean organ absorbed dose, DT\n    2. The relative biological effectiveness, RBE\n    3. The radiation weighting factor, wR\n    4. The organ equivalent dose, HT\n    5. The tissue weighting factor, wT, and \n    6. The effective dose, E.\n        NOTE 1 Protection quantities are defined by the International Commission on Radiobiological Protection (ICRP).\n        NOTE 2 The mean organ dose, organ equivalent dose, and effective dose are not directly measurable, but are essential for assessing risk due to a radiation environment."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.2.2.2a","Requirement","ECSS-E-ST-10-12_0980129",1,"Created","The values of the radiation weighting factor shall be as specified in Table 11-1."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.2.2.2b","Requirement","ECSS-E-ST-10-12_0980130",1,"Created","Values for the radiation weighting factor of particles not specified in Table 11 shall be derived by dividing the ambient dose equivalent for the particle H*(10) by the dose at 10 mm depth in the ICRU sphere [12].\n    NOTE 1 The radiation weighting factor, , accounts for the different levels of biological effects resulting from different particle types, although they can produce the same mean organ dose. For further discussion on  see ECSS-E-HB-10-12 Section 10.2.2.\n    NOTE 2 The values in Table 11-1 are from ICRP-60 [11], and are defined and maintained by the ICRP. The users are encouraged to consult the ICRP for the more recent updates."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.2.2.3a","Requirement","ECSS-E-ST-10-12_0980131",1,"Created","The values of the tissue weighting factor shall be as specified in Table 11-2.\n    NOTE 1 The tissue weighting factor takes into account the variability in sensitivity of different organs and tissue subject to the same equivalent dose.\n    NOTE 2 The values in Table 11-2 are from ICRP Publication 60 Table A-3 [11] and are defined and maintained by the ICRP. The users are encouraged to consult the ICRP for the more recent updates."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.2.3.1a","Requirement","ECSS-E-ST-10-12_0980132",1,"Created","The following operational quantities shall be used for the assessment of radiation exposure:\n    1. the ambient dose equivalent, H*(d)\n    2. the directional dose equivalent, H'(d,W)\n    3. the personal dose equivalent, HP\n    4. the quality factor, Q\n        NOTE Operational quantities are measurable. They are defined by the International Commission on Radiation Units and Measurements (ICRU) with the aim of never underestimating the relevant protection quantities, in particular the effective dose, E, under conventional normally-occurring exposure conditions. "]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.2.3.2a","Requirement","ECSS-E-ST-10-12_0980133",1,"Created","The values of the quality factors given in Equation (3) shall be used.\n \t (3)\n\n    NOTE These values, related to the unrestricted LET in water, correspond to the ones given by equation below, which is established by ICRP-60 [11]."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.3a","Requirement","ECSS-E-ST-10-12_0980134",1,"Created","Radiobiological effects resulting from the following environments shall be analysed for all manned missions:\n    1. trapped proton and electron belts (terrestrial and other planetary belts);\n    2. solar protons and ions;\n    3. cosmic ray protons and heavier nuclei;\n    4. bremsstrahlung produced as secondaries from electrons;\n    5. secondary protons, neutrons and other nuclear fragments which can be generated in atmospheric showers in the planetary environment or within the spacecraft or planetary-habitat structure, including the body itself. \n        NOTE This contribution is particularly important for cosmic-ray induced secondaries.\n    6. emmisions from radioactive or nuclear-energy sources on the spacecraft.\n        NOTE For example, RTGs generating g-ray and neutron radiation."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.4a","Requirement","ECSS-E-ST-10-12_0980135",1,"Created","The project shall establish the radiation protection limits to be applied to the mission.\n    NOTE These limits are established based on the policies and standards defined by the space agency for manned space flight (see ECSS-E-HB-10-12 Section 10.4, and ECSS-E-ST-10-11). Where there is more than one space agency involved, the radiation protection limits to be adopted by the project are normally agreed through consensus (e.g. through a working group of radiation effects experts from the different partner agencies)."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.4b","Requirement","ECSS-E-ST-10-12_0980136",1,"Created","The radiation protection limits shall be defined in terms of the protection quantities in Clause 11.2.2 and the operational quantities in Clause 11.2.3. \n    NOTE These limits can vary between different space agencies."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.4c","Requirement","ECSS-E-ST-10-12_0980137",1,"Created","Synergistic effects between radiobiological damage and other environmental stressors and the radiation protection limits specified in 11.4a shall be analysed.\n    NOTE 1 Example of such environmental stressors are microgravity, vibration, acceleration, and hypoxia\n    NOTE 2 For guidelines on the influence of spaceflight environment, see ECSS-E-HB-10-12 Section 10.5.7."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.4d","Requirement","ECSS-E-ST-10-12_0980138",1,"Created","The quality factors, radiation weighting factors and tissue weighting factors identified in Table 11-1, Table 11-2 and equation (3), shall be used to determine dose equivalent, organ equivalent dose and effective dose.\n    NOTE It is the responsibility of the project manager to perform the trade-off between spacecraft and mission design and operation, and their effects on predicted crew exposure, in order to:\n        · achieve the defined protection limits, and\n        · ensure radiation protection is managed according to the ALARA (as low as reasonably achievable) principle."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.5a","Requirement","ECSS-E-ST-10-12_0980139",1,"Created","A radiobiological risk assessment shall be performed by comparing the protection and operational quantities calculated according to the definitions in Clause 11.2 with the protection limits defined for the project in accordance with requirement 11.4a."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.5b","Requirement","ECSS-E-ST-10-12_0980140",1,"Created","When calculating the protection and operational quantities as specified in requirement 11.5a, the influence of shielding in attenuating the primary particle environment and modification to its spectrum at the location of the astronaut shall be evaluated as follows:\n    1. Perform initial calculations as specified in Clause 6.2.2 to assess the influence of shielding for worst-case shielding, environment and secondary production. \n    2. If these indicate that the protection limits are exceeded, perform more detailed calculations using a detailed sector shielding calculation or Monte-Carlo analysis, calculation, as specified in Clauses 6.2.3 and 6.2.4, respectively. "]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.5c","Requirement","ECSS-E-ST-10-12_0980141",1,"Created","The evaluation specified in requirement 11.5b shall include the potential variations in radiation exposure as a function of shielding material and its configuration."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.5d","Requirement","ECSS-E-ST-10-12_0980142",1,"Created","Scaling to the equivalent areal mass shall not be performed, unless an analysis is performed that demonstrates that the scaling provides an overestimate of the severity of the environment."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.5e","Requirement","ECSS-E-ST-10-12_0980143",1,"Created","The minimum shielding requirements shall be specified for each mission phase.\n    NOTE The reason is that the shielding issues depend on the mission phase scenario and the associated crew activities within the spacecraft habitats, lunar or planetary habitats, or extra-vehicular activities."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.5f","Requirement","ECSS-E-ST-10-12_0980144",1,"Created","The crew exposure shall be assessed for all the following:\n    1. the nominal environment, \n    2. energetic solar particle events,\n    3. radiation belt passages, and\n    4. conditions where the 30-day radiation environment exceeds the nominal environment by a factor of 5. \n        NOTE This is to account for anomalous environmental changes that can affect the 30-day dose limits."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.5g","Requirement","ECSS-E-ST-10-12_0980145",1,"Created","The linear, no threshold (LNT) hypothesis shall be applied extrapolating high-dose-rate data in order to quantify the risk of radiobiological effects.\n    NOTE For long-term missions the doses are likely to attain values where extrapolation can be replaced by a look up into epidemiological data."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.5h","Requirement","ECSS-E-ST-10-12_0980146",1,"Created","If shielding simulations are performed which include self-shielding, the simulation shall include the variations in a build-up of high LET particles, including the nuclear interactions (“star” events) of these particles."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.5i","Requirement","ECSS-E-ST-10-12_0980147",1,"Created","Self-shielding shall be included for simulations where the shielding afforded is less than provided by the self shielding.\n    NOTE For example, astronauts during an EVA."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.5j","Requirement","ECSS-E-ST-10-12_0980148",1,"Created","For simulation of the effects of self-shielding, secondary radiation generated within an organ shall not be included in the calculation of the equivalent dose to that organ.\n    NOTE 1 The reason is that radiation weighting factors already include secondary particle contribution.\n    NOTE 2 For extremely densely ionising radiation like HZE (high mass and energy) particles and nuclear disintegration stars the concept of absorbed dose can break down and has therefore become inapplicable, but not having better concepts it is the only one used to calculate effective dose or dose equivalent."]
["ECSS-E-ST-10-12C","ECSS - Current v1.0","11.6a","Requirement","ECSS-E-ST-10-12_0980149",1,"Created","Analysis of the uncertainties in the exposure calculation shall incorporate the uncertainties in the source data identified in Table 11-3 (from the atomic bomb data) and Table 11-4 (from the space radiation field). \n    NOTE 1 The uncertainties in risk estimates have been evaluated in detail in ‘NCRP 1997’ [14]. The risk estimates are presented in a distribution that ranges from 1,15 to 8,1x10-2 Sv-1 for the 90 % confidence interval for the nominal value of 4 % per Sv for an adult US population.\n    NOTE 2 Uncertainties also arise from systematic errors (and potentially statistical errors in the case of Monte Carlo simulation) in the radiation shielding calculation - see ECSS-E-HB-10-12, Section 5.8."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.1a","Requirement","ECSS-E-ST-10-24_1290001",1,"Unchanged","An interface management plan shall be established by the interface responsible to describe the Interface Management approach."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.1b","Permission","ECSS-E-ST-10-24_1290073",1,"Unchanged","The interface management plan may be part of the Project Management Plan (ECSS-M-ST-10 Annex A) or part of the System Engineering Plan (ECSS-E-ST-10 Annex D) or a self-standing document, subject to agreement between the interface responsible and its customer.","NOTE \tThe chosen approach depends on the complexity of the project.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.1c","Requirement","ECSS-E-ST-10-24_1290002",1,"Unchanged","The interface management plan shall define the applicability of this standard. "]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.1d","Requirement","ECSS-E-ST-10-24_1290003",1,"Unchanged","The interface management plan shall define tailoring and adaptation of this standard to Project needs and life cycle.","NOTE \tWhile interface management steps are mandatory, the way in which each step is documented can be tailored according to the rules defined in each clause of this standard.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.1e","Requirement","ECSS-E-ST-10-24_1290004",1,"Unchanged","The interface management plan shall define at least the:\n1.\tapplicability domain,\n2.\tmanagement logic, \n3.\tresponsibility and approval authorities, \n4.\tinterface consolidation approach and life cycle, \n5.\tschedule,\n6.\tdocumentation tree,\n7.\tinternal documentation organization approach (contractual, discipline or product decomposition), and\n8.\tchange management approach."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.2a","Requirement","ECSS-E-ST-10-24_1290005",1,"Unchanged","The supplier shall list all the interfaces involved within his product."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.2b","Requirement","ECSS-E-ST-10-24_1290006",1,"Unchanged","The interfaces list of 5.2a shall include:\n1.\tall interfaces crossing contractual boundaries, \n2.\tany interface identified by the customer.","NOTE \tCriteria used by the customer to identify additional interface to be managed within the supplier product, are for example reuse, technical risk, criticality.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.2c","Requirement","ECSS-E-ST-10-24_1290007",1,"Unchanged","For each interface identified in the list of 5.2b, the following shall be provided:\n1.\tinvolved interface ends, \n2.\tcontractual responsibilities, \n3.\ttechnical documentation and their version specifying and defining the interface. "]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.2d","Requirement","ECSS-E-ST-10-24_1290008",1,"Unchanged","The information in the list of 5.2b, shall be updated and distributed to the involved actors every time that any applicable document is updated or a baseline established.","NOTE \tThis interface information can be in the form of an Interface Identification Document (IID), as defined in Annex D.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.3a","Requirement","ECSS-E-ST-10-24_1290009",1,"Unchanged","The customer shall define the interface requirements in conformance with the IRD DRD in Annex A.","NOTE\t1\tInformation regarding the expected delivery of the document for each project review is provided in Annex A of ECSS-E-ST-10.\nNOTE\t2\tAs indicated in DRD Annex A, the IRD content can be merged together with Technical Specification.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.3b","Requirement","ECSS-E-ST-10-24_1290010",1,"Unchanged","The complete set of interface requirements shall be specified by the customer prior to the start of the supplier’s contract."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.3c","Requirement","ECSS-E-ST-10-24_1290011",1,"Unchanged","The precedence of the IRD with respect to other project documents shall be defined."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.3d","Requirement","ECSS-E-ST-10-24_1290012",1,"Unchanged","Suppliers shall provide their compliance status to the interface requirements."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.3e","Requirement","ECSS-E-ST-10-24_1290013",1,"Unchanged","Nonconformance to interface requirements shall be treated as major NCR in accordance with the NCR process as defined in ECSS-Q-ST-10-09."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.4a","Requirement","ECSS-E-ST-10-24_1290014",1,"Unchanged","The interface responsible shall perform the following tasks:\n1.\tcollection of interface end data from involved actors;\n2.\tsharing of interface data with involved actors;\n3.\tcoordination of the interface definition compliance with respect to interface requirements of clause 5.3;\n4.\tchecking of interface end data from suppliers, for:\n(a)\tconsistency,\n(b)\tmutual compatibility.\n5.\tbaselining of the interface definition;\n6.\tcommunicating interface changes among involved actors."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.4b","Requirement","ECSS-E-ST-10-24_1290015",1,"Unchanged","The actors shall be responsible of the interface end, by means of:\n1.\tcontributing to interface definition, providing an IDD, an one-end ICD, or relevant technical design data, in conformance with the IDD DRD in Annex C;\n2.\tsupporting the iterations of the interface definition, in order to achieve an agreed baseline;\n3.\tensuring interface end compatibility with respect to:\n(a)\tinterface requirement,\n(b)\tinterface definition."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.4c","Requirement","ECSS-E-ST-10-24_1290016",1,"Unchanged","For each identified and specified interface, the interface responsible with the contribution of the involved actors shall define interface characteristics in terms of:\n1.\tinterface plane definition;\n2.\tinterface behaviour identification;\n3.\tdata affecting the interface definition.","NOTE\t1\tExamples for 5.4c.1 are: mounting surface (between hardware products), Application Program Interface (between software products), communication network (between data systems).\nNOTE\t2\tExamples for 5.4c.2 are: static, dynamic, nominal/off nominal, \"state machine\".\nNOTE\t3\tExamples for 5.4c.3 are: dimensions, tolerances, coordinates, voltage, data format, temperature, load, heat flow, material, surface treatment, external standard reference.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.4d","Requirement","ECSS-E-ST-10-24_1290017",1,"Unchanged","To define the interfaces, the interface responsible shall provide an ICD in conformance with the ICD DRD in Annex B."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.4e","Requirement","ECSS-E-ST-10-24_1290018",1,"Unchanged","The ICD shall be put under configuration control prior to interface end suppliers PDR."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.4f","Requirement","ECSS-E-ST-10-24_1290019",1,"Unchanged","Nonconformance to ICD shall be treated as major NCR in accordance with the NCR process as defined in ECSS-Q-ST-10-09."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.5a","Requirement","ECSS-E-ST-10-24_1290020",1,"Unchanged","Modifications to an ICD shall be managed in conformance with ECSS-M-ST-40, adapting the process as defined in Clause 4.2.6."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.5b","Requirement","ECSS-E-ST-10-24_1290021",1,"Unchanged","The interface responsible shall communicate the approval or non-approval of an interface definition change with a rationale to all the actors."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.5c","Requirement","ECSS-E-ST-10-24_1290022",1,"Unchanged","The interface definition change shall be managed through a CR."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.5d","Requirement","ECSS-E-ST-10-24_1290023",1,"Unchanged","The CR shall be agreed and signed by each of the actors and by the interface responsible before it becomes applicable for implementation."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.5e","Requirement","ECSS-E-ST-10-24_1290024",1,"Unchanged","The interface definition agreed change shall be listed, until relevant CR content is incorporated in a new version of a baseline ICD.","NOTE \tInterface definition agreed change is as documented in the agreed CR.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.5f","Requirement","ECSS-E-ST-10-24_1290025",1,"Unchanged","The ICD shall be consolidated to the frozen status, prior to the CDR of the first product involved in the interface."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.5g","Requirement","ECSS-E-ST-10-24_1290026",1,"Unchanged","The frozen ICD shall be approved (signed) by all involved parties. "]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.6a","Requirement","ECSS-E-ST-10-24_1290027",1,"Unchanged","Interface requirement verification shall be performed in conformance with ECSS-E-ST-10-02."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.6b","Requirement","ECSS-E-ST-10-24_1290028",1,"Unchanged","The approach for verifying interfaces shall be defined by the customer, identifying the type and method of verification activity.","NOTE \tOne of the following types of verification, or a combination:\n·\tStand-alone verification activity under supplier responsibility.\n·\tJoint verification activity, performed under customer responsibility with supplier support.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.6c","Requirement","ECSS-E-ST-10-24_1290029",1,"Unchanged","The customer shall define the supplier support needed for any joint verification activity."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.6d","Requirement","ECSS-E-ST-10-24_1290030",1,"Unchanged","Any stand-alone verification shall be completed successfully prior to the joint verification applicable to the same interface."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.6e","Requirement","ECSS-E-ST-10-24_1290031",1,"Unchanged","The customer and the suppliers shall agree whether interface validation is included or not."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.6f","Requirement","ECSS-E-ST-10-24_1290032",1,"Unchanged","If validation is included, the customer and suppliers shall agree on the interface validation approach."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.7a","Requirement","ECSS-E-ST-10-24_1290077",1,"Created","A manufacturer of an equipment shall provide the equipment EICD, MICD, TICD for all equipment models that will be delivered and connected to other equipment for higher level verification.","NOTE \tEquipment models are EM, EQM, PFM, FM.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.7b","Requirement","ECSS-E-ST-10-24_1290078",1,"Created","All equipment models that are delivered and used at system level in a non-flight satellite model or in a non-flight instrument subsystem model shall be covered in the relevant EICD, MICD, TICD.","NOTE\t1\tA non-flight satellite model is for example the Satellite Electrical Functional Model.\nNOTE\t2\tA non-flight instrument subsystem models are for example EM, EQM.\nNOTE\t3\tThe EICD can be relevant to all equipment models (EM, EQM, PFM, FM) or to each one of them.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.7c","Requirement","ECSS-E-ST-10-24_1290079",1,"Created","Either the EICD or the MICD of an equipment shall include the drawings or pictures of the equipment models with all connectors’ location, connectors’ types, and names/references."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.7d","Requirement","ECSS-E-ST-10-24_1290080",1,"Created","The equipment, subsystem and system EICD, MICD, TICD shall contain or refer to the document containing the list of RFDs of interfaces not respecting the applicable interface requirements.","NOTE \tThe applicable reference document is the latest available issue at any time.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.7e","Requirement","ECSS-E-ST-10-24_1290081",1,"Created","The same unique naming conventions shall be used for space segment equipment, subsystem and element.","NOTE \tThe responsibility of the naming convention lies with the element integrator, who delegates the compliance to equipment and subsystem responsible entities.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.1a","Requirement","ECSS-E-ST-10-24_1290082",1,"Created","The equipment EICD shall contain the overall circuit diagram of the space segment equipment including component values or provide the reference to the applicable document containing such information."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.1b","Requirement","ECSS-E-ST-10-24_1290083",1,"Created","The equipment EICD shall contain the detailed diagram of all electrical interfaces including the part types, the parts references and the part values."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.1c","Permission","ECSS-E-ST-10-24_1290084",1,"Created","The parts references mentioned in requirement ‎5.8.1b may be provided in a separate document in case of confidential information.","NOTE \tThe separate document is for example a Declared Component List.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.1d","Requirement","ECSS-E-ST-10-24_1290085",1,"Created","The equipment EICD shall include the relevant grounding diagram or provide the reference to the applicable document containing such information."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.1e","Requirement","ECSS-E-ST-10-24_1290086",1,"Created","The equipment EICD shall include the grounding implementation for each electrical interface type."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.1f","Requirement","ECSS-E-ST-10-24_1290087",1,"Created","The equipment EICD shall include the lists of all electrical Interfaces of the equipment classified per signal type, electrical connector list and types (including supplier) and the equipment electrical connectors pin-to pin table.","NOTE \tIt is necessary to produce such lists and tables respecting a specific format for supporting the harness design (electrical interconnections with other equipment) at a higher level.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.1g","Requirement","ECSS-E-ST-10-24_1290088",1,"Created","The electrical interfaces specified in requirement ‎5.8.1f shall comprise:\n1.\tPer connector: module identifier, connector identifier, nominal / redundant, connector type, connector manufacturer, part number, connector function.\n2.\tPer pin: connector identifier, contact identifier, signal identifier, contact properties, signal type, directions, ratings.","NOTE\t1\tContact properties are for example Signal, Hot, Return, True, Complementary.\nNOTE\t2\tDirections are typically transmission related, driver or receiver.\nNOTE\t3\tRatings are expressed in terms of voltage or current.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.1h","Requirement","ECSS-E-ST-10-24_1290089",1,"Created","Fault emission and fault tolerance requirements shall be specified, and then verified, for all equipment external electrical interfaces.","NOTE \tFault emission and fault tolerance requirements are expressed in terms of voltage and current.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.1i","Requirement","ECSS-E-ST-10-24_1290090",1,"Created","The equipment EICD shall either be self-contained or refer to module level EICD of the modules used within the equipment.","NOTE \tThe module level EICD is intended for modules under a different responsibility than the one of the overall equipment containing them.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.1j","Requirement","ECSS-E-ST-10-24_1290091",1,"Created","For an equipment made of several modules, the electrical connections among the modules within the equipment shall be described in the equipment EICD."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.1k","Requirement","ECSS-E-ST-10-24_1290092",1,"Created","With respect to requirement ‎5.8.1j, one of the following options shall be applied:\n1.\tin case the modules are developed and integrated by the same interface actor, only a functional description of the connections is provided,\n2.\totherwise a full description of the connections is provided as per requirement ‎5.8.1f and ‎5.8.1g."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.1l","Requirement","ECSS-E-ST-10-24_1290093",1,"Created","The equipment EICD shall contain a summary table of the equipment power consumption and dissipation in the equipment operational modes including average power consumption, peak power consumption and any boundary condition.","NOTE \tA non-exhaustive list of equipment operational modes is the following: OFF, Stand-by operation, nominal operation, fault operation.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.1m","Recommendation","ECSS-E-ST-10-24_1290094",1,"Created","In the summary table specified in 5.8.1i the equipment actual electrical interface performances should be included in addition or in place of the ones specified by the specific contractual requirements.","NOTE\t1\tExample of maximum performances are the ones relevant to power consumption and dissipation, and boundary conditions as per requirement 5.8.1i.\nNOTE\t2\tThis recommendation is important for products development.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.2a","Requirement","ECSS-E-ST-10-24_1290095",1,"Created","The manufacturer responsible of an instrument/sub-system shall produce an EICD covering the Flight Model Electrical Architecture."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.2b","Requirement","ECSS-E-ST-10-24_1290096",1,"Created","The manufacturer responsible of an instrument/sub-system shall produce EICD covering the EM and EQM Electrical Architecture showing all the differences versus the Flight Model Electrical Architecture.","NOTE \tDifferences are for example on redundancies, simplified interfaces, reduced functionality.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.2c","Requirement","ECSS-E-ST-10-24_1290097",1,"Created","The instrument/sub-system EICD shall contain, or refer to the document containing, the Electrical Interface Budget including the margins per interface type (number of un-used interfaces vs number of implemented interfaces)."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.2d","Requirement","ECSS-E-ST-10-24_1290098",1,"Created","Fault emission and fault tolerance requirements shall be specified, and then verified, for all space segment subsystem external electrical interfaces.","NOTE \tFault emission and fault tolerance requirements are expressed in terms of voltage and current.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.2e","Requirement","ECSS-E-ST-10-24_1290099",1,"Created","The instrument or sub-system EICD shall include a global electrical diagram of the relevant instrument/sub-system.","NOTE \tThe global electrical diagram as a minimum covers equipment (with details of the relevant external interfaces), interconnections within the sub-system and external to it, and redundancies.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.2f","Requirement","ECSS-E-ST-10-24_1290100",1,"Created","The instrument/sub-system EICD shall describe with block diagrams how the different electrical interfaces of the equipment are connected to each other.","NOTE \tThe block diagrams include the implementation principles showing:\n·\tthe nominal and redundant equipment circuitries that are cross strapped and not cross strapped;\n·\tthe cross strap functional locations;\n·\tthe operative electrical interfaces in nominal operation;\n·\tthe non-operative electrical interfaces in nominal operation (interfaces either OFF for interfaces used in cold redundancy, or ON for interfaces used in Hot “Stand By” redundancy);\n·\tconnectors functional locations (main or redundant side), including skin, plugs and strap connectors;\n·\tprotections within an equipment protecting the cross straps (e.g. Overvoltage protections, over current protections, reference to the double isolation requirements and implementation).\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.2g","Requirement","ECSS-E-ST-10-24_1290101",1,"Created","The instrument/sub-system EICD shall refer to applicable EICD of equipment composing the instrument/sub-system at EM, EQM, FM, PFM level."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.2h","Requirement","ECSS-E-ST-10-24_1290102",1,"Created","The instrument/sub-system EICD shall contain or refer to the document containing a compatibility assessment of the electrical interface requirements and the instrument/sub-system harness specification.","NOTE \tThis applies to Electrical Interface defined in the GDIR/GERD, or specific interfaces.\nNOTE \tThe applicable reference document is the latest available issue at any time.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.2i","Requirement","ECSS-E-ST-10-24_1290103",1,"Created","The instrument/sub-system EICD shall include the allocation tables per electrical interface types. ","NOTE \tFor example, LCL allocation table with LCL classes, heaters allocation table, thermistors allocation table per thermistor type, etc.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.2j","Requirement","ECSS-E-ST-10-24_1290104",1,"Created","The allocation tables per electrical interface type shall be in line with the implementation of the redundancy scheme specified by the system at subsystem level.","NOTE \tFor example, thermistors acquisition on different analogue acquisition groups for triple majority voting implementation.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.2k","Requirement","ECSS-E-ST-10-24_1290105",1,"Created","The instrument/sub-system EICD shall include the electrical connector pin-to-pin tables describing the links:\n1.\tbetween all equipment (e.g. harnesses definition file);\n2.\tbetween the instrument/sub-system and its EGSEs;\n3.\tbetween the satellite platform equipment and the instrument/sub-system equipment."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.2l","Requirement","ECSS-E-ST-10-24_1290106",1,"Created","The electrical interfaces specified in requirement ‎5.8.2k shall comprise:\n1.\tPer connector: equipment identifier, connector identifier, nominal / redundant, connector type, connector manufacturer, part number, connector function.\n2.\tPin to pin table: connectors identifiers, contact identifier, signal identifier, contact properties (SIG, RTN, True, Comp), signal type.","NOTE \tContact properties are for example Signal, Hot, Return, True, Complementary\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.3a","Requirement","ECSS-E-ST-10-24_1290107",1,"Created","The manufacturer responsible of a satellite shall produce an EICD covering the Satellite Flight Model Electrical Architecture."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.3b","Requirement","ECSS-E-ST-10-24_1290108",1,"Created","The manufacturer responsible of a satellite shall produce an EICD covering the Satellite Electrical Functional Model, showing all the differences versus the Satellite Flight Model Electrical Architecture.","NOTE\t1\tDifferences are for example on redundancies, simplified interfaces, reduced functionality.\nNOTE\t2\tthe Satellite Electrical Functional Model is also called “Flat Sat”.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.3c","Requirement","ECSS-E-ST-10-24_1290109",1,"Created","The satellite EICD shall contain, or refer to the document containing, the Electrical Interface Budget including the margins per interface type (number of un-used interfaces vs number of implemented interfaces)."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.3d","Requirement","ECSS-E-ST-10-24_1290110",1,"Created","Fault emission and fault tolerance requirements shall be specified, and then verified, for all space segment element external electrical interfaces.","NOTE \tFault emission and fault tolerance requirements are expressed in terms of voltage and current.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.3e","Requirement","ECSS-E-ST-10-24_1290111",1,"Created","The satellite EICD shall include a global electrical diagram of the satellite.","NOTE \tThe global electrical diagram as a minimum covers equipment (with details of the relevant external interfaces), interconnections within the sub-system and external to it, and redundancies.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.3f","Requirement","ECSS-E-ST-10-24_1290112",1,"Created","The satellite EICD shall describe with block diagrams how the different electrical interfaces of the satellite equipment and sub-system/instruments are connected to each other.","NOTE \tThe block diagrams include the implementation principles showing:\n·\tthe nominal and redundant equipment circuitries that are cross strapped and not cross strapped;\n·\tthe cross strap functional locations;\n·\tthe operative electrical interfaces in nominal operation;\n·\tthe non-operative electrical interfaces in nominal operation (interfaces either OFF for interfaces used in cold redundancy, or ON for interfaces used in Hot “Stand By” redundancy);\n·\tconnectors functional locations (main or redundant side), including skin, plugs and strap connectors;\n·\tprotections within a equipment protecting the cross straps (e.g. Overvoltage protections, over current protections, reference to the double isolation requirements and implementation).\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.3g","Requirement","ECSS-E-ST-10-24_1290113",1,"Created","The satellite block diagram shall be presented on different levels, top level with summary functional lines, lower level with individual functional lines and at signal level."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.3h","Requirement","ECSS-E-ST-10-24_1290114",1,"Created","The satellite EICD shall refer to applicable EICD of equipment and sub-system/instruments composing the satellite at EM, EQM, FM, PFM level."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.3i","Requirement","ECSS-E-ST-10-24_1290115",1,"Created","The satellite EICD shall contain or refer to the document containing a compatibility assessment of the electrical interface requirements and the satellite harness specification.","NOTE\t1\tThis applies to Electrical Interface defined in the GDIR/GERD, or specific interfaces.\nNOTE\t2\tThe applicable reference document is the latest available issue at any time.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.3j","Requirement","ECSS-E-ST-10-24_1290116",1,"Created","The satellite EICD shall include the allocation tables per electrical interface types.","NOTE \tFor example RLCL/LCL allocation table with LCL classes, heaters allocation table, thermistors allocation table per thermistor type, fuses allocation table, etc.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.3k","Requirement","ECSS-E-ST-10-24_1290117",1,"Created","The allocation tables per electrical interface type shall be in line with the implementation of the redundancy scheme specified at system level.","NOTE \tFor example, thermistors acquisition on different analog acquisition groups for triple majority voting implementation.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","5.8.3l","Requirement","ECSS-E-ST-10-24_1290118",1,"Created","The satellite EICD shall include the electrical connector pin-to-pin tables describing the links:\n1.\tbetween the satellite and its EGSEs;\n2.\tbetween the satellite and the launcher;\n3.\tbetween all the satellite equipment and the instrument/sub-system."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","A.2.1<1>a","Requirement","ECSS-E-ST-10-24_1290033",1,"Unchanged","The IRD shall contain a description of the purpose, objective, content and the reason prompting its preparation."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","A.2.1<2>a","Requirement","ECSS-E-ST-10-24_1290034",1,"Unchanged","The IRD shall list the applicable and reference documents in support to the generation of the document."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","A.2.1<2>b","Requirement","ECSS-E-ST-10-24_1290035",1,"Unchanged","The relationship and precedence of the IRD to other project documents shall be clearly defined. "]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","A.2.1<2>c","Requirement","ECSS-E-ST-10-24_1290036",2,"Normative Change","The IRD shall include the following references:\n1.\tProduct tree (as defined in ECSS-M-ST-10 Annex B),\n2.\tSpecification tree (as defined in ECSS-E-ST-10),\n3.\tCoordinate system document (as defined in ECSS-E-ST-10-09)\n4.\tReferences to requirements specified in other Technical requirement specifications or Standards which are applicable for a particular Interface.","NOTE \tFor example, an IRD can refer to individual requirements coming from Technical Requirement Specification such as GDIR (General Design and Interface Requirements) or SSS (System Support Specification) or Standards such as MIL-STD-1553 Bus.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","A.2.1<2>d","Requirement","ECSS-E-ST-10-24_1290037",1,"Unchanged","It shall be confirmed that the IRD does not include duplicate or conflicting requirements already specified in another Technical requirements specification applicable to any interface end. "]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","A.2.1<3>a","Requirement","ECSS-E-ST-10-24_1290038",1,"Unchanged","The applicable dictionary or glossary and the meaning of specific terms or abbreviation utilized in IRD shall be defined."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","A.2.1<4>a","Requirement","ECSS-E-ST-10-24_1290039",1,"Unchanged","The IRD shall define the physical, functional, procedural and operational interface requirements between two or more items in the product tree and ensure hardware and software compatibility.","NOTE \tInterface requirements include for example, physical measures, definitions of sequences, of energy or information transfer, design constraints, and all other significant interactions between items. \n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","A.2.1<4>b","Requirement","ECSS-E-ST-10-24_1290040",1,"Unchanged","Interface Requirements shall be specified in accordance with ECSS-E-ST-10-06."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","A.2.1<4>c","Requirement","ECSS-E-ST-10-24_1290041",1,"Unchanged","Each interface requirements shall be accompanied by its verification requirements."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","A.2.1<4>d","Requirement","ECSS-E-ST-10-24_1290042",1,"Unchanged","For each verification requirement as defined in A.2.1<4>c., the verification responsibility shall be defined.","NOTE \tThis can be joint responsibility, stand-alone responsibility or any combination of them.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","A.2.1<4>e","Requirement","ECSS-E-ST-10-24_1290043",1,"Unchanged","The IRD shall specify the requirements of an interface, for all identified interface ends."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","A.2.1<4>f","Requirement","ECSS-E-ST-10-24_1290044",1,"Unchanged","The IRD shall specify for each requirement the applicability to each interface end."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","A.2.1<4>g","Requirement","ECSS-E-ST-10-24_1290045",1,"Unchanged","In case of an existing interface end design, the interface requirements shall address:\n1.\tinterface plane definition,\n2.\tinterface behaviour definition,\n3.\tdata affecting the interface definition."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","A.2.1<4>h","Requirement","ECSS-E-ST-10-24_1290046",1,"Unchanged","In addition to the general requirements defined in ECSS-E-ST-10-06, for each interface requirement the applicability to each interface end shall be specified."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","A.2.1<4>i","Requirement","ECSS-E-ST-10-24_1290047",1,"Unchanged","In case the IRD addresses more than one interface, the interface requirements shall be grouped either by interface end pair, by nature of interface, or by contractual party.","NOTE \tAn example of grouping by nature of interface is arranging the requirements by discipline such as mechanical, electrical, thermal and software/data. See also Annex E.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","A.2.1<5>a","Requirement","ECSS-E-ST-10-24_1290048",1,"Unchanged","For each interface, the following aspects shall be addressed:\n1.\tinterface description using tables, figures, or drawings,\n2.\tunits of measure including scale of measure,\n3.\ttolerances or required accuracies,\n4.\tin case of using non-SI quantities or units, conversions and conventions,\n5.\tinterface plane specification,\n6.\tcoordinate system specification, in case of interfaces involving geometric aspects,\n7.\tinterface behaviour specification, including limitation of use.","NOTE 1\tExample of interface plane is the separation plane between launch adapter and spacecraft.\nNOTE 2\tExample of limitation of use is decrease in capability.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","A.2.1<5>b","Requirement","ECSS-E-ST-10-24_1290049",1,"Unchanged","Interface requirements shall be built starting from the Reference Interface Data List of Annex E and adding all data necessary to specify the interface. ","NOTE \tIt is good practice to group the interface requirements by the interface natures as defined in Annex E.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","A.2.2a","Permission","ECSS-E-ST-10-24_1290074",2,"Normative Change","The content of the IRD may be merged with the content of the technical requirements specification (as defined in ECSS-E-ST-10-06 Annex A) of the product."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","B.2.1<1>a","Requirement","ECSS-E-ST-10-24_1290050",1,"Unchanged","The ICD shall contain a description of the purpose, objective, content and the reason prompting its preparation."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","B.2.1<2>a","Requirement","ECSS-E-ST-10-24_1290051",1,"Unchanged","The responsibilities of the interfacing organizations for development of the ICD shall be stated. "]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","B.2.1<2>b","Requirement","ECSS-E-ST-10-24_1290052",1,"Unchanged","The document approval authority (including change approval authority) shall be defined. "]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","B.2.1<2>c","Requirement","ECSS-E-ST-10-24_1290053",1,"Unchanged","The interface ends responsible shall be stated. "]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","B.2.1<3>a","Requirement","ECSS-E-ST-10-24_1290054",1,"Unchanged","The ICD shall list the applicable and reference documents and standards in support to the generation of the document. "]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","B.2.1<3>b","Requirement","ECSS-E-ST-10-24_1290055",1,"Unchanged","The relationship and precedence of the ICD to other programme documents shall be clearly defined. "]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","B.2.1<3>c","Requirement","ECSS-E-ST-10-24_1290056",1,"Unchanged","The ICD shall include the following references:\n1.\tProduct tree (as defined in ECSS-M-ST-10 Annex B),\n2.\tSpecification tree (as defined in ECSS-E-ST-10)."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","B.2.1<4>a","Requirement","ECSS-E-ST-10-24_1290057",1,"Unchanged","The applicable dictionary or glossary and the meaning of specific terms or abbreviation utilized in ICD shall be defined."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","B.2.1<5>a","Requirement","ECSS-E-ST-10-24_1290058",1,"Unchanged","The interface responsible shall establish a complete and exhaustive list of technical characteristics of the interface to be reflected in the interface definition/data. ","NOTE \tInformative Annex E lists a number of example aspects to be considered in interface definition. The list is meant to be used as a starting point but cannot be considered exhaustive.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","B.2.1<5>b","Requirement","ECSS-E-ST-10-24_1290059",1,"Unchanged","For each identified and specified interface, the interface responsible accounting for the contribution of the involved actors shall define interface characteristics in terms of:\n1.\tinterface plane definition,\n2.\tinterface behaviour identification, including limitation of use,\n3.\tinterface description using tables, figures, drawings, models, data base as appropriate,\n4.\tdata affecting the interface definition,\n5.\tunits of measure including scale of measure,\n6.\ttolerances or required accuracies,\n7.\tin case of using non-SI quantities or units, conversions and conversions.","NOTE 1\tExamples for item 1 are: mounting surface (between hardware products), Application Program Interface (between software products), communication network (between data systems).\nNOTE 2\tExamples for item 2 are: static, dynamic, nominal/off nominal, state machine. Possible limitation of use is coming from a decrease of capability.\nNOTE 3\tExample of item 3 are: mechanical drawing, interface 3D CAD model, electrical circuit schematic, software API, software architectural or detailed design document.\nNOTE 4\tExamples for item 4 are: dimensions, tolerances, coordinates, voltage, data format, temperature, load, heat flow, material, surface treatment, external standard reference.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","B.2.1<5>c","Requirement","ECSS-E-ST-10-24_1290060",1,"Unchanged","The ICD shall detail the interface definition between two (or more) interface ends."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","B.2.1<5>d","Requirement","ECSS-E-ST-10-24_1290061",1,"Unchanged","The ICD shall be grouped by contractual, discipline or product decomposition (product tree). "]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","B.2.1<5>e","Requirement","ECSS-E-ST-10-24_1290062",1,"Unchanged","Each ICD version shall identify the incorporated approved CR."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","B.2.1<5>f","Requirement","ECSS-E-ST-10-24_1290063",1,"Unchanged","The interface definitions shall be grouped per pair of interface ends having a common interface plane."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","B.2.1<5>g","Requirement","ECSS-E-ST-10-24_1290064",1,"Unchanged","In case the ICD addresses more than one interface, the interface definition shall be grouped either per physical/logical interface, or per nature of interface.","NOTE 1\tAn example of physical/logical grouping is arranging the interface data by a pair of interface ends (see Figure B-1).\nNOTE 2\tAn example of grouping by nature is arranging the interface data by discipline such as mechanical, electrical, thermal and software/data (see Figure B-1).\nNOTE 3\tIt is a good practice to group the interface requirements by the interface natures defined in Annex E.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","B.2.2a","Requirement","ECSS-E-ST-10-24_1290119",1,"Created","The naming of any unit or item shall be consistent with the system-level naming convention (as per Technology Plan required in ECSS-E-ST-10, annex E), including the system-level coordinate system document (as defined in ECSS-E-ST-10-09)."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","C.2.1<1>a","Requirement","ECSS-E-ST-10-24_1290065",1,"Unchanged","The IDD shall contain a description of the purpose, objective, content and the reason prompting its preparation."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","C.2.1<2>a","Requirement","ECSS-E-ST-10-24_1290066",1,"Unchanged","The IDD shall be issued and controlled by the interface end supplier."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","C.2.1<2>b","Requirement","ECSS-E-ST-10-24_1290067",1,"Unchanged","The document approval authority (including change approval authority) shall be defined. "]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","C.2.1<3>a","Requirement","ECSS-E-ST-10-24_1290068",1,"Unchanged","The IDD shall list the applicable and reference documents and standards in support to the generation of the document. "]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","C.2.1<3>b","Requirement","ECSS-E-ST-10-24_1290069",1,"Unchanged","The relationship and precedence of the IDD to other programme documents shall be clearly defined. "]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","C.2.1<4>a","Requirement","ECSS-E-ST-10-24_1290070",1,"Unchanged","The applicable dictionary or glossary and the meaning of specific terms or abbreviation utilized in IDD shall be defined."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","C.2.1<5>a","Requirement","ECSS-E-ST-10-24_1290071",1,"Unchanged","The IDD shall contain:\n1.\tinterface end description and data definition using tables, figures, drawings, models, data base as appropriate,\n2.\tunits of measure including scale of measure, \n3.\ttolerances or required accuracies,\n4.\tin case of using non-SI quantities or units, conversions and conventions,\n5.\tinterface plane implementation,\n6.\tinterface end behaviour,\n7.\tinterface end data."]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","C.2.1<5>b","Requirement","ECSS-E-ST-10-24_1290072",1,"Unchanged","Interface end data shall be built starting from the Reference Interface Data List of Annex E and further identify all data necessary to document the design of the interface end. ","NOTE \tIt is recommended to group the interface end data by the interface natures defined in Annex E.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","C.2.2<1>a","Permission","ECSS-E-ST-10-24_1290075",1,"Unchanged","The IDD may take different forms depending on the kind of interface end it documents.","NOTE \tExamples of different forms are: a mechanical drawing, interface 3D CAD model, electrical circuit schematic, software API, software architectural or detailed design document.\n"]
["ECSS-E-ST-10-24C Rev.1","ECSS - Current v1.0","C.2.2<1>b","Permission","ECSS-E-ST-10-24_1290076",2,"Unchanged","The IDD may be a container with unambiguous references into the supplier's Design Definition File (DDF).","NOTE \tIDD covers the formerly called \"interface inputs\" from the supplier to the customer.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.1a","Requirement","ECSS-E-ST-10_0790001",2,"Normative Change","The system engineering function shall produce and maintain a system engineering plan (SEP) in conformance with Annex D.","NOTE\tThe system engineering function establishes the SEP with the contributions and constraints of management, product assurance, engineering disciplines, production, and operations and logistics.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.1b","Requirement","ECSS-E-ST-10_0790002",2,"Deleted","<<deleted and moved modified as Note to 5.1a>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.1c","Requirement","ECSS-E-ST-10_0790003",2,"Normative Change","The SEP shall take consideration of the lower level plans, ensure consistency between these plans, and, be consistent with these plans.","NOTE \t1\tThe early version of the Project Management Plan (PMP), which includes the early version of the SEP, contains all the information which was traditionally contained in the Design and Development Plan (DDP). See Annex R which illustrates the mapping between a typical DDP and ECSS DRDs. \nNOTE \t2\tThe SEP content evolves with the phase of the project, with more information on risk analysis and new technologies in early phases 0, A and B, and more information on verification and validation aspects in phases C, D.\nNOTE \t3\tThe SEP can be considered a collection of documents delivered over the life-cycle as illustrated in Table A-1.\nNOTE \t4\tNo SEP lower than equipment/unit.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.1d","Requirement","ECSS-E-ST-10_0790394",1,"Created","The system engineering function shall support the project manager in the project reviews as defined in the Project Management Plan in accordance with ECSS-M-ST-10."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.1a","Requirement","ECSS-E-ST-10_0790004",2,"Normative Change","The system engineering function shall analyse the requirements for the system issued by the customer.","NOTE \t1\tThis analysis enables the transformation of customer requirements into the supplier’s system solution.\nNOTE \t2\tThe level of the required analysis and form of any deliverable is expressed in the business agreement.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.1b","Requirement","ECSS-E-ST-10_0790005",2,"Normative Change","The system engineering function shall derive, generate, control and maintain the set of requirements for the lower level elements, defining their design and operational constraints and the parameters of functionality, performance, and verification necessary to meet the system requirements issued by the customer."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.1c","Requirement","ECSS-E-ST-10_0790006",2,"Normative Change","The system engineering function shall ensure consistency of the requirements at system level, at lower levels, as well as amongst levels.","NOTE\tConsistency of requirements of different system engineering sub-functions at the same level is the responsibility of the higher level system engineering function.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.1d","Requirement","ECSS-E-ST-10_0790007",2,"Normative Change","The system engineering function shall ensure requirements generated in 5.2.1b. are in conformance with characteristics specified in ECSS-E-ST-10-06 clause 8."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.1e","Requirement","ECSS-E-ST-10_0790008",2,"Normative Change","The system engineering function shall ensure that each requirement for the lower level elements has a justification reflected in the requirement justification file in conformance with Annex O.","NOTE\tTailoring of a standard in a list of applicable standards, or of a requirement in an applicable standard, is possible where each tailoring measure is duly justified.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.2a","Requirement","ECSS-E-ST-10_0790009",2,"Normative Change","The system engineering function shall ensure forward and backward traceability of all requirements:\n1.\tto their sources; \n2.\tto the lower level requirements, if existing;\n3.\tto changes in the design inducing modifications of the requirements;\n4.\tto their verification close-out.","NOTE\tto item 1: Examples for sources: a higher level requirement, an imposed management constraint, an applicable standard or an accepted lower level constraint.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.2b","Requirement","ECSS-E-ST-10_0790010",2,"Normative Change","The system engineering function shall establish and maintain the requirements traceability matrix in conformance with Annex N."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.2c","Requirement","ECSS-E-ST-10_0790011",2,"Normative Change","The system engineering function shall ensure that the requirement close-out traceability is documented in the VCD in conformance with ECSS-E-ST-10-02 Annex B."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.3.1a","Requirement","ECSS-E-ST-10_0790012",2,"Normative Change","The system engineering function shall establish technical requirements specifications of the next lower level products consistent among them and with the technical specification received from the customer."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.3.1b","Requirement","ECSS-E-ST-10_0790013",2,"Normative Change","The system engineering function shall ensure that the technical requirements specifications it establishes conform to ECSS-E-ST-10-06 and its DRD in Annex A."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.3.1c","Requirement","ECSS-E-ST-10_0790014",2,"Normative Change","The system engineering function shall establish a specification tree in conformance with Annex J.","NOTE \t1 \tRequirements common to more than one lower level product can be gathered in “common” technical specifications called “support specifications” (e.g. GDIR “General Design and Interface Requirements”, environmental, test, EMC requirements specifications).\nNOTE \t2\tRequirements for equipment level products (or lower level products) can be issued in self-contained specifications. \n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.3.1d","Requirement","ECSS-E-ST-10_0790015",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.3.2a","Requirement","ECSS-E-ST-10_0790016",2,"Normative Change","The system engineering function shall involve the customer in the consolidation of requirements by identifying and resolving incomplete, duplicate, ambiguous, and contradictory requirements for customer-issued requirements."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.3.2b","Requirement","ECSS-E-ST-10_0790017",2,"Normative Change","The system engineering function shall reflect the consolidated requirements in the release of the technical specifications."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.3.3a","Requirement","ECSS-E-ST-10_0790018",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.3.3b","Requirement","ECSS-E-ST-10_0790019",2,"Normative Change","The system engineering function shall perform the requirements analysis to identify impacts on system risks."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.3.3c","Requirement","ECSS-E-ST-10_0790395",1,"Created","As part of the risk management process implemented on the project, the system engineering function shall report the requirement impacts on the risk.","NOTE\tECSS‐M‐ST‐80 Annex E describes the risk reporting process.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.3.4a","Requirement","ECSS-E-ST-10_0790020",2,"Normative Change","The system engineering function shall ensure that for each requirement contained in the technical requirements specification, one or a combination of verification methods are identified. ","NOTE\tTechnical requirements specification is defined in ECSS-E-ST-10-06 Annex A.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.3.4b","Requirement","ECSS-E-ST-10_0790021",2,"Normative Change","The system engineering function shall ensure that for each requirement contained in the technical requirements specification, the verification methods are reflected in the verification matrix.","NOTE\tTechnical requirements specification is defined in ECSS-E-ST-10-06 Annex A.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.3.5a","Requirement","ECSS-E-ST-10_0790022",2,"Normative Change","The system engineering function shall ensure that the system requirements and their verification methods are allocated to lower levels and included in the specifications of the related products."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.3.6a","Requirement","ECSS-E-ST-10_0790023",2,"Deleted","<<deleted>>."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.3.6b","Requirement","ECSS-E-ST-10_0790024",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.3.7a","Requirement","ECSS-E-ST-10_0790025",2,"Normative Change","In phase 0 the system engineering function shall propose   requirements in response to  the expressed user needs, for agreement with the customer.","NOTE\t”User needs” are expressed in the Mission Statement document.\nNOTE\tIn some contexts this activity is called “requirements validation”. This terminology has not been used to avoid confusion with the term “validation” as defined in ECSS-S-ST-00-01.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.3.8a","Requirement","ECSS-E-ST-10_0790026",2,"Normative Change","The system engineering function shall ensure that agreed changes to requirements are applied to and maintained in system and lower level specifications."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.3.8b","Requirement","ECSS-E-ST-10_0790027",2,"Deleted","<<deleted>>."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.2.3.9a","Requirement","ECSS-E-ST-10_0790028",2,"Normative Change","The system engineering function shall establish the list of documents constituting the system requirements baselines in contribution to the configuration baselines.","NOTE\tDetails on configuration baselines are provided in ECSS-M-ST-40.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.1a","Requirement","ECSS-E-ST-10_0790029",2,"Normative Change","In phase 0 the system engineering function shall perform an analysis of the Mission Statement document, produce Mission Description document(s) in conformance with Annex B, and maintain this latter document for the final selected concept. "]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.1b","Requirement","ECSS-E-ST-10_0790030",2,"Normative Change","The system engineering function shall perform a functional analysis, produce the functional architecture, and produce the function tree which satisfy the customer technical requirements specification, in conformance with Annex H."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.1c","Requirement","ECSS-E-ST-10_0790031",2,"Normative Change","The system engineering function shall document the functional architecture in the design definition file (DDF) in conformance with Annex G."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.1d","Requirement","ECSS-E-ST-10_0790032",2,"Normative Change","The system engineering function shall justify the functional architecture in the DJF in conformance with Annex K."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.1e","Requirement","ECSS-E-ST-10_0790033",2,"Normative Change","The system engineering function shall perform a physical analysis, produce the physical architecture and produce the product tree in conformance with ECSS-M-ST-10 Annex B."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.1f","Requirement","ECSS-E-ST-10_0790034",2,"Normative Change","The system engineering function shall document the physical architecture in the DDF in conformance with Annex G."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.1g","Requirement","ECSS-E-ST-10_0790035",2,"Normative Change","The system engineering function shall justify the physical architecture in the DJF in conformance with Annex K."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.1h","Requirement","ECSS-E-ST-10_0790036",2,"Normative Change","The system engineering function shall analyse the performance of the system, including end-to-end evaluation, documenting the results of the analysis in the Design Justification File in conformance with Annex K."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.1i","Requirement","ECSS-E-ST-10_0790037",2,"Normative Change","The system engineering function shall analyse the influence of mission, design, development, operations and constraints on cost and schedule as an input to the project cost and schedule consolidation and to the utilisation recurring cost"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.1j","Requirement","ECSS-E-ST-10_0790038",2,"Normative Change","The system engineering function shall document analysis that it performs in an analysis report.","NOTE\tAn example of an analysis report is given in Annex S.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.2a","Requirement","ECSS-E-ST-10_0790039",2,"Normative Change","The system engineering function shall establish the influence of all types of environments applied during each life profile event on system and its elements in terms of nominal and extreme environmental conditions including all applicable operational phases. "]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.2b","Requirement","ECSS-E-ST-10_0790040",2,"Normative Change","The system engineering function shall establish the criteria for qualification and acceptance in conformance with Annex K of system and system elements for all types of environment."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.2c","Requirement","ECSS-E-ST-10_0790041",2,"Normative Change","The system engineering function shall ensure that analyses include design induced effects between system components or the system and its external environment and account for analysis uncertainties, in conformance with Annex K."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.2d","Requirement","ECSS-E-ST-10_0790042",2,"Normative Change","The system engineering function shall establish the design and test factors and margins applicable for design in conformance with Annex K.","NOTE \t1\tDesign factors are factors applied to specified loads to ensure robustness of the design.\nNOTE \t2\tTest factors are factors applied to specified loads to demonstrate margins w.r.t. these loads (e.g. qualification / acceptance factors).\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.2e","Requirement","ECSS-E-ST-10_0790043",2,"Normative Change","The system engineering function shall establish test environment conditions for product verification in test specifications."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.3a","Requirement","ECSS-E-ST-10_0790044",2,"Normative Change","The system engineering function shall conduct or consolidate trade-off analyses to:\n1.\tassist in selecting system concepts, designs and solutions (including people, parts and materials availability);\n2.\tsupport material selection and process decisions;\n3.\tsupport make-or-buy and supplier selection;\n4.\texamine alternative technologies to satisfy functional and design requirements; \n5.\tevaluate environmental and cost impacts of materials and processes;\n6.\tevaluate alternative physical architectures to select preferred products and processes;\n7.\testablish the system and its configuration items;\n8.\tanalyze planning critical paths and propose alternatives;\n9.\tselect standard components, techniques, services and facilities that reduce system life-cycle cost;\n10.\testablish model and product verification philosophy for achieving qualification and acceptance objectives while considering testability;\n11.\tassess design capacity to evolve."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.3b","Requirement","ECSS-E-ST-10_0790045",2,"Normative Change","The system engineering function shall evaluate alternative concepts, designs and solutions against each other in a Trade-off report in conformance with Annex L."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.3c","Requirement","ECSS-E-ST-10_0790046",2,"Normative Change","The system engineering function shall document alternative system concepts considered during system trade-off studies in a System Concept Report in conformance with Annex C."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.4a","Requirement","ECSS-E-ST-10_0790047",2,"Normative Change","The system engineering function shall define the analysis methods and tools to be used during the product life cycle, as well as the related models and data exchanges between the tools, and document these in the SEP in conformance with Annex D."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.4b","Requirement","ECSS-E-ST-10_0790048",2,"Normative Change","The system engineering function shall ensure that analysis tools are validated."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.4c","Requirement","ECSS-E-ST-10_0790049",2,"Normative Change","The system engineering function shall ensure that analysis tools are maintained."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.4d","Requirement","ECSS-E-ST-10_0790050",2,"Normative Change","The system engineering function shall ensure that analysis tools are capable of exchanging and using models and data where agreed by customer and supplier.","NOTE \t1\tFor exchange of models and data, see ECSS-E-TM-10-20 and ECSS-E-TM-10-21.\nNOTE \t2\tExchange can be either direct or via interfaces.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.4e","Requirement","ECSS-E-ST-10_0790051",2,"Normative Change","The system engineering function shall ensure that analysis tools are capable of transferring models and data for multi-disciplinary analysis where agreed by customer and supplier. ","NOTE \t1\tDetails on product data exchange and system modelling and simulation are provided in ECSS-E-TM-10-20 and ECSS-E-TM-10-21.\nNOTE \t2\tExchange can be either direct or via interfaces.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.4f","Requirement","ECSS-E-ST-10_0790052",2,"Normative Change","The system engineering function shall ensure that models produced by analysis tools are validated based on documented procedures and results."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.4g","Requirement","ECSS-E-ST-10_0790053",2,"Normative Change","The system engineering function shall ensure that modelling and test accuracy as well as limitations are considered (as part of Annex K) when establishing the performances and specifying environmental conditions for product verification."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.3.4h","Requirement","ECSS-E-ST-10_0790054",2,"Normative Change","The system engineering function shall ensure that models are kept operational in accordance with the terms of the business agreement."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.1.1a","Requirement","ECSS-E-ST-10_0790055",2,"Normative Change","The system engineering function shall establish a design of the system from its functional architecture, requirement allocation, and technology selection.","NOTE\tThis includes definition of the interfaces and corresponding ICDs.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.1.1b","Requirement","ECSS-E-ST-10_0790056",2,"Normative Change","The system engineering function shall ensure that the design addresses system aspects, covering its whole lifecycle, producing the physical architecture documented in conformance with Annex G and the product tree in conformance with ECSS-M-ST-10 Annex B."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.1.1c","Requirement","ECSS-E-ST-10_0790057",2,"Normative Change","The system engineering function shall take into account the outcome of the design and verification activities of the lower level products."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.1.1d","Requirement","ECSS-E-ST-10_0790058",2,"Normative Change","The system engineering function shall ensure that the design covers hardware, software, and human-in-the-loop (HITL)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.1.1e","Requirement","ECSS-E-ST-10_0790059",2,"Normative Change","The system engineering function shall ensure that the design is supported by analyses consistent with the level of maturity of the design."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.1.1f","Requirement","ECSS-E-ST-10_0790060",2,"Normative Change","The system engineering function shall coordinate with all entities for design data exchange..","NOTE\tThis relates to coordination between the various functions given in Figure 4-1.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.1.2a","Requirement","ECSS-E-ST-10_0790061",2,"Normative Change","The system engineering function shall define, control and maintain all technical budgets of the system in conformance with Annex I in terms of target, current status and their trends."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.1.2b","Requirement","ECSS-E-ST-10_0790062",2,"Normative Change","The system engineering function shall apportion and control budget requirements to all levels of system decomposition."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.1.2c","Requirement","ECSS-E-ST-10_0790063",2,"Normative Change","The system engineering function shall define and apply the margin policy agreed between customer and supplier in compliance with Annex D.2.1<4.2>b.5.","NOTE\tThe system margin policy is defined in the SEP.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.1.3a","Requirement","ECSS-E-ST-10_0790064",2,"Normative Change","The system engineering function shall define the design methods, tools and related models to be used during the product life cycle and document them in the SEP."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.1.3b","Requirement","ECSS-E-ST-10_0790065",2,"Normative Change","The system engineering function shall ensure that design tools are validated and maintained."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.1.3c","Requirement","ECSS-E-ST-10_0790066",2,"Normative Change","The system engineering function shall ensure that design tools are capable of exchanging and using design models and data where agreed by the customer and supplier."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.1.3d","Requirement","ECSS-E-ST-10_0790067",2,"Normative Change","The system engineering function shall ensure that models  are kept operational in accordance with the business agreements."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.1.3e","Requirement","ECSS-E-ST-10_0790068",2,"Normative Change","The system engineering function shall ensure that design models produced by design tools are validated."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.1.3f","Requirement","ECSS-E-ST-10_0790069",2,"Normative Change","The system engineering function shall ensure that all design models are defined in accordance with the Coordinate System Document  with transformation methods as defined in ECSS-E-ST-10-09.","NOTE\tCoordinate system document is delivered as part of the SEP.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.1.4a","Requirement","ECSS-E-ST-10_0790070",2,"Normative Change","The system engineering function shall establish and maintain a design definition file in conformance with Annex G."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.1.4b","Requirement","ECSS-E-ST-10_0790071",2,"Normative Change","The system engineering function shall establish and maintain a design justification file in conformance with Annex K."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.1.4c","Requirement","ECSS-E-ST-10_0790072",2,"Normative Change","The system engineering function shall establish and maintain a product user’s manual (PUM) or user’s manual (UM) in conformance with Annex P.","NOTE\tIn case the product considered is a space segment, the Space Segment User Manual defined in ECSS-E-ST-70 Annex E is generated with support of the system engineering function.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.2.1a","Requirement","ECSS-E-ST-10_0790073",2,"Normative Change","The system engineering function shall ensure that the configuration includes the system functional, physical and software characteristics, budgets, and, internal and external interfaces."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.2.1b","Requirement","ECSS-E-ST-10_0790074",2,"Normative Change","The system engineering function shall ensure that the configuration includes lower decomposition levels."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.2.1c","Requirement","ECSS-E-ST-10_0790075",2,"Normative Change","The system engineering function shall ensure that the configuration is documented in the DDF and in configuration definition documents.","NOTE\tDetails on configuration definition documents are provided in ECSS-M-ST-40.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.2.2a","Requirement","ECSS-E-ST-10_0790076",2,"Normative Change","The system engineering function shall establish the system configuration baselines to be placed under control at defined project milestones.","NOTE\tDetails on system configuration baselines are provided in ECSS-M-ST-40. \n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.2.3a","Requirement","ECSS-E-ST-10_0790077",2,"Normative Change","The system engineering function shall define and document the hierarchy and assembly sequence of the system elements in line with the physical architecture."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.4.2.3b","Requirement","ECSS-E-ST-10_0790078",2,"Deleted","<<deleted and incorporated in 5.4.2.3a.>>."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.5.1a","Requirement","ECSS-E-ST-10_0790079",2,"Normative Change","The system engineering function shall define the Verification Plan in accordance with ECSS-E-ST-10-02 Annex A and coordinate the product verification accordingly.."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.5.2a","Requirement","ECSS-E-ST-10_0790080",2,"Deleted","<<deleted, covered by 5.5.2c.>>."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.5.2b","Requirement","ECSS-E-ST-10_0790081",2,"Normative Change","The system engineering function shall assign the product to a verification product category, as defined in ECSS-E-ST-10-02 Table 5-1."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.5.2c","Requirement","ECSS-E-ST-10_0790082",2,"Normative Change","The system engineering function shall specify the configuration and environment conditions for product verification and the criteria for its qualification and acceptance."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.5.2d","Requirement","ECSS-E-ST-10_0790083",2,"Normative Change","The system engineering function shall confirm that all product verification objectives are achieved by analysing the results of the verification activities. ","NOTE\tThis includes analysis of Verification Control Document and its closeout documents, as defined in ECSS-E-ST-10-02 Annex B.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.5.2e","Requirement","ECSS-E-ST-10_0790084",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.5.2f","Requirement","ECSS-E-ST-10_0790085",2,"Normative Change","The system engineering function shall ensure that the verification covers the complete product including hardware, software, human-in-the-loop (HITL), operations and representative mission scenarios (including pre-launch, launch and early orbit, in-orbit, post-landing, or other mission scenario).","NOTE \t1\tThe testing performed during and at the end of the integration of a system is defined as System Functional Test (SFT).\nNOTE \t2\tFor system composed of different segments (e.g. space segment, ground segment), the testing performed to ensure operability and functionality of the complete system is defined as System Validation Test (SVT).\nNOTE \t3\tSystem validation is performed against user needs and is typically performed under customer authority, with supplier involvement as detailed in the business agreement.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.1a","Requirement","ECSS-E-ST-10_0790086",2,"Normative Change","The system engineering function  shall implement the SEP including quantification of this effort as input to management."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.1b","Requirement","ECSS-E-ST-10_0790087",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.1c","Requirement","ECSS-E-ST-10_0790088",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.1d","Requirement","ECSS-E-ST-10_0790089",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.1e","Requirement","ECSS-E-ST-10_0790090",2,"Deleted","<<deleted, covered by 5.6.1a.>>."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.1f","Requirement","ECSS-E-ST-10_0790091",2,"Normative Change","The system engineering function shall ensure that all engineering changes, dispositions and decisions are provided to project configuration control in accordance with the Configuration Management Plan."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.1g","Requirement","ECSS-E-ST-10_0790092",2,"Normative Change","The system engineering function shall ensure that the experience gained in past and in parallel activities is systematically considered and support project management in the collection of experience gained for future use."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.2a","Requirement","ECSS-E-ST-10_0790093",2,"Normative Change","The system engineering function shall ensure that the SEP is consistent with the project schedule.","NOTE\tDetails on the project schedule content are provided in ECSS-M-ST-60, in particular the DRD Annex B.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.3a","Requirement","ECSS-E-ST-10_0790094",2,"Normative Change","The system engineering function shall define the engineering data to be stored in a data repository."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.3b","Requirement","ECSS-E-ST-10_0790095",2,"Normative Change","The system engineering function shall ensure that engineering data can be exchanged in electronic form between the different organizations in charge of the elements of the product decomposition levels via agreed and validated interfaces."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.3c","Requirement","ECSS-E-ST-10_0790396",1,"Created","The system engineering function shall ensure the availability of engineering data to meet the schedule which enable the system to be designed, produced, tested, delivered, operated, maintained, and disposed of."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.4a","Requirement","ECSS-E-ST-10_0790096",2,"Normative Change","The system engineering function shall ensure external and internal interfaces  are controlled in conformance with ECSS-E-ST-10-24.","NOTE \t1\tThe control of the external interfaces is performed in cooperation with the parties involved in the interface.\nNOTE \t2\tInterface requirements are rolled-out of the technical specification as interface requirements documents\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.4b","Requirement","ECSS-E-ST-10_0790097",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.4c","Requirement","ECSS-E-ST-10_0790098",2,"Deleted","<<deleted>>. "]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.5a","Requirement","ECSS-E-ST-10_0790099",2,"Normative Change","The system engineering function shall define the coordinate systems and related coordinate units  in the Coordinate System Document conforming to DRD ECSS-E-ST-10-09 Annex A."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.5b","Requirement","ECSS-E-ST-10_0790100",2,"Normative Change","The system engineering function shall define the units system to be used during the product life cycle and document it in the SEP.","NOTE\tFor example; the unit system being selected as \"metric\".\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.6a","Requirement","ECSS-E-ST-10_0790101",2,"Deleted","<<deleted, covered by clause 5.4.1.2>>."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.6b","Requirement","ECSS-E-ST-10_0790102",2,"Deleted","<<deleted, covered by clause 5.4.1.2>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.7a","Requirement","ECSS-E-ST-10_0790103",2,"Normative Change","The system engineering function shall identify candidate technologies, and document them in the Technology Matrix in conformance with Annex F."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.7b","Requirement","ECSS-E-ST-10_0790104",2,"Normative Change","The technologies proposed shall be assessed and verified in terms of TRL levels, defined in ECSS-E-AS-11, and documented in the Technology Plan in conformance with Annex E.","NOTE\tFor assessing and verifying technologies, the process described in ECSS-E-HB-11 “TRL Handbook” can be used.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.7c","Requirement","ECSS-E-ST-10_0790105",2,"Normative Change","The system engineering function shall demonstrate supportability and feasibility within the defined supplier’s cost and schedule constraints."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.7d","Requirement","ECSS-E-ST-10_0790397",1,"Created","The Technology Readiness Status List (TRSL) shall be completed and provided to the customer for Phase 0 in conformance with Annex E.2.1<5>."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.7e","Requirement","ECSS-E-ST-10_0790398",1,"Created","The Technology Readiness Status List (TRSL) of the programme technologies shall be maintained and provided to the customer at Phase A and B project reviews"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.7f","Requirement","ECSS-E-ST-10_0790399",1,"Created","The TRSL specified in Annex E.2.1<5> shall be developed by the system engineering team with the support of the PA manager."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.7g","Requirement","ECSS-E-ST-10_0790400",1,"Created","The items identified in the TRSL shall be assessed at Phase B for inclusion and tracking in the Critical Items List","NOTE\tThe TRSL and the processes of transferring technologies to the Critical Item List is captured in ECSS-E-HB-11.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.8a","Requirement","ECSS-E-ST-10_0790106",2,"Normative Change","The system engineering function shall contribute to the identification of risks and mitigation measures.","NOTE\tDetails on risk management are provided in ECSS-M-ST-80.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.8b","Requirement","ECSS-E-ST-10_0790107",2,"Deleted","<<deleted, covered in 5.4.1.1f.>>."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.8c","Requirement","ECSS-E-ST-10_0790108",2,"Normative Change","The system engineering function shall implement and control the content of the risk management plan which is within system engineering responsibility."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.9a","Requirement","ECSS-E-ST-10_0790109",2,"Normative Change","The system engineering function shall provide a technical assessment on any change proposal to the baseline of the product."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.9b","Requirement","ECSS-E-ST-10_0790110",2,"Normative Change","The system engineering function shall provide a technical assessment on any nonconformance to the status of the product ","NOTE \tNonconformance treatment is described by ECSS-Q-ST-10-09.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","5.6.9c","Requirement","ECSS-E-ST-10_0790111",2,"Normative Change","The system engineering function shall implement and control agreed actions assigned to it, arising from change proposals and nonconformances.","NOTE \t1\tChange is related to a request for deviation.\nNOTE \t2\tNonconformance is related to a request for waiver.\nNOTE \t3\tThe change procedure/control is defined as part of the configuration management as defined in ECSS-M-ST-40.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.2a","Requirement","ECSS-E-ST-10_0790112",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.2b","Requirement","ECSS-E-ST-10_0790113",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.2c","Requirement","ECSS-E-ST-10_0790114",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.2d","Requirement","ECSS-E-ST-10_0790115",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.2e","Requirement","ECSS-E-ST-10_0790116",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.3a","Requirement","ECSS-E-ST-10_0790117",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.3b","Requirement","ECSS-E-ST-10_0790118",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.3c","Requirement","ECSS-E-ST-10_0790119",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.4a","Requirement","ECSS-E-ST-10_0790120",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.4b","Requirement","ECSS-E-ST-10_0790121",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.4c","Requirement","ECSS-E-ST-10_0790122",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.5a","Requirement","ECSS-E-ST-10_0790123",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.5b","Requirement","ECSS-E-ST-10_0790124",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.5c","Requirement","ECSS-E-ST-10_0790125",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.6a","Requirement","ECSS-E-ST-10_0790126",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.6b","Requirement","ECSS-E-ST-10_0790127",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.6c","Requirement","ECSS-E-ST-10_0790128",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.7a","Requirement","ECSS-E-ST-10_0790129",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.7b","Requirement","ECSS-E-ST-10_0790130",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.7c","Requirement","ECSS-E-ST-10_0790131",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.8a","Requirement","ECSS-E-ST-10_0790132",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.8b","Requirement","ECSS-E-ST-10_0790133",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.8c","Requirement","ECSS-E-ST-10_0790134",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.8d","Requirement","ECSS-E-ST-10_0790135",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.9a","Requirement","ECSS-E-ST-10_0790136",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","6.9b","Requirement","ECSS-E-ST-10_0790137",2,"Deleted","<<deleted, modified and inserted as informative text in clause 4>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","B.2.1<1>a","Requirement","ECSS-E-ST-10_0790138",1,"Unchanged","The MDD shall contain a description of the purpose, objective, content and the reason prompting its preparation (e.g. logic, organization, process or procedure)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","B.2.1<2>a","Requirement","ECSS-E-ST-10_0790139",1,"Unchanged","The MDD shall list the applicable and reference documents in support to the generation of the document, and include, as a minimum, the current preliminary technical requirements specification."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","B.2.1<3>a","Requirement","ECSS-E-ST-10_0790140",1,"Unchanged","The MDD shall provide a summary of the preliminary technical requirements specification objectives and list the design driving requirements, derived from the current initial specification."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","B.2.1<4>a","Requirement","ECSS-E-ST-10_0790141",2,"Normative Change","The MDD shall provide:\n1.\tOverview of the concept\n2.\tMission analysis\n3.\tSystem description, element by element\n4.\tDescription of how the system works in each mission phase\n(a)\tPerformance drivers\n(b)\tConstraints\n(c)\tMain events\n(d)\tOperations scenarios","NOTE 1 to item 3: For example: For a spacecraft, its ground control segment, and a user segment, e.g.\n\tSpace Segment\n·\tPayload \n·\tPlatform \n·\tLaunch Vehicle \n·\tOrbit related aspects\n·\tOn-Board Data Handling \n·\tReference Operation Scenarios / Observation characteristics\n·\tOperability / Autonomy Requirements \n\tGround Segment \n·\tFunctional Requirements and Major Elements \n·\tMonitoring and Control Segment \n·\tData Processing Segment \n\tUser segment\n·\tFunctional Requirements and Major Elements \n·\tMonitoring requirements \nNOTE 2 to item 4: For example: For a spacecraft, the following phase:\n·\tLaunch preparation \n·\tLaunch and Early Orbit Phase \n·\tIn Orbit Commissioning \n·\tNominal Operations \n·\tSpacecraft Disposal "]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","B.2.1<4>b","Requirement","ECSS-E-ST-10_0790142",2,"Deleted","<<deleted and moved as item 4 into requirement B.2.1<4>a>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","B.2.1<5>a","Requirement","ECSS-E-ST-10_0790143",1,"Unchanged","The MDD shall provide the\n1.\tassessment against the current preliminary technical requirements specification requirements, and\n2.\tidentification of non-compliances, and their impact on the current preliminary technical requirements specification."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","B.2.1<6>a","Requirement","ECSS-E-ST-10_0790144",1,"Unchanged","The MDD shall provide the list of identified risk related to the concept, including as a minimum technology, contingencies handling, and programmatic aspects."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","B.2.1<7>a","Requirement","ECSS-E-ST-10_0790145",1,"Unchanged","The MDD shall summarize the strengths and weaknesses of the concept."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","C.2.1a","Requirement","ECSS-E-ST-10_0790146",1,"Unchanged","The system concept report shall be an instantiation of the trade-off report at system level in Phase 0 and Phase A of a project, conforming to ECSS-E-ST-10 Annex L.","NOTE\tThe system concept report can be extended to Phase B where needed (e.g. late trade-offs).\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","C.2.1b","Requirement","ECSS-E-ST-10_0790147",1,"Unchanged","This report shall address all technical (e.g. engineering disciplines), programmatic and related aspects relevant to the system."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","C.2.1c","Requirement","ECSS-E-ST-10_0790148",1,"Unchanged","Where relevant, specific e.g. discipline trade-off’s shall be performed, contributing to the system trade-off, each one being reported in a document conforming to ECSS-E-ST-10 Annex L."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<1>a","Requirement","ECSS-E-ST-10_0790149",1,"Unchanged","The SEP shall contain a description of the purpose, objective, content and the reason prompting its preparation (e.g. programme or project reference and phase)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<2>a","Requirement","ECSS-E-ST-10_0790150",1,"Unchanged","The SEP shall list the applicable and reference documents in support to the generation of the document."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<2>b","Requirement","ECSS-E-ST-10_0790151",1,"Unchanged","The SEP shall include the references to the following applicable documents:\n1.\tBusiness agreement\n2.\tProject management plan, as defined in ECSS-M-ST-10 Annex A\n3.\tProduct assurance plan, as defined in ECSS-Q-ST-10 Annex A\n4.\tConfiguration management plan, as defined in ECSS-M-ST-40 Annex A\n5.\tProduction plan\n6.\tMission operations plan, as defined in ECSS-E-ST-70 Annex G\n7.\tILS plan."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<3.1>a","Requirement","ECSS-E-ST-10_0790152",2,"Normative Change","The SEP shall contain the following description of:\n1.\tThe project objective and the main elements that characterize the user’s need.\n2.\tThe objective of the system or product as established by the TS (as defined in the ECSS-E-ST-10-06 Annex A).\n3.\tThe main elements of the system architecture (i.e. first level elements of the architecture adopted for the system and identification of their reuse constraints).\n4.\tThe principal characteristics of the project lifecycle and the incremental development of the system (e.g. successive versions, progressive implementation of the functions of the system).\n5.\tThe main elements supporting the project lifecycle (e.g. ground support equipment, and facilities).\n6.\tThe organizational constraints impacting system engineering activities (e.g. the external and internal industrial organization (e.g. contractors, partners, suppliers, own company) constraints).\n7.\tThe list of the critical issues identified at the beginning of the project phase(s).\n8.\tThe list of national and international regulations.\n9.\tThe capacity for verification and validation of the product, taking into account the means available, e.g. for tests, analysis, or simulation."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<3.2>a","Requirement","ECSS-E-ST-10_0790153",1,"Unchanged","The SEP shall detail the incremental development of the system: \n1.\tprogressive implementation of system functionalities,\n2.\tidentification of possible successive versions, \n3.\tobjectives and strategy for the implementation of the successive versions."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<3.3>a","Requirement","ECSS-E-ST-10_0790154",1,"Unchanged","The SEP shall provide an implementation and schedule of the system engineering activities and identify for the considered phase(s), as a minimum:\n1.\tthe main project milestones driving the system engineering process,\n2.\tthe phase(s) of the project lifecycle and the main reviews in accordance to project management plan."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<3.3>b","Requirement","ECSS-E-ST-10_0790155",1,"Unchanged","The SEP shall provide dates of milestones or the duration of phases and the critical path according to the project master schedule."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<3.4>a","Requirement","ECSS-E-ST-10_0790156",1,"Unchanged","The SEP shall describe the strategy for acquisition of the items of the system or products defined in the product tree (e.g. make or buy, product line, incremental development)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<3.5>a","Requirement","ECSS-E-ST-10_0790157",1,"Unchanged","The SEP shall list the critical issues identified at the beginning of the project phase(s) covered in the SEP (e.g. any specific issues, problems, critical subjects, which require dedicated attention, investigation, action and planning)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<4.1>a","Requirement","ECSS-E-ST-10_0790158",1,"Unchanged","The SEP shall list the driving inputs for the system engineering activities described and defined by the:\n1.\tbusiness agreement,\n2.\toutputs from previous phase(s) or expected under the heading of activities which are not controlled within the context of this SEP (e.g. data provided by the customer, data coming from other projects, upstream or predevelopment studies, product lines),\n3.\tproject management plan, product assurance plan, risk management plan, and configuration and documentation management plans."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<4.1>b","Requirement","ECSS-E-ST-10_0790159",2,"Normative Change","The SEP shall list the external means and facilities (e.g. equipment, software, and premises) made available by the customer or by any other entity external to the supplier that is responsible of this SEP, and, for each identified mean or facility, identify the applicable interface requirements (e.g. interface control documentation) as well as the authority in charge of it."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<4.1>c","Requirement","ECSS-E-ST-10_0790160",1,"Unchanged","The SEP shall list the internal means and facilities (e.g. equipment, software, and premises) made available by the organization in charge of the development of the system or product."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<4.1>d","Requirement","ECSS-E-ST-10_0790161",1,"Unchanged","The SEP shall contain the Coordinate System Document (as defined in ECSS-E-ST-10-09 Annex A)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<4.1>e","Requirement","ECSS-E-ST-10_0790162",1,"Unchanged","The SEP shall define the units system to be used in the project."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<4.2>a","Requirement","ECSS-E-ST-10_0790163",1,"Unchanged","The SEP shall list the specified system engineering outputs as defined in ECSS-E-ST-10 clause 6 for the specific project phase(s) covered in the SEP.","NOTE\tAn overview of document delivery is given in Annex A.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<4.2>b","Requirement","ECSS-E-ST-10_0790164",1,"Unchanged","The SEP shall describe the following:\n1.\tThe strategy for the system engineering activities in line with the guidelines addressed by the management plan. In particular, identifying intermediate technical events for each phase in compliance with the master program schedule.\n2.\tThe system design activities, with their objectives and major outputs according to the phase.\n3.\tThe major engineering activities for each intermediate technical events, showing their mutual interactions and their relationships with the principal milestones (i.e. internal or contractual) of the project.\n4.\tThe model philosophy (as defined in ECSS-E-ST-10-02 clause 4.2.5) in terms of number and characterization of models, from system to the requested lower level, necessary to achieve a high confidence in the product verification. \n5.\tThe margin policy according to project phase, product category and maturity level."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<4.2>c","Requirement","ECSS-E-ST-10_0790165",1,"Unchanged","The SEP shall also describe \n1.\tthe method(s) and process(es) considered for the engineering activities (e.g. concurrent engineering, value analysis, or iteration cycle), \n2.\tthe interrelation between the different engineering disciplines and other project activities (e.g. production, quality assurance, and operations and logistics), \n3.\tthe interaction with other actors (e.g. customer and suppliers),\n4.\tthe consistency and coherency of simultaneous activities (e.g. performed in parallel),\n5.\twhich and how, control activities are implemented,\n6.\tAssessment of potential COTS usage"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<4.2>d","Requirement","ECSS-E-ST-10_0790166",1,"Unchanged","In the case of a system incremental evolution, the SEP shall describe the design strategy for the:\n1.\tdevelopment of the initial release of the product,\n2.\tdevelopment, the verification of subsequent releases and their deployment,\n3.\tintroduction of new technologies,\n4.\ttools and methods used for analysis,\n5.\tcontrol of the evolutions for each release."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<4.3>a","Requirement","ECSS-E-ST-10_0790167",1,"Unchanged","The SEP shall contain the following:\n1.\tDefinition of the entities participating in the system engineering activities and the corresponding functions according to the project management plan.\n2.\tIdentification of key engineering roles and responsibilities (e.g. system engineers, disciplines engineers, and technical managers).\n3.\tDescription of the co-operative work amongst the different teams participating in the system design."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<4.4>a","Requirement","ECSS-E-ST-10_0790168",2,"Normative Change","The SEP shall describe the external and internal coordination in line with the project management plan."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<5.1.1>a","Requirement","ECSS-E-ST-10_0790169",1,"Informative Change","The SEP shall describe the system engineering process tailored to the specifics of the considered project, and identify all the system engineering tasks to be implemented from the starting conditions (e.g. kick-off) to the closing event (e.g. review), their relationship, and their interfaces with other actors of the project, and identify and describe any existing iteration within the process."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<5.1.1>b","Requirement","ECSS-E-ST-10_0790170",1,"Informative Change","For each task, the input information and their origin, the document(s) delivered (i.e. expected output) and their destination, the system engineering function(s) performed and the contribution of other actors shall be identified."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<5.1.2>a","Requirement","ECSS-E-ST-10_0790171",1,"Unchanged","The SEP shall address the following activities that concern the different engineering disciplines, recalling the relevant applicable standards and ancillary dedicated plans that are considered integral part of this SEP."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<5.1.2>b","Requirement","ECSS-E-ST-10_0790172",1,"Unchanged","The SEP shall define the process and control to be put in place to meet requirements for the thermal, structures, mechanisms, environmental control and life support, propulsion, pyrotechnics, mechanical parts, and materials functions and interfaces.","NOTE\tThese requirements refer to Mechanical engineering as defined in ECSS-E-ST-3x series of standards.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<5.1.2>c","Requirement","ECSS-E-ST-10_0790173",1,"Unchanged","The SEP shall define the process and control to be put in place to meet requirements for electrical and electronic engineering, covering all electrical and electronic aspects of the relevant space product, including functions such as power generation, storage, conversion and distribution, and optical, avionics and microwave domains, electromagnetic compatibility, and electrical interfaces. ","NOTE\tThese requirements refer to Electrical and electronic engineering as defined in ECSS-E-ST-20.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<5.1.2>d","Requirement","ECSS-E-ST-10_0790174",1,"Unchanged","The SEP shall define process and control to be put in place to meet requirements for software engineering, covering, amongst others, flight and ground software, checkout software and simulation software.","NOTE\tThese requirements refer to Software engineering as defined in ECSS-E-ST-40.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<5.1.2>e","Requirement","ECSS-E-ST-10_0790175",1,"Unchanged","The SEP shall define process and control to be put in place to meet requirements for communication engineering, covering, amongst others, spacecraft-to-ground, spacecraft-to-spacecraft, ground-to-ground and on-board communications links. ","NOTE 1\tThese requirements refer for Communications engineering as defined in ECSS-E-ST-50.\nNOTE 2\tIt includes aspects such link budgets, data management, RF, audio and video communications and protocols.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<5.1.2>f","Requirement","ECSS-E-ST-10_0790176",1,"Informative Change","The SEP shall define process and control to be put in place to meet requirements for control engineering, covering, amongst others, AOCS, robotics, rendez-vous and docking."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<5.1.2>g","Requirement","ECSS-E-ST-10_0790177",1,"Unchanged","The SEP shall define the process and control to be put in place to meet requirements specifying natural environment for all space regimes (e.g. debris regulations, or planetary contamination protection) and general models and rules for determining the local induced environment","NOTE\tThese requirements refer to Space environment as defined in ECSS-E-ST-10-04.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<5.1.2>h","Requirement","ECSS-E-ST-10_0790178",1,"Unchanged","The SEP shall define the process and control to be put in place to meet requirements for the approach, methods, procedures, organization and resources to be implemented to ensure proper technical interfaces between system engineering and production. "]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<5.1.2>i","Requirement","ECSS-E-ST-10_0790179",1,"Unchanged","The SEP shall define the process and control to be put in place to meet requirements of operations of the space segment, covering, amongst others:\n1.\tmission operation definition and preparation, \n2.\tmission and trajectory analysis, and\n3.\toperability analysis (e.g. autonomy, operational scenario, nominal and non-nominal modes, failure detection isolation and recovery).","NOTE\tThese requirements refer to Operations engineering as defined in ECSS-E-ST-70.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<5.1.2>j","Requirement","ECSS-E-ST-10_0790180",1,"Unchanged","The SEP shall define the process and control to be put in place to meet requirements for ground and in-orbit logistics and maintenance, addressing, amongst others, technical activities, related engineering standards, methods and analyses to be performed to ensure that the development of space systems (i.e. manned and unmanned) properly takes into account and integrates the supportability and support aspects for the whole life cycle."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<5.1.2>k","Requirement","ECSS-E-ST-10_0790181",1,"Unchanged","The SEP shall define the process and control to be put in place to meet requirements for human activities and environments associated with space systems. ","NOTE\tThese requirements refer to Human factors engineering as defined in ECSS-E-ST-10-11.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<5.1.2>l","Requirement","ECSS-E-ST-10_0790182",1,"Unchanged","The SEP shall define process and control to be put in place to meet requirements for implementation of design selections relating to humans for any item with associated human interface, including computer based system and equipment."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<5.1.3>a","Requirement","ECSS-E-ST-10_0790183",1,"Unchanged","The SEP shall define and describe the work package(s) for the relevant engineering tasks, which are maintained in the work breakdown structure."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<5.2>a","Requirement","ECSS-E-ST-10_0790184",1,"Unchanged","When the SEP includes sub-plans covering parts of system engineering activities, these sub-plans shall be annexed to the SEP."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<5.2>b","Requirement","ECSS-E-ST-10_0790185",2,"Normative Change","The SEP shall identify the other plans relevant to system engineering function activity belonging to the following categories:\n1.\tProgrammatic plans\n2.\tVerification plans\n3.\tEngineering discipline plans\n4.\tOperations plans","NOTE 1\tSome of these plans can be integrated in the SEP in the early phases of a project.\nNOTE 2\tNote to item 1: Examples of programmatic plans are: the SEP plans of sub-products constituting the system or product, Industrial procurement plan, risk management plan, off-the-shelf plan (see ECSS-Q-ST-20-10). \nNOTE 3\tNotes to item 2:\n·\tExamples of verification plans are: verification plan (VP), AIT plan, AIV plan and technology plan, system calibration plan, Security Aspects Verification Plan. Some of those DRDs are defined in this document, in ECSS-E-ST-10-02 or ECSS-E-ST-10-03.\n·\tVP and AIT plans can be integral parts of the SEP, or rolled out separately (without overlap), or combined as the AIV Plan which can also be rolled out separately. However, the existence of the AIV Plan excludes independent VP and AIT plans.\nNOTE 4\tNote to item 3: Examples of engineering discipline plans are: Fracture Control Plan (see ECSS-E-ST-32), Micro-gravity Control Plan, Electro-Magnetic Compatibility Plan (see ECSS-E-ST-20), Audible Noise Control Plan, Radio Frequency Plan, Alignment Requirements and Control Plan, System Performance Simulations Plan, Software Development Plan, Orbital Debris Mitigation Plan and Disposal Plan (as defined in ISO 24113:2011), Planetary protection Plan, Cleanliness and Contamination Control Plan. \nNOTE  5\tNote to item 4: Examples of operation plans are: launch site operations and logistics plan, system commissioning and operation support plan. \n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<5.2>c","Requirement","ECSS-E-ST-10_0790186",1,"Unchanged","The SEP shall describe the constraints and the interactions impacting the system engineering activities derived from the analysis of the plans identified as relevant in D.2.1<5.2>b."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<5.3>a","Requirement","ECSS-E-ST-10_0790187",1,"Unchanged","The SEP shall list and briefly describe the methods, tools, and data models that the system engineering team uses in performing their tasks."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<5.3>b","Requirement","ECSS-E-ST-10_0790188",1,"Unchanged","In relation to requirements traceability and demonstration of verification (compliance with requirements, VCD), the specific methods and tools shall be described (including interfaces to next lower level suppliers), and reuse of elements (e.g. COTS) identified."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<5.4>a","Requirement","ECSS-E-ST-10_0790189",1,"Unchanged","The SEP shall describe any specific issues, problems requiring dedicated attention, investigations or actions during the current phase and identify risks, and risk mitigation measures."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","D.2.1<6>a","Requirement","ECSS-E-ST-10_0790190",1,"Unchanged","The SEP shall introduce the system engineering activities, to be conducted during subsequent phase(s) of the project, and as a minimum, list any identified critical issue and risk to be mitigated during the subsequent phase(s)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","E.2.1<1>a","Requirement","ECSS-E-ST-10_0790191",1,"Unchanged","The TP shall contain a description of the purpose, objective, content and the reason prompting its preparation (e.g. programme or project reference and phase)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","E.2.1<2>a","Requirement","ECSS-E-ST-10_0790192",1,"Unchanged","The TP shall list the applicable and reference documents in support to the generation of the document and include the reference to the following applicable documents:\n1.\tSEP\n2.\tTechnology matrix (as defined in ECSS-E-ST-10, Annex F)\n3.\tFunction tree\n4.\tSpecification tree."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","E.2.1<3>a","Requirement","ECSS-E-ST-10_0790193",1,"Unchanged","The TP shall contain a summary of the main aspects of:\n1.\tproject objectives and constraints (i.e. section <3.1> of ECSS-E-ST-10, Annex D \"SEP DRD\");\n2.\tproduct evolution logic (i.e. section <<3.2> of ECSS-E-ST-10, Annex D \"SEP DRD\");\n3.\tproject phase(s), reviews and planning (i.e. section <3.3> of ECSS-E-ST-10, Annex D \"SEP DRD\"),\n4.\tProcurement approach (i.e. section <3.4> of ECSS-E-ST-10, Annex D \"SEP DRD\")"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","E.2.1<4.1>a","Requirement","ECSS-E-ST-10_0790194",1,"Unchanged","The TP expected output shall be an answer concerning the possibility for using the identified or needed technology to perform a function."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","E.2.1<4.2>a","Requirement","ECSS-E-ST-10_0790195",1,"Unchanged","For each system function, the TP input shall be:\n1.\ttechnical requirements, \n2.\tthe selected technology or technological element and its TRL, \n3.\tthe list of the identified project risks and critical aspects, and\n4.\tthe schedule for Engineering activities."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","E.2.1<4.3>a","Requirement","ECSS-E-ST-10_0790196",1,"Unchanged","The TP shall establish and describe the necessary activities to complete the acquisition of each technology or technological element, including verification strategies and methods, and the link to product assurance aspects."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","E.2.1<4.3>b","Requirement","ECSS-E-ST-10_0790197",1,"Unchanged","The TP shall define the model philosophy for each technology or technological element, based on an assessment on the maturity status and on the criticality of the technology with respect to functions' requirements."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","E.2.1<4.3>c","Requirement","ECSS-E-ST-10_0790198",1,"Unchanged","The TP shall describe the technology development activities, their required or possible interrelations and timings, as necessary for the satisfactory acquisition of the technologies and procurement of the technological elements."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","E.2.1<4.3>d","Requirement","ECSS-E-ST-10_0790199",1,"Unchanged","The TP shall identify technical milestones, showing their interactions and relationships with the SEP milestones."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","E.2.1<4.4>a","Requirement","ECSS-E-ST-10_0790200",1,"Unchanged","The TP shall contain the following:\n1.\tdefinition of the entities participating in the engineering activities and the corresponding functions according to the SEP;\n2.\tidentification of key engineering roles and responsibilities for each technology or technological element."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","E.2.1<4.5>a","Requirement","ECSS-E-ST-10_0790201",1,"Unchanged","The TP shall describe the external and internal interfaces in conformance to the SEP."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","E.2.1<5>a","Requirement","ECSS-E-ST-10_0790202",1,"Unchanged","The TP shall describe, for any identified technology risk and related critical aspects for the project, the specific actions taken for risk mitigation based on identified technology readiness level (TRL)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","E.2.1<5>b","Requirement","ECSS-E-ST-10_0790401",1,"Created","The TP shall include the TRSL by using the template in Figure E-1, and listing:\n1.\tthe critical function, with reference to the Function tree,\n2.\tthe name of the technology or element(s) implementing such a function,\n3.\tcurrent declared and verified TRL, as defined in ECSS-E-AS-11,\n4.\treference to the TRA report confirming the declared TRL,\n5.\tdate of the report,\n6.\tkey points to support TRL declared in column [3],\n7.\tforward plan for TRL evaluation, indicating the target TRL, the phase or date at which such target TRL is expected, and status of the planning to achieve the target TRL,\n8.\tduring phases A & B, indication whether or not the technology/element is a candidate for the CIL.","NOTE 1\tThe key point in column [6] are normally few lines summarizing the TRL assessment report referenced in column [4].\nNOTE 2\tAt the end of Phase B, the TRSL is introduced as part of the CIL.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","E.2.2a","Permission","ECSS-E-ST-10_0790403",1,"Created","The content of the TP may be merged with the content of the SEP."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","E.2.2b","Requirement","ECSS-E-ST-10_0790204",1,"Unchanged","The TP shall introduce the related activities, to be conducted during all phase(s) of the project."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","F.2.1<1>a","Requirement","ECSS-E-ST-10_0790205",1,"Unchanged","The technology matrix shall contain a description of the purpose, objective, content and the reason prompting its preparation."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","F.2.1<2>a","Requirement","ECSS-E-ST-10_0790206",1,"Unchanged","The technology matrix shall list the applicable and reference documents in support to the generation of the document and include the reference to the following applicable documents:\n1.\tSpecification tree\n2.\tPreliminary technical requirements specifications\n3.\tFunction tree."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","F.2.1<3>a","Requirement","ECSS-E-ST-10_0790207",1,"Unchanged","The technology matrix shall list the system technical requirements/functions as defined in the functional architecture and its corresponding function tree, and their associated preliminary TS."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","F.2.1<4>a","Requirement","ECSS-E-ST-10_0790208",1,"Unchanged","The technology matrix shall list the system technical requirements/functions and for each, a potential technology or technological element.","NOTE\tSources to identify potential technologies are technology watch, corporate technology plan, or research and development programme.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","F.2.1<4>b","Requirement","ECSS-E-ST-10_0790209",2,"Normative Change","For each technology or technological element, the following information shall be listed:\n1.\tindex of technology readiness and maturity as defined in Table 4-2 of ECSS-E-AS-11;\n2.\tproof of company's maturity concerning the knowledge and expertise of the technology, including a description of the necessary technology acquisition activities;\n3.\tidentification of potential risks, e.g. technology availability, programmatic and financial aspects."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","F.2.1<5>a","Requirement","ECSS-E-ST-10_0790210",1,"Unchanged","The technology matrix shall propose a ranking of the potential technology or technological element for each system requirement/ function."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","F.2.1<6>a","Requirement","ECSS-E-ST-10_0790211",1,"Unchanged","The technology matrix shall provide, for each system requirement/function, the selected technology or technological element, a list of the identified project risks and critical aspects, and an identified back-up technological solution."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<1>a","Requirement","ECSS-E-ST-10_0790212",1,"Unchanged","The DDF shall contain a description of the purpose, objective and the reason prompting its preparation (e.g. programme or project reference and phase). "]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<2>a","Requirement","ECSS-E-ST-10_0790213",1,"Unchanged","The DDF shall contain the list of applicable and reference documents, used in support to the generation of the document. "]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<2>b","Requirement","ECSS-E-ST-10_0790214",1,"Unchanged","The DDF shall include the reference to the following applicable documents:\n1.\tBusiness agreement\n2.\tSystem engineering plan (as defined in ECSS-E-ST-10 Annex D)\n3.\tCoordinate system document (as defined in ECSS-E-ST-10-09 Annex A)\n4.\tTechnical requirements specification (TS)\n5.\tProduct assurance plan\n6.\tConfiguration management plan (as defined in ECSS-M-ST-40)\n7.\tConfiguration status report (as defined in ECSS-M-ST-40)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<2>c","Requirement","ECSS-E-ST-10_0790215",1,"Unchanged","The DDF shall refer to DDFs of next higher and lower level products."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<3>a","Requirement","ECSS-E-ST-10_0790216",1,"Unchanged","The DDF shall contain a brief description of the product and of the main technical requirements throughout its life cycle phases (e.g. launch, deployed, operations, end-of-life)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<3>b","Requirement","ECSS-E-ST-10_0790217",1,"Unchanged","The DDF shall contain the description of the system or product design documentation, based on the product tree (as defined in ECSS-M-ST-10) and also include, or refer to, the specifications tree (as defined in ECSS-E-ST-10 Annex J)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<3>c","Requirement","ECSS-E-ST-10_0790218",1,"Unchanged","The DDF of a system shall contain at least the technical requirements specifications of the elements in which the system is broken down "]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<4.1>a","Requirement","ECSS-E-ST-10_0790219",1,"Unchanged","The DDF shall contain the description of the functional architecture of the system or product i.e. the arrangement of functions, their sub-functions and interfaces (internal and external), and the performance requirements to satisfy the requirements of the TS."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<4.1>b","Requirement","ECSS-E-ST-10_0790220",1,"Unchanged","The DDF shall present the data and their flow interchanged between the different functions, the conditions for control, and the execution sequencing for the different operational modes and states.","NOTE\tThe Functional Architecture is an output of the functional analysis process (as defined in ECSS-E-ST-10 clause 5.3.1a)\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<4.2>a","Requirement","ECSS-E-ST-10_0790221",1,"Unchanged","The DDF shall contain or refer to the system or product function tree, the latter conforming to ECSS-E-ST-10 Annex H."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<4.3>a","Requirement","ECSS-E-ST-10_0790222",1,"Unchanged","The DDF shall describe the functional chains that contribute to the realization of the functional requirements of the TS and their contributing functions, consider the different operational modes and states, and indicate the selected physical implementation for each of the functions."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<5.1>a","Requirement","ECSS-E-ST-10_0790223",1,"Unchanged","The DDF shall contain the description of physical architecture of the system or product i.e. the arrangement of elements, their decomposition, interfaces (internal and external), and physical constraints, which form the basis of a system or product design to satisfy the functional architecture and the technical requirements.","NOTE\tThe Physical Architecture is an output of the preliminary design definition activities (as defined in clause 5.3.1f).\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<5.2>a","Requirement","ECSS-E-ST-10_0790224",1,"Unchanged","The DDF shall contain or refer to the product tree of the system or product, as defined in ECSS-M-ST-10 Annex B.","NOTE\tThe Product Tree is a breakdown of the Physical Architecture.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<5.3>a","Requirement","ECSS-E-ST-10_0790225",1,"Unchanged","The DDF shall contain or refer to the specification tree of the system or product, the latter conforming to Annex J."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<5.4>a","Requirement","ECSS-E-ST-10_0790226",1,"Unchanged","The DDF shall provide\n1.\tthe nomenclature of the system or product, \n2.\tthe overall system or product drawings,\n3.\tfor each element of the system, the description of the different constituents of the physical architecture,\n4.\tthe characteristics of the respective elements, \n5.\ttheir configuration management identifier (e.g. hardware part number, software version number, drawings number, electrical schematics numbers)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<5.4>b","Requirement","ECSS-E-ST-10_0790227",1,"Unchanged","The DDF shall reference any documentation containing detailed technical descriptions and associated matrices to ensure overall consistency and completeness."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<5.5>a","Requirement","ECSS-E-ST-10_0790228",2,"Normative Change","The DDF shall describe the physical and functional characteristics of the internal and external interfaces of the system and refer to the relevant IRD and ICD, conforming to Annex A of ECSS-E-ST-10-24."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<6>a","Requirement","ECSS-E-ST-10_0790229",1,"Unchanged","The DDF shall present the budget allocation of the technical parameters of the system and provide the actual status of the system margins, and deviations. "]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<6>b","Requirement","ECSS-E-ST-10_0790230",1,"Unchanged","The DDF shall contain or refer to the system or product technical budget, the latter conforming to Annex I."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<7.1>a","Requirement","ECSS-E-ST-10_0790231",1,"Unchanged","The DDF shall present the constraints induced by the system or product design definition on the production activities e.g. operational allowable envelopes, restrictions on assembling sequences, procedures and testing modes, exclusion zones, manufacturing environmental conditions, and conditions for procurement."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<7.2>a","Requirement","ECSS-E-ST-10_0790232",1,"Unchanged","The DDF shall present the constraints induced by the system or product design definition on the implementation of the operations e.g. operational allowable envelopes, restrictions on operating modes, and exclusion zones."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<7.3>a","Requirement","ECSS-E-ST-10_0790233",1,"Unchanged","The DDF shall present the constraints induced by the system or product design definition on the transportation activities and during the periods of storage of the product e.g. allowable envelopes, restrictions on transportation and storage, exclusion zones, packaging, shock levels, temperature environments, humidity, cleanliness, regulations, and dangerous materials."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<7.4>a","Requirement","ECSS-E-ST-10_0790234",1,"Unchanged","The DDF shall present the constraints induced by the system or product design definition on the maintenance activities and procedures e.g. operational allowable envelopes, accessibility, tooling, support materials, parts availability, and deliveries."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<8>a","Requirement","ECSS-E-ST-10_0790235",2,"Normative Change","The DDF shall contain the information on the system or product engineering data repository that contains the complete set of design parameters, or a reference to it.","NOTE\tInformation about the set of design parameters is provided in ECSS-E-TM-10-10.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","G.2.1<9>a","Requirement","ECSS-E-ST-10_0790236",1,"Unchanged","The DDF shall list and summarize all deviations of the design with respect to the technical specifications and constraints induced by the system or product design definition."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","H.2.1<1>a","Requirement","ECSS-E-ST-10_0790237",1,"Unchanged","The function tree document shall contain a description of the purpose, objective and the reason prompting its preparation."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","H.2.1<2>a","Requirement","ECSS-E-ST-10_0790238",1,"Unchanged","The function tree document shall contain the list of applicable and reference documents, used in support to the generation of the document."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","H.2.1<3>a","Requirement","ECSS-E-ST-10_0790239",1,"Unchanged","The function tree document shall contain a brief description of the project and of the key user’s needs."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","H.2.1<4>a","Requirement","ECSS-E-ST-10_0790240",1,"Unchanged","The function tree document shall provide the complete list of functions that the system or product shall perform, and contain a graphical representation where the main specified function(s) (i.e. at the top level of the tree) is/are decomposed into lower level functions."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","H.2.1<4>b","Requirement","ECSS-E-ST-10_0790241",1,"Unchanged","When recurrent products from previous space projects are used, the product’s functions shall be identified in the tree structure, and addition, every necessary function by the system or product that is not under the supplier’s responsibility identified in the tree structure."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","H.2.2a","Requirement","ECSS-E-ST-10_0790242",1,"Unchanged","The function tree shall be coherent with other functional descriptions of the system or product (e.g. functional architecture, functional block diagram)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","I.2.1<1>a","Requirement","ECSS-E-ST-10_0790243",1,"Unchanged","The technical budget shall contain a description of the purpose, objective, content and the reason prompting its preparation."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","I.2.1<2>a","Requirement","ECSS-E-ST-10_0790244",1,"Unchanged","The technical budget shall list the applicable and reference documents in support to the generation of the document."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","I.2.1<3>a","Requirement","ECSS-E-ST-10_0790245",1,"Informative Change","The technical budget shall: \n1.\tlist the selected key engineering parameters (those specified by the customer and those selected by the supplier),\n2.\tpresent the reason for their selection,\n3.\tidentify for each key engineering parameters the stages of maturity of the design.\n4.\tpresent the related margin policy for these parameters.","NOTE\tto item 1: Examples of key engineering parameters are mass, communication links, power, and on-board computer memory capacity.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","I.2.1<4>a","Requirement","ECSS-E-ST-10_0790246",1,"Unchanged","For each key engineering parameter, the technical budget shall:\n1.\tprovide the specified value of the parameter,\n2.\tprovide the supplier’s margin resulting of the allocation of the parameter to the lower level products,\n3.\tprovide the specified values with the reference to the relevant technical requirement of the lower level products, \n4.\tpropose a specific program to conform to the specified value in case of nonconformance,\n5.\tcontain a chart of parameter history that presents the evolution of the parameter’s value at the different design maturity steps for which the evaluation of the parameter is performed,\n6.\tlist the documentation sources (e.g. analysis report and verification report)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","I.2.1<5>a","Requirement","ECSS-E-ST-10_0790247",1,"Unchanged","The technical budget shall contain a conclusion that identifies the key engineering parameters having a negative margin, and identify for each of those:\n1.\tthe impact on the technical requirements and the associated risk for the project, and\n2.\tthe specific program to conform to the specified value and for project risk mitigation."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","J.2.1<1>a","Requirement","ECSS-E-ST-10_0790248",1,"Unchanged","The specification tree document shall contain a description of the purpose, objective and the reason prompting its preparation. "]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","J.2.1<2>a","Requirement","ECSS-E-ST-10_0790249",1,"Unchanged","The specification tree document shall contain the list of applicable and reference documents, used in support to the generation of the document. "]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","J.2.1<3>a","Requirement","ECSS-E-ST-10_0790250",1,"Unchanged","The specification tree document shall contain a brief description of the project and the key user’s needs."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","J.2.1<4>a","Requirement","ECSS-E-ST-10_0790251",1,"Unchanged","The specification tree document shall provide the complete list of specifications defining the system or product, and contain a graphical representation where the system or product specification (i.e. at the top level of the tree) is decomposed into lower level product specifications."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","J.2.1<4>b","Requirement","ECSS-E-ST-10_0790252",1,"Unchanged","When recurrent products from previous space projects are used, their specification shall be identified in the tree structure, and in addition, for every necessary product that is not under the supplier’s responsibility, their specification shall be identified in the tree structure."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","J.2.2a","Requirement","ECSS-E-ST-10_0790253",1,"Unchanged","The specification tree shall be coherent with the product tree (see ECSS-M-ST-10) and the business agreement structure (see ECSS-M-ST-60)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<1>a","Requirement","ECSS-E-ST-10_0790254",1,"Unchanged","The DJF shall contain a description of the purpose, objective, content and the reason prompting its preparation."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<2>a","Requirement","ECSS-E-ST-10_0790255",1,"Unchanged","The DJF shall list the applicable and reference documents in support to its generation."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<2>b","Requirement","ECSS-E-ST-10_0790256",1,"Unchanged","The applicable document list shall contain the reference to the relevant product specifications, and the relevant DDF and system engineering plan."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<2>c","Requirement","ECSS-E-ST-10_0790257",1,"Unchanged","The reference document list shall contain the reference to:\n1.\tTrade-Off-Reports, as defined Annex L.\n2.\tAnalysis Reports (e.g. requirements allocation analysis, functional analysis).\n3.\tRequirements Traceability Matrix, as defined in Annex N (with link to analysis).\n4.\tVerification Control Document \n5.\tAll verification documentation, such as:\n(a)\tAnalysis Reports (e.g. reports w.r.t. qualification aspects)\n(b)\tTest Reports\n(c)\tROD Reports\n(d)\tInspection Reports\n(e)\tVerification Reports"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<3>a","Requirement","ECSS-E-ST-10_0790258",1,"Unchanged","The DJF shall contain a description of the expected product, its intended mission, architecture and design, and the functioning principles on which it is based."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<3>b","Requirement","ECSS-E-ST-10_0790259",1,"Unchanged","The DJF shall define the requirement criteria levels for qualification and acceptance verification of the product."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<4>a","Requirement","ECSS-E-ST-10_0790260",1,"Unchanged","The DJF shall present status of the design justification in response to requirements, with emphasis on the driving requirements that have a big impact on the system design, production and maintainability (see also K.2.1<8.2.4>a.)"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<4>b","Requirement","ECSS-E-ST-10_0790261",1,"Unchanged","The DJF shall present an overall system qualification status synthesis, including:\n1.\tthe list of requirements which have not been met (e.g. nonconformances), including proposed actions,\n2.\tthe list of all critical points, and how criticalities have been or are intended to be resolved,\n3.\tthe identification of requirements which have not been justified yet, and associated risks analysis, with emphasis on those that can have an impact at system level."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<5>a","Requirement","ECSS-E-ST-10_0790262",1,"Unchanged","The DJF shall contain the demonstration that all requirements of the preliminary technical requirements specification are allocated to functional blocks of the system functional architecture."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<5>b","Requirement","ECSS-E-ST-10_0790263",1,"Unchanged","Where requirements assigned to functional blocks do not have their origin within any of the customer preliminary technical specifications, these requirements shall be justified. "]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<6>a","Requirement","ECSS-E-ST-10_0790264",1,"Unchanged","The DJF shall contain the demonstration that the system design conforms to the requirements of the technical specification, and identify products which are reused (e.g. COTS)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<6>b","Requirement","ECSS-E-ST-10_0790265",1,"Unchanged","The DJF shall also provide the justification for the choice of architectural elements at the next lower level, or lower levels in case of system critical elements."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<6>c","Requirement","ECSS-E-ST-10_0790266",1,"Unchanged","Where requirements do not have their origin within any of the upper level technical specifications, these shall be justified. "]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<7>a","Requirement","ECSS-E-ST-10_0790267",1,"Unchanged","The DJF shall present the development activities (e.g. assessments, analyses, tests, and trade-offs) and the design drivers, which lead to and justify the design as defined in the DDF, in line with the development approach identified in the SEP."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<7>b","Requirement","ECSS-E-ST-10_0790268",1,"Unchanged","The justification shall concern all the engineering disciplines contributing to design and development of the product (including its operational modes and scenarios)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<7>c","Requirement","ECSS-E-ST-10_0790269",1,"Unchanged","The DJF shall include the status of DJF of lower level products.","NOTE\tActivities related to verification are dealt with in section K.2.1<8>.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<7>d","Requirement","ECSS-E-ST-10_0790270",1,"Unchanged","For the system and each discipline, following information shall be produced:\n1.\tActivity inputs, such as requirements, operational modes, assumptions, analysis cases, boundary conditions, model descriptions and limitations.\n2.\tActivity results, such as\n(a)\traw results,\n(b)\tevaluation of results,\n(c)\tevaluation of margins with respect to the technical requirements contained in the TS,\n(d)\tidentification of any marginal areas.\n3.\tActivity synthesis, such as\n(a)\tevidence of compliance to the technical requirements contained in the TS,\n(b)\tlist of technical requirements which have not been met, including proposed actions,\n(c)\tlist of all critical points, and how criticalities have been or are intended to be resolved,\n(d)\tidentification of aspects of the design, which are not yet justified, and assessment of inherent risks. "]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<7>e","Requirement","ECSS-E-ST-10_0790271",1,"Unchanged","The DJF shall reference the requirements traceability matrix, e.g. w.r.t. building up the justification of a considered system top level requirements in terms of the various elements contributing to it, including where relevant contribution from other disciplines (e.g. pointing as a function of thermal, structures, and AOCS)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<8.1>a","Requirement","ECSS-E-ST-10_0790272",1,"Unchanged","The DJF shall integrate or refer to the document that conforms to the verification plan DRD defined in ECSS-E-ST-10-02 Annex A.","NOTE\tThe verification activities are detailed in the Verification Plan (VP), which also contains the justification of the verification strategy (as defined in ECSS-E-ST-10-02).\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<8.2.1>a","Requirement","ECSS-E-ST-10_0790273",1,"Unchanged","The DJF shall present the evidence of the qualification of the design in conformance to the applicable technical requirements and proper qualification margins. ","NOTE\tThis is done in line with the qualification approach identified in the VP. \n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<8.2.1>b","Requirement","ECSS-E-ST-10_0790274",1,"Unchanged","The DJF shall cover the system and all disciplines relevant to the product in all its operational modes and scenarios, addressing all applicable technical requirements and proper qualification margins. ","NOTE 1\tThis is done in line with the system verification matrix. \nNOTE 2\tThe formal compliance with the qualification requirements is recorded in the VCD, together with references to the close-out documents.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<8.2.2>a","Requirement","ECSS-E-ST-10_0790275",1,"Unchanged","The DJF shall present the implementation of the qualification plan and the status thereof, addressing the detailed definition of qualification activities (e.g. analysis, test, ROD, and inspection), including the detailed definition of the tests, the prediction of expected test results, test success criteria, test specifications, and model validations.","NOTE\tDetails on test specifications are provided in ECSS-E-ST-10-03 Annex B.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<8.2.3>a","Requirement","ECSS-E-ST-10_0790276",1,"Unchanged","The DJF shall contain all evidence (e.g. analyses, test results, and model descriptions and correlations) regarding the suitability and validation of all models used for the analysis of the system."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<8.2.4>a","Requirement","ECSS-E-ST-10_0790277",1,"Unchanged","The DJF shall include a requirement status log addressing each requirement in turn, and including the\n1.\treference to relevant elements of the verification plan,\n2.\tsynthesis of the justifications acquired, calling up references to the supporting activities and evidence (e.g. Technical Notes listed in section K.2.1<4>),\n3.\tlist of justifications to be acquired and related activities,\n4.\tconclusion / action flag."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<8.2.5>a","Requirement","ECSS-E-ST-10_0790278",1,"Unchanged","The DJF shall include a requirement status log, addressing design relevant aspects of manufacturing processes, and recording their characteristics in regard to qualification."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<8.3>a","Requirement","ECSS-E-ST-10_0790279",1,"Unchanged","The DJF shall present the implementation of the acceptance verification and the status thereof, addressing the detailed definition of acceptance activities (e.g. inspection, test, analysis), including the detailed definition of the tests, the prediction of expected test results, test success criteria, and test specifications.","NOTE\tDetails on test specifications are provided in ECSS-E-ST-10-03 Annex B.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<8.3>b","Requirement","ECSS-E-ST-10_0790280",1,"Unchanged","The DJF shall cover the system and all disciplines relevant to the product, addressing all acceptance verification activities in line with the system verification Plan (VP)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<9>a","Requirement","ECSS-E-ST-10_0790281",1,"Unchanged","The DJF shall present a synthesis of all technical budgets and margins for specific parameters according to the functional and physical architectures.","NOTE\tFor technical budgets and margins, see ECSS-E-ST-10 Annex I.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<10.1>a","Requirement","ECSS-E-ST-10_0790282",1,"Unchanged","The DJF shall present the justification of constraints induced by the system or product design definition on the production activities e.g. operational allowable envelopes, restrictions on assembling sequences, procedures and testing modes, exclusion zones, manufacturing environmental conditions, and conditions for procurement."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<10.2>a","Requirement","ECSS-E-ST-10_0790283",1,"Unchanged","The DJF shall present the justification of constraints induced by the system or product design definition on the implementation of the operations e.g. operational allowable envelopes, restrictions on operating modes, and exclusion zones."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<10.3>a","Requirement","ECSS-E-ST-10_0790284",1,"Unchanged","The DJF shall present the justification of constraints induced by the system or product design definition on the transportation activities and during the periods of storage of the product e.g. allowable envelopes, restrictions on transportation and storage, exclusion zones, packaging, shock levels, temperature environments, humidity, cleanliness, regulations, and dangerous materials."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<10.4>a","Requirement","ECSS-E-ST-10_0790285",1,"Unchanged","The DJF shall present the justification of constraints induced by the system or product design definition on the maintenance activities and procedures e.g. operational allowable envelopes, accessibility, tooling, support materials, parts availability, and deliveries. "]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<11>a","Requirement","ECSS-E-ST-10_0790286",1,"Unchanged","The DJF shall integrate or refer to the documents that conform to the:\n1.\tECSS-E-ST-10 Annex L, Trade-Off-Report - DRD\n2.\tECSS-E-ST-10 Annex Q, Analysis Report - DRD\n3.\tECSS-E-ST-10 Annex O, Requirement Justification File - DRD\n4.\tECSS-E-ST-10 Annex N, Requirements Traceability Matrix - DRD\n5.\tECSS-E-ST-10-02 Annex B, Verification Control Document - DRD\n6.\tECSS-E-ST-10-02 Annex C, Test Report - DRD\n7.\tECSS-E-ST-10-02 Annex D, Review Of Design Report - DRD\n8.\tECSS-E-ST-10-02 Annex E, Inspection Report - DRD\n9.\tECSS-E-ST-10-02 Annex F, Verification Report - DRD"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","K.2.1<11>b","Requirement","ECSS-E-ST-10_0790287",1,"Unchanged","The DJF shall include or refer to the DJF of lower level elements of the product."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","L.2.1<1>a","Requirement","ECSS-E-ST-10_0790288",1,"Unchanged","The trade-off report shall contain a description of the purpose, objective, content and the reason prompting its preparation."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","L.2.1<2>a","Requirement","ECSS-E-ST-10_0790289",1,"Unchanged","The trade-off report shall list the applicable and reference documents in support to the generation of the document and include the reference to the following applicable documents:\n1.\tMission description document, if relevant\n2.\tTechnical requirements specification\n3.\tSystem engineering plan\n4.\tProject phasing and planning requirement document."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","L.2.1<3>a","Requirement","ECSS-E-ST-10_0790290",1,"Unchanged","The trade-off report shall contain a brief description of the purpose of the trade-off study and its context (e.g. logic, organization, process or procedure)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","L.2.1<4>a","Requirement","ECSS-E-ST-10_0790291",1,"Unchanged","The trade-off report shall list the key technical requirements from the TS (as defined in ECSS-E-ST-10-06) to be satisfied by the possible alternative design solutions to conform to the needs or requirements of the user."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","L.2.1<4>b","Recommendation","ECSS-E-ST-10_0790404",1,"Created","The research of possible alternative design solutions should not preclude the identification of design solutions which are not currently mature enough, but which can be potential design solution for future similar applications.","NOTE\tA possible design solution is a technical answer that has the capability to meet a set of technical requirements.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","L.2.1<4>c","Requirement","ECSS-E-ST-10_0790293",1,"Unchanged","The system trade-off report shall identify and present the sources of information used to identify the possible design solution, e.g. R&D results, lessons learned, or similar applications."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","L.2.1<5>a","Requirement","ECSS-E-ST-10_0790294",1,"Unchanged","The trade-off report shall list the selected evaluation criteria and precise the justification for selecting those criteria, and provide the weighting of criteria and their justifications.","NOTE\tThe criteria are selected theme by theme from the Technical Specification (as defined in ECSS-E-ST-10-06 Annex A), the programmatic aspects (including e.g. budget, schedule, etc… for development, manufacturing, as well as target cost for operations and recurrent items), and the technical risks.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","L.2.1<5>b","Requirement","ECSS-E-ST-10_0790295",1,"Unchanged","The trade-off report shall identify the entity responsible for the evaluation of the design solutions for any criteria, as well as the source and agreement regarding weighting factors (e.g. with management)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","L.2.1<6>a","Requirement","ECSS-E-ST-10_0790296",1,"Unchanged","The trade-off report shall present every different alternative design solutions proposed by the organization in charge of the development of the system or product, the proposals from the customer and supplier if any, and emphasize the technical description that is correlated to the criteria of evaluation. "]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","L.2.1<6>b","Requirement","ECSS-E-ST-10_0790297",1,"Unchanged","The trade-off report shall characterize each alternative design solution in terms of technology status or maturity, performances capability, and risks."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","L.2.1<7>a","Requirement","ECSS-E-ST-10_0790298",1,"Unchanged","The system trade-off report shall present the result of the evaluation of every identified alternative design solution with regard to the key technical requirements."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","L.2.1<7>b","Requirement","ECSS-E-ST-10_0790299",1,"Unchanged","For each alternative design solution the following shall be performed: \n1.\tassessment of all the key technical requirements / evaluation criteria,\n2.\tpresentation of the pros and cons of the design solution, and\n3.\tidentification of the technical and programmatic risks."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","L.2.1<7>c","Requirement","ECSS-E-ST-10_0790300",1,"Unchanged","The trade-off report shall present, in a table, the result of the evaluation per criteria."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","L.2.1<8>a","Requirement","ECSS-E-ST-10_0790301",1,"Unchanged","Based on the proposed scheme for weighting the evaluation criteria, the trade-off report shall provide a classification of the different alternative design solutions."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","L.2.1<9>a","Requirement","ECSS-E-ST-10_0790302",1,"Unchanged","The trade-off report shall provide the result of a sensitivity analysis of the criteria that provide advantage to the solution ranked first, e.g. when changing the weighting of the evaluation criteria. "]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","L.2.1<10>a","Requirement","ECSS-E-ST-10_0790303",1,"Unchanged","The trade-off report shall recommend one solution and explain the reason for this choice (e.g. evaluation criteria where the selected solution take advantage), and precise the condition for the application of the recommended solution."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","L.2.1<10>b","Requirement","ECSS-E-ST-10_0790304",1,"Unchanged","The trade-off report shall present the identified technical and programmatic risks induced by the choice of the recommended solution, and any additional activity necessary to be performed for risk mitigation."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","M.2.1<1>a","Requirement","ECSS-E-ST-10_0790305",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","M.2.1<2>a","Requirement","ECSS-E-ST-10_0790306",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","M.2.1<2>b","Requirement","ECSS-E-ST-10_0790307",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","M.2.1<3>a","Requirement","ECSS-E-ST-10_0790308",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","M.2.1<3>b","Requirement","ECSS-E-ST-10_0790309",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","M.2.1<3>c","Requirement","ECSS-E-ST-10_0790310",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","N.2.1<1>a","Requirement","ECSS-E-ST-10_0790312",1,"Unchanged","The RTM shall contain a description of the purpose, objective, content and the reason prompting its preparation."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","N.2.1<2>a","Requirement","ECSS-E-ST-10_0790313",1,"Unchanged","The RTM shall list the applicable and reference documents in support to the generation of the document."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","N.2.1<2>b","Requirement","ECSS-E-ST-10_0790314",1,"Unchanged","The RTM shall include the following:\n1.\tTechnical requirements specification (as defined in ECSS-E-ST-10-06 Annex A) of the product and its lower level elements\n2.\tProduct tree (as defined in ECSS-M-ST-10 Annex B)\n3.\tSpecification tree (as defined in ECSS-E-ST-10 Annex J)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","N.2.1<3>a","Requirement","ECSS-E-ST-10_0790315",1,"Unchanged","The RTM shall list all the technical requirement of the product TS."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","N.2.1<3>b","Requirement","ECSS-E-ST-10_0790316",1,"Unchanged","The RTM shall list all the lower level elements constituting the product and their technical requirements (contained in the lower-level element TS)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","N.2.1<3>c","Requirement","ECSS-E-ST-10_0790317",1,"Unchanged","The requirement identification shall be identical in the RTM and the different TS."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","N.2.1<3>d","Requirement","ECSS-E-ST-10_0790318",1,"Unchanged","Each technical requirement of the product shall be linked to at least one requirement of a lower level element.","NOTE\tThe required visibility of the traceability down the elements of the product tree is depending on the criticality of some lower level elements w.r.t. the product requirements.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","N.2.1<3>e","Recommendation","ECSS-E-ST-10_0790405",1,"Created","Each technical requirement of a lower level element should be linked to a technical requirement of the product."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","N.2.1<3>f","Requirement","ECSS-E-ST-10_0790320",1,"Unchanged","When a technical requirement of a lower level element is not linked to a technical requirement of the product, this requirement shall be justified and an evaluation of its existence or removal on the product shall be agreed between the customer and the supplier."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","O.2.1<1>a","Requirement","ECSS-E-ST-10_0790321",1,"Unchanged","The RJF shall contain a description of the purpose, objective, content and the reason prompting its preparation."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","O.2.1<2>a","Requirement","ECSS-E-ST-10_0790322",1,"Unchanged","The RJF shall list the applicable and reference documents in support to the generation of the document."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","O.2.1<2>b","Requirement","ECSS-E-ST-10_0790323",1,"Unchanged","The RJF shall include the reference to the technical requirements specification."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","O.2.1<3>a","Requirement","ECSS-E-ST-10_0790324",1,"Unchanged","The RJF shall present the rationale for the selection of a concept for the technical requirements specification.","NOTE\tFor justification, reference can be made to the system concept report of the considered project.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","O.2.1<4>a","Requirement","ECSS-E-ST-10_0790325",1,"Unchanged","The RJF shall present and justify the life profile situations for the concept presented in the technical requirements specification.","NOTE\tFor justification, reference can be made to the system concept report of the considered project where relevant.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","O.2.1<5>a","Requirement","ECSS-E-ST-10_0790326",1,"Unchanged","The RJF shall present and justify the different environments and constraints for each life profile situations for the concept presented in the technical requirements specification.","NOTE\tFor justification, reference can be made to the system concept report of the considered project where relevant.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","O.2.1<6>a","Requirement","ECSS-E-ST-10_0790327",1,"Unchanged","The RJF shall list all the technical requirements, and their identifier, expressed by the corresponding TS as they are organized in these documents. "]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","O.2.1<6>b","Requirement","ECSS-E-ST-10_0790328",1,"Unchanged","For each technical requirement the following information shall be provided:\n1.\tthe justification of the requirement (i.e. justified source),\n2.\tthe Entity or owner responsible for the requirement,\n3.\tif one technical requirement is induced by several sources, the reason of the specified performance,\n4.\tthe justification of the quantified performance (such as the range, the approach used to determine the level, e.g. measure, estimation), \n5.\tthe justification of the selected verification method."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","O.2.1<7>a","Requirement","ECSS-E-ST-10_0790329",1,"Unchanged","The RJF shall present the requirement traceability between the technical requirements of the TS, and their justified source."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","O.2.1<8>a","Requirement","ECSS-E-ST-10_0790330",1,"Unchanged","For COTS, the RJF shall contain a compliance matrix between the technical specification/characteristics of the COTS and the technical requirement expressed by the TS."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","O.2.2a","Permission","ECSS-E-ST-10_0790406",1,"Created","The RJF may be part of the design justification file (DJF) (as defined in ECSS-E-ST-10 Annex K)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<1>a","Requirement","ECSS-E-ST-10_0790332",1,"Unchanged","The introduction shall describe the purpose and objective of the PUM."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<2>a","Requirement","ECSS-E-ST-10_0790333",1,"Unchanged","The PUM shall list the applicable and reference documents in support of the generation of the document."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<3.1>a","Requirement","ECSS-E-ST-10_0790334",1,"Unchanged","The PUM shall provide a general description of the expected functions of the product during its lifetime in expected operational context and environment."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<3.2>a","Requirement","ECSS-E-ST-10_0790335",1,"Unchanged","The PUM shall describe all product functional constraints."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<3.3>a","Requirement","ECSS-E-ST-10_0790336",1,"Unchanged","The PUM shall address the whole product life cycle and all its modes: \n1.\tHandling\n2.\tStorage\n3.\tInstallation\n4.\tOperations (nominal and contingency)\n5.\tMaintenance\n6.\tDisposal."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<3.3>b","Requirement","ECSS-E-ST-10_0790337",1,"Unchanged","The PUM shall consider potential consequences of the environment on those sequences (e.g. sensor blinding, eclipses);"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.1>a","Requirement","ECSS-E-ST-10_0790338",1,"Unchanged","The PUM shall include the following:\n1.\tsummary of the product design, showing the definition of the product, its constituents, the distribution of functions and the major interfaces;\n2.\tblock diagram of the product;\n3.\ttop-level description of the product software architecture;\n4.\tdescription of nominal product operations scenarios and constraints e.g. mutually exclusive modes of operation, power or resource sharing."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.2>a","Requirement","ECSS-E-ST-10_0790339",1,"Unchanged","The PUM shall include the following:\n1.\tdescription of product-level autonomy provisions in the areas of fault management (FDIR);\n2.\tdefinition, for each autonomous function, of the logic or rules used and of its internal (product constituents) and external interfaces. "]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.3>a","Requirement","ECSS-E-ST-10_0790340",1,"Unchanged","The PUM shall include the following:\n1.\tdrawings of the overall product configuration in all product modes;\n2.\tdefinition of the product reference axes system(s);\n3.\tdrawings of the product layouts."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.4>a","Requirement","ECSS-E-ST-10_0790341",1,"Unchanged","The PUM shall provide the distribution (or allocation) of the following budgets, per product constituent, or per operating mode, as appropriate:\n1.\tmass properties;\n2.\talignment;\n3.\tpower consumption for all operational modes;\n4.\tthermal budget and constraints and predictions;\n5.\tDescription of interfaces and related budgets. (e.g. RF links);\n6.\ttelemetry and telecommand date rates;\n7.\tmemory;\n8.\ttiming."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.5>a","Requirement","ECSS-E-ST-10_0790342",1,"Unchanged","The PUM shall provide a cross-reference to the applicable version of the ICD."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.6>a","Requirement","ECSS-E-ST-10_0790343",1,"Unchanged","The PUM shall describe the conditions and procedures for the handling of the product, be it integrated or stand-alone."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.6>b","Requirement","ECSS-E-ST-10_0790344",1,"Unchanged","The PUM shall describe the specific design features, transport and environmental conditions, required GSE, and limitations for the handling of the product."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.7>a","Requirement","ECSS-E-ST-10_0790345",1,"Unchanged","The PUM shall describe the conditions and procedures for the storage of the product, be it integrated or stand-alone."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.7>b","Requirement","ECSS-E-ST-10_0790346",1,"Unchanged","The PUM shall describe the specific design features, environmental conditions, required GSE, monitoring requirements, life-limited items, health maintenance procedures (activation, monitoring) and limitations for the storage of the product."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.8>a","Requirement","ECSS-E-ST-10_0790347",1,"Unchanged","The PUM shall describe the conditions and procedures for the installation of the product, be it integrated or stand-alone."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.8>b","Requirement","ECSS-E-ST-10_0790348",1,"Unchanged","The PUM shall describe the specific design features, required GSE, modes, environmental conditions, and limitations for the installation of the product."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.9.1>a","Requirement","ECSS-E-ST-10_0790349",1,"Unchanged","The PUM shall include timelines, modes and procedures, constraints to operate the product during its life cycle in nominal and contingency conditions, and highlight critical operations.","NOTE 1\tWhen the product is a space segment, the product operations aspects are included in a specific part of the UM called Flight Operations Manual (FOM).\nNOTE 2\tThe implementation of the FOM by the ground segment responsible organisation is contained in the Mission Operations Plan (MOP, as defined in ECSS-E-ST-70 Annex G).\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.9.2>a","Requirement","ECSS-E-ST-10_0790350",1,"Unchanged","The PUM shall include:\n1.\tBaseline event timelines for all nominal and contingency modes and phases.\n2.\tRelated constraints."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.9.2>b","Requirement","ECSS-E-ST-10_0790351",1,"Unchanged","Each timeline shall contain a detailed description (i.e. down to the level of each single operational action) of the complete sequence of operations to be carried out, including a description of the rationale behind the chosen sequence of events, a definition of any constraints (e.g. absolute timing, relative timing) and the interrelationships between operations in the sequence."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.9.3>a","Requirement","ECSS-E-ST-10_0790352",1,"Unchanged","The PUM shall describe all nominal and contingency modes, including:\n1.\ttheir purpose (i.e. circumstances under which they are used),\n2.\tthe related procedures,\n3.\toperational constraints,\n4.\tresource utilization,\n5.\tthe definition of the associated modes, and\n6.\tmonitoring requirements."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.9.3>b","Requirement","ECSS-E-ST-10_0790353",1,"Unchanged","The PUM shall describe the allowable mode transitions and the operations procedure corresponding to each such transition."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.9.3>c","Requirement","ECSS-E-ST-10_0790354",1,"Unchanged","Appropriate cross-reference shall be made to product constituent modes and procedures."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.9.4>a","Requirement","ECSS-E-ST-10_0790355",1,"Unchanged","The PUM shall provide the results of the product failure modes, effects and criticality analysis (FMECA) and the resulting list of single point failures."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.9.4>b","Requirement","ECSS-E-ST-10_0790356",1,"Unchanged","Potential product failures shall be identified by means of a fault-tree analysis (FTA)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.10>a","Requirement","ECSS-E-ST-10_0790357",1,"Unchanged","The PUM shall describe the conditions, procedures and logistics for the maintenance of the product, be it integrated or stand-alone.","NOTE\tThe description can refer to the document that conforms to the Integrated Logistic Support Plan in conformance with ECSS-M-ST-70.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.11>a","Requirement","ECSS-E-ST-10_0790358",1,"Unchanged","The PUM shall describe the conditions and procedures for the disposal of the product, be it integrated or stand-alone."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.11>b","Requirement","ECSS-E-ST-10_0790359",1,"Unchanged","The procedures shall include passivation, as relevant."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<4.11>c","Requirement","ECSS-E-ST-10_0790360",1,"Unchanged","The PUM shall identify the risks during and after disposal."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<5.1>a","Requirement","ECSS-E-ST-10_0790361",1,"Unchanged","The information specified in P.2.1<5.2> to P.2.1<5.9> shall be provided for each product constituent."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<5.2>a","Requirement","ECSS-E-ST-10_0790362",1,"Unchanged","The PUM shall describe the product constituent including:\n1.\tthe overall functions of the product constituent and the definition of its operational modes during the different mission phases;\n2.\tdescription of any product constituent management functions, fault management concept and redundancy provisions;\n3.\ta summary description of the component units/equipment and software including the functions which each supports;\n4.\tproduct constituent functional block diagrams and a diagram showing the source of telemetry outputs and the sink of telecommand inputs;\n5.\tinterfaces;\n6.\tbudgets."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<5.3>a","Requirement","ECSS-E-ST-10_0790363",2,"Normative Change","The following shall be provided for each product constituent:\n1.\ta detailed design description, including block diagrams, functional diagrams, logic and circuit diagrams;\n2.\tphysical characteristics including location and connections to the support structure, axes definition and alignment where relevant, dimensions and mass properties;\n3.\tprinciple of operation and operational constraints of the product constituent;\n4.\tlower level of breakdown for products composed of many complex elements."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<5.4>a","Requirement","ECSS-E-ST-10_0790364",1,"Unchanged","The PUM shall include:\n1.\tdescription of software design,\n2.\tproduct constituent software,\n3.\tapplication process service software, and\n4.\tmemory map."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<5.4>b","Requirement","ECSS-E-ST-10_0790365",1,"Unchanged","The PUM shall describe the organization of the software and its physical mapping onto hardware."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<5.4>c","Requirement","ECSS-E-ST-10_0790366",1,"Unchanged","The PUM shall describe the details of each software component i.e. scheduler, interrupt handler, I/O system, telecommand packet handling system, telemetry packet handling system, including for each component its functions, component routines, input/output interfaces, timing and performance characteristics, flowcharts and details of any operational constraints."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<5.4>d","Requirement","ECSS-E-ST-10_0790367",1,"Unchanged","For the application process service software, the PUM shall:\n1.\tdescribe the services implemented making cross-reference to ECSS-E-ST-70-41 “Telemetry and telecommand packet utilization”, as tailored for the mission;\n2.\tsummarize all telemetry and telecommand structures (e.g. packets) including the conditions under which they are generated, the generation frequency, content and interpretation."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<5.4>e","Requirement","ECSS-E-ST-10_0790368",1,"Unchanged","For each memory block, a map shall be provided showing RAM and ROM address areas, areas allocated for program code, buffer space and working parameters (e.g. content of protected memory)."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<5.5>a","Requirement","ECSS-E-ST-10_0790369",1,"Unchanged","The PUM shall describe all relevant product constituent performance characteristics, define the expected performance degradation as a function of time during the mission, and identify the resulting impact in terms of modifications to operational requirements or constraints."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<5.6>a","Requirement","ECSS-E-ST-10_0790370",1,"Unchanged","For each product constituent, the following lists shall be provided:\n1.\ta list of the housekeeping telemetry parameters;\n2.\ta list of the telecommands."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<5.6>b","Requirement","ECSS-E-ST-10_0790371",1,"Unchanged","Each housekeeping telemetry shall have a functional description with validity conditions, telecommand relationship, and all technical information necessary for using it."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<5.6>c","Requirement","ECSS-E-ST-10_0790372",1,"Unchanged","Each telecommand shall have a functional description with utilization conditions (e.g. pre-transmission validity, criticality level), command parameters (syntax and semantics) and execution verification in telemetry."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<5.7>a","Requirement","ECSS-E-ST-10_0790373",1,"Unchanged","The PUM shall describe:\n1.\tIdentification of potential product constituent failures by means of a systematic failure analysis (including a subsystem FMECA and FTA).\n2.\tIdentification of the methods by which the higher levels can identify a failure condition from analysis of the telemetry data and isolate the source of the failure."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<5.8>a","Requirement","ECSS-E-ST-10_0790374",1,"Unchanged","The PUM shall describe:\n1.\tproduct constituent modes;\n2.\tnominal operational procedures;\n3.\tcontingency procedures."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<5.8>b","Requirement","ECSS-E-ST-10_0790375",1,"Unchanged","product constituent modes shall be defined for all distinct nominal and back-up modes of the subsystem including:\n1.\tpurpose (i.e. conditions under which each is used);\n2.\toperational constraints;\n3.\tresource utilization;\n4.\tthe definition of the associated modes for each product constituent and its software functions;\n5.\thigher level monitoring requirements;\n6.\tidentification of the allowable mode transitions and any product constituent operational constraints."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<5.8>c","Requirement","ECSS-E-ST-10_0790376",1,"Unchanged","Nominal operational procedures shall be defined for each nominal mode transition identified under P.2.1<5.8>b.6."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<5.8>d","Requirement","ECSS-E-ST-10_0790377",1,"Unchanged","For each procedure described in P.2.1<5.8>c., the following shall be provided:\n1.\tan introduction describing the purpose of the procedure and the phase(s) or conditions when applicable;\n2.\tthe body of the procedure, structured according to operational steps, including:\n(a)\tpre-conditions for the start of the step defining, where applicable:\n-\tproduct or product constituent level pre-requisites (e.g. configuration and resource requirements, such as power, fuel);\n-\texternal interfacing products pre-requisites.\n(b)\ttelecommands to be sent;\n(c)\ttelemetry data to be monitored to verify correct execution of the step;\n(d)\tinterrelationships between steps (e.g. conditional branching within the procedure, timing requirements or constraints, hold and check points);\n(e)\tconditions for completion of the step."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<5.8>e","Requirement","ECSS-E-ST-10_0790378",1,"Unchanged","Contingency procedures shall be defined for each failure case identified in the product constituent failure analysis (FMECA/FTA).","NOTE\tThis can utilize a nominal operational procedure already identified in P.2.1<5.8>c. above.\n"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<5.8>f","Requirement","ECSS-E-ST-10_0790379",1,"Unchanged","For contingency procedures, the same details shall be provided as for nominal operational procedures in P.2.1<5.8>d. above."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<5.8>g","Requirement","ECSS-E-ST-10_0790380",1,"Unchanged","Where the recovery method for a failure or group of failures is mode, mission, or phase dependent, separate procedures shall be described for each mode/mission phase."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<5.9>a","Requirement","ECSS-E-ST-10_0790381",1,"Unchanged","For each operational mode of the product constituent, sensor output data, conditions under which they are generated, their contents, and data rate shall be described."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.1<5.9>b","Requirement","ECSS-E-ST-10_0790382",1,"Unchanged","Required on-board processing performed on sensor data and algorithms used for this shall be described."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0","P.2.2a","Requirement","ECSS-E-ST-10_0790383",1,"Unchanged","Where the objective is to allow for the accommodation of equipment designed a posteriori w.r.t an existing platform or vehicle, the following documents shall be part of the UM: \n1.\tThe accommodation handbook describing the location, mounting, all interfaces and clearances of equipment in a platform or vehicle.\n2.\tThe installation plan describing the approach, methods, procedures, resources and organization to install, commission, and check the operation of the equipment in its fixed operational environment."]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0",null,"Requirement","ECSS-E-ST-10_0790384",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0",null,"Requirement","ECSS-E-ST-10_0790385",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0",null,"Requirement","ECSS-E-ST-10_0790386",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0",null,"Requirement","ECSS-E-ST-10_0790387",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0",null,"Requirement","ECSS-E-ST-10_0790388",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0",null,"Requirement","ECSS-E-ST-10_0790389",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0",null,"Requirement","ECSS-E-ST-10_0790390",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0",null,"Requirement","ECSS-E-ST-10_0790391",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0",null,"Requirement","ECSS-E-ST-10_0790392",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-10C Rev.1","ECSS - Current v1.0",null,"Requirement","ECSS-E-ST-10_0790393",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.1a","Requirement","ECSS-E-ST-20-01_1450001",1,"Created","The process of verification of the equipment with respect to multipactor performance shall demonstrate conformance to the margin requirements defined in clauses 4.6 and 4.7."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.1b","Requirement","ECSS-E-ST-20-01_1450002",1,"Created","Verification of the equipment with respect to multipactor shall be performed as part of the overall verification process specified in ECSS-E-ST-10-02, by applying Table 4-1."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.1c","Requirement","ECSS-E-ST-20-01_1450003",1,"Created","Each equipment shall have a dedicated multipactor verification plan as specified in 4.2.2a. ","NOTE\tIt can involve a combination of design analyses, inspections, development testing, qualification testing, batch acceptance testing and equipment or component acceptance testing.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.1d","Requirement","ECSS-E-ST-20-01_1450004",1,"Created","Multipactor performance shall be verified at equipment level."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.1e","Permission","ECSS-E-ST-20-01_1450005",1,"Created","If multipactor performance cannot be verified at equipment level, as specified in 4.1d, then verification may be performed at component level."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.1f","Requirement","ECSS-E-ST-20-01_1450006",1,"Created","The process of verification of the component with respect to multipactor performance shall demonstrate conformance to the margin requirements defined in clauses 4.6 and 4.7."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.1g","Requirement","ECSS-E-ST-20-01_1450007",1,"Created","Verification of the component with respect to multipactor shall be performed as part of the overall verification process specified in ECSS-E-ST-10-02, by applying Table 4-1."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.1h","Requirement","ECSS-E-ST-20-01_1450008",1,"Created","Each component shall have a dedicated multipactor verification plan as specified in 4.2.2a. ","NOTE\tIt can involve a combination of design analyses, inspections, development testing, qualification testing, batch acceptance testing and equipment or component acceptance testing.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.1i","Requirement","ECSS-E-ST-20-01_1450009",1,"Created","Multipactor performance shall be verified at component level."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.2.1a","Requirement","ECSS-E-ST-20-01_1450011",1,"Created","A multipactor verification plan shall be produced at EQSR and, if necessary, updated at the PDR and the CDR at the latest."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.2.1b","Requirement","ECSS-E-ST-20-01_1450012",1,"Created","The multipactor verification plan specified in 4.2.2a shall be kept up-to-date and under configuration control.","NOTE\tThe detailed verification plan adopted for any particular project can depend on the qualification status of the equipment and on the model philosophy or production philosophy adopted.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.2.1c","Requirement","ECSS-E-ST-20-01_1450013",1,"Created","The inputs for the multipactor verification plan shall include as a minimum:\n1.\tequipment or component requirements specification,\n2.\tproposed design,\n3.\tequipment or the component qualification status as per Table 4-1,\n4.\tequipment or component type as per Table 4-2."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.2.2a","Requirement","ECSS-E-ST-20-01_1450014",1,"Created","The multipactor verification plan shall be in conformance with the Verification Plan DRD specified in Annex A of ECSS-E-ST-10-02 plus the following items:\n1.\tthe verification route as per Figure 4-1: ,\n2.\tlist of the multipactor deliverable documents per review,\n3.\tdescription of tests or analysis to be performed.","NOTE\tThe list of Multipactor deliverable documents is given in Table A-1.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.2.2b","Requirement","ECSS-E-ST-20-01_1450015",1,"Created","The multipactor verification plan shall present a coherent sequence of activities that are proposed in order to provide adequate evidence that the requirement specifications for the product are achieved for each delivered item."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.2.2c","Requirement","ECSS-E-ST-20-01_1450016",1,"Created","The multipactor verification plan shall state the criteria for successful completion of each of the verification activities."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.3.1.1a","Requirement","ECSS-E-ST-20-01_1450017",1,"Created","The nominal power shall be the specified input power for which the equipment or component is designed and verified to be multipactor free."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.3.1.1b","Requirement","ECSS-E-ST-20-01_1450018",1,"Created","The nominal power shall be the RF power level to which the analysis margin and test margin refers."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.3.1.1c","Requirement","ECSS-E-ST-20-01_1450019",1,"Created","The nominal power specified at equipment or component level shall exclude RF boundary conditions, neither from payload assembly nor from test bed.","NOTE\tThe nominal power for multicarrier signal can be given as power per carrier, or a list of power per carrier.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.3.1.2a","Requirement","ECSS-E-ST-20-01_1450020",1,"Created","The increased power DP of the Table 4-3, Table 4-4, Table 4-6 and Table 4-7 shall be calculated including the mismatch at the RF boundaries of the equipment or the component.","NOTE\tFurther details can be found in the Handbook ECSS-E-HB-20-01A.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.3.1.3a","Requirement","ECSS-E-ST-20-01_1450021",1,"Created","At payload level, the design and the verification of the equipment or component identified as critical shall include failure modes."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.3.1.3b","Requirement","ECSS-E-ST-20-01_1450022",1,"Created","As a minimum, the failure modes shall include the following:\n1.\tfailed equipment \n2.\thot switching \n3.\toverdrive scenario \n4.\tunexpected thermal variations\n5.\tunexpected full or partial RF power reflection\n6.\tunexpected increase of input power"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.3.1.3c","Requirement","ECSS-E-ST-20-01_1450023",1,"Created","For multipactor design and verification, the failures modes shall be included only if the equipment recovery is possible."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.3.1.3d","Recommendation","ECSS-E-ST-20-01_1450024",1,"Created","For multipactor design and verification, failure modes that are not recoverable should not be taken."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.3.1.3e","Requirement","ECSS-E-ST-20-01_1450025",1,"Created","At equipment or component level, the multipactor design and verification shall include the impact of the applicable failure modes identified at payload level. "]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.3.1.3f","Requirement","ECSS-E-ST-20-01_1450026",1,"Created","The increased power DP shall be determined by taking the change of RF boundary conditions due to the failure mode that yields the worst case among the ones defined in 4.3.1.3c."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.4.1a","Requirement","ECSS-E-ST-20-01_1450027",1,"Created","The classification of equipment or component types given in Table 4-1 and in Table 4-2 shall be used to determine the applicable multipactor margin.","NOTE\tThis requirement defines a classification of equipment or component types according to the materials employed in the construction and the geometry and according to the qualification status from a multipactor point of view.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.4.1b","Requirement","ECSS-E-ST-20-01_1450028",1,"Created","In case of doubt when determining the classification of any particular equipment or component, the type with a higher number and a lower level of qualification status shall be used."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.4.1c","Requirement","ECSS-E-ST-20-01_1450029",1,"Created","An equipment consisting of several components shall have the type of the component with the highest number and the lowest level of qualification status."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.4.1d","Requirement","ECSS-E-ST-20-01_1450030",1,"Created","An RF equipment assembly consisting of equipment shall have the type of the equipment with the highest number and the lowest level of qualification status."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.4.1e","Requirement","ECSS-E-ST-20-01_1450031",1,"Created","In case the equipment or component has multiple potential critical gaps of different nature, each one shall be classified as P1 or P2 and follow the verification approach as defined in 4.2.","NOTE\tExamples of potential critical gaps of different nature are metal/metal, metal/dielectric or dielectric/dielectric.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.4.1f","Requirement","ECSS-E-ST-20-01_1450032",1,"Created","In case SEY characterization of materials present in an equipment or component including dielectrics materials is not performed, it shall be considered as P3 equipment or component."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.5a","Requirement","ECSS-E-ST-20-01_1450034",1,"Created","Verification shall be accomplished by one of the verification routes shown in Figure 4-1."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.6.2.1a","Requirement","ECSS-E-ST-20-01_1450036",1,"Created","The Multipactor analysis shall be performed following one of the two possible design analysis levels, L1 and L2, as per clause 5.3.2."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.6.2.2a","Requirement","ECSS-E-ST-20-01_1450037",1,"Created","The nominal margins shown in Table 4-3 and Table 4-4 for the different contributions and equipment or component types according to the heritage shall be applied."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.6.2.2b","Permission","ECSS-E-ST-20-01_1450038",1,"Created","The reduced margins, as indicated in Table 4-3 and Table 4-4, may be used if justification is given by the supplier.","NOTE\tThe nominal and reduced margins as indicated in Table 4-3 and Table 4-4 include modelling error.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.6.3.1a","Requirement","ECSS-E-ST-20-01_1450041",1,"Created","The test margin shall be defined according to the equipment or component type and the heritage."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.6.3.1b","Requirement","ECSS-E-ST-20-01_1450042",1,"Created","The test margins as shown in Table 4-5 shall be applied. ","NOTE\tMargins shown in Table 4-5 are those for a payload mismatch of -12 dB. Further discussions regarding the payload mismatch can be found in the Multipactor handbook ECSS-E-HB-20-01.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.6.3.1c","Requirement","ECSS-E-ST-20-01_1450043",1,"Created","Any deviation from requirement 4.6.3.1b shall be proposed by the supplier and agreed with the customer."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.6.3.1d","Requirement","ECSS-E-ST-20-01_1450044",1,"Created","Multipactor tests shall be conducted at the temperature range defined in clause 6.3. "]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.6.3.1e","Permission","ECSS-E-ST-20-01_1450045",1,"Created","For P1 equipment or component of type Bm and Cm, the test at ambient temperature may be performed if justifications are provided of the non-impact of temperature over any parameter affecting the breakdown threshold.","NOTE\tDiscussions regarding test at ambient can be found in the Multipactor handbook ECSS-E-HB-20-01.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.7.2.1a","Requirement","ECSS-E-ST-20-01_1450047",1,"Created","The Multipactor analysis shall be performed following one of the two possible levels L1 and L2 as per clause 5.3.2."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.7.2.2a","Requirement","ECSS-E-ST-20-01_1450048",1,"Created","The nominal margins shown in Table 4-6 and Table 4-7 for the different contributions and equipment or component types according to the heritage shall be applied in addition to the nominal power."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.7.2.2b","Permission","ECSS-E-ST-20-01_1450049",1,"Created","The reduced margins as indicated in Table 4-6 and Table 4-7 may be used if justification is given by the supplier and agreed by the customer","NOTE\tThe nominal and reduced margins as indicated in Table 4-6 and Table 4-7 include modelling error.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.7.3.1a","Requirement","ECSS-E-ST-20-01_1450052",1,"Created","The test margin shall be defined according to the equipment or component type and the heritage."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.7.3.1b","Requirement","ECSS-E-ST-20-01_1450053",1,"Created","The test margins as shown in Table 4-8 shall be applied for test performed in single carrier with an equivalent single carrier CW power determined in 6.4.3.2.","NOTE\t1\tMargins shown in Table 4-8 are those for a payload mismatch of -12 dB.\nNOTE\t2\tIf a single carrier test is not possible, see requirement 6.4.3.1b.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.7.3.1c","Requirement","ECSS-E-ST-20-01_1450054",1,"Created","Any deviation from Table 4-8 shall be proposed by the supplier and agreed with the customer."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.7.3.1d","Requirement","ECSS-E-ST-20-01_1450055",1,"Created","Multipactor tests shall be conducted at the temperature range defined in the clause 6.3. "]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","4.7.3.1e","Permission","ECSS-E-ST-20-01_1450056",1,"Created","For P1 equipment or component of type B and C, the test at ambient temperature may be performed if justifications are provided of the non-impact of temperature over any parameter affecting the breakdown threshold.","NOTE\tDiscussions regarding test at ambient can be found in the Multipactor handbook ECSS-E-HB-20-01.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.2a","Requirement","ECSS-E-ST-20-01_1450058",1,"Created","An analysis of the electromagnetic fields within the complete equipment or component shall be performed before establishing the worst case multipactor threshold under the specified conditions.","NOTE\t1\tMultipactor analysis is performed with a proper understanding of the electric fields within the whole equipment or component.\nNOTE\t2\tSpecified conditions include parameters such as operational frequency bandwidth, temperature extremes, mismatch conditions, which are applicable to the equipment or component.\nNOTE\t3\tField analysis without electron tracking solver and surface modelling is used in L1 analysis as described in 5.3.2.2.\nNOTE\t4\tField analysis with electron tracking solver and surface modelling is used in L2 analysis described in 5.3.2.3.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.2b","Requirement","ECSS-E-ST-20-01_1450059",1,"Created","The analysis shall be accomplished by using one of the following methods:\n1.\tRF EM software, \n2.\testimations from the appropriate use of equivalent circuit models, \n3.\tanalytical solution of canonical geometries."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.2c","Requirement","ECSS-E-ST-20-01_1450060",1,"Created","All regions shall be analyzed to identify the multipactor critical gap."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.2d","Requirement","ECSS-E-ST-20-01_1450061",1,"Created","If ferrite materials are present in the equipment or component the following two analyses shall be performed:\n1.\tan EM field analysis based on the knowledge of the magnetic properties of such ferrite materials, and\n2.\ta multipactor analysis including the DC magnetic field applied to the ferrite.","NOTE\tDC magnetic fields applied to ferrite equipment or components include permanent magnets and coils.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.1a","Requirement","ECSS-E-ST-20-01_1450062",1,"Created","The Multipactor design analysis shall be performed at the frequency within the full bandwidth, at which the EM fields yield the lowest breakdown power."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.1b","Requirement","ECSS-E-ST-20-01_1450063",1,"Created","For multicarrier analysis, the carrier frequencies of each of the specified channels shall be used.","NOTE\tCarrier frequency is chosen for multicarrier analysis in order to obtain representative signal envelope characteristics.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.1a","Requirement","ECSS-E-ST-20-01_1450064",1,"Created","Design analysis shall be applied to equipment or components P1 and P2, according to clause 4.6.2 for single carrier and clause 4.7.2 for multicarrier."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.1b","Requirement","ECSS-E-ST-20-01_1450065",1,"Created","The level of analysis shall be selected and performed according to Table 4-3 and Table 4-4 for single carrier analysis and to Table 4-6 and Table 4-7 for multi-carrier analysis."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.1c","Requirement","ECSS-E-ST-20-01_1450066",1,"Created","Depending on the design analysis level, margin shall be adequately applied according to clause 4.6.2.2 or 4.7.2.2."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.2.1a","Requirement","ECSS-E-ST-20-01_1450067",1,"Created","Analysis level 1 shall be applied on equipment or components of type P1."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.2.2a","Requirement","ECSS-E-ST-20-01_1450068",1,"Created","The critical gap shall be similar to a parallel surface or coaxial geometry, and the electron trajectory is only possible between two-surfaces."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.2.2b","Requirement","ECSS-E-ST-20-01_1450069",1,"Created","The material, in terms of SEY, shall be selected according to criteria specified in clause 5.3.3.3 "]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.2.2c","Permission","ECSS-E-ST-20-01_1450070",1,"Created","In case the analysis includes fringing field effect for iris-like geometries, then analyses may be modified based on relevant heritage or studies on such effect if agreed between the supplier and customer on the degree of similarity of the proposed studies.","NOTE\tFringing field effect can increase the multipactor threshold power level (see respective clause in the Multipactor handbook ECSS-E-HB-20-01).\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.2.3a","Requirement","ECSS-E-ST-20-01_1450071",1,"Created","The analysis level 1 with single-carrier signals shall consist of the following steps:\n1.\tComputation of the voltage inside the critical region, Vgap, through analytical formula or an electromagnetic software, for a given input power Pin, using the definition of the voltage to power ratio as  \n2.\tComputation of the multipactor threshold at the corresponding frequency gap distance product, by either:\n(a)\tusing one of the dedicated charts for the list of ECSS materials of clause 5.3.3.4, or\n(b)\tusing a multipactor theory or numerical method for parallel surfaces or coaxial geometry. \n3.\tComputation of input power corresponding to the Multipactor threshold voltage computed in point b as  ","NOTE\tThe voltage to power ratio of item 1 is equivalent to the voltage magnification factor defined in the handbook.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.2.3b","Requirement","ECSS-E-ST-20-01_1450072",1,"Created","The customer and supplier shall agree on the method to follow regarding requirement 5.3.2.2.3a.2."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.2.3c","Permission","ECSS-E-ST-20-01_1450073",1,"Created","Different analysis methodologies may be used in agreement with the customer."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.2.3d","Requirement","ECSS-E-ST-20-01_1450074",1,"Created","The resulting threshold shall be compared with the nominal power increased with the dedicated margin of Table 4-3 and Table 4-4."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.2.4a","Requirement","ECSS-E-ST-20-01_1450075",1,"Created","The analysis level 1with multi-carrier signals shall consist of the following steps:\n1.\tComputation of the voltage inside the critical region, Vgap, through analytical formula or an electromagnetic software, for a given input power Pin, giving the EM fields solved for a frequency equal to the mean frequency of all carriers and using the definition of the voltage to power ratio as  ","NOTE\tThis ratio is equivalent to the voltage magnification factor defined in the Multipactor handbook ECSS-E-HB-20-01.\n1.\tCompute the breakdown voltage threshold per carrier by either:\n(a)\tUsing the pulsed model approximation in combination with single-carrier analysis. \n(b)\tUsing the envelope sweep approach in combination with a full multicarrier multipactor theory or numerical method for L1, to find the worst-case pulse width that leads to the minimum breakdown power.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.2.4b","Requirement","ECSS-E-ST-20-01_1450076",1,"Created","The pulsed model approximation, specified in 5.3.2.2.4a.2(a), shall consist of the following steps:\n1.\tApproximate the multicarrier signal by a pulsed signal, consisting of an on-off rectangular signal, with a frequency of the signal equal to the mean frequency of all carriers, and a period equal to that of the envelope of the multicarrier signal.\n2.\tSelect the single carrier multipactor theory employed in item 3 in agreement with the customer that allows for analytically computing the electron growth during the \"on\" interval, and electron absorption during the \"off\" interval.\n3.\tCompute the electron growth during a period by employing the theory selected in item 2.\n4.\tSelect the worst-case as the combination of the duration and amplitude of the pulse, that produces a discharge with the lowest voltage per carrier, by:\n(a)\tUsing the long-term discharge criterion, where the number of produced electrons is higher than the number of absorbed electrons during a period of the multicarrier signal.\n(b)\tDetermining the computation of the voltage per carrier, given the amplitude of the pulse, by the use of a multicarrier envelope fitting function.","NOTE\tSpecific analytical formulas, methodology and different envelope fitting functions are given in the Multipactor handbook ECSS-E-HB-20-01.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.2.4c","Requirement","ECSS-E-ST-20-01_1450077",1,"Created","The envelope sweep, specified in 5.3.2.2.4a.2(b), shall consist of the computation of the Multipactor threshold voltage per carrier given by a full-multicarrier multipactor theory or numerical method for parallel plates, as follows:.\n1.\tSelection of M different time intervals of duration ti, i varying from 1 to M, in order to fully cover the duration range between 0 and T, where T is the multi-carrier envelop period by ensuring that the number of time intervals is large enough for the convergence.\n2.\tOptimization of the carrier phases for each value of ti in order to maximize the minimum value of the envelope voltage amplitude during the respective time interval of duration ti.\n3.\tComputation of the Multipactor voltage threshold for each phase scenario resulting from step 2, considering a long-term discharge, where the number of produced electrons is higher than the number of absorbed electrons during a period of the multicarrier signal.\n4.\tSelection of the minimum Multipactor voltage threshold.","NOTE\tA full-multicarrier theory is able to compute the multipactor dynamics (electron growth in time) for an arbitrary combination of frequencies, amplitudes and phases with no simplification of the signal.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.2.4d","Requirement","ECSS-E-ST-20-01_1450078",1,"Created","The customer and supplier shall agree on the method for the computation of the multipactor threshold voltage, specified in 5.3.2.2.4c. "]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.2.4e","Requirement","ECSS-E-ST-20-01_1450079",1,"Created","The input power corresponding to the Multipactor threshold voltage computed in 5.3.2.2.4a.2 shall be computed as  "]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.2.4f","Permission","ECSS-E-ST-20-01_1450080",1,"Created","Different analysis methodologies may be used in agreement with the customer."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.2.4g","Requirement","ECSS-E-ST-20-01_1450081",1,"Created","The resulting threshold shall be compared with the nominal power increased with the dedicated margin of Table 4-6 and Table 4-7."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.3.1a","Requirement","ECSS-E-ST-20-01_1450082",1,"Created","Analysis level 2 shall be applied on equipment or components of type P1 or P2."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.3.2a","Requirement","ECSS-E-ST-20-01_1450083",1,"Created","The secondary emission properties used shall be selected according to criteria specified in clause 5.3.3.3. "]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.3.2b","Requirement","ECSS-E-ST-20-01_1450084",1,"Created","According to the geometry of the critical gap, any equipment or component type 1 (P1) which cannot be analysed through L1, shall be analysed through L2.","NOTE\tThis includes for instance multiple electron trajectories, complex 3D structures where the critical cannot be locally approximated by a parallel plate or coaxial cases.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.3.2c","Requirement","ECSS-E-ST-20-01_1450085",1,"Created","Type 2 equipment or components (P2) shall be analysed through L2, considering the DC electric field created by the dielectric charging in order to determine the worst case of Multipactor threshold."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.3.3a","Requirement","ECSS-E-ST-20-01_1450086",1,"Created","The analysis level 2 shall be characterized by the computation of the Multipactor threshold with a 3D coupled RF EM and electron tracking and surface modelling software."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.3.3b","Requirement","ECSS-E-ST-20-01_1450087",1,"Created","A convergence study of the mesh density and of the initial number of electrons shall be performed until the Multipactor threshold is stabilized."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.3.3c","Requirement","ECSS-E-ST-20-01_1450088",1,"Created","The resulting threshold shall be compared with the nominal power increased with the dedicated margin of Table 4-3 and Table 4-4"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.3.4a","Requirement","ECSS-E-ST-20-01_1450089",1,"Created","The analysis L2 with multi-carrier signals shall be done by using the envelope sweep approach to find the worst-case pulse width that leads to the minimum breakdown power in the following sequence:\n1.\tComputation of the Multipactor threshold power per carrier given by a 3D coupled RF EM and electron tracking and surface modelling software.\n2.\tComparison of the obtained power threshold per carrier with the nominal power per carrier increased with the dedicated margin of Table 4-6 and Table 4-7. "]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.3.4b","Requirement","ECSS-E-ST-20-01_1450090",1,"Created","The computation of the multipactor threshold power per carrier, as specified in 5.3.2.3.4a.1, shall consist of:\n1.\tSelection of M different time intervals of duration ti, i varying from 1 to M, in order to fully cover the duration range between 0 and T, where T is the multi-carrier envelop period by ensuring that the number of time intervals is large enough for the convergence.\n2.\tOptimization of the carrier phases for each value of ti in order to maximize the minimum value of the envelope voltage amplitude during the respective time interval of duration ti.\n3.\tComputation of the Multipactor power threshold for each phase scenario resulting from step 2, considering a long-term discharge, where the number of produced electrons is higher than the number of absorbed electrons during a period of the multicarrier signal.\n4.\tSelection of the minimum Multipactor power threshold."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.3.4c","Permission","ECSS-E-ST-20-01_1450091",1,"Created","Different analysis methods may be used in agreement with the customer.","NOTE\tAlternative methods are described in the handbook.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.3.4d","Requirement","ECSS-E-ST-20-01_1450092",1,"Created","A convergence study of the mesh density and of the initial number of electrons shall be performed until the Multipactor threshold is stabilized."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.2.4a","Requirement","ECSS-E-ST-20-01_1450093",1,"Created","For parallel-plate theory and both 3D EM and electron trajectory computation, any technique shall be validated by either:\n1.\tdemonstrable heritage, or\n2.\tmultipactor breakdown computation of representative sample and comparison with experimental results or results coming from a validated theory or software.","NOTE\tExamples of representative samples are given in the Multipactor handbook ECSS-E-HB-20-01.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.3.1a","Requirement","ECSS-E-ST-20-01_1450094",1,"Created","The analysis margin strategy to be applied shall depend on the available data for two parameters, dimensions and SEY:\n1.\tDimensional accuracy and stability:\n(a)\tNominal values\n(b)\tWorst case, including manufacturing tolerances and thermal effect.\n2.\tSEY available data\n(a)\tECSS SEY data\n(b)\tMeasured SEY, including ageing and temperature effect and charging (if applicable)"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.3.1b","Requirement","ECSS-E-ST-20-01_1450095",1,"Created","For each case specified in 5.3.3.1a, the dedicated margin of Table 4-3, Table 4-4, Table 4-6 or Table 4-7 shall be applied depending on the level analysis and the type of equipment or component."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.3.2a","Requirement","ECSS-E-ST-20-01_1450096",1,"Created","The worst case dimension shall be determined using following steps: \n1.\tinclude the accuracy and stability of the dimensions of the equipment or component, including manufacturing tolerances and the thermal effect.\n2.\tstudy the effect of the thermo-elastic distortion on the qualification temperature range.\n3.\tuse the smallest dimension of the critical gap, provided that the RF equipment or component remains compliant with the electrical performance specifications. \n4.\tevaluate the lowest breakdown power within the whole gap dimensional variation range, if the fxd product is lower than the minimum inflexion point of the curve, and select the gap yielding the lowest breakdown power.\n5.\tcompute the dimensional variation over the iris length in the presence of short irises, and select the longest iris length as the worst-case for all cases."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.3.2b","Requirement","ECSS-E-ST-20-01_1450097",1,"Created","For the nominal dimension, the analysis shall be performed without including the manufacturing tolerances and the thermal effect."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.3.2c","Requirement","ECSS-E-ST-20-01_1450098",1,"Created","In case tuning elements are present in P1 or P2 equipment or component, the predicted worst and best case threshold power shall be derived by applying the range of the tuning elements."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.3.3a","Requirement","ECSS-E-ST-20-01_1450099",1,"Created","SEY data used in the analysis shall be representative of the material in the critical part of the equipment and come from either measured SEY or ECSS SEY. "]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.3.3b","Requirement","ECSS-E-ST-20-01_1450100",1,"Created","For measured SEY, the SEY curve shall be the worst case including the ageing, contamination and temperature and charging properties as specified in requirement9.3a."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.3.3c","Requirement","ECSS-E-ST-20-01_1450101",1,"Created","If no ad-hoc SEY measurement data are available, and the material is listed in Table 9-1, the corresponding material data from this table shall be taken."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.3.3d","Requirement","ECSS-E-ST-20-01_1450102",1,"Created","If no ad-hoc SEY measurement data are available, and the material is not listed in Table 9-1, no analysis is possible and the equipment or component shall be classified as P3."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.3.3e","Requirement","ECSS-E-ST-20-01_1450103",1,"Created","P1 equipment or components shall be analysed with either measured SEY or ECSS SEY data."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.3.3f","Requirement","ECSS-E-ST-20-01_1450104",1,"Created","P2 equipment or components shall be analysed with measured SEY data."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.3.3g","Requirement","ECSS-E-ST-20-01_1450105",1,"Created","If different materials are present at the critical gap, the material with the worse SEY envelope curve shall be taken for analysis level 1."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","5.3.3.4a","Requirement","ECSS-E-ST-20-01_1450106",1,"Created","To compute the threshold level for L1 analysis according to clause 5.3.2.2 the values of Table 5-1 shall be taken.","NOTE\tThe multipactor charts in Figure 5-1 to Figure 5-5 are a visual representation of breakdown voltage for each of the metals listed in Table 9-1.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.1a","Requirement","ECSS-E-ST-20-01_1450108",1,"Created","Airborne particulate cleanliness class 8 as per ISO 14644-1 or better conditions, shall be maintained throughout the equipment or component assembly, test, delivery and post-delivery phases."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.1b","Requirement","ECSS-E-ST-20-01_1450109",1,"Created","In addition, standard clean room practices for handling flight equipment and for general prevention of contamination, agreed with the customer, shall be strictly applied."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.1c","Requirement","ECSS-E-ST-20-01_1450110",1,"Created","Protective covers to prevent the ingress of contaminants shall be used."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.1d","Requirement","ECSS-E-ST-20-01_1450111",1,"Created","If surfaces are vulnerable to contamination the surface molecular and particle contamination shall be monitored in accordance with clause 5.4.2 of ECSS-Q-ST-70-01."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.1e","Requirement","ECSS-E-ST-20-01_1450112",1,"Created","If the contamination monitoring, specified in 6.1d, shows that the specified levels are exceeded, the surface shall be cleaned according to the requirement of clause 5.4.1 of ECSS-Q-ST-70-01.","NOTE\tContamination is any unwanted molecular or particulate matter, including microbiological matter, on the surface or in the environment of interest that can affect or degrade the relevant performance or life time.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.2a","Requirement","ECSS-E-ST-20-01_1450113",1,"Created","A vacuum bake-out shall be performed on all equipment or components before multipactor testing."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.2b","Requirement","ECSS-E-ST-20-01_1450114",1,"Created","The combination of maximum temperature and time duration used for the bake-out shall be equivalent to that which is present in the operational environment of the spacecraft payload.","NOTE\tThe above requirement allows for accelerated bake-out at higher temperatures over relatively short time periods, where the maximum allowable temperature has been approved by the customer. Refer to the ECSS Multipactor handbook ECSS-E-HB-20-01, for further details on determining equivalence of outgassing conditions.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.2c","Requirement","ECSS-E-ST-20-01_1450115",1,"Created","Multipactor testing shall be performed at pressures below 1,0 × 10-5 hPa in the thermal vacuum chamber.","NOTE\tA lower pressure inside the critical regions of the equipment or component can be achieved by providing an adequate combination of:\n·\tpressure in the vacuum chamber,\n·\tventing design for the equipment or component, and\n·\ttime for moisture to outgas from the equipment or component.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.2d","Requirement","ECSS-E-ST-20-01_1450116",1,"Created","The pressure in the thermal vacuum chamber shall be monitored continuously during the test."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.2e","Requirement","ECSS-E-ST-20-01_1450117",1,"Created","If, as a consequence of the monitoring specified in 6.2d, any unexpected pressure increases are detected, these events shall be noted in the test report and correlated against the readings of the multipactor detection methods."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.3a","Requirement","ECSS-E-ST-20-01_1450118",1,"Created","Multipactor tests shall be performed at the temperature extremes defined for the DUT at the critical gap.","NOTE\tThermal analysis results can be used to ensure that the required temperature is met in the critical region (including thermal stability)\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.3b","Permission","ECSS-E-ST-20-01_1450119",1,"Created","For P1 equipment or component of type Bm and Cm, test at ambient temperature may be performed if justifications are provided and agreed with the customer, of the non-impact of temperature over any parameter affecting the breakdown threshold.","NOTE\tDiscussions regarding test at ambient can be found in the corresponding clause ECSS Multipactor handbook ECSS-E-HB-20-01.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.3c","Requirement","ECSS-E-ST-20-01_1450120",1,"Created","A equipment or component tested at extreme temperatures as described in 6.3a shall be tested at the hot and cold extremes with reference to the relevant temperature range:\n1.\tFor qualification tests, the qualification temperature range for EQM and QM.\n2.\tFor batch- and unit tests, the acceptance temperature range for PFM and FM."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.3d","Permission","ECSS-E-ST-20-01_1450121",1,"Created","In the case that a reduced temperature range is agreed with the customer, the new temperature limits may be used for the tests specified in 6.3a."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.3e","Requirement","ECSS-E-ST-20-01_1450122",1,"Created","As a minimum the Temperature Reference Point (TRP) of the DUT shall be monitored during the complete test duration, for ambient tests as well as for tests performed at extreme temperatures."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.3f","Requirement","ECSS-E-ST-20-01_1450123",1,"Created","A maximum acceptable temperature of the TRP shall be specified by the customer."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.3g","Requirement","ECSS-E-ST-20-01_1450124",1,"Created","The thermal dissipation in the DUT caused by the selected multipactor test signal profile, CW, pulsed or multi-carrier, shall be analysed."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.3h","Requirement","ECSS-E-ST-20-01_1450125",1,"Created","The maximum average power applied during multipactor testing shall be no greater than the value used in the thermal analysis."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.4.1a","Requirement","ECSS-E-ST-20-01_1450126",1,"Created","The applicable bandwidth for a multipactor test shall be defined as follows:\n1.\tFor a qualification test, the applicable bandwidth is the full bandwidth for which the equipment or component is designed.\n2.\tFor a batch- or unit test, the applicable bandwidth is the bandwidth, which is applicable for the current project or application."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.4.2a","Requirement","ECSS-E-ST-20-01_1450127",1,"Created","The test frequency shall be determined in accordance with 5.3.1."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.4.3.1a","Requirement","ECSS-E-ST-20-01_1450128",1,"Created","A test with a single carrier, applying an equivalent power as specified in clause 6.4.3.2. shall be performed. "]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.4.3.1b","Permission","ECSS-E-ST-20-01_1450129",1,"Created","If a single carrier test is not possible, a test with a multi-carrier signal, subjected to a frequency multiplex with CW carriers located in accordance with the operational frequency plan and with free-running phase per carrier may be performed under the condition that the test margins and test conditions, including the duration, are agreed between supplier and customer."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.4.3.1c","Permission","ECSS-E-ST-20-01_1450130",1,"Created","If the two tests specified in 6.4.3.1a and 6.4.3.1b are not possible a test with a reduced number of carriers applying an equivalent power as specified in clause 6.4.3.3 may be performed with free-running phase per carrier under the condition that the test margins and test conditions, including the duration are agreed between supplier and customer."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.4.3.2a","Requirement","ECSS-E-ST-20-01_1450131",1,"Created","For the multi-carrier tests performed with an equivalent CW single carrier, test margins of Table 4-5 shall be applied."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.4.3.2b","Requirement","ECSS-E-ST-20-01_1450132",1,"Created","A single carrier equivalent power for a test as described under 6.4.3.2a above shall be defined as follows:\n1.\tperform a single carrier analysis at the average frequency of the multicarrier signal in accordance with clause 5.3.2.1 and 5.3.2.2.3 for L1 or 5.3.2.3.3 for L2 where the threshold power in Watts is denoted Pth,sc,\n2.\tperform a multicarrier analysis on the same analysis level, L1 or L2,as the single carrier analysis specified in 1 above,\n3.\tcalculate the average threshold power in Watts, sum of all carrier power values, found in the multicarrier analysis, denoted Pth,mc with m the number of carriers, using for both, the single carrier and the multi carrier analysis, identical design charts, identical electromagnetic computational model as well as identical material parameters and geometry definitions,\n4.\tcalculate the equivalent power for a single carrier test of a multicarrier device using following formula: \nPeq,sc = P0 · Pth,sc/Pth,mc, where P0 is the nominal multicarrier average power in Watts, sum of all carrier power values, of the input signal,\n5.\tverify that the computed equivalent power from step 4 for a single carrier test of a multicarrier device is always bounded by P0 ≤ Peq,sc ≤ NP0, where N is the number or of carriers,\n6.\tThe single carrier test frequency is the average frequency of the multi-carrier signal as for the single carrier analysis in step 1.","NOTE\t1\tIf the single carrier analysis was an L1 analysis performed according to clause 5.3.2.1 and 5.3.2.2.3, the multicarrier analysis is performed according to clauses 5.3.2.1 and 5.3.2.2.4.\nNOTE\t2\tIf the single carrier analysis was an L2 analysis performed according to clauses 5.3.2.1 and 5.3.2.3.3, the multicarrier analysis is performed according to clauses 5.3.2.1 and 5.3.2.3.4.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.4.3.3a","Requirement","ECSS-E-ST-20-01_1450133",1,"Created","A reduced number of carrier equivalent power for a test as described under 6.4.3.2 shall be defined as follows:\n1.\tSelect the reduced frequency plan in order to have the same average frequency and the same voltage envelope period as the original multi-carrier signal.\n2.\tIf item 1 is not possible due to test facility constraints, a different frequency plan with a reduced number of carriers can be used in agreement with the customer.\n3.\tPerform a multicarrier analysis for both frequency plans, with reduced number of carrier or not, with the same analysis level in accordance with clause 5.3.2.2.4 for L1 and clause 5.3.2.3.4 for L2,\n4.\tcalculate the threshold power found in the multicarrier analysis, denoted Pth,mc,n, with n being the reduced number of carriers compared to Pth,mc,m, with m being the original number of carriers, using for both cases identical simulation models.,\n5.\tcalculate the equivalent power for a multicarrier test with a reduced number of carriers using following formula:\n \nWhere:\nP0,mc,n is the nominal power of the input signal for n carriers\nP0,mc,m is the nominal power of the input signal for m carriers\nP0,mc,n is the nominal power of the input signal for n carriers"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.4.4a","Permission","ECSS-E-ST-20-01_1450134",1,"Created","Pulsed testing may be applied in the cases of equipment or components operating in CW mode.","NOTE\tFor equipment or components operating in CW mode, pulsed testing is an alternative commonly used to avoid thermal effects, which could generate temperature levels in the unit beyond the maximum allowed limits. For this reason, the duty cycle is proportionally and gradually reduced to keep the average CW level constant as the peak power is increased towards the required test margin. This is achieved by varying the PRF between each power step to allow the mean power to be maintained, such that it does not exceed the maximum permitted level.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.4.4b","Requirement","ECSS-E-ST-20-01_1450135",1,"Created","The pulse width shall be equal or greater than 20 microseconds with a duty cycle of at least 2% to ensure sufficient electron seeding as per 6.5.3.","NOTE\tShorter pulsed width and lower duty cycles can be used if they are representative of the operational signal characteristics.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.4.4c","Requirement","ECSS-E-ST-20-01_1450136",1,"Created","The pulse duration used to test equipment or component that experience pulsed excitation in service shall be between 20 microseconds and the longest pulse duration that the equipment or component experiences in service."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.4.4d","Requirement","ECSS-E-ST-20-01_1450137",1,"Created","The suitability of the proposed pulse width and duty cycle as well as compliance with the definition of sensitivity and rise time for the detection methods as described in 7.3.2 and 7.3.3 shall be demonstrated through the reference sample multipactor test according to 8.3b.2."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.5.1a","Permission","ECSS-E-ST-20-01_1450138",1,"Created","If seeding is proven to be inefficient on the real DUT at the critical area, the verification by test may be performed on a dedicated BB or EM unit where the design of outer parts and structures is modified in such a way that the critical gaps can be properly seeded."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.5.2a","Requirement","ECSS-E-ST-20-01_1450139",1,"Created","An electron seed source shall be used for CW Multipactor test."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.5.2b","Permission","ECSS-E-ST-20-01_1450140",1,"Created","Electron seeding may not be used, if the test site demonstrates according to 8.3b.2, with a known reference sample representative of the DUT with respect to the material, the surface properties, the wall thickness - if applicable to the seeding method - and the gap dimensions that the same multipactor threshold as with electron seeding is achieved."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.5.3a","Requirement","ECSS-E-ST-20-01_1450141",1,"Created","An electron seed source shall be used in pulsed testing."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.5.3b","Requirement","ECSS-E-ST-20-01_1450142",1,"Created","In those test cases where electron seeding is ineffective due to restricted access to the critical areas, the test signal shall be in CW mode and validated in accordance with 6.5.2b."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.5.3c","Permission","ECSS-E-ST-20-01_1450143",1,"Created","If, in a test case as described in 6.5.3b, it is not possible to perform CW test, the pulsed test may be performed using a longer pulse width and higher duty cycle than what is defined in 6.4.4, pending customer approval on a case by case basis."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.5.4a","Requirement","ECSS-E-ST-20-01_1450144",1,"Created","An electron seed source shall be used in the multi-carrier environment."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.5.4b","Permission","ECSS-E-ST-20-01_1450145",1,"Created","If the test site demonstrates with a reference sample according to 8.3b.2 that the expected multipactor threshold is achieved, electron seeding may not be used. "]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.5.5a","Requirement","ECSS-E-ST-20-01_1450146",1,"Created","Any applied method or technique of electron seeding shall be implemented aiming at the critical gap where multipactor breakdown can occur during the test."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.5.5b","Requirement","ECSS-E-ST-20-01_1450147",1,"Created","If the DUT has more than one critical gap, where a seeding source is required according to 6.5.5a, at least one seeding source shall be used at each critical gap, simultaneously or consecutively."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.5.5c","Requirement","ECSS-E-ST-20-01_1450148",1,"Created","The seeding electrons shall have a direct path to the critical gap where seeding is required. ","NOTE\tFor a radioactive β source according to 6.5.5d.4, the direct path requirement is applicable to the secondary low energy electrons.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.5.5d","Requirement","ECSS-E-ST-20-01_1450149",1,"Created","At least one of the following seeding sources shall be used: \n1.\tUV light source, which produces electrons by the photoemission mechanism. \n2.\tAn electron gun, which produces a known beam of electrons where both the energy and flux can be characterised.\n3.\tA charged wire probe, which produces electrons by the point discharge mechanism.\n4.\tRadioactive β source, which produces high-energy electrons that, after impacting with metal surfaces or propagation though metallic or dielectric walls, yield a supply of secondary low energy seed electrons.","NOTE\tIf a metallic or dielectric wall is too thick, the high-energy electrons will not be able to propagate and the supply of secondary low energy electrons will not be sufficient. Recommendations for wall thickness are provided in the Multipactor handbook ECSS-E-HB-20-01.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.5.6a","Requirement","ECSS-E-ST-20-01_1450150",1,"Created","It shall be verified during the test facility validation, according to clause 8.3, using the chosen detection methods and a reference sample with a known multipactor threshold, that the seeding method is able to produce a sufficient number of seed electrons in the critical gaps of the DUT."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","6.5.6b","Requirement","ECSS-E-ST-20-01_1450151",1,"Created","The reference sample shall have a geometry, which allows for a representative path of the seeding electrons compared to the seeding electron path of the DUT.","NOTE\tFurther guidelines can be found in the Multipactor handbook ECSS-E-HB-20-01.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","7.2a","Requirement","ECSS-E-ST-20-01_1450152",1,"Created","The detection methods shall be selected from the following list:\n1.\tGlobal methods:\n(a)\tClose to carrier noise\n(b)\tPhase noise\n(c)\tHarmonic noise\n(d)\t Phase nulling.\n(e)\tPulse envelope detection\n(f)\tLow-level amplitude modulation of test signal\n2.\tLocal methods:\n(a)\tOptical\n(b)\tElectron probe\n3.\tOther detection methods, providing demonstration of its effectiveness and validation as per clause 7.3."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","7.2b","Requirement","ECSS-E-ST-20-01_1450153",1,"Created","At least two detection methods shall be present in the test configuration and at least one of them be a global method.","NOTE\tIt is good practise to use both local and global detection methods simultaneously.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","7.3.1a","Requirement","ECSS-E-ST-20-01_1450154",1,"Created","The testing entity shall verify that the detection methods selected are able to detect multipactor events."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","7.3.1b","Requirement","ECSS-E-ST-20-01_1450155",1,"Created","The verification specified in 7.3.1a shall be done during the test facility validation, according to 8.3b.2, using the chosen detection methods and a reference sample with a known multipactor threshold.","NOTE\tFurther guidelines can be found in the Multipactor Handbook ECSS-E-HB-20-01.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","7.3.2a","Requirement","ECSS-E-ST-20-01_1450156",1,"Created","When phase nulling is used as a detection technique, it shall be tuned regularly throughout the test campaign by minimising the null level, in order to maximise detection sensitivity.","NOTE\tIt is good practice that the lowest residual level of the nulling system is kept at least 45 dB below the level obtained with only one of the two nulling paths connected to the detection system.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","7.3.2b","Requirement","ECSS-E-ST-20-01_1450157",1,"Created","When harmonic detection is used, the residual harmonic level in the test system shall be minimised, in order to improve detection sensitivity. ","NOTE\tIt is good practice to keep the residual harmonics system level at least 100 dBc with respect to the carrier power level.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","7.3.2c","Requirement","ECSS-E-ST-20-01_1450158",1,"Created","The testing entity shall ensure that neither the DUT nor any of the equipment or components of the test bed itself is rejecting the selected harmonic frequency."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","7.3.2d","Requirement","ECSS-E-ST-20-01_1450159",1,"Created","For pulsed signal tests, the signal from the phase nulling and the residual harmonics detection systems shall be sampled with a frequency that is sufficient to detect multipactor events on single pulses.","NOTE\tFor pulsed signals, it is good practice that the sampling rate is sufficient to provide at least 10 points during each single pulse.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","7.3.2e","Requirement","ECSS-E-ST-20-01_1450160",1,"Created","For CW tests, the sampling density shall be such that short events are not missed.","NOTE\tFor CW signals, a sampling rate of at least 1 kHz is best practice.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","7.3.2f","Requirement","ECSS-E-ST-20-01_1450161",1,"Created","The bandwidth of each detection system shall be sufficient to detect signal variations with at least the same resolution in the time domain as the interval between sampling points.","NOTE\tThe sampling rate of the monitoring equipment is determined by the combination of the sweep time and the number of points in a sweep.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","7.3.2g","Requirement","ECSS-E-ST-20-01_1450162",1,"Created","A global detection system shall be considered triggered when the residual level, nominal response without discharge, experiences a significant increment with respect to the peak residual level. ","NOTE\tAn increment can be considered significant if it has a magnitude larger than 5 dB - 6 dB. The triggering of the global detection method complies with the nature of a Multipactor breakdown discharge (sudden, self-extinguished after its ignition), in order to avoid misleading diagnostics (e.g. thermal issues on the device under test confused for multipactor discharge).\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","7.3.2h","Recommendation","ECSS-E-ST-20-01_1450163",1,"Created","In local detection methods, electron probe and photodetection, the following conditions should be met:\n1.\telectron probe current noise floor be lower than 10-11 A with a sampling rate of at least 1 reading/second.\n2.\tphoto electron probe noise floor not exceeding |0,5| V with a sampling rate of at least 1 reading/second."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","7.3.2i","Requirement","ECSS-E-ST-20-01_1450164",1,"Created","A local detection system shall be considered triggered when the measured value experiences an abrupt variation, significantly higher than the typical deviation measured in the last minute of the measurement. ","NOTE\tAn increment can be considered significant if it has a magnitude larger than 4 times the typical deviation measured in the last minute of the measurement.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","7.3.3a","Requirement","ECSS-E-ST-20-01_1450165",1,"Created","Each global detection method selected shall have a rise time of less than one tenth of the RF pulse width applied to the DUT in single carrier.","NOTE\tThis does not apply to local detection methods, which are technologically limited to longer rise times.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","7.3.3b","Requirement","ECSS-E-ST-20-01_1450166",1,"Created","For multicarrier operations the rise times shall be short enough to detect breakdown within the period of the multicarrier signal envelope.","NOTE\tFor multi-carrier tests, the use of sensitive, short rise time detection methods enables recording of occasional isolated transient events, particularly if a fast seeding environment is provided.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.1a","Requirement","ECSS-E-ST-20-01_1450167",1,"Created","The execution of a multipactor test shall be controlled by a detailed test procedure aligned with the requirements provided in this clause.","NOTE\tFurther requirements applicable to the test procedure are provided in clause 8.6.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.1b","Requirement","ECSS-E-ST-20-01_1450168",1,"Created","Unless otherwise stated, the requirements in clauses 8.2 to 8.7 shall be applicable to single carrier as well as multicarrier tests."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.2a","Requirement","ECSS-E-ST-20-01_1450169",1,"Created","The multipactor test bed configuration shall conform to the following conditions, as a minimum:\n1.\tUse calibrated equipment where it is required in a measurement role.\n2.\tUse continuous monitoring of the RF power applied to the test item.\n3.\tProvide continuous thermal monitoring and control for the test item.\n4.\tUse continuous pressure monitoring within the vacuum chamber.\n5.\tUse detection methods in accordance with 7.2.\n6.\tUse seeding source in accordance with 6.5.5\n7.\tProvide RF signal generation and amplification."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.2b","Requirement","ECSS-E-ST-20-01_1450170",1,"Created","All reference planes used for RF power monitoring shall be calibrated at the test frequency or frequencies."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.2c","Requirement","ECSS-E-ST-20-01_1450171",1,"Created","As a minimum, the following two reference planes shall be identified for the calibration specified in 8.2b:\n1.\tThe reference plane corresponding to the input port of the test item where input and reverse power are monitored.\n2.\tThe reference plane corresponding to the output port of the test item where the transmit power is monitored.\n3.\tMultiport test items, like circulators typically need multiple reference planes. ","NOTE\t1\tMultiport test items, like circulators typically need multiple reference planes.\nNOTE\t2\tIt is good practise to use a sliding short at the output port to ensure in-phase condition at the critical gap.\nNOTE\t3\tRF items with only one port, such as antennas and loads can be treated on a case by case basis as agreed with the customer.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.2d","Requirement","ECSS-E-ST-20-01_1450172",1,"Created","If any element of the RF chain was modified, replaced, added or removed, the calibration shall be repeated."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.2e","Requirement","ECSS-E-ST-20-01_1450173",1,"Created","The return loss seen from the DUT output port into the test setup at the reference plane described in 8.2c.2 shall be equal or better than -18 dB. "]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.2f","Requirement","ECSS-E-ST-20-01_1450174",1,"Created","In case of deviation from requirement 8.2e, the supplier shall propose a correction action to be agreed with the customer.","NOTE\tThis correction action can be an increment on the input RF power proportional to the mismatch.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.3a","Requirement","ECSS-E-ST-20-01_1450175",1,"Created","Validation of the test bed shall consist of two distinct steps defined in requirement 8.3b and 8.3c."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.3b","Requirement","ECSS-E-ST-20-01_1450176",1,"Created","The first step shall be performed immediately before the multipactor test of the equipment, according to the following sequence:\n1.\tDemonstration of the multipactor-free operation of the test bed, using a transmission line thru replacing the DUT, conducted up to at least the maximum input power foreseen during the test.\n2.\tDemonstration of the correct functioning of all detection systems and seeding sources used conducted by using a reference sample with a known multipactor threshold. ","NOTE\t1\tSee also 6.5.6 Seeding verification and 7.3.1 Verification.\nNOTE\t2\tThe maximum input power includes the sum of nominal power, the mismatch correction (if applicable) and the test margin.\nNOTE\t3\tThe seeding configuration during the verification of multipactor-free test bed operation is representative of the configuration during the test of the DUT. If, for example, a coaxial connector at the DUT input port is irradiated by a radioactive b source during the test of the DUT, the same connector is irradiated in a similar way also during the verification. Parts of the test bed that are not affected by the seeding during the test of the DUT are not necessarily seeded during the verification.\nNOTE\t4\tRecommendations concerning the reference sample can be found in the Handbook.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.3c","Requirement","ECSS-E-ST-20-01_1450177",1,"Created","The second step shall be performed immediately after the multipactor test of the equipment, depending on its outcome."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.3d","Requirement","ECSS-E-ST-20-01_1450178",1,"Created","If a multipactor discharge was detected during the test, the demonstration of the multipactor-free operation of the test bed as per requirement 8.3b.1 shall be repeated and the verification be performed at the maximum power level the DUT was subject to and, if possible, at higher power levels to include margin for potential surface conditioning of the test setup. ","NOTE\tThe purpose of this test is to exclude the test setup as a potential root cause of the observed discharge. Surface conditioning caused by the first discharge (if in the setup) can increase the multipactor threshold of the setup, therefore additional power can be applied if possible.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.3e","Requirement","ECSS-E-ST-20-01_1450179",1,"Created","If no multipactor discharge was observed during the test, the demonstration of the correct functioning of all detection systems and seeding sources as per requirement 8.3b.2 shall be repeated. "]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.3f","Requirement","ECSS-E-ST-20-01_1450180",1,"Created","The test bed validation as per requirement b.1 shall be performed at the same pressure and temperature conditions as for the equipment test."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.3g","Recommendation","ECSS-E-ST-20-01_1450181",1,"Created","For extended or multiple tests with an identical configuration, the validation should be periodically repeated at a rate proposed by the supplier and agreed with the customer."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.3h","Requirement","ECSS-E-ST-20-01_1450182",1,"Created","If any element of the RF chain was modified, replaced, added or removed, the validation shall be repeated."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.4a","Requirement","ECSS-E-ST-20-01_1450183",1,"Created","The S-parameters of the equipment or component to be tested shall be measured at the test site prior to multipactor testing within a frequency range including all frequencies relevant to the detection systems of the test setup.","NOTE\t1\tThe purpose of the S-parameter measurement prior to multipactor testing is: \n·\tto document the status of the equipment or component at the test start, after transportation to the test site (if applicable),\n·\tto provide the possibility to compare the performance of the equipment or component before and after the multipactor test.\n·\tdetermine the suitability of the detection methods to be used (for example harmonic detection).\nNOTE\t2\tAn illustration of the test sequence is given in Figure 8-1.\nNOTE\t3\tFor specific equipment or component (e.g. amplifiers), additional electrical measurements can be considered.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.4b","Requirement","ECSS-E-ST-20-01_1450184",1,"Created","The RF interfaces shall be calibrated according to 8.2b."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.4c","Requirement","ECSS-E-ST-20-01_1450185",1,"Created","The test bed shall be validated according to clause 8.3."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.4d","Requirement","ECSS-E-ST-20-01_1450186",1,"Created","The vacuum chamber containing the test equipment shall be evacuated and baked-out for a sufficiently long period to enable adequate venting and outgassing according to 6.2a, 6.2b and 6.2c."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.4e","Requirement","ECSS-E-ST-20-01_1450187",1,"Created","The test on the equipment shall be performed by applying first the lowest test power, and then increasing in steps to the maximum test power."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.4f","Requirement","ECSS-E-ST-20-01_1450188",1,"Created","The power profile versus time shall be determined considering the following test parameters:\n1.\tSignal characteristics; CW, pulsed, pulse duration, duty cycle, multicarrier, modulation,\n2.\tPower compensation for return loss seen by the DUT output port, if applicable,\n3.\tSeeding,\n4.\tMaximum test power,\n5.\tThermal stabilisation time when applicable.","NOTE\t1\tIt is good practice that the power profile includes several intermediate power steps including the nominal power level.\nNOTE\t2\tRecommended methods to define levels and time duration for the power steps can be found in the Multipactor handbook ECSS-E-HB-20-01.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.4g","Requirement","ECSS-E-ST-20-01_1450189",1,"Created","During the test as a minimum the following parameters shall continuously be monitored and recorded:\n1.\tResponses from the detection systems,\n2.\tReturn loss and insertion loss of the equipment or component,\n3.\tInput power,\n4.\tTemperature,\n5.\tPressure.","NOTE\tIt is good practice to use a common time base for all recordings.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.4h","Requirement","ECSS-E-ST-20-01_1450190",1,"Created","Any detected pressure rise above the value specified in clause 6.2 or temperature above the maximum allowed value at the TRP according to requirement 6.3f shall cause an interruption of the test until satisfactory conditions are restored. "]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.4i","Requirement","ECSS-E-ST-20-01_1450191",1,"Created","During the stepping up of test power, the definitions, and acceptance criteria defined in clause 8.5 shall be applied.","NOTE\tAn illustration of the test sequence is given in Figure 8-1.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.4j","Requirement","ECSS-E-ST-20-01_1450192",1,"Created","After reviewing all the test results, the vacuum chamber shall be returned to ambient pressure."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.4k","Requirement","ECSS-E-ST-20-01_1450193",1,"Created","On completion of the test, validation according to 8.3c shall be performed."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.4l","Requirement","ECSS-E-ST-20-01_1450194",1,"Created","The S-parameters of the tested equipment or component shall be measured at the test site after multipactor testing.","NOTE\tThe purpose of the S-parameter test after multipactor testing is to document the status of the equipment or component after the test, before shipping the equipment or component from the test site (if applicable). Comparisons of S-parameter measurements before and after the multipactor tests are not primarily intended to be used to detect signs of multipactor discharges but can of course be part of an investigation as defined in 8.5.4.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.5.2a","Permission","ECSS-E-ST-20-01_1450195",1,"Created","The tested equipment or component may be declared multipactor free up to the maximum test power if:\n1.\tNo multipactor discharge or event was detected during the test in any of the detection systems at any input power up to the maximum test power, and\n2.\tthe test setup was successfully validated before and after the test according to 8.3. "]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.5.2b","Permission","ECSS-E-ST-20-01_1450196",1,"Created","On a case by case basis, pending customer approval, the equipment or component may be declared multipactor free up to the maximum test power if:\n1.\tInvestigations related to events or to a single non-repeatable discharge as described in clause 8.5.4 lead to the conclusion that the observed phenomena are not related to multipactor, and\n2.\tthe test setup was successfully validated before and after the test according to 8.3. "]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.5.3a","Requirement","ECSS-E-ST-20-01_1450197",1,"Created","If one or several events are detected at power level n during the measurement, the following steps shall be taken:\n1.\tKeep the power constant at power level n for the remaining dwell time after the last event.\n2.\tIf the power level n is equal to the maximum test power, perform an investigation according to 8.5.4 in order to establish the cause of the event.\n3.\tAfter completing the power step where event or events were detected, continue the test with the next power level, n+1.\n4.\tIf further events are detected at power level n+1, repeat the procedure from steps 1, 2 or 3.\n5.\tIf a discharge is detected during steps 1, 2 or 3 stop the test and take the multipactor discharge threshold as the level where the first event was observed.\n6.\tIf no event or discharge is detected during step 3, continue the test with power level n+2.\n7.\tIf further events are detected at power level n+2 or higher, repeat the procedure from steps 1, 2 and 3.\n8.\tIf a discharge is detected at power level n+2 or higher, continue the test in accordance with the procedure for discharges in 8.5.3c and once the test is completed select, pending on the test result either:\n(a)\tto take the multipactor threshold as the level where the first event was observed during the test, or.\n(b)\tif an investigation in accordance with clause 8.5.4 concludes that the first event or events seen during the test were not related to multipactor, perform, pending customer approval, the determination of the multipactor threshold according to the procedure for discharges in 8.5.3c. \n9.\tIf no further events or discharges are detected during the subsequent power steps up to the maximum test power, perform an investigation in accordance with clause 8.5.4 in order to explain the detected event or events. ","NOTE\tAn illustration of the various steps is given in Figure 8-2.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.5.3b","Requirement","ECSS-E-ST-20-01_1450198",1,"Created","The results of the investigation of 8.5.3a.9 shall be reported to the customer to conclude on the nature of the discharge or event."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.5.3c","Requirement","ECSS-E-ST-20-01_1450199",1,"Created","If a discharge is detected at power level n during the measurement, the following steps shall be taken:\n1.\tReduce the power until no discharges or events are detected.\n2.\tKeep the power at the level at which no discharges or events were detected for the nominal duration of a power step.\n3.\tBring back the power to level n, where the first discharge was detected and keep it for the nominal duration of a power step.\n4.\tIf no further discharge or event was detected during step 3, continue the test with the subsequent power steps until either a second event or discharge is detected or the maximum specified test power is reached.\n5.\tIf, during steps 3 and 4, events or discharges occur, record the lowest power level where a discharge was detected as the multipactor discharge threshold.\n6.\tIf, during steps 3 and 4, no events or discharges occur, select, pending on the test result either:\n(a)\ttake the multipactor threshold as the level where the single discharge was observed during the test, or\n(b)\tperform an investigation in accordance with clause 8.5.4 in order to explain the detected potential discharge.","NOTE\tAn illustration of the various steps is given in Figure 8-3.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.5.3d","Requirement","ECSS-E-ST-20-01_1450200",1,"Created","The results of the investigation of 8.5.3c.6(b) shall be reported to the customer to conclude on the nature of the discharge or event."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","8.5.4a","Requirement","ECSS-E-ST-20-01_1450201",1,"Created","If non-repeatable or ambiguous events or discharges have occurred, an investigation shall be performed in order to determine the root cause of the event, events or isolated discharge that was observed. ","NOTE\tThis investigation can include:\n·\tContinued testing at higher power levels or lower duty cycle, pending approval of the customer.\n·\tVenting of the chamber, followed by a repeated test.\n·\tValidation of the test bed, repeating one or more of the steps described in clause 8.3.\n·\tEvaluation of the conditions under which the event or discharge occurred. For example; Test witness getting close to the test bed, unexpected test bed shock, abrupt increment in temperature leading to a return loss change, fluctuations in the high power amplifier.\n·\tOther aspects that are motivated by the experience and knowledge of the equipment or component supplier, the test supplier or the customer.\n"]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","9.4.1.2a","Requirement","ECSS-E-ST-20-01_1450213",1,"Created","The cleanliness and contamination control policy shall be in accordance with the ECSS-Q-ST-70-01."]
["ECSS-E-ST-20-01C","ECSS - Current v1.0","9.4.1.4a","Requirement","ECSS-E-ST-20-01_1450217",1,"Created","The temperature range of the SEY measurement shall be specified by the supplier and approved by the customer."]
["ECSS-E-ST-20-06C Rev.1","ECSS - Current v1.0","6.2.1b","Requirement","ECSS-E-ST-20-06_0070004",1,"Unchanged","If the limits specified in 6.2.1a are not met, the assembly shall be submitted to charging tests as described in clause 6.6. "]
["ECSS-E-ST-20-06C Rev.1","ECSS - Current v1.0","6.3.2c","Requirement","ECSS-E-ST-20-06_0070016",2,"Normative Change","In case of multiple elements, in which case the empirical rule in 6.3.2a does not apply, tests shall be performed.","NOTE \t1\tExamples are patched antenna and solar arrays are multiple elements.\nNOTE \t2\tSee 6.3.1d NOTE for definition of a multi-conductor structures.\n"]
["ECSS-E-ST-20-06C Rev.1","ECSS - Current v1.0","6.6.1c","Requirement","ECSS-E-ST-20-06_0070036",1,"Informative Change","The tests shall either:\n1.\treproduce the physical process of concern, i.e. charging, in a worst-case environment, or \n2.\tyield electrostatic material properties enabling the materials response to such an environment to be assessed."]
["ECSS-E-ST-20-06C Rev.1","ECSS - Current v1.0","6.6.1j","Requirement","ECSS-E-ST-20-06_0070043",1,"Unchanged","Tests shall be performed at temperature of use in space.","NOTE \tThis is because temperature has a large effect on conductivity in dielectric materials. As temperature falls, resistivity rises.\n"]
["ECSS-E-ST-20-06C Rev.1","ECSS - Current v1.0","6.7d","Requirement","ECSS-E-ST-20-06_0070058",1,"Unchanged","The effect of elevated voltage systems and of the spacecraft motion through the ambient magnetic field shall be analysed.","NOTE \tAn example is for solar array.\n"]
["ECSS-E-ST-20-06C Rev.1","ECSS - Current v1.0","6.8.4e","Requirement","ECSS-E-ST-20-06_0070070",1,"Unchanged","If assessment of the electric fields and space charge density in a large volume is performed, the 3-D spacecraft charging codes to be used shall be defined.","NOTE \tThese 3-D spacecraft charging codes can consider the detailed geometry of the spacecraft. Various charging codes with different complexity are available for performing the assessment (see Annex C).\n"]
["ECSS-E-ST-20-06C Rev.1","ECSS - Current v1.0","7.2.3.2f","Requirement","ECSS-E-ST-20-06_0070084",1,"Unchanged","The test coupon shall be a flight-representative qualification coupon."]
["ECSS-E-ST-20-06C Rev.1","ECSS - Current v1.0","9.2.2a","Requirement","ECSS-E-ST-20-06_0070103",2,"Normative Change","All metallic components shall be supplied with two separated grounding paths.","NOTE \tThis requirement includes structural elements, spot shielding, transformer cores, metal packaging of components, unused tracks on PCBs etc. Also included are cables used for testing on the ground but unused in orbit and cables that become temporarily isolated through the operation of a relay, e.g. antenna feeds when in redundant mode. \n"]
["ECSS-E-ST-20-06C Rev.1","ECSS - Current v1.0","9.2.3g","Requirement","ECSS-E-ST-20-06_0070112",1,"Unchanged","The electric fields in systems sensitive to absolute levels of internal electric fields shall stay within the levels agreed with the customer.","NOTE \t1\tThe acceptability of field levels depends on the application.\nNOTE \t2\tThe electric field can be controlled through radiation shielding of sensitive areas, grounding or controlled discharge strategies. \n"]
["ECSS-E-ST-20-06C Rev.1","ECSS - Current v1.0","10.2.5a","Requirement","ECSS-E-ST-20-06_0070128",1,"Unchanged","The current shall not bypass the planned circuit due to conductive paths through the deployment mechanism. ","NOTE \tThis is particularly a problem if the tether insulation is compromized.\n"]
["ECSS-E-ST-20-06C Rev.1","ECSS - Current v1.0","11.2.1d","Requirement","ECSS-E-ST-20-06_0070139",1,"Unchanged","There shall be a ground path linking the neutralizer and the ion beam emitter so that there is a complete circuit including the flow of neutralizer electrons and thruster ions in space.","NOTE \tUnless there is a direct ground path linking the thruster and the neutralizer directly, so that the neutralization current does not pass through other on-board systems, there can be EMC issues.\n"]
["ECSS-E-ST-20-06C Rev.1","ECSS - Current v1.0","11.3.2c","Requirement","ECSS-E-ST-20-06_0070157",1,"Unchanged","Computer models shall be validated with data coming from ground tests or with flight tests. "]
["ECSS-E-ST-20-07C Rev. 2","ECSS - Current v1.0","4.2.5.2b","Requirement","ECSS-E-ST-20-07_0080011",1,"Unchanged","The specified maximum magnetic field value shall comprise the remanent magnetization (magnets, electro-magnets in off-state, or residual perm-up due to hysteresis of soft materials), the induced magnetization of soft materials by the geomagnetic field, and the momentum of current loops."]
["ECSS-E-ST-20-07C Rev. 2","ECSS - Current v1.0","4.2.11.2c","Requirement","ECSS-E-ST-20-07_0080025",2,"Normative Change","Each unit housing shall be bonded to the nearby local structure grounding point from the equipment bonding stud."]
["ECSS-E-ST-20-07C Rev. 2","ECSS - Current v1.0","4.2.13.2d","Requirement","ECSS-E-ST-20-07_0080041",2,"Normative Change","The bonding of cable shields shall be done as follows:\nOvershields shall be bonded to chassis ground:\n1.\tBonding to chassis ground is performed at both ends:\n(a)\tthrough the equipment connector body,\n(b)\tusing a backshell or a dedicated intermediate metal part,\n(c)\twith a DC resistance ≤ 5 mΩ between cable shield and connector housing.\n2.\t<<deleted>>","NOTE \t1\tThis is intended to prevent grounding of the shields inside the equipment through a connector ground pin, which could promote the propagation of interference.\nNOTE \t2\tExamples of dedicated intermediate metal parts are combs, such as Halorings, or Tag rings."]
["ECSS-E-ST-20-07C Rev. 2","ECSS - Current v1.0","5.2.2.3a","Requirement","ECSS-E-ST-20-07_0080049",1,"Unchanged","The ambient electromagnetic level shall be measured with the EUT not operating and all auxiliary equipment turned on."]
["ECSS-E-ST-20-07C Rev. 2","ECSS - Current v1.0","5.2.4g","Requirement","ECSS-E-ST-20-07_0080070",1,"Unchanged","If the return line is grounded at the power source in the actual installation (star distribution), the return line of the LISN shall be grounded on the power source side."]
["ECSS-E-ST-20-07C Rev. 2","ECSS - Current v1.0","5.2.6.3c","Requirement","ECSS-E-ST-20-07_0080081",1,"Unchanged","When mounting bases do not have bonding straps, bonding straps shall not be used in the test setup."]
["ECSS-E-ST-20-07C Rev. 2","ECSS - Current v1.0","5.2.6.6.3a","Requirement","ECSS-E-ST-20-07_0080094",1,"Unchanged","Two metres of input power leads (including neutrals and returns) shall be routed parallel to the front edge of the setup in the same manner as the interconnecting leads."]
["ECSS-E-ST-20-07C Rev. 2","ECSS - Current v1.0","5.2.8.2a","Requirement","ECSS-E-ST-20-07_0080113",1,"Unchanged","A peak detector shall be used for all frequency domain emission and susceptibility measurements.","NOTE \tThis device detects the peak value of the modulation envelope in the receiver pass band. Measurement receivers are calibrated in terms of an equivalent root mean square value of a sine wave that produces the same peak value.\n"]
["ECSS-E-ST-20-07C Rev. 2","ECSS - Current v1.0","5.2.9.3d","Requirement","ECSS-E-ST-20-07_0080124",1,"Unchanged","For equipment that operates, such that potential emissions are produced at only infrequent intervals, times for frequency scanning shall be increased such than any emission is captured."]
["ECSS-E-ST-20-07C Rev. 2","ECSS - Current v1.0","5.2.10.1f","Requirement","ECSS-E-ST-20-07_0080279",1,"Created","In any case, the following additional test frequencies shall be included:\n1.\tknown frequencies where strong emissions exist in the system, to be agreed with the customer;\n2.\tknown frequencies where the EUT is expected to be susceptible.","NOTE \tExamples of known frequencies where susceptibility could be expected are: image frequencies for RF receivers; intermediate frequencies; clock frequencies.\n"]
["ECSS-E-ST-20-07C Rev. 2","ECSS - Current v1.0","5.2.10.4e","Requirement","ECSS-E-ST-20-07_0080144",1,"Unchanged","Data shall be reported with frequency resolution of 1 %."]
["ECSS-E-ST-20-07C Rev. 2","ECSS - Current v1.0","5.3.4a","Requirement","ECSS-E-ST-20-07_0080156",1,"Informative Change","Lightning protection specified in ECSS-E-ST-20 (in clause “Inter-system EMC and EMC with environment”), shall be verified by analysis from equipment demonstration.","NOTE \tTest at system level is not performed.\n"]
["ECSS-E-ST-20-07C Rev. 2","ECSS - Current v1.0","5.4.2.2a","Requirement","ECSS-E-ST-20-07_0080168",1,"Unchanged","The test equipment shall be as follows:\n1.\tMeasurement receiver,\n2.\tCurrent probe,\n3.\tSignal generator with amplifier,\n4.\tDC-current supply,\n5.\tData recording device,\n6.\tOscilloscope,\n7.\tCoaxial “T” connector and coaxial to bifilar transition,\n8.\t1 W and 10 W power metal film resistors with inductance lower than 100 nH,\n9.\tLISN defined in 5.2.4."]
["ECSS-E-ST-20-07C Rev. 2","ECSS - Current v1.0","5.4.6.2a","Requirement","ECSS-E-ST-20-07_0080186",2,"Normative Change","The test equipment shall be as follows:\n1.\tMeasurement receiver,\n2.\tData recording device,\n3.\tLinearly polarized antennas,\n(a)\tbiconical, 137 cm tip to tip from 30 MHz to 200 MHz\n(b)\tdouble ridge horn, 24,2 cm by 13,6 cm opening, from 1 GHz to 18 GHz\n4.\tSignal generators,\n5.\tStub radiator,\n6.\tLISN defined in 5.2.4, unless the primary power lines are shielded in the actual installation of the relevant space segment element and in the test setup.","NOTE \tThe LISN provides a defined common mode impedance.\n"]
["ECSS-E-ST-20-07C Rev. 2","ECSS - Current v1.0","5.4.7.4a","Requirement","ECSS-E-ST-20-07_0080199",2,"Normative Change","The measurement equipment shall be turned on and sufficient time allowed for its stabilisation."]
["ECSS-E-ST-20-07C Rev. 2","ECSS - Current v1.0","5.4.8.4d","Permission","ECSS-E-ST-20-07_0080270",1,"Unchanged","The calibration need not be re-performed before testing each EUT bundle."]
["ECSS-E-ST-20-07C Rev. 2","ECSS - Current v1.0","5.4.11.4d","Requirement","ECSS-E-ST-20-07_0080297",1,"Created","If a power meter is used, the EUT shall be tested as follows:\n1.\tTurn on the EMC test equipment and the EUT and allow sufficient time for their stabilisation.\n2.\tAdjust the band and gain settings of the RF power amplifier chosen to test the first frequency band.\n3.\tUsing the transmit antenna chosen to test the first frequency band vertically polarised, set the unmodulated signal generator to the first test frequency, at low output power level.\n4.\tIncrease the signal generator output power level until the forward power level to the transmit antenna, as determined during calibration is met.\n5.\tAdjust and apply the signal modulation specified in 5.2.10.2.\n6.\tMaintain the signal during the dwell time specified in 5.2.10.1.\n7.\tMonitor the EUT for signs of susceptibility.\n8.\tRecord, for information only, the electric field level measured by the isotropic field probe, as a confirmation that an electric field was actually applied.\n9.\tIf susceptibility is noted, determine the threshold level in accordance with 5.2.10.3.\n10.\tRepeat 5.4.11.4d.3 to 5.4.11.4d.9 for each frequency testable with the same signal-generator – amplifier – transmit-antenna chain.\n11.\tRepeat 5.4.11.4d.3 to 5.4.11.4d.10 for the horizontal polarisation.\n12.\tRepeat 5.4.11.4d.3 to 5.4.11.4d.11 for each test antenna position determined in 5.4.11.3e.\n13.\tRepeat 5.4.11.4d.2 to 5.4.11.4d.12 for each signal-generator – amplifier – transmit antenna chain.","NOTE \tTo 5.4.11.4d.8: The electric field level measured by the isotropic probe with the EUT present and with the modulation applied is in practice significantly different from the calibrated electric field level, so is only useful for direct confirmation that an electric field is actually present.\n"]
["ECSS-E-ST-20-07C Rev. 2","ECSS - Current v1.0","5.4.13.3b","Requirement","ECSS-E-ST-20-07_0080303",1,"Created","The calibration shall be performed as follows:\n1.\tTurn on the measurement equipment and wait until it is stabilized,\n2.\tTurn on the dedicated ESD pulse generator,\n3.\tStarting from 3 kV, adjust the amplitude of the charging voltage of the pulse generator until the waveform is within the following ranges, also illustrated in Figure 5-36:\n(a)\tamplitude: 13 A ± 1 A\n(b)\trise time: 1,5 ns ± 0,3 ns, measured between 10% and 90% of the peak amplitude\n(c)\tduration: 3 ns ± 1 ns at 50% amplitude\n4.\tRecord the pulse generator settings,\n5.\tRecord the last transient current pulse measured by the oscilloscope."]
["ECSS-E-ST-20-07C Rev. 2","ECSS - Current v1.0","5.3.3a","Requirement","ECSS-E-ST-20-07_0080153",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","4.4a","Requirement","ECSS-E-ST-20-08_0090014",1,"Unchanged","The critical interface information shall be part of the PMP list.","NOTE \tFor PMP, see ECSS-Q-ST-70 Annex B.\n"]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","5.3.2.4c","Requirement","ECSS-E-ST-20-08_0090029",1,"Unchanged","To avoid electrolytic corrosion, a process, approved by the customer, shall be used."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","5.3.3.4a","Requirement","ECSS-E-ST-20-08_0090044",1,"Unchanged","Sections shall not be included at the coupon level. "]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","5.3.3.9c","Requirement","ECSS-E-ST-20-08_0090050",1,"Informative Change","No single fault shall result in the following:\n1.\tThe loss of integrity of the redundant parts indicated in requirement 5.3.3.9b.2.\n2.\tThe propagation of the fault causing permanent damage or loss of use of the units connected to the PVA. ","NOTE \tExamples: solar array regulator unit, solar array drive mechanism.\n"]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","5.3.3.12c","Requirement","ECSS-E-ST-20-08_0090059",1,"Unchanged","The thermal conductance towards the panel substrate shall be such that the specified solar cell and protection diode temperature can be maintained."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","5.4.3.6a","Requirement","ECSS-E-ST-20-08_0090074",2,"Normative Change","The continuity of all strings shall be checked after stringing."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","5.5.1.3.3i","Requirement","ECSS-E-ST-20-08_0090101",1,"Unchanged","At least 3 thermocouples on the front side and 3 on the rearside of each qualification coupon shall be placed for temperature monitoring."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","5.5.1.3.4a","Permission","ECSS-E-ST-20-08_0091068",1,"Unchanged","The number of cycles and temperature deltas may be determined using one of the following criteria:\n1.\tThe number of cycles is four times the number of cycles that occur during the mission with 0 °C temperature delta (at both upper and lower design temperature limit). \n2.\tThe number of cycles is equal to 1,5 times the number of cycles occurring during the mission with a temperature delta of 10 °C at extremes (both upper and lower qualification temperature limit). "]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","5.5.1.4.4g","Requirement","ECSS-E-ST-20-08_0090122",1,"Unchanged","Water condensation on the surface of the test sample shall be prevented."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","5.5.1.6a","Requirement","ECSS-E-ST-20-08_0090127",1,"Unchanged","The test sequence, test definitions and requirements for the tests for erosion of material shall be agreed between the supplier and the customer and stated in the SCD-PVA."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","5.5.3.2.6e","Requirement","ECSS-E-ST-20-08_0090149",1,"Unchanged","Coverglasses with any of the following defects shall be rejected at the end of acceptance:\n1.\tCoverglasses installed upside down as indicated by improper location of the coating orientation mark in conformance with clause 8.3.3.\n2.\tCoverglass which is not flush with or overhanging all four cell edges.\n3.\tCoverglasses with dirty and contaminated surface if they cannot be cleaned.\n4.\tLoose coverglasses.\n5.\tCorner chip exceeding the limits specified in requirement 5.5.3.2.6b.1.\n6.\tEdge chips exceeding the limits specified in clause 6.4.3.1.4.\n7.\tCoverglasses with intersecting cracks exceeding the limits specified clause 6.4.3.1.4."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","5.5.3.2.8c","Requirement","ECSS-E-ST-20-08_0090155",2,"Normative Change","Solar cells with any of the following defects shall be rejected at the end of acceptance: \n1.\tCracks crossing more gridlines than specified in requirement 5.5.3.2.8a.2.\n2.\tMore cracks than specified in requirement 5.5.3.2.8a.1 on a single cell.\n3.\tCracks between the cell edges parallel to the gridlines and the outermost edges of the interconnectors.\n4.\tCorner chip exceeding the limits specified in clause 6.4.3.1.4.\n5.\tEdge chips exceeding the limits specified in clause 6.4.3.1.4.","NOTE \tto item 1: Multiple crossing of the same gridline can be present.\n"]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","5.5.3.2.16a","Requirement","ECSS-E-ST-20-08_0090170",1,"Unchanged","Attachments based on bonding techniques shall be fully cured and not exhibit any tackiness."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","5.5.3.3.3b","Requirement","ECSS-E-ST-20-08_0090185",1,"Unchanged","The insulation shall be in conformance with that stated in the SCD-PVA."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","5.5.3.3.9a","Requirement","ECSS-E-ST-20-08_0090199",1,"Unchanged","The resistance of the harness shall be measured at the interface connector by measuring the redundant coupon wiring in series (i.e. positive end to positive end and negative end to negative end)."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","5.5.3.7.3d","Requirement","ECSS-E-ST-20-08_0090220",1,"Unchanged","During thermal cycling, the electrical insulation shall be measured."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","5.5.3.10.1a","Requirement","ECSS-E-ST-20-08_0090229",1,"Unchanged","The structural integrity of the substrate shall be inspected after thermal cycling."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","5.5.3.11.3b","Requirement","ECSS-E-ST-20-08_0090242",1,"Unchanged","No open circuit conditions shall be recorded during continuity testing."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","6.1.2c","Requirement","ECSS-E-ST-20-08_0090254",1,"Unchanged","Any deviation from the required in-process, acceptance and qualification test shall be justified in the documentation package."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","6.4.1a","Requirement","ECSS-E-ST-20-08_0090271",1,"Unchanged","All SCA procurement lots shall be qualified. "]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","6.4.2.3d","Requirement","ECSS-E-ST-20-08_0090287",1,"Unchanged","A failure in any subgroup shall constitute a failure in the qualification. ","NOTE \tFor a definition of failure see clause 6.5. \n"]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","6.4.3.1.5e","Requirement","ECSS-E-ST-20-08_0090299",1,"Unchanged","The coverglass shall not contain bubbles having a projected area larger than 0,02 mm2."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","6.4.3.3.2c","Requirement","ECSS-E-ST-20-08_0090315",1,"Unchanged","The accuracy of the SCA measured parameters (Isc, Itest, Vtest Voc and Pmax) shall be provided to the customer. "]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","6.4.3.4d","Requirement","ECSS-E-ST-20-08_0090324",1,"Unchanged","Data for all electrical performance parameters at the different solar cell temperatures shall be provided."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","6.4.3.8.2f","Requirement","ECSS-E-ST-20-08_0090342",1,"Unchanged","High-purity water in conformance with ASTM D1193-99, Type I, shall be used."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","6.4.3.11.2e","Requirement","ECSS-E-ST-20-08_0090356",2,"Normative Change","Selection of solar cell assemblies for electron irradiation shall be performed as follows:\n1.\tthree fluences as stated in the SCD-SCA are applied;\n2.\tfor each fluence, and in conformance with 6.4.2.2f, a minimum of the following SCA’s numbers are tested:\n(a)\t2 high-grade cells;\n(b)\t4 mid-grade cells;\n(c)\t2 low grade cells. "]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","6.4.3.15.2c","Requirement","ECSS-E-ST-20-08_0090371",1,"Unchanged","Spectral Irradiance for UV light sources shall be performed in conformance with ECSS-Q-ST-70-06."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","6.4.3.16.2c","Requirement","ECSS-E-ST-20-08_0090382",1,"Unchanged","The capacitance shall be measured at SCA level in conformance with the method referred in requirement 6.4.3.16.2b at the temperature range stated in the SCD-SCA."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","6.5.2c","Requirement","ECSS-E-ST-20-08_0090390",1,"Unchanged","Failure analysis of these SCAs shall be performed by the supplier and the results provided to the customer, as part of an NRB documentation.","NOTE \tFor NRB, see ECSS-Q-ST-10-09.\n"]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","7.1.1.4c","Requirement","ECSS-E-ST-20-08_0090405",1,"Unchanged","The manufacturer shall propose a sampling method and procedure for customer approval.","NOTE \tNo pass fails are foreseen during the execution of the sampling\n"]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","7.3.2.1a","Requirement","ECSS-E-ST-20-08_0090417",1,"Unchanged","Except for electrical performance, the test methods and conditions for acceptance shall conform to clause 7.5."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","7.4.2.1b","Requirement","ECSS-E-ST-20-08_0090435",1,"Unchanged","A production flow chart, process schedules and inspection procedures shall be provided."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","7.5.1.4.1b","Requirement","ECSS-E-ST-20-08_0090448",1,"Unchanged","The cumulative area of all edge chips, corner chips and surface nicks shall not exceed 5 % of the total cell area."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","7.5.1.5.4d","Requirement","ECSS-E-ST-20-08_0090465",1,"Unchanged","The maximum area of worm shaped bulges shall be 3 % of total cell contact area."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","7.5.4f","Requirement","ECSS-E-ST-20-08_0091134",1,"Created","For the 3 MeV electron samples of subgroup C as well as all samples of subgroup P only measurement at 60 °C and 90 °C shall be performed."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","7.5.6.2a","Requirement","ECSS-E-ST-20-08_0090484",1,"Unchanged","Hemispherical reflectance shall be measured in the wavelength region from 250 nm to 2 500 nm."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","7.5.8.2c","Requirement","ECSS-E-ST-20-08_0090509",1,"Unchanged","The adhesive tape used for this test shall be clear in colour with an adhesive strength on steel of at least 0,28 N/mm.","NOTE \tFor measuring the adhesive strength on steel, EN 1939 can be used.\n"]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","7.5.12.2c","Requirement","ECSS-E-ST-20-08_0090519",1,"Unchanged","The pull direction shall:\n1.\tbe either 0°, 45° or 90°; \n2.\tbe as stated in the SCD-BSC."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","7.5.15.2c","Requirement","ECSS-E-ST-20-08_0090535",1,"Unchanged","After the tests, the cells shall be kept at temperatures below 50 °C until they are electrically measured."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","7.8a","Requirement","ECSS-E-ST-20-08_0090549",1,"Unchanged","All deliverable hardware specified in the order shall be delivered together with documentation in conformance with the requirements specified in clause 7.7."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","7.9.2a","Requirement","ECSS-E-ST-20-08_0090551",1,"Unchanged","If a bare cell is sensitive to ESD according to clause 5.2 of ESCC 23800 Issue 1 then it shall be handled and stored according to ESCC 24900 Issue 2, clause 10."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","8.6.2.1a","Requirement","ECSS-E-ST-20-08_0090579",1,"Unchanged","Before starting production of the qualification lot, the manufacturer shall compile a production test schedule, showing by date and duration, production and test activities, including all major processing operations and key stages in the production and testing. "]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","8.7.1.2a","Requirement","ECSS-E-ST-20-08_0090586",1,"Unchanged","Any deviation from the visual inspection requirements on defects in clause 8.7.1.3 shall:\n1.\tnot affect performance or reliability,\n2.\tbe agreed with the customer, and\n3.\tbe justified."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","8.7.1.3.5a","Requirement","ECSS-E-ST-20-08_0090594",1,"Unchanged","The length of the hypotenuse, as defined by “d” in Figure 8‑3, of any corner chip in the coverglass, shall not exceed 0,75 mm."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","8.7.4.5a","Requirement","ECSS-E-ST-20-08_0090609",1,"Unchanged","The perpendicularity of the sides of the coverglass shall be measured using an optical instrument with a reference normal. "]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","8.7.11.2.2e","Requirement","ECSS-E-ST-20-08_0090637",1,"Unchanged","High-purity water in conformance with ASTM D1193-99, Type I, shall be used."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","8.7.11.2.2g","Requirement","ECSS-E-ST-20-08_0090639",1,"Unchanged","If there are requirements on specific environmental conditions, they shall be stated in the SCD-CVG.","NOTE \tFor example, requirements on chemical vapours.\n"]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","8.7.16b","Requirement","ECSS-E-ST-20-08_0090658",1,"Unchanged","After exposure, the coverglasses shall show no signs of physical degradation when inspected in conformance with a standard agreed with the customer","NOTE \tExample of such a standard is MIL-PRF-13830. \n"]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","8.9a","Requirement","ECSS-E-ST-20-08_0090668",1,"Unchanged","The supplier shall provide a data documentation package (DDP) in conformance with Annex G for the qualification approval records and for each component delivery lot. "]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","9.4.4b","Requirement","ECSS-E-ST-20-08_0090693",1,"Unchanged","The sample size shall be in conformance with Table 9‑1 (for IPD) or Table 9‑2 (for EPD)."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","9.4.5.2.2b","Requirement","ECSS-E-ST-20-08_0090698",1,"Unchanged","Provision 9.4.5.2.2a shall be performed for the following variables, as stated in the SCD-BSC or SCD-EPD:\n1.\tAt one temperature specified. \n2.\tUp to a forward current, IDIODE–FORWARD., which is as a minimum, equal to 1,1 times the expected string current at solar array level at the corresponding temperature\n3.\tUp to a reverse voltage, VDIODE–REVERSE. which is as a minimum, equal to 1,33 times the expected solar cell open circuit voltage at the corresponding temperature. "]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","9.5.3c","Requirement","ECSS-E-ST-20-08_0090714",1,"Unchanged","For a procurement lot of a previously qualified external protection diodes, the qualification tests need not be repeated if the following conditions are satisfied:\n1.\tNo changes are made to the design, function or electrical or mechanical parameters of the external protection diode.\n2.\tThe same source control drawing is applicable.\n3.\tNo changes are made to the PID.\n4.\tDelta qualification tests are performed to cover the requirements imposed by the new application. "]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","9.6.2.5.1a","Requirement","ECSS-E-ST-20-08_0090729",1,"Unchanged","The protection diode contact area shall be free of digs, scratches, and probe prints, unless metallization is still present."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","9.6.5.2c","Requirement","ECSS-E-ST-20-08_0090741",1,"Unchanged","During the process the samples shall be under load. "]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","9.6.10.2a","Requirement","ECSS-E-ST-20-08_0090756",2,"Normative Change","All diodes shall be subjected to a coating adherence test on both full sample faces."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","9.6.11.2d","Requirement","ECSS-E-ST-20-08_0091148",1,"Created","The type of failure shall be recorded in the data documentation package (DDP) as specified in clause 9.8."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","9.6.15.2d","Requirement","ECSS-E-ST-20-08_0090778",1,"Unchanged","The increase of temperature in forward mode at maximum operating temperature shall be assessed in order to avoid overheating of the diode."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","9.6.17.2d","Requirement","ECSS-E-ST-20-08_0090792",1,"Unchanged","The applied signal for the switching cycles shall be in conformance with the Figure 9‑2."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","9.9b","Requirement","ECSS-E-ST-20-08_0090808",1,"Unchanged","One set of documents shall be sent to the customer."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","10.1.3d","Requirement","ECSS-E-ST-20-08_0090827",1,"Unchanged","The irradiance stability of the Sun simulator in the test plane shall be capable to guarantee reproducibility and, thus, not introduce errors on measured solar cell electrical parameters (Isc, Voc, and Pmax) higher than 1 % or other value proposed by the supplier and accepted by the customer."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","10.2.2.3.2a","Requirement","ECSS-E-ST-20-08_0090838",1,"Unchanged","The stability of the sensitivity of the SWS under operating conditions shall be verified by comparing the short-circuit current of five of the SWS before and after a photon-irradiation test with the short-circuit current of the remaining five SWS which are kept in the dark."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","10.2.6.1c","Requirement","ECSS-E-ST-20-08_0090853",1,"Unchanged","The simulator intensity shall be verified with the aid of the SWS at regular intervals."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","11.1.4.1a","Recommendation","ECSS-E-ST-20-08_0091089",1,"Unchanged","For a 1 W shunt, the value given by the analyser is the impedance of the cell in series with the 1 W resistor, where the cell impedance should be determined using the following calculation:\n1.\tIf B/A is given in amplitude |B/A| and phase j (B/A), the cell impedance is:\nZcell = Rshunt measured ´  \n2.\tIf B/A is given in the complex form X+j ´ Y\nZcell = Rshunt measured ´ [ 1 +X2 + Y2 – 2X]1/2"]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","12.2.1.2d","Requirement","ECSS-E-ST-20-08_0091154",1,"Created","Deviations from this Standard applicable to the SCD-PBD shall:\n1.\tbe agreed between the customer and the supplier;\n2.\tinclude alternative requirements equivalent to those of this Standard;\n3.\tnot affect the reliability and performances of the PBD;\n4.\tonly be those specified in requirement 12.2.1.2c."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","12.5.3a","Requirement","ECSS-E-ST-20-08_0091171",1,"Created","Before starting production of the qualification lot, the manufacturer shall compile a production test schedule showing by date and duration the production and test activities, including all major processing operations and key stages in the production and testing."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","12.6.1.3e","Requirement","ECSS-E-ST-20-08_0091187",1,"Created","There shall be no evidence of corrosion, peeling of finish or plating or of holes and cracks."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","12.6.4.1.2h","Requirement","ECSS-E-ST-20-08_0091202",1,"Created","For connector integrated blocking diodes, requirements for voltage loading to simulate ambient illumination and other required environmental conditions shall be stated in the SCD-PBD.","NOTE \tOther required environmental conditions are for example, chemical vapour requirements.\n"]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","12.6.5.2a","Requirement","ECSS-E-ST-20-08_0091210",1,"Created","The number of cycles and the extreme temperatures shall be as stated in the SCD-PBD."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","12.6.9.2a","Requirement","ECSS-E-ST-20-08_0091232",1,"Created","Electrical measurements shall be performed at maximum (t1) and minimum (t2) junction temperatures, as well as at operational temperature and three temperatures close to extremes t1 and three temperatures close to extreme t2, where:\n1.\tt1 = highest temperature (without margins) predicted for the application. \n2.\tt2 = lowest temperature (without margins) predicted for the application. ","NOTE \tThe 3 temperatures close to the extremes to be chosen at equidistance of 10 K to 20 K depending on the limitations of the test facility with at least one measurement at the extreme temperature.\n"]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","12.6.11.1.1f","Requirement","ECSS-E-ST-20-08_0091242",1,"Created","A ionizing dose of 50 Mrad is a typical value and shall cover most LEO and GEO missions."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","12.6.16.3a","Requirement","ECSS-E-ST-20-08_0091263",1,"Created","The pull strength shall satisfy the pass-fail criteria stated in the SCD-PBD."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","A.2.1<1>a","Requirement","ECSS-E-ST-20-08_0090878",1,"Unchanged","The SCD-PVA shall contain a description of the purpose, objective, content and the reasons prompting its preparation."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","A.2.1<8.1>a","Requirement","ECSS-E-ST-20-08_0090892",1,"Unchanged","In conformance with clause 5.5.3.1, the SCD-PVA shall state the maximum add-on mass of the coupon, in g, obtained from a mass measurement."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","A.2.1<8.9>a","Requirement","ECSS-E-ST-20-08_0090907",1,"Unchanged","In conformance with clause 5.5.3.9, the SCD-PVA shall state the acceptance criteria for the change in transmission due to contamination in the band of 280 nm < l < 2 500 nm."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","B.2.1<3>a","Requirement","ECSS-E-ST-20-08_0090913",1,"Unchanged","The SCD-SCA shall include any additional definition, abbreviation or symbol used."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","C.2.1<6.2>a","Requirement","ECSS-E-ST-20-08_0090937",1,"Unchanged","In conformance with clause 7.5.2, the SCD-BSC shall include:\n1.\tThe dimensions shown in Figure C-1 to Figure C-3 including tolerances.\n2.\tThe measurement method used to perform the test.\n3.\tThe interval of the thickness of the silicon layer, in mm, for silicon solar cells.\n4.\tThe interval of the thickness of the substrate with epi-layers, in mm, for III-IV cells.\n5.\tThe maximum weight, in mg, of the average shipment lot."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","C.2.1<7.1>a","Requirement","ECSS-E-ST-20-08_0090948",1,"Unchanged","The SCD-BSC shall include the same provisions as in the visual inspection for the acceptance tests (in conformance with clause C.2.1<6.1>)."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","D.2.1<3>a","Requirement","ECSS-E-ST-20-08_0090967",1,"Unchanged","The SCD-CVG shall include any additional definition, abbreviation or symbol used."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","D.2.1<8.5>a","Requirement","ECSS-E-ST-20-08_0090982",1,"Unchanged","In conformance with clause 8.7.4, the SCD-CVG shall include a figure showing the nominal values and tolerances of the following mechanical properties:\n1.\tdimensions (A: length, B: width);\n2.\tweight (average per shipping lot);\n3.\tdensity\n4.\tthickness;\n5.\tedge parallelism;\n6.\tperpendicularity of sides.","NOTE \tThis figure can be the same as in clause D.2.1<8.4>.\n"]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","D.2.1<8.8>a","Requirement","ECSS-E-ST-20-08_0090985",1,"Unchanged","In conformance with clause 8.7.7, the SCD-CVG shall include the minimum value of the surface resistivity, in W/cm2, and the equipment used to measure the resistivity."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","E.2.1<7.8>a","Requirement","ECSS-E-ST-20-08_0091012",1,"Unchanged","In conformance with clause 9.6.9.3, the SCD-EPD shall include the requirements for the interconnection process."]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","F.2.2b","Requirement","ECSS-E-ST-20-08_0091019",2,"Normative Change","In the case specified in requirement 12.10.2a, a reference to the document shall be included. "]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","H.2.1<7>e","Requirement","ECSS-E-ST-20-08_0091289",1,"Created","For humidity and temperature, in conformance with clause 12.6.4, the SCD-PBD shall include the chemical contents, type and % in the mist, to be added to the humid environment when there are specific requirements on the contents of the environment. "]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","H.2.1<7>f","Requirement","ECSS-E-ST-20-08_0091290",1,"Created","For Pull, in conformance with clause 12.6.16, the SCD-PBD shall include: \n1.\tthe interconnection technique parameter; \n2.\tthe material and dimension of the interconnectors; \n3.\tthe value of the pull speed in mm/min and direction (0°, 45° or 90°); \n4.\tthe value of the ultimate pull strength in N. "]
["ECSS-E-ST-20-08C Rev.2","ECSS - Current v1.0","H.2.1<8.11>b","Requirement","ECSS-E-ST-20-08_0091305",1,"Created","In conformance with clause 12.6.8, the SCD-PBD shall include maximum allowable temperature of the diode, as defined in the Temperature Stress Step Test of ESCC 2265000."]
["ECSS-E-ST-20-20C","ECSS - Current v1.0","5.2.3.2.1a","Requirement","ECSS-E-ST-20-20_1320013",1,"Created","For LCL/RLCL/HLCL, the switch element shall be on the hot main bus side."]
["ECSS-E-ST-20-20C","ECSS - Current v1.0","5.2.8.1.1a","Requirement","ECSS-E-ST-20-20_1320031",1,"Created","The LCL/HLCL/RLCL ON/OFF status shall confirm that the LCL/RLCL/HLCL output voltage is within its nominal range."]
["ECSS-E-ST-20-20C","ECSS - Current v1.0","5.2.10.2.1a","Requirement","ECSS-E-ST-20-20_1320039",1,"Created","The RLCL shall correctly operate the application of repetitive overload conditions within the applicable derating limits.","NOTE \tFor instance hiccup between RLCL and UVP of the function supplied by the RLCL. In absence of specific needs, the approach described in ECSS-E-HB-20-20 section 5.7.2.6 can conveniently be used (e.g. ensuring a ratio of 30 between the count down and count up time constant of the RLCL trip-off counter).\n"]
["ECSS-E-ST-20-20C","ECSS - Current v1.0","5.3.1.1.1a","Requirement","ECSS-E-ST-20-20_1320060",1,"Created","During nominal operation after switch-on, the load current for LCL/RLCL/HLCL shall always be smaller than the correspondent class current."]
["ECSS-E-ST-20-20C","ECSS - Current v1.0","5.3.2.3.1a","Requirement","ECSS-E-ST-20-20_1320064",1,"Created","If the LCL/RLCL current limit is reached, the load input filter shall be completely charged within the relevant LCL/RLCL maximum charge time defined in requirement 5.4.2.3.1a."]
["ECSS-E-ST-20-20C","ECSS - Current v1.0","5.4.2.2.1a","Requirement","ECSS-E-ST-20-20_1320078",1,"Created","Maximum LCL/RLCL/HLCL switch-off current rate dI/dt shall be 1A/µs."]
["ECSS-E-ST-20-20C","ECSS - Current v1.0","5.4.6.1.1a","Requirement","ECSS-E-ST-20-20_1320096",1,"Created","Minimum phase margin for LCL/RLCL/HLCL shall be 50°, under the following conditions:\n1.\ta zero Ohm impedance load is applied, and\n2.\tthe DC voltage across the LCL/RLCL/HLCL equals (4 ±1) V.","NOTE \tThe zero Ohm impedance is implemented by a voltage source with current sink capability.\n"]
["ECSS-E-ST-20-20C","ECSS - Current v1.0","5.5.1.1.1a","Recommendation","ECSS-E-ST-20-20_1320128",1,"Created","For LCL/RLCL, a load should not reinject current into the bus."]
["ECSS-E-ST-20-21C","ECSS - Current v1.0","5.2.1e","Requirement","ECSS-E-ST-20-21_1400012",1,"Created","Dedicated connectors dedicated to the actuators electronics outputs shall be implemented."]
["ECSS-E-ST-20-21C","ECSS - Current v1.0","5.2.2e","Requirement","ECSS-E-ST-20-21_1400019",1,"Created","In case the return lines to the actuators cannot be disconnected as specified in 5.2.2d, then two following conditions shall be met to avoid failure propagation due to loss of insulation:\n1.\tThe relevant actuator group does not share connectors with other groups or with other electronic functions having source capability to trigger the relevant actuators.\n2.\tThe harness of the relevant actuator group are not bundled together with any other wire or bundle carrying a positive or negative potential sufficient to trigger the relevant actuators."]
["ECSS-E-ST-20-21C","ECSS - Current v1.0","5.2.4b","Requirement","ECSS-E-ST-20-21_1400034",1,"Created","The actuator electronics shall provide the indication of the status of each selection switch."]
["ECSS-E-ST-20-21C","ECSS - Current v1.0","5.4.1a","Requirement","ECSS-E-ST-20-21_1400049",1,"Created","For current-driven actuators, one of the following two conditions shall be met:\n1.\tIf the actuator maximum resistance as per requirement 5.6.1a is specified, the actuators electronics is able to provide the specified current when the load resistance, including actuator plus harness, is equal to the maximum value not to exceed the voltage as per requirement 5.5.1b.\n2.\tOtherwise, the system ensures that the minimum current and voltage as qualified is applied at actuator level."]
["ECSS-E-ST-20-21C","ECSS - Current v1.0","5.5.4a","Recommendation","ECSS-E-ST-20-21_1400064",1,"Created","The power output capability of a generic design of actuator electronics should be 50 W DC."]
["ECSS-E-ST-20-40C","ECSS - Current v1.0","5.1.3b","Requirement","ECSS-E-ST-20-40_1580004",1,"Created","If the DEVICE Development Plan includes any variations with respect to the generic flow shown in Figure 5‑1, all the outputs expected at every new phase and associated review shall reflect these changes too. [ALL]","NOTE\t1\tFor example, in case of having phase iterations or additional sub-phases and reviews, the Verification and Validation Plans include what requirements are covered in each new phase.\nNOTE\t2\tAnnex J describes the main types of DEVICE development flow variations.\n"]
["ECSS-E-ST-20-40C","ECSS - Current v1.0","5.1.4d","Requirement","ECSS-E-ST-20-40_1580014",1,"Created","Any missing information and open points and their impact on following phases shall be assessed, registered and agreed with the customer in the MoM of the phase review with an indication of the expected time of completion of the open points. [ALL]"]
["ECSS-E-ST-20-40C","ECSS - Current v1.0","5.2.4b","Requirement","ECSS-E-ST-20-40_1580029",1,"Created","The supplier shall include the different types of verification and validation methods and test procedures, and a preliminary matrix for the traceability. [ALL]","NOTE\tFor example, which parts of the DEVICE are verified and validated separately, whether or not preliminary HW prototypes are used for DEVICE verification, specific Design-for-Test and test modes needed to accelerate otherwise too lengthy verification or validation steps, verification and validation approach when processing units are part of the DEVICE.\n"]
["ECSS-E-ST-20-40C","ECSS - Current v1.0","5.3.4c","Requirement","ECSS-E-ST-20-40_1580041",1,"Created","The following expected outputs shall be reviewed during DEVICE Architecture Definition Phase Review: [ALL]\n1.\tDEVICE Architecture Definition Report as in DRD in Annex G\n2.\tDEVICE Requirements Specification (final) as in DRD in Annex A.\n3.\tDEVICE Verification plan (update) (DVeP) as in DRD in Annex C\n4.\tDEVICE Validation Plan (update) (DVaP) as in DRD in Annex D\n5.\tDEVICE Feasibility and Risk Assessment Report (update) (DFRAR) as in DRD in Annex F\n6.\tDEVICE VCD (update)"]
["ECSS-E-ST-20-40C","ECSS - Current v1.0","5.4.5b","Requirement","ECSS-E-ST-20-40_1580059",1,"Created","The preliminary DEVICE Data Sheet shall contain all parts of the final DEVICE Data Sheet, with the same level of detail, using clearly identified estimated values for those parameter values that are not yet confirmed. [ALL]","NOTE\tFor example, preliminary values can be obtained by simulation or measurements on a prototype, while final parameter values are confirmed with the validated DEVICE.\n"]
["ECSS-E-ST-20-40C","ECSS - Current v1.0","5.5.2j","Requirement","ECSS-E-ST-20-40_1580072",1,"Created","The supplier shall justify and document any library cells selections. \n[D-ASIC, A-ASIC, --, IP]","NOTE\tFor example, some cells can be excluded from being used due to their weaker radiation performance, or some specific cells get higher priority in being used due to their more favorable timing characteristics.\n"]
["ECSS-E-ST-20-40C","ECSS - Current v1.0","5.5.5b","Requirement","ECSS-E-ST-20-40_1580089",1,"Created","The DEVICE Database shall include the pre-layout netlist. [ALL]"]
["ECSS-E-ST-20-40C","ECSS - Current v1.0","5.6.2h","Requirement","ECSS-E-ST-20-40_1580104",1,"Created","Any other global networks that need place and route decisions shall be generated. [D-ASIC, --, --, --]\n","NOTE\tFor example, reset networks.\n"]
["ECSS-E-ST-20-40C","ECSS - Current v1.0","5.6.3a","Requirement","ECSS-E-ST-20-40_1580113",1,"Created","The supplier shall perform comprehensive layout and post-layout or post-place-and-route netlist verification according to the DEVICE Verification Plan specified in DRD in Annex C and document the results in the Layout Verification Report. [D-ASIC, A-ASIC, FPGA, --]"]
["ECSS-E-ST-20-40C","ECSS - Current v1.0","5.8.2a","Requirement","ECSS-E-ST-20-40_1580134",1,"Created","Tasks specified in requirements 5.8.2b to 5.8.2f shall be performed and documented by the supplier in the DEVICE Validation Report. [ALL]"]
["ECSS-E-ST-20-40C","ECSS - Current v1.0","5.8.5b","Requirement","ECSS-E-ST-20-40_1580144",1,"Created","For DEVICEs that are used as off-the-shelf products the final DEVICE Data Sheet shall be updated based on the validation test results. [ALL]"]
["ECSS-E-ST-20-40C","ECSS - Current v1.0","A.2.1<4>e","Requirement","ECSS-E-ST-20-40_1580164",1,"Created","The DRS shall specify the functional and performance requirements of each internal element of the DEVICE, indicating their internal and external interfaces. [ALL]","NOTE 1\tExamples of elements of the DEVICE are any digital functions such as FIFOs, state machines or bus controllers, and any analogue functions like converters, mixers, amplifiers, V or I sources.\nNOTE 2\tPerformance of typical analogue and digital functions can be described following existing standards such as IEEE Std 1241-2010 for ADC, JEDEC or ECSS. \n"]
["ECSS-E-ST-20-40C","ECSS - Current v1.0","A.2.1<9>a","Requirement","ECSS-E-ST-20-40_1580179",1,"Created","The DRS shall specify the thermal environment and DEVICE thermal dissipation requirements. [D-ASIC, A-ASIC, FPGA, --]"]
["ECSS-E-ST-20-40C","ECSS - Current v1.0","B.2.1<2>j","Requirement","ECSS-E-ST-20-40_1580194",1,"Created","The DDP shall define the strategy intended to achieve best design practices and coding rules as agreed with the customer. [ALL]","NOTE 1 \tFor example, conformity to a set of good coding rules and IC best design practices to prevent problems related to asynchronous signals, metastability, clock domain crossing, reset management, glitches, pipelining, or timing or area or power optimization.\nNOTE 2\tGood examples of such set of rules and design practices are available commercially or sometimes already exist at supplier level.\n"]
["ECSS-E-ST-20-40C","ECSS - Current v1.0","C.2.1<1>m","Requirement","ECSS-E-ST-20-40_1580209",1,"Created","The DVeP shall define the strategy to verify the key analogue parameters. [D-ASIC, A-ASIC, --, --]","NOTE\tFor example, bias voltages, operating point, frequencies, bandwidth, matching, s-parameters, noise, dynamic, linear ranges or shaping times.\n"]
["ECSS-E-ST-20-40C","ECSS - Current v1.0","C.2.1<2>d","Requirement","ECSS-E-ST-20-40_1580216",1,"Created","Justifications for keeping, changing or eliminating the uncovered code shall be provided and approved by the customer. [ALL]"]
["ECSS-E-ST-20-40C","ECSS - Current v1.0","E.2.1d","Requirement","ECSS-E-ST-20-40_1580239",1,"Created","The DSMP shall define what resources and during which time frame are dedicated to support the customer in using or modifying the DEVICE. [ALL]"]
["ECSS-E-ST-20-40C","ECSS - Current v1.0","F.2.1<2>f","Requirement","ECSS-E-ST-20-40_1580251",1,"Created","The DFRAR shall include conclusions regarding the DEVICE packaging solutions and all related requirements. [ALL] "]
["ECSS-E-ST-20-40C","ECSS - Current v1.0","F.2.1<6>a","Requirement","ECSS-E-ST-20-40_1580268",1,"Created","The DFRAR shall include conclusions regarding the risks of not being able to run a comprehensive verification and validation of complex DEVICEs and the feasibility of countermeasures proposed. [ALL]","NOTE  \tFor example, highly reconfigurable or reprogrammable DEVICEs, many core DEVICEs or complex mixed-signal DEVICEs. \n"]
["ECSS-E-ST-20-40C","ECSS - Current v1.0","G.2.1l","Requirement","ECSS-E-ST-20-40_1580284",1,"Created","The DADR shall identify which circuit architecture elements are introduced to meet the test requirements. [ALL]","NOTE  \tFor example, Production Tests such as scan paths, DFT logic, observability and controllability points, measurement points, test busses and boundary scan as in JTAG, see IEEE 1149.1-2013, performed during verification and validation.\n"]
["ECSS-E-ST-20-40C","ECSS - Current v1.0","H.2.1c","Requirement","ECSS-E-ST-20-40_1580288",1,"Created","The DDS shall contain a full functionality description including all operating modes. [ALL] "]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","4.1.3f","Requirement","ECSS-E-ST-20_0020012",1,"Unchanged","The functionality shall be provided to repeat the transmission of all the executable commands without degradation of the function or a change of its status."]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","4.2.1.1a","Requirement","ECSS-E-ST-20_0020021",2,"Informative Change","Failure propagation shall meet the following conditions:\n1.\tA single hardware failure does not propagate to neighbouring components circuits or interfaces in an undetermined way.\n2.\tFailure propagation is verified by analysis.\n3.\tMechanical, thermal or electrical propagation of single hardware failures does not impair the corresponding protection or redundancy implemented at equipment or system level.\n4.\tSingle hardware failure does not propagate to equipment or functions under different contractual responsibility than the item where the failure takes place.","NOTE\t1\t4.2.1.1a.4 is normally covered by specification of fault emission and tolerance conditions.\nNOTE\t2\tComponent assembly (e.g. single cavity hybrid) and integrated circuits, especially if they contain redundancy or protection, require special attention.”\n"]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","4.2.1.1u","Requirement","ECSS-E-ST-20_0020041",1,"Unchanged","Any on-board autonomous protection override, leading to hazardous situation for the mission (category 1 and 2 criticality), shall not be implemented. ","NOTE \tE.g. an LCL function for instance protecting the main power Bus against a short circuit at Bus user level or Main Bus over-voltage protection.\n"]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","4.2.1.1v","Requirement","ECSS-E-ST-20_0020042",1,"Unchanged","SEE shall not activate protection circuits of essential functions. ","NOTE \tMitigation techniques can be implemented to avoid such phenomena: filtering, majority voting, etc\n"]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","4.2.1.2.3l","Requirement","ECSS-E-ST-20_0020439",1,"Created","The electrical insulation materials shall have a dielectric strength in excess of 2 times the peak operative voltage in the actual application.","NOTE \tAs a reference, the dielectric strength value of Air (3 kV/mm) can be used as selection criterion for materials.\n\tFor resistivity, typical value is 10E9 Ohm.m.\n\tThe selection of insulation material needs to take into account potential charging/ESD constraints (see ECSS-E-ST-20-06).\n"]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","4.2.1.2.3y","Requirement","ECSS-E-ST-20_0020452",1,"Created","A dedicated analysis shall confirm that reliable insulation of critical lines or nets is not jeopardized by failures, at system, subsystem or equipment level.","NOTE \tFailures can be of electrical, thermal or mechanical nature (for example issues of interference especially in integration and manufacturing phases). Dissipative failures are part of the analysis required.\n"]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","4.2.3m","Requirement","ECSS-E-ST-20_0020061",2,"Unchanged","The following shall be performed for any connector the loss of which can lead to the loss of the mission:\n1.\tDocument the connector in the single point failure list\n2.\tVerify and document its integrity up to the highest spacecraft integration level, to avoid accidental demating."]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","4.2.4f","Requirement","ECSS-E-ST-20_0020069",1,"Unchanged","Test points on equipment shall be such that unintentional connection of these points to ground does not damage the equipment."]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","5.2.2.2e","Requirement","ECSS-E-ST-20_0020094",1,"Unchanged","A system margin of not less than 5 % at AR on available power and energy shall be included in the budget, available (as a minimum) with the solar array string losses as defined by the customer with the minimum of one string lost and one battery cell failed during all the designed life of the power system including all spacecraft modes of operation."]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","5.3b","Requirement","ECSS-E-ST-20_0020097",2,"Unchanged","It shall not be possible to inhibit a protection feature if such an inhibition can lead to the loss of the main primary power bus in case of a single failure at spacecraft level."]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","5.5.2h","Requirement","ECSS-E-ST-20_0020112",1,"Unchanged","In the flight configuration, means to prevent differential voltage due to electrostatic charging between solar array structure and the spacecraft electrical ground reference shall be implemented."]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","5.5.3f","Requirement","ECSS-E-ST-20_0020127",1,"Unchanged","The BOL worst and best case power calculations shall include the parameters indicated in Table 5‑1."]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","5.6.2c","Requirement","ECSS-E-ST-20_0020138",1,"Unchanged","Specific measures shall be taken in the battery design to keep under control the series inductance and the magnetic moment."]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","5.6.4e","Requirement","ECSS-E-ST-20_0020161",1,"Unchanged","Any test equipment interfacing with the battery shall include an associated undervoltage, overvoltage, overcurrent and over-temperature activated insulation switch."]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","5.6.5.2d","Recommendation","ECSS-E-ST-20_0020398",1,"Unchanged","The failure of one or more cells within a battery due to imbalance in the state of charge, temperature or other parameter between cells should be prevented by the battery control electronics."]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","5.7.2m","Requirement","ECSS-E-ST-20_0020182",1,"Unchanged","A fully regulated bus shall have a nominal ripple voltage below 0,5 % peak-to-peak of the nominal bus voltage, measured at the regulation point with at least 1 MHz bandwidth."]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","5.7.3i","Requirement","ECSS-E-ST-20_0020197",2,"Unchanged","Battery charge and discharge management shall be such that a single failure for unmanned missions and two failures for manned missions does not impair the lifetime of the energy storage system with respect to minimum or maximum voltage as well as maximum charge or maximum discharge current.","NOTE \tSuch failure tolerance can be implemented at cell, battery or subsystem level.\n"]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","5.7.5h","Requirement","ECSS-E-ST-20_0020211",1,"Unchanged","A switching converter shall be able to reach nominal operation when the nominal input voltage is applied with any slope that can be provided by the power source and its associated impedance, connected to the switching converter."]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","5.8.1m","Requirement","ECSS-E-ST-20_0020228",2,"Unchanged","<<deleted>>"]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","5.8.2b","Requirement","ECSS-E-ST-20_0020233",1,"Unchanged","With the exception of the solar array, routing of power lines shall be near ground."]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","5.11.1a","Recommendation","ECSS-E-ST-20_0020248",2,"Unchanged","The requirements of this Clause 5 should be verified by the verification methods and at the verification points listed in Table 8‑3.","NOTE\t1\tTable 8‑3 can be used as a starting point for the definition of the verification methods.\nNOTE\t2\tFor more details on verification, see also ECSS-E-ST-10-02, in particular requirements 5.2.1c, 5.2.1d and 5.2.1e.\n"]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","6.3.1.2a","Requirement","ECSS-E-ST-20_0020260",1,"Unchanged","The list of points where the margin is demonstrated (critical points) shall be submitted to the customer for approval."]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","6.3.6a","Requirement","ECSS-E-ST-20_0020277",1,"Unchanged","The spacecraft shall be RF compatible with all antenna-connected equipments and subsystems, the compatibility criteria being based on the mission performance and operability requirements."]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","6.4.2b","Requirement","ECSS-E-ST-20_0020291",1,"Unchanged","If the demonstration of safety margins is done by test, the spacecraft suite of equipment and subsystems shall be operated in a manner simulating actual operations, agreed with the customer."]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","7.2.2.3.1b","Requirement","ECSS-E-ST-20_0020307",1,"Unchanged","Whenever an antenna RF chain is attached to the radiating element its impact on the radiating element performances shall be assessed."]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","7.2.2.3.4c","Requirement","ECSS-E-ST-20_0020322",1,"Unchanged","In all RF BFN structures having a central conductor (ideally insulated), the thermal power generated by Joule effect on the conductor itself shall be quantified and its impact on antenna performances assessed. "]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","7.2.3.1b","Requirement","ECSS-E-ST-20_0020342",1,"Unchanged","It shall be demonstrated that the generation of passive inter-modulation products that can occur at the antenna ports is below the specified limits agreed with the customer."]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","7.3.3.2a","Requirement","ECSS-E-ST-20_0020352",1,"Unchanged","RF components and equipments of the RF chain shall be designed and verified to withstand the maximum specified operating RF power levels plus safety margins agreed with the customer in the development phase. "]
["ECSS-E-ST-20C Rev.2","ECSS - Current v1.0","7.4.4e","Requirement","ECSS-E-ST-20_0020363",1,"Unchanged","Acceptance testing shall be carried out on flight components, equipments or systems over an acceptance temperature range to be agreed with the customer, range which can be limited to ambient temperature."]
["ECSS-E-ST-31-02C Rev.1","ECSS - Current v1.0","5.1.1b","Requirement","ECSS-E-ST-31-02_1190004",2,"Normative Change","The technical specification specified in 5.1.1a shall be written in accordance with DRD in ECSS-E-ST-10-06 Annex A."]
["ECSS-E-ST-31-02C Rev.1","ECSS - Current v1.0","5.1.3f","Requirement","ECSS-E-ST-31-02_1190019",2,"Normative Change","To ensure that a specification is verifiable, requirement 5.1.3f of ECSS-E-ST-10-06 shall apply."]
["ECSS-E-ST-31-02C Rev.1","ECSS - Current v1.0","5.3.2d","Requirement","ECSS-E-ST-31-02_1190031",1,"Unchanged","Calibration of laboratory equipment shall be verified prior to their use."]
["ECSS-E-ST-31-02C Rev.1","ECSS - Current v1.0","5.5.3.2c","Requirement","ECSS-E-ST-31-02_1190049",2,"Normative Change","Qualification shall be carried out on hardware representative of the end item in terms of design, materials, tooling and methods."]
["ECSS-E-ST-31-02C Rev.1","ECSS - Current v1.0","5.5.3.3.2a","Requirement","ECSS-E-ST-31-02_1190056",2,"Deleted","<<deleted and moved into requirement 5.5.3.3.1a>>"]
["ECSS-E-ST-31-02C Rev.1","ECSS - Current v1.0","5.6.3.2.1a","Requirement","ECSS-E-ST-31-02_1190080",1,"Unchanged","The test tolerances specified in Table 5-2 shall be applied to the nominal test values specified."]
["ECSS-E-ST-31-02C Rev.1","ECSS - Current v1.0","5.6.6b","Requirement","ECSS-E-ST-31-02_1190094",1,"Unchanged","The supplier shall analyse the number of cycles above the 2000 cycles, to which the TPHTE can be exposed before reaching the Woehler curve."]
["ECSS-E-ST-31-02C Rev.1","ECSS - Current v1.0","5.6.9.1e","Requirement","ECSS-E-ST-31-02_1190110",1,"Unchanged","For each temperature step, the temperatures along the length of the unit shall be measured and recorded."]
["ECSS-E-ST-31-02C Rev.1","ECSS - Current v1.0","5.6.9.5a","Requirement","ECSS-E-ST-31-02_1190126",1,"Unchanged","Start-up with low power shall be verified by testing with and without thermal inertia on the evaporator heater system."]
["ECSS-E-ST-31-02C Rev.1","ECSS - Current v1.0","5.6.10.1d","Requirement","ECSS-E-ST-31-02_1190131",1,"Unchanged","Sinusoidal and random vibration tests shall be performed at the maximum internal pressure, which the device is exposed to during ascent."]
["ECSS-E-ST-31-02C Rev.1","ECSS - Current v1.0","5.7b","Requirement","ECSS-E-ST-31-02_1190157",1,"Unchanged","The procedures specified in 5.7a shall be compatible with the safety requirements and personnel control requirements at the facility where the operations are conducted."]
["ECSS-E-ST-31-02C Rev.1","ECSS - Current v1.0","6.1c","Requirement","ECSS-E-ST-31-02_1190273",1,"Created","It shall be confirmed by analysis that the performance requirements of the intended application are covered by the previous qualification campaign."]
["ECSS-E-ST-31-02C Rev.1","ECSS - Current v1.0","A.2.1<2>a","Requirement","ECSS-E-ST-31-02_1190168",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-31-02C Rev.1","ECSS - Current v1.0","A.2.1<3>a","Requirement","ECSS-E-ST-31-02_1190169",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-31-02C Rev.1","ECSS - Current v1.0","B.2.1<8>a","Requirement","ECSS-E-ST-31-02_1190186",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-31-02C Rev.1","ECSS - Current v1.0","C.2.1<5>a","Requirement","ECSS-E-ST-31-02_1190198",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-31-02C Rev.1","ECSS - Current v1.0","F.2.1<1>a","Requirement","ECSS-E-ST-31-02_1190221",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-31-02C Rev.1","ECSS - Current v1.0","F.2.1<6>a","Requirement","ECSS-E-ST-31-02_1190228",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-31-02C Rev.1","ECSS - Current v1.0","G.2.1<4>a","Requirement","ECSS-E-ST-31-02_1190244",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-31-02C Rev.1","ECSS - Current v1.0","H.2.1<5>b","Requirement","ECSS-E-ST-31-02_1190258",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-31-04C","ECSS - Current v1.0","5.4e","Requirement","ECSS-E-ST-31-04_1370009",1,"Created","When model features are simplified as specified in requirement 5.4d, STEP-TAS interfaces shall emit appropriate diagnostic messages."]
["ECSS-E-ST-31C","ECSS - Current v1.0","4.1.8a","Requirement","ECSS-E-ST-31_0800012",1,"Created","The TCS shall be designed for heat flux effects as well as transient phenomena during descent, entry and landing including:\n    1. loss of MLI efficiency due to re-pressurization;\n    2. heating and cooling effects due to the inlet of air and gas for re-pressurization;\n    3. requirement for special heat sinks during descent."]
["ECSS-E-ST-31C","ECSS - Current v1.0","4.2.1g","Requirement","ECSS-E-ST-31_0800022",1,"Created","The TCS shall conform to the following requirements to be specified in the TCS specification:\n    1. Temperature gradients\n    2. Temperature stability\n    3. Temperature uniformity\n    4. Heat flux\n    5. Heat storage\n    6. Heat lift\n    7. Electrical power allocation for heating and cooling\n    8. TM/TC allocation for TCS parameter;\n        NOTE For requirements on TM/TC, see 4.3.5.\n    9. Mass allocation for TCS."]
["ECSS-E-ST-31C","ECSS - Current v1.0","4.3.4.1b","Requirement","ECSS-E-ST-31_0800043",1,"Created","The TCS shall be designed for effects of heat soak after firing of thrusters."]
["ECSS-E-ST-31C","ECSS - Current v1.0","4.3.8b","Requirement","ECSS-E-ST-31_0800052",1,"Created","TCS specific requirements for ground support equipment shall be specified by the thermal control subsystem."]
["ECSS-E-ST-31C","ECSS - Current v1.0","4.4.6a","Requirement","ECSS-E-ST-31_0800067",1,"Created","The TCS shall be designed such that conformance to performance requirements of clause 4.2 can be demonstrated by thermal analyses and thermal test.\n    NOTE Modularity of the TCS design can facilitate its predictability and testability."]
["ECSS-E-ST-31C","ECSS - Current v1.0","4.5.2.1g","Requirement","ECSS-E-ST-31_0800084",1,"Created","Conformance to specified performance shall be demonstrated by performing thermal balance, thermal vacuum and climatic tests."]
["ECSS-E-ST-31C","ECSS - Current v1.0","4.5.3.1e","Requirement","ECSS-E-ST-31_0800097",1,"Created","The TBT shall provide accurate and reliable input data for the thermal model correlation."]
["ECSS-E-ST-31C","ECSS - Current v1.0","4.6.2b","Requirement","ECSS-E-ST-31_0800115",1,"Created","The number of samples to be manufactured for evaluation and testing shall be agreed with the customer."]
["ECSS-E-ST-31C","ECSS - Current v1.0","4.6.8a","Requirement","ECSS-E-ST-31_0800127",1,"Created","Storage conditions shall not cause any degradation to the thermal hardware. "]
["ECSS-E-ST-31C","ECSS - Current v1.0","A.2.1<1>b","Requirement","ECSS-E-ST-31_0800145",1,"Created","Any open issue, assumption and constraint relevant to this document shall be stated and described."]
["ECSS-E-ST-31C","ECSS - Current v1.0","A.2.1<7>a","Requirement","ECSS-E-ST-31_0800155",1,"Created","The software tools to be used for development of the mathematical models shall be described.\n    NOTE 1 The software to be used for the preparation and delivery of GMM's should be ESARAD or THERMICA.\n    NOTE 2 The software to be used for the preparation and delivery of TMM's should be ESATAN."]
["ECSS-E-ST-31C","ECSS - Current v1.0","B.2.1<7>a","Requirement","ECSS-E-ST-31_0800175",1,"Created","The following information, in a format as agreed with the system authority, shall be attached to the document as annexes:\n    1. Identification of delivered computer files,\n    2. GMM and TMM source lists based on applied tools."]
["ECSS-E-ST-31C","ECSS - Current v1.0","C.2.1<7>b","Requirement","ECSS-E-ST-31_0800190",1,"Created","The description shall include a list of all input data including starting conditions for the analysis cases."]
["ECSS-E-ST-31C","ECSS - Current v1.0","D.2.1<5>a","Requirement","ECSS-E-ST-31_0800205",1,"Created","Reference shall be given to subsystem specific ICDs to be delivered as separate package."]
["ECSS-E-ST-31C","ECSS - Current v1.0","E.2.1<8>a","Requirement","ECSS-E-ST-31_0800220",1,"Created","The TCS thermal balance test specification shall list the test activity flow and the associated requirements."]
["ECSS-E-ST-31C","ECSS - Current v1.0","F.2.1<3>a","Requirement","ECSS-E-ST-31_0800227",1,"Created","The TCS detailed design description shall list the applicable directory or glossary and the meaning of specific terms or abbreviations utilized in this document."]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","6.1b","Permission","ECSS-E-ST-32-01_0810319",2,"Normative Change","For unmanned, single‐mission, space vehicles and their payloads, and GSE the identification of PFCIs may be limited to the items listed in clause 11.2.2.1."]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","6.3.2a","Requirement","ECSS-E-ST-32-01_0810024",2,"Normative Change","The evaluation procedure for a PFCI considered as a safe life item shall be in conformance with Figure 6-4, for metallic items, and Figure 6-5, for composite, bonded and sandwich items."]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","6.3.4b","Requirement","ECSS-E-ST-32-01_0810042",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","6.4.4a","Requirement","ECSS-E-ST-32-01_0810057",1,"Unchanged","A fracture control summary report shall be provided with each deliverable flight hardware item."]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","7.2.2c","Requirement","ECSS-E-ST-32-01_0810069",1,"Unchanged","In cases where the most critical location or orientation of the initial crack is not obvious, the analysis shall consider a sufficient number of locations and orientations."]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","7.2.6b","Requirement","ECSS-E-ST-32-01_0810085",2,"Normative Change","The initial crack sizes used in the analysis shall be defined based on the NDT level or proof load screening used for the item.","NOTE\tSee also clause 10 and ECSS-Q-ST-70-15.\n"]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","7.2.8d","Requirement","ECSS-E-ST-32-01_0810094",1,"Unchanged","The loading spectrum shall be an envelope of all the credible load events that can be encountered during the design life."]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","8.2.3.1b","Requirement","ECSS-E-ST-32-01_0810111",1,"Unchanged","Pressurized structures shall be in conformance with ECSS-E-ST-32-02, clause 4.4."]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","8.2.6b","Requirement","ECSS-E-ST-32-01_0810125",1,"Unchanged","If provision 8.2.6a is not met, hazardous fluid containers shall:\n    1. Have safe-life against rupture and leakage.\n    2. Be treated and certified the same as pressure vessels when the contained fluid has a delta pressure greater than one atmosphere."]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","8.4.2.1c","Requirement","ECSS-E-ST-32-01_0810139",1,"Informative Change","The effects of the potential manufacturing defects on the structural integrity shall be established, documented and verified.","NOTE\tExamples of such effects are strength, stability, and fatigue.\n"]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","8.4.4.1c","Requirement","ECSS-E-ST-32-01_0810155",2,"Normative Change","A fail safe item shall be inspected at least by close visual testing covering hundred per cent of the item before each flight, in addition to NDT during manufacturing."]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","8.4.4.2f","Requirement","ECSS-E-ST-32-01_0810161",1,"Unchanged","For a safe life item the test programme (including applied LEF and fatigue spectrum) shall be approved by the customer; "]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","8.7h","Permission","ECSS-E-ST-32-01_0810326",1,"Unchanged","If a factor of safety on strength of 5 or greater can be shown, and if approved by the customer, the proof test in conformance with 8.7g.1 may be omitted."]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","9a","Requirement","ECSS-E-ST-32-01_0810194",1,"Informative Change","Materials shall be selected and controlled in conformance with ECSS-Q-ST-70 “Materials, mechanical parts and processes”.","NOTE\tThe material selection process takes into account structural and non-structural requirements. The materials selected possess the appropriate fracture toughness, crack-growth characteristics, and structural properties, such as Young’s modulus and yield strength, in specified environmental conditions.\n"]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","10.3.1n","Requirement","ECSS-E-ST-32-01_0810236",2,"Normative Change","Special fracture control NDT shall be used only in special cases where limited life is demonstrated for standard initial crack sizes and serious problems can occur as a result of redesign or acceptance of the limited life, and its application is subject to approval by the customer.","NOTE \tFor special fracture control NDT, see in particular clause 9 of ECSS-Q-ST-70-15.\n"]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","10.3.3g","Requirement","ECSS-E-ST-32-01_0810224",2,"Normative Change","Safe life items made of other non-metallic materials shall be non-destructive tested and proof tested in conformance with clause 8.5."]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","10.4.1b","Requirement","ECSS-E-ST-32-01_0810228",2,"Deleted","<<deleted (moved to ECSS-Q-ST-70-15)>>"]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","10.4.2.2e","Requirement","ECSS-E-ST-32-01_0810240",2,"Deleted","<<deleted (moved to ECSS-Q-ST-70-15)>>"]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","10.4.3.5c","Requirement","ECSS-E-ST-32-01_0810264",2,"Deleted","<<deleted (moved to ECSS-Q-ST-70-15)>>"]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","10.5.2.1b","Requirement","ECSS-E-ST-32-01_0810270",2,"Deleted","<<deleted (moved to ECSS-Q-ST-70-15)>>"]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","10.6.2d","Requirement","ECSS-E-ST-32-01_0810285",1,"Unchanged","For each fracture-critical item a log shall be maintained, which documents the environmental and operational aspects (including fluid exposure for pressure vessels) of all storage conditions during the life of the item."]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","10.7.2.2d","Requirement","ECSS-E-ST-32-01_0810301",1,"Unchanged","For composite, bonded and sandwich parts the fatigue verification shall be based on tests of representative defects."]
["ECSS-E-ST-32-01C Rev. 2","ECSS - Current v1.0","11.2.2.8a","Permission","ECSS-E-ST-32-01_0810354",1,"Created","X-ray testing of fusion welded joints post proof test may be omitted. "]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.2.3.1e","Requirement","ECSS-E-ST-32-02_1660019",1,"Created","Procedures to ensure compatibility of the pressurizing system with the structural capability of the pressurized hardware shall be established."]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.2.3.2e","Requirement","ECSS-E-ST-32-02_1660028",1,"Created","The minimum internal pressure to guaranty structural stabilization shall be identified and included in the acceptance data package."]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.3.2.1a","Requirement","ECSS-E-ST-32-02_1660052",1,"Created","Clause 5.2 on structural engineering shall be applied.","NOTE \tClause 5.2 refers to the requirements of ECSS-E-ST-32, which include requirements on stiffness, strength and stability.\n"]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.3.2.1i","Requirement","ECSS-E-ST-32-02_1660060",1,"Created","For material selection, material design allowables and their characterisation, requirements shall be applied in conformance with ECSS-E-ST-32."]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.3.3.1b","Requirement","ECSS-E-ST-32-02_1660075",1,"Created","A stiffness demonstration shall be performed by analysis and test."]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.3.3.2c","Requirement","ECSS-E-ST-32-02_1660089",1,"Created","A second qualification test article shall be submitted to the following sequence of tests, or alternative sequence agreed between customer and supplier:\n1.\tNDT;\n2.\tproof pressure test;\n3.\tleak test;\n4.\tNDT;\n5.\tvibration tests;\n6.\tpressure cycling test;\n7.\tleak test;\n8.\tdesign burst pressure test;\n9.\tburst test.","NOTE \tThis the standard sequence of tests specified in ECSS-E-ST-10-03. Examples of rationale for changes to this sequence are:\n·\tAdditional qualification test types (e.g. thermal) or inspection steps (e.g. before burst pressure testing).\n·\tIdentified risk that for the particular design the defined sequence can be either unconservative or unnecessarily conservative.\n·\tOmission of test types based on e.g. successful heritage/similarity, testing of engineering model or analysis-based verification approach.\n"]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.3.4.1f","Requirement","ECSS-E-ST-32-02_1660105",1,"Created","The CPV shall exhibit a LBB failure mode, if requested by the customer.","NOTE \tExperience with CPV is limited, and LBB demonstration can be difficult or not relevant for the composite wall. No definite guidance is therefore provided in this standard.\n"]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.3.4.2j","Requirement","ECSS-E-ST-32-02_1660124",1,"Created","If external cycling loads are applied, the load shall be cycled to design limit load for four times the predicted number of operating cycles of the most severe design condition. ","NOTE \t1\tExamples: Destabilizing load with constant minimum internal pressure or maximum additive load with a constant MDP.\t\nThe actual cycle life can be complex and is often replaced by a simplified test spectrum, of comparable severity, in the cycling test.\nNOTE \t2\tDesign limit load (DLL) for pressurized hardware is normally defined, in accordance with Figure 4-1 and Table 4-1 of ECSS-E-ST-32-10, as KP x KM x limit load (LL) for pressure load. For loads other than internal pressure the Satellite Test Logic of Figure 4-1 of ECSS-E-ST-32-10 is applied, for example.\n"]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.4.2.1d","Permission","ECSS-E-ST-32-02_1660135",1,"Created","For pressurized structures with a non-hazardous LBB failure mode, the safe-life demonstration specified in 4.4.2.1c may be replaced by a fatigue life demonstration by analysis or test or both, with customer approval.","NOTE \tThis can have an impact on the mission reliability.\nNHLBB demonstration, either full or partial, can be challenging for pressurized structures, because pressure is most likely not the dominant loading type.\t\nAlso, if a project is rated highly critical by the customer due to considerations other than safety, safe life to leakage verification of the metallic pressurized structure is sometimes requested instead of, or in addition to, LBB verification.\nIt is recommended that this agreement is achieved as early as possible, for example in the statement of work and associated baseline requirements, and then reflected in the Fracture Control Plan.\n"]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.4.3.1a","Requirement","ECSS-E-ST-32-02_1660150",1,"Created","Clause 5.2 on structural engineering shall be applied.","NOTE \t1\tPressurized structures are both pressurized hardware and structures. It is specifically emphasized here that it is important to ensure that both the specific pressurized hardware requirements of this standard and the structural requirements of the other ECSS structural standards are met.\t\nSolid propellant motor cases are not covered by this standard, unless specified or agreed otherwise.\nNOTE \t2\tFor composite hardware this includes consideration of stress rupture (see 5.2j) as well as prevention of failure due to mechanical impact damage (see 4.2.3 on damage control).\n"]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.4.3.1l","Requirement","ECSS-E-ST-32-02_1660161",1,"Created","For ‘process control’, requirements shall be in conformance with ECSS-Q-ST-70."]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.4.4.1i","Requirement","ECSS-E-ST-32-02_1660180",1,"Created","Qualification tests shall be conducted according to clause 4.4.4.2 to demonstrate the structural adequacy of the design."]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.4.4.3d","Requirement","ECSS-E-ST-32-02_1660196",1,"Created","Clause 5.5 shall be applied to the acceptance tests."]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.5.1.3b","Permission","ECSS-E-ST-32-02_1660210",1,"Created","The pressure cycling test specified in 4.5.1.3.a, and the final burst test specified in 4.5.1.3.a may be deleted with customer approval.","NOTE \tPressure cycling testing is often waived based on analytical fatigue verification indicating low fatigue damage caused by pressure cycles up to proof pressure level.\n"]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.5.2.2f","Requirement","ECSS-E-ST-32-02_1660225",1,"Created","Except in the case specified in 4.5.2.2e, ‘safe life item’ demonstration shall be performed for the metallic liner by analysis or test or both in conformance with ECSS-E-ST-32-01.","NOTE \tPlastically operating liners, during autofrettage or post autofrettage cycles, can be difficult to verify for crack propagation by analysis only. See for example 7.2.8.i-j and 7.3.b of ECSS-E-ST-32-01.\n"]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.5.2.3a","Requirement","ECSS-E-ST-32-02_1660233",1,"Created","A first qualification test article shall be submitted to the following sequence of tests, or alternative sequence agreed between customer and supplier:\n1.\tnon-destructive testing (NDT);\n2.\tproof pressure test;\n3.\tleak test;\n4.\tNDT;\n5.\tpressure cycling test;\n6.\tleak test;\n7.\tdesign burst pressure test;\n8.\tburst test.","NOTE \tThis the standard sequence of tests defined in ECSS-E-ST-10-03. Examples of rationale for changes to this sequence are:\n·\tAdditional qualification test types (e.g. thermal) or inspection steps (e.g. before burst pressure testing).\n·\tIdentified risk that for the particular design the defined sequence can be either unconservative or unnecessarily conservative.\n·\tOmission of test types based on e.g. successful heritage/similarity, testing of engineering model or analysis-based verification approach. Examples: pressure cycling test, burst test, NDT steps.\n"]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.5.3.2h","Requirement","ECSS-E-ST-32-02_1660255",1,"Created","Qualification tests shall be conducted according to clause 4.5.3.3 to demonstrate the structural adequacy of the design."]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.5.3.3g","Requirement","ECSS-E-ST-32-02_1660268",1,"Created","Clause 5.4 shall be applied to the qualification tests."]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.6.1.2h","Requirement","ECSS-E-ST-32-02_1660284",1,"Created","For ‘process control’, requirements shall be in conformance with ECSS-Q-ST-70."]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.6.2.2h","Requirement","ECSS-E-ST-32-02_1660303",1,"Created","Qualification tests shall be conducted in conformance with clause 4.6.2.3 to demonstrate the structural adequacy of the design."]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.6.2.3f","Requirement","ECSS-E-ST-32-02_1660314",1,"Created","NDT operations shall be applied to the over-wrap, in addition to NDT on the liner."]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.6.3.2g","Requirement","ECSS-E-ST-32-02_1660330",1,"Created","Except in the case specified in 4.6.3.2e, ‘safe life item’ demonstration of the liner shall be performed in accordance with ECSS-E-ST-32-01:\n1.\tby test for non-metallic items;\n2.\tby analysis or test or both for metallic items, for example metallic bosses.","NOTE \tPlastically operating metallic parts of liners, during autofrettage or post autofrettage cycles, can be difficult to verify for crack propagation by analysis only. See for example 7.2.8.i-j and 7.3.b of ECSS-E-ST-32-01.\n"]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","4.6.3.3c","Requirement","ECSS-E-ST-32-02_1660340",1,"Created","A second qualification test article shall be submitted to the following sequence of tests, or alternative sequence agreed between customer and supplier:\n1.\tNDT;\n2.\tproof pressure test;\n3.\tleak test;\n4.\tNDT;\n5.\tvibration tests;\n6.\tpressure cycling test;\n7.\tleak test;\n8.\tdesign burst pressure test;\n9.\tburst test.","NOTE \tThis the standard sequence of tests defined in ECSS-E-ST-10-03. Examples of rationale for changes to this sequence are:\n·\tAdditional qualification test types (e.g. thermal) or inspection steps.\n·\tIdentified risk that for the particular design the defined sequence can be either unconservative or unnecessarily conservative.\n·\tOmission of test types based on e.g. successful heritage/similarity, testing of engineering model or analysis-based verification approach.\n"]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","5.2i","Requirement","ECSS-E-ST-32-02_1660359",1,"Created","Limit loads, design limit loads and associated load cases shall be defined, in agreement with the customer.","NOTE \t1 \tRefer to ECSS-E-ST-32, 4.2.7 and 4.2.8.\nNOTE \t2 \tThis includes definition of MEOP and MDP values (see definitions in ECSS-E-ST-32). Note that MDP includes KM and KP, but not KQ, KMP and KLD according to Figure 4-1 of ECSS-E-ST-32-10. For loads other than internal pressure the Satellite Test Logic of Figure 4-1 of ECSS-E-ST-32-10 is applied, for example.\nNOTE \t3 \tMEOP or MDP can be specified by the customer, or derived, for example, from an analysis of the pressurized system.\nNOTE \t4 \tMDP is equal to or larger than MEOP. Via the factors KP and KM, MDP accounts for uncertainties that are not already accounted for in MEOP. ECSS-E-ST-32-10 mentions a typical KM of 1,0 for internal pressure loads for pressurized hardware. Note that a different KM>1 can apply to the finite element analysis of the pressurized hardware, especially for verification of non-pressure loads.\nNOTE \t5 \tFault tolerance requirements are sometimes specified by the customer for MEOP.\nNOTE \t6 \tDifferent components and locations in a pressurized system can have different MEOPs and MDPs. For example, due to pressure transient peaks, barriers, regulators. \nNOTE \t7 \tHistorically the MDP definition of ECSS-E-ST-32 can differ from other standards, and it is difficult to achieve full consistency. Example: MDP in NASA standards or similar are equivalent to MEOP per ECSS-E-ST-32 definition (including fault tolerance)\n"]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","5.3.3f","Requirement","ECSS-E-ST-32-02_1660375",1,"Created","It shall be shown that the length of the through crack becomes equal to or greater than 10 times the specimen's thickness and remains stable at MDP."]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","5.4.1b","Requirement","ECSS-E-ST-32-02_1660389",1,"Created","When the hardware mounting induces axial or radial restrictions on the pressure driven expansion of the hardware, the pressure test fixture shall simulate the structural response or reaction loads of the flight mounting."]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","5.4.4a","Requirement","ECSS-E-ST-32-02_1660404",1,"Created","Vibration testing shall be conducted in accordance with ECSS-E-ST-10-03 at the most critical combination or combinations of pressure condition and  vibration environment.","NOTE \tAdequate coverage of critical criteria (e.g. strength, stability, natural frequencies, cavitation) can necessitate repeating vibration tests at more than one internal pressure. In many cases the proof test scopes the structural integrity of the pressurized wall and vibration testing can be performed at a reduced pressure. For example, system test at low pressure ('empty tank testing') can be specified.\n"]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","5.4.7b","Requirement","ECSS-E-ST-32-02_1660412",1,"Created","The burst pressure shall be recorded."]
["ECSS-E-ST-32-02C Rev.2","ECSS - Current v1.0","5.7.2c","Requirement","ECSS-E-ST-32-02_1660434",1,"Created"," "]
["ECSS-E-ST-32-03C","ECSS - Current v1.0","4.4h","Requirement","ECSS-E-ST-32-03_0100011",1,"Created","A specific format of reduced matrices and OTMs shall be agreed with the customer."]
["ECSS-E-ST-32-03C","ECSS - Current v1.0","5.4.3c","Requirement","ECSS-E-ST-32-03_0100028",1,"Created","The maximum acceptable non-zero terms of the (6x6) matrix KR shall be agreed.\n    ","NOTE 1 All the terms of ER are theoretically equal to zero.\nNOTE 2 For 1 meter or 1 radian rigid motion, typical acceptable values of ER terms are not exceeding 1.E-03 joule."]
["ECSS-E-ST-32-03C","ECSS - Current v1.0","6.2b","Requirement","ECSS-E-ST-32-03_0100043",1,"Created","If the mathematical model predictions are outside the applicable correlation criteria, the mathematical model shall be modified and the analysis rerun until it meets the criteria.\n    ","NOTE 1 This process is known as “model updating”.\nNOTE 2 The FE model is commonly said to be “valid” when it meets the correlation criteria."]
["ECSS-E-ST-32-08C Rev. 1","ECSS - Current v1.0","4.2.2a","Requirement","ECSS-E-ST-32-08_0220002",1,"Unchanged","For composites, the specified elastic modulus shall be verified by test on representative samples, in tension and in compression directions.\n    ","NOTE 1 For metallic and alloy, it can be based on values certified by the manufacturer.\nNOTE 2 The elastic modulus defined as the ratio between the uniaxial stress and the strain (e.g. Young’s modulus, compressive modulus, shear modulus) is for metals and alloys weakly dependant on heat-treatment and orientation. However, for fibre reinforced materials, the elastic modulus depends on the fibre orientation."]
["ECSS-E-ST-32-08C Rev. 1","ECSS - Current v1.0","4.2.7c","Requirement","ECSS-E-ST-32-08_0220012",1,"Unchanged","The CTE of composite materials used in high stability structural applications shall be determined by means of dry test coupons under dry test conditions after release of all potential moisture."]
["ECSS-E-ST-32-08C Rev. 1","ECSS - Current v1.0","4.4.2a","Requirement","ECSS-E-ST-32-08_0220036",2,"Deleted","<< deleted, see Note 2 in 4.4.1b. >>"]
["ECSS-E-ST-32-08C Rev. 1","ECSS - Current v1.0","4.5.2b","Requirement","ECSS-E-ST-32-08_0220041",2,"Normative Change","The supplier shall justify his choice of composite material for approval by the customer at MPCB, including the provision of the technical information on which the selection was based."]
["ECSS-E-ST-32-08C Rev. 1","ECSS - Current v1.0","4.6.2f","Requirement","ECSS-E-ST-32-08_0220056",2,"Normative Change","Except for near net shape manufacturing techniques, the production laminate shall be fabricated to a greater size than the final one, then cut down to the final dimensions , and the excess pieces be used for quality control testing.\n    ","NOTE Example of near net shape manufacturing techniques is RTM “Resin Transfer Moulding”."]
["ECSS-E-ST-32-08C Rev. 1","ECSS - Current v1.0","4.6.5e","Requirement","ECSS-E-ST-32-08_0220071",2,"Normative Change","The NDI plan shall be available for review by the customer upon request at MPCB."]
["ECSS-E-ST-32-10C Rev.2 Corr.1","ECSS - Current v1.0","4.1.5.2b","Requirement","ECSS-E-ST-32-10_0110011",1,"Unchanged","KLD values shall be justified.","NOTE \t1\tJustification can be performed based on relevant historical practice, analytical or experimental means.\nNOTE \t2\tFor satellites, a typical value of 1,2 is used in the following cases:\n·\tComposite structures discontinuities;\n·\tSandwich structures discontinuities (face wrinkling, intracell buckling, honeycomb s\nhear);\n·\tJoints and inserts.\nNOTE \t3\tThe use of a local design factor does not preclude appropriate engineering analysis (e.g. KLD does not cover the stress concentration factors) and assessment of all uncertainties.\n"]
["ECSS-E-ST-32-11C","ECSS - Current v1.0","4.1.2a","Requirement","ECSS-E-ST-32-11_0250001",1,"Created","Prior to the execution of the test, the frequencies of interest and the mode shapes of interest shall be identified.\n    NOTE 1 The “frequencies of interest” and the “mode shapes of interest” are those identified as being relevant for achieving the modal survey test objectives.\n    NOTE 2 Instead of specific frequencies of interest, a frequency range of interest can be identified.\n    NOTE 3 In cases where the test article mathematical model is employed for accurate response predictions, the frequency range of interest is usually defined as being the frequency range in which major dynamic excitations from the launch vehicle are expected."]
["ECSS-E-ST-32-11C","ECSS - Current v1.0","4.2.1a","Requirement","ECSS-E-ST-32-11_0250013",1,"Created","The test article shall be representative with respect to the test objectives described in the test specification \n    NOTE 1 For example, a test objective can be the verification of the flight hardware.\n    NOTE 2 For the test specification, see “Test specification” DRD in ECSS-E-ST-10-03."]
["ECSS-E-ST-32-11C","ECSS - Current v1.0","5.2.1a","Requirement","ECSS-E-ST-32-11_0250036",1,"Created","The test planning shall be broken down into \n    1. pre-test activities, in conformance with 5.2.2, \n    2. test activities, in conformance with 5.2.3, and \n    3. post-test activities, in conformance with 5.2.4.\n        NOTE Figure 5-1 shows the test planning activities.            "]
["ECSS-E-ST-32-11C","ECSS - Current v1.0","5.3.2.2a","Requirement","ECSS-E-ST-32-11_0250043",1,"Created","The suspension system shall be defined such that it is flexible compared to the rigidity of the test article."]
["ECSS-E-ST-32-11C","ECSS - Current v1.0","5.3.4c","Recommendation","ECSS-E-ST-32-11_0250133",1,"Created","The mass loading effect of the test equipment, including the co-vibrating exciter coil, should have no significant influence on the test measurements."]
["ECSS-E-ST-32-11C","ECSS - Current v1.0","5.4.2f","Requirement","ECSS-E-ST-32-11_0250073",1,"Created","The maximum acceleration overload specified in 5.4.2e shall be defined prior to starting the tests."]
["ECSS-E-ST-32-11C","ECSS - Current v1.0","5.7.1.3a","Recommendation","ECSS-E-ST-32-11_0250134",1,"Created","A definition of the MIF applied should be given with the test results to indicate whether a mass weighting is used for the MIF."]
["ECSS-E-ST-32-11C","ECSS - Current v1.0","5.8.2.2b","Requirement","ECSS-E-ST-32-11_0250108",1,"Created","Conformance shall be demonstrated by comparing the dynamic behaviour of the reduced mathematical model with the dynamic analysis results obtained from the detailed FEM."]
["ECSS-E-ST-32-11C","ECSS - Current v1.0","6.3.3a","Requirement","ECSS-E-ST-32-11_0250118",1,"Created","The number of accelerometer locations (experimental DOFs) shall be chosen such that the modal characteristics of the test article (including natural frequencies, mode shapes, modal damping ratios, generalized and effective masses) in the frequency range of interest can be determined in conformance with the requirements listed in the test specification.\n    NOTE For the frequency range of interest, see 4.1.2. For the test specification, see “Test specification” DRD in ECSS-E-ST-10-03. "]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","4.2.1e","Requirement","ECSS-E-ST-32_0050005",1,"Created","Service-life evaluations shall determine: \n    1. the inspection and maintenance requirements,\n    2. the item replacement procedure (preventive maintenance), and\n    3. the inspection and repair procedures and intervals (corrective maintenance)."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","4.2.6b","Requirement","ECSS-E-ST-32_0050017",1,"Created","Load application sequence shall be defined.\n    NOTE For example to account for any non-linear effect depending on load application sequence."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","4.3.8b","Requirement","ECSS-E-ST-32_0050035",1,"Created","The resistance of the structure against manufacturing defects and the result of accidental damage (e.g. low energy impact) shall be taken into account in the design.\n    NOTE A structure is considered tolerant to damage if the amount of general degradation or the size and distribution of local defects expected during operation does not lead to structural degradation below specified performance."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","4.5.3a","Requirement","ECSS-E-ST-32_0050052",1,"Created","The mechanical design shall be performed in such a way that assembly, integration and repair and maintenance activities can be carried out with tools and test equipment agreed with the customer.\n    NOTE It is good practice to minimize the number of special tools and equipment to minimize cost."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","4.5.8b","Requirement","ECSS-E-ST-32_0050064",1,"Created","The scatter bands of the data shall be derived and design allowables defined in terms of fractions of their statistical distribution with A-basis or B-basis specified levels of reliability and confidence."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","4.5.13b","Requirement","ECSS-E-ST-32_0050080",1,"Created","In cases where the behaviour of a material in a specific environment is not known, ablation and pyrolysis tests of representative materials (composition and condition) shall be performed, either under the service conditions, or in more severe conditions (accelerated testing)."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","4.5.16d","Requirement","ECSS-E-ST-32_0050089",1,"Created","MOS shall be computed by accounting for interactions of different types of failures (e.g. failure of a bolt due to shear and tension)\n    NOTE The following “interaction equation” is normally used to compute l for interacting failure types: \n \nwhere a, b, g, and d are experimental exponents and Ri are the ratios between the i-th DLL x FOS and the allowable load (which causes the failure if the i-th load is applied alone)"]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","4.6.2.5b","Requirement","ECSS-E-ST-32_0050110",1,"Created","Coupled loads analyses are performed to verify the loads resulting from dynamic behaviour of structural assemblies as follows:\n    1. The mathematical models applied in coupled analyses shall represent the structural assemblies by characterization of the dynamic parameters, namely natural frequencies, mode shapes, associated generalized and effective masses, and damping.\n    2. The characterization of natural frequencies with small effective masses (e.g. multilayer insulation) need not be performed if it can be shown that these modes do not participate to the overall dynamic behaviour."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","4.6.2.11b","Requirement","ECSS-E-ST-32_0050124",1,"Created","Hygro-thermal analysis shall be performed to compute deformations due to occurring moisture release or absorbtion."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","4.6.3.2a","Requirement","ECSS-E-ST-32_0050139",1,"Created","The test objectives and success criteria shall be specified."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","4.6.3.8a","Requirement","ECSS-E-ST-32_0050155",1,"Created","Modal survey test shall be performed to verify the modal characteristics.\n    NOTE See ECSS-E-ST-32-11."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","4.6.3.12a","Requirement","ECSS-E-ST-32_0050161",1,"Created","The conformance to requirements on micro-vibrations and microgravity disturbances originating from the structure shall be verified by test."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","4.6.4c","Requirement","ECSS-E-ST-32_0050184",1,"Created","Except in the case specified in 4.6.4d, composite structure acceptance tests shall be performed at component level or on fully assembled structure."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","4.7.5.2b","Requirement","ECSS-E-ST-32_0050196",1,"Created","Major assembly operations shall be accompanied by inspection and tests. "]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","4.8.4.3a","Requirement","ECSS-E-ST-32_0050214",1,"Created","Corrective maintenance shall be performed on parts incurring damage and those undergoing higher than expected rates of deterioration. \n    NOTE Expected rates of deterioration are a result of the design."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","4.9.7c","Recommendation","ECSS-E-ST-32_0050762",1,"Created","When exchanging structural mathematical model data, for physical models, the same version of the software should be used."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","4.10g","Requirement","ECSS-E-ST-32_0050244",1,"Created","The supplier shall provide Fracture control items lists in conformance with Annex G."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","A.2.1<4.1>b","Requirement","ECSS-E-ST-32_0050259",1,"Created","A level of maturity shall be included for the components identified in a. above. "]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","A.2.1<4.6>a","Requirement","ECSS-E-ST-32_0050268",1,"Created","The CADMDD shall describe the reference coordinate system and its definition. "]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","A.2.1<6.1>a","Requirement","ECSS-E-ST-32_0050289",1,"Created","When design parts are represented by an idealized model and their mass represented with the physical value, the assumed density shall be reported in the CADMDD. "]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","B.2.1<1>a","Requirement","ECSS-E-ST-32_0050303",1,"Created","The DL document shall contain a description of the purpose, objective, applicability, content and the reason prompting its preparation"]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","B.2.1<6.1>a","Requirement","ECSS-E-ST-32_0050319",1,"Created","The DL document shall report the design limit loads (DLL) deriving from the limit load cases (see <5.2>), after possible multiplication by dedicated design (or project) factors, if specified by the customer. "]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","C.2.1<4.3>b","Requirement","ECSS-E-ST-32_0050334",1,"Created","If no changes have been made w.r.t. previous DSA report issues, it shall be explicitly stated."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","C.2.1<4.4>d","Requirement","ECSS-E-ST-32_0050340",1,"Created","List and description of each stability figure described in the DSA report (e.g. elements of the structure which are considered, type of performances which are reported such as relative positioning of two points, contributors which are taken into account such as micro sliding of junctions, thermo-elastic deformation, and moisture induced deformation)."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","C.2.1<8>a","Recommendation","ECSS-E-ST-32_0050768",1,"Created","The DSA should contain limitations of the performed work."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","E.2.1<5>a","Requirement","ECSS-E-ST-32_0050371",1,"Created","The FCA shall state and describe all the cyclic and sustained load events encountered during the life of the item."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","E.2.1<6.3>a","Requirement","ECSS-E-ST-32_0050379",1,"Created","Fatigue and strength data for the actual material and geometry (i.e. alloy, production form, heat treatment and stress concentration factor) shall be reported."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","F.2.1<2>a","Requirement","ECSS-E-ST-32_0050394",1,"Created","The FCP shall list the applicable and reference documents in support to the generation of the document."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","G.2.1<1>a","Requirement","ECSS-E-ST-32_0050412",1,"Created","The PFCIL, FCIL and FLLIL shall contain a description of the purpose, objective, applicability, content and the reason prompting its preparation"]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","H.2.1<2>a","Requirement","ECSS-E-ST-32_0050424",1,"Created","The MMPA shall list the applicable and reference documents in support to the generation of the document."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","I.2.1<4.1>a","Requirement","ECSS-E-ST-32_0050443",1,"Created","The MMDD shall indicate the consistent unit system of measures used."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","I.2.1<6.4>a","Requirement","ECSS-E-ST-32_0050454",1,"Created","The MMDD shall indicate the analysis code, (e.g. NASTRAN, SAMCEF, ABAQUS.), which the model is designed for. "]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","I.2.1<8.2>b","Requirement","ECSS-E-ST-32_0050478",1,"Created","The position of the masses shall be indicated also by plotting the model and labelling the masses."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","I.2.1<8.3>d","Requirement","ECSS-E-ST-32_0050483",1,"Created","If distributed non structural masses are not included in the model, this shall be explicitly declared."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","I.2.1<13.5>a","Requirement","ECSS-E-ST-32_0050499",1,"Created","The MMDD shall report the results of dedicated checks performed to assess adequacy to perform thermal stress analysis. "]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","J.2.1<4.5>a","Requirement","ECSS-E-ST-32_0050515",1,"Created","Load cases shall be listed and described with reference to relevant applicable documents."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","J.2.1<8>a","Requirement","ECSS-E-ST-32_0050529",1,"Created","The MDRA shall describe the main outcome of the analysis performed, reporting all key conclusions. "]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","K.2.1<7.1>a","Requirement","ECSS-E-ST-32_0050550",1,"Created","The SSA shall include a general presentation of analysis methods and tools, including annexes to document the specific methods applied in the analysis of any structural item."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","K.2.1<7.5>a","Requirement","ECSS-E-ST-32_0050558",1,"Created","Formulae used to compute the margins of safety shall be documented in this subclause."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","K.2.1<9.4>a","Requirement","ECSS-E-ST-32_0050574",1,"Created","The SSA shall define the format to transfer stress data to fracture and fracture mechanics. "]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","K.2.1<10.3>g","Requirement","ECSS-E-ST-32_0050587",1,"Created","A summary of all part numbers and their critical loads which are being covered by similarity shall be included."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","L.2.1<4.2>a","Requirement","ECSS-E-ST-32_0050604",1,"Created","The SAB shall describe all the modifications brought to the structure w.r.t. the referenced previous SAB document issues. "]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","M.2.1<3>a","Requirement","ECSS-E-ST-32_0050622",1,"Created","The SB shall include the terms and definitions, abbreviated terms, and symbols used."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","M.2.1<5.1>f","Requirement","ECSS-E-ST-32_0050633",1,"Created","Each structure item shall be identified in the report by a structure part or component identifier, previously described, and covered independently."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","N.2.1<4.2>b","Requirement","ECSS-E-ST-32_0050649",1,"Created","If no mass change arose w.r.t. previous SMS issues, it shall be explicitly stated."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","N.2.1<7>b","Requirement","ECSS-E-ST-32_0050659",1,"Created","The SMS shall include limitations of the performed work."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","O.2.1<7>b","Requirement","ECSS-E-ST-32_0050678",1,"Created","The TAC shall report the objectives of the test predictions."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","P.2.1<4.2>b","Requirement","ECSS-E-ST-32_0050694",1,"Created","The units for mass, force, length, time, temperature and angles shall be explicitly reported."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","P.2.1<6.6>a","Requirement","ECSS-E-ST-32_0050708",1,"Created","The TE shall describe any test fixtures, instruments, loading devices, and special equipment."]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","P.2.1<8>a","Requirement","ECSS-E-ST-32_0050724",1,"Created","The TE shall include any other information that can help planning a similar test. "]
["ECSS-E-ST-32C Rev. 1","ECSS - Current v1.0","Q.2.1<4.2>a","Requirement","ECSS-E-ST-32_0050731",1,"Created","The TP shall indicate the consistent unit system of measures used."]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.2.4.1.1a","Requirement","ECSS-E-ST-33-01_0820003",1,"Unchanged","The identification of delivered pieces of hardware, parts, components, sub­assemblies and assemblies shall carry at least the equipment title.","NOTE \t1\tFor the identification of pieces of hardware, parts, components, sub­assemblies, and assemblies of the mechanism, see clause 5.3.1.5 of ECSS-M-ST-40.\nNOTE \t2\tThe identification can be removable.\nNOTE \t3\tThe identification number and the equipment title can be defined by the contracting authority.\n"]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.2.5.1d","Requirement","ECSS-E-ST-33-01_0820016",1,"Unchanged","For structural reliability aspects ECSS-E-ST-32 shall apply."]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.5.2.1a","Requirement","ECSS-E-ST-33-01_0820033",1,"Unchanged","Materials shall be selected in conformance with ECSS-Q-ST-70 clause 5, or be verified that they conform to requirements, approved by the customer.","NOTE \t1\tFor general requirements on materials used for space mechanisms, see ECSS-E-ST-32-08. The material requirements in 4.5.2.2 to 4.5.2.7 are specific to mechanisms.\nNOTE \t2\tFor selection of materials, see ECSS-Q-ST-70-71.\nNOTE \t3\tFor additional requirements relating to tribology, see clause 4.7.3.\n"]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.5.2.4a","Requirement","ECSS-E-ST-33-01_0820037",1,"Unchanged","Materials shall be selected as specified in ECSS-Q-ST-70-36."]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.7.3.1f","Recommendation","ECSS-E-ST-33-01_0820457",1,"Unchanged","Metal to metal tribological contacts should be composed of dissimilar materials, in conformance with 4.5.2.3."]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.7.3.3.3c","Requirement","ECSS-E-ST-33-01_0820078",1,"Unchanged","The integrity of the anti­creep barrier shall be verifiable by indicators.","NOTE \tFor example, UV­detectable.\n"]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.7.3.4.2i","Requirement","ECSS-E-ST-33-01_0820088",1,"Unchanged","If bearing preload can be affected by the running­in process, the preload shall be confirmed after running­in. "]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.7.5.2.5b","Requirement","ECSS-E-ST-33-01_0820107",1,"Unchanged","Mechanisms shall be designed with a positive margin of safety against yielding and against ultimate under all environmental and operational load conditions."]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.7.5.2.6f","Requirement","ECSS-E-ST-33-01_0820398",1,"Unchanged","In the mechanism requirement specification the Design Limit Loads (DLL) shall be specified.","NOTE \t 1\tIt is good practice to clarify with the customer that the Project factor (KP) and the Model factor (KM) are already included, to avoid duplication of factors.\nNOTE \t2\tDLL are intended to be environmental loads.\n"]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.7.5.3.3a","Requirement","ECSS-E-ST-33-01_0820403",1,"Unchanged","For safety critical mechanisms in crewed space missions, the holding torque or force shall be sized to provide 2 times the torques or forces applied by operational or environmental design limit loads under worst case conditions and throughout the operational lifetime.","NOTE \tThe holding function prevents motion and inadvertent operation of a mechanism by providing torque or force using powered or unpowered means.\n"]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.7.5.4.3g","Requirement","ECSS-E-ST-33-01_0820143",1,"Unchanged","Latches shall be resettable for ground testing."]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.7.5.4.4e","Requirement","ECSS-E-ST-33-01_0820150",1,"Unchanged","The end stop sizing shall take into account the worst-case loads, including the shock loads."]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.7.5.4.5e","Requirement","ECSS-E-ST-33-01_0820158",1,"Unchanged","Except for gears and ball or journal bearings, sliding at the separable contact surfaces before separation shall be prevented, in order to avoid potential contact surface property changes. "]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.7.5.4.12b","Requirement","ECSS-E-ST-33-01_0820177",1,"Unchanged","Where no actuator redundancy is provided, redundancy shall be provided by duplicating up to and including the level of the initiators, heating element or equivalent for non­pyrotechnic devices, and its power supply."]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.7.7.1.1a","Requirement","ECSS-E-ST-33-01_0820184",1,"Unchanged","Mechanisms shall be designed to meet all the requirements regarding electrical interfaces and performances."]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.7.7.4a","Requirement","ECSS-E-ST-33-01_0820197",1,"Unchanged","Each mechanism shall be electrically bonded to the spacecraft structure or its carrying equipment. "]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.7.7.7d","Requirement","ECSS-E-ST-33-01_0820212",1,"Unchanged","The relative position of cables within the harness shall not change during motion.","NOTE \tThe four previous requirements are introduced in order to achieve reproducible resistive torques or forces of moving cable harness.\n"]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.7.8.5h","Recommendation","ECSS-E-ST-33-01_0820470",1,"Unchanged","The ratio between the derivative time constant and the time constant limiting the high frequency gain should not exceed 20."]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.8.2.6.3c","Requirement","ECSS-E-ST-33-01_0820247",1,"Unchanged","An integrity check of the results of the analysis shall be performed. ","NOTE \tFor example, energy or momentum balance. \n"]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.8.2.11b","Requirement","ECSS-E-ST-33-01_0820257",1,"Unchanged","Dimensioning and sizing methods shall be agreed by the customer."]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.8.3.1g","Requirement","ECSS-E-ST-33-01_0820282",1,"Unchanged","The mechanism shall be subjected to a structural verification.","NOTE \tFor structural requirements, see ECSS-E-ST-32.\n"]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.8.3.2.2b","Permission","ECSS-E-ST-33-01_0820473",1,"Unchanged","Verification test specified in requirement 4.8.3.2.2a need not be performed if the customer agrees that the test available data from previous space application can be used instead."]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.8.3.3.8a","Requirement","ECSS-E-ST-33-01_0820301",2,"Unchanged","The EMC performance of mechanisms shall be verified by testing when:\n1.\tEMC sensitive components are used on the mechanism, or \n2.\tspacecraft specific EMC requirements are applicable to the mechanism.","NOTE \tEMC comprises susceptibility and emissivity.\n"]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.8.3.3.14b","Requirement","ECSS-E-ST-33-01_0820317",1,"Unchanged","For the test verification, the number of expected cycles shall be multiplied by the factors in Table 4-4."]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","4.8.3.4.3a","Requirement","ECSS-E-ST-33-01_0820329",2,"Unchanged","Electrical wires shall be tested to verify their insulation from the structure and from each other by not less than 100 MW with a DC voltage of 500 V applied until a steady state resistance value is measured with a minimum duration of 1s."]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","A.2.1<4>a","Requirement","ECSS-E-ST-33-01_0820347",1,"Unchanged","The SMS shall include the specific climatic protection and environmental requirements."]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","A.2.1<6>d","Requirement","ECSS-E-ST-33-01_0820354",1,"Unchanged","The SMS shall include the qualification temperature range under all ground, test, launch and in­orbit conditions.","NOTE \tThis is used for the mechanism thermal design and sizing (see 4.7.4.2a).\n"]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","B.2.1<6>a","Requirement","ECSS-E-ST-33-01_0820370",1,"Unchanged","The MDD shall provide informative data with regard to performance, mass and power budgets.","NOTE \tThis is provided for information only. The contractual values are provided in the verification files.\n"]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","D.2.1<4>a","Requirement","ECSS-E-ST-33-01_0820384",1,"Unchanged","The user manual shall define the information to be recorded after delivery.","NOTE \tFor example: Number of limited operations.\n"]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","F.2.1<3>a","Requirement","ECSS-E-ST-33-01_0820430",1,"Unchanged","The MSVP shall describe the mechanism detailed design, including the following: \n1.\tproduct tree down to sub assembly break down;\n2.\tphysical design of the mechanism in all configurations;\n3.\thow each function is achieved;\n4.\tprotection and redundancy implementation;\n5.\tgeneral assembly drawings with cross sections or equivalent;\n6.\tinterface descriptions, comprising mechanical, thermal and electrical;\n7.\tstatic and dynamic envelopes."]
["ECSS-E-ST-33-01C Rev.2","ECSS - Current v1.0","G.2.1<5>c","Requirement","ECSS-E-ST-33-01_0820450",1,"Unchanged","The MSVR shall cross-reference any separate test analyses."]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.2.2b","Requirement","ECSS-E-ST-33-11_0280010",2,"Normative Change","The reliability demonstration shall be: .\n1.\tused to justify design margins including the influence of ageing, temperature and explosive batch,\n2.\tjustified according to clause 6.4.2 of ECSS-Q-ST-30 or dedicated system specification, and\n3.\tstated in a reliability prediction document as per Annex E of ECSS-Q-ST-30.","NOTE\tDedicated system specifications are, for example, GDIR and SG.\n"]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.2.5.2d","Requirement","ECSS-E-ST-33-11_0280026",2,"Normative Change","Deformation of any component shall not:\n1.\treduce its specified performance,\n2.\taffect any part of the subsystem,\n3.\tcause leakage more than the specified limit,\n4.\tcause debris more than the specified limit."]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.3b","Requirement","ECSS-E-ST-33-11_0280037",1,"Informative Change","The environmental conditions, life cycle and the functions being activated shall be specified.","NOTE\tE.g. ground storage, transport, launcher ignition, staging and safety functions, spacecraft separation, motor ignition, solar array, antenna, boom or cover release, propulsion subsystem branch opening or closing, de-orbiting.\n"]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.5.2.1c","Requirement","ECSS-E-ST-33-11_0280055",2,"Normative Change","If the explosive subsystem contains two or more barriers then at least two of these barriers shall:\n1.\tbe independent, \n2.\tnot be subject to common cause failure, \n3.\teach provide disconnection of the firing circuit.","NOTE\tThe electrical architecture is designed with the following barriers:\n·\tArming switch,\n·\tPulse generator,\n·\tSelection switch, with monitoring of the status,\n·\tfor spacecraft, in addition satellite separation and Safe and Arm connector.\n"]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.5.2.5a","Requirement","ECSS-E-ST-33-11_0280072",1,"Unchanged","The fire function shall be the last action in the sequence."]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.7.2d","Requirement","ECSS-E-ST-33-11_0280085",1,"Unchanged","Each interface shall sustain without degradation in both coupled and separated states\n1.\tthe assembly and dismantling duty-cycle, and\n2.\tthe operational and environmental conditions of the application."]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.8.2.1b","Requirement","ECSS-E-ST-33-11_0280100",2,"Normative Change","The explosive subsystem shall provide power pulses to initiators at the times required by the application. "]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.8.2.3a","Requirement","ECSS-E-ST-33-11_0280108",1,"Unchanged","The power supply shall ensure that the power subsystem is not overloaded before, during or after the actuation of any explosive device even in case of a single-point failure together with a short circuit (both pin-to-pin and pin-to-ground)."]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.8.2.9a","Requirement","ECSS-E-ST-33-11_0280128",2,"Normative Change","The explosive subsystem shall neither function nor degrade as a result of the voltage difference between the firing circuits and the shielding or the ground within specified limits."]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.8.3.1e","Requirement","ECSS-E-ST-33-11_0280141",2,"Normative Change","Explosive devices shall not decompose when exposed to thermal environments that are 30 °C above the maximum predicted temperature and 10 °C below the minimum predicted temperature during worst case service life.","NOTE\tThis is to ensure no self-ignition under cook-off test.\n"]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.9c","Requirement","ECSS-E-ST-33-11_0280156",1,"Unchanged","Any sealing system used to prevent degradation shall be demonstrated to be effective."]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.10.1g","Requirement","ECSS-E-ST-33-11_0280171",1,"Unchanged","Prime and redundant circuits for the same function shall not pass through the same connector."]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.10.5a","Requirement","ECSS-E-ST-33-11_0280185",1,"Unchanged","All requirements for safe and arm devices of Clause 4.10.11 shall apply."]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.10.8c","Requirement","ECSS-E-ST-33-11_0280200",1,"Informative Change","The safe plug shall be\n1.\tcompatible with the safe and arm connector receptacle,\n2.\tsuitable for use with flight hardware,\n3.\tsuitable for the number of connection cycles necessary to cover integration, test and use,\n4.\tscoop proof,\n5.\tlockable,\n6.\tvisibly identified,\n7.\tcarrying a “Remove before Flight” banner.","NOTE\tExamples of lockable safe plugs are sub-D connector, bayonet or triple-start thread types.\n"]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.10.11.2a","Requirement","ECSS-E-ST-33-11_0280211",2,"Normative Change","The electrically actuated safe and arm devices shall be designed to withstand repeated cycling from Arm to Safe for at least five times the expected number of cycles, without any malfunction, failure, or degradation in performance;"]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.11.1.2a","Requirement","ECSS-E-ST-33-11_0280231",2,"Normative Change","Identification marking shall be in conformance with ECSS-M-ST-40, clause 5.3.1.5."]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.11.2.2c","Requirement","ECSS-E-ST-33-11_0280243",1,"Unchanged","After exposure to the no-fire current or no-fire power, the EED shall be capable to function in conformance with its requirements."]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.11.3.2d","Requirement","ECSS-E-ST-33-11_0280259",2,"Normative Change","The connection shall be able to undergo specified thermal and mechanical environments without degradation."]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.11.7b","Requirement","ECSS-E-ST-33-11_0280272",2,"Normative Change","Under the conditions in column E of Table 4-13, the property in column A in the units in column B shall be between the values in column C (maximum) and column D (minimum)."]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.11.9b","Requirement","ECSS-E-ST-33-11_0280276",2,"Normative Change","Under the conditions in column E of Table 4-15, the properties in column A, expressed in the units specified in column B, shall be between the values in column C (maximum) and column D (minimum)."]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.12.2e","Requirement","ECSS-E-ST-33-11_0280291",1,"Unchanged","Under the conditions in column E of Table 4-18, the properties in column A, expressed in the units specified in column B, shall be between the values in column C (maximum) and column D (minimum)."]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.13.3b","Requirement","ECSS-E-ST-33-11_0280315",1,"Unchanged","The status of explosive safety barriers shall be monitored when the space vehicle induces a catastrophic risk.","NOTE\tThe space vehicle comprises e.g. the launcher, satellite, spacecraft.\n"]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.14.2a","Requirement","ECSS-E-ST-33-11_0280321",1,"Unchanged","Inspection shall be performed in conformance with ECSS-Q-ST-20."]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.14.3.6c","Requirement","ECSS-E-ST-33-11_0280336",1,"Unchanged","Firing tests shall not be performed until a successful rehearsal has been completed."]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.15.2a","Requirement","ECSS-E-ST-33-11_0280352",2,"Normative Change","Explosives devices shall be transported in conformance with the latest version of UNECE regulations ST/SG/AC.10/1. "]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.15.3e","Requirement","ECSS-E-ST-33-11_0280364",2,"Normative Change","Records of all environmental conditions in locations where explosive components or subsystems are stored or handled shall be maintained and be available for review.","NOTE\tE.g. environmental conditions such as thermal, humidity.\n"]
["ECSS-E-ST-33-11C Rev.1","ECSS - Current v1.0","4.17.1b","Requirement","ECSS-E-ST-33-11_0280385",2,"Normative Change","ECSS-Q-ST-10-04 shall be applied for all explosive devices identified as critical items."]
["ECSS-E-ST-34C","ECSS - Current v1.0","4.2.2.3b","Requirement","ECSS-E-ST-34_0830004",1,"Created","The storage and transport conditions for supplies shall be specified."]
["ECSS-E-ST-34C","ECSS - Current v1.0","4.4.2.2.3a","Requirement","ECSS-E-ST-34_0830019",1,"Created","Means for adjusting pressure at the selected value (up or down) inside the specified range applicable for each type of pressurized volume shall be provided."]
["ECSS-E-ST-34C","ECSS - Current v1.0","4.4.2.3.2b","Requirement","ECSS-E-ST-34_0830032",1,"Created","The accuracy for the stabilized dry bulb temperature in the habitable volume shall be specified."]
["ECSS-E-ST-34C","ECSS - Current v1.0","4.4.2.5.3a","Requirement","ECSS-E-ST-34_0830049",1,"Created","The range and accuracy for the monitoring of the atmosphere carbon dioxide partial pressure shall be specified."]
["ECSS-E-ST-34C","ECSS - Current v1.0","4.4.2.11a","Recommendation","ECSS-E-ST-34_0830230",1,"Created","Non-ionizing radiation limits should be specified."]
["ECSS-E-ST-34C","ECSS - Current v1.0","4.4.3.3.4a","Requirement","ECSS-E-ST-34_0830078",1,"Created","Means of restoration of a habitable environment shall be provided, at least to reach degraded conditions.\n    ","NOTE This includes removal of combustion products from the atmosphere."]
["ECSS-E-ST-34C","ECSS - Current v1.0","4.4.4.2.3a","Requirement","ECSS-E-ST-34_0830102",1,"Created","Oxygen usage and contingency needs, including the accessible volume’s atmosphere restoration, shall be specified."]
["ECSS-E-ST-34C","ECSS - Current v1.0","4.4.4.3.2b","Requirement","ECSS-E-ST-34_0830108",1,"Created","Storage breathing gases capacity shall be specified."]
["ECSS-E-ST-34C","ECSS - Current v1.0","4.4.4.4.7a","Requirement","ECSS-E-ST-34_0830124",1,"Created","Resupplied water shall be accepted in conformance with the interface specifications. \n    ","NOTE Resupply can include water obtained from in situ resources."]
["ECSS-E-ST-34C","ECSS - Current v1.0","4.4.4.5.5.2","Requirement","ECSS-E-ST-34_0830225",1,"Created","Means for food processing, serving as well as utensil and restraints and mobility aids, shall be provided."]
["ECSS-E-ST-34C","ECSS - Current v1.0","4.4.5.2.2a","Requirement","ECSS-E-ST-34_0830142",1,"Created","Storage of waste water shall be provided taking into account the capacity to meet peak recovery rate and storage contingency needs.\n    ","NOTE Storage contingencies include temporary loss of downstream processing capability."]
["ECSS-E-ST-34C","ECSS - Current v1.0","4.4.6.1.3a","Requirement","ECSS-E-ST-34_0830163",1,"Created","Decompression of the airlock from the habitable volume pressure to the external pressure shall be supported at a specified rate. "]
["ECSS-E-ST-34C","ECSS - Current v1.0","4.4.6.1.10a","Requirement","ECSS-E-ST-34_0830172",1,"Created","Safe haven operations shall be supported."]
["ECSS-E-ST-34C","ECSS - Current v1.0","4.6.3.2a","Requirement","ECSS-E-ST-34_0830187",1,"Created","The ECLSS shall conform to the specified data handling and software."]
["ECSS-E-ST-34C","ECSS - Current v1.0","4.6.3.8a","Requirement","ECSS-E-ST-34_0830200",1,"Created","The dedicated human time allocation for operation and maintenance on ground and on board shall: \n    1. be specified (in man-year per mission), and\n    2. not exceed the value specified in conformance with 1. above.\n        ","NOTE To prevent too frequent human interventions on board and actions from the personnel on the ground in order to replace consumable or dispose waste, maintainability issues are given a particular importance in ECLS design."]
["ECSS-E-ST-34C","ECSS - Current v1.0","4.9.1b","Requirement","ECSS-E-ST-34_0830217",1,"Created","Since the ECLSS can consist of several functional sub-units, for each sub-unit integration procedures and interfaces shall be defined during project Phase B.\n    ","NOTE Examples of the hardware to be delivered include\n        · ECLSS hardware for different models (e.g. EM, QM and FM),\n        · hardware for sample test,\n        · spare, tools and repair hardware, and \n        · integration and support hardware."]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","4.5.1.2a","Requirement","ECSS-E-ST-35-01_0840017",1,"Created","For replacement of parts during development, testing and mission life pre-launch activities ECSS-E-ST-35, requirements 4.5.1c, d and e. shall be applied."]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","4.5.2.2a","Requirement","ECSS-E-ST-35-01_0840029",1,"Created","The selection shall be based on trade-off analyses of:\n    1. The propulsion system.\n        NOTE For example: monopropellant, bipropellant, or cold gas.\n    2. The operating mode.\n        NOTE For example: pressure regulated and blow-down."]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","4.5.5.1b","Requirement","ECSS-E-ST-35-01_0840044",1,"Created","The potential hazard of contamination and the expected level of contamination due to thruster exhaust shall be included in the plume analysis.\n    NOTE See clause 4.3.5c."]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","4.5.7e","Requirement","ECSS-E-ST-35-01_0840054",1,"Created","The propulsion system requirements shall specify operation under conditions different from operational conditions, such as ground tests. "]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","4.5.13b","Requirement","ECSS-E-ST-35-01_0840074",1,"Created","Flow calibration can be done at propulsion system or thruster level. "]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","4.5.15d","Requirement","ECSS-E-ST-35-01_0840089",1,"Created","The stiffness of the engine mounting, including feed lines and piping, and the actuator mounting on the engine shall meet the minimum values."]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","4.5.19.3b","Requirement","ECSS-E-ST-35-01_0840104",1,"Created","In case the GSE is used in the vicinity of inflammable or explosive materials, it shall be explosion proof."]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","4.6.2.3.1a","Requirement","ECSS-E-ST-35-01_0840120",1,"Created","The transient analyses of clause 4.6.2.3 shall be reported in conformance with the Propulsion transient analysis report DRD in ECSS-E-ST-35."]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","4.6.3.2a","Requirement","ECSS-E-ST-35-01_0840134",1,"Created","Proof pressure tests shall be performed on all pressure vessels and pressurized components.\n    NOTE For minimum factors of safety, see ECSS-E-ST-32-02. "]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","4.6.3.6a","Requirement","ECSS-E-ST-35-01_0840149",1,"Created","In case the compatibility between propellants and materials in possible contact with each other, and between dissimilar materials in contact with each other, is not known, the conformance to the compatibility requirements shall be established over time.\n    NOTE Accelerated tests can be used."]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","4.6.3.8b","Requirement","ECSS-E-ST-35-01_0840157",1,"Created","The test results, in combination with analysis, shall demonstrate the adequacy of the design with the specified margin under all mission conditions."]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","4.8.1e","Requirement","ECSS-E-ST-35-01_0840179",1,"Created","At the end of any operation, the propulsion system shall be configured by isolating, draining or venting the system, to minimize risks.\n    NOTE Minimize the risks of, e.g. explosion, toxicity and corrosion."]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","5.2.2a","Requirement","ECSS-E-ST-35-01_0840192",1,"Created","The propulsion system shall provide the total impulse required to fulfil the mission objectives."]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","5.3.3a","Requirement","ECSS-E-ST-35-01_0840209",1,"Created","The plume effects analysis on the spacecraft shall be performed and reported in conformance with clause 4.3.5 and 4.6.2.2.6."]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","5.5.1.4b","Requirement","ECSS-E-ST-35-01_0840224",1,"Created","The consequences in terms of operational restrictions shall be identified."]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","5.5.1.9a","Requirement","ECSS-E-ST-35-01_0840229",1,"Created","The system shall meet the requirements on the number of cycles and cycle life for the whole mission at component, propulsion and spacecraft system level, for both on ground and in-service operation."]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","5.5.2.3.1b","Requirement","ECSS-E-ST-35-01_0840239",1,"Created","The propellant shall be defined and specified including; \n    1. Chemical composition\n    2. Purity\n    3. Cleanliness."]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","5.5.8.4a","Requirement","ECSS-E-ST-35-01_0840264",1,"Created","The use of oxygen absorbers shall be assessed."]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","5.5.10b","Requirement","ECSS-E-ST-35-01_0840269",1,"Created","For propellant tanks design of EP systems using gaseous propellants, clause 4.5.10 shall be applied.\n    NOTE Example of gaseous propellant: xenon."]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","5.5.12.8a","Requirement","ECSS-E-ST-35-01_0840284",1,"Created","The heat fluxes at the interface between the thruster and supporting structure shall be specified."]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","5.5.15.2b","Requirement","ECSS-E-ST-35-01_0840301",1,"Created","The design of the following shall conform to ECSS-E-ST-20 and ECSS-E-ST-20-07.\n    1. Interference\n    2. susceptibility\n    3. grounding\n    4. Shielding\n    5. Isolation."]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","5.5.18.3b","Requirement","ECSS-E-ST-35-01_0840314",1,"Created","The procedures to operate and the design of the equipment shall prevent the inadvertent activation of the spacecraft components."]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","5.6.3.5b","Requirement","ECSS-E-ST-35-01_0840336",1,"Created","Life tests shall be conducted according to the mission duty cycles, with a reduction of the off-cycle duration in agreement with a good representation of the thermal transients."]
["ECSS-E-ST-35-01C","ECSS - Current v1.0","5.6.3.7b","Requirement","ECSS-E-ST-35-01_0840343",1,"Created","Conformity to the requirements of the components or subsystems, specified in 5.6.3.7a, shall be demonstrated."]
["ECSS-E-ST-35-02C","ECSS - Current v1.0","4.3.1a","Requirement","ECSS-E-ST-35-02_1100010",1,"Created","Pressure or thrust oscillation levels vs frequency range shall be specified at system and subsystem level."]
["ECSS-E-ST-35-02C","ECSS - Current v1.0","4.3.7a","Requirement","ECSS-E-ST-35-02_1100024",1,"Created","For safety aspects, ECSS-Q-ST-40 shall apply."]
["ECSS-E-ST-35-02C","ECSS - Current v1.0","4.5.2.2a","Requirement","ECSS-E-ST-35-02_1100040",1,"Created","The MEOP shall be calculated as specified in ECSS-E-ST-32 clause 4.2.7 ‘Limit loads’.\n    ","NOTE 1 The MDP is calculated as defined in ECSS-E-ST-32 clause 3.2.27 ‘MDP’.\nNOTE 2 If model uncertainties are included in the MEOP determination, Km is 1 for the calculation of MDP."]
["ECSS-E-ST-35-02C","ECSS - Current v1.0","4.5.4c","Requirement","ECSS-E-ST-35-02_1100058",1,"Created","The operating time of the igniter shall exceed the ignition time tign."]
["ECSS-E-ST-35-02C","ECSS - Current v1.0","4.5.5.3.1a","Requirement","ECSS-E-ST-35-02_1100068",1,"Created","For the ballistic dimensioning of the propellant grain, the pressure and mass flow rate histories shall be determined, in conformance with the system and subsystem requirements, according to the throat design (i.e. dimensions and erosion)."]
["ECSS-E-ST-35-02C","ECSS - Current v1.0","4.5.5.4.3a","Requirement","ECSS-E-ST-35-02_1100078",1,"Created","Nozzle housing stiffness and strength shall conform to the system and subsystem requirements."]
["ECSS-E-ST-35-02C","ECSS - Current v1.0","4.9c","Requirement","ECSS-E-ST-35-02_1100097",1,"Created","For the structural components of a solid propulsion system or subsystem, ECSS-E-ST-32 clause 4.7 shall apply."]
["ECSS-E-ST-35-02C","ECSS - Current v1.0","4.11a","Requirement","ECSS-E-ST-35-02_1100109",1,"Created","For solid rocket motors, the documentation listed in Table 4-1 of ECSS-E-ST-35 shall be delivered with the exception of ‘Gauging analysis’ and ‘Sloshing analysis’.\n    ","NOTE 1 The Dynamic analysis report (Annex A) is called by requirements 4.3.1e and 4.3.4b\t\t\t\t\t\nNOTE 2 The Material safety data sheet (Annex B) document is called by requirement 4.3.7d"]
["ECSS-E-ST-35-02C","ECSS - Current v1.0","A.2.1<6.2>f","Requirement","ECSS-E-ST-35-02_1100126",1,"Created","The AR-DY shall include a justification and validation of the methodology, either in the AR-DY itself, or by referenced documents."]
["ECSS-E-ST-35-02C","ECSS - Current v1.0","B.2.1<2>e","Requirement","ECSS-E-ST-35-02_1100139",1,"Created","The AR-MSDS shall describe the packaging."]
["ECSS-E-ST-35-02C","ECSS - Current v1.0","B.2.1<16>a","Recommendation","ECSS-E-ST-35-02_1100169",1,"Created","The AR-MSDS should provide all other information relative to safety which the provider estimates necessary for the use of the propulsion system, from the delivery until the flight."]
["ECSS-E-ST-35-03C","ECSS - Current v1.0","7.2b","Requirement","ECSS-E-ST-35-03_1110008",1,"Created","The development logic shall be structured into phases with a goal assigned to each phase."]
["ECSS-E-ST-35-03C","ECSS - Current v1.0","7.2q","Requirement","ECSS-E-ST-35-03_1110023",1,"Created","At the end of the development, the testing of the integrated system in its final configuration, including the electrical system, shall include tests with representative interfaces.\n    ","NOTE For example, typical interfaces are control computer, electrical interface, flight instrumentation."]
["ECSS-E-ST-35-03C","ECSS - Current v1.0","9.3.4a","Requirement","ECSS-E-ST-35-03_1110037",1,"Created","For the selection of the engine, a trade-off analysis shall be performed using the following parameters:\n    1. global stage performance (e.g. Isp, mass budget);\n    2. development costs;\n    3. recurring cost;\n    4. industrial infra structure;\n    5. test infra structure;\n    6. reliability;\n    7. strength;\n    8. architecture and overall dimensions;\n    9. the technical readiness level of the technologies;\n    10. any additional parameters specified by the customer."]
["ECSS-E-ST-35-03C","ECSS - Current v1.0","9.4.3.3f","Requirement","ECSS-E-ST-35-03_1110053",1,"Created","Flushing, purging and venting in flight shall not create unwanted propulsive effects.\n    ","NOTE For example, non-propulsive venting."]
["ECSS-E-ST-35-03C","ECSS - Current v1.0","9.4.4.3c","Requirement","ECSS-E-ST-35-03_1110072",1,"Created","The tank design shall be such that the occurrence of a vortex is prevented.\n    ","NOTE This usually happens when the tank is nearly empty"]
["ECSS-E-ST-35-03C","ECSS - Current v1.0","9.4.5.1a","Requirement","ECSS-E-ST-35-03_1110083",1,"Created","The feed system shall ensure a homogeneous parallel flow at the engine inlet in the thermodynamic conditions defined in the engine technical specification."]
["ECSS-E-ST-35-03C","ECSS - Current v1.0","9.5.1e","Requirement","ECSS-E-ST-35-03_1110098",1,"Created","The engine system shall assign pollution objective for each subsystem (including distribution of size and numbers of incoming and exiting particles)."]
["ECSS-E-ST-35-03C","ECSS - Current v1.0","9.5.3.3.2c","Requirement","ECSS-E-ST-35-03_1110109",1,"Created","The operational envelope shall be designed with the following parameters:\n    1. The range of functional parameters of the liquid propulsion system during flight and testing.\n        NOTE In particular flow rate, mixture ratio, tank propellant pressure.\n    2. The range of interface parameters.\n        NOTE In particular acceleration effect, inlet pressure and inlet temperature variations, temperature environment.\n    3. Deviations in the trimming and throttling of the propulsion system.\n    4. Deviations in the various modelling processes.\n    5. Deviations in component performances.\n    6. Deviations in manufacturing.\n    7. Deviations in measurements."]
["ECSS-E-ST-35-03C","ECSS - Current v1.0","9.5.3.4.3g","Requirement","ECSS-E-ST-35-03_1110128",1,"Created","If a liquid propulsion system is expected to be activated after a ballistic flight, a propellant settling analysis shall be carried out."]
["ECSS-E-ST-35-03C","ECSS - Current v1.0","9.5.4.2b","Requirement","ECSS-E-ST-35-03_1110140",1,"Created","The chemical effects of the propellants and of the burned gases shall be analysed in the TCA design and justification."]
["ECSS-E-ST-35-03C","ECSS - Current v1.0","9.5.4.5m","Requirement","ECSS-E-ST-35-03_1110158",1,"Created","During engine start-up, flow rate shall not block in the cooling channels."]
["ECSS-E-ST-35-03C","ECSS - Current v1.0","9.5.4.8.1e","Requirement","ECSS-E-ST-35-03_1110175",1,"Created","The mixing of propellants inside the injector shall be prevented during the whole mission."]
["ECSS-E-ST-35-03C","ECSS - Current v1.0","9.5.4.8.2i","Requirement","ECSS-E-ST-35-03_1110188",1,"Created","The measurement to ensure that proper operation of the ignition system is obtained shall be defined."]
["ECSS-E-ST-35-03C","ECSS - Current v1.0","9.5.5.2c","Requirement","ECSS-E-ST-35-03_1110203",1,"Created","Combustion chamber requirements of clause 9.5.4.8.3 shall apply."]
["ECSS-E-ST-35-03C","ECSS - Current v1.0","9.5.6.2f","Requirement","ECSS-E-ST-35-03_1110212",1,"Created","For stable pump operation, the pump shall operate in the part of the performance curve with a negative slope in the (dimensionless flow coefficient, dimensionless pressure head coefficient)  axis."]
["ECSS-E-ST-35-03C","ECSS - Current v1.0","9.5.7.2a","Requirement","ECSS-E-ST-35-03_1110233",1,"Created","A stability analysis shall be made for the operating points of the extreme envelope of the liquid engine."]
["ECSS-E-ST-35-03C","ECSS - Current v1.0","9.5.7.3i","Requirement","ECSS-E-ST-35-03_1110247",1,"Created","If closed loop systems are used, the sensors shall be characterized and validated."]
["ECSS-E-ST-35-03C","ECSS - Current v1.0","9.5.9.3.2a","Requirement","ECSS-E-ST-35-03_1110262",1,"Created","The pressure regulator functional characteristics shall be established over the entire extreme envelope.\n    ","NOTE For example downstream pressure versus mass flow rate curve."]
["ECSS-E-ST-35-03C","ECSS - Current v1.0","9.6e","Requirement","ECSS-E-ST-35-03_1110278",1,"Created","Minimum material properties for yield strength, ultimate tensile strength and rupture elongation, defined as values with 99 % probability to be exceeded at 90 % confidence level, shall be used for strength justification i.e. departure from elastic behaviour (yielding), rupture, instability (plastic or elastic)."]
["ECSS-E-ST-35-03C","ECSS - Current v1.0","9.6k","Requirement","ECSS-E-ST-35-03_1110284",1,"Created","For cases identified in 9.6j ECSS-E-ST-32-01 shall apply."]
["ECSS-E-ST-35-03C","ECSS - Current v1.0","9.6t","Requirement","ECSS-E-ST-35-03_1110293",1,"Created","External loads shall be derived from launch vehicle and stage specification using analytical model of the engine and propulsive system."]
["ECSS-E-ST-35-03C","ECSS - Current v1.0","14.2c","Requirement","ECSS-E-ST-35-03_1110319",1,"Created","The number of launch aborts the propulsion system can undergo shall be specified."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","4.1a","Requirement","ECSS-E-ST-35-06_0200001",1,"Unchanged","This standard shall only apply to propulsion systems using Hydrazines, MON, Propane, Butane, Nitrogen, Helium, Xenon as propellants."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","4.2.2.1b","Requirement","ECSS-E-ST-35-06_0200017",1,"Unchanged","Tank internal structures shall allow for draining and cleaning.","NOTE Examples of such structures are diaphragms, bladders, baffles, and surface tension screens."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","4.2.2.5b","Requirement","ECSS-E-ST-35-06_0200035",1,"Unchanged","Cavities or dead end tubing shall allow for thermal and vacuum drying.\n    ","NOTE See Annex B."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","4.2.4d","Requirement","ECSS-E-ST-35-06_0200047",1,"Unchanged","The GSE shall provide sampling interfaces and sampling equipment to verify cleanliness."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","4.3.5a","Requirement","ECSS-E-ST-35-06_0200070",1,"Unchanged","Components with liquid retaining cavities or capillary structures used for gas applications shall be\n    1. flushed with liquids only at component level,\n    2. verified to be dry.","NOTE E.g. pressure regulators, non return and relief valves."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","4.3.5g","Requirement","ECSS-E-ST-35-06_0200076",1,"Unchanged","Procedures shall ensure that components that can be damaged or contaminated by reverse flow are not flushed or purged in opposite direction, neither during component operation, nor during subsystem or system operation."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","4.4.1a","Requirement","ECSS-E-ST-35-06_0200092",1,"Unchanged","The particulate cleanliness class required shall be defined and selected, meeting program and system requirements. "]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","4.4.3c","Requirement","ECSS-E-ST-35-06_0200107",1,"Unchanged","Dryness from other liquids (e.g. IPA, HFE) shall correspond to a vapour concentration in the purge gas \n    1. For chemical propulsion systems the effluent gas liquid vapour content to be less than 10 ml/l for individual components and systems,\n    2. For electrical propulsion systems using Xenon the effluent gas moisture content to be less than 10 ml/l for individual components and systems."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","4.5a","Requirement","ECSS-E-ST-35-06_0200121",1,"Unchanged","Cleanliness test methods shall be selected and justified."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","5.2.2b","Requirement","ECSS-E-ST-35-06_0200142",1,"Unchanged","Decontamination shall take place in an approved facility."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","5.3.1a","Requirement","ECSS-E-ST-35-06_0200151",1,"Unchanged","All critical surfaces of system hardware shall be pre-cleaned to remove contaminants, e.g. dirt, grit, scale, corrosion, grease, oil and other foreign matter prior to any precision-cleaning process."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","5.3.3.1b","Requirement","ECSS-E-ST-35-06_0200163",1,"Unchanged","Alkaline cleaners and organic or water-based solvents shall be used for degreasing and removal of organic and inorganic contamination, e.g. scale and soluble metal oxides, see Annex D."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","5.5.1b","Requirement","ECSS-E-ST-35-06_0200181",1,"Unchanged","The hardware shall be dried by removing traces of cleaning liquids from the outside and from the inside."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","5.5.3.3b","Requirement","ECSS-E-ST-35-06_0200196",1,"Unchanged","Samples for qualification of the drying process shall be selected as follows:\n    1. Select a minimum of five cleaned, verified and dried items from each of the hardware configuration to be qualified,\n    2. Evaluate samples in accordance with 5.5.3.4."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","5.5.5.4a","Requirement","ECSS-E-ST-35-06_0200214",1,"Unchanged","Once the temperature monitor indicates that the hardware in the oven has reached the desired temperature, a vacuum shall be drawn on the parts and maintained for the period specified in 5.5.5.3b."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","6.1.1f","Requirement","ECSS-E-ST-35-06_0200226",1,"Unchanged","The UV light source shall have a wave length between 250 nm and 395 nm."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","6.2.2c","Requirement","ECSS-E-ST-35-06_0200235",1,"Unchanged","The test fluids shall be compatible with the fluid used in the system or components being tested."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","6.2.6.3b","Requirement","ECSS-E-ST-35-06_0200256",1,"Unchanged","All items rinsed with reagent water which cannot be visually inspected (100 %) shall be tested by the method of clause 6.4.2 or 6.4.3 for surface moisture. "]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","6.4.1a","Requirement","ECSS-E-ST-35-06_0200271",1,"Unchanged","The results of the dryness verification shall be reported in conformance with Annex C."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","7.1b","Requirement","ECSS-E-ST-35-06_0200285",1,"Unchanged","The packaging materials shall be clean room compatible and visibly clean."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","7.5.4b","Requirement","ECSS-E-ST-35-06_0200300",1,"Unchanged","The following rinsing procedure shall be used:\n    1. introduce the test liquid into the sealed bag through the previously cut opening;\n    2. close the bag by folding over the cut corner;\n    3. agitate the test liquid within the bag for a minimum of 15 s, wetting all surfaces;\n    4. pour the used test liquid into a precision-cleaned beaker, taking care to exclude airborne contamination;\n    5. analyse the test fluid for particulate population in conformance with Table 4-1 sub-class I."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","9a","Requirement","ECSS-E-ST-35-06_0200316",1,"Unchanged","The following documents specific to the cleaning of a propulsion system shall be delivered:\n    1. The Propulsion Cleanliness Requirements Analysis in conformance with Annex A.\n    2. The Propulsion Cleaning Techniques Selection in conformance with Annex B.\n    3. The Cleanliness Certificate in conformance with Annex C."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","11.1.2d","Requirement","ECSS-E-ST-35-06_0200330",1,"Unchanged","Small components, e.g. fittings, elastomers, and items small enough to fit inside an 1l beaker shall be: \n    1. combined into batches having a total surface area not exceeding 0,1 m2. \n    2. individually dipped and agitated in 100 ml of test liquid\n    3. combined into batches having a total surface area exceeding 0,1 m2,\n    4. individually dipped and agitated in 1 l of test liquid per m2 of surface area."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","A.2.1<2>a","Requirement","ECSS-E-ST-35-06_0200345",1,"Unchanged","The CRA shall list the applicable and reference documents in support to the generation of the document."]
["ECSS-E-ST-35-06C Rev.2","ECSS - Current v1.0","A.2.1<5>g","Requirement","ECSS-E-ST-35-06_0200357",1,"Unchanged","Specific issues (e.g. avoidance of metallic particles above 50 mm) and caution notes shall be presented."]
["ECSS-E-ST-35-10C","ECSS - Current v1.0","4.1.2a","Requirement","ECSS-E-ST-35-10_1050002",1,"Created","Compatibility testing shall take place under conditions reproducing the actual use of the items.\n    NOTE For example: The test items treatments, processes and handling, to be the same as those for the actual flight hardware items. "]
["ECSS-E-ST-35-10C","ECSS - Current v1.0","4.2.4b","Recommendation","ECSS-E-ST-35-10_1050185",1,"Created","Compatibility testing should take place following the logic of Figure 4-1\n    NOTE 1 This guarantees that they are performed with increasing complexity, generation of details, and for the specific applications.\n    NOTE 2 The requirements list needs to be tailored. It depends on the specific application which tests are going to be performed and which by-passed: e.g. if no hydrogen is involved, no hydrogen embrittlement tests are performed.\n    NOTE 3 An example of tailoring the requirements list is given in Annex C and Annex E"]
["ECSS-E-ST-35-10C","ECSS - Current v1.0","5.3.2a","Requirement","ECSS-E-ST-35-10_1050032",1,"Created","If material combinations are selected that appear in Table D-1 for the planned duration and conditions, the risks of using this combination shall be analysed."]
["ECSS-E-ST-35-10C","ECSS - Current v1.0","6.2.2.2d","Requirement","ECSS-E-ST-35-10_1050047",1,"Created","The test specimen and fluid shall be put into the container according to the compatibility test procedure specified in 6.2.2.2a."]
["ECSS-E-ST-35-10C","ECSS - Current v1.0","6.2.3.2a","Requirement","ECSS-E-ST-35-10_1050052",1,"Created","The material to be tested in clause 6.2.3.3 shall meet the requirements of clause 4.1.2."]
["ECSS-E-ST-35-10C","ECSS - Current v1.0","6.5.3c","Requirement","ECSS-E-ST-35-10_1050077",1,"Created","The tests shall be carried out under conditions that are representative of the propulsion system service environment."]
["ECSS-E-ST-35-10C","ECSS - Current v1.0","6.6.3a","Requirement","ECSS-E-ST-35-10_1050087",1,"Created","The change in volume and mass properties due to the absorption of liquids shall be determined according to either:\n    1. ASTM D 570-98 Clauses 5 through 8 or\n    2. ISO 1817 Clauses 3 through 6, 7.1 through 7.5, and 7.8 or\n    3. ISO 175 clauses 4 through 6.\n        NOTE ASTM D 570-98 specifically applies water as absorption liquid; the same procedure can be followed for other liquids of interest. "]
["ECSS-E-ST-35-10C","ECSS - Current v1.0","6.7.3.1b","Requirement","ECSS-E-ST-35-10_1050107",1,"Created","If in conformance with the analysis performed in 6.7.3.1a a ceramic material in the specific environment foreseen for the application, can change its compatibility characteristics, a specific application oriented test or set of tests shall be established (covering the load and conditions history), agreed with the customer and executed to establish the long term compatibility characteristics of the ceramic material and the fluid."]
["ECSS-E-ST-35-10C","ECSS - Current v1.0","6.8.3.3b","Requirement","ECSS-E-ST-35-10_1050122",1,"Created","The amount of fluid to be used shall be established based on the objectives and methods of the test and the measurements to be performed after the completion of the compatibility tests.\n    NOTE Examples of methods or the tests are micro calorimeter, and pressure measurement."]
["ECSS-E-ST-35-10C","ECSS - Current v1.0","6.9.1g","Requirement","ECSS-E-ST-35-10_1050136",1,"Created","Fracture toughness tests shall be carried out in conformance with ECSS-Q-ST-70-45 clause 5.3 ‘Fracture toughness test’."]
["ECSS-E-ST-35-10C","ECSS - Current v1.0","A.2.1<4>b","Requirement","ECSS-E-ST-35-10_1050153",1,"Created","Reference shall be made to the applicable design definition file, inclusive of its revision status."]
["ECSS-E-ST-35-10C","ECSS - Current v1.0","A.2.1<6>c","Requirement","ECSS-E-ST-35-10_1050160",1,"Created","For each build level, lower build level analyses shall be included for reference."]
["ECSS-E-ST-35-10C","ECSS - Current v1.0","A.2.1<9>a","Requirement","ECSS-E-ST-35-10_1050168",1,"Created","The CAAR shall summarize the tests to be performed."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","4.4b","Requirement","ECSS-E-ST-35_0850015",1,"Created","Interface characteristics amongst the components, sub-systems and the propulsion system shall be accounted for in the respective requirements."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","4.5.1a","Requirement","ECSS-E-ST-35_0850017",1,"Created","When developing a product intended for production use, only mature technologies with TRL higher or equal to 5 shall be used."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","4.5.2.6c","Requirement","ECSS-E-ST-35_0850033",1,"Created","The mass flow shall be verified by representative flight condition tests."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","4.5.6a","Requirement","ECSS-E-ST-35_0850052",1,"Created","The load combinations of the dimensioning case shall be determined from the internal and external loads and documented in the DJF.\n    NOTE 1 Examples of loads are mechanical and thermal loads, pressures, temperatures, temperature gradients.\n    NOTE 2 The determination is based on the functions to be performed by the system, subsystem or component during the whole life.\n    NOTE 3 See ECSS-E-ST-32."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","4.5.8b","Requirement","ECSS-E-ST-35_0850062",1,"Created","Compatibility between the propulsion system and the TVC shall be ensured over the whole operating range."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","4.5.11.4b","Requirement","ECSS-E-ST-35_0850087",1,"Created","If fluids are used to dilute, ventilate or purge areas where hazardous concentrations of fluids can be expected due to leakage, the amount of these fluids shall be accounted for in the leakage budget."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","4.5.13d","Requirement","ECSS-E-ST-35_0850092",1,"Created","Chemical stability of the propellants shall be demonstrated by tests."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","4.5.14.1.2d","Requirement","ECSS-E-ST-35_0850108",1,"Created","The impact of the location and mounting on the operation of the measurement equipment, the response and measurement accuracy shall be verified."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","4.6.2c","Requirement","ECSS-E-ST-35_0850124",1,"Created","The procedures and the design of the equipment shall be such that inadvertent operation and pressurization of the subsystems is avoided."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","4.8.2.1e","Requirement","ECSS-E-ST-35_0850137",1,"Created","For system and sub-system tests, a measurement plan shall be established."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","A.2.1<1>a","Requirement","ECSS-E-ST-35_0850159",1,"Created","The AR-P shall contain a description of the purpose, objective, content and the reason prompting its preparation."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","A.2.1<5>b","Requirement","ECSS-E-ST-35_0850167",1,"Created","The AR-P shall include the discussion on the understanding and clarification of the requirements."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","A.2.1<7>a","Requirement","ECSS-E-ST-35_0850180",1,"Created","The AR-P shall include a discussion of the results in view of\n    1. The accuracy of input data.\n    2. The validation status of the computational methods and models used.\n    3. Deviations in test conditions and test items used to obtain experimental data.\n    4. The simplifications and assumptions used in the models and calculations."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","B.2.1<6.2>b","Requirement","ECSS-E-ST-35_0850197",1,"Created","If experimental input data is used, the data sheet or test results shall be referenced or reproduced in the AR-G;"]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","C.2.1<1>a","Requirement","ECSS-E-ST-35_0850212",1,"Created","In a thermal analysis of a propulsion system, subsystem, or component, the information specified in the DRDs in ECSS-E-ST-31 shall be given:"]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","D.2.1<3>b","Requirement","ECSS-E-ST-35_0850231",1,"Created","The AR-Pl shall include any additional term, definition, abbreviated term or symbol used."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","D.2.1<6.2>d","Requirement","ECSS-E-ST-35_0850242",1,"Created","If experimental input data is used, a description of the test conditions shall be given in the AR-Pl."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","E.2.1<4.2>a","Requirement","ECSS-E-ST-35_0850262",1,"Created","The AR-N shall describe the coordinate systems used in the nozzle- discharge system."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","E.2.1<6.2>f","Requirement","ECSS-E-ST-35_0850272",1,"Created","If data from modelling, not within the project is used, the models from which this data results, shall be referenced and a discussion of these models shall be included. "]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","F.2.1<3>b","Requirement","ECSS-E-ST-35_0850287",1,"Created","The AR-S shall include any additional term, definition, abbreviated term or symbol used."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","F.2.1<6.2>h","Requirement","ECSS-E-ST-35_0850303",1,"Created","An estimate of the accuracy of the methodology shall be included in the AR-S."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","G.2.1<5>b","Requirement","ECSS-E-ST-35_0850317",1,"Created","The AR-Tr shall include:\n    1. A description of the operations.\n    2. A list and a summary of the parameters that are used to describe transient operations and their related effects.\n    3. A discussion of the understanding and clarification of the requirements."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","G.2.1<8>d","Requirement","ECSS-E-ST-35_0850334",1,"Created","In case previous propulsion transients’ analyses are available, the AR-Tr shall include a comparison of the result of the present transient analysis with the previous ones and a report on the discussion of the differences."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","H.2.1<5.1>b","Requirement","ECSS-E-ST-35_0850347",1,"Created","The UM shall include a recommendation that at least one copy of the UM is delivered with the hardware."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","H.2.1<5.8>a","Requirement","ECSS-E-ST-35_0850362",1,"Created","The UM shall list:\n    1. The permitted handling conditions.\n        NOTE For example, change of orientation, position, deposition.\n    2. The limiting conditions for handling.\n        NOTE For example, shocks, environmental conditions.\n    3. Where the handling forces can be applied on the propulsion subsystem or system.\n    4. The protective measures to be implemented.\n    5. The safety measures to be implemented.\n        NOTE Handling is the moving (translation or rotation) of a propulsion subsystem or system when it is not in a container or integrated in a system (e.g. spacecraft, satellite, launcher)."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","H.2.1<6>a","Requirement","ECSS-E-ST-35_0850371",1,"Created","The UM shall contain the following:\n    1. Recommendations for the correct use of the UM.\n    2. Limitations of the UM.\n    3. A statement requesting the user to provide feedback to the propulsion system supplier for statistical evaluation and further improvement of the propulsion system."]
["ECSS-E-ST-35C Rev. 1","ECSS - Current v1.0","I.2.1<6.3>c","Requirement","ECSS-E-ST-35_0850392",1,"Created","The MM-PA shall list the range and conditions for which the mathematical models are valid."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.1.1c","Requirement","ECSS-E-ST-40-07_1630005",1,"Created","The Duration type as per Table 5‑1 shall be used for specifying a duration, as follows:\n1.\tIt is expressed in nanoseconds; \n2.\tIt is stored in a signed 64 bit integer;\n3.\tPositive values correspond to positive durations; \n4.\tNegative values correspond to negative durations.","NOTE\t1\tNanoseconds is the lowest level of granularity supported for time in SMP.\nNOTE\t2\tThe duration type allows specifying values roughly between ‐290 years and 290 years.\nNOTE\t3\tThe duration type allows expression of relative time, hence “negative duration” implies a relative time in the past.\n"]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.1.3g","Requirement","ECSS-E-ST-40-07_1630021",1,"Created","It shall be possible to reference the current object by:\n1.\tthe “.” string \n2.\tan empty string “”","NOTE\tThis allows the following to be used as path to operations of current object:\n·\t.Operation()\n·\t./Operation()\n"]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.2.3.1a","Requirement","ECSS-E-ST-40-07_1630036",1,"Created","All SMP Components shall implement the IComponent interface as per IComponent.h in [SMP_FILES]."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.2.3.1g","Requirement","ECSS-E-ST-40-07_1630043",1,"Created","The IComponent GetField method shall provide access to the IField interface for fields of the component, taking the following argument and behaviour:\n1.\tArgument:\n(a)\t“fullName” giving the path of the field for whom it returns the IField interface.\n2.\tBehaviour:\n(a)\tIf the passed fullName does not exist, it returns nullptr;\n(b)\tIf the passed field name exists and it is a field of simple type it returns its ISimpleField interface;\n(c)\tIf the passed field name exists and it is an array field it returns its IArrayField or ISimpleArrayField interface;\n(d)\tIf the passed field name exists and it is a structure field it returns its IStructureField interface.","NOTE\tThis includes fields of structures and items of arrays.\n"]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.2.4.2g","Requirement","ECSS-E-ST-40-07_1630067",1,"Created","The IReference GetUpper method shall return the upper limit, with the following behaviour:\n1.\tIf a maximum number has been defined, it returns the maximum number;\n2.\tIf no maximum number has been defined, it returns -1.","NOTE\tThe usage of -1 is consistent with the use of upper bounds in UML, where a value of -1 represents no limit (typically shown as *)\n"]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.2.5.2g","Requirement","ECSS-E-ST-40-07_1630078",1,"Created","The IContainer GetLower method shall return the minimum number of components in the collection or 0 when not defined. ","NOTE\tThe lower bound can be used to validate a model hierarchy. If a collection specifies a Lower value above its current Count, then it is not properly configured. An external component can use this information to validate the configuration before executing it.\n"]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.2.7.2a","Requirement","ECSS-E-ST-40-07_1630097",1,"Created","All SMP components which hold entry points and want to allow external access to them shall implement the IEntryPointPublisher interface as per IEntryPointPublisher.h in [SMP_FILES]."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.2.7.2c","Requirement","ECSS-E-ST-40-07_1630099",1,"Created","The IEntryPointPublisher GetEntryPoint method shall return the component’s entry point corresponding to the given name, with the following argument and behaviour:\n1.\tArgument:\n(a)\t“name” giving the name of the EntryPoint to be returned.\n2.\tBehaviour:\n(a)\tIf no entry point with the given name exists, it returns nullptr;\n(b)\tIf an entry point with the given name exists, it returns the corresponding IEntryPoint object.","NOTE\tThe “name” always identifies a unique EntryPoint, as a component cannot have several EntryPoints with same name.\n"]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.2.10.2c","Requirement","ECSS-E-ST-40-07_1630127",1,"Created","The IFallibleModel GetFailure method shall return a failure instance from the list of possible failures, with the following argument and behaviour:\n1.\tArgument:\n(a)\t“name” giving the name of the failure.\n2.\tBehaviour:\n(a)\tIf none of the failures in the list of possible failures matches the given name, it returns nullptr;\n(b)\tIf a failure matching the given name exists, it returns the pointer to the IFailure instance."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.2.11.4e","Requirement","ECSS-E-ST-40-07_1630143",1,"Created","The ISimpleArrayField GetValues method shall return all the array item values stored in an AnySimpleArray as per AnySimpleArray.h in [SMP_FILES] with the following arguments and behaviour:\n1.\tArguments:\n(a)\t“length” giving the length of the return array for values;\n(b)\t“values” giving an array of allocated storage for which the return values are put;\n(c)\t“startIndex” giving the 0-based start index in the array from which values are returned.\n2.\tBehaviour:\n(a)\tIf the given value array size does not match the ArrayField size, it throws an InvalidArraySize as per InvalidArraySize.h in [SMP_FILES];\n(b)\tOtherwise, it copies the range of item values, given by the startIndex and length arguments, into the given AnySimpleArray."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.2.11.6a","Requirement","ECSS-E-ST-40-07_1630151",1,"Created","All SMP simple fields which allow forcing of the field value shall implement the IForcibleField interface as per IForcibleField.h in [SMP_FILES]. "]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.2.13.1b","Requirement","ECSS-E-ST-40-07_1630174",1,"Created","The IProperty GetView method shall return the View Kind for the property. ","NOTE\tSee Table 4‑2 for specification of View Kind.\n"]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.3.1a","Requirement","ECSS-E-ST-40-07_1630189",1,"Created","The Simulation Environment shall provide a component implementing the ILogger interfaces as per Services/ILogger.h in [SMP_FILES]."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.3.1b","Requirement","ECSS-E-ST-40-07_1630190",1,"Created","The component implementing the ILogger interface shall maintain a list mapping the defined Log Message Kinds to names and IDs, including and possibly extending Table 5‑7."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.3.3c","Requirement","ECSS-E-ST-40-07_1630207",1,"Created","The Scheduler shall allow to specify the cycle time between each call for cyclic Events with the following behaviour:\n1.\tFor non-cyclic Events, the cycle time parameter is stored, but not used;\n2.\tFor cyclic Events, the cycle time is a Duration;\n3.\tFor cyclic Simulation Time Events, an InvalidCycleTime exception as per Services/InvalidCycleTime.h in [SMP_FILES] is thrown if the cycle time is a value less than -1 or is 0;\n4.\tFor cyclic Simulation Time Events, if after the event execution the Cycle Time is -1 and repeat count is not 0, then the event is not re-posted on the timeline;\n5.\tFor cyclic Epoch/Mission/Zulu Time Events, an InvalidCycleTime exception as per Services/InvalidCycleTime.h in [SMP_FILES] is thrown if the cycle time is a value less than 1.","NOTE\tto item 1: The cycle time can become relevant if a subsequent call to SetEventRepeat is received before the Event is removed from the scheduler.\n"]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.3.3w","Requirement","ECSS-E-ST-40-07_1630227",1,"Created","When the simulator is in Standby state, the scheduler shall behave as follows:\n1.\tEvents scheduled on simulation time including immediate Events, epoch and mission time are not processed;\n2.\tEvents scheduled on Zulu time are executed."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.3.4c","Requirement","ECSS-E-ST-40-07_1630236",1,"Created","The Event Manager shall maintain a list of pairs of unique event identifiers and entry points.","NOTE\tThe event identifier must only be unique within the Event Manager context; the Scheduler service uses the same EventId type, but uniqueness across services is not required.\n"]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.3.7h","Requirement","ECSS-E-ST-40-07_1630263",1,"Created","The ISimulator Run method shall change the state from Standby to Executing as per the following procedure:\n1.\tIf the simulation is not in Standby state, then it throws an InvalidSimulatorState exception as per InvalidSimulatorState.h in [SMP_FILES];\n2.\tIf the Run method is called during the execution of the global event SMP_LeaveStandby, then it throws an InvalidSimulatorState exception as per InvalidSimulatorState.h in [SMP_FILES];\n3.\tIf the Run method is called during the execution of the global event SMP_EnterStandby, then it throws an InvalidSimulatorState exception as per InvalidSimulatorState.h in [SMP_FILES];\n4.\tIf the simulation is in Standby state, it issues the global event “SMP_LeaveStandby” via the Event Manager;\n5.\tAfter returning from the SMP_LeaveStandby global event, it changes the simulation state to “Executing” state;\n6.\tAfter entering Executing state, it issues the global event “SMP_EnterExecuting” via the Event Manager."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.3.7l","Requirement","ECSS-E-ST-40-07_1630267",1,"Created","The ISimulator Reconnect method shall reconnect the component hierarchy starting at the root component given as parameter, with the following argument and procedure:\n1.\tArgument:\n(a)\t“root” giving the component in the hierarchy for which the reconnect shall start from. If nullptr is passed, the whole simulator tree is reconnected.\n2.\tProcedure: \n(a)\tIf the simulation is not in Standby state, then the method throws an InvalidSimulatorState exception as per InvalidSimulatorState.h in [SMP_FILES];\n(b)\tIf Reconnect method is called during the execution of the global event SMP_LeaveStandby, then the method throws an InvalidSimulatorState exception as per InvalidSimulatorState.h in [SMP_FILES];\n(c)\tIf Reconnect method is called during the execution of the global event SMP_EnterStandby, then the method throws an InvalidSimulatorState exception as per InvalidSimulatorState.h in [SMP_FILES];\n(d)\tIf the simulation is in Standby state, the global event “SMP_LeaveStandby” is issued via the Event Manager;\n(e)\tAfter returning from the SMP_LeaveStandby global event, the simulation state is changed to “Reconnecting” state.\n(f)\tAfter entering Reconnecting state, it issues the global event “SMP_EnterReconnecting” via the Event Manager;\n(g)\tThe simulation environment ensures that all models under the given Root component parameter are published, configured and connected;\n(h)\tAfter Reconnect operation has been completed, it issues the global event “SMP_LeaveReconnecting” via the Event Manager;\n(i)\tAfter returning from the “SMP_LeaveReconnecting” event, the simulation state is changed to Standby;\n(j)\tAfter entering Standby state, the global event “SMP_EnterStandby” is issued via the Event Manager."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.3.7aa","Requirement","ECSS-E-ST-40-07_1630282",1,"Created","The ISimulator CreateInstance method shall create an instance of a component, with the following arguments and behaviour:\n1.\tArguments:\n(a)\t “uuid” giving a unique identifier of the component implementation to create;\n(b)\t“name” giving the name of the new instance;\n(c)\t“description” giving the description of the new instance;\n(d)\t“parent” giving the parent object of the new instance.\n2.\tBehaviour:\n(a)\tIf the “uuid” provided does not corresponds to a registered factory through the RegisterFactory method, it returns nullptr;\n(b)\tIf the name provided is not a valid object name, it raises an InvalidObjectName exception as per InvalidObjectName.h in [SMP_FILES];\n(c)\tIf the parent provided is not a valid object, it raises an InvalidParent exception as per InvalidParent.h in [SMP_FILES];\n(d)\tIf the “uuid” provided corresponds to a registered model, and name and parent are valid, it returns a reference to the newly created model with name, description and parent set as provided. ","NOTE\tThis method is typically called during the Building state when building the hierarchy of models or in the Standby state when adding new components to the hierarchy of models.\n"]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.3.9.1b","Requirement","ECSS-E-ST-40-07_1630300",1,"Created","The IPublication GetTypeRegistry method shall return a reference to the Type Registry.","NOTE\tSee clause 5.3.10 for details on the Type Registry.\n"]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.3.9.2a","Requirement","ECSS-E-ST-40-07_1630312",1,"Created","The simulation environment shall provide a component implementing the IPublishOperation interface as per Publication/IPublishOperation.h in [SMP_FILES]. "]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.3.10.2b","Requirement","ECSS-E-ST-40-07_1630335",1,"Created","The IType GetPrimitiveTypeKind method shall return the primitive type kind as per PrimitiveTypes.h in [SMP_FILES] for types in the type registry as follows:\n1.\tIf the type cannot be mapped to a primitive type kind, it returns PTK_None;\n2.\tIf the type is registered as a derived type of one of the primitive types, it returns the Primitive type kind;\n3.\tIf the type is one of the primitive types themselves, it returns the corresponding primitive type kind. ","NOTE\t1\tThe primitive types are specified in Table 5‑1.\nNOTE\t2\tTypes that cannot be mapped to a primitive type include:\n·\tArrays registered via ITypeRegistry AddArrayType;\n·\tStructures registered via ITypeRegistry AddStructureType;\n·\tClasses registered via ITypeRegistry AddClassType.\nNOTE\t3\tDerived types include:\n·\tEnumerations registered via ITypeRegistry AddEnumerationType;\n·\tStrings registered via ITypeRegistry AddStringType;\n·\tInteger types registered via the ITypeRegistry AddIntegerType;\n·\tFloat types registered via the ITypeRegistry AddFloatType.\n"]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.3.10.5b","Requirement","ECSS-E-ST-40-07_1630342",1,"Created","The IArrayType GetSize method shall return the number of elements in the array."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.4.1.2.1b","Requirement","ECSS-E-ST-40-07_1630366",1,"Created","No recursive Types shall be specified.","NOTE\tModels, interfaces, entry points, fields, etc… are Types in the catalogue, so these Types cannot be typed as, be derived from or use themselves at any level of their specification.\n"]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.4.1.2.2b","Permission","ECSS-E-ST-40-07_1630372",1,"Created","The PrimitiveType for a Float may only point to Float32 or Float64."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.4.1.2.3e","Requirement","ECSS-E-ST-40-07_1630387",1,"Created","A Named Element Name shall only contain letters, digits, and the underscore."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.4.1.2.8c","Requirement","ECSS-E-ST-40-07_1630407",1,"Created","A Reference upper bound shall be ‐1, larger or equal to Reference lower bound."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.4.1.2.12a","Requirement","ECSS-E-ST-40-07_1630417",1,"Created","The EventArgs link for an EventType shall only point to a SimpleType."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","5.4.3.2a","Requirement","ECSS-E-ST-40-07_1630438",1,"Created","All path strings in configuration files shall be valid SMP path strings.","NOTE\tValid SMP path strings are specified in clause 5.1.3\n"]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","6.2.2d","Requirement","ECSS-E-ST-40-07_1630449",1,"Created","Header files shall avoid circular dependencies by using forward declaration."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","6.2.4.4c","Requirement","ECSS-E-ST-40-07_1630465",1,"Created","The ByPointer attribute as per ecss.smp.l1.smpcat in [SMP_FILES] shall have the following effect for the Association C++ mapping:\n1.\tIf set to “true”, then the C++ mapping of the type includes the ‘*’ specifier as per “Association” template in Table 6‑1;\n2.\tIf not set, then the C++ mapping of the type includes the specifier corresponding to the type referenced in the Type attribute as per Table 6‑4;\n3.\tIf set to “false”, then the C++ mapping of the type does not include the ‘*’ specifier."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","6.2.4.6f","Requirement","ECSS-E-ST-40-07_1630481",1,"Created","The Static attribute as per ecss.smp.l1.smpcat in [SMP_FILES] shall have the following effect for the Property C++ mapping:\n1.\tIf set to “true”, then the C++ mapping includes the ‘static’ specifier as per “Property Getter” and “Property Setter” template in Table 6‑1;\n2.\tIf not set, then it has no effect;\n3.\tIf set to “false”, then it has no effect."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","6.2.4.9a","Requirement","ECSS-E-ST-40-07_1630498",1,"Created","EventSink elements shall be mapped to ISO/ANSI C++ member pointer variables as per “EventSink” template in Table 6‑1."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","6.2.5.1c","Requirement","ECSS-E-ST-40-07_1630516",1,"Created","For each type, a method to register the type in the registry shall be defined as per “Global Registry” template in Table 6‑1."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","6.2.6.1c","Requirement","ECSS-E-ST-40-07_1630528",1,"Created","For each type, a method to register the type in the registry shall be defined as follows:\n1.\tSyntax is as per “Scoped Registry” template in Table 6‑1;\n2.\tMethod is declared as member of the C++ structure or class the type is mapped to."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","6.2.6.4d","Requirement","ECSS-E-ST-40-07_1630543",1,"Created","Exception classes shall have a virtual destructor whose access specifier is defined by the mapping of the Visibility attribute.","NOTE\tSee clause 6.2.3 for details on the mapping of Visibility attributes.\n"]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","6.2.7.3a","Requirement","ECSS-E-ST-40-07_1630553",1,"Created","Model types shall be mapped to ISO/ANSI C++ classes as follows:\n1.\tSyntax as per “Model” template in Table 6‑1;\n2.\tIf Base element is defined, the class inherits from the Base class;\n3.\tIf Interface elements are defined, the class inherits from the Interface classes;\n4.\tIf at least one EntryPoint is defined, the class inherits from the Smp::IEntryPointPublisher class;\n5.\tIf at least one EventSink element is defined, the class inherits from the Smp::IEventConsumer class;\n6.\tIf at least one EventSource element is defined, the class inherits from the Smp::IEventProvider class;\n7.\tIf at least one Container element is defined, the class inherits from the Smp::IComposite class;\n8.\tIf at least one Reference element is defined, the class inherits from the Smp::IAggregate class."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","6.3.2j","Requirement","ECSS-E-ST-40-07_1630573",1,"Created","The Library shall contain a GetSmpVersion method as per GetSmpVersion template in  Table 6‑8."]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","6.3.4a","Requirement","ECSS-E-ST-40-07_1630588",1,"Created","A package shall be mapped to a single DLL file. "]
["ECSS-E-ST-40-07C Rev.1","ECSS - Current v1.0","C.2.1a","Requirement","ECSS-E-ST-40-07_1630603",1,"Created","The suffix for configuration files shall be “smpcfg”."]
["ECSS-E-ST-40-08C","ECSS - Current v1.0","5.2.1.2b","Requirement","ECSS-E-ST-40-08_1640007",1,"Created","A Template Argument shall have a Description feature."]
["ECSS-E-ST-40-08C","ECSS - Current v1.0","5.2.1.2i","Requirement","ECSS-E-ST-40-08_1640014",1,"Created","Template argument interpretation and substitution shall be performed during the loading of the Assembly and before applying the Assembly content to the simulator."]
["ECSS-E-ST-40-08C","ECSS - Current v1.0","5.2.6.2f","Permission","ECSS-E-ST-40-08_1640037",1,"Created","A Component Configuration may contain Global Event Subscriptions relative to the component instance defined by the InstancePath feature."]
["ECSS-E-ST-40-08C","ECSS - Current v1.0","5.2.7.2f","Requirement","ECSS-E-ST-40-08_1640049",1,"Created","Mismatch between the Interface implemented by the client model instance and the type of the Reference shall result in an error in the application of the Assembly which contains the Interface Link."]
["ECSS-E-ST-40-08C","ECSS - Current v1.0","5.2.8h","Permission","ECSS-E-ST-40-08_1640066",1,"Created","The Model Instance may contain Links."]
["ECSS-E-ST-40-08C","ECSS - Current v1.0","5.2.8l","Requirement","ECSS-E-ST-40-08_1640070",1,"Created","A Model Instance, which is not the root instance of an Assembly, shall have the Container feature, which provides the Name of the parent Model Instance container in which the model instance is created.","NOTE\tA child instance is added to one of the compatible Containers of the parent instance, meaning it is the container with the object type that is compatible with the child instance type (same implemented Interface).\n"]
["ECSS-E-ST-40-08C","ECSS - Current v1.0","5.4.3.2a","Requirement","ECSS-E-ST-40-08_1640096",1,"Created","Template argument interpretation and substitution shall be performed during the loading of the Schedule and before applying the Schedule content to the simulator."]
["ECSS-E-ST-40-08C","ECSS - Current v1.0","5.4.5l","Permission","ECSS-E-ST-40-08_1640112",1,"Created","Execute Task Activity may provide the RootPath feature that contains the root model instance path of the sub-assembly with which the referenced external Schedule is associated."]
["ECSS-E-ST-40-08C","ECSS - Current v1.0","5.4.6g","Requirement","ECSS-E-ST-40-08_1640121",1,"Created","Mission Time Event shall provide the MissionTime feature that specifies the event first occurrence mission time.","NOTE\tSemantics of this feature is as specified in ECSS-E-ST-40-07.\n"]
["ECSS-E-ST-40-08C","ECSS - Current v1.0","5.5.1.2m","Requirement","ECSS-E-ST-40-08_1640141",1,"Created","The application order of field values, property values and operation calls shall follow their specification order in the Assembly or in the Link Base artefact. ","NOTE\tThe specification order is in general the order in which the loader reads in from the file: elements at the top are read-in first, the loader progressing towards the bottom of the file.\n"]
["ECSS-E-ST-40-08C","ECSS - Current v1.0","5.5.1.2n","Requirement","ECSS-E-ST-40-08_1640142",1,"Created","Adding elements to unresolved element lists shall respect the order in which the elements appear in the Assembly."]
["ECSS-E-ST-40-08C","ECSS - Current v1.0","5.5.4.2d","Requirement","ECSS-E-ST-40-08_1640156",1,"Created","The ISimulatorL2 LoadSchedule method shall load and apply a Schedule file with the following argument and behaviour:\n1.\tArgument:\n(a)\t“schedulePath” giving the path to the schedule file to load.\n2.\tBehaviour:\n(a)\tIf called while simulator is neither in the Building nor in the Standby state, it throws an InvalidSimulatorState exception as per InvalidSimulatorState.h in [SMPL1_FILES];\n(b)\tIf called with an invalid schedulePath, it throws a FileNotFound exception as per FileNotFound.h in [SMPL1_FILES];\n(c)\tIf called more than one time, it requests the Logger to write a warning message and it returns immediately;\n(d)\tOtherwise, it loads and applies the schedule file according to clause 5.5.2;\n(e)\tIf an error is encountered during the processing of the file, it throws InvalidFile as per InvalidFile.h in [SMPL1_FILES] providing a textual description of the error.","NOTE\t1\tThe message has to contain sufficient information to identify easily and unambiguously the source element that causes the error.\nNOTE\t2\tto item (c): This is because a simulator can use at most one Schedule.\n"]
["ECSS-E-ST-40-08C","ECSS - Current v1.0","5.7.2.3f","Permission","ECSS-E-ST-40-08_1640171",1,"Created","A Link may specify paths to elements that do not exist at loading time and that are created dynamically during the simulator Building state or during the simulator Reconnecting state."]
["ECSS-E-ST-40-08C","ECSS - Current v1.0","5.8.2h","Requirement","ECSS-E-ST-40-08_1640193",1,"Created","The data type specified in the Field Value shall be checked against the corresponding Field data type."]
["ECSS-E-ST-40-08C","ECSS - Current v1.0","5.8.2p","Requirement","ECSS-E-ST-40-08_1640201",1,"Created","The Set Property Activity execution shall be mapped to a call to SetValue() on the Smp::IProperty interface."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","5.2.4.3a","Requirement","ECSS-E-ST-40_0860010",1,"Informative Change","The customer shall specify the external interfaces of the software, including the static and dynamic aspects, for nominal and degraded modes.\nEXPECTED OUTPUT:\tExternal interface requirements specification [RB, IRD; SRR].","NOTE \tExternal interfaces include interfaces with ASIC and FPGA.\n"]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","5.2.4.4b","Requirement","ECSS-E-ST-40_0860724",1,"Created","The customer shall specify the security constraints on the content of the system database as specified under 5.2.4.4a for the supplier, based on the security sensitivity of the data in the database."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","5.3.2.2a","Requirement","ECSS-E-ST-40_0860022",2,"Normative Change","The interfaces between development and maintenance shall be identified in the software life cycle.\nEXPECTED OUTPUT:\tIdentification of interface between development and maintenance [MGT, SDP; PDR].","NOTE \tThis includes documents to be handed over and tools to be kept for maintenance.\n"]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","5.3.4.3b","Requirement","ECSS-E-ST-40_0860040",2,"Normative Change","In case the software detailed design is baselined before the start of the coding, the part of the CDR addressing the software detailed design, the interfaces design and the software budget shall be held in a separate joint review anticipating the CDR, in a detailed design review (DDR).\nAIM:\tTo baseline the software detailed design before the start of the coding.\nEXPECTED OUTPUT:\tApproved detailed design, interface design and budget [DDF, DJF; CDR].","NOTE \te.g. in case of complex software products or when an early baseline of the design is required.\n"]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","5.3.8.1a","Requirement","ECSS-E-ST-40_0860049",2,"Normative Change","Technical budget targets and margin philosophy dedicated to the software shall be specified by the customer in the requirements baseline in order to define the limits of software budgets associated with computer and network resources such as PU load, maximum memory size, deadline fulfilment, communication, archiving needs, remote access needs and performance requirements such as data throughput.\nAIM:\tThis allows anticipating:\n—\tExpected changes in the requirements baseline,\n—\tRequirements on reprogramming of the system during operational use,\n—\tRequired budget for temporary copies of software images,\n—\tConstraints on state transitions, especially when recovery from a faulty state is concerned,\n—\tConstraints on physical processor (CPU) type and memory  and expected processor capacity, wait states, interfaces, caching and pipelining, interference scheme between processing units, etc.,\n—\tEquipment, communication and performances aspects such as buses, protocols, acceptable errors, bus capacity usage by other sources.,\n—\tAccuracy aspects, such as conversion to/from analogue signals, and accuracy of timing signals,\n—\tBudgets for OS kernel characterisation, such as context switch latency or deadlines for tasking,\n—\tMission and system operation characteristics and reference operational scenarios.\nEXPECTED OUTPUT:\tTechnical budgets and margin philosophy for the project [RB, SSS; SRR]."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","5.5.2.1b","Requirement","ECSS-E-ST-40_0860071",1,"Informative Change","Each software component shall be refined into lower levels containing software units that can be coded, compiled, and tested.\nEXPECTED OUTPUT:\tSoftware components design documents [DDF, SDD; CDR]."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","5.5.2.5b","Requirement","ECSS-E-ST-40_0860077",1,"Informative Change","The supplier shall document and justify all timing and synchronization mechanisms.\nEXPECTED OUTPUT:\tReal-time software dynamic design model [DDF, SDD; CDR]."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","5.6.2.1a","Requirement","ECSS-E-ST-40_0860092",1,"Informative Change","The validation process shall be established to validate the software product.\nEXPECTED OUTPUT:\tSoftware validation plan - validation process identification [DJF, SValP; PDR]."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","5.6.4.2b","Requirement","ECSS-E-ST-40_0860107",1,"Informative Change","The validation tests shall be “black box”, i.e. performed on the final software product to be delivered, without any modification of the code or of the data.\nEXPECTED OUTPUT:\tSoftware validation report with respect to the requirements baseline [DJF, - ; QR, AR].","NOTE \tIn particular, this is essential when a mission database is used to customize the final product, and when late versions of the database are used to update the software.\n"]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","5.7.3.2a","Requirement","ECSS-E-ST-40_0860118",1,"Informative Change","The customer shall perform the acceptance testing.\nEXPECTED OUTPUT:\tAcceptance test report [DJF, - ; AR]."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","5.8.3.5a","Requirement","ECSS-E-ST-40_0860134",2,"Normative Change","The supplier shall verify the software code ensuring at least that:\n1.\tthe code is externally consistent with the requirements and design of the software item;\n2.\tthere is internal consistency between software units;\n3.\tthe code is traceable to design and requirements, testable, correct, and in conformity to software requirements and coding standards;\n4.\tthe code that is not traced to the units is justified;\n5.\tthe code implements proper events sequences, consistent interfaces, correct data and control flow, completeness, appropriate allocation of timing and sizing budgets;\n6.\tthe code implements safety, security, and other critical requirements correctly as shown by appropriate methods;\n7.\tthe code is implemented in a way that it cannot result in runtime errors;\n8.\tthe effects of any residual runtime errors are controlled through error handling.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na.\tSoftware code traceability matrices [DJF, SVR; CDR];\nb.\tSoftware code verification report [DJF, SVR; CDR].","NOTE \tExamples of code checks are proposed in Annex U.\n"]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","5.8.3.11b","Requirement","ECSS-E-ST-40_0860149",1,"Informative Change","As part of the verification of the software detailed design, the supplier shall refine the schedulability analysis performed during the software architectural design on the basis of the software detailed design documentation.\nEXPECTED OUTPUT:\tSchedulability analysis (update) [DJF, SVR; CDR]."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","5.9.5.2b","Requirement","ECSS-E-ST-40_0860168",1,"Informative Change","The SOS entity shall address user’s requests.\nEXPECTED OUTPUT:\tUser’s request record - actions [OP, - ; - ]."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","5.10.2.1e","Requirement","ECSS-E-ST-40_0860176",1,"Informative Change","Whenever problems are encountered, they shall be recorded and entered in accordance with the change control established and maintained in conformance with ECSS-M-ST-40.\nEXPECTED OUTPUT:\tProblem and nonconformance report [MF, - ; QR ].","NOTE \tECSS-Q-ST-80 clause 5.2.6 (non-conformances) and clause 5.2.5 (software problems) contain further requirements relevant for this clause.\n"]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","5.10.5.1a","Requirement","ECSS-E-ST-40_0860190",1,"Informative Change","The maintainer shall conduct joint reviews with the organization authorizing the modification to determine the integrity of the modified system.\nEXPECTED OUTPUT:\tJoint review reports [MF, - ; - ]."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","5.10.7.4a","Requirement","ECSS-E-ST-40_0860204",1,"Informative Change","Data used by or associated with the retired software product shall be accessible in accordance with the business agreement requirements for data protection and audit applicable to the data.\nEXPECTED OUTPUT:\tRetirement plan [MF, - ; - ]."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","5.11.3l","Requirement","ECSS-E-ST-40_0860758",1,"Created","In the absence of an existing classification, the software security analysis shall classify software components according to their sensitivity.\nEXPECTED OUTPUT:\tSoftware security analysis report [SF, SSAR; PDR, CDR].","NOTE \tA classification can be can be defined on the basis of a classification guide.\n"]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","5.11.5.4a","Requirement","ECSS-E-ST-40_0860777",1,"Created","Validation activities shall conform with applicable security organisational regulations and policies.","NOTE \tRegulations and policies can require, for example, that only authorised personnel perform certain activities or the use of protected facilities.\n"]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","5.11.5.6d","Requirement","ECSS-E-ST-40_0860787",1,"Created","The software security analysis, vulnerabilities and risks shall be reviewed and updated as necessary as part of changes implemented during software maintenance.\nEXPECTED OUTPUT:\tSoftware security analysis report [SF, -; -]."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","B.2.1<4.4>d","Recommendation","ECSS-E-ST-40_0860668",2,"Normative Change","d.\tIf a system specification defines a product that is a component of a parent system or project, then the SSS should list the activities that are supported by external systems."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","B.2.1<5.2>e","Requirement","ECSS-E-ST-40_0860226",1,"Unchanged","The SSS shall state the capabilities to be implemented by on-board control procedures (OBCP) (5.2.4.6)"]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","B.2.1<6.1>b","Requirement","ECSS-E-ST-40_0860795",1,"Created","The SSS shall include the requirements needed for planning and setting up the system security verification and validation process related to software"]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","C.2.1<4.4>a","Requirement","ECSS-E-ST-40_0860258",1,"Unchanged","The IRD shall list or make reference to the existing assumptions and dependencies."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","D.2.1<4.3>a","Requirement","ECSS-E-ST-40_0860271",1,"Unchanged","The SRS shall describe in detail the product’s relationship to other systems."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","D.2.1<5.4>b","Requirement","ECSS-E-ST-40_0860287",1,"Unchanged","The following interfaces shall be fully described either in the SRS itself or by reference to the ICD:\n1.\tinterfaces between the software item and other software items;\n2.\tinterfaces between the software item and hardware products;\n3.\tinterfaces requirements relating to the man–machine interaction."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","D.2.1<5.7>b","Requirement","ECSS-E-ST-40_0860295",1,"Unchanged","Requirements applicable to the following items shall be included:\n1.\tsoftware standards (e.g. applicable coding standards, and development standards);\n2.\tdesign requirements;\n3.\tspecific design methods to be applied to minimize the number of critical software components (see ECSS-Q-ST-80 6.2.2.4);\n4.\trequirements relevant to numerical accuracy management;\n5.\tdesign requirements relevant to the “in–flight modification” of the software item;\n6.\tspecific design requirements to be applied if the software is specified to be designed for intended reuse;\n7.\tspecific constraints induced by reused software (e.g. COTS, free software and open source)."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","E.2.1<3>a","Requirement","ECSS-E-ST-40_0860317",2,"Normative Change","The ICD shall include any additional terms, definition or abbreviated terms used not already defined in any applicable or reference documentation."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","E.2.1<6>b","Requirement","ECSS-E-ST-40_0860330",1,"Unchanged","A validation matrix (requirements to validation approach correlation table) shall be utilized to describe the validation approach applicable to each requirement."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","F.2.1<5.1>a","Requirement","ECSS-E-ST-40_0860346",1,"Unchanged","The SDD shall describe the software architectural design."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","F.2.1<5.2>b","Requirement","ECSS-E-ST-40_0860351",1,"Unchanged","The software static architecture shall be summarized describing its components."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","F.2.1<5.4.8>e","Recommendation","ECSS-E-ST-40_0860704",1,"Unchanged","If control flows take place during execution (e.g. interrupt), they should be described."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","F.2.1<6>c","Requirement","ECSS-E-ST-40_0860391",1,"Unchanged","The SDD shall define the potential specific measures taken for critical software in the design documentation."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","H.2.1<3>a","Requirement","ECSS-E-ST-40_0860402",2,"Normative Change","The SUM shall include any additional terms, definition or abbreviated terms used not already defined in any applicable or reference documentation."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","H.2.1<10.2>a","Requirement","ECSS-E-ST-40_0860420",2,"Normative Change","The SUM shall include the help information about the actions to be performed by the user, how to invoke the function, possible errors, how to resolve them and what results to expect."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","H.2.1<10.4>a","Requirement","ECSS-E-ST-40_0860422",1,"Unchanged","The SUM shall include a guide to the command language used, operations and functions."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","I.2.1<4.3>b","Requirement","ECSS-E-ST-40_0860435",1,"Unchanged","This SVerP shall describe the schedule for the planned verification activities."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","J.2.1<3>a","Requirement","ECSS-E-ST-40_0860450",2,"Normative Change","The SValP shall include any additional terms, definition or abbreviated terms used not already defined in any applicable or reference documentation."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","J.2.1<6>a","Requirement","ECSS-E-ST-40_0860473",1,"Unchanged","The SValP shall describe the overall requirements applicable to the software validation testing activities, providing for definition of overall requirements, guidelines on the kinds of tests to be executed. "]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","J.2.1<9>a","Requirement","ECSS-E-ST-40_0860480",1,"Unchanged","The SVS w.r.t. TS or RB shall list the requirements of the TS or RB that cannot be tested in the validation environment and need the full real system to be tested, therefore including the customer support."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","K.2.1<5.7>a","Requirement","ECSS-E-ST-40_0860494",1,"Unchanged","The SUITP shall describe (or refer to the SDP) risks to the software unit testing and integration testing campaign."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","K.2.1<8.2.3>b","Requirement","ECSS-E-ST-40_0860510",1,"Unchanged","The description specified in a. shall provide the rationale for the test case selection and grouping into test procedures."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","K.2.1<9.2.8>a","Requirement","ECSS-E-ST-40_0860525",1,"Unchanged","The SUITP shall describe all the test cases to be executed before this test case. "]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","L.2.1<5.6>a","Requirement","ECSS-E-ST-40_0860545",1,"Unchanged","The SVS shall address separately the activities to be performed for manually and automatically generated code, although they have the same objective (ECSS-Q-ST-80 clause 6.2.8.2 and 6.2.8.7)."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","L.2.1<7.1>a","Requirement","ECSS-E-ST-40_0860555",1,"Unchanged","The SVS w.r.t. TS or RB shall provide the identification of software validation test cases. "]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","M.2.1<1>a","Requirement","ECSS-E-ST-40_0860576",1,"Unchanged","The SVR shall contain a description of the purpose, objective, content and the reason prompting its preparation."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","M.2.1<4.5>a","Requirement","ECSS-E-ST-40_0860585",2,"Normative Change","The SVR shall present in gathering all the specific verification reports that have been planned to be provided w.r.t. the SVerP, including:\n1.\tTraceability (when not already included in related software acceptance documents), presenting the following traceability matrices:\no\tSoftware acceptance testing to requirements baseline.\n2.\tFeasibility, presenting in gathering all the specific verification reports that have been planned to be provided w.r.t. the SVerP, including:\no\tStructural code coverage achievement (update for QR and AR);\no\tVerification of software documentation as per 5.8.3.10;\no\tOthers specific verification related to RAMS design (e.g. unit and integration testing coverage ratio)."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","N.2.1<4>b","Requirement","ECSS-E-ST-40_0860599",2,"Normative Change","For each software item, the SRF shall provide (or state the absence of) the following information:\n1.\tsoftware item name and main features;\n2.\tsoftware item developer identification;\n3.\tconsidered version and list of components;\n4.\tlicensing conditions;\n5.\tindustrial property and exportability constraints, if any;\n6.\timplementation language;\n7.\tdevelopment and execution environment (e.g. platform, and operating system);\n8.\tapplicable dispositions for warranty, maintenance, installation and training;\n9.\tcommercial software necessary for software execution, if any;\n10.\tsize of the software (e.g. number of source code lines, and size of the executable code)."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","O.2.1<4.5>a","Requirement","ECSS-E-ST-40_0860616",1,"Unchanged","The SDP shall describe the contribution of the software engineering function to the project risk management approach.","NOTE \tSee ECSS-M-ST-80 for further explanations.\n"]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","O.2.1<5.3>a","Requirement","ECSS-E-ST-40_0860629",1,"Unchanged","The SDP shall describe (or provide references to their description of) the applied methodologies and list the standards for each software process and relevant activity."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","O.2.1<5.5.4>b","Requirement","ECSS-E-ST-40_0860646",1,"Unchanged","Any tailoring to applicable documentation standards shall be detailed in this clause."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","P.2.1<8>b","Permission","ECSS-E-ST-40_0860716",1,"Unchanged","The agenda of the presentation session may be as follows:\n1.\tPresentation of the review group and its report;\n2.\tPresentation of the project (context, technical and management requirements);\n3.\tPresentation of the product (definition, critical points, performance, operations);\n4.\tState of recommendations of the previous review (if any)."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","T.2.1<3>a","Requirement","ECSS-E-ST-40_0860802",1,"Created","The SMP shall include any additional terms, definition or abbreviated terms used not already defined in any applicable or reference documentation."]
["ECSS-E-ST-40C Rev.1","ECSS - Current v1.0","T.2.1<10.1>b","Requirement","ECSS-E-ST-40_0860822",1,"Created","The SMP shall describe the Software Configuration Control Board (i.e. participants, roles, activities)."]
["ECSS-E-ST-50-02C","ECSS - Current v1.0","4.1.2a","Requirement","ECSS-E-ST-50-02_0870001",1,"Created","The Earth-to-Space link function shall consist of the following:\n    1. Reception of control signals for ranging signal composition (tone frequency, ambiguity resolution code, and modulation index).\n    2. Generation of the ambiguity resolution code.\n    3. Generation of the composite ranging signal, consisting of tone and code.\n    4. Selection of the modulating source, between.\n        (a) ranging,\n        (b) telecommand, and\n        (c) ranging and telecommand.\n    5. Generation and phase modulation of the first Earth-to-Space link intermediate frequency (IF) carrier.\n    6. Local oscillator (LO) frequency selection and up-conversion of the modulated IF carrier to the assigned Earth-to-Space link radio frequency (RF).\n    7. Power amplification of the RF signal.\n    8. Transmission to spacecraft."]
["ECSS-E-ST-50-02C","ECSS - Current v1.0","4.2.2.2a.3","Requirement","ECSS-E-ST-50-02_0870016",1,"Created","the series of codes is described by means of the following expression:\nCn = Q1   Å  Q2  Å     Q3   Å … Qn\nwhere\nCn\tis the n-th code;\nÅ\tstands for exclusive or;\n\t\t\t   Qi\tare square waves at frequencies 2-i x ft ."]
["ECSS-E-ST-50-02C","ECSS - Current v1.0","4.2.3.2.3a","Recommendation","ECSS-E-ST-50-02_0870097",1,"Created","If the simultaneous ranging and telecommand mode is selected (see also clause 4.2.2.5), the following conditions should be taken into account in order to minimize this interference:\n1.\tPCM(NRZ-L)/PSK/PM telecommand\n| 2 m fTC - ft  |   ³  5 Hz \n| (2 n - 1) fTC  -  ft  |   ³  2 fb \nwhere\nft\t= tone frequency \nfb\t= telecommand bit rate\nfTC\t= telecommand subcarrier frequency\nm, n\t= integers \n2.\tPCM(SP-L)/PM telecommand \n|ft  - fb | ³  2,5 fb   \n|ft - 3 fb| ³  fb\n|k fb - ft | ³ 5 Hz\nwhere\nft\t= tone frequency\nfb\t= telecommand bit rate \nk\t= integer "]
["ECSS-E-ST-50-02C","ECSS - Current v1.0","4.5.5a","Requirement","ECSS-E-ST-50-02_0870051",1,"Created","In order to verify correct functioning of the system and for calibration purposes, telemetry information shall be available regarding: \n    1. the chosen mode of operation, \n    2. the receiver input level, \n    3. the receiver frequency offset from the best lock frequency, \n    4. the lock status, and\n    5. the transponder temperature and power supply voltage."]
["ECSS-E-ST-50-02C","ECSS - Current v1.0","4.5.9b","Requirement","ECSS-E-ST-50-02_0870060",1,"Created","For category B missions, the modulation index shall be selectable by telecommand to at least two values between 0,2 rad and 0,7 rad. "]
["ECSS-E-ST-50-02C","ECSS - Current v1.0","4.6.3.2c","Recommendation","ECSS-E-ST-50-02_0870099",1,"Created","The error due to the station group delay variation versus frequency should be as per clauses 4.4.1a.10 and 4.4.2.1a.8. \n    NOTE Since normal mission scenarios result in small Doppler shifts on the nominal carrier and tone frequencies, this effect is typically negligible."]
["ECSS-E-ST-50-02C","ECSS - Current v1.0","5.1a","Permission","ECSS-E-ST-50-02_0870102",1,"Created","The tests to demonstrate compatibility of ranging transponder and Earth equipment as specified in clause 5.2 may be combined with similar telecommand and telemetry compatibility tests;"]
["ECSS-E-ST-50-05C Rev. 2","ECSS - Current v1.0","4.2.2a","Requirement","ECSS-E-ST-50-05_0900016",1,"Unchanged","The same RFI mitigation methods specified in 4.2.1.2.1 for the 2 200 MHz - 2 290 MHz band shall be applied to the 8 025 MHz - 8 400 MHz band.\n    NOTE The 8 025 MHz - 8 400 MHz band is the only direct data transmission band allocated to the Earth Exploration Satellite service below 20 GHz. Its occupation density is similar to that of the 2 200 MHz - 2 290 MHz band; additionally the interference situation is aggravated by the fact that most of the Earth Exploration-Satellites use very similar (polar) orbits."]
["ECSS-E-ST-50-05C Rev. 2","ECSS - Current v1.0","5.2.1b","Requirement","ECSS-E-ST-50-05_0900033",1,"Unchanged","In addition to clause 5.2.1a for Category B missions the short term frequency stability shall be such that the resulting phase error when tracking the carrier with a second-order PLL with loop bandwidth 2BL as specified for the mission, does not exceed 10 degrees peak in high signal-to-noise conditions and in non-coherent mode.\n    NOTE 1 The “short term frequency stability” includes phase noise contribution and any “instantaneous” phase or frequency variations (“discontinuities”) due to technological aspects and related to oscillator implementation.\n    NOTE 2 Depending on the link budget and on the ground station 2BL value, this requirement may have strong impact on the onboard subsystem architecture and the selection of the proper oscillator technology."]
["ECSS-E-ST-50-05C Rev. 2","ECSS - Current v1.0","5.5.1.4a","Requirement","ECSS-E-ST-50-05_0900045",1,"Unchanged","Spurious emissions from spacecraft which are active during the launch shall be in conformance to the RF interface requirements of the launcher.\n    NOTE For guidance on the levels to be met by the spacecraft equipment in terms of directly measurable parameters (e.g. power, frequency in an antenna feed cable), the conversion method given in Annex C can be used. This annex also provides some examples of typical requirements for Ariane 5. Note that the conversion method given is used to derive an estimate of the values; however, the real requirement is on the actual field strength at the vehicle equipment bay antennas."]
["ECSS-E-ST-50-05C Rev. 2","ECSS - Current v1.0","6.1.1a","Requirement","ECSS-E-ST-50-05_0900061",1,"Unchanged","Phase modulation shall be used for the following:\n    1. Telemetry in the UHF (2 200 MHz - 2 300 MHz), SHF (8 400 MHz - 8 500 MHz) and EHF (31,8 GHz - 32,3 GHz) bands, unless modulation in accordance with clause 6.2 of this Standard is adopted.\n    2. Telecommand in the UHF (2 025 MHz - 2 120 MHz), SHF (7 145 MHz - 7 235 MHz) and EHF (34,2 GHz - 34,7 GHz) bands.\n    3. Ranging (Earth-space) in the UHF (2 025 MHz - 2 120 MHz), SHF (7 145 MHz - 7 235 MHz) and EHF (34,2 GHz - 34,7 GHz) bands.\n    4. Ranging (space-Earth) in the UHF (2 200 MHz - 2 300 MHz), SHF (8 400 - 8 500 MHz) and EHF (31,8 GHz - 32,3 GHz) bands."]
["ECSS-E-ST-50-05C Rev. 2","ECSS - Current v1.0","6.1.4.1.2c","Requirement","ECSS-E-ST-50-05_0900070",1,"Unchanged","For telecommand symbol rates in excess of 4 ksps, the symbols shall be SP-L encoded and directly modulated onto the carrier."]
["ECSS-E-ST-50-05C Rev. 2","ECSS - Current v1.0","6.1.5b","Requirement","ECSS-E-ST-50-05_0900090",1,"Unchanged","To ensure recovery of the symbol clock by the ground demodulators, the maximum string of either ones or zeros shall be limited to 64 symbols."]
["ECSS-E-ST-50-05C Rev. 2","ECSS - Current v1.0","6.1.11a","Requirement","ECSS-E-ST-50-05_0900105",1,"Unchanged","The residual power in the modulated carrier shall be greater than -15 dBc for space-Earth and -10 dBc for Earth-space links."]
["ECSS-E-ST-50-05C Rev. 2","ECSS - Current v1.0","6.2.2e","Recommendation","ECSS-E-ST-50-05_0900279",1,"Created","From a spectrum efficiency point of view, OQPSK should be used instead of QPSK."]
["ECSS-E-ST-50-05C Rev. 2","ECSS - Current v1.0","6.2.3.2d","Requirement","ECSS-E-ST-50-05_0900126",1,"Unchanged","Modulation shall be such that for each channel, the suppression of the signal from the other channel is more than 21 dB."]
["ECSS-E-ST-50-05C Rev. 2","ECSS - Current v1.0","6.2.3.5d","Requirement","ECSS-E-ST-50-05_0900150",1,"Unchanged","In the case of impairments the following conditions shall be met:\n    1. For an I-Q implementation of the modulator:\n        (a) A phase angle between the two quadrature carriers of (90 ± 5)°.\n        (b) An amplitude imbalance between the two quadrature carriers of less than 0,5 dB.\n        (c) A modulation such that for each channel, the suppression of the signal from the other channel is more than 21 dB.\n    2. For any implementation, a synchronization of the symbol clocks within ±2 % of the symbol period or 1 ns, whichever is larger. \n    3. For digital implementation:\n        (a) A FIR filter impulse response of at least 4 bits long for category B applications and 5 bits long for category A applications.\n        (b) A minimum number of bits for the FIR coefficient quantization of 12."]
["ECSS-E-ST-50-05C Rev. 2","ECSS - Current v1.0","6.2.7a","Requirement","ECSS-E-ST-50-05_0900165",1,"Unchanged","The carrier suppression shall always be greater than 30 dBc."]
["ECSS-E-ST-50-05C Rev. 2","ECSS - Current v1.0","7.2.1c","Requirement","ECSS-E-ST-50-05_0900181",1,"Unchanged","After a single sweep the frequency shall return to the centre value."]
["ECSS-E-ST-50-05C Rev. 2","ECSS - Current v1.0","7.2.4b","Recommendation","ECSS-E-ST-50-05_0900285",1,"Created","The Earth station design should be such that it can enable the support of transponders with other PLL bandwidths.\n    NOTE This can be achieved by including flexibility on the parameters given in 7.2.4a."]
["ECSS-E-ST-50-05C Rev. 2","ECSS - Current v1.0","8.2.2c","Recommendation","ECSS-E-ST-50-05_0900286",1,"Created","When the definitive spacecraft parameters are specified, the final version of the document should be produced and agreed upon by the project manager and the duly appointed representative of the network operations manager."]
["ECSS-E-ST-50-05C Rev. 2","ECSS - Current v1.0","8.3.2f","Requirement","ECSS-E-ST-50-05_0900214",1,"Unchanged","If a particular variance is dominant, its statistics shall be treated separately."]
["ECSS-E-ST-50-05C Rev. 2","ECSS - Current v1.0","9.2.2e","Requirement","ECSS-E-ST-50-05_0900229",1,"Unchanged","The constellation mapper shall deliver 4 parallel symbols coded with three bits to perform 8PSK modulation based on natural mapping (i.e., 0, 1, 2 …, 7 anticlockwise)."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.2.2d","Requirement","ECSS-E-ST-50-11_1410006",1,"Created","The SpaceFibre Network layer shall use the services of the SpaceFibre Data Link layer."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.2.4c","Requirement","ECSS-E-ST-50-11_1410012",1,"Created","The Multi-Lane layer shall use the services of the SpaceFibre Lane layer."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.3.3.2d","Requirement","ECSS-E-ST-50-11_1410040",1,"Created","The fourth and final symbol in the SKIP control word shall be a copy of the third symbol. ","NOTE\tThe SKIP control word is used to support operation of the data signalling rate compensation in the SpaceFibre receiver, see 5.5.3.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.3.3.4a","Requirement","ECSS-E-ST-50-11_1410045",1,"Created","The INIT1 control word, used during lane initialisation, shall begin with an initialisation comma, K28.5, which is in the least significant symbol position of the control word and is sent first."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.3.3.7c","Requirement","ECSS-E-ST-50-11_1410060",1,"Created","The third symbol in the Inverse INIT2 control word shall identify the Lane Layer Control Word as being an Inverse INIT2 control word, and has the value D25.2."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.3.3.10c","Requirement","ECSS-E-ST-50-11_1410081",1,"Created","The third symbol in the LOST_SIGNAL control word shall identify the Lane Layer Control Word as being a LOST_SIGNAL control word, and has the value D4.3."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.3.4.2e","Requirement","ECSS-E-ST-50-11_1410090",1,"Created","When a particular bit is set in the ACT field of an ACTIVE control word, it shall indicate that the corresponding lane at the end of the link sending the ACTIVE control word is in the Active state."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.3.5.1.4a","Requirement","ECSS-E-ST-50-11_1410112",1,"Created","The EDF control word shall be used to indicate the end of a data frame."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.3.5.1.5d","Requirement","ECSS-E-ST-50-11_1410120",1,"Created","The third symbol in the SBF control word shall be a data symbol with any value from D0.0 to D31.7 and encode a data character containing the broadcast channel number that this broadcast frame is travelling over."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.3.5.2c","Requirement","ECSS-E-ST-50-11_1410135",1,"Created","The FCT control word shall begin with the K28.3 control character which is in the least significant symbol position of the control word and is sent first."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.3.5.3.3c","Requirement","ECSS-E-ST-50-11_1410149",1,"Created","The second symbol in the NACK control word shall identify the control word as being a NACK control word, and has the value D27.5."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.3.6e","Requirement","ECSS-E-ST-50-11_1410165",1,"Created","When loss of signal, (LoS), is detected, at least one RXERR word shall be passed up to the Multi-Lane or Data Link layer"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.3.8.2c","Requirement","ECSS-E-ST-50-11_1410184",1,"Created","A data frame shall contain between one and N×64 data words each, where N is an integer less than or equal to the \"maximum number of data-sending lanes\" parameter."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.3.8.3f","Requirement","ECSS-E-ST-50-11_1410195",1,"Created","The PRBS shall be generated using the algorithm specified in clause 5.7.6.2.3."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.3.8.4d","Requirement","ECSS-E-ST-50-11_1410205",1,"Created","The broadcast channel, BC, field in the SBF control word shall identify the broadcast channel transmitting and receiving the broadcast frame."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.3.10c","Requirement","ECSS-E-ST-50-11_1410224",1,"Created","Once one or more lanes have been established to form a link, the control words and frames shall have the following precedence:\n1.\tSKIP, highest precedence.\n2.\tLOST_SIGNAL.\n3.\tSTANDBY.\n4.\tALIGN.\n5.\tACTIVE.\n6.\tRETRY.\n7.\tBroadcast frame in error recovery buffer to be resent.\n8.\tBroadcast frame.\n9.\tACK/NACK.\n10.\tFCT in error recovery buffer to be resent.\n11.\tFCT.\n12.\tFULL.\n13.\tData frame in error recovery buffer to be resent.\n14.\tData frame.\n15.\tIdle frame.\n16.\tIDLE, lowest precedence.","NOTE\tIt is not possible for an ACK and NACK to be waiting to be sent at the same time: one replaces the other.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.3.10s","Requirement","ECSS-E-ST-50-11_1410240",1,"Created","While any broadcast frames or FCTs or data frames in the error recovery buffer are being resent, new data frames cannot be sent and shall wait for the error recovery buffer to finish resending any broadcast frames or FCTs or data frames it contains.","NOTE\tSee clause 5.7.7 for details of error recovery.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.4.2.1f","Requirement","ECSS-E-ST-50-11_1410258",1,"Created","The recovered serial bit stream shall be converted to 10-bit parallel form by a deserialiser.","NOTE\tThe deserialiser does not necessarily produce a stream of 10-bit symbols because the boundary of the symbols is not known by the deserialiser. One, two or four sets of 10-bit parallel data are provided by the deserialiser, depending upon the implementation.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.4.3.2c","Permission","ECSS-E-ST-50-11_1410273",1,"Created","If a particular SerDes requires different AC coupling capacitors, values outside the 100 nF to 200 nF range may be used."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.4.3.2j","Permission","ECSS-E-ST-50-11_1410282",1,"Created","When operating between 3,125 Gbit/s and 6,125 Gbit/s and the receiver has a lower input threshold voltage, the far-end value of A1 may be 50 mV.","NOTE\tThis allows greater distances to be covered using electrical media, when the receiver is capable of detecting smaller signals.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.4.3.3p","Requirement","ECSS-E-ST-50-11_1410308",1,"Created","The line receiver shall be operational when the line receiver enable signal is asserted."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.4.4.3.4a","Requirement","ECSS-E-ST-50-11_1410325",1,"Created","One male two-way connector and one female two-way connector conforming to clause 5.4.4.3.1 shall be used on flight connector savers."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.4.4.4.4b","Requirement","ECSS-E-ST-50-11_1410339",1,"Created","Type-B flight cable assemblies shall carry one or more lanes."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.4.4.5.4c","Requirement","ECSS-E-ST-50-11_1410357",1,"Created","The other end of the EGSE to flight adaptor cable assembly shall be terminated by a female 2-way connector conforming to clause 5.4.4.3.1."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.4.4.6.4i","Recommendation","ECSS-E-ST-50-11_1410379",1,"Created","The lengths of the signal wires used in the Type-D EGSE cable assembly should be matched to within ±2 mm."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.4.5.2j","Requirement","ECSS-E-ST-50-11_1410392",1,"Created","A transmitter operating over the 1 Gbit/s to 10 Gbit/s range shall comply with 10GBASE-SR jitter and eye-mask margin at 10,3125 Gbit/s as specified in IEEE802.3 Clause 52.5."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.4.6.1.2b","Requirement","ECSS-E-ST-50-11_1410410",1,"Created","The minimum quality level shall be IEC 60793-2-10 A1a.2:2015.","NOTE\tThese correspond to OM3 respectively. This is needed to achieve 10 Gbit/s over a link length of 300 meters (IEEE802.3:2012 Clause 52.5). Optical Multi-mode (OM) describes the modal bandwidth of the fibre by quantifying the modal dispersion characteristics of the optical fibre.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.4.6.2.1a","Requirement","ECSS-E-ST-50-11_1410421",1,"Created","A specific Type-B flight fibre optic medium shall be referred to by a unique descriptive name based on the type of insert and connector used in the following format: SpFi-TypeB-Insert-Connector, where Insert is the type of insert and Connector is a unique name for the type of connector and its specific contact allocation.","NOTE\t1\tFor example, a Type-B flight fibre optic medium using MT inserts in a 38999 connector with a specific contact allocation (D) is given the name SpFi-TypeB-MT-38999D.\nNOTE\t2\tThe Type-B fibre optic medium is intended to be a generic specification of a cable assembly without defining the insert or connector body to be used.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.4.6.3.2b","Requirement","ECSS-E-ST-50-11_1410442",1,"Created","When more than one lane is provided in an active optical cable assembly, it shall provide one set of the signals listed in Table 5-32 for each lane."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.5.1h","Requirement","ECSS-E-ST-50-11_1410459",1,"Created","The Lane layer shall report far-end capability information received in the INIT3 Capability field to the Data Link or Multi-Lane layer."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.5.2.3c","Requirement","ECSS-E-ST-50-11_1410473",1,"Created","For a single lane link FarEndActive shall be de-asserted."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.5.2.7b","Requirement","ECSS-E-ST-50-11_1410488",1,"Created","When in the Started state the Lane Initialisation state machine shall initiate the following actions:\n1.\tOn entry to the state, start an initialisation timeout timer, set to the time needed to transmit 5000 words.\n2.\tWhen RxOnly is not asserted, enable the transmitter driver.\n3.\tWhen TxOnly is not asserted, enable the receiver and CDR.\n4.\tSend INIT1 control words.\n5.\tReceive Lane layer control words, LLCW.","NOTE\tThe time to transmit 5000 words allows plenty of time for the receive clock-data recovery at the far-end of the lane to lock onto the transmitted signal, a response to be generated and returned to the near-end.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.5.2.8d","Recommendation","ECSS-E-ST-50-11_1410496",1,"Created","When in the InvertRxPolarity state and TxOnly is asserted, the Lane Initialisation state machine should disable the receiver and CDR.","NOTE\tThis requirement has been added for symmetry with the other states, but the InvertRxPolarity state cannot be reached when TxOnly is asserted, as nothing can be received.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.5.2.12d","Recommendation","ECSS-E-ST-50-11_1410518",1,"Created","When in the PrepareStandby state and TxOnly is asserted, the Lane Initialisation state machine should disable the receiver and CDR."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.5.4b","Requirement","ECSS-E-ST-50-11_1410531",1,"Created","When received, IDLE control words shall be discarded when they are read out of the receive elastic buffer."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.5.7f","Requirement","ECSS-E-ST-50-11_1410548",1,"Created","On word synchronisation, the first word shall comprise a comma control symbol in the least significant symbol position, together with the following three symbols."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.5.8.4a","Requirement","ECSS-E-ST-50-11_1410562",1,"Created","The Ready state shall be entered on the following condition:\n1.\tFrom the CheckSync state, when all symbols within a word are valid."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.5.8.4b","Requirement","ECSS-E-ST-50-11_1410563",1,"Created","When in the Ready state the Receiver Synchronisation state machine shall initiate the following action:\n1.\tReceive symbols."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.6.1n","Requirement","ECSS-E-ST-50-11_1410578",1,"Created","The Multi-Lane layer shall pass near-end capability control information to the Lane layer."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.6.4.3a","Requirement","ECSS-E-ST-50-11_1410603",1,"Created","A data word from a broadcast frame shall be replicated and sent over all data-sending lanes in the same sending row.","NOTE\tThis means that broadcast messages in a multi-lane system occupy L times the bandwidth that they occupy in a single lane configuration, where L is the number of data-sending lanes.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.6.4.5d","Permission","ECSS-E-ST-50-11_1410608",1,"Created","An implementation may send IDLE control words from active lanes provided they are sent over all active lanes simultaneously.","NOTE\tA complete row of IDLE control words is then sent.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.6.6.4g","Requirement","ECSS-E-ST-50-11_1410634",1,"Created","When the row is fully aligned and the ALIGN control words have been read, each following row contains aligned data and control words and each row shall be read, until a misalignment condition occurs and the Alignment state machine enters the Not Ready state.","NOTE\t1\tSee clause 5.6.7 for the specification of the Alignment state machine.\nNOTE\t2\tThe Alignment of a row is illustrated in Figure 5-36.\nNOTE\t3\tThe misalignment condition is specified in requirement 5.6.7.1c.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.6.7.1b","Requirement","ECSS-E-ST-50-11_1410638",1,"Created","The Aligned condition shall arise when all of the following conditions occur:\n1.\tAll lanes are aligned.\n2.\tThe far-end lanes in the active state are the same as the near-end lanes in the active state.","NOTE\tLane alignment is specified in requirement 5.6.6.4f.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.6.9.1b","Requirement","ECSS-E-ST-50-11_1410653",1,"Created","The ACTIVE control word shall be sent by all bi-directional and transmit only lanes. ","NOTE\tThe ACTIVE control word is also used to indicate when an RxOnly lane has detected an error and exited the Active state so that the other end of the lane, that is a TxOnly lane, is notified and reset.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.6.10h","Requirement","ECSS-E-ST-50-11_1410671",1,"Created","Hot redundant lanes shall have higher lane numbers than active lanes that are not hot redundant. "]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.7.1h","Requirement","ECSS-E-ST-50-11_1410683",1,"Created","The Data Link layer shall pass near-end capability control information to the Multi-Lane or Lane layer."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.7.2.3d","Requirement","ECSS-E-ST-50-11_1410706",1,"Created","When Link Reset is asserted, the following actions shall take place:\n1.\tAll input virtual channel buffers are flushed.\n2.\tIf the last character read from an input virtual channel buffer was not an EOP, EEP or Fill character, an EEP is the next character read from the input virtual channel buffer.","NOTE\tThis is equivalent to SpaceWire error handling, which uses the EEP to indicate at the receiver side that the link was disconnected and that the last packet provided was incomplete and in error.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.7.3.1g","Requirement","ECSS-E-ST-50-11_1410713",1,"Created","When an FCT is received for a particular virtual channel, M×64 shall be added to the FCT credit counter for that virtual channel, where M is the value of the Multiplier field in the FCT plus 1.","NOTE\tThe FCT indicates that the virtual channel buffer at the far-end of the link is able to accept another M×64 data words, see clause 5.3.5.2.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.7.4.2b","Permission","ECSS-E-ST-50-11_1410728",1,"Created","When hardware resources are extremely limited and there are no more than two virtual channels in a link, bandwidth reservation or scheduled QoS may be not supported.","NOTE\tThis limits the usefulness and interoperability of the device and means that babbling node protection is not provided.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.7.4.4e","Requirement","ECSS-E-ST-50-11_1410743",1,"Created","The precedence of a virtual channel shall be determined by its quality of service parameters and its bandwidth credit."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.7.4.5n","Requirement","ECSS-E-ST-50-11_1410758",1,"Created","The Minimum Bandwidth Credit Threshold shall be set at approximately 90 % of the value of the Negative Bandwidth Credit Limit."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.7.5g","Requirement","ECSS-E-ST-50-11_1410778",1,"Created","The Broadcast Bandwidth Credit Counter shall saturate at the Broadcast Bandwidth Credit Limit.","NOTE\tTherefore, when the Broadcast Bandwidth Credit exceeds the Broadcast Bandwidth Credit Limit, it is set to the value of the Broadcast Bandwidth Credit Limit.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.7.6.2.1c","Requirement","ECSS-E-ST-50-11_1410788",1,"Created","The seed for the scrambler shall be 0xFFFF.","NOTE\t0xFFFF results in all flip-flops in the random number generator being set to one. \n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.7.6.2.3e","Requirement","ECSS-E-ST-50-11_1410799",1,"Created","The initial seed value 0xFFFF shall be used to calculate the first idle word after link reset. ","NOTE\tAfter link reset, the first idle frame contains the values specified in Figure 5-43.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.7.6.3.2e","Requirement","ECSS-E-ST-50-11_1410817",1,"Created","The Receive Sequence Counter shall be cleared to zero on link reset of the SpaceFibre port."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.7.6.4e","Requirement","ECSS-E-ST-50-11_1410833",1,"Created","When the data in the frame is scrambled, the CRC shall be calculated using the scrambled data."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.7.6.6b","Requirement","ECSS-E-ST-50-11_1410850",1,"Created","The Sequence Number field in the start of idle frame shall be set to the current value of the Transmit Sequence Number, including the polarity flag.","NOTE\tAfter a link reset this counter is set to zero so if an idle frame is the first frame sent after link reset, its Sequence Number field is zero. If a data frame, FCT, or broadcast frame is the first frame sent after a link reset its Sequence Number field is one.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.7.7.1e","Requirement","ECSS-E-ST-50-11_1410862",1,"Created","When the contents of the error recovery buffer are resent, the broadcast frames shall always be sent before FCT and data frames, even if the broadcast frames were not sent before the NACK was received. ","NOTE\tThe frame precedence specified in clause 5.3.10 prevails.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.7.7.1n","Requirement","ECSS-E-ST-50-11_1410871",1,"Created","The error recovery buffer shall be considered as full when there is insufficient space in the buffer to store either an FCT, broadcast frame or all or part of a data frame."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.7.7.2.4a","Requirement","ECSS-E-ST-50-11_1410892",1,"Created","When a NACK is received it shall be checked for errors using its CRC."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.7.7.3.5b","Requirement","ECSS-E-ST-50-11_1410908",1,"Created","When in the Error Negative state, the Receive Polarity Flag shall be negative.","NOTE\tNACKs are therefore sent with positive Sequence Numbers.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.7.8.5b","Requirement","ECSS-E-ST-50-11_1410922",1,"Created","When in the RxBroadcast&DataFrame state the Data Word Identification state machine shall initiate the following actions:\n1.\tIndicate that data words being received belong to a broadcast frame.\n2.\tCount the number of data words being received in the broadcast frame."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.7.9.4b","Requirement","ECSS-E-ST-50-11_1410937",1,"Created","When in the Check Far-End Reset state the Link Reset state machine shall initiate the following actions:\n1.\tPass Lane Capability information to the Lane layer or Multi-Lane layer with the INIT3LinkResetFlag field set to 1."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.7.10b","Requirement","ECSS-E-ST-50-11_1410943",1,"Created","When link reset is asserted, the following actions shall take place:\n1.\tStop passing the current data frame or broadcast frame to the Lane or Multi-Lane layer.\n2.\tSet the Broadcast Bandwidth Credit Counter to zero as per requirement 5.7.5d.\n3.\tSet the initial seed for the PRBS generator to 0xFFFF and use this value to calculate the first idle word after link reset as per requirements 5.7.6.2.3d and 5.7.6.2.3e.\n4.\tClear the Transmit Sequence Counter to zero as per requirement 5.7.6.3.1d.\n5.\tClear the Transmit Polarity Flag to zero as per requirement 5.7.6.3.1e.\n6.\tClear the Receive Sequence Counter to zero as per requirement 5.7.6.3.2e.\n7.\tClear the Receive Polarity Flag to zero as per requirement 5.7.6.3.2f.\n8.\tEmpty the error recovery buffer as per requirement 5.7.7.1h.\n9.\tMove the Data Word Identification state machine to the RxNothing state as per requirement 5.7.8.2a.1.\n10.\tMove the Link Reset state machine to the Near-End Reset state as per requirement 5.7.9.3a.2."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.8.3b","Requirement","ECSS-E-ST-50-11_1410967",1,"Created","Two or more applications shall be interconnected and communicate via a virtual network."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.8.3q","Requirement","ECSS-E-ST-50-11_1410982",1,"Created","A virtual network shall comprise one virtual channel on each of the links it uses in a SpaceFibre network.","NOTE\tThe virtual channels on the links used by the virtual network are each a part of the virtual network.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.8.4a","Requirement","ECSS-E-ST-50-11_1410994",1,"Created","A link shall connect two ports of the same type together."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.8.8.1a","Requirement","ECSS-E-ST-50-11_1411012",1,"Created","A SpaceFibre routing switch shall forward a packet, arriving at one port, towards its needed destination, through another port or, when self-addressing is enabled, back through the same port as determined by the first data character of the packet and the contents of the routing table.","NOTE\tA packet can be forwarded through two or more ports when packet multicast is being used, see clause 5.8.11.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.8.8.1r","Requirement","ECSS-E-ST-50-11_1411029",1,"Created","A routing switch configuration port shall be accessed using path addressing only. "]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.8.8.3e","Requirement","ECSS-E-ST-50-11_1411043",1,"Created","If the output virtual channel is not able to accept more N-Chars and Fills, the input virtual channel shall hold them until the output virtual channel becomes ready to accept more N-Chars and Fills."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.8.9.1a","Requirement","ECSS-E-ST-50-11_1411058",1,"Created","A path address shall describe the path through the SpaceFibre network from the source of the packet to its destination.","NOTE\tTable 5-35 summarises the function of each type of address.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.8.9.2c","Requirement","ECSS-E-ST-50-11_1411067",1,"Created","When a SpaceFibre packet arrives at a routing switch and the leading data character is in the range 32 to 255, the leading data character shall be used as an index into a routing table in the routing switch to determine which port the packet is forwarded through.","NOTE\tFor example, a leading data character with a value of 49 results in entry 49 of the routing table specifying the output port that the packet is forwarded through. If entry 49 contains the value 7, the packet is forwarded through port 7.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.8.12.1a","Recommendation","ECSS-E-ST-50-11_1411088",1,"Created","256 broadcast channels should be supported by each SpaceFibre router."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.8.13d","Requirement","ECSS-E-ST-50-11_1411102",1,"Created","An end-point shall provide the means by which an application is able to interface to a virtual channel in a port and send and receive SpaceFibre packets over a network."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.9.2d","Requirement","ECSS-E-ST-50-11_1411118",1,"Created","Only network managers shall be permitted to be RMAP initiators on virtual network VN0.","NOTE\tSince only VN0 is used for network configuration, control and monitoring and only network managers can be RMAP initiators on VN0, this prevents any other node from inadvertently accessing the configuration, control and monitoring space of the routing switches and nodes in a SpaceFibre network.\n"]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","5.9.3a","Requirement","ECSS-E-ST-50-11_1411119",1,"Created","Configuration parameters shall be readable and writable via the management interface."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","6.2.2.2.4a","Requirement","ECSS-E-ST-50-11_1411135",1,"Created","On receipt of the SEND_PACKET.request primitive the SpaceFibre node receiving the request shall send the SpaceFibre packet over the SpaceFibre network using the specified virtual network."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","6.3.2.1a","Requirement","ECSS-E-ST-50-11_1411150",1,"Created","The service primitives that shall be associated with the Virtual Channel service are:\n1.\tTX_N-CHAR.request.\n2.\tRX_N-CHAR.indication."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","6.3.4.2.4a","Requirement","ECSS-E-ST-50-11_1411172",1,"Created","On receipt of the SCHEDULE.request primitive the Data Link layer shall use the time-slot information to end the previous time-slot and start the next one."]
["ECSS-E-ST-50-11C","ECSS - Current v1.0","6.4.2.3.2a","Requirement","ECSS-E-ST-50-11_1411180",1,"Created","The RX_10BITS.indication primitive shall have the following parameters: \n1.\tRX_10BITS.indication (10-bits)."]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.2.2e","Requirement","ECSS-E-ST-50-12_1420006",1,"Created","The SpaceWire Network layer shall use the services of the SpaceWire Data Link Layer."]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.2.3c","Requirement","ECSS-E-ST-50-12_1420009",1,"Created","The Data Link layer shall be responsible for establishing communications across the SpaceWire link, for controlling the flow of information over the link, for sending and receiving N-Chars, for sending and receiving broadcast codes and for re-establishing communications across the link after errors that occur over the link."]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.2.8c","Requirement","ECSS-E-ST-50-12_1420024",1,"Created","A SpaceWire Port shall incorporate a receive FIFO (RX FIFO) which stores received N-Chars until they can be read by the application via the SpaceWire port interface."]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.3.2.5e","Recommendation","ECSS-E-ST-50-12_1420046",1,"Created","The values calculated in 5.3.2.5d should be rounded in accordance with Table 5-4.","NOTE\tThe resulting insertion loss values in Table 5-4 from 1 up to 500 MHz concern the cable only. The additional losses due to the connectors of a SpaceWire cable assembly are not taken into account. The values in Table 5-4 have been rounded.\n"]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.3.3.2f","Recommendation","ECSS-E-ST-50-12_1420060",1,"Created","The connector with female contacts should include a conductive gasket for EMI improvement."]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.3.4.2b","Requirement","ECSS-E-ST-50-12_1420086",1,"Created","The maximum permitted inter-pair skew of a cable assembly shall be the maximum inter-pair skew of the cable, as defined in 5.3.2.4, plus 0.07 ns.","NOTE\tThe value 0,07 ns covers the skew in the connectors at both ends of the cable assembly.\n"]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.3.4.3.2c","Requirement","ECSS-E-ST-50-12_1420094",1,"Created","Pin 3 of the connector shall be left unconnected."]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.3.5.1a","Requirement","ECSS-E-ST-50-12_1420111",1,"Created","When using LVDS signals, the PCB tracks shall be differential tracks with a differential impedance of 100 Ohm ± 10 Ohm."]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.3.6.2.2c","Requirement","ECSS-E-ST-50-12_1420128",1,"Created","When terminated, for measurement purposes, by a 100 Ohm ± 1 Ohm termination resistor, the two outputs of the LVDS line driver (Out+ and Out-) shall have amplitude, VOUTp-PK or VOUTn-PK, of 124 mV to 227 mV, and a differential amplitude, of VDIFF-PK, of 247 mV to 454 mV, as illustrated in Figure 5-7.","NOTE\t1\tFigure 4 of TIA-644-A includes two 3,74 kOhm resistors in the test circuitry which simulate multiple line receivers connected to the line driver. These are not necessary when testing SpaceWire LVDS because the SpaceWire link is point-to-point NOT multi-drop.\nNOTE\t2\tA higher value of VDIFF-PK, within the specified range, allows longer cable lengths, see clause 5.3.6.2.3.\n"]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.3.6.2.3f","Requirement","ECSS-E-ST-50-12_1420144",1,"Created","The line receiver shall maintain correct operation for differential input voltages of up to 600 mV magnitude.","NOTE\tThis corresponds to the maximum permitted receiver differential signal in clause 4.2.4 of TIA-644-A.\n"]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.3.7.2e","Requirement","ECSS-E-ST-50-12_1420165",1,"Created","The unit and cable assembly suppliers shall provide designs that are compliant to the specified values of data and strobe skew and jitter for the unit and cable assembly respectively."]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.3.7.2m","Requirement","ECSS-E-ST-50-12_1420173",1,"Created","The maximum operating frequency of the SpaceWire link shall be less than the inverse of the minimum bit unit interval, TUIMIN.","NOTE\t1\tFigure 5-10 illustrates the effect of skew and jitter on the Data and Strobe signals, where the parameters are as follows:\n·\ttskew       is the skew between the Data and Strobe signals.\n·\ttjitter\tis the jitter on the Data or Strobe signal. tjitter data = tjitter strobe since they follow identical signal paths (as close as possible).\n·\ttdclk\tis the delay in the receiver from the edge of the Data or Strobe signal, through the XOR operation which produces the clock signal, to the clocking in of the data in the input flip­flop. This can be regarded as the set­up time for the data input flip­flop from the edge of the Data or Strobe signal.\n·\tthold\tis the hold time for the Data signal after the clocking of the data into the input flip­flop.\n·\ttui\tis the unit interval or bit period. tui = 1/Fop, where Fop is the link operating data signalling rate.\n·\ttmargin\tis the available margin.\t \ntmargin = tui - (tskew + 2*tjitter + tdclk + thold).\nNOTE\t2\tThe tdclk and thold parameters can be combined into a minimum specification for the separation of consecutive edges on the Data and Strobe signals at the input to the decoder, tds = tdclk + thold. \n"]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.4.3.2c","Requirement","ECSS-E-ST-50-12_1420187",1,"Created","A flow control token (FCT) shall be encoded as a control symbol with the two-bit control type set to 0b00.","NOTE\tThe FCT is used in the data link layer to manage the flow of N-Chars over a SpaceWire link.\n"]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.4.5a","Requirement","ECSS-E-ST-50-12_1420208",1,"Created","The first bit of the first Null to be sent after the Transmitter Enabled flag is asserted shall be a parity bit, which is set to zero so that the first transition is on the Strobe line. ","NOTE\tThis results in the patterns shown in Figure 5-17 appearing when a link is started.\n"]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.4.10.3a","Requirement","ECSS-E-ST-50-12_1420224",1,"Created","The maximum data signal rate shall be the highest data signalling rate at which a SpaceWire link can operate taking into account signal attenuation, skew and jitter."]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.5.4a","Requirement","ECSS-E-ST-50-12_1420242",1,"Created","The flow of N-Chars across a link shall be controlled using flow control tokens sent from one end of the link (end A) to the other end (end B) to signify that end A is ready to receive some more data. "]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.5.4l","Requirement","ECSS-E-ST-50-12_1420253",1,"Created","The data link layer shall keep a credit count of the number of N-Chars it has asked for by passing FCTs to the encoding layer and has yet to receive from the encoding layer (receive credit count) as follows: \n1.\tIncrement the receive credit count by eight each time an FCT is passed to the encoding layer.\n2.\tDecrement the receive credit count by one each time an N­Char is received from the encoding layer."]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.5.6e","Requirement","ECSS-E-ST-50-12_1420263",1,"Created","When no broadcast code, FCT or N­Char is ready to be sent, a Null shall be sent to indicate that the link is still active.","NOTE\tThis prevents the disconnect detection mechanism from being triggered at the far end of the link.\n"]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.5.8.1a","Requirement","ECSS-E-ST-50-12_1420283",1,"Created","The recovery of the link from errors shall follow the behaviour described in the following clauses.","NOTE\tThe link error recovery behaviour is illustrated by way of a state diagram for a link error recovery state machine in Figure 5-20.\n"]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.6.3b","Requirement","ECSS-E-ST-50-12_1420298",1,"Created","A distributed interrupt code shall be a broadcast code with the broadcast code type set to 0b10.","NOTE\tThe specialisations of broadcast codes are illustrated in the UML diagram of Figure 5-22.\n"]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.6.4.5b","Requirement","ECSS-E-ST-50-12_1420314",1,"Created","If the received time-code has a value which is one more, modulo 64, than the value in the time-code register, the received time-code shall be valid."]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.6.5.2d","Requirement","ECSS-E-ST-50-12_1420328",1,"Created","An interrupt code shall be associated with one of 32 possible interrupts as determined by the value of the interrupt identifier in the interrupt code."]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.6.5.4c","Recommendation","ECSS-E-ST-50-12_1420335",1,"Created","When operating in interrupt mode, there should be a minimum interval between a node sending one interrupt code with a particular value and sending the next interrupt with that same value which is greater than the maximum propagation time of an interrupt code across the network.","NOTE\t1\tIf an interrupt is used in interrupt mode and the host system requests to send an interrupt too fast after the previous identical interrupt was sent, i.e. before the corresponding interrupt time-out timer in the routing switches has expired, the new interrupt code that the node sends is discarded by a router.\nNOTE\t2\tIf an interrupt is sent before the minimum interval, that interrupt can be discarded by a routing switch in the network. Since the same interrupt has already been sent, this is not necessarily a problem at the system level.\n"]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.6.5.6h","Recommendation","ECSS-E-ST-50-12_1420358",1,"Created","A node not supporting receipt of interrupt acknowledgements should discard any received interrupt acknowledgement codes."]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.6.6g","Requirement","ECSS-E-ST-50-12_1420373",1,"Created","An end-point that supports time-codes shall pass time-codes, received over the SpaceWire network via the port, to the host system."]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.6.8.2c","Requirement","ECSS-E-ST-50-12_1420386",1,"Created","A routing switch shall use the leading data character of a packet to determine the output port of the routing switch that the packet is forwarded through."]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.6.8.6a","Requirement","ECSS-E-ST-50-12_1420403",1,"Created","A routing switch shall be configurable to delete a logical address from the front of the packet (leading data character with a value in the range 32 to 255) before it is forwarded through that port."]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.6.8.7b","Requirement","ECSS-E-ST-50-12_1420407",1,"Created","If the allocated output port is able to accept the start of another packet, the input port shall be connected to the output port so that the packet arriving at the input port is forwarded through the output port. "]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.6.9b","Requirement","ECSS-E-ST-50-12_1420433",1,"Created","A SpaceWire routing switch shall provide the management parameters for each of its ports as detailed in the following clauses:\n1.\tClause 5.5.3 data link layer management parameters\n2.\tClause 5.4.9 encoding layer management parameters\n3.\tClause 5.3.8 physical layer management parameters"]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","5.7.4a","Requirement","ECSS-E-ST-50-12_1420448",1,"Created","The encoding layer management parameters detailed in clause 5.4.9 shall be incorporated in the SpaceWire Management Information Base."]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","6.1.1.3.2a","Requirement","ECSS-E-ST-50-12_1420458",1,"Created","The RECEIVE_PACKET.indication primitive shall have the following parameters: \n1.\tRECEIVE_PACKET.indication (End-point, SpaceWire Packet, EOP/EEP)."]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","6.1.3.3.4a","Requirement","ECSS-E-ST-50-12_1420478",1,"Created","The effect on receipt of the DISTRIBUTED_INTERRUPT.indication primitive by the SpaceWire user shall depend upon the application."]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","6.2.1.2.2a","Requirement","ECSS-E-ST-50-12_1420489",1,"Created","The SEND_NCHAR.request primitive shall have the following parameters:\n1.\tSEND_NCHAR.request (Port, N-Char)."]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","6.3.1.2.3a","Requirement","ECSS-E-ST-50-12_1420508",1,"Created","When the data link layer wants to send a character through its output port, it shall generate a TX_CHAR.request primitive to encode the character, serialise it and send it through its output port."]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","6.3.1.3.1a","Requirement","ECSS-E-ST-50-12_1420510",1,"Created","The TX_ENABLE.request primitive shall be used by the data link layer to request that the output port is enabled."]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","6.3.2.4.1a","Requirement","ECSS-E-ST-50-12_1420523",1,"Created","The function of the DISCONNECT.indication primitive shall be to indicate to the data link layer that the SpaceWire link is disconnected. "]
["ECSS-E-ST-50-12C Rev.1","ECSS - Current v1.0","6.4.1.2.3a","Requirement","ECSS-E-ST-50-12_1420538",1,"Created","When the encoding layer wants to drive the data and strobe signals over the physical medium, it shall generate a DS_TX.request primitive."]
["ECSS-E-ST-50-13C","ECSS - Current v1.0","5.3f","Permission","ECSS-E-ST-50-13_1010204",1,"Created","Optionally, non redundant data bus may be selected for specific applications. "]
["ECSS-E-ST-50-13C","ECSS - Current v1.0","5.5.2a","Requirement","ECSS-E-ST-50-13_1010014",1,"Created","For Table 5-1 and Table 5-2, the RT address shall be obtained by connecting straps between an RT address or RT Address Parity signal and a GND signal such that:\n    1. A logical “1” level is defined by an unconnected RT address signal.\n    2. A logical “0” level is defined by a strap between the RT address signal and a GND signal.\n        NOTE For the case of a 9-pole connector no specific address connector is specified."]
["ECSS-E-ST-50-13C","ECSS - Current v1.0","6.2.1.2.2b","Requirement","ECSS-E-ST-50-13_1010028",1,"Created","If mode code 8 is used, while the RT is being reset it shall not respond to any valid command."]
["ECSS-E-ST-50-13C","ECSS - Current v1.0","7.1.2a","Requirement","ECSS-E-ST-50-13_1010043",1,"Created","For TimeSynchronize primitive Table 7-2 shall apply."]
["ECSS-E-ST-50-13C","ECSS - Current v1.0","8.2.1.2c","Requirement","ECSS-E-ST-50-13_1010059",1,"Created","The RT shall reserve words 5 – 9 of its output buffer of subaddress 29 for the host application to store the latest latched value of the local On-Board Time counter in the same format as is used for the Time Message. "]
["ECSS-E-ST-50-13C","ECSS - Current v1.0","8.3.1.1g","Requirement","ECSS-E-ST-50-13_1010079",1,"Created","The BC shall indicate the start of a frame by sending Communication Frame Synchronization Messages in the format of Synchronize with Data Word mode commands, except when coinciding with the Time Synchronization Message where this message replaces the Communication Frame Synchronization Message."]
["ECSS-E-ST-50-13C","ECSS - Current v1.0","8.3.2.1c","Requirement","ECSS-E-ST-50-13_1010089",1,"Created","The BC shall indicate the start of a frame by sending Communication Frame Synchronization Messages in the format of Synchronize with Data Word mode commands."]
["ECSS-E-ST-50-13C","ECSS - Current v1.0","8.6.1.1f","Requirement","ECSS-E-ST-50-13_1010114",1,"Created","The Distribution Transfer Descriptor (DTD) shall be sent to the RT in SA 27R."]
["ECSS-E-ST-50-13C","ECSS - Current v1.0","8.6.1.1j","Requirement","ECSS-E-ST-50-13_1010118",1,"Created","If the Mode flag is ‘1’ the Distribution Data Block shall be \n    1. sent to the Receive SA of the destination RT as specified by the Distribution Transfer Descriptor, and \n    2. segmented into a number 1553 messages of maximum size, i.e. 32 words, with the first 64 bytes of the block sent to the selected SA, the next 64 bytes sent to the same SA etc. "]
["ECSS-E-ST-50-13C","ECSS - Current v1.0","8.6.2.1b","Requirement","ECSS-E-ST-50-13_1010134",1,"Created","The BC shall maintain, for each Remote Terminal Address using the protocol, an Acquisition Block Counter value of the last Acquisition Data Block received."]
["ECSS-E-ST-50-13C","ECSS - Current v1.0","8.6.2.2h","Permission","ECSS-E-ST-50-13_1010211",1,"Created","The last message (see requirement 8.6.2.2g), or a the single message if the data block contains 64 bytes or less, may be shorter and "]
["ECSS-E-ST-50-13C","ECSS - Current v1.0","8.7.2c","Requirement","ECSS-E-ST-50-13_1010164",1,"Created","When a RT_Health bit is set, it shall not be reset by the RT until reception of the terminal configuration command Reset_RT_Health."]
["ECSS-E-ST-50-14C","ECSS - Current v1.0","4.2.3.2b","Requirement","ECSS-E-ST-50-14_0940006",1,"Created","For pulse commands it shall be ensured that spurious commands are not emitted during power cycling that exceed activation limits for the receivers.\n    ","NOTE 1 For pulse commands, see Clause 7                                                 \nNOTE 2 This requirement does not specify the prevention of spurious pulses, but ensures either that:\n        · spurious pulses are below the threshold for the receiver, or\n        · the spurious pulse duration is short enough to not drive the load into activation (for example a relay coil or opto-coupler diode)."]
["ECSS-E-ST-50-14C","ECSS - Current v1.0","4.2.4.4a","Requirement","ECSS-E-ST-50-14_0940013",1,"Created","Under the condition (Receiver = OFF linked to Transmitter = ON of UNIT_1), whether powered or not, UNIT_2 receivers shall withstand any driver characteristics as described in Clauses 5 to 8."]
["ECSS-E-ST-50-14C","ECSS - Current v1.0","5.3.2b","Requirement","ECSS-E-ST-50-14_0940029",1,"Created","The resulting voltage shall be utilised to feed a dedicated analogue channel.\n    ","NOTE The objective of these requirements is that the receiver is able to directly interface with a passive thermistor:"]
["ECSS-E-ST-50-14C","ECSS - Current v1.0","6.1.2.2.1a","Requirement","ECSS-E-ST-50-14_0940043",1,"Created","The source circuit shall meet the characteristics specified in Table 6-1."]
["ECSS-E-ST-50-14C","ECSS - Current v1.0","7.1.2.6a","Requirement","ECSS-E-ST-50-14_0940058",1,"Created","The high power discrete pulse command source shall be referenced to source signal ground. "]
["ECSS-E-ST-50-14C","ECSS - Current v1.0","7.2.3.2a","Requirement","ECSS-E-ST-50-14_0940078",1,"Created","The receiver circuit shall meet the characteristics specified in Table 7-8."]
["ECSS-E-ST-50-14C","ECSS - Current v1.0","8.3.4.3b","Requirement","ECSS-E-ST-50-14_0940088",1,"Created","The DATA_CLK_OUT burst shall last 16 times the bit sampling pseudoperiod (tb) plus the optional extension of the clock gap between clock pulse 8 and 9 (tb8)."]
["ECSS-E-ST-50-14C","ECSS - Current v1.0","8.3.4.7f","Permission","ECSS-E-ST-50-14_0940170",1,"Created","When bit 15 of DATA_IN is reached, DATA_IN may be set to any value; \n    ","NOTE The reason is that the next value of DATA_IN is not important since the DATA_IN signal is not sampled after this."]
["ECSS-E-ST-50-14C","ECSS - Current v1.0","8.4.4.8d","Requirement","ECSS-E-ST-50-14_0940118",1,"Created","The DATA_OUT signal shall meet the data set-up and hold times as specified in Table 8-3. "]
["ECSS-E-ST-50-14C","ECSS - Current v1.0","8.7.5b","Requirement","ECSS-E-ST-50-14_0940133",1,"Created","The balanced differential pair specified in 8.7.5a shall \n    1. be driven by the core element, and \n    2. carry the GATE_READ signal."]
["ECSS-E-ST-50-15C","ECSS - Current v1.0","5.1.2c","Requirement","ECSS-E-ST-50-15_1270013",1,"Created","To minimize reflections, stub-line length shall not exceed one-third (1/3) of the network critical length.","NOTE\t1\tSee definition 3.2.16.\nNOTE\t2\tAdditional considerations and requirements are addressed in 5.4.3."]
["ECSS-E-ST-50-15C","ECSS - Current v1.0","5.2.2.2b","Requirement","ECSS-E-ST-50-15_1270026",1,"Created","Receptacles shall be equipped with male contacts."]
["ECSS-E-ST-50-15C","ECSS - Current v1.0","5.3.3.1a","Requirement","ECSS-E-ST-50-15_1270033",1,"Created","Transceivers shall withstand a voltage in the range between -10V and +15V on their bus pins w.r.t to chassis ground.","NOTE\t1\tThis requirement introduces a dedicated specification for ‘battery voltage’ as defined in ISO 11898-2:2003 that is relative to use of CAN in space equipment.\nNOTE\t2\tThe rationale behind this choice is that those numbers envelope possible performances from present and future ISO and RS-485 transceivers (see for example absolute maximum ratings in [37])."]
["ECSS-E-ST-50-15C","ECSS - Current v1.0","5.3.5a","Requirement","ECSS-E-ST-50-15_1270048",1,"Created","ISO11898-2:2003 and RS-485 devices shall never be used on the same bus. "]
["ECSS-E-ST-50-15C","ECSS - Current v1.0","5.6.2a","Requirement","ECSS-E-ST-50-15_1270062",1,"Created","The Data Link layer shall implement fault confinement, as specified in ISO 11898-2:2003 clause 7.6, Fault Confinement.","NOTE\t1\tThe ISO 11898-2:2003 document inherits fault confinement definitions from the Bosch specification, [3]. It is left to the system engineer as how best to utilize the fault containment mechanisms provided for in clause 7.6 of the ISO reference for system FDIR purposes.\nNOTE\t2\tThe ISO 11898-1:2003, specifies that only Bus Off and Normal Mode indications to be provided to the application. "]
["ECSS-E-ST-50-15C","ECSS - Current v1.0","6.6a","Requirement","ECSS-E-ST-50-15_1270075",1,"Created","Each device in the network shall be accompanied by a Device Configuration File in accordance with the CANopen standard as per CiA DS306 Version 1.3.0.","NOTE\tThe functions and properties of CANopen devices are largely described by objects and are managed in an object directory. The object directory is represented in electronic form by so-called EDS files. EDS files are a fixed component of standardization in the CANopen field (CiA DS306) and play a key role in configuring CANopen networks. The file format specified by CiA guarantees that device descriptions generated by tools of different software producers can be read and processed. All participants in the development of CANopen systems benefit from complete and correct EDS files for the CANopen devices available on the market."]
["ECSS-E-ST-50-15C","ECSS - Current v1.0","6.10g","Requirement","ECSS-E-ST-50-15_1270091",1,"Created","The Node-ID shall be configurable when the node is in a specific maintenance mode only."]
["ECSS-E-ST-50-15C","ECSS - Current v1.0","7.1.2d","Requirement","ECSS-E-ST-50-15_1270105",1,"Created","The Local SCET Get object shall allow reading the local time of the node via the CAN Network."]
["ECSS-E-ST-50-15C","ECSS - Current v1.0","7.2.2c","Requirement","ECSS-E-ST-50-15_1270122",1,"Created","The Time Consumers shall map the Local SCET Set or Local UTC Set objects to the Spacecraft Time PDO receive PDO."]
["ECSS-E-ST-50-15C","ECSS - Current v1.0","7.2.3k","Requirement","ECSS-E-ST-50-15_1270137",1,"Created","The value of the Local Time PDO shall correspond to the local time when the last preceding SYNC object was successfully received.","NOTE\t1\tThe detailed mechanisms for transmission of the Local Time PDOs are out of scope in this standard.\nNOTE\t2\tIt is left to the implementer to define if the sampling of the local time at the occurrence of the SYNC object are implemented in H/W or S/W in order to achieve the required accuracy. It is good practice that generic H/W implementations always provide the possibility to signal, e.g. by means of an interrupt, that the SYNC object has been successfully transmitted/received."]
["ECSS-E-ST-50-15C","ECSS - Current v1.0","8.3.2b","Requirement","ECSS-E-ST-50-15_1270150",1,"Created","When in the CANopen Pre-operational state, each slave node shall listen for an NMT message, alternatively on the two busses according to the toggling mechanism specified in clause 8.3.3.","NOTE\tThe nodes start-up procedure is illustrated in Figure 8-1. The start-up procedure ends with an entry to the bus selection process specified in clause 8.3.3."]
["ECSS-E-ST-50-15C","ECSS - Current v1.0","9.4.1c","Requirement","ECSS-E-ST-50-15_1270173",1,"Created","For unconfirmed command exchanges, the slave unit shall not answer to the command exchange."]
["ECSS-E-ST-50-15C","ECSS - Current v1.0","9.4.4c","Requirement","ECSS-E-ST-50-15_1270187",1,"Created","The PDO communication parameter object relative to a Data Transmission triggered by a Telemetry Request shall correspond to the structure and entries defined in Table 9-5 and Table 9-6."]
["ECSS-E-ST-50-15C","ECSS - Current v1.0","9.4.10d","Requirement","ECSS-E-ST-50-15_1270209",1,"Created","If forbidden objects exist in a device, their default values shall be set to the unused value."]
["ECSS-E-ST-50-15C","ECSS - Current v1.0","9.5a","Requirement","ECSS-E-ST-50-15_1270214",1,"Created","Free COB-ID (1921 to 2014 and 2032 to 2047) shall not be used.","NOTE\tTable 9-13 recalls the list of predefined set of objects."]
["ECSS-E-ST-50-16C","ECSS - Current v1.0","5.2.1b","Requirement","ECSS-E-ST-50-16_1490002",1,"Created","All Time-Triggered End-System shall be of either SM or SC type as specified in [SAE AS6802]."]
["ECSS-E-ST-50-16C","ECSS - Current v1.0","5.2.1c","Requirement","ECSS-E-ST-50-16_1490003",1,"Created","All Time-Triggered Switches shall be of either CM or SC type as specified in [SAE AS6802]."]
["ECSS-E-ST-50-16C","ECSS - Current v1.0","6.2.2e","Requirement","ECSS-E-ST-50-16_1490027",1,"Created","The Const. Field (5-Bit) of the source MAC address shall be set to “0 0000”.","NOTE\tAs illustrated in Figure 6-3.\n"]
["ECSS-E-ST-50-16C","ECSS - Current v1.0","6.2.3c","Requirement","ECSS-E-ST-50-16_1490034",1,"Created","PCF, TT, RC and BE traffic shall be sent according to their priority."]
["ECSS-E-ST-50-16C","ECSS - Current v1.0","6.2.5.2e","Requirement","ECSS-E-ST-50-16_1490049",1,"Created","The time-skew between the redundant instances of the TT frames shall be configurable."]
["ECSS-E-ST-50-16C","ECSS - Current v1.0","6.2.6k","Requirement","ECSS-E-ST-50-16_1490063",1,"Created","A PCF frame shall include the synchronization priority and synchronization domain as specified in [SAE AS6802] §4.6."]
["ECSS-E-ST-50-16C","ECSS - Current v1.0","7.2.3.2a","Requirement","ECSS-E-ST-50-16_1490082",1,"Created","A Switch shall associate each Time-Triggered frame it forwards with a SW_TT_TX_LENGTH, a SW_TT_TX_PERIOD, and a SW_TT_TX_PHASE. ","NOTE\tA scheduler for Time-Triggered frames typically takes the SW_TT_TX_LENGTH and SW_TT_TX_PERIOD values of all frames as an input and returns a value for SW_TT_TX_PHASE for each Time-Triggered frame as an output. \n\tSW_TT_TX_LENGTH is the allowed length of an Ethernet frame including IFG and preamble:\n·\tMinimum(SW_TT_TX_LENGTH) = IFG (12 bytes) + preamble (7 bytes) + start of frame delimiter (1 bytes) + frame (64 bytes)\n·\tMaximum(SW_TT_TX_LENGTH) = IFG (12 bytes) + preamble (7 bytes) + start of frame delimiter (1 bytes) + frame (1518 bytes)\n\tSW_TT_TX_PERIOD is the transmission period with which the Switch dispatches the respective Time-Triggered frame.\n\tSW_TT_TX_PHASE is a value given by: \n \n\twhere:\n\tSW_SCHEDULE_GRANULARITY is the granularity of the schedule\n\tK is a natural number such that SW_TT_TX_PHASE <= SW_TT_TX_PERIOD holds. \n"]
["ECSS-E-ST-50-16C","ECSS - Current v1.0","7.2.4.2a","Requirement","ECSS-E-ST-50-16_1490103",1,"Created","An End-System shall identify a frame for transmission as a Time-Triggered frame by a lookup in an internal table. ","NOTE\tThe intent of this requirement is to make clear that the End-System operates Time-Triggered communication on a per-frame basis. \n"]
["ECSS-E-ST-50-16C","ECSS - Current v1.0","7.2.4.2j","Requirement","ECSS-E-ST-50-16_1490112",1,"Created","An End-System shall specify a list ES_LIST_TT_TX_PERIOD of different ES_TT_TX_PERIOD it can support during operation. "]
["ECSS-E-ST-50-16C","ECSS - Current v1.0","7.3.1.3a","Requirement","ECSS-E-ST-50-16_1490130",1,"Created","The scheduling parameters of a Switch device shall be configured as defined in Table 7-10."]
["ECSS-E-ST-50-16C","ECSS - Current v1.0","7.5.8a","Recommendation","ECSS-E-ST-50-16_1490153",1,"Created","For each TT frames received by a Switch, the receive window, acceptance window, should be defined by a start time and an end time respecting the two formulas provided on Table 7-18."]
["ECSS-E-ST-50-16C","ECSS - Current v1.0","8.2.3a","Requirement","ECSS-E-ST-50-16_1490170",1,"Created","In transmission, the UDP packet structure shall be compliant with [RFC 768] with 5 fields defined as follow\n1.\tSource Port: 16 bits\n2.\tDestination Port: 16 bits\n3.\tLength: 16 bits\n4.\tChecksum: 16 bits\n5.\tUDP Payload: 1-8 Kbytes"]
["ECSS-E-ST-50-16C","ECSS - Current v1.0","8.3.2e","Recommendation","ECSS-E-ST-50-16_1490188",1,"Created","Each TFTP client and server should support the following configurable parameters: \n1.\tDefault Timeout: sets the packet timeout. \n2.\tRetry Count: sets the retry limit.","NOTE\tThe use of [RFC 2349] (TFTP Timeout Interval and Transfer Size Options) to define the Timeout as a negotiated parameter under the framework defined by [RFC 1782] (TFTP Option Extension) is not considered in this standard.\n"]
["ECSS-E-ST-50-16C","ECSS - Current v1.0","8.4.3.1h","Recommendation","ECSS-E-ST-50-16_1490199",1,"Created","In an End-System tteEsCfgSignature should containing the signature of the configuration file."]
["ECSS-E-ST-50-16C","ECSS - Current v1.0","8.4.3.2t","Recommendation","ECSS-E-ST-50-16_1490223",1,"Created","In reception, if the Switch receives a frame with a VL number not consistent with the port number it is received through, the tteSweEthPortNoLossUnknownVl counter of the relevant port entry should be incremented."]
["ECSS-E-ST-50-16C","ECSS - Current v1.0","8.4.4a","Recommendation","ECSS-E-ST-50-16_1490229",1,"Created","Each Switch of a TTEthernet network should provide a port for Spy mode. ","NOTE\tIt can be a port temporarily allocated (configurable) or a physically isolated port.\n"]
["ECSS-E-ST-50-16C","ECSS - Current v1.0","9.2.2c","Requirement","ECSS-E-ST-50-16_1490245",1,"Created","The network shall be configured and monitored using the same procedures that is applied to set the network in Flight configuration. ","NOTE\tThis includes the use of the foreseen services (TFTP, SNMP…).\n"]
["ECSS-E-ST-50-51C","ECSS - Current v1.0","5.2.5a","Requirement","ECSS-E-ST-50-51_1070013",1,"Created","Protocol Identifiers in the range 1 to 239 (0x01 to 0xEF) that shall be used are those listed in Table 5-1.\n    ","NOTE 1 The identifiers in Table 5-1 have been assigned by the SpaceWire working group. The protocols starting at number 1 and working upwards as defined in this standard document define the current set of approved SpaceWire protocols and their Protocol Identifiers. The protocols starting at 239 and working downwards are legacy protocols and are not covered by this standard document.\nNOTE 2 The reader is advised to consult the SpaceWire website (http://www.spacewire.esa.int) for the latest Table defining the Protocol Identifiers and Extended Protocol Identifier allocation. "]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.1.5a","Requirement","ECSS-E-ST-50-52_1080013",1,"Created","The Key field shall be an 8-bit field that contains a key which is matched by the target user application in order for the RMAP command to be authorised.\n    ","NOTE The Key is only used for command authorisation. It is not used for other purposes."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.1.14a","Requirement","ECSS-E-ST-50-52_1080034",1,"Created","The Mask field shall be a variable length field containing the mask in a read-modify-write command."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.2f","Requirement","ECSS-E-ST-50-52_1080043",1,"Created","If the value of the data length field is zero, then the Data CRC shall be 0x00.\n    ","NOTE Read commands and write replies have no Data CRC field."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.3.1.5.3a","Requirement","ECSS-E-ST-50-52_1080051",1,"Created","The Write/Read bit shall be set (1) for a write command."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.3.2.4a","Requirement","ECSS-E-ST-50-52_1080073",1,"Created","The Protocol Identifier field shall be as defined in clause 5.1.3."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.3.3.4.2a","Requirement","ECSS-E-ST-50-52_1080088",1,"Created","If an EEP or EOP is received before the complete header including header CRC has been received the target shall:\n    1. Discard the entire packet,\n    2. Not send a reply packet."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.3.3.5.4a","Requirement","ECSS-E-ST-50-52_1080106",1,"Created","If the command is not accepted by the target user application for any other reason, the target shall:\n    1. Discard the command packet,\n    2. Return a “RMAP command not implemented or not authorised” error as specified in clause 5.6 to the node specified in the Reply Address and Initiator Logical Address fields if a reply has been requested, Reply bit set (1)."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.3.3.6.7b","Recommendation","ECSS-E-ST-50-52_1080414",1,"Created","If the Verify-Data-Before-Write bit is set (1) in the command field of the header and if there is more data in the data field than specified in the Data Length field of the write command header, the target should update the error information to reflect “too much data” error if the target supports error information gathering."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.3.3.10a","Recommendation","ECSS-E-ST-50-52_1080421",1,"Created","If the write operation to memory fails, the target should stop writing to memory as soon as the memory error is detected."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.4.1.5.1a","Requirement","ECSS-E-ST-50-52_1080148",1,"Created","The Instruction field format shall be as defined in clause 5.1.4."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.4.1.12a","Requirement","ECSS-E-ST-50-52_1080163",1,"Created","The Data Length field format shall be as defined in clause 5.1.11.\n    ","NOTE This gives a maximum Data Length of 16 Megabytes - 1 in a single read command. If a single byte is being read this field is set to one. If set to zero then no bytes are read from memory which can be used as a test transaction depending upon the implementation."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.4.2.8a","Requirement","ECSS-E-ST-50-52_1080178",1,"Created","The Target Logical Address field shall be set to either of:\n    1. The value of the Target Logical Address field of the read command, see clause 5.3.1.3, or\n    2. A logical address of the target.\n        ","NOTE Normally these are the same."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.4.3.4.3a","Requirement","ECSS-E-ST-50-52_1080193",1,"Created","If an EEP is received immediately after the complete header including header CRC has been received the target shall:\n    1. Discard the entire packet,\n    2. Not send a reply packet."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.4.3.5.3a","Requirement","ECSS-E-ST-50-52_1080209",1,"Created","If the Target Logical Address is not a logical address recognised by the target user application, the target shall:\n    1. Discard the command packet,\n    2. Return an “invalid Target Logical Address” error as specified in clause 5.6 to the node specified in the Reply Address and Initiator Logical Address fields."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.4.3.10b","Recommendation","ECSS-E-ST-50-52_1080438",1,"Created","If the read memory operation memory fails, the target should update the error information to reflect the memory access error if the target supports error information gathering."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.5.1.5.3b","Requirement","ECSS-E-ST-50-52_1080238",1,"Created","The Verify-Data-Before-Write bit shall be set (1) for a read-modify-write command.\n    ","NOTE This is so that the data is verified before it is written to memory and also distinguishes a read-modify-write from a read command."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.5.1.10a","Requirement","ECSS-E-ST-50-52_1080246",1,"Created","The Extended Address field shall be as defined in clause 5.1.9."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.5.2.6b","Requirement","ECSS-E-ST-50-52_1080268",1,"Created","The Packet Type field shall be 0b00 to indicate that RMAP packet is a reply."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.5.2.14a","Requirement","ECSS-E-ST-50-52_1080281",1,"Created","The end of the Packet containing the read-modify-write reply shall be indicated by an EOP character."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.5.3.4.8a","Requirement","ECSS-E-ST-50-52_1080298",1,"Created","When checking the Header CRC indicates no error present in the header, the data and mask shall be buffered and checked using the Data CRC before command authorisation is requested."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.5.3.4.10b","Recommendation","ECSS-E-ST-50-52_1080449",1,"Created","When checking the Header CRC indicates no error present in the header and if the Data CRC is in error the target should update the error information to reflect the “invalid Data CRC” error if the target supports error information gathering."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.5.3.10a","Requirement","ECSS-E-ST-50-52_1080381",1,"Created","When the read-modify-write reply is received at the initiator (or other node specified by the Reply Address), successful completion of the read-modify-write request shall be indicated to the user application on that node (RMW Complete Confirmation)."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.5.3.10b","Requirement","ECSS-E-ST-50-52_1080328",1,"Created","The Transaction Identifier shall be used to relate the reply to the command that caused the reply.\n    ","NOTE It is the responsibility of the initiator user application to read the data in the read reply once it has been informed that the data has been received."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.8.2.1a","Requirement","ECSS-E-ST-50-52_1080385",1,"Created","An implementation of \"SpaceWire RMAP Target only\" shall conform to all requirements given in clause 5.7.1.3 and may claim such compliance by using the following conformance statement “This product conforms to the SpaceWire RMAP Target only specification of the ECSS SpaceWire Protocols Standard (ECSS-E-ST-50-52)”."]
["ECSS-E-ST-50-52C","ECSS - Current v1.0","5.8.2.4b","Requirement","ECSS-E-ST-50-52_1080358",1,"Created","The supplier of the RMAP equipment shall provide a table detailing the read characteristics of the RMAP implementation.\n    ","NOTE An example of the required table is given in Table 5-8."]
["ECSS-E-ST-50-53C","ECSS - Current v1.0","5.2.2.5a","Requirement","ECSS-E-ST-50-53_1090014",1,"Created","The CCSDS_PACKET_SEND.request primitive shall be used to transfer CCSDS Packets across the SpaceWire network along the route defined by the Target SpaceWire Address and Target Logical Address parameters."]
["ECSS-E-ST-50-53C","ECSS - Current v1.0","5.3.3b","Requirement","ECSS-E-ST-50-53_1090027",1,"Created","The Protocol Identifier field shall be set to the value 2 (0x02) which is the Protocol Identifier for the CCSDS Packet Encapsulation Protocol."]
["ECSS-E-ST-50-53C","ECSS - Current v1.0","5.5.2c","Requirement","ECSS-E-ST-50-53_1090043",1,"Created","If the Packet Length of the CCSDS Packet is greater than the maximum acceptable length, the following shall be done:\n    1. Reject the Send Request\n    2. Inform the initiator user application."]
["ECSS-E-ST-60-10C","ECSS - Current v1.0","4.2.3a","Requirement","ECSS-E-ST-60-10_1020014",1,"Created","If the total error is a linear combination of individual contributing errors, classified in one or several groups according to 4.2.2.2, the mean of the total error shall be computed using a linear sum over the means of all the individual contributing errors."]
["ECSS-E-ST-60-10C","ECSS - Current v1.0","5.2.1.2a","Requirement","ECSS-E-ST-60-10_1020021",1,"Created","An uncertainty domain shall be defined identifying the set of physical parameters of the system over which the stability property is going to be verified."]
["ECSS-E-ST-60-10C","ECSS - Current v1.0","5.2.5a","Requirement","ECSS-E-ST-60-10_1020035",1,"Created","Nominal stability margins are given by specifying values  ,  ,  , and   such that the following relations shall be met:\n1.\tThe gain margin is greater than  \n2.\tThe phase margin is greater than  \n3.\tThe modulus margin is greater than  \n4.\tThe peak sensitivity and complementary sensitivity functions is lower than  ."]
["ECSS-E-ST-60-20C Rev. 2","ECSS - Current v1.0","4.1.4.2a","Requirement","ECSS-E-ST-60-20_0920012",1,"Unchanged","A sensor with the autonomous star tracking capability shall have the minimum outputs:\n1.\tthe position of each star image with respect to a sensor-defined reference frame;\n2.\tthe Measurement date.","NOTE \tThis capability does not imply the stars to be explicitly identified by the unit. However, it does include the ability to maintain the identification of each star image once selected, to correctly update the co-ordinates of each image as it moves across the detector, and autonomously manage the set of star images being tracked.\n"]
["ECSS-E-ST-60-20C Rev. 2","ECSS - Current v1.0","4.1.8.1b","Requirement","ECSS-E-ST-60-20_0920023",1,"Informative Change","Any use of image compression (e.g. for transmission) shall be documented.","NOTE \t1\tThe definition of the capability is intended to exclude ‘lossy’ image compression, though such compression can be a useful option under certain circumstances.\nNOTE \t2\tImage compression is used for example for transmission.\n"]
["ECSS-E-ST-60-20C Rev. 2","ECSS - Current v1.0","4.4i","Requirement","ECSS-E-ST-60-20_0920160",1,"Created","Limitations as per requirement 4.4h shall be agreed upon between the supplier and the customer."]
["ECSS-E-ST-60-20C Rev. 2","ECSS - Current v1.0","5.2.4e","Requirement","ECSS-E-ST-60-20_0920165",1,"Created","The test inputs shall be in accordance with the required observability in terms of operational range and in terms of the test resolution. "]
["ECSS-E-ST-60-20C Rev. 2","ECSS - Current v1.0","5.4c","Requirement","ECSS-E-ST-60-20_0920050",2,"Normative Change","The supplier shall identify the worst case projection in BRF of the value defined in 5.4b. ","NOTE \tDifferent angular rates can be specified with associated required performance.\n"]
["ECSS-E-ST-60-20C Rev. 2","ECSS - Current v1.0","5.5.3.2a","Requirement","ECSS-E-ST-60-20_0920069",1,"Informative Change","Error sources that gradually change the alignment of the sensor Mechanical Reference Frame (MRF) and the sensor Boresight Reference Frame (BRF) from the start of the in-flight mission shall be included.","NOTE \t1\tE.g. “The thermal sensitivity to temperature of line of sight stability shall be less than 1 arcsec/Kelvin.”\nNOTE \t2\tRefer to the Annex G for the contributing error sources description.\n"]
["ECSS-E-ST-60-20C Rev. 2","ECSS - Current v1.0","5.5.5.3a","Requirement","ECSS-E-ST-60-20_0920082",1,"Unchanged","Contributing error sources shall be verified by on ground tests."]
["ECSS-E-ST-60-20C Rev. 2","ECSS - Current v1.0","5.6a","Requirement","ECSS-E-ST-60-20_0920098",1,"Unchanged","For star position measurements, the performance conditions of the ‘statistical ensemble’ shall be used to encompass the following conditions for BOL:\n1.\tworst-case star location in FOV;\n2.\tworst-case Star Magnitude within specified range."]
["ECSS-E-ST-60-20C Rev. 2","ECSS - Current v1.0","5.9.3a","Requirement","ECSS-E-ST-60-20_0920111",1,"Unchanged","The probabilities of attitude determination specification shall be verified by applying the general provisions in 5.2.2 and 5.2.3."]
["ECSS-E-ST-60-20C Rev. 2","ECSS - Current v1.0","5.10.3a","Requirement","ECSS-E-ST-60-20_0920124",1,"Unchanged","The performance shall be specified under the conditions given in 5.10.1."]
["ECSS-E-ST-60-20C Rev. 2","ECSS - Current v1.0","5.12b","Requirement","ECSS-E-ST-60-20_0920132",1,"Unchanged","The functional mathematical model shall be representative of the sensor actual temporal performances for realistic kinematic profiles."]
["ECSS-E-ST-60-20C Rev. 2","ECSS - Current v1.0","5.13.4a","Requirement","ECSS-E-ST-60-20_0920189",1,"Created","The orbit, the Space Radiation model to be used and the availability requirement shall be provided in order to specify the level of perturbation that is handled by the star tracker.","NOTE \t1\tThe orbit is a key element since it determines the protection provided, for instance in Earth vicinity, by the Van Allen belts. In interplanetary missions, the orbit is also key since the strength of the solar flare fluxes scales with square of the distance to the sun below 1 AU, as described in ECSS‐E‐ST‐10‐04 “Space environment”.\nNOTE \t2\tThe Space Radiation model generally used as a reference is CREME96 - October 1989 event.\n"]
["ECSS-E-ST-60-21C","ECSS - Current v1.0","4.2.1c","Requirement","ECSS-E-ST-60-21_1350003",1,"Created","The gyro shall perform a health-check at the end of the initialization phase."]
["ECSS-E-ST-60-21C","ECSS - Current v1.0","4.5.1a","Requirement","ECSS-E-ST-60-21_1350018",1,"Created","The gyro shall be capable to perform measurements together with the associated validity check and the sampling of housekeeping data at a frequency to be specified by the customer.","NOTE\tThe sampling frequency is between some Hz and some tens of Hz depending on the application.\n"]
["ECSS-E-ST-60-21C","ECSS - Current v1.0","4.7.2a","Requirement","ECSS-E-ST-60-21_1350037",1,"Created","The verification test shall be performed with a test set-up representative of the interface requirements specified by the customer"]
["ECSS-E-ST-60-21C","ECSS - Current v1.0","4.10.1b","Requirement","ECSS-E-ST-60-21_1350048",1,"Created","The use of the Test mode for the unit in-flight shall be specified if necessary."]
["ECSS-E-ST-60-21C","ECSS - Current v1.0","4.11.1c","Requirement","ECSS-E-ST-60-21_1350054",1,"Created","If using an anti-aliasing filter which can be disabled, performance shall be evaluated with and without the filter so that both raw and filtered outputs satisfy the performance requirements."]
["ECSS-E-ST-60-21C","ECSS - Current v1.0","5.2h","Requirement","ECSS-E-ST-60-21_1350078",1,"Created","The performance requirements verification shall be done with individual tests or by combined tests.","NOTE\tOne test serves the verification of several performance requirements.\n"]
["ECSS-E-ST-60-21C","ECSS - Current v1.0","5.4.2.2.3a","Requirement","ECSS-E-ST-60-21_1350093",1,"Created","The bias repeatability from switch-on to switch-on shall be specified by the customer denoting the performance type in terms of maximum, 1 sigma, 68% confidence level or peak to peak.","NOTE\tThe on and off durations are specified.\n"]
["ECSS-E-ST-60-21C","ECSS - Current v1.0","5.4.2.3.2a","Requirement","ECSS-E-ST-60-21_1350105",1,"Created","The duration of the test shall be long enough to obtain the required confidence level in the bias estimate."]
["ECSS-E-ST-60-21C","ECSS - Current v1.0","5.4.4.1b","Requirement","ECSS-E-ST-60-21_1350123",1,"Created","The statistical interpretation of the scale factor error shall be defined by the customer."]
["ECSS-E-ST-60-21C","ECSS - Current v1.0","5.4.4.3a","Requirement","ECSS-E-ST-60-21_1350140",1,"Created","The measurement of the scale factor error shall be performed via ground test with a motion table. "]
["ECSS-E-ST-60-21C","ECSS - Current v1.0","5.4.4.3n","Requirement","ECSS-E-ST-60-21_1350153",1,"Created","Scale factor errors verification shall not be done without verification of the measurement accuracy of the set‐up used for calibration."]
["ECSS-E-ST-60-21C","ECSS - Current v1.0","5.4.5.2.5a","Requirement","ECSS-E-ST-60-21_1350168",1,"Created","The absolute gyro axes, w.r.t. mechanical reference frame, alignment variation over operating temperature range shall be specified by the customer denoting the performance type in terms of maximum, 1 sigma, 68% confidence level or peak to peak."]
["ECSS-E-ST-60-21C","ECSS - Current v1.0","5.4.5.3e","Requirement","ECSS-E-ST-60-21_1350177",1,"Created","The alignment errors sensitivity shall be measured in stable environmental conditions and after internal stabilisation of the gyro consistent with the required accuracy of the alignment errors estimate."]
["ECSS-E-ST-60-21C","ECSS - Current v1.0","5.4.8.3a","Requirement","ECSS-E-ST-60-21_1350195",1,"Created","The warm-up performance requirements shall be verified by test."]
["ECSS-E-ST-60-21C","ECSS - Current v1.0","5.4.13.1a","Requirement","ECSS-E-ST-60-21_1350208",1,"Created","The performance of the stimulation function shall be specified.","NOTE\tThe stimulation function performance can be specified as follows: \n·\t“The stimuli resolution shall be better than 0,1 deg/h.”\n·\t“The stimuli scale factor error shall be better than 1 %.”\n"]
["ECSS-E-ST-60-21C","ECSS - Current v1.0","A.2.1<4>a","Requirement","ECSS-E-ST-60-21_1350222",1,"Created","The FMM description shall document the steps from the actual angular rate in inertial frame to the gyro outputs."]
["ECSS-E-ST-60-30C","ECSS - Current v1.0","5.1.1.7a","Requirement","ECSS-E-ST-60-30_1160008",1,"Created","The AOCS shall provide the capability for achieving orbit control manoeuvres specified by mission analysis.\n    ","NOTE Orbit control manoeuvres include the following cases: \n• initial orbit acquisition or transfer phase so as to reach the operational orbit,\n• orbit correction manoeuvres on-station for orbit maintenance, \n• orbit change on station for repositioning,\n• end-of-life orbit change for de-orbiting, transfer towards graveyard orbit or parking orbit."]
["ECSS-E-ST-60-30C","ECSS - Current v1.0","5.1.1.9c","Requirement","ECSS-E-ST-60-30_1160014",1,"Created","The capability shall be provided to inhibit or to force Auto and FDIR transitions by TC."]
["ECSS-E-ST-60-30C","ECSS - Current v1.0","5.1.1.14c","Recommendation","ECSS-E-ST-60-30_1160143",1,"Created","For inertia cross-products, one of the following usual conventions should be used :\n ,   ,   \nor: \n ,   ,   \n"]
["ECSS-E-ST-60-30C","ECSS - Current v1.0","5.2.2.2b","Requirement","ECSS-E-ST-60-30_1160049",1,"Created","Depending on the mission need, the AOCS shall provide TM for ground reconstruction of the spacecraft attitude and orbit.\n    ","NOTE 1 The ground reconstruction can be in real time or a posteriori.\nNOTE 2 Orbit reconstruction can also use data which are not transmitted from the satellite.\nNOTE 3 The ground processing can combine attitude and orbit measurements to compute geo-location products, for instance.\nNOTE 4 The volume and frequency of the attitude and orbit TM depend on the required accuracy of the reconstructed attitude and orbit, as well as the system constraints (such as communication with the ground and on-board storage capacity)."]
["ECSS-E-ST-60-30C","ECSS - Current v1.0","5.2.2.3b","Requirement","ECSS-E-ST-60-30_1160052",1,"Created","The AOCS shall provide the capability to download simultaneously nominal and redundant sensors data to the ground. \n    ","NOTE 1 Depending on the mission, a degradation of the nominal performance can be accepted while the redundant sensor is switched on.\nNOTE 2 This cannot be applied to low cost satellites without redundancy."]
["ECSS-E-ST-60-30C","ECSS - Current v1.0","5.3.3.1b","Requirement","ECSS-E-ST-60-30_1160070",1,"Created","The navigation function of the AOCS shall provide inputs to the ground for orbit estimation.\n    ","NOTE If the ground processing includes other data (payload data or ground-based measurements for instance), this requirement cannot be construed as AOCS as sole input provider."]
["ECSS-E-ST-60-30C","ECSS - Current v1.0","5.3.6e","Requirement","ECSS-E-ST-60-30_1160082",1,"Created","For a given duration of the mode of TBS days, the AOCS control of the safe mode shall not generate an orbit degradation greater than:\n    1. TBS m/s along the track,\n    2. TBS m/s along the cross track direction,\n    3. TBS m/s along the direction perpendicular to the orbit plane.\n        ","NOTE It is usually difficult to design a safe mode minimizing the orbit degradation on a specific direction, because of the great variety of attitude profiles, and the verification can be done only a posteriori through simulations. It is also possible to have a requirement on a maximum degradation on any axis."]
["ECSS-E-ST-60-30C","ECSS - Current v1.0","5.4.4d","Requirement","ECSS-E-ST-60-30_1160098",1,"Created","The AOCS design and performance verification shall include a robustness analysis covering the nominal variation range specified for the physical data and hardware performances.\n    ","NOTE Usual parameters include mass properties, sensor and actuators performances, environmental conditions, orbit uncertainties and drifts."]
["ECSS-E-ST-60-30C","ECSS - Current v1.0","A.2.1a","Requirement","ECSS-E-ST-60-30_1160121",1,"Created","The AOCS design definition file shall provide the reference frames and conventions."]
["ECSS-E-ST-60-30C","ECSS - Current v1.0","A.2.1g","Requirement","ECSS-E-ST-60-30_1160127",1,"Created","The AOCS design definition file shall provide commandability, observability and FDIR information:\n    1. Summary of the TM/TC\n    2. AOCS level Failure detection and reconfiguration"]
["ECSS-E-ST-70-01C","ECSS - Current v1.0","5.1a","Requirement","ECSS-E-ST-70-01_1060001",1,"Created","Each OBCP shall have a unique “OBCP Identifier”, which is assigned by the ground system."]
["ECSS-E-ST-70-01C","ECSS - Current v1.0","5.2.4a","Requirement","ECSS-E-ST-70-01_1060016",1,"Created","It shall be possible to declare variables of any data type, including their initialisation values."]
["ECSS-E-ST-70-01C","ECSS - Current v1.0","5.2.7a","Requirement","ECSS-E-ST-70-01_1060031",1,"Created","It shall be possible to include the following execution controls within an OBCP:\n    1. simple conditional branching (i.e. if … then … else …);\n    2. multiple conditional branching where the path taken is dependent on the value of a specified parameter (or variable);\n    3. repeated execution of a statement (or a group of statements) with the possibility of repeating the execution a specified number of times, repeating the execution indefinitely whilst a given condition holds true or repeating the execution until a given condition becomes true."]
["ECSS-E-ST-70-01C","ECSS - Current v1.0","5.2.9.3b","Requirement","ECSS-E-ST-70-01_1060052",1,"Created","It shall be possible to access events raised on-board together with their associated parameters."]
["ECSS-E-ST-70-01C","ECSS - Current v1.0","5.3.3b","Requirement","ECSS-E-ST-70-01_1060061",1,"Created","It shall be possible to generate a report containing the activity call tree of all OBCPs, i.e. a tree showing all calling and called activities."]
["ECSS-E-ST-70-01C","ECSS - Current v1.0","5.4.2.2a","Requirement","ECSS-E-ST-70-01_1060073",1,"Created","The following OBCP execution states shall be supported:\n    1. in store i.e. the OBCP is in the executable form, stored either on-board or on-ground.\n    2. in engine i.e. the OBCP is in an on-board memory accessible by the OBCP engine:\n        (a) inactive i.e. the OBCP is idle;\n        (b) active i.e. the OBCP is under control of the OBCP engine:\n            1. running i.e. the OBCP is executing;\n            2. held i.e. the OBCP execution has been placed on hold."]
["ECSS-E-ST-70-01C","ECSS - Current v1.0","5.4.4.2c","Requirement","ECSS-E-ST-70-01_1060091",1,"Created","The behaviour of the OBCP engine in the event of a reset of, or discontinuity in, the reference clock on which the wait services of the OBCP engine depend, shall be defined."]
["ECSS-E-ST-70-01C","ECSS - Current v1.0","5.4.4.5h","Requirement","ECSS-E-ST-70-01_1060106",1,"Created","The rules for the allocation and utilisation of available resources to concurrently executing OBAPs shall be defined.\n    NOTE This covers in particular the definition of a priority scheme for OBAP scheduling."]
["ECSS-E-ST-70-01C","ECSS - Current v1.0","6.2.1f","Requirement","ECSS-E-ST-70-01_1060124",1,"Created","The capabilities of the OBCP engine and the preparation environment shall be defined and frozen at the software PDR, see Figure 6-3.\n    NOTE The trade-off between implementation of one single OBCP engine or several OBCP engines is performed as part of the OBSW engineering process."]
["ECSS-E-ST-70-01C","ECSS - Current v1.0","6.3a","Requirement","ECSS-E-ST-70-01_1060136",1,"Created","The engineering process for OBOPs and for OBAPs shall be defined and documented."]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","4.5a","Requirement","ECSS-E-ST-70-11_1670005",1,"Created","No  telecommand executed at the wrong time or in the wrong configuration shall lead to the loss of the mission.","NOTE \tFor a mission­critical on-board function, this can be ensured by the provision of two independent telecommands, both to be executed (e.g. ARM and FIRE).\n"]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","4.7f","Requirement","ECSS-E-ST-70-11_1670026",1,"Created","No fault management function shall trigger on offline data generated by a unit operating in \"off-line\" mode.","NOTE \tOffline data is data not used by the on-board control or FDIR monitoring loops.\n"]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.3.1a","Requirement","ECSS-E-ST-70-11_1670036",1,"Created","Throughout all mission phases, engineering telemetry data shall be provided for the ground segment to determine the status, health and performance of the space segment subsystems and payloads and to monitor the execution of nominal and anticipated contingency operations, independently of telecommand history on-board actions or previous telemetry.","NOTE \tThis requirement covers the information to be telemetered for the purpose of both ground testing and in-flight operations.\n"]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.3.1u","Requirement","ECSS-E-ST-70-11_1670056",1,"Created","If a parameter is super-commutated in a telemetry source packet, then the parameter shall be sampled regularly in time.","NOTE \tA super‐commutated parameter is one that appears more than once in a packet.\n"]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.3.2a","Requirement","ECSS-E-ST-70-11_1670071",1,"Created","For anomaly investigation purposes, the capability shall be provided for the ground segment to select a set of housekeeping telemetry parameters to be sampled at a high rate."]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.4l","Requirement","ECSS-E-ST-70-11_1670087",1,"Created","It shall be possible to establish the original on-board sampling time of any space segment status telemetry parameter appearing in the telemetry source packets."]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.5.1b","Requirement","ECSS-E-ST-70-11_1670101",1,"Created","If a telecommand executes more than one action, these actions shall be strictly operationally related, such that they constitute a single logical on-board function.","NOTE \tTo comply with this requirement, a device telecommand cannot put a battery in trickle charge and at the same time switch on a heater, unless these operations are always strictly related.\n"]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.5.1i","Requirement","ECSS-E-ST-70-11_1670108",1,"Created","Redundancy switching at unit level shall not require changes in operational procedures / telecommands directed to the operational unit. ","NOTE \tThis allows previously loaded commands (e.g. mission timeline, OBCPs) to address the current operational unit. This implies a different method than that used for direct physical unit control.\n"]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.5.4d","Requirement","ECSS-E-ST-70-11_1670131",1,"Created","Verification telemetry shall be provided with a delay of less than <TC_VERIF_DELAY> with respect to the time of completion of the corresponding telecommand execution stage."]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.6.1g","Requirement","ECSS-E-ST-70-11_1670146",1,"Created","All modes shall be defined such that, for any logical unit used in this mode, any serviceable combination of physical units is possible.","NOTE \t1\tLogical unit refers to the role of the unit in the redundancy scheme (i.e. nominal or redundant).\nNOTE \t2\tServiceable means that is not necessary to consider configurations that do not make sense (e.g. operating only on one wheel).\n"]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.6.2d","Requirement","ECSS-E-ST-70-11_1670159",1,"Created","The reconfiguration of on­board units or the switching between on­board functions shall not affect the status, the configuration, or the proper operation of any other unrelated unit or function."]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.7.2k","Requirement","ECSS-E-ST-70-11_1670176",1,"Created","For autonomous functions used both in nominal and safe/survival space segment modes, ground shall have the capability to enable/disable the function independently for nominal and safe/survival modes.","NOTE \tThis includes FDIR functions.\n"]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.7.5.2b","Requirement","ECSS-E-ST-70-11_1670180",1,"Created","FDIR functions shall be implemented in a hierarchical manner in order to detect, isolate and recover failures at the lowest possible implementation level.","NOTE \t1\tFor example, FDIR handling on an on­board data bus implying retries and subsequent error mechanisms in case these retries are unsuccessful.\nNOTE \t2\tThis requirement can imply a staggered recovery scheme based on retry functions (see also clause 5.7.5.4).\n"]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.7.5.3i","Requirement","ECSS-E-ST-70-11_1670205",1,"Created","All units capable of performing self-checks shall report any detected failures."]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.7.5.6h","Requirement","ECSS-E-ST-70-11_1670221",1,"Created","The space segment shall support automatic transition from survival to safe mode."]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.7.5.6r","Requirement","ECSS-E-ST-70-11_1670231",1,"Created","No nominal operation shall require inhibition of the safe/survival mode nor a forced entry into safe/survival mode.","NOTE \tThis applies also to critical operations in the nominal timeline\n"]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.8.3f","Requirement","ECSS-E-ST-70-11_1670251",1,"Created","The capability shall be provided to persistently store updated memory content on-board, such that time-consuming memory re­loads from the ground following memory switch on are avoided.","NOTE \tFor example, using EEPROM.\n"]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.8.6c","Requirement","ECSS-E-ST-70-11_1670266",1,"Created","The capability shall be provided to perform any action affecting on-board monitoring definitions even when the on-board monitoring function is in a disabled state."]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.8.9d","Requirement","ECSS-E-ST-70-11_1670280",1,"Created","On­board control procedures shall have access to any engineering telemetry parameter available to the ground."]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.9.1k","Requirement","ECSS-E-ST-70-11_1670296",1,"Created","Whenever an unexpected arithmetic overflow condition is detected, an event report shall be generated."]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.9.1r","Requirement","ECSS-E-ST-70-11_1670303",1,"Created","The space segment shall be robust against complete loss of the operational context.","NOTE \tThis implies the existence of an autonomous mode that does not rely on the operational context (e.g. survival mode).\n"]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.9.1z","Requirement","ECSS-E-ST-70-11_1670311",1,"Created","Each on-board application software shall save, in non-volatile memory, and report to ground, data relating to the self-test executed by the boot software.","NOTE \tSuch reports are typically referred to as boot reports.\n"]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.9.3p","Requirement","ECSS-E-ST-70-11_1670338",1,"Created","The space segment shall avoid the loss of telemetry upon changing telemetry bit rate.","NOTE \tThis can be achieved by sending a synchronisation stream (i.e. idle frames) of sufficient duration to allow receivers at the ground station to re-synchronise.\n"]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.9.3r","Requirement","ECSS-E-ST-70-11_1670340",1,"Created","The space segment design shall not place a constraint on the achievable daily duration for ground communication."]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.9.4s","Requirement","ECSS-E-ST-70-11_1670359",1,"Created","If authorised by ground, reaction wheel offloading shall be autonomously calculated and executed onboard and implemented to minimise mission interruption."]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.9.6b","Requirement","ECSS-E-ST-70-11_1670370",1,"Created","Except for loops that are driven by thermostats, the capability shall be provided to adjust the temperature control thresholds of each thermal control loop by ground command."]
["ECSS-E-ST-70-11C Rev.1","ECSS - Current v1.0","5.9.8f","Requirement","ECSS-E-ST-70-11_1670385",1,"Created","The space segment shall provide the capability for ground to verify the completeness and correctness of each file transfer transaction."]
["ECSS-E-ST-70-31C","ECSS - Current v1.0","6.2.1a","Requirement","ECSS-E-ST-70-31_0270012",1,"Created","It shall be possible to include comments at any location in the script of a complex data type."]
["ECSS-E-ST-70-31C","ECSS - Current v1.0","6.2.3c","Requirement","ECSS-E-ST-70-31_0270017",1,"Created","Mathematical, time and string functions shall be supported."]
["ECSS-E-ST-70-31C","ECSS - Current v1.0","6.2.6b","Requirement","ECSS-E-ST-70-31_0270033",1,"Created","It shall be possible to synthesize a parameter or one or more components of a compound parameter."]
["ECSS-E-ST-70-31C","ECSS - Current v1.0","6.2.6p","Requirement","ECSS-E-ST-70-31_0270047",1,"Created","The capability to mix compatible units freely within an expression shall be supported"]
["ECSS-E-ST-70-31C","ECSS - Current v1.0","6.3.2.8a","Requirement","ECSS-E-ST-70-31_0270062",1,"Created","For each system element, activity, reporting data and event of the SSM, the data specified in Table 6-7 shall be provided."]
["ECSS-E-ST-70-31C","ECSS - Current v1.0","6.5.3.2a","Requirement","ECSS-E-ST-70-31_0270084",1,"Created","For system elements of type “system” that utilise ECSS-E-ST-70-41, the additional data specified in Table 6-12 shall be provided."]
["ECSS-E-ST-70-31C","ECSS - Current v1.0","6.5.5.3.1a","Requirement","ECSS-E-ST-70-31_0270092",1,"Created","For the definition of the tailoring of the device command distribution service, the additional data shown in Table 6-20 shall be provided."]
["ECSS-E-ST-70-31C","ECSS - Current v1.0","6.5.5.7.1a","Requirement","ECSS-E-ST-70-31_0270105",1,"Created","For the definition of the tailoring of the memory management service, the additional data shown in Table 6-33 shall be provided."]
["ECSS-E-ST-70-31C","ECSS - Current v1.0","6.5.5.12.2a","Requirement","ECSS-E-ST-70-31_0270122",1,"Created","For the data types of the packet fields of the large data transfer service, the additional data shown in Table 6-50 shall be provided."]
["ECSS-E-ST-70-31C","ECSS - Current v1.0","6.5.8.1a","Requirement","ECSS-E-ST-70-31_0270137",1,"Created","For system elements of type “function” (see clause 6.5.5.8 for the related PUS function management service), the additional data specified in Table 6-65 shall be provided.\n    ","NOTE A function command can load a sub-set of the function arguments. This subset is identified by using the same names for the arguments that are defined for the corresponding command. "]
["ECSS-E-ST-70-31C","ECSS - Current v1.0","6.6.4.2a","Requirement","ECSS-E-ST-70-31_0270156",1,"Created","For compound parameters of type “record”, the additional data specified in Table 6-81 shall be provided."]
["ECSS-E-ST-70-31C","ECSS - Current v1.0","6.7.2a","Requirement","ECSS-E-ST-70-31_0270167",1,"Created","For each activity, the additional data specified in Table 6-92 shall be provided."]
["ECSS-E-ST-70-31C","ECSS - Current v1.0","6.8a","Requirement","ECSS-E-ST-70-31_0270187",1,"Created","For each event, the data specified in Table 6-111 shall be provided."]
["ECSS-E-ST-70-32C","ECSS - Current v1.0","5.1j","Permission","ECSS-E-ST-70-32_0950049",1,"Created","Preconditions and confirmation conditions may also be defined for steps."]
["ECSS-E-ST-70-32C","ECSS - Current v1.0","5.2c","Requirement","ECSS-E-ST-70-32_0950021",1,"Created","The capability shall be provided to request the execution of an activity and wait for the confirmation of execution before continuing."]
["ECSS-E-ST-70-32C","ECSS - Current v1.0","5.2v","Requirement","ECSS-E-ST-70-32_0950040",1,"Created","The capability shall be provided to generate a message for entry in the procedure execution log."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","5.3.1d","Requirement","ECSS-E-ST-70-41_1330004",1,"Created","Each mission specific service type shall be associated with a service type identifier greater than or equal to 128."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","5.3.3.2d","Requirement","ECSS-E-ST-70-41_1330021",1,"Created","For each request type and for each instruction type of that request type, whether that request type provides a single instruction slot or multiple instruction slots for that instruction type shall be declared when specifying that request type.","NOTE\tFor some instruction types, it make sense to allow multiple instructions in a request and, for others, it does not. Although an instruction type offers the possibility to have multiple instructions of that type inside a single request, that multiple instructions capability is a decision taken at request type level.\n\tAn example of an instruction type that offers the possibility to have multiple instructions inside a single request is the \"report a parameter monitoring definition\" instruction type specified in requirement 6.12.3.10b for which the request to \"report parameter monitoring definitions\" defined in clause 6.12.3.10 provide the capability to have multiple instructions inside a single request. \n\tAn example of an instruction type for which it does not make sense to allow multiple instructions in a request is the \"report all parameter monitoring definition\" instruction type also specified in requirement 6.12.3.10b.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","5.3.5.1b","Requirement","ECSS-E-ST-70-41_1330034",1,"Created","Each transaction type shall either be:\n1.\ta request related transaction type,\n2.\tan autonomous data reporting transaction type, or\n3.\tan event reporting transaction type.","NOTE 1\tFor item 1, refer to clause 5.3.5.2.\nNOTE 2\tFor item 2, refer to clause 5.3.5.3.\nNOTE 3\tFor item 3, refer to clause 5.3.5.4.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","5.3.5.2.3d","Requirement","ECSS-E-ST-70-41_1330042",1,"Created","For each instruction type, the conditions to verify during the execution of each instruction of that type shall be declared when specifying that instruction type."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","5.4.2.1j","Requirement","ECSS-E-ST-70-41_1330063",1,"Created","Each application process that provides the capability to count the type of generated messages per destination and report the corresponding message type counter shall maintain, per destination, a counter for each message type that it generates."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","5.4.3.4b","Requirement","ECSS-E-ST-70-41_1330079",1,"Created","For each virtual channel defined for downlinking reports, the virtual channel identifier used to refer to that virtual channel shall be declared when specifying that virtual channel."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","5.4.7.1b","Requirement","ECSS-E-ST-70-41_1330093",1,"Created","Each subservice shall belong to exactly one service.","NOTE\tThe type of a subservice is one of the subservice types defined for the related service type.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","5.4.11.2.1e","Requirement","ECSS-E-ST-70-41_1330109",1,"Created","Each request whose request type provides a single instruction slot shall contain exactly one instruction that is of an instruction type defined for that request type."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","5.4.11.3.1b","Requirement","ECSS-E-ST-70-41_1330114",1,"Created","Each report shall be addressed to exactly one subservice user.","NOTE\tThe subservice user addressed by this requirement is the final destination. This Standard does not address e.g.:\n·\tthe possibility for a report to be forwarded via different paths to its final destination, \n·\tin case e.g. of event reports, the possibility to dispatch the report on-board, \n·\tthe possibility for having more than one ground application processing the report.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.1.4.1b","Requirement","ECSS-E-ST-70-41_1330137",1,"Created","The list of acceptance verification checks that the acceptance and reporting subservice performs during the acceptance verification of a request shall be declared when specifying that subservice.","NOTE\tThe acceptance and reporting subservice can, for example, check:\n·\tthat the request has not been corrupted;\n·\tthe availability of the service.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.1.5.2.1a","Requirement","ECSS-E-ST-70-41_1330153",1,"Created","The execution reporting subservice shall provide the capability to generate the successful progress of execution verification reports.","NOTE\tThe corresponding verification reports are of message type \"TM[1,5] successful progress of execution verification report\".\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.2.3a","Requirement","ECSS-E-ST-70-41_1330164",1,"Created","The device access subservice shall provide at least one of:\n1.\tthe capability for distributing on/off device commands specified in clause 6.2.4;\n2.\tthe capability for distributing register commands specified in clause 6.2.5;\n3.\tthe capability for distributing software CPDU commands specified in clause 6.2.6;\n4.\tthe capability for physical devices commanding access specified in clause 6.2.7."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.2.5.2f","Requirement","ECSS-E-ST-70-41_1330183",1,"Created","For each request to distribute register load commands that contains only valid instructions, the device access subservice shall execute those instructions in the order of their appearance in that request."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.2.5.3a","Requirement","ECSS-E-ST-70-41_1330185",1,"Created","The device access subservice capability to distribute register dump commands shall be declared when specifying that subservice.","NOTE 1\tThe corresponding requests are of message type \"TC[2,5] distribute register dump commands\". The responses are data reports of message type \"TM[2,6] register dump report\".\nNOTE 2\tThat capability requires the capability for that subservice to distribute register load commands (refer to clause 6.2.5.2).\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.2.7.1.3b","Requirement","ECSS-E-ST-70-41_1330212",1,"Created","Each request to acquire data from physical devices shall contain an ordered list of one or more instructions to acquire data from a physical device."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.2.7.2.2h","Requirement","ECSS-E-ST-70-41_1330228",1,"Created","For each request to distribute logical device commands that results in at least one unsuccessful command transmission check, the device access subservice shall generate a single failed completion of execution verification report that includes the first failed progress of execution notification generated for that request."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.2.7.2.3h","Requirement","ECSS-E-ST-70-41_1330236",1,"Created","For each logical device, the list of data acquisition return codes and associated auxiliary data shall be declared when specifying that logical device.","NOTE\tAuxiliary data can be associated to each data acquisition return code in the list, to provide detail reporting on the reason for that return code.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.3.3.4.1d","Requirement","ECSS-E-ST-70-41_1330257",1,"Created","The housekeeping reporting subservice shall reject any instruction to enable the periodic generation of a housekeeping parameter report if:\n1.\tthat instruction refers to a housekeeping parameter report structure that is unknown."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.3.3.5.1d","Requirement","ECSS-E-ST-70-41_1330271",1,"Created","The housekeeping reporting subservice shall reject any request to create a housekeeping parameter report structure if any of the following conditions occurs:\n1.\tthat request contains an instruction that refers to a housekeeping parameter report structure that is already in use;\n2.\tthe same parameter is identified more than once in that request;\n3.\tthe resources allocated to the hosting of housekeeping parameter report structures are exceeded."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.3.3.5.1e","Requirement","ECSS-E-ST-70-41_1330272",1,"Created","For each request to create a housekeeping parameter report structure that is rejected, the housekeeping reporting subservice shall generate a failed start of execution notification."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.3.3.7e","Requirement","ECSS-E-ST-70-41_1330292",1,"Created","For each instruction to generate a one shot report for a housekeeping parameter report structure that it rejects, the housekeeping reporting subservice shall generate the failed start of execution notification for that instruction."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.3.3.9b","Requirement","ECSS-E-ST-70-41_1330302",1,"Created","Each request to modify the collection interval of housekeeping parameter report structures shall contain one or more instructions to modify the collection interval of a housekeeping parameter report structure."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.3.4.2a","Requirement","ECSS-E-ST-70-41_1330317",1,"Created","The on-board resources allocated to the diagnostic reporting subservice to host the diagnostic parameter report structures shall be declared when specifying that subservice.","NOTE\tThe number of diagnostic parameter report structures that can be hosted by the subservice depends on these resources and the size (in parameter number) of the diagnostic parameter report structures.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.3.4.6d","Requirement","ECSS-E-ST-70-41_1330343",1,"Created","The diagnostic reporting subservice shall reject any request to create a diagnostic parameter report structure if any of the following conditions occurs:\n1.\tthat request contains an instruction that refers to a diagnostic parameter report structure identifier that is already in use;\n2.\tthe same parameter is identified more than once in that request;\n3.\tthe resources allocated to the hosting of diagnostic parameter report structures are exceeded."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.3.4.7b","Requirement","ECSS-E-ST-70-41_1330347",1,"Created","Each request to delete diagnostic parameter report structures shall contain one or more instructions to delete a diagnostic parameter report structure."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.3.4.9e","Requirement","ECSS-E-ST-70-41_1330364",1,"Created","For each instruction to generate a one shot report for a diagnostic parameter report structure that it rejects, the diagnostic reporting subservice shall generate the failed start of execution notification for that instruction."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.3.4.11e","Requirement","ECSS-E-ST-70-41_1330377",1,"Created","For each instruction to modify the collection interval of a diagnostic parameter report structure that it rejects, the diagnostic reporting subservice shall generate the failed start of execution notification for that instruction."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.3.5.3a","Requirement","ECSS-E-ST-70-41_1330392",1,"Created","The parameter functional reporting configuration subservice shall provide the capability to apply parameter functional reporting configurations.","NOTE\tThe corresponding requests are of message type \"TC[3,37] apply parameter functional reporting configurations\".\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.3.5.4.2g","Requirement","ECSS-E-ST-70-41_1330415",1,"Created","For each valid instruction to delete a parameter functional reporting definition, the parameter functional reporting configuration subservice shall:\n1.\tdelete that definition."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.3.5.5g","Requirement","ECSS-E-ST-70-41_1330422",1,"Created","For each valid instruction to report a parameter functional reporting definition, the parameter functional reporting configuration subservice shall generate a single parameter functional reporting definition report that contains:\n1.\tthe identifier of the parameter functional reporting definition;\n2.\tfor each related parameter reporting entry, exactly one parameter functional reporting definition notification, that includes:\n(a)\tif the housekeeping service is distributed on several on-board application processes, the application process identifier;\n(b)\tan indication of the nature of the parameter report definition as housekeeping or diagnostic;\n(c)\tthe identifier of the parameter report definition;\n(d)\tthe periodic generation action status;\n(e)\tthe collection interval."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.3.5.6.3f","Requirement","ECSS-E-ST-70-41_1330446",1,"Created","The parameter functional reporting configuration subservice shall reject any instruction to modify the periodic generation properties of a parameter report definition of a parameter functional reporting definition if:\n1.\tthat instruction refers to a parameter report definition that is not in that parameter functional reporting definition"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.4.3.1a","Requirement","ECSS-E-ST-70-41_1330452",1,"Created","The maximum number of parameter statistics definitions that the parameter statistics reporting subservice can contemporaneously evaluate at any time shall be declared when specifying that subservice."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.4.5.2c","Requirement","ECSS-E-ST-70-41_1330467",1,"Created","For each valid instruction to report the parameter statistics, the parameter statistics reporting subservice shall generate a single parameter statistics report.","NOTE\tFor the parameter statistics report, refer to clause 6.4.5.3.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.4.6.3b","Requirement","ECSS-E-ST-70-41_1330487",1,"Created","Each request to disable the periodic parameter statistics reporting shall contain exactly one instruction to disable the periodic parameter statistics reporting.","NOTE\tThe instructions to disable the periodic parameter statistics reporting contain no argument.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.4.7.2a","Requirement","ECSS-E-ST-70-41_1330497",1,"Created","The parameter statistics reporting subservice shall provide the capability to delete parameter statistics definitions if the capability to add or update parameter statistics definitions is provided by that subservice.","NOTE 1\tThe corresponding requests are of message type \"TC[4,7] delete parameter statistics definitions\".\nNOTE 1\tFor the capability to add or updates parameter statistics definitions, refer to clause 6.4.7.1.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.5.4d","Requirement","ECSS-E-ST-70-41_1330518",1,"Created","If the event reporting subservice does not support the capability for controlling the generation of event reports specified in clause 6.5.5, that subservice shall generate an event notification whenever it detects the occurrence of an event."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.5.5.2e","Requirement","ECSS-E-ST-70-41_1330527",1,"Created","For each instruction to enable the report generation of an event definition that it rejects, the event reporting subservice shall generate the failed start of execution notification for that instruction."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.6.2.1.1a","Requirement","ECSS-E-ST-70-41_1330542",1,"Created","Each memory management service shall contain at least one of:\n1.\tthe raw data memory management subservice;\n2.\tthe structured data memory management subservice."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.6.3.3.1b","Requirement","ECSS-E-ST-70-41_1330555",1,"Created","Each request to load raw memory data areas shall contain:\n1.\tif the raw data memory management subservice manages more than one memory, the identifier of the memory;\n2.\tan ordered list of one or more instructions to load a raw memory data area.","NOTE 1\tFor item 1, refer to requirement 6.6.3.2a. If the raw data memory management subservice manages only one memory, the instructions apply to that memory.\nNOTE 2\tAll the instructions in the request apply to the same memory. \n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.6.3.3.2h","Requirement","ECSS-E-ST-70-41_1330572",1,"Created","If an error occurs during the writing to memory of the data related to an instruction load a raw memory atomic data area in a non-interruptible transaction, the raw data memory management subservice shall:\n1.\tgenerate a failed execution notification for that instruction."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.6.3.5g","Requirement","ECSS-E-ST-70-41_1330590",1,"Created","For each instruction to check a raw memory data that it rejects, the raw data memory management subservice shall generate the failed start of execution notification for that instruction."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.6.3.6i","Requirement","ECSS-E-ST-70-41_1330602",1,"Created","If an error occurs during the writing to memory of the data related to an instruction to load a raw memory data area by reference, the raw data memory management subservice shall:\n1.\timmediately abort the execution of the related request;\n2.\tgenerate a failed execution notification for that instruction.","NOTE\tFor example, an error can occur when the memory becomes write-protected by hardware during the course of the load operation.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.6.3.7g","Requirement","ECSS-E-ST-70-41_1330611",1,"Created","For each instruction to dump a raw memory data area to file that it rejects, the raw data memory management subservice shall generate the failed start of execution notification for that instruction."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.6.4.4i","Requirement","ECSS-E-ST-70-41_1330631",1,"Created","If an error occurs during the writing to memory of the data related to an instruction to load an object memory data, the structured data memory management subservice shall:\n1.\timmediately abort the execution of the related request;\n2.\tgenerate a failed execution notification for that instruction.","NOTE\tFor example, an error can occur when the memory becomes write-protected by hardware during the course of the load operation.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.6.4.6d","Requirement","ECSS-E-ST-70-41_1330647",1,"Created","For each request to check object memory data that is rejected, the structured data memory management subservice shall generate a failed start of execution notification."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.6.4.8b","Requirement","ECSS-E-ST-70-41_1330662",1,"Created","Each request to load object memory data areas by reference shall contain:\n1.\tif the structured data memory management subservice manages more than one memory, the identifier of the memory;\n2.\tthe base identifier;\n3.\tthe file path of the file containing the data to load;\n4.\tan ordered list of one or more instructions to load an object memory data area by reference.","NOTE 1\tFor item 1, refer to requirement 6.6.4.2a. If the structured data memory management subservice manages only one memory, the instructions apply to that memory.\nNOTE 2\tAll the instructions in the request apply to the same memory and to the same file. \n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.6.4.9f","Requirement","ECSS-E-ST-70-41_1330677",1,"Created","The structured data memory management subservice shall reject any instruction to dump an object memory data area to file if any of the following conditions occurs:\n1.\tthat instruction refers to an offset that, combined with the length of the memory area to dump, exceeds the maximum memory size of the memory object identified by the base identifier;\n2.\tthat instruction refers to an offset which is not aligned with the memory access alignment constraint;\n3.\tthat instruction refers to a length that is not a multiple of the memory access alignment constraint."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.6.5.1b","Requirement","ECSS-E-ST-70-41_1330683",1,"Created","Each request to abort all memory dumps shall contain exactly one instruction to abort all memory dumps.","NOTE\tThe instructions to abort all memory dumps contain no argument.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.6.6.2.4b","Requirement","ECSS-E-ST-70-41_1330706",1,"Created","Each request to enable the write protection of a memory shall contain exactly one instruction to enable the write protection of a memory."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.8.3.1c","Requirement","ECSS-E-ST-70-41_1330722",1,"Created","For each function that uses arguments, the policy for supplying the arguments shall be declared when specifying that function:\n1.\tsupplying a value for each argument, or\n2.\tsupplying only values for those arguments to update, the other arguments retaining their current values."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.9.2.3c","Requirement","ECSS-E-ST-70-41_1330734",1,"Created","If the time reporting control subservice has the capability to generate reports, that subservice shall not be hosted by the application process that hosts the time reporting subservice.","NOTE\tAll reports generated by the application process that is identified by APID 0 are time reports. These time reports are transported in CCSDS space packets that have no secondary header, resulting in no adequate means to identify reports of any other type.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.9.4.3b","Requirement","ECSS-E-ST-70-41_1330751",1,"Created","Whether the time reporting subservice includes the P-field in the CDS time reports shall be declared when specifying that subservice.","NOTE\tIf the P-field is not explicitly included, the P-field value is considered implicit.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.9.4.4a","Requirement","ECSS-E-ST-70-41_1330755",1,"Created","The time reporting subservice shall sample the spacecraft time reference once for each telemetry transfer frame on virtual channel 0 that satisfies the following condition:\n1.\tthe virtual channel frame count carried in the header of a telemetry transfer frame modulo the time report generation rate equals to 0."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.11.4.3.2c","Requirement","ECSS-E-ST-70-41_1330781",1,"Created","For each valid instruction to enable the time-based schedule execution function, the time-based scheduling subservice shall:\n1.\tset the time-based schedule execution function status to \"enabled\".","NOTE\tEnabling the time-based schedule execution function does not depend on the presence of scheduled activities in the schedule.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.11.4.5j","Requirement","ECSS-E-ST-70-41_1330797",1,"Created","For each valid request to insert activities into the time-based schedule, the time-based scheduling subservice shall:\n1.\tif sub-schedules are supported and the sub-schedule specified in that request is unknown:\n(a)\tcreate that sub-schedule;\n(b)\tset its status to \"disabled\".","NOTE\tFor item 1, refer to requirement 6.11.4.1a.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.11.5.2.1c","Requirement","ECSS-E-ST-70-41_1330806",1,"Created","Each instruction to enable a time-based sub-schedule shall contain:\n1.\tthe identifier of the sub-schedule to enable."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.11.6.2.1a","Requirement","ECSS-E-ST-70-41_1330826",1,"Created","The time-based scheduling subservice capability to create time-based scheduling groups shall be declared when specifying that subservice.","NOTE 1\tThe corresponding requests are of message type \"TC[11,22] create time-based scheduling groups\".\nNOTE 2\tFor the capability to delete time-based scheduling groups, refer to clause 6.11.6.2.2.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.11.6.2.1b","Requirement","ECSS-E-ST-70-41_1330827",1,"Created","Each request to create time-based scheduling groups shall contain one or more instructions to create a time-based scheduling group."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.11.6.3.1a","Requirement","ECSS-E-ST-70-41_1330841",1,"Created","The time-based scheduling subservice shall provide the capability to enable time-based scheduling groups if the capability to create time-based scheduling groups is provided by that subservice.","NOTE 1\tThe corresponding requests are of message type \"TC[11,24] enable time-based scheduling groups\". \nNOTE 2\tFor the capability to disable time-based scheduling groups, refer to clause 6.11.6.3.2.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.11.6.3.3b","Requirement","ECSS-E-ST-70-41_1330858",1,"Created","Each request to report the status of each time-based scheduling group shall contain exactly one instruction to report the status of each time-based scheduling group.","NOTE\tThe instructions to report the status of each time-based scheduling group contain no argument.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.11.8.1e","Requirement","ECSS-E-ST-70-41_1330871",1,"Created","For each request to time-shift all scheduled activities that is rejected, the time-based scheduling subservice shall generate a failed start of execution notification."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.11.9.2e","Requirement","ECSS-E-ST-70-41_1330886",1,"Created","For each instruction to delete a time-based scheduled activity identified by request identifier that it rejects, the time-based scheduling subservice shall generate the failed start of execution notification for that instruction."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.11.9.5h","Requirement","ECSS-E-ST-70-41_1330913",1,"Created","For each valid request to detail-report time-based scheduled activities identified by request identifier, the time-based scheduling subservice shall generate a single time-based schedule detail report that contains all related time-based schedule detail notifications.","NOTE\tThe time-based schedule detail report is specified in clause 6.11.7.2.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.11.10.2.2b","Requirement","ECSS-E-ST-70-41_1330916",1,"Created","The set of scheduled activities identified by the \"select all activities scheduled from time tag to time tag\" filtering mechanism shall be all activities that are scheduled between and including the specified \"from time tag\" and \"to time tag\"."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.11.10.4c","Requirement","ECSS-E-ST-70-41_1330930",1,"Created","Each instruction to time-shift the scheduled activities identified by a filter shall contain:\n1.\ta time offset, positive or negative, to add to the release time of the identified scheduled activities;\n2.\tthe time window, consisting of:\n(a)\tthe type of the time window that is one of \"select all\", \"from time tag\", \"to time tag\", \"from time tag to time tag\";\n(b)\tfor \"from time tag\" and \"from time tag to time tag\", the from time tag;\n(c)\tfor \"to time tag\" and \"from time tag to time tag\", the to time tag;\n3.\tif sub-schedules are supported, zero or more sub-schedules;\n4.\tif groups are supported, zero or more groups.","NOTE 1\tFor item 3, refer to requirement 6.11.4.1a.\nNOTE 2\tFor item 4, refer to requirement 6.11.4.1b.\nNOTE 3\tFor the filtering mechanism, including the interaction of the parts of the filter, refer to clause 6.11.10.2.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.11.10.6f","Requirement","ECSS-E-ST-70-41_1330946",1,"Created","For each valid instruction to detail-report the time-based scheduled activities identified by a filter, the time-based scheduling subservice shall generate, for each scheduled activity identified by that instruction, a single time-based schedule detail notification.","NOTE\tThe time-based schedule detail notification content is specified in clause 6.11.7.2.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.12.3.3a","Requirement","ECSS-E-ST-70-41_1330960",1,"Created","The maximum number of parameter monitoring definitions that the parameter monitoring subservice can contemporaneously evaluate at any time shall be declared when specifying that subservice.","NOTE\tThis maximum represents the maximum number of entries in the parameter monitoring definition list. The parameter monitoring definition list is named \"PMON list\".\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.12.3.6.1c","Requirement","ECSS-E-ST-70-41_1330984",1,"Created","Each instruction to enable a parameter monitoring definition shall contain:\n1.\tthe identifier of the parameter monitoring definition."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.12.3.6.2b","Requirement","ECSS-E-ST-70-41_1330990",1,"Created","Each request to disable parameter monitoring definitions shall contain one or more instructions to disable a parameter monitoring definition."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.12.3.6.3f","Requirement","ECSS-E-ST-70-41_1331001",1,"Created","When a new PMON checking status is established for a limit-check, the parameter monitoring subservice shall set the PMON checking status to:\n1.\t\"above high limit\", if the specified \"repetition number\" of consecutive checks were declared unsuccessful and the parameter value in each check was greater than the high limit value;\n2.\t\"below low limit\", if the specified \"repetition number\" of consecutive checks were declared unsuccessful and the parameter value in each check was less than the low limit value;\n3.\t\"within limits\", if the specified \"repetition number\" of consecutive checks were declared successful.","NOTE\tSee requirement 6.12.3.2.1b for the conditions to declare success for a limit check.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.12.3.9.1h","Requirement","ECSS-E-ST-70-41_1331020",1,"Created","For each valid instruction to add a parameter monitoring definition, the parameter monitoring subservice shall:\n1.\tadd a new parameter monitoring definition to the PMON list, using data from that instruction;\n2.\tset the PMON checking status of the new parameter monitoring definition to \"unchecked\";\n3.\tset the PMON status of the new parameter monitoring definition to \"disabled\"."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.12.3.9.4c","Requirement","ECSS-E-ST-70-41_1331035",1,"Created","Each instruction to modify a parameter monitoring definition shall contain:\n1.\tthe identifier of the parameter monitoring definition;\n2.\tthe identifier of the monitored parameter used by that parameter monitoring definition;\n3.\tthe means to modify:\n(a)\tthe repetition number;\n(b)\tfor a limit-check, its low limit, its high limit and the event definition identifier of each associated event;\n(c)\tfor an expected-value-check, its expected-value-check mask, its expected value and the event definition identifier of its associated event;\n(d)\tfor a delta-check, its low delta threshold, its high delta threshold and the event definition identifier of each associated event.","NOTE\tIn order to modify the other parameter monitoring definition characteristics, e.g. the check type, this Standard promotes the scenario to delete the parameter monitoring definition and create a new one.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.12.3.11d","Requirement","ECSS-E-ST-70-41_1331052",1,"Created","For each valid request to report the status of each parameter monitoring definition, the parameter monitoring subservice shall generate a single parameter monitoring definition status report that includes all related parameter monitoring definition status notifications."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.12.4.2.1d","Requirement","ECSS-E-ST-70-41_1331065",1,"Created","Whether the functional monitoring subservice supports specifying, for each functional monitoring definition, the minimum number of contemporaneously violated parameter monitoring definitions that establishes a functional monitoring checking failure shall be declared when specifying that subservice.","NOTE 1\tThis minimum number is named \"minimum PMON failing number\".\nNOTE 1\tA minimum PMON failing number that equals 1 means that a functional monitoring definition fails as soon as one of its parameter monitoring definitions fails. This is equivalent to a logical OR of the PMON conditions.\nNOTE 2\tIf a functional monitoring definition has a minimum PMON failing number that is equal to the number of its parameter monitoring definitions, then the functional monitoring definition fails when all its parameter monitoring definitions fail. This is equivalent to a logical AND of the PMON conditions.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.12.4.5.2g","Requirement","ECSS-E-ST-70-41_1331087",1,"Created","For each valid instruction to enable a functional monitoring definition, the functional monitoring subservice shall:\n1.\tset the FMON status of the functional monitoring definition to \"enabled\".","NOTE\tEnabling the FMON status of the functional monitoring definition does not affect the FMON checking status of that definition.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.12.4.6.1a","Requirement","ECSS-E-ST-70-41_1331095",1,"Created","The functional monitoring subservice capability to protect functional monitoring definitions shall be declared when specifying that subservice.","NOTE 1\tThe corresponding requests are of message type \"TC[12,21] protect functional monitoring definitions\".\nNOTE 2\tFor the capability to unprotect functional monitoring definitions, refer to clause 6.12.4.6.2.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.12.4.7.1b","Requirement","ECSS-E-ST-70-41_1331110",1,"Created","Each request to add functional monitoring definitions shall contain one or more instructions to add a functional monitoring definition."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.12.4.7.2g","Requirement","ECSS-E-ST-70-41_1331124",1,"Created","For each valid instruction to delete a functional monitoring definition, the functional monitoring subservice shall:\n1.\tremove the functional monitoring definition that is referred to by that instruction from the FMON list."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.13.2.1.2a","Requirement","ECSS-E-ST-70-41_1331140",1,"Created","Each large packet transfer service shall contain at most one large packet downlink subservice."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.13.3.3.2g","Requirement","ECSS-E-ST-70-41_1331159",1,"Created","Upon completion of the downlink operation, if all part reports have been successfully received, the receiving entity of the large packet downlink subservice shall:\n1.\tgenerate that large packet for subsequent routing to its destination.","NOTE\tThe receiving entity is not in charge of checking the checksum of the reconstructed large packet.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.13.4.3.2a","Requirement","ECSS-E-ST-70-41_1331170",1,"Created","The receiving entity of the large packet uplink subservice shall be able to process all uplink part requests that it receives.","NOTE\tThis process is called \"large packet acceptance and reconstruction process\".\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.13.4.3.3b","Requirement","ECSS-E-ST-70-41_1331180",1,"Created","For each large packet uplink abortion notification that it generates, the receiving entity of the large packet uplink subservice shall generate a single large packet uplink abortion report that contains that notification."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.14.3.2.4b","Requirement","ECSS-E-ST-70-41_1331199",1,"Created","Each diagnostic parameter report forward-control definition shall contain:\n1.\tthe identifier of the application process;\n2.\ta list of zero or more related diagnostic parameter report structure identifiers. ","NOTE 1\tAn empty diagnostic parameter report forward-control configuration (i.e. no diagnostic parameter report forward-control definition is defined) implies that the subservice blocks all diagnostic parameter reports.\nNOTE 1\tA diagnostic parameter report is forwarded to ground only if the application process forward-control configuration does not block that report and one of the following conditions occurs:\n·\ta diagnostic parameter report forward-control definition with no diagnostic parameter report structure identifiers is defined for the application process identifier of that report;\n·\ta diagnostic parameter report forward-control definition with a diagnostic parameter report structure identifier is defined for the application process identifier and the diagnostic parameter report structure identifier of that report.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.14.3.4.1c","Requirement","ECSS-E-ST-70-41_1331215",1,"Created","Each instruction to add a report type to the application process forward-control configuration shall contain:\n1.\tthe application process identifier addressed by that instruction,\n2.\tthe message type identifier consisting of:\n(a)\tthe service type identifier;\n(b)\tthe message subtype identifier."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.14.3.4.2f","Requirement","ECSS-E-ST-70-41_1331231",1,"Created","Each instruction to delete a service type from the application process forward-control configuration shall contain:\n1.\tthe application process identifier addressed by that instruction,\n2.\tthe service type identifier. "]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.14.3.4.3c","Requirement","ECSS-E-ST-70-41_1331244",1,"Created","For each valid instruction to report the content of the application process forward-control configuration, the real-time forwarding control subservice shall generate, for each existing application process forward-control definition, a single application process forward-control definition notification that includes:\n1.\tthe related application process identifier;\n2.\tfor each related service type forward-control definition, if any:\n(a)\tthe related service type identifier;\n(b)\tfor each related report type forward-control definition, if any, the related message subtype identifier."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.14.3.5.1g","Requirement","ECSS-E-ST-70-41_1331252",1,"Created","For each instruction contained within a request to add structure identifiers to the housekeeping parameter report forward-control configuration that it rejects, the real-time forwarding control subservice shall generate the failed start of execution notification for that instruction."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.14.3.6.1c","Requirement","ECSS-E-ST-70-41_1331274",1,"Created","Each instruction to add a structure identifier to the diagnostic parameter report forward-control configuration shall contain:\n1.\tthe application process identifier addressed by that instruction;\n2.\tthe diagnostic parameter report structure identifier;\n3.\tif subsampling is supported, the subsampling rate.","NOTE\tFor item 3, refer to requirement 6.14.3.2.1d.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.14.3.6.2i","Requirement","ECSS-E-ST-70-41_1331290",1,"Created","The real-time forwarding control subservice shall process any valid instruction that is contained within a request to delete structure identifiers from the diagnostic parameter report forward-control configuration regardless of the presence of faulty instructions."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.14.3.7.1f","Requirement","ECSS-E-ST-70-41_1331303",1,"Created","Each instruction to delete an application process from the event report blocking forward-control configuration shall contain:\n1.\tthe application process identifier addressed by that instruction."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.14.3.7.2j","Requirement","ECSS-E-ST-70-41_1331319",1,"Created","For each valid instruction to add all event definition identifiers to the event report blocking forward-control configuration, the real-time forwarding control subservice shall:\n1.\tadd, for the specified application process identifier, an event report blocking forward-control definition if not already existing;\n2.\tdelete, if any, all event definition identifiers of the related event report blocking forward-control definition. "]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.15.2.1.1a","Requirement","ECSS-E-ST-70-41_1331324",1,"Created","Each on-board storage and retrieval service shall contain exactly one storage and retrieval subservice."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.15.3.3.2e","Requirement","ECSS-E-ST-70-41_1331349",1,"Created","For each instruction to enable the storage function of a packet store that it rejects, the storage and retrieval subservice shall generate the failed start of execution notification for that instruction."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.15.3.4.2a","Requirement","ECSS-E-ST-70-41_1331364",1,"Created","The storage and retrieval subservice shall provide the capability to change the open retrieval start time tag of packet stores.","NOTE\tThe corresponding requests are of message type \"TC[15,14] change the open retrieval start time tag of packet stores\".\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.15.3.4.3b","Requirement","ECSS-E-ST-70-41_1331375",1,"Created","Each request to resume the open retrieval of packet stores shall contain:\n1.\tone or more instructions to resume the open retrieval of a packet store, or\n2.\texactly one instruction to resume the open retrieval of all packet stores.","NOTE\tThe instructions to resume the open retrieval of all packet stores contain no argument.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.15.3.5.2b","Requirement","ECSS-E-ST-70-41_1331394",1,"Created","Each request to start the by-time-range retrieval of packet stores shall contain one or more instructions to start the by-time-range retrieval of a packet store."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.15.3.5.2d","Requirement","ECSS-E-ST-70-41_1331396",1,"Created","The storage and retrieval subservice shall reject any instruction to start the by-time-range retrieval of a packet store if any of the following conditions occurs:\n1.\tthat instruction refers to a packet store that does not exist;\n2.\tthat subservice does not support concurrent retrieval requests executing in parallel and the packet store open retrieval status of that packet store is in-progress;\n3.\tthe retrieval start time in that instruction is later than the retrieval end time;\n4.\tthe storage time period of that instruction is fully in the past and the packet store contains no packet with a time stamp in that time period;\n5.\tthat instruction refers to a packet store whose by-time-range retrieval status is \"enabled\".","NOTE\tFor item 2, refer to requirement 6.15.3.1i.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.15.3.6b","Requirement","ECSS-E-ST-70-41_1331409",1,"Created","Each request to report the status of each packet store shall contain exactly one instruction to report the status of each packet store.","NOTE\tThe instructions to report the status of each packet store contain no argument.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.15.3.8.1h","Requirement","ECSS-E-ST-70-41_1331427",1,"Created","The storage and retrieval subservice shall process any valid instruction that is contained within a request to create packet stores regardless of the presence of faulty instructions."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.15.3.8.3c","Requirement","ECSS-E-ST-70-41_1331439",1,"Created","For each valid instruction to report the configuration of each packet store, the storage and retrieval subservice shall:\n1.\tgenerate, for each managed packet store, a single packet store configuration notification that includes:\n(a)\tthe packet store identifier;\n(b)\tthe packet store size in bytes;\n(c)\tif more than one packet store type is supported, the packet store type (bounded or circular);\n(d)\tif more than one packet store virtual channel is supported, the virtual channel identifier.","NOTE 1\tFor item 1(c), refer to requirement 6.15.3.1f.\nNOTE 2\tFor item 1(d), refer to requirement 6.15.3.1g.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.15.3.9.1d","Requirement","ECSS-E-ST-70-41_1331454",1,"Created","The storage and retrieval subservice shall reject any instruction to resize a packet store if any of the following conditions occurs:\n1.\tthat instruction refers to a packet store that does not exist;\n2.\tthat instruction specifies a packet store size that is not compatible with the current memory availability;\n3.\tthat instruction refers to a packet store whose packet store storage status is \"enabled\";\n4.\tthat instruction refers to a packet store whose packet store open retrieval status is \"in-progress\";\n5.\tthat instruction refers to a packet store that packet store by-time-range retrieval status is \"enabled\"."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.15.3.9.3e","Requirement","ECSS-E-ST-70-41_1331468",1,"Created","For each request to change a packet store type to bounded that is rejected, the storage and retrieval subservice shall generate a failed start of execution notification."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.15.3.10.1i","Requirement","ECSS-E-ST-70-41_1331484",1,"Created","For each valid request to summary-report the content of packet stores, the storage and retrieval subservice shall generate a single packet store content summary report that contains all related packet store content summary notifications."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.15.4.2.3c","Requirement","ECSS-E-ST-70-41_1331499",1,"Created","The maximum number of housekeeping parameter report structure identifiers that can be contained within a housekeeping parameter report storage-control definition shall be declared when specifying the packet selection subservice."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.15.4.3i","Requirement","ECSS-E-ST-70-41_1331514",1,"Created","If the packet selection subservice provides the capability to control, per event definition, the storage of event reports, the subservice shall block the storage of an event report to a packet store if that report fulfils all of the following conditions:\n1.\tthe application process identifier of that report is contained within an event report blocking storage-control definition for that packet store, and\n2.\tthat event report blocking storage-control definition contains the event definition identifier of that report.","NOTE\tThe storage of an event definition of an application process is enabled if it is blocked neither by the application process storage control configuration nor by the event report blocking control configuration.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.15.4.4.1o","Requirement","ECSS-E-ST-70-41_1331529",1,"Created","For each valid instruction to add all report types of an application process to the application process storage-control configuration, the packet selection subservice shall, for the related packet store:\n1.\tadd, for the specified application process identifier, an application process storage-control definition if not already existing;\n2.\tdelete, if any, all service type storage-control definitions of the related application process storage-control definition."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.15.4.4.3c","Requirement","ECSS-E-ST-70-41_1331550",1,"Created","Each instruction to report the content of the application process storage-control configuration shall contain:\n1.\tthe packet store identifier of the packet store. "]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.15.4.5.1e","Requirement","ECSS-E-ST-70-41_1331559",1,"Created","Each instruction to add all structure identifiers to the housekeeping parameter report storage-control configuration shall contain:\n1.\tthe application process identifier addressed by that instruction."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.15.4.5.2f","Requirement","ECSS-E-ST-70-41_1331571",1,"Created","Each instruction to delete an application process from the housekeeping parameter report storage-control configuration shall contain:\n1.\tthe application process identifier addressed by that instruction."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.15.4.6.1f","Requirement","ECSS-E-ST-70-41_1331589",1,"Created","The packet selection subservice shall reject any instruction contained within a request to add structure identifiers to the diagnostic parameter report storage-control configuration if:\n1.\tthat instruction refers to an application process that is not controlled by that subservice."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.15.4.6.2j","Requirement","ECSS-E-ST-70-41_1331604",1,"Created","For each valid instruction to delete a structure identifier from the diagnostic parameter report storage-control configuration , the packet selection subservice shall, for the related packet store:\n1.\tdelete the diagnostic parameter report structure identifier related to the specified application process identifier;\n2.\tif that diagnostic parameter report structure identifier deletion results in an emptied diagnostic parameter report storage-control definition, delete that diagnostic parameter report storage-control definition. ","NOTE\tDeleting a diagnostic parameter report structure identifier implies deleting the corresponding subsampling rate if any (see also requirement 6.15.4.2.1d).\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.15.4.7.1j","Requirement","ECSS-E-ST-70-41_1331622",1,"Created","For each valid instruction to add an event definition identifier to the event report blocking storage-control configuration, the packet selection subservice shall, for the related packet store:\n1.\tadd, for the specified application process identifier, an event report blocking storage-control definition if not already existing;\n2.\tadd, to the related event report blocking storage-control definition, the specified event definition identifier, if not already existing."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.15.4.7.2k","Requirement","ECSS-E-ST-70-41_1331634",1,"Created","For each valid instruction to delete an application process from the event report blocking storage-control configuration, the packet selection subservice shall, for the related packet store:\n1.\tdelete the event report blocking control definition for the specified application process identifier."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.17.2.2a","Requirement","ECSS-E-ST-70-41_1331643",1,"Created","Each application process shall host at most one test subservice provider."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.18.2.3b","Requirement","ECSS-E-ST-70-41_1331663",1,"Created","The on-board control procedure service shall maintain a status that reflects whether the OBCP engine is running or not.","NOTE 1\tThis status is called the \"OBCP engine status\".\nNOTE 1\tThis status exists regardless of the presence of an OBCP engine management subservice to start or stop the OBCP engine.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.18.4.4.2a","Requirement","ECSS-E-ST-70-41_1331679",1,"Created","The OBCP management subservice capability to direct-load an OBCP shall be declared when specifying that subservice.","NOTE 1\tThe corresponding requests are of message type \"TC[18,1] direct-load an OBCP\".\nNOTE 1\tFor that declaration, refer to requirement 6.18.4.4.1a.\nNOTE 2\tFor the capability to unload an OBCP, refer to clause 6.18.4.4.4.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.18.4.4.4b","Requirement","ECSS-E-ST-70-41_1331694",1,"Created","Each request to unload an OBCP shall contain exactly one instruction to unload an OBCP."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.18.4.4.6e","Requirement","ECSS-E-ST-70-41_1331709",1,"Created","The OBCP management subservice shall reject any request to load by reference and activate an OBCP if any of the following conditions occurs:\n1.\tthe OBCP engine is not running;\n2.\tthat request contains an instruction that refers to an OBCP identifier that is already in the OBCP engine;\n3.\tthat request contains an instruction that refers to a file that does not exist;\n4.\tthat request contains an instruction that refers to a file that is not recognized as an OBCP file;\n5.\tthe on-board file determined by the loading policy does not exist;\n6.\tthe OBCP code in the file fails the checksum verification;\n7.\tthat request contains an instruction that refers to an observability level that is invalid;\n8.\tthat OBCP cannot be loaded and activated due to the lack of OBCP engine available resources.","NOTE\tItem 8 implies that insufficient resources to activate the OBCP prevents the loading of the OBCP.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.18.4.4.9b","Requirement","ECSS-E-ST-70-41_1331729",1,"Created","Each request to abort an OBCP shall contain exactly one instruction to abort an OBCP."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.18.4.4.10e","Requirement","ECSS-E-ST-70-41_1331738",1,"Created","For each valid instruction to abort all OBCPs and report, the OBCP management subservice shall:\n1.\tfreeze the execution of all OBCP statements;\n2.\tfor each active OBCP, set the execution status of that OBCP to \"inactive\".\n3.\tgenerate, for each aborted OBCP, a single aborted OBCP notification that includes:\n(a)\tthe identifier of that aborted OBCP."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.18.4.6.1e","Requirement","ECSS-E-ST-70-41_1331750",1,"Created","The OBCP management subservice shall reject any request to suspend an OBCP if any of the following conditions occurs:\n1.\tthe OBCP engine is not running;\n2.\tthat request contains an instruction that refers to an OBCP identifier that is not loaded in the OBCP engine;\n3.\tthat request contains an instruction that refers to an OBCP that is not active."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.18.4.6.4c","Requirement","ECSS-E-ST-70-41_1331768",1,"Created","Each instruction to resume and execute one OBCP step shall contain:\n1.\tthe identifier of the OBCP."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.18.4.8.1g","Requirement","ECSS-E-ST-70-41_1331784",1,"Created","For each instruction to set the observability level of an OBCP that it rejects, the OBCP management subservice shall generate the failed start of execution notification for that instruction."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.19.3.1a","Requirement","ECSS-E-ST-70-41_1331801",1,"Created","The list of event reporting subservices that generate the event reports used by the event-action subservice shall be declared when specifying that event-action subservice.","NOTE\tThe event reporting subservice is specified in clause 6.5\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.19.6.1c","Requirement","ECSS-E-ST-70-41_1331813",1,"Created","For each valid instruction to enable the event-action function, the event-action subservice shall:\n1.\tset the event-action function status to \"enabled\".","NOTE 1\tWhen the event-action function status is \"enabled\", the event-action subservice reacts to event reports as specified in requirement 6.19.5.2b.\nNOTE 1\tEnabling the event-action function has no impact on the event-action status of the event-action definitions.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.19.7.1f","Requirement","ECSS-E-ST-70-41_1331822",1,"Created","The event-action subservice shall process any valid instruction that is contained within a request to enable event-action definitions regardless of the presence of faulty instructions."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.19.8.3b","Requirement","ECSS-E-ST-70-41_1331843",1,"Created","Each request to delete event-action definitions shall contain one or more instructions to delete an event-action definition."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.19.8.6c","Requirement","ECSS-E-ST-70-41_1331858",1,"Created","Each instruction to report an event-action definition shall contain:\n1.\tthe system identifier of the event definition.","NOTE\tFor the system identifier of the event definition, refer to requirement 6.19.4b.1.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.20.4.1d","Requirement","ECSS-E-ST-70-41_1331873",1,"Created","The parameter management subservice shall reject any instruction to report a parameter value if:\n1.\tthat instruction refers to an unknown parameter."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.20.5.2b","Requirement","ECSS-E-ST-70-41_1331888",1,"Created","Each request to change raw memory parameter definitions shall contain one or more instructions to change a raw memory parameter definition."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.20.5.3a","Requirement","ECSS-E-ST-70-41_1331894",1,"Created","The parameter management subservice capability to change object memory parameter definitions shall be declared when specifying that subservice.","NOTE\tThe corresponding requests are of message type \"TC[20,5] change object memory parameter definitions\". \n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.21.5.1a","Requirement","ECSS-E-ST-70-41_1331918",1,"Created","The request sequencing subservice shall provide at least one of the following capabilities:\n1.\tthe capability to directly load a request sequence specified in clause 6.21.5.2;\n2.\tthe capability to load a request sequence by reference specified in clause 6.21.5.3;\n3.\tthe capability to load by reference and activate a request sequence specified in clause 6.21.5.6.","NOTE 1\tDirectly loading a request sequence means the corresponding load sequence request contains the requests that constitute the sequence.\nNOTE 1\tLoading a request sequence by reference means that the request sequence is already defined on-board within a file. The request to load that request sequence refers to that file.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.21.5.4b","Requirement","ECSS-E-ST-70-41_1331933",1,"Created","Each request to unload a request sequence shall contain exactly one instruction to unload a request sequence."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.21.5.6b","Requirement","ECSS-E-ST-70-41_1331945",1,"Created","Each request to load by reference and activate a request sequence shall contain exactly one instruction to load by reference and activate a request sequence."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.21.6d","Requirement","ECSS-E-ST-70-41_1331963",1,"Created","For each valid request to report the execution status of each request sequence, the request sequencing subservice shall generate a single request sequence execution status report that includes all related request sequence execution status notifications."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.21.7c","Requirement","ECSS-E-ST-70-41_1331966",1,"Created","Each instruction to checksum a request sequence shall contain:\n1.\tthe identifier of the request sequence to checksum."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.21.9a","Requirement","ECSS-E-ST-70-41_1331978",1,"Created","The following observables shall be defined for the request sequencing subservice:\n1.\tthe list of request sequence identifiers and associated execution status of the loaded request sequences, in an array of size corresponding to the maximum number of request sequences that can be contemporaneously loaded at any time."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.22.6.3.1a","Requirement","ECSS-E-ST-70-41_1331993",1,"Created","The position-based scheduling subservice shall maintain a status indicating whether the overall position-based schedule execution function is enabled or disabled.","NOTE\tThis status is named \"position-based schedule execution function status\".\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.22.6.6j","Requirement","ECSS-E-ST-70-41_1332017",1,"Created","For each valid request to insert activities into the position-based schedule, the position-based scheduling subservice shall:\n1.\tif sub-schedules are supported and the sub-schedule specified in that request is unknown:\n(a)\tcreate that sub-schedule;\n(b)\tset its status to \"disabled\"."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.22.7.1b","Requirement","ECSS-E-ST-70-41_1332023",1,"Created","For each sub-schedule, the position-based scheduling subservice shall maintain a status indicating whether the schedule execution function for that sub-schedule is enabled or disabled.","NOTE\tThis status is named \"sub-schedule status\".\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.22.8.2.1d","Requirement","ECSS-E-ST-70-41_1332048",1,"Created","The position-based scheduling subservice shall reject any instruction to create a position-based scheduling group if any of the following conditions occurs:\n1.\tthat instruction refers to an already existing group;\n2.\tthe maximum number of groups that can be contemporaneously managed is already reached."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.22.8.2.2b","Requirement","ECSS-E-ST-70-41_1332053",1,"Created","Each request to delete position-based scheduling groups shall contain:\n1.\tone or more instructions to delete a position-based scheduling group, or\n2.\texactly one instruction to delete all position-based scheduling groups.","NOTE\tThe instructions to delete all position-based scheduling groups contain no argument.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.22.8.3.2b","Requirement","ECSS-E-ST-70-41_1332069",1,"Created","Each request to disable position-based scheduling groups shall contain:\n1.\tone or more instructions to disable a position-based scheduling group, or\n2.\texactly one instruction to disable all position-based scheduling groups.","NOTE\tThe instructions to disable all position-based scheduling groups contain no argument.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.22.9.2a","Requirement","ECSS-E-ST-70-41_1332083",1,"Created","The position-based scheduling subservice shall provide the capability to generate position-based schedule detail reports if any of the capabilities to detail-report scheduled activities is provided by that subservice.","NOTE 1\tThe corresponding reports are data reports of message type \"TM[22,10] position-based schedule detail report\".\nNOTE 1\tThe capabilities to detail-report scheduled activities are:\n·\tthe capability to detail-report all position-based scheduled activities (refer to clause 6.22.10.4);\n·\tthe capability to detail-report position-based scheduled activities identified by request identifier (refer to clause 6.22.11.5);\n·\tthe capability to detail-report the position-based scheduled activities identified by a filter (refer to clause 6.22.12.6).\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.22.10.4c","Requirement","ECSS-E-ST-70-41_1332098",1,"Created","For each valid instruction to detail-report all position-based scheduled activities, the position-based scheduling subservice shall generate, for each scheduled activity contained within the schedule, a single position-based schedule detail notification.","NOTE\tThe position-based schedule detail notification is defined in clause 6.22.9.2.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.22.11.4d","Requirement","ECSS-E-ST-70-41_1332120",1,"Created","The position-based scheduling subservice shall reject any instruction to summary-report a position-based scheduled activity identified by request identifier if:\n1.\tthat request identifier is unknown."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.22.11.5d","Requirement","ECSS-E-ST-70-41_1332128",1,"Created","The position-based scheduling subservice shall reject any instruction to detail-report a position-based scheduled activity identified by request identifier if:\n1.\tthat request identifier is unknown."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.22.12.3a","Requirement","ECSS-E-ST-70-41_1332141",1,"Created","The position-based scheduling subservice capability to delete the position-based scheduled activities identified by a filter shall be declared when specifying that subservice.","NOTE 1\tThe corresponding requests are of message type \"TC[22,6] delete the position-based scheduled activities identified by a filter\".\nNOTE 2\tThat capability implies that the subservice provides the capability of the position-window filtering function (refer to requirement 6.22.12.1a).\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.22.12.5e","Requirement","ECSS-E-ST-70-41_1332157",1,"Created","For each request to summary-report the position-based scheduled activities identified by a filter that is rejected, the position-based scheduling subservice shall generate a failed start of execution notification."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.23.3.4.1a","Requirement","ECSS-E-ST-70-41_1332173",1,"Created","For each on-board file system, the set of file attributes that the file management service can read shall be declared when specifying that subservice.","NOTE\tFor the list of file attributes supported by the on-board file system, refer to requirement 5.4.5d.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.23.4.2d","Requirement","ECSS-E-ST-70-41_1332192",1,"Created","The file handling subservice shall reject any request to report the attributes of a file if:\n1.\tthat request contains an instruction that refers to an object path that is invalid."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.23.4.3.2b","Requirement","ECSS-E-ST-70-41_1332203",1,"Created","Each request to unlock a file shall contain exactly one instruction to unlock a file."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.23.4.4f","Requirement","ECSS-E-ST-70-41_1332213",1,"Created","Each instruction to find files shall contain:\n1.\tthe repository path;\n2.\tthe search pattern.","NOTE\tWildcards are limited to the search pattern. The find files request cannot be used to search for files in multiple repositories by means of wildcard characters in the repository path.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.23.4.5.3b","Requirement","ECSS-E-ST-70-41_1332232",1,"Created","Whether the file handling subservice supports the renaming of directories shall be declared when specifying that subservice."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.23.5.1b","Requirement","ECSS-E-ST-70-41_1332248",1,"Created","A file in a remote file system shall be uniquely identified to the file copy subservice by a remote file path that is the combination of a repository path and a file name."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.23.5.2.3f","Requirement","ECSS-E-ST-70-41_1332264",1,"Created","For each valid instruction to move a file, the file copy subservice shall:\n1.\tuse the file copy operation identifier contained in that instruction as the identifier of the new file copy operation that it starts;\n2.\tfrom the file paths of the source file and the target file in that instruction, determine the underlying file transfer handler to use for moving the file;\n3.\trequest the underlying file transfer handler to move the source file to the target file.","NOTE\tThe file copy subservice uses an underlying file transfer handler to perform the file move. For example, this can be a file transfer layer or it can be a capability of a local file system. The choice is implementation dependent and it also depends on the file systems affected by the move request.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.23.5.3.2d","Requirement","ECSS-E-ST-70-41_1332278",1,"Created","The file copy subservice shall reject any instruction to resume a file copy operation if:\n1.\tthe identifier in that instruction refers to a file copy operation that does not exist."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.23.5.3.3d","Requirement","ECSS-E-ST-70-41_1332285",1,"Created","For each valid instruction to suspend all file copy operations involving a repository path, the file copy subservice shall:\n1.\tfor each on-going file copy operation, if either the source or the destination of the copy is constrained within the provided repository path, request the associated underlying file transfer handler to suspend that file copy operation."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","6.23.5.5.2d","Requirement","ECSS-E-ST-70-41_1332307",1,"Created","The file copy subservice shall reject any request to enable the periodic reporting of the file copy status if:\n1.\tthat request contains an instruction that specifies an invalid reporting interval."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","7.3.1c","Requirement","ECSS-E-ST-70-41_1332321",1,"Created","Tailoring this Standard for a mission, for each message type field that packet field format code is unknown, the packet field format code of that field shall be declared when specifying the application process that uses the related message type."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","7.3.7c","Requirement","ECSS-E-ST-70-41_1332345",1,"Created","The variable­length bit­string shall have the structure specified in Figure 7-3."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","7.3.9d","Requirement","ECSS-E-ST-70-41_1332364",1,"Created","The variable­length character­string format shall have the structure specified in Figure 7-5:"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","7.4.3.1c","Requirement","ECSS-E-ST-70-41_1332388",1,"Created","Each application process shall set the TM packet PUS version number of each telemetry packet it generates to 2.","NOTE\tThe TM packet PUS version number reflects the different versions of this Standard.\n·\tVersion 0 was used by the ESA PUS (ESA PSS-07-101).\n·\tVersion 1 corresponds to the ECSS-E-70-41A.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","7.4.3.2b","Requirement","ECSS-E-ST-70-41_1332400",1,"Created","The telemetry padding word size used by each application process shall be declared when specifying that application process.","NOTE\tThe telemetry padding word size is the multiple-of-bits number to apply when padding telemetry packets.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","7.4.4.1f","Requirement","ECSS-E-ST-70-41_1332411",1,"Created","For each request that it issues, each application process shall set the source ID field to its source identifier.","NOTE\tFor the source identifier, see requirement 5.4.11.2.1c.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.1.2.7a","Requirement","ECSS-E-ST-70-41_1332438",1,"Created","Each telemetry packet transporting a successful completion of execution verification report shall be of message subtype 7.","NOTE\tFor the corresponding system requirements, refer to clause 6.1.5.3.1.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.2.2.5a","Requirement","ECSS-E-ST-70-41_1332460",1,"Created","Each telemetry packet transporting a register dump report shall be of message subtype 6. ","NOTE\tFor the corresponding system requirements, refer to clause 6.2.5.3.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.3.2.1b","Requirement","ECSS-E-ST-70-41_1332483",1,"Created","For each telecommand packet transporting a request to create a housekeeping parameter report structure, the application data field shall have the structure specified in Figure 8-21."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.3.2.8b","Requirement","ECSS-E-ST-70-41_1332504",1,"Created","For each telecommand packet transporting a request to disable the periodic generation of diagnostic parameter reports, the application data field shall have the structure specified in Figure 8-28."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.3.2.12a","Requirement","ECSS-E-ST-70-41_1332515",1,"Created","Each telemetry packet transporting a diagnostic parameter report structure report shall be of message subtype 12. ","NOTE\tFor the corresponding system requirements, refer to clause 6.3.4.8.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.3.2.23b","Requirement","ECSS-E-ST-70-41_1332549",1,"Created","For each telemetry packet transporting a housekeeping parameter report periodic generation properties report, the source data field shall have the structure specified in Figure 8-43."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.3.2.31a","Requirement","ECSS-E-ST-70-41_1332572",1,"Created","Each telecommand packet transporting a request to remove parameter report definitions from a parameter functional reporting definition shall be of message subtype 43. ","NOTE\tFor the corresponding system requirements, refer to clause 6.3.5.6.2.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.4.2.4a","Requirement","ECSS-E-ST-70-41_1332591",1,"Created","Each telecommand packet transporting a request to enable the periodic parameter statistics reporting shall be of message subtype 4. ","NOTE\tFor the corresponding system requirements, refer to clause 6.4.6.2.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.5.2.2a","Requirement","ECSS-E-ST-70-41_1332613",1,"Created","Each telemetry packet transporting a low severity anomaly report shall be of message subtype 2. ","NOTE\tFor the corresponding system requirements, refer to clause 6.5.4.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.6.1a","Requirement","ECSS-E-ST-70-41_1332633",1,"Created","Each packet transporting a memory management message shall be of service type 6."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.6.1b","Requirement","ECSS-E-ST-70-41_1332634",1,"Created","Whether the memory management service supports multiple instructions within memory management related requests shall be declared when specifying that service."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.6.2.8a","Requirement","ECSS-E-ST-70-41_1332656",1,"Created","Each telemetry packet transporting a checked object memory data report shall be of message subtype 8. ","NOTE\tFor the corresponding system requirements, refer to clause 6.6.4.6.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.6.2.20b","Requirement","ECSS-E-ST-70-41_1332692",1,"Created","For each telecommand packet transporting a request to dump raw memory data areas to file, the application data field shall have the structure specified in Figure 8-84."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.8.1a","Requirement","ECSS-E-ST-70-41_1332700",1,"Created","Each packet transporting a function management message shall be of service type 8."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.11.2.7a","Requirement","ECSS-E-ST-70-41_1332733",1,"Created","Each telecommand packet transporting a request to time-shift scheduled activities identified by request identifier shall be of message subtype 7. ","NOTE\tFor the corresponding system requirements, refer to clause 6.11.9.3.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.11.2.9a","Requirement","ECSS-E-ST-70-41_1332739",1,"Created","Each telecommand packet transporting a request to detail-report time-based scheduled activities identified by request identifier shall be of message subtype 9. ","NOTE\tFor the corresponding system requirements, refer to clause 6.11.9.5.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.11.2.17b","Requirement","ECSS-E-ST-70-41_1332763",1,"Created","For each telecommand packet transporting a request to summary-report all time-based scheduled activities, the application data field shall be omitted."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.11.2.22b","Requirement","ECSS-E-ST-70-41_1332778",1,"Created","For each telecommand packet transporting a request to create time-based scheduling groups, the application data field shall have the structure specified in Figure 8-106."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.11.3c","Requirement","ECSS-E-ST-70-41_1332801",1,"Created","The values of the type of time window shall be as specified in Table 8-5."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.12.2.7f","Requirement","ECSS-E-ST-70-41_1332835",1,"Created","For limit-checking, the check type dependent criteria field of the modify parameter monitoring definitions request shall have the structure specified in Figure 8-121."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.12.2.9c","Requirement","ECSS-E-ST-70-41_1332846",1,"Created","For expected-value-checking, the check type dependent criteria field of the parameter monitoring definition report shall have the structure specified in Figure 8-125."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.12.2.15a","Requirement","ECSS-E-ST-70-41_1332866",1,"Created","Each telecommand packet transporting a request to enable the parameter monitoring function shall be of message subtype 15. ","NOTE\tFor the corresponding system requirements, refer to clause 6.12.3.5.1.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.12.2.22b","Requirement","ECSS-E-ST-70-41_1332884",1,"Created","For each telecommand packet transporting a request to unprotect functional monitoring definitions, the application data field shall have the structure specified in Figure 8-134."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.12.3.1c","Requirement","ECSS-E-ST-70-41_1332908",1,"Created","The values of the PMON status shall be as specified in Table 8-10."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.14.2.1a","Requirement","ECSS-E-ST-70-41_1332935",1,"Created","Each telecommand packet transporting a request to add report types to the application process forward-control configuration shall be of message subtype 1. ","NOTE\tFor the corresponding system requirements, refer to clause 6.14.3.4.1.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.14.2.3b","Requirement","ECSS-E-ST-70-41_1332947",1,"Created","For each telecommand packet transporting a request to report the content of the application process forward-control configuration, the application data field shall be omitted."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.14.2.6c","Requirement","ECSS-E-ST-70-41_1332961",1,"Created","To empty the housekeeping parameter report forward-control configuration, N1 shall be set to 0."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.14.2.12b","Requirement","ECSS-E-ST-70-41_1332982",1,"Created","For each telemetry packet transporting a diagnostic parameter report forward-control configuration content report, the source data field shall have the structure specified in Figure 8-155."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.15.2.1a","Requirement","ECSS-E-ST-70-41_1333002",1,"Created","Each telecommand packet transporting a request to enable the storage function of packet stores shall be of message subtype 1. ","NOTE\tFor the corresponding system requirements, refer to clause 6.15.3.3.2.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.15.2.6a","Requirement","ECSS-E-ST-70-41_1333024",1,"Created","Each telemetry packet transporting an application process storage-control configuration content report shall be of message subtype 6. ","NOTE\tFor the corresponding system requirements, refer to clause 6.15.4.4.3.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.15.2.11a","Requirement","ECSS-E-ST-70-41_1333041",1,"Created","Each telecommand packet transporting a request to change the open retrieval start time tag of packet stores shall be of message subtype 14. ","NOTE\tFor the corresponding system requirements, refer to clause 6.15.3.4.2.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.15.2.14a","Requirement","ECSS-E-ST-70-41_1333053",1,"Created","Each telecommand packet transporting a request to abort the by-time-range retrieval of packet stores shall be of message subtype 17. ","NOTE\tFor the corresponding system requirements, refer to clause 6.15.3.5.3.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.15.2.23b","Requirement","ECSS-E-ST-70-41_1333081",1,"Created","For each telecommand packet transporting a request to change a packet store type to circular, the application data field shall have the structure specified in Figure 8-179."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.15.2.28c","Requirement","ECSS-E-ST-70-41_1333101",1,"Created","To add all structure identifiers to the diagnostic parameter report storage-control configuration, N2 shall be set to 0."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.15.2.34a","Requirement","ECSS-E-ST-70-41_1333122",1,"Created","Each telecommand packet transporting a request to report the content of the diagnostic parameter report storage-control configuration shall be of message subtype 37. ","NOTE\tFor the corresponding system requirements, refer to clause 6.15.4.6.3.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.17.2.2b","Requirement","ECSS-E-ST-70-41_1333144",1,"Created","For each telemetry packet transporting an are-you-alive connection test report, the source data field shall be omitted."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.18.2.1a","Requirement","ECSS-E-ST-70-41_1333152",1,"Created","Each telecommand packet transporting a request to direct-load an OBCP shall be of message subtype 1. ","NOTE\tFor the corresponding system requirements, refer to clause 6.18.4.4.2.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.18.2.12a","Requirement","ECSS-E-ST-70-41_1333186",1,"Created","Each telecommand packet transporting a request to activate and execute one OBCP step shall be of message subtype 14. ","NOTE\tFor the corresponding system requirements, refer to clause 6.18.4.6.3.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.18.2.15b","Requirement","ECSS-E-ST-70-41_1333196",1,"Created","For each telecommand packet transporting a request to abort all OBCPs and report, the application data field shall be omitted."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.19.2.5a","Requirement","ECSS-E-ST-70-41_1333227",1,"Created","Each telecommand packet transporting a request to disable event-action definitions shall be of message subtype 5. ","NOTE\tFor the corresponding system requirements, refer to clause 6.19.7.2.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.19.3a","Requirement","ECSS-E-ST-70-41_1333246",1,"Created","The values of the event-action function status shall be as specified in Table 8-19."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.20.2.7c","Requirement","ECSS-E-ST-70-41_1333271",1,"Created","For absolute address addressing scheme, the addressing scheme dependent address field of the parameter definition report shall have the structure specified in Figure 8-226."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.21.2.5b","Requirement","ECSS-E-ST-70-41_1333291",1,"Created","For each telecommand packet transporting a request to abort a request sequence, the application data field shall have the structure specified in Figure 8-232."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.21.2.7b","Requirement","ECSS-E-ST-70-41_1333296",1,"Created","For each telemetry packet transporting a request sequence execution status report, the source data field shall have the structure specified in Figure 8-233."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.22.2.4b","Requirement","ECSS-E-ST-70-41_1333330",1,"Created","For each telecommand packet transporting a request to insert activities into the position-based schedule, the application data field shall have the structure specified in Figure 8-240."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.22.2.12a","Requirement","ECSS-E-ST-70-41_1333353",1,"Created","Each telecommand packet transporting a request to summary-report position-based scheduled activities identified by request identifier shall be of message subtype 12. ","NOTE\tFor the corresponding system requirements, refer to clause 6.22.11.4.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.22.2.19a","Requirement","ECSS-E-ST-70-41_1333371",1,"Created","Each telemetry packet transporting a position-based sub-schedule status report shall be of message subtype 19. ","NOTE\tFor the corresponding system requirements, refer to clause 6.22.7.2.3.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.22.2.25a","Requirement","ECSS-E-ST-70-41_1333393",1,"Created","Each telecommand packet transporting a request to disable position-based scheduling groups shall be of message subtype 25. ","NOTE\tFor the corresponding system requirements, refer to clause 6.22.8.3.2.\n"]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.22.2.25b","Requirement","ECSS-E-ST-70-41_1333394",1,"Created","For each telecommand packet transporting a request to disable position-based scheduling groups, the application data field shall have the structure specified in Figure 8-258."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.23.2.1b","Requirement","ECSS-E-ST-70-41_1333415",1,"Created","For each telecommand packet transporting a request to create a file, the application data field shall have the structure specified in Figure 8-261."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.23.2.8b","Requirement","ECSS-E-ST-70-41_1333437",1,"Created","For each telemetry packet transporting a found files report, the source data field shall have the structure specified in Figure 8-268."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.23.2.19b","Requirement","ECSS-E-ST-70-41_1333470",1,"Created","For each telecommand packet transporting a request to suspend all file copy operations involving a repository path, the application data field shall have the structure specified in Figure 8-279."]
["ECSS-E-ST-70-41C","ECSS - Current v1.0","8.23.2.23b","Requirement","ECSS-E-ST-70-41_1333482",1,"Created","For each telemetry packet transporting a file copy status report, the source data field shall have the structure specified in Figure 8-283."]
["ECSS-E-ST-70C","ECSS - Current v1.0","5.2.2.1c","Requirement","ECSS-E-ST-70_0060005",1,"Created","The output of the mission analysis shall be the mission analysis report (MAR) in conformance with Annex B."]
["ECSS-E-ST-70C","ECSS - Current v1.0","5.2.2.3a","Requirement","ECSS-E-ST-70_0060008",1,"Created","Space segment operability requirements shall be identified to ensure that the space segment can be operated during nominal situations and foreseeable contingency situations, in accordance with the mission requirements and objectives in terms of the quantity, quality and availability of mission products."]
["ECSS-E-ST-70C","ECSS - Current v1.0","5.3.2a","Requirement","ECSS-E-ST-70_0060026",1,"Created","Information for the in-orbit monitoring and control of the space segment (including payload/on-board instruments) and for the monitoring and control of the supporting ground segment shall be documented in the mission operations plan (MOP).\n    NOTE For example, procedures, rules, plans and schedules."]
["ECSS-E-ST-70C","ECSS - Current v1.0","5.3.2l","Requirement","ECSS-E-ST-70_0060037",1,"Created","The contents of operations procedures shall be in conformance with Annex I."]
["ECSS-E-ST-70C","ECSS - Current v1.0","5.6.1a","Requirement","ECSS-E-ST-70_0060053",1,"Created","The inputs to the operations validation process shall be the ones specified in Table 5-9."]
["ECSS-E-ST-70C","ECSS - Current v1.0","5.8.2.3b","Requirement","ECSS-E-ST-70_0060077",1,"Created","Detailed operations schedules shall be produced from the mission planning."]
["ECSS-E-ST-70C","ECSS - Current v1.0","5.8.2.3h","Requirement","ECSS-E-ST-70_0060083",1,"Created","Payload data shall be processed, archived and distributed to end users along with any necessary ancillary data."]
["ECSS-E-ST-70C","ECSS - Current v1.0","5.9.2a","Requirement","ECSS-E-ST-70_0060098",1,"Created","The space segment disposal operations process shall include:\n    1. Disposal operations analyses.\n    2. Development of products and processes for disposal.\n    3. Processes validation.\n    4. Final de-orbiting, ,re-entry or retrieval operations, and\n    5. Disposal or recycling of retrieved space segment elements.\n        NOTE 1 As defined in ECSS-E-ST-10, disposal constitutes the tasks, actions, and activities to be performed, and the system elements used, to ensure mission termination without degradation to the environment.\n        NOTE 2 The initial disposal operations concept is provided via the MDD and OCRD and further elaborated in the MOCD."]
["ECSS-E-ST-70C","ECSS - Current v1.0","6.2.2.3c","Requirement","ECSS-E-ST-70_0060112",1,"Created","The architecture shall cover integrated logistics support systems in accordance with the “Requirements for control of logistic activities” of ECSS-M-ST-70. "]
["ECSS-E-ST-70C","ECSS - Current v1.0","6.2.2.5c","Requirement","ECSS-E-ST-70_0060128",1,"Created","A logistics support plan shall be generated which responds to the logistics support requirements contained in the GSCRD, addressing the following issues:\n    1. Staffing, training and proficiency maintenance.\n    2. Spares provisioning.\n    3. Procurement of support equipment.\n    4. Provision of software support.\n    5. Packaging, handling, storage (PHS) and transport."]
["ECSS-E-ST-70C","ECSS - Current v1.0","6.4.2.2b","Requirement","ECSS-E-ST-70_0060149",1,"Created","The ground segment AIT plan shall:\n    1. Include the steps from the receipt of the first integration release to the completion of integration.\n    2. Cover the following aspects:\n        (a) The execution of each of the tests covered by the test specifications and production of the associated test documentation;\n        (b) the sequence in which the individual systems are integrated, taking account of expected readiness;\n        (c) the use of test systems or simulators;\n        (d) the integration with individual external elements;\n        (e) the relationship between these tests and planned pre-releases of the systems for ground segment AIT purposes."]
["ECSS-E-ST-70C","ECSS - Current v1.0","6.4.3a","Requirement","ECSS-E-ST-70_0060157",1,"Created","The outputs of the ground segment AIT and verification process shall be the ones specified in Table 6-6."]
["ECSS-E-ST-70C","ECSS - Current v1.0","6.6.2a","Requirement","ECSS-E-ST-70_0060170",1,"Created","The disposal engineering process shall include\n    1. Disposal analyses.\n    2. Development of products and processes for disposal.\n    3. Processes validation.\n    4. Disposal or recycling of ground systems.\n        NOTE As defined in ECSS-E-ST-10, disposal constitutes the tasks, actions, and activities to be performed, and the system elements used, to ensure mission termination without degradation to the environment."]
["ECSS-E-ST-70C","ECSS - Current v1.0","7.4.2a","Requirement","ECSS-E-ST-70_0060187",1,"Created","The main processes specified in Table 7-3 shall be carried out during phase C."]
["ECSS-E-ST-70C","ECSS - Current v1.0","7.6.3b","Requirement","ECSS-E-ST-70_0060203",1,"Created","During the utilisation phase (E2) in-orbit operations reviews (IOORs) shall be held on a regular basis to assess the performance of the space system, i.e. both space segment and ground segment .\n    NOTE For example, on a yearly basis."]
["ECSS-E-ST-70C","ECSS - Current v1.0","B.2.1<3>a","Requirement","ECSS-E-ST-70_0060221",1,"Created","The MAR shall identify all pertinent requirements and constraints arising from the following:\n    1. the mission definition, including the scientific objectives;\n    2. the spacecraft platform and payload design;\n    3. data recovery and data circulation;\n    4. the selected launcher;\n    5. orbit and ground station network."]
["ECSS-E-ST-70C","ECSS - Current v1.0","C.2.1<3.1>a","Requirement","ECSS-E-ST-70_0060232",1,"Created","The MOCD shall provide all the essential input information that drives or constrains the operations concepts."]
["ECSS-E-ST-70C","ECSS - Current v1.0","C.2.1<5.2>a","Requirement","ECSS-E-ST-70_0060242",1,"Created","The MOCD shall describe the concept for the planning and scheduling of space and ground segment operations, including:\n    1. user request management;\n    2. space segment routine operations;\n    3. ground segment maintenance requests;\n    4. constraints management;\n    5. resources management (space and ground);\n    6. conflict resolution;\n    7. space segment operations scheduling;\n    8. ground segment operations scheduling."]
["ECSS-E-ST-70C","ECSS - Current v1.0","E.2.1<4.3>a","Requirement","ECSS-E-ST-70_0060262",1,"Created","The system-level configurations shall include the following:\n    1. drawings of the overall satellite configuration in all mission phases;\n        NOTE Launch, separation, following deployments;\n            · definition of the satellite reference axes system(s);\n            · drawings of the platform and equipment layouts."]
["ECSS-E-ST-70C","ECSS - Current v1.0","E.2.1<5.3>d","Requirement","ECSS-E-ST-70_0060277",1,"Created","For the application process service software, the SSUM shall:\n    1. describe the services implemented making cross-reference to ECSS-E-ST-70-41 “Telemetry and telecommand packet utilization”, as tailored for the mission.\n    2. summarize all telemetry and telecommand structures including the conditions under which they are generated, the generation frequency, content and interpretation."]
["ECSS-E-ST-70C","ECSS - Current v1.0","E.2.1<5.8>c","Requirement","ECSS-E-ST-70_0060293",1,"Created","The data processing algorithms necessary to interpret the payload telemetry on-ground shall be provided."]
["ECSS-E-ST-70C","ECSS - Current v1.0","G.2.1<3.2>a","Requirement","ECSS-E-ST-70_0060307",1,"Created","The MOP shall contain the rules and criteria governing the conduct of mission operations, including:\n    1. launch hold criteria;\n    2. the principles and mechanisms for the routine and foreseen contingency operations of the mission;\n    3. rules and criteria for emergencies and anomalies not covered by existing contingency procedures. This relates to situations arising from multiple or unforeseen failures for which no pre-defined recovery action exists;\n    4. rules and criteria for transferring operations between different authorities (where applicable);\n    5. mission termination criteria."]
["ECSS-E-ST-70C","ECSS - Current v1.0","G.2.1<5>a","Requirement","ECSS-E-ST-70_0060314",1,"Created","The MOP shall contain the procedures for the nominal and contingency operations of the space and ground segments. "]
["ECSS-E-ST-70C","ECSS - Current v1.0","I.2.2<6>a","Requirement","ECSS-E-ST-70_0060337",1,"Created","An operations procedure shall list all conditions to be satisfied before procedure execution can be started. "]
["ECSS-E-ST-70C","ECSS - Current v1.0","I.2.2<7.3>a","Requirement","ECSS-E-ST-70_0060345",1,"Created","The procedure shall contain the information about what to do in case of contingency.\n    NOTE This is necessary for those steps for which the system cannot be left as it is (e.g. when some critical on-board protection has been disabled as part of the execution, or when an activity started as part of this procedure has to be aborted when it goes wrong, as in an orbital manoeuvre). "]
["ECSS-E-ST-80C","ECSS - Current v1.0","5.1.2b","Requirement","ECSS-E-ST-80_0600008",1,"Created","A Security Management Plan shall be part of entity’s Information Security Management System (ISMS)."]
["ECSS-E-ST-80C","ECSS - Current v1.0","5.1.3.2e","Requirement","ECSS-E-ST-80_0600023",1,"Created","The Security Internal Auditor shall have direct reporting line to the high-level management of the project or mission."]
["ECSS-E-ST-80C","ECSS - Current v1.0","5.1.3.2i","Requirement","ECSS-E-ST-80_0600027",1,"Created","The responsibilities of the Security Internal Auditor shall be defined in the Security Management Plan.\nEXPECTED OUTPUT:\tSecurity Management Plan [MGT; KOM, SRR, and updated when needed]"]
["ECSS-E-ST-80C","ECSS - Current v1.0","5.2.2i","Requirement","ECSS-E-ST-80_0600053",1,"Created","Mission security requirements shall be captured in the Mission Security Policy and be flown down to System and sub-system like any other functional and non-functional requirement.\nEXPECTED OUTPUT:\tMission Security Policy [TS; KOM, SRR, PDR, CDR; updated when needed]"]
["ECSS-E-ST-80C","ECSS - Current v1.0","5.2.3e","Requirement","ECSS-E-ST-80_0600058",1,"Created","Incident handling capability shall be incorporated into the security monitoring capability of the mission."]
["ECSS-E-ST-80C","ECSS - Current v1.0","5.3.2t","Requirement","ECSS-E-ST-80_0600083",1,"Created","System security engineering requirements shall be included in the system security engineering plan.\nEXPECTED OUTPUT:\tSystem Security Engineering Plan [TS; SRR, PDR, CDR, QR]"]
["ECSS-E-ST-80C","ECSS - Current v1.0","5.4.1b","Requirement","ECSS-E-ST-80_0600098",1,"Created","The pre-defined acceptable security risk level shall be agreed by the security risk owner.\nEXPECTED OUTPUT:\tMission Security Policy [TS; KOM, SRR, PDR, CDR; updated when needed]","NOTE\tThe pre-defined acceptable security risk is called “risk appetite”.\n"]
["ECSS-E-ST-80C","ECSS - Current v1.0","5.4.1m","Requirement","ECSS-E-ST-80_0600109",1,"Created","Where identified security risk mitigation strategies conflict with other types of risk, most notably safety, environmental risk and dependability they shall be agreed with the risk owner(s)."]
["ECSS-E-ST-80C","ECSS - Current v1.0","5.4.3d","Requirement","ECSS-E-ST-80_0600128",1,"Created","The security risk analysis shall be updated based on findings of the security audits.\nEXPECTED OUTPUT:\tSecurity audits report [SF; QR, AR, ORR]."]
["ECSS-E-ST-80C","ECSS - Current v1.0","5.4.4b","Requirement","ECSS-E-ST-80_0600130",1,"Created","The vulnerability management policy shall include at least the following:\n1.\tThe vulnerability scoring methodology to be used to assess the severity of the identified vulnerabilities;\n2.\tThe sources (“feeds”) of known vulnerabilities applicable to the system;\n3.\tA mechanism/methodology to automatically correlate the system inventory with known vulnerabilities on COTS and FOSS used in the system (passive vulnerability assessment);\n4.\tThe importance of the system and information assets in terms of Confidentiality, Integrity and Availability (known also as “Security Sensitivity” or “Security Profile” of the assets).","NOTE\tThe importance of a system and information assets in terms of Confidentiality, Integrity and Availability can be assessed using a security risk assessment.\n"]
["ECSS-I-ST-30-10C","ECSS - Current v1.0","5.2.2c","Requirement","ECSS-I-ST-30-10_1610003",1,"Created","The IPS function shall ensure that each requirement for the lower-level elements has been validated and verified."]
["ECSS-I-ST-30-10C","ECSS - Current v1.0","5.3.9.3a","Requirement","ECSS-I-ST-30-10_1610018",1,"Created","The IPS function shall specify and verify the Information System (IS) requirements before entry into service."]
["ECSS-I-ST-30-10C","ECSS - Current v1.0","A.2.1<8>d","Requirement","ECSS-I-ST-30-10_1610041",1,"Created","The IPSP shall describe the measures to ensure the data quality, their integrity and consistency."]
["ECSS-I-ST-30-10C","ECSS - Current v1.0","B.2.1<5>a","Requirement","ECSS-I-ST-30-10_1610048",1,"Created","The PSAP shall describe the logistic data development, data documentation and data exchange."]
["ECSS-M-ST-10-01C","ECSS - Current v1.0","5.2b","Requirement","ECSS-M-ST-10-01_0310007",1,"Created","The members of the review authority shall be appointed by the consumer organization."]
["ECSS-M-ST-10-01C","ECSS - Current v1.0","5.3.4a","Requirement","ECSS-M-ST-10-01_0310022",1,"Created","The review team leader shall manage the activities of the review team."]
["ECSS-M-ST-10-01C","ECSS - Current v1.0","5.6c","Requirement","ECSS-M-ST-10-01_0310042",1,"Created","The content of the RID form shall conform to the DRD in Annex B."]
["ECSS-M-ST-10-01C","ECSS - Current v1.0","B.2.1a","Requirement","ECSS-M-ST-10-01_0310052",1,"Created","A RID shall contain at least the following information:\n    1. Issue raised and reference of the applicable document violated\n    2. Originator recommendation to resolve the issue\n    3. Classification in major or minor\n    4. Endorsement of the RID by the review team\n    5. Response from the supplier\n    6. Concurrence (or not) of the review team with the supplier response\n    7. Identification of action items\n    8. Confirmation of RID status or close-out reference\n    9. Any attached document supporting the issue.\n        NOTE An example of a RID form is provided in Figure B-1."]
["ECSS-M-ST-10C Rev. 1","ECSS - Current v1.0","5.2.1.2a","Requirement","ECSS-M-ST-10_0010014",1,"Created","The supplier shall set up the project management organization in such a way that adequate resources are allocated to the project to ensure timely completion of the business agreement."]
["ECSS-M-ST-10C Rev. 1","ECSS - Current v1.0","5.2.3.1d","Requirement","ECSS-M-ST-10_0010039",1,"Created","The final audit report shall not be divulged without the agreement of the audited supplier."]
["ECSS-M-ST-10C Rev. 1","ECSS - Current v1.0","5.2.3.3c","Requirement","ECSS-M-ST-10_0010043",1,"Created","The supplier shall perform audits of his own project activities and of the project activities of his lower tier supplier(s) to verify conformance with project requirements."]
["ECSS-M-ST-10C Rev. 1","ECSS - Current v1.0","5.3o","Requirement","ECSS-M-ST-10_0010060",1,"Created","Each WP shall have a single responsible WP manager."]
["ECSS-M-ST-10C Rev. 1","ECSS - Current v1.0","A.2.1<6>a","Requirement","ECSS-M-ST-10_0010073",1,"Created","The PMP shall describe the configuration, information and documentation management approach, as defined in ECSS-M-ST-40, Annex A."]
["ECSS-M-ST-10C Rev. 1","ECSS - Current v1.0","B.2.1<3>e","Requirement","ECSS-M-ST-10_0010089",1,"Created","When recurrent products from previous space projects are used, they shall be identified in the tree structure."]
["ECSS-M-ST-40C Rev. 1","ECSS - Current v1.0","5.2.1.3f","Requirement","ECSS-M-ST-40_0320012",1,"Created","The responsibility for classifying information shall rest solely with the originating organization."]
["ECSS-M-ST-40C Rev. 1","ECSS - Current v1.0","5.2.2e","Requirement","ECSS-M-ST-40_0320019",1,"Created","Configuration management processes shall interface with logistic and maintenance processes to determine up to which level of product the CM process shall be applied."]
["ECSS-M-ST-40C Rev. 1","ECSS - Current v1.0","5.3.1.5f","Requirement","ECSS-M-ST-40_0320033",1,"Created","All product items subject to major nonconformances shall receive supplemental identification to provide a link to the departure authorization document."]
["ECSS-M-ST-40C Rev. 1","ECSS - Current v1.0","5.3.1.6k","Requirement","ECSS-M-ST-40_0320049",1,"Created","Digital data media shall be identified by the following:\n    1. CI identifier\n    2. File names\n    3. Version and issue\n    4. Date of generation\n    5. Generating entity\n    6. Total number of delivered media per information set (1 of ...)."]
["ECSS-M-ST-40C Rev. 1","ECSS - Current v1.0","5.3.2.2i","Requirement","ECSS-M-ST-40_0320064",1,"Created","The evaluation shall be transmitted to the customer for information."]
["ECSS-M-ST-40C Rev. 1","ECSS - Current v1.0","5.3.3.1b","Requirement","ECSS-M-ST-40_0320084",1,"Created","Each supplier shall provide configuration status accounting reports in conformance with Annex F, configuration status accounting reports DRD."]
["ECSS-M-ST-40C Rev. 1","ECSS - Current v1.0","5.3.4.1a","Requirement","ECSS-M-ST-40_0320094",1,"Created","At SRR, the functional configuration definition shall be verified against mission objectives."]
["ECSS-M-ST-40C Rev. 1","ECSS - Current v1.0","5.3.7.1c","Requirement","ECSS-M-ST-40_0320105",1,"Created","The relevant project information/documentation shall be accessible to all authorized project members. "]
["ECSS-M-ST-40C Rev. 1","ECSS - Current v1.0","5.3.7.2.5b","Requirement","ECSS-M-ST-40_0320124",1,"Created","Changes to information/documentation and their justification shall be traceable within the information /documentation."]
["ECSS-M-ST-40C Rev. 1","ECSS - Current v1.0","5.3.7.3.2f","Requirement","ECSS-M-ST-40_0320139",1,"Created","Digitally signed information shall provide indication that the information has been digitally signed. "]
["ECSS-M-ST-40C Rev. 1","ECSS - Current v1.0","5.3.7.5e","Requirement","ECSS-M-ST-40_0320156",1,"Created","Access to classified information/documentation shall be restricted to authorized personnel."]
["ECSS-M-ST-40C Rev. 1","ECSS - Current v1.0","A.2.1<4.2>a","Requirement","ECSS-M-ST-40_0320169",1,"Created","The configuration management plan shall identify, name, and describe the documented physical and functional characteristics of the information to be maintained under configuration management control for the programme or project."]
["ECSS-M-ST-40C Rev. 1","ECSS - Current v1.0","A.2.1<4.5>b","Requirement","ECSS-M-ST-40_0320177",1,"Created","The configuration management plan shall define the process and data to incorporate the supplier developed items into programme or project configuration management and to coordinate changes to these items. "]
["ECSS-M-ST-40C Rev. 1","ECSS - Current v1.0","A.2.1<5.7>a","Requirement","ECSS-M-ST-40_0320199",1,"Created","The configuration management plan shall describe the process and content for reporting the status of information items."]
["ECSS-M-ST-40C Rev. 1","ECSS - Current v1.0","C.2.1<2>a","Requirement","ECSS-M-ST-40_0320208",1,"Created","The configuration item data list shall list the applicable and reference documents in support to the generation of the document."]
["ECSS-M-ST-40C Rev. 1","ECSS - Current v1.0","E.2.1<11>a","Requirement","ECSS-M-ST-40_0320229",1,"Created","The SCF shall include any auxiliary information to describe the software configuration."]
["ECSS-M-ST-60C","ECSS - Current v1.0","7.1.3c","Requirement","ECSS-M-ST-60_0300007",1,"Created","The CCS shall be maintained up to date during the project’s life cycle."]
["ECSS-M-ST-60C","ECSS - Current v1.0","9.1.1a","Requirement","ECSS-M-ST-60_0300022",1,"Created","The rates and cost structure of the companies shall be approved by the relevant national authority or international organization."]
["ECSS-M-ST-60C","ECSS - Current v1.0","9.2.5b","Recommendation","ECSS-M-ST-60_0300135",1,"Created","The Price Variation Mechanism should include the following information, mutually agreed by the parties:\n    1. Amounts that are the basis of the price variation computation;\n    2. Indices, generally reflecting the evolution of raw material prices and of the remuneration of labour categories representative of the project activities;\n    3. A price escalation formula associating the two elements mentioned above, defining how the revised price (cost or fee, as applicable) is computed."]
["ECSS-M-ST-60C","ECSS - Current v1.0","9.3.1.1c","Requirement","ECSS-M-ST-60_0300043",1,"Created","The OBCP shall be used as the reference for all Control Work Packages."]
["ECSS-M-ST-60C","ECSS - Current v1.0","B.2.1b","Requirement","ECSS-M-ST-60_0300067",1,"Created","When defining the schedule, the total float for each activity with respect to the agreed milestones shall be available."]
["ECSS-M-ST-60C","ECSS - Current v1.0","F.2.1<3.4>a","Requirement","ECSS-M-ST-60_0300082",1,"Created","The cost estimate plan shall explain:\n    1. How the methods are selected in relation with the class of estimate and in particular the expected level of accuracy.\n        NOTE For example: are cost items estimated using several independent methods?\n    2. How the total cost is obtained, including those items derived by application of cost-to-cost relations to other items."]
["ECSS-M-ST-60C","ECSS - Current v1.0","G.2.1<6>a","Requirement","ECSS-M-ST-60_0300093",1,"Created","The customer and the supplier shall mutually agree in advance on the template format and the level of details to be produced. "]
["ECSS-M-ST-60C","ECSS - Current v1.0","J.2.1<2>a","Requirement","ECSS-M-ST-60_0300111",1,"Created","The cost and manpower report shall include:\n    1. Reporting Period Start\n    2. Reporting Period Finish\n    3. For each Control Work Package (CWP):\n        (a) CWP Number\n        (b) CWP Title\n        (c) For the period considered and cumulative from project start, in line with the applicable category identified in the CBS:\n\t- Current planned man-hours, quantities, and costs as per CBCP\n\t- Actual man-hours, quantities, and costs\n\t- Deviation on man-hours, quantities and costs (planned vs. actual)\n    4. CWP totals for the above\n    5. A summary of the above costs for each business agreement of the project"]
["ECSS-M-ST-60C","ECSS - Current v1.0","K.2.1<2>a","Requirement","ECSS-M-ST-60_0300114",1,"Created","The OBCP (respectively CBCP) shall list the applicable and reference documents supporting the generation of the document, such as the applicable business agreements, minutes of meeting, complete list of the agreed CCNs taken into account."]
["ECSS-M-ST-80C","ECSS - Current v1.0","7.2.10a","Requirement","ECSS-M-ST-80_0340010",1,"Created","Residual risks at the end of a risk management cycle shall be submitted to the appropriate management level, as defined in the risk management plan, for acceptance.\n    ","NOTE The aim is formal acceptance of residual risks at the appropriate management level."]
["ECSS-M-ST-80C","ECSS - Current v1.0","7.2.11a","Requirement","ECSS-M-ST-80_0340011",1,"Created","Risks shall be monitored, communicated, and results shall be displayed in conformance with risk assessment report DRD, Annex C.","NOTE The aim is to ensure complete and systematic control of the implementation of risk management activities."]
["ECSS-M-ST-80C","ECSS - Current v1.0","A.2.2a","Permission","ECSS-M-ST-80_0340071",1,"Created","The response to this DRD may be combined with the response to the risk management plan DRD, ECSS-M-ST-80 Annex B."]
["ECSS-M-ST-80C","ECSS - Current v1.0","B.2.1<5>a","Requirement","ECSS-M-ST-80_0340041",1,"Created","The risk management plan shall describe the structure, the rules and the procedures used to document the results of the risk management and the follow-up process."]
["ECSS-M-ST-80C","ECSS - Current v1.0","C.2.1<1>a","Requirement","ECSS-M-ST-80_0340056",1,"Created","The assessment report shall introduce the following items:\n    1. The purpose and objective of the risk assessment report;\n    2. A brief description of what was done during the identification and assessment exercise, and its outcome;\n    3. Identification of organizations that contributed to the preparation of the document."]
["ECSS-Q-ST-10-04C","ECSS - Current v1.0","5.1.1d","Requirement","ECSS-Q-ST-10-04_0180004",1,"Created","The supplier shall define specific control measures for the critical items."]
["ECSS-Q-ST-10-04C","ECSS - Current v1.0","5.2.4.2a","Requirement","ECSS-Q-ST-10-04_0180025",1,"Created","The supplier shall identify means by which critical items can be controlled.\n    ","NOTE Refer to the examples of CI control measures in the form of design, operation, test and inspection related means and associated actions in Annex D."]
["ECSS-Q-ST-10-04C","ECSS - Current v1.0","5.2.5.1a","Requirement","ECSS-Q-ST-10-04_0180034",1,"Created","The supplier shall assess and review all critical items periodically for status."]
["ECSS-Q-ST-10-04C","ECSS - Current v1.0","5.3.4e","Requirement","ECSS-Q-ST-10-04_0180050",1,"Created","At the end of the AR, the supplier shall verify the action closure for open critical items and shall provide it for customer approval."]
["ECSS-Q-ST-10-04C","ECSS - Current v1.0","A.2.1<9>b","Requirement","ECSS-Q-ST-10-04_0180062",1,"Created","In case of closed action, the list shall provide the reference to the close-out document."]
["ECSS-Q-ST-10-09C Rev. 1","ECSS - Current v1.0","5.2.2.2c","Requirement","ECSS-Q-ST-10-09_0350017",1,"Unchanged","In case of doubt, the internal NRB shall classify nonconformances as major."]
["ECSS-Q-ST-10-09C Rev. 1","ECSS - Current v1.0","5.2.3.3b","Requirement","ECSS-Q-ST-10-09_0350035",1,"Unchanged","The customer NRB shall decide if additional analyses are needed from the supplier to assess the cause and consequences of a nonconformance and to support its disposition. "]
["ECSS-Q-ST-10-09C Rev. 1","ECSS - Current v1.0","5.4.1a","Requirement","ECSS-Q-ST-10-09_0350047",1,"Unchanged","The supplier shall implement disposition by performing actions defined by the NRB and approved RFWs and RFDs."]
["ECSS-Q-ST-10-09C Rev. 1","ECSS - Current v1.0","5.5.2c","Recommendation","ECSS-Q-ST-10-09_0350145",1,"Created","The database should contain information related to both minor and major NCRs.","The amount of information stored should be sufficient to allow statistical and trend analysis."]
["ECSS-Q-ST-10-09C Rev. 1","ECSS - Current v1.0","6.3.2.2c","Requirement","ECSS-Q-ST-10-09_0350086",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-10-09C Rev. 1","ECSS - Current v1.0","A.2.1<1>a","Requirement","ECSS-Q-ST-10-09_0350092",1,"Unchanged","The NCR shall identify the supplier of the nonconforming item."]
["ECSS-Q-ST-10-09C Rev. 1","ECSS - Current v1.0","A.2.1<14>b","Requirement","ECSS-Q-ST-10-09_0350107",1,"Unchanged","The NCR shall include the name and organization group of the NC observer."]
["ECSS-Q-ST-10-09C Rev. 1","ECSS - Current v1.0","A.2.1<29>a","Requirement","ECSS-Q-ST-10-09_0350122",1,"Unchanged","The NCR shall contain the document identification number of the failure analysis report on customer NRB level."]
["ECSS-Q-ST-10-09C Rev. 1","ECSS - Current v1.0","B.2.1<4>a","Requirement","ECSS-Q-ST-10-09_0350137",1,"Unchanged","The NCR status shall provide short description of the nonconformance."]
["ECSS-Q-ST-10C Rev.1","ECSS - Current v1.0","5.1.3b","Requirement","ECSS-Q-ST-10_0360016",1,"Unchanged","The Product Assurance plan shall be prepared in conformance with DRD in Annex A."]
["ECSS-Q-ST-10C Rev.1","ECSS - Current v1.0","5.2.1h","Requirement","ECSS-Q-ST-10_0360025",1,"Informative Change","The PA manager shall ensure that a qualification programme is defined, approved and maintained by the relevant organization.","NOTE \tRequirement for the qualification programme are addressed in ECSS-Q-ST-20, ECSS-Q-ST-60, ECSS-Q-ST-70, ECSS-Q-ST-80, ECSS-E-ST-10-02 and ECSS-E-ST-10-03.\n"]
["ECSS-Q-ST-10C Rev.1","ECSS - Current v1.0","5.2.3a","Requirement","ECSS-Q-ST-10_0360033",1,"Unchanged","The supplier shall perform audits on his own performance to verify the implementation and effectiveness of the provisions defined in the PA plan.","NOTE \t1\tAudits can be performed by sampling on various projects or by periodic audits of the supplier quality system.\nNOTE \t2\tThe general contents of project audits are detailed in ECSS-M-ST-10 clause 5.2.3.\n"]
["ECSS-Q-ST-10C Rev.1","ECSS - Current v1.0","5.2.9d","Requirement","ECSS-Q-ST-10_0360051",1,"Unchanged","The supplier shall participate in the alert system organized by the customer or other sources, by:\n1.\tassessment of the impact of incoming alerts to project work, and definition, implementation and follow-up of necessary corrective actions at any contractual level.\n2.\tdistribution of incoming alerts to the possible affected users within the project.","NOTE \tThe alert system is set up for the prompt interchange of information on failures or problems which can affect more than one user, or can recur in other projects or circumstances, if no preventive actions are taken.\n"]
["ECSS-Q-ST-10C Rev.1","ECSS - Current v1.0","B.2.2a","Permission","ECSS-Q-ST-10_0360074",1,"Created","The form may be a table which contains the here above information of B.2.1 or reference to separate document.","NOTE \tAn example of such a table is shown in Figure B-1.\n"]
["ECSS-Q-ST-20-07C","ECSS - Current v1.0","5.2.2b","Requirement","ECSS-Q-ST-20-07_0370017",1,"Created","The facility description shall be provided to the customer upon request."]
["ECSS-Q-ST-20-07C","ECSS - Current v1.0","5.4.1d","Requirement","ECSS-Q-ST-20-07_0370029",1,"Created","Where contracted and additional technical and key personnel are used, the space test centre shall demonstrate that such personnel are competent and that they work in compliance with the space test centre's quality and safety management system."]
["ECSS-Q-ST-20-07C","ECSS - Current v1.0","5.5.2b","Requirement","ECSS-Q-ST-20-07_0370048",1,"Created","In addition to environmental parameters specified in the requirement 5.5.2a, the space test centre shall assess the impacts of other parameters specified by the customer that affect the test specimen's environmental conditions or the test results.","NOTE\tThese parameters can include among others the following: light level, electromagnetic radiation, magnetic cleanliness, vibration, ionising radiation, and acoustic environment."]
["ECSS-Q-ST-20-07C","ECSS - Current v1.0","5.5.3g","Requirement","ECSS-Q-ST-20-07_0370059",1,"Created","For a space test centre where flight hardware is exposed, the minimum cleanliness level of the environment for airborne particles shall be ISO class 8."]
["ECSS-Q-ST-20-07C","ECSS - Current v1.0","5.6.1e","Requirement","ECSS-Q-ST-20-07_0370068",1,"Created","The space test centre shall demonstrate that personnel are trained on the maintenance and operation of the new or modified test facility."]
["ECSS-Q-ST-20-07C","ECSS - Current v1.0","5.6.3i","Requirement","ECSS-Q-ST-20-07_0370088",1,"Created","If the requirement 5.6.3h is not met, the space test centre shall justify the lower tier supplier selection."]
["ECSS-Q-ST-20-07C","ECSS - Current v1.0","5.6.5a","Requirement","ECSS-Q-ST-20-07_0370103",1,"Created","For each facility, new or existing, a risk assessment covering all operational and non-operational aspects as well as health and safety risks shall be conducted and documented. "]
["ECSS-Q-ST-20-07C","ECSS - Current v1.0","5.7.3d","Requirement","ECSS-Q-ST-20-07_0370119",1,"Created","The planning shall demonstrate the compatibility of the design of the test processes with the infrastructure, the test facilities, the test execution, and the applicable test procedures."]
["ECSS-Q-ST-20-07C","ECSS - Current v1.0","5.7.4.3e","Requirement","ECSS-Q-ST-20-07_0370133",1,"Created","Any activity carried out by the space test centre on the test specimen shall be authorized by the customer."]
["ECSS-Q-ST-20-07C","ECSS - Current v1.0","5.7.4.4e","Requirement","ECSS-Q-ST-20-07_0370140",1,"Created","All lifting and hoisting equipment, including slings and accessories, shall be certified by an authorized body and covered by a valid certificate. "]
["ECSS-Q-ST-20-07C","ECSS - Current v1.0","5.9.1.1a","Requirement","ECSS-Q-ST-20-07_0370162",1,"Created","The space test centre, in cooperation with the designated safety representative, shall establish a safety programme to assure the safety of all space test centre personnel, including the customer and visitors, the test specimen, the test facilities and its associated infrastructure."]
["ECSS-Q-ST-20-07C","ECSS - Current v1.0","5.9.4h","Requirement","ECSS-Q-ST-20-07_0370178",1,"Created","Critical operations shall be performed under the surveillance of designated qualified staff."]
["ECSS-Q-ST-20-08C","ECSS - Current v1.0","4.2g","Requirement","ECSS-Q-ST-20-08_1170008",1,"Created","Test or stimulus points shall be accessible without the need to disconnect or deroute flight harness of an item of equipment."]
["ECSS-Q-ST-20-08C","ECSS - Current v1.0","5.3e","Requirement","ECSS-Q-ST-20-08_1170024",1,"Created","Supplier shall consolidate all inputs from lower level to build the Storage Plan:\n1.\tverify and apply consistency between all inputs,\n2.\tsynchronize all inputs to limit operation on hardware.","NOTE \tFor example to anticipate an operation in time to group with other."]
["ECSS-Q-ST-20-08C","ECSS - Current v1.0","5.4.1b","Requirement","ECSS-Q-ST-20-08_1170028",1,"Created","The storage configuration shall be verified before storage is authorized."]
["ECSS-Q-ST-20-08C","ECSS - Current v1.0","5.7a","Requirement","ECSS-Q-ST-20-08_1170053",1,"Created","An analysis shall be performed on the need to conserve the specific knowledge for product over the time to be used to derive the dispositions to be revisited during key points specified in the requirement 5.5.1c.","NOTE \t1\tTypical conservation topics include training, documentation, and lessons learned.\nNOTE \t2\tThe dispositions are recorded in the Storage Plan in conformance with Annex A."]
["ECSS-Q-ST-20-08C","ECSS - Current v1.0","6.2.1a","Requirement","ECSS-Q-ST-20-08_1170054",1,"Created","All GSE fixing points shall be able to be visually inspected.","NOTE \tThis requirements imply that attachment parts necessary to secure the flight hardware are clearly visible by design."]
["ECSS-Q-ST-20-08C","ECSS - Current v1.0","6.3.2f","Requirement","ECSS-Q-ST-20-08_1170078",1,"Created","In this perimeter, only operators involved in the operations shall be authorized."]
["ECSS-Q-ST-20-08C","ECSS - Current v1.0","6.3.4b","Requirement","ECSS-Q-ST-20-08_1170083",1,"Created","Non-interruptible sequence of operations shall be explained to the operators during the pre-operation briefing."]
["ECSS-Q-ST-20-08C","ECSS - Current v1.0","7.3g","Requirement","ECSS-Q-ST-20-08_1170099",1,"Created","After the transport, the entity taking the responsibility of the hardware shall:\n1.\tensure hardware integrity by a visual inspection, and a post transport test, in conformance with requirements 5.1f or 6.5.2.1e of ECSS-E-ST-10-03,\n2.\trelease the hardware for post transport activities."]
["ECSS-Q-ST-20-08C","ECSS - Current v1.0","7.6.1c","Requirement","ECSS-Q-ST-20-08_1170112",1,"Created","A nominated contact person at the sending entity, responsible for transport and at the transport company, shall be available on phone for the escort in case of need."]
["ECSS-Q-ST-20-08C","ECSS - Current v1.0","7.8.2b","Requirement","ECSS-Q-ST-20-08_1170131",1,"Created","The packages shall be marked with: “HANDLE WITH CARE”."]
["ECSS-Q-ST-20-10C","ECSS - Current v1.0","5.2.1.1a","Requirement","ECSS-Q-ST-20-10_1120014",1,"Created","In order to evaluate the possible use of OTS item the supplier shall investigate the existence of products already successfully qualified in similar application."]
["ECSS-Q-ST-20-10C","ECSS - Current v1.0","5.2.1.3d","Requirement","ECSS-Q-ST-20-10_1120021",1,"Created","The supplier shall identify all the OTS item functions which can lead to negative effects."]
["ECSS-Q-ST-20-10C","ECSS - Current v1.0","5.3.2.1.1c","Requirement","ECSS-Q-ST-20-10_1120035",1,"Created","The supplier shall identify the dependability technical risks in satisfying dependability requirements."]
["ECSS-Q-ST-20-10C","ECSS - Current v1.0","5.3.2.1.8a","Requirement","ECSS-Q-ST-20-10_1120051",1,"Created","The supplier shall ask the existing field data that justify the operational life claimed by the manufacturer. ","NOTE For example: Market feedback for the products, worst case analysis, possibility to get the internal parts activation energy characteristics and operating temperature."]
["ECSS-Q-ST-20-10C","ECSS - Current v1.0","5.3.2.3.2a","Requirement","ECSS-Q-ST-20-10_1120070",1,"Created","The supplier shall assess part purchase policy applied by the OTS item manufacturer.","NOTE Part quality level, multiple suppliers for each part type, part incoming inspection, burn in data, and mechanical tests."]
["ECSS-Q-ST-20-10C","ECSS - Current v1.0","5.4.1b","Requirement","ECSS-Q-ST-20-10_1120081",1,"Created","The supplier shall verify that the OTS item does not generate any detrimental mechanical effect within the operational environment."]
["ECSS-Q-ST-20-10C","ECSS - Current v1.0","5.4.3.2c","Requirement","ECSS-Q-ST-20-10_1120096",1,"Created","The OTS item new power supply shall be designed and manufactured by the supplier according to the space environment and constraints in accordance with ECSS-E-ST-20."]
["ECSS-Q-ST-20-10C","ECSS - Current v1.0","5.4.3.5b","Requirement","ECSS-Q-ST-20-10_1120107",1,"Created","For OTS items that exist in plastic cases only, the viability of upgrading their housing to a metallic one shall be investigated and implemented by the supplier, where feasible."]
["ECSS-Q-ST-20-10C","ECSS - Current v1.0","5.6.1.4a","Requirement","ECSS-Q-ST-20-10_1120126",1,"Created","The supplier shall verify that the procurement documentation of the OTS items are in accordance with the ECSS-Q-ST-20."]
["ECSS-Q-ST-20-10C","ECSS - Current v1.0","A.2.1<8>a","Requirement","ECSS-Q-ST-20-10_1120138",1,"Created","The OTS plan shall describe the:\n    1. procurement activities once the project has completed the OTS item selection and characterization processes;\n    2. activities for the configuration control to track any OTS item modification;\n    3. description of the procurement verification approach and its implementation;\n    4. product assurance approach and its implementation;\n    5. batch policy;\n    6. qualification activities and logic according to ECSS-E-ST-10, and ECSS-E-ST-10-02."]
["ECSS-Q-ST-20-30C","ECSS - Current v1.0","6.3.3a","Requirement","ECSS-Q-ST-20-30_1660016",1,"Created","[Not applicable]"]
["ECSS-Q-ST-20-30C","ECSS - Current v1.0","6.15.1a","Requirement","ECSS-Q-ST-20-30_1660033",1,"Created","Table 15-1 of IPC/WHMA-A-620E-S is not applicable. Any broken strand shall be considered as a defect."]
["ECSS-Q-ST-20-30C","ECSS - Current v1.0","7.5h","Requirement","ECSS-Q-ST-20-30_1660056",1,"Created","There shall be no foreign particles entrapped underneath the shrinking sleeve.","NOTE\tExamples of a foreign particle trapped underneath a shrinking sleeve is shown in Figure 7‑5.\n"]
["ECSS-Q-ST-20-30C","ECSS - Current v1.0","7.7e","Requirement","ECSS-Q-ST-20-30_1660066",1,"Created","The braids of the different branches shall overlap for at least 30 mm or two times the diameter of the largest bundle, whichever is longer, at the breakout."]
["ECSS-Q-ST-20-30C","ECSS - Current v1.0","7.8e","Requirement","ECSS-Q-ST-20-30_1660081",1,"Created","The ends of the foil pieces shall be secured."]
["ECSS-Q-ST-20C Rev.2 Corr.1","ECSS - Current v1.0","5.2.5c","Requirement","ECSS-Q-ST-20_0380019",1,"Unchanged","The supplier shall be capable to trace backward the locations of materials, parts, sub-assemblies."]
["ECSS-Q-ST-20C Rev.2 Corr.1","ECSS - Current v1.0","5.2.6m","Requirement","ECSS-Q-ST-20_0380034",1,"Unchanged","The supplier shall ensure that inspection, measuring and test facilities, including both test hardware and test software are protected against adjustments, which can invalidate the calibration setting."]
["ECSS-Q-ST-20C Rev.2 Corr.1","ECSS - Current v1.0","5.2.8.2a","Requirement","ECSS-Q-ST-20_0380049",1,"Unchanged","When sampling plans are used the supplier shall define and justify the following:\n1.\tsample size, sample selection methods and criteria for inspection severity, \n2.\tacceptance / rejection criteria, and \n3.\tscreening of rejected lots."]
["ECSS-Q-ST-20C Rev.2 Corr.1","ECSS - Current v1.0","5.3.2.2a","Requirement","ECSS-Q-ST-20_0380060",1,"Unchanged","The supplier shall ensure that the objectives of the analysis are defined in relation with the development logic defined in the verification plan."]
["ECSS-Q-ST-20C Rev.2 Corr.1","ECSS - Current v1.0","5.3.2.4.1d","Requirement","ECSS-Q-ST-20_0380226",1,"Unchanged","The supplier QA manager shall ensure that a Verification Control Board (VCB) is established to monitor the qualification process.","NOTE\tVerification Control Board (VCB) is defined in ECSS-E-ST-10-02.\n"]
["ECSS-Q-ST-20C Rev.2 Corr.1","ECSS - Current v1.0","5.4.3c","Requirement","ECSS-Q-ST-20_0380086",2,"Unchanged","The supplier shall define the type and extent of surveillance by reviewing the following criteria:\n1.\tTesting or inspections cannot be accomplished by the supplier.\n2.\tVerification tests are destructive in nature and the quality cannot be verified solely by inspection or test at supplier’s facility.\n3.\tSupplies are designated for direct shipment from source to a customer site or the using site.\n4.\tManufacturing and AIV of complex equipment or subsystems.\n5.\tPast performance or quality history of the lower level supplier is marginal.\n6.\tFunctional criticality and technical complexity of the supplies.\n7.\tThe degree of responsibility placed on the procurement source.","NOTE \t1\tExamples for item 1: environments or test equipment not available at supplier’s facility.\nNOTE \t2\tExample for item 4: payloads.\n"]
["ECSS-Q-ST-20C Rev.2 Corr.1","ECSS - Current v1.0","5.5.1c","Requirement","ECSS-Q-ST-20_0380097",1,"Informative Change","Instructions shall direct the actual performance of manufacturing, assembly and integration operations and inspections, to ensure that the activities proceed in an orderly manner and according to the planned sequence."]
["ECSS-Q-ST-20C Rev.2 Corr.1","ECSS - Current v1.0","5.5.5c","Requirement","ECSS-Q-ST-20_0380115",2,"Unchanged","Sensitive items shall be processed or manufactured, inspected and tested in a controlled environment to prevent any degradation. "]
["ECSS-Q-ST-20C Rev.2 Corr.1","ECSS - Current v1.0","5.5.7.4a","Requirement","ECSS-Q-ST-20_0380131",1,"Unchanged","Contamination shall be minimized by operating in clean working areas and by proper handling, preservation, packaging and storage."]
["ECSS-Q-ST-20C Rev.2 Corr.1","ECSS - Current v1.0","5.5.9.1c","Requirement","ECSS-Q-ST-20_0380146",1,"Unchanged","The supplier shall establish and maintain records of temporary installations and removals."]
["ECSS-Q-ST-20C Rev.2 Corr.1","ECSS - Current v1.0","5.6.2c","Requirement","ECSS-Q-ST-20_0380157",1,"Unchanged","The supplier shall ensure that test equipment are designed such that their correct operation can be verified without having to apply them to the test item."]
["ECSS-Q-ST-20C Rev.2 Corr.1","ECSS - Current v1.0","5.6.4d","Requirement","ECSS-Q-ST-20_0380165",2,"Unchanged","Self-verification by the operators performing the test activities shall not be considered sufficient for critical characteristics."]
["ECSS-Q-ST-20C Rev.2 Corr.1","ECSS - Current v1.0","5.7.5.1a","Requirement","ECSS-Q-ST-20_0380185",1,"Unchanged","The supplier shall ensure that the items to be shipped from his plant are inspected before release and found to be complete, adequately preserved and packaged, correctly marked and accompanied by all the required documentation."]
["ECSS-Q-ST-20C Rev.2 Corr.1","ECSS - Current v1.0","5.8.4.3b","Requirement","ECSS-Q-ST-20_0380200",1,"Unchanged","The delivery board shall include QA representatives from the supplier and the customer."]
["ECSS-Q-ST-20C Rev.2 Corr.1","ECSS - Current v1.0","A.2.1<10>a","Requirement","ECSS-Q-ST-20_0380242",1,"Created","The Quality Assurance Plan shall describe the activities to be applied to fulfil the applicable Quality assurance requirements for ground support equipment (GSE) defined in ECSS-Q-ST-20 clause 5.8."]
["ECSS-Q-ST-30-02C","ECSS - Current v1.0","4.1d","Requirement","ECSS-Q-ST-30-02_0390004",1,"Created","The FMEA shall be used in the definition of:\n    1. failure tolerance design provisions (i.e. redundancy, inhibits, FDIR),\n    2. special test considerations,\n    3. maintenance actions (preventive or corrective),\n    4. operational constraints."]
["ECSS-Q-ST-30-02C","ECSS - Current v1.0","4.2c","Requirement","ECSS-Q-ST-30-02_0390009",1,"Created","For analyses lower than system level the severity level due to possible failure propagation shall be identified as level 1 for dependability.\n    NOTE For example, for analysis at subsystem and equipment levels."]
["ECSS-Q-ST-30-02C","ECSS - Current v1.0","4.6i","Requirement","ECSS-Q-ST-30-02_0390033",1,"Created","Failures requiring failure detection and recovery action in a time interval greater than the time to an irreversible consequence shall be identified and subjected to recommendation for corrective action."]
["ECSS-Q-ST-30-02C","ECSS - Current v1.0","4.6j","Requirement","ECSS-Q-ST-30-02_0390034",1,"Created","For electromechanical and electrical equipment, assembly or subsystem additional product design aspects shall include:\n    1. failure modes resulting from the location of the components, causing failure propagation due to components being mounted too close to each other;\n        NOTE The location of the components is considered for external failure propagation or internal failure propagation in case of internal redundancy.\n    2. failure modes resulting from multi-application of individual components;\n        NOTE Example of multi-applications is the use of one integrated circuit for two redundant paths.\n    3. failure of grounding or shielding or insulation.\n        NOTE Annex H gives examples of check-list items for electromechanical and electrical equipment, assembly or subsystem."]
["ECSS-Q-ST-30-02C","ECSS - Current v1.0","6.3c","Requirement","ECSS-Q-ST-30-02_0390060",1,"Created","The FMEA/FMECA shall be performed to provide the following results:\n    1. evaluation of the conformance of each design concept function to the system dependability and safety requirements;\n    2. identification of critical failure scenarios; \n    3. identification of needs of focused analyses;\n        NOTE For example: fault tree.\n    4. identification of the features to be implemented for each analysed function in order to meet the system dependability and safety requirements.\n        NOTE 1 Example of the identified features are: functional redundancies or inhibits, possible alternative implementations.\n        NOTE 2 A report for FMEA/FMECA is, typically, not required for phase A."]
["ECSS-Q-ST-30-02C","ECSS - Current v1.0","6.4c","Requirement","ECSS-Q-ST-30-02_0390063",1,"Created","The FMEA/FMECA shall:\n    1. support the trade-offs from the dependability and safety point of view;\n    2. support the definition of the requirements to be implemented in the product as redundancies, inhibits, operations to be followed to avoid hazards or loss of mission, and others, such as fail-safe, leak before burst, and maximum time allowable before compensation activation."]
["ECSS-Q-ST-30-02C","ECSS - Current v1.0","7.2d","Requirement","ECSS-Q-ST-30-02_0390081",1,"Created","In the performance of the System HSIA, the supplier shall integrate the HSIAs performed at one level lower than the level of the supplier."]
["ECSS-Q-ST-30-02C","ECSS - Current v1.0","8.3c","Requirement","ECSS-Q-ST-30-02_0390094",1,"Created","The severity of failure effects shall be identified by assigning a severity number (SN) according to a table agreed with the customer. \n    NOTE Table 8-1 gives an example of definitions for Severity Numbers (SN) for some categories of failure effects. It can be customised or completed depending on the process analyzed and on the purpose of the analysis."]
["ECSS-Q-ST-30-02C","ECSS - Current v1.0","8.6.4b","Requirement","ECSS-Q-ST-30-02_0390110",1,"Created","The modified situation shall be treated on the same process FMECA worksheet to identify the improvements.\n    NOTE The final closing of the action by the project can only be:\n        • acceptance according to case 1, or\n        • rejection according to case 2."]
["ECSS-Q-ST-30-02C","ECSS - Current v1.0","B.2.1<3>a","Requirement","ECSS-Q-ST-30-02_0390133",1,"Created","The FMEA worksheet shall contain\n    1. the name of the item or function being analysed, and \n    2. the block of the reliability block diagram that is applicable to the analysis entry."]
["ECSS-Q-ST-30-02C","ECSS - Current v1.0","B.2.1<9>a","Requirement","ECSS-Q-ST-30-02_0390139",1,"Created","The FMEA worksheet shall contain the severity classification category assigned to each failure mode according to the worst potential end effect of the failure (see clause 4.1 and 4.2)."]
["ECSS-Q-ST-30-02C","ECSS - Current v1.0","D.2.1<6>b","Requirement","ECSS-Q-ST-30-02_0390154",1,"Created","The HSIA form shall contain the identification of corresponding health signal (health signal = result of comparison between detected and reference values)."]
["ECSS-Q-ST-30-02C","ECSS - Current v1.0","E.2.1<6>a","Requirement","ECSS-Q-ST-30-02_0390169",1,"Created","The Process FMECA report shall include follow-on action to be presented to the project team responsible for final decisions.\n    NOTE 1 The follow-on actions (references for implementation, rejection, or analysis of alternative recommendations) apply to the updates of the report. \n    NOTE 2 In the case where company “CONFIDENTIAL” processes are documented, the report can be split into:\n        · a summary report including recommendations and unacceptable points (to be submitted to the customer);\n        · the detailed process FMECA worksheets (company confidential).\n    NOTE 3 See also clause 8.6 about “Follow-on actions”."]
["ECSS-Q-ST-30-09C","ECSS - Current v1.0","5.1.2c","Requirement","ECSS-Q-ST-30-09_0400003",1,"Created","Each availability requirement shall be a quantitative requirement."]
["ECSS-Q-ST-30-09C","ECSS - Current v1.0","5.2.5a","Requirement","ECSS-Q-ST-30-09_0400017",1,"Created","In the specific case that the availability is specified by an outage distribution and duration, and if a maximum duration is specified, a probability of exceeding this duration shall be associated.\n    NOTE 1 This can apply at subsystem level when a short service interruption is masked or filtered by the upper level function.\n    NOTE 2 For example, typically a GPS receiver temporary outage is tolerated by a navigation model. For this type of application, numerous short outages would be preferable to a few long ones."]
["ECSS-Q-ST-30-09C","ECSS - Current v1.0","6.3f","Requirement","ECSS-Q-ST-30-09_0400032",1,"Created","The results of availability analyses shall be reiterated in a timely manner through the design, integration processes and operation engineering to reflect the actual system baseline."]
["ECSS-Q-ST-30-09C","ECSS - Current v1.0","7.2.3a","Requirement","ECSS-Q-ST-30-09_0400044",1,"Created","During Phase C/D, the availability analysis shall cover the following aspects:\n    1. A review of the lower level analyses.\n    2. Consolidation of the input data (input data consistency check).\n    3. Support to the design, logistics and operations activities.\n    4. Contribution to design reviews.\n    5. Evaluation of the availability performance of the system or equipment baseline.\n    6. Identification of the critical parameters or points to be monitored or controlled.\n    7. Support to quality assurance activity during manufacture, integration and test, nonconformance review board (NRB) and failure review board.\n    8. Support flight readiness reviews."]
["ECSS-Q-ST-30-11C Rev.2","ECSS - Current v1.0","5.4.2e","Requirement","ECSS-Q-ST-30-11_0140016",1,"Unchanged","As an exception in case clause 5.4.2c is not compatible for specific repeated and incessant transient use conditions, for the parts types and parameters listed, load ratio shall not exceed the steady state derated values +10 % or 80 % of the steady state rated values, which ever is lower:\n1.\tConnectors: voltage, current\n2.\tCeramic Capacitors: voltage\n3.\tResistors: current \n4.\tDiodes: current\n5.\tTransistors_ bipolar , MOSFETs, power FETs: current."]
["ECSS-Q-ST-30-11C Rev.2","ECSS - Current v1.0","6.3.1f","Recommendation","ECSS-Q-ST-30-11_0140166",2,"Normative Change","Internal heating due to ESR can increase ageing and should be taken into account by applying a margin in temperature."]
["ECSS-Q-ST-30-11C Rev.2","ECSS - Current v1.0","6.6.1a","Recommendation","ECSS-Q-ST-30-11_0140169",2,"Normative Change","Internal heating due to ESR can increase ageing and should be taken into account by applying a margin in temperature."]
["ECSS-Q-ST-30-11C Rev.2","ECSS - Current v1.0","6.11.2a","Requirement","ECSS-Q-ST-30-11_0140050",1,"Unchanged","Parameters of connectors from family-group code 02-01, 02-02, 02-03, 02-07 and 02-09 shall be derated as per Table 6‑10."]
["ECSS-Q-ST-30-11C Rev.2","ECSS - Current v1.0","6.12.3c","Requirement","ECSS-Q-ST-30-11_0140061",1,"Unchanged","Maximum mating and de-mating cycles shall be limited to 50 cycles."]
["ECSS-Q-ST-30-11C Rev.2","ECSS - Current v1.0","6.20.2a","Requirement","ECSS-Q-ST-30-11_0140088",1,"Unchanged","Parameters of Integrated circuits from family-group code: 08-22, 08-23 and 08-24 shall be derated as per Table 6‑20."]
["ECSS-Q-ST-30-11C Rev.2","ECSS - Current v1.0","6.23.2d","Requirement","ECSS-Q-ST-30-11_0140192",1,"Created","Transistors parameters of custom designed MMICs shall be derated as per Table 6‑37 and Table 6‑38, for RF bipolar and RF field effect transistors, respectively."]
["ECSS-Q-ST-30-11C Rev.2","ECSS - Current v1.0","6.26.2.3a","Requirement","ECSS-Q-ST-30-11_0140116",2,"Normative Change","Parameters of Foil resistor (type RNC 90) shall be derated as per Table 6‑27."]
["ECSS-Q-ST-30-11C Rev.2","ECSS - Current v1.0","6.29.3a","Requirement","ECSS-Q-ST-30-11_0140136",1,"Unchanged","Only SEE radiation characterized MOSFETs shall be used in space applications."]
["ECSS-Q-ST-30-11C Rev.2","ECSS - Current v1.0","6.32.2b","Requirement","ECSS-Q-ST-30-11_0140144",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-30-11C Rev.2","ECSS - Current v1.0","6.33.3c","Requirement","ECSS-Q-ST-30-11_0140152",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-30-11C Rev.2","ECSS - Current v1.0","6.36.2a","Requirement","ECSS-Q-ST-30-11_0140162",1,"Unchanged","For hybrids, individual components shall be in conformance with their respective derating rules."]
["ECSS-Q-ST-30C Rev.1","ECSS - Current v1.0","4.9a","Requirement","ECSS-Q-ST-30_0410022",1,"Unchanged","The supplier shall maintain all data used for the dependability programme."]
["ECSS-Q-ST-30C Rev.1","ECSS - Current v1.0","5.3.2c","Requirement","ECSS-Q-ST-30_0410034",1,"Unchanged","For analyses lower than system level, the severity due to possible failure propagation shall be identified as level 1 for dependability. ","NOTE \tFor example, for analysis at subsystem, and equipment level\n"]
["ECSS-Q-ST-30C Rev.1","ECSS - Current v1.0","5.4.1e","Requirement","ECSS-Q-ST-30_0410128",1,"Created","The function criticality shall be assigned according to the categories of Table 5-2, without taking into account any compensating provisions.","NOTE \tContinuing functional decomposition into lower-level functions, to distinguish between functions that could lead to different feared events, is not considered as creating compensating provisions.\n"]
["ECSS-Q-ST-30C Rev.1","ECSS - Current v1.0","5.7b","Requirement","ECSS-Q-ST-30_0410053",1,"Unchanged","All recommendations from 5.7a shall be justified, documented and tracked."]
["ECSS-Q-ST-30C Rev.1","ECSS - Current v1.0","6.1b","Requirement","ECSS-Q-ST-30_0410057",1,"Unchanged","Preliminary identification and classification of undesirable events shall be determined from analysis of criteria for mission success, during conceptual and preliminary design phases. "]
["ECSS-Q-ST-30C Rev.1","ECSS - Current v1.0","6.4.2.3b","Requirement","ECSS-Q-ST-30_0410083",1,"Unchanged","HSIA shall be performed at the level of the technical specification of the software. ","NOTE \tHSIA can be included in the FMEA/FMECA (refer to ECSS-Q-ST-30-02).\n"]
["ECSS-Q-ST-30C Rev.1","ECSS - Current v1.0","6.4.2.9a","Requirement","ECSS-Q-ST-30_0410092",1,"Unchanged","Zonal analysis shall be performed in conformance with Annex G, in order to evaluate the consequences due to potential subsystem-to-subsystem interactions inherent in the system installation."]
["ECSS-Q-ST-30C Rev.1","ECSS - Current v1.0","7.3b","Requirement","ECSS-Q-ST-30_0410112",1,"Unchanged","“The maintainability demonstration” shall verify the ability to:\n1.\tdetect, diagnose and isolate each faulty line replaceable unit or orbit replaceable unit;\n2.\tremove and replace each line replaceable unit or orbit replaceable unit;\n3.\tperform mission-essential repairs on units that are not intended to be replaced;\n4.\tcheck that the product is fully functional after maintenance actions have been completed;\n5.\tdemonstrate that no safety hazard is introduced as a result of maintenance actions;\n6.\tdemonstrate that the maintenance operations can be performed within the applicable constraints, including the operations necessary to prepare a system during the launch campaign ","NOTE\t1\tExample of such a constraints are time and volume or accessibility. \nNOTE\t2\tExample of such operations are “remove-before-flight” items or replacement of batteries. \n"]
["ECSS-Q-ST-30C Rev.1","ECSS - Current v1.0","J.2.1a","Requirement","ECSS-Q-ST-30_0410121",1,"Unchanged","The WCA document shall include:\n1.\tassumptions applicable to the environmental condition,\n2.\ta list of the selected parts database with the worst case parameters,\n3.\ta description of the general methodology,\n4.\tan explanation of the numerical analysis technique,\n5.\tresults and conclusion of the WCA."]
["ECSS-Q-ST-40-12C","ECSS - Current v1.0","5.1.1c","Requirement","ECSS-Q-ST-40-12_0430003",1,"Created","The supplier shall agree with the customer on the content of the FTA."]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","5.4.2.1a","Requirement","ECSS-Q-ST-40_0440010",1,"Unchanged","The safety manager shall:\n1.\thave the right of access to safety-related data relevant to project safety in conformance with ECSS-M-ST-40, \n2.\thave unimpeded access to any management level without organizational constraint on any aspect of project safety."]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","5.4.6a","Requirement","ECSS-Q-ST-40_0440017",1,"Unchanged","The safety manager or designated delegate shall be represented at configuration control boards (CCBs), nonconformance review boards (NRBs), test review board (TRBs), and at qualification, and acceptance reviews, where safety requirements and safety-critical functions are involved."]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","5.7.1.6b","Requirement","ECSS-Q-ST-40_0440040",1,"Unchanged","Disposal solutions shall be identified which meet the project's safety requirements."]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","5.7.1.6c","Requirement","ECSS-Q-ST-40_0440041",1,"Informative Change","The following safety programme tasks shall apply for human spaceflight programmes and safety critical systems:\n1.\tPerform hazard analysis with respect to the disposal operations;\n2.\tCheck that the disposal operation conforms to international safety regulations by performing the necessary safety analysis;\n3.\tReview the procedures of the disposal operations;\n4.\tSupport the mission close-out review.","NOTE \tThese tasks also serve as a guideline for other space programmes.\n"]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","5.11.2b","Requirement","ECSS-Q-ST-40_0440068",1,"Unchanged","The safety data package shall contain at least the following safety related documentation:\n1.\tSafety analysis report (in accordance with Annex D);\n2.\tSupporting analysis (if applicable);\n3.\tSafety risk assessment (if applicable);\n4.\tHazardous ground operations list and procedures;\n5.\tSafety verification tracking log (SVTL, in accordance with Annex C)."]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","5.11.2d","Requirement","ECSS-Q-ST-40_0440070",1,"Unchanged","The supplier shall use the actual configuration baseline, as defined by ECSS-M-ST-40, as the design and operational baseline that is the subject of the safety data package."]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","6.3.3.4.1b","Requirement","ECSS-Q-ST-40_0440089",1,"Unchanged","The following measures shall be applied in order of precedence:\n1.\tDesign selection\n2.\tAutomatic safety devices\n3.\tWarning devices\n4.\tSpecial procedures."]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","6.3.3.4.6b","Requirement","ECSS-Q-ST-40_0440101",1,"Unchanged","Special procedures shall be verified by test and appropriate training be provided for personnel."]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","6.3.6i","Requirement","ECSS-Q-ST-40_0440116",1,"Unchanged","Control of warning and caution situations shall be acceptable by system reconfiguration or by dedicated safing functions."]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","6.4.1d","Requirement","ECSS-Q-ST-40_0440141",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","6.4.1i","Requirement","ECSS-Q-ST-40_0440320",1,"Created","A comprehensive list of hazardous events shall be compiled for the space system and mission."]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","6.4.3.2b","Requirement","ECSS-Q-ST-40_0440157",1,"Unchanged","Safety margins shall be based on worst credible combinations of environmental conditions."]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","6.5.5a","Requirement","ECSS-Q-ST-40_0440171",1,"Unchanged","Electronic, electrical, electromechanical (EEE) components used to support safety-critical functions in flight standard hardware shall be selected and procured in accordance with the applicable programme requirements of ECSS-Q-ST-60."]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","6.6.1d","Requirement","ECSS-Q-ST-40_0440182",1,"Unchanged","The design shall not require continuous active control by personnel in order to stay within the established operating ranges and performance limits."]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","6.6.2.6b","Requirement","ECSS-Q-ST-40_0440195",1,"Unchanged","Safety status parameters shall be monitored."]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","6.6.3.6c","Requirement","ECSS-Q-ST-40_0440210",1,"Unchanged","Conformance to 6.6.3.6b. shall be shown by the addition of the ‘CE’ mark to the product and the issuing of a ‘Declaration of Conformity’."]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","7.5.1a","Requirement","ECSS-Q-ST-40_0440223",1,"Unchanged","The safety analysis report shall be established in conformance with the DRD in Annex D in order to gather results of safety analyses, which use deterministic and probabilistic methods which are described in the clauses 7.5.2 to 7.5.4."]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","7.5.4.4.2a","Requirement","ECSS-Q-ST-40_0440240",1,"Unchanged","The supplier shall identify the requirement for and the scope of dedicated common-cause and common-mode analyses by means of the review of the results of the other safety analyses, such as FTA and hazard analysis, and of the characteristic of the system and of its environment."]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","8.1a","Requirement","ECSS-Q-ST-40_0440254",1,"Unchanged","A system shall be in place that tracks all hazards and related risks, to relate all verifications of the corresponding hazard uniquely to unambiguous causes and controls."]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","8.3.4.2a","Requirement","ECSS-Q-ST-40_0440270",1,"Unchanged","All preflight safety inspections shall be assessed for inclusion in the MIP list. ","NOTE \tIf preflight safety inspections are included on the MIP list, closeout is feasible by MIP reporting or individual reporting as appropriate.\n"]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","8.4.4a","Requirement","ECSS-Q-ST-40_0440285",1,"Unchanged","Verification of unique safety required design or operational characteristics shall form part of the development, qualification or acceptance testing programmes as appropriate. "]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","C.2.1<5>b","Requirement","ECSS-Q-ST-40_0440305",1,"Unchanged","If “yes” for flight tracking log: an attachment shall be provided that identifies which ground operation is constrained."]
["ECSS-Q-ST-40C Rev.1","ECSS - Current v1.0","D.2.1<1>e","Requirement","ECSS-Q-ST-40_0440315",1,"Unchanged","Introduction - An introduction shall be provided."]
["ECSS-Q-ST-60-03C","ECSS - Current v1.0","5.1.3.2c","Requirement","ECSS-Q-ST-60-03_1590008",1,"Created","The supplier shall ensure that personnel conducting activities in compliance with ECSS-Q-ST-60-03 and ECSS-E-ST-20-40 are trained."]
["ECSS-Q-ST-60-03C","ECSS - Current v1.0","5.2.6c","Requirement","ECSS-Q-ST-60-03_1590027",1,"Created","The DEVICE product assurance plan shall specify the point in the DEVICE development flow from which the nonconformance procedures apply."]
["ECSS-Q-ST-60-03C","ECSS - Current v1.0","5.5.1c","Requirement","ECSS-Q-ST-60-03_1590042",1,"Created","The correct use of methods and tools shall be verified and reported in the DEVICE product assurance report in compliance with DRD in Annex B. "]
["ECSS-Q-ST-60-03C","ECSS - Current v1.0","6.2.2.1c","Requirement","ECSS-Q-ST-60-03_1590059",1,"Created","The need for updating the DRS, and any of DEVICE Development, verification or validation Plans and its impact in the development flow for critical DEVICE shall be analysed, in the DEVICE Product Assurance Report in compliance with DRD in Annex B, after: \n1.\tAny change of the underlying platform hardware, \n2.\tAny change in the environment in which the DEVICE operates,\n3.\tAny change of the tools, including configuration of the tools, that affect directly or indirectly the development of the DEVICE.","NOTE\t1\tFor 2 example is memory used with reprogrammable FPGA.\nNOTE\t2\tAdditional verification and validation, or regression testing which can be done at DEVICE or system-level\n"]
["ECSS-Q-ST-60-03C","ECSS - Current v1.0","6.2.3.6a","Requirement","ECSS-Q-ST-60-03_1590072",1,"Created","All the reused DEVICEs and Building Blocks shall be kept under configuration control in compliance with ECSS-Q-ST-60-03 clause 8."]
["ECSS-Q-ST-60-03C","ECSS - Current v1.0","6.2.5a","Requirement","ECSS-Q-ST-60-03_1590080",1,"Created","The supplier shall define PA tasks and responsibilities related to the security requirements of the project for which the DEVICE is being developed, in the DEVICE Product Assurance Plan in compliance with DRD in Annex A for customer approval."]
["ECSS-Q-ST-60-03C","ECSS - Current v1.0","6.3.4j","Requirement","ECSS-Q-ST-60-03_1590101",1,"Created","Functional areas affected by any modification shall be identified and retested.","NOTE\t1\tThis can be triggered by a nonconformance or problem report fix.\nNOTE\t2\tThis can be triggered by a new FPGA bit stream and can result in full testing of the DEVICE\n"]
["ECSS-Q-ST-60-03C","ECSS - Current v1.0","6.3.4.4c","Requirement","ECSS-Q-ST-60-03_1590117",1,"Created","The customer shall ensure that the acceptance tests are performed in accordance with the approved acceptance test plan. "]
["ECSS-Q-ST-60-03C","ECSS - Current v1.0","7.2.3a","Requirement","ECSS-Q-ST-60-03_1590131",1,"Created","The DEVICE Requirement Specification, in compliance with DRD in ECSS-E-ST-20-40 Annex A, of DEVICEs developed for reuse shall include requirements for portability."]
["ECSS-Q-ST-60-03C","ECSS - Current v1.0","8.2.2d","Requirement","ECSS-Q-ST-60-03_1590147",1,"Created","The CIDL and ABCL shall be provided and up to date for each project review. "]
["ECSS-Q-ST-60-03C","ECSS - Current v1.0","8.2.2i","Requirement","ECSS-Q-ST-60-03_1590152",1,"Created","All inputs to the DEVICE development that are not automatically generated and are needed to reproduce the design shall be put under a revision control mechanism agreed with the customer.","NOTE\tExamples are simulation pattern, schematics, VHDL source codes, synthesis scripts\n"]
["ECSS-Q-ST-60-03C","ECSS - Current v1.0","A.2.1<5.8>a","Requirement","ECSS-Q-ST-60-03_1590176",1,"Created","The DPAP shall define the methods and tools used for all the activities of the development cycle, and their level of maturity. "]
["ECSS-Q-ST-60-03C","ECSS - Current v1.0","A.2.1<6.6>a","Requirement","ECSS-Q-ST-60-03_1590187",1,"Created","The DPAP shall define the contribution of the DEVICE product assurance function to the proper implementation of documentation and configuration management. "]
["ECSS-Q-ST-60-03C","ECSS - Current v1.0","B.2.1<3>a","Requirement","ECSS-Q-ST-60-03_1590206",1,"Created","The DPAR shall include any additional terms, definition or abbreviated terms used. "]
["ECSS-Q-ST-60-03C","ECSS - Current v1.0","B.2.1<14>b","Requirement","ECSS-Q-ST-60-03_1590222",1,"Created","The DPAR shall include references to IVV plans and reports as well status of open points with associated correction plan."]
["ECSS-Q-ST-60-03C","ECSS - Current v1.0","B.2.1<15>b","Requirement","ECSS-Q-ST-60-03_1590224",1,"Created","The DPAR shall include reporting on Improvement planning and results."]
["ECSS-Q-ST-60-05C Rev. 1","ECSS - Current v1.0","6.2.4.2a","Requirement","ECSS-Q-ST-60-05_0160020",1,"Created","The review and validation activities for the production lines for category 2 manufacturers shall be implemented at the PDR milestone of the project."]
["ECSS-Q-ST-60-05C Rev. 1","ECSS - Current v1.0","6.3.3a","Requirement","ECSS-Q-ST-60-05_0160028",1,"Created","After construction analysis, a quality and technical audit shall be carried out by the supplier as follows:\n    1. Present the results of the construction analysis.\n    2. Analyse the results of internal evaluations of the technologies implemented by the manufacturer. Compare these previously obtained results to the tests defined in the evaluation plans (see ESA-PSS-01-606, ESA-PSS-01-605, and ESA-PSS-01-612), and apply the following criteria. \n        (a) If the results of the tests are successful, consider the manufacturer “validated”, but only for the project. \n        (b) If only some of the results are successful, perform additional tests pertaining to the failures (see the evaluation plans ESA-PSS-01-606, ESA-PSS-01-605, and ESA-PSS-01-612).\n        (c) If all the results are unsuccessful, draw up a completely new evaluation plan (see ESA-PSS-01-606, ESA-PSS-01-605, and ESA-PSS-01-612).\n    3. Judge the validity of manufacturer’s in-house data in conformance with the following criteria: \n        (a) Equivalence of the test structure(s) subjected to the in-house evaluation tests and the hybrid circuits proposed by the project, this “equivalence” including assessment of the following:\n            • technology of the circuit,\n            • circuit function,\n            • circuit complexity,\n            • power dissipation.\n            • Comparison between the in-house evaluation tests and the reference evaluation plans with respect to the severity of the tests (e.g. level, duration, temperature) and the accept or reject criteria applied.\n    4. Validate the capability of the production line to meet the quality requirements of the project and ensure the following:\n        (a) The components, materials and processes used are governed by specifications written, approved by the manufacturer’s quality control departments and that this documentation is applied at the time of the manufacturer’s in-house evaluation tests.\n        (b) The quality control operations on the production line conform in frequency and severity to the “high reliability” requirements.\n        (c) The traceability of the finished product and its component parts is guaranteed by the manufacturer and can be used by the customer.\n        (d) All the documentation relating to production and quality assurance specified in the process identification document (PID) is approved by the customer.\n            NOTE For guidelines for carrying out such audits see ESA-PSS-01-607 and ESA-PSS-01-611."]
["ECSS-Q-ST-60-05C Rev. 1","ECSS - Current v1.0","8.1.2e","Requirement","ECSS-Q-ST-60-05_0160050",1,"Created","If non-qualified components are procured, a component evaluation and approval testing programme shall be implemented in conformance with the component approval requirements of ECSS-Q-ST-60."]
["ECSS-Q-ST-60-05C Rev. 1","ECSS - Current v1.0","8.3.1a","Requirement","ECSS-Q-ST-60-05_0160065",1,"Created","Each lot of active chips shall be characterized by the supplier as follows and checked and accepted by the customer:\n    1. Conformance of the active chip to its detail specification (e.g. size, masks).\n    2. Traceability and homogeneity of the lot.\n    3. 100 % probe testing of the wafers at 25 °C and marking of chips that do not conform.\n    4. Visual inspection of the wafer in conformance with:\n        (a) MIL-STD-883 method 2010 condition A or B (integrated circuits);\n        (b) MIL-STD-750 methods 2072 and 2073 (diodes and transistors).\n    5. SEM inspection in conformance with the component technology (i.e. in case of metallization over oxide steps)."]
["ECSS-Q-ST-60-05C Rev. 1","ECSS - Current v1.0","8.3.3.2.4b","Requirement","ECSS-Q-ST-60-05_0160079",1,"Created","The values for “n” and the acceptance criteria are given in Table 8-2."]
["ECSS-Q-ST-60-05C Rev. 1","ECSS - Current v1.0","8.3.3.2.4c","Requirement","ECSS-Q-ST-60-05_0160080",1,"Created","After encapsulation, the sample batch of “n” chips shall be subjected, either by the hybrid manufacturer or by a subcontractor under his/her responsibility, to the following procedure:\n    1. Serialization.\n    2. Take electrical measurements at ambient temperatures in conformance with Table 2 of the chip detail specification. \n        NOTE Table 3 optional.\n    3. Take electrical measurements before burn-in in conformance with Table 4 of the chip detail specification, values shall be recorded.\n    4. Subject the samples to burn-in over a period of 240 h at 125 °C in conformance with the chip detail specification.\n    5. Take electrical measurements at ambient and extreme temperatures in conformance with Tables 2 and 3 and the drift calculated in conformance with Table 4 of the chip detail specification, with the maximum number of rejects allowed given in Table 8-2.\n    6. Perform a life-test for a period of 1 000 hours at 125 °C in conformance with the chip detail specification.\n    7. Take electrical measurements in conformance with Table 6 of the chip detail specification with the maximum number of rejects allowed given in Table 8-2.\n    8. Perform a wire pull test in conformance with MIL-STD-883 method 2011 on 22 wires or on all the wires if less, with no failure allowed. \n    9. Perform a shear test on the assembled chips in conformance with MIL-STD-883 method 2019 on 4 chips, with no failure allowed."]
["ECSS-Q-ST-60-05C Rev. 1","ECSS - Current v1.0","10.2.1f","Requirement","ECSS-Q-ST-60-05_0160100",1,"Created","Each hybrid circuit shall be marked with the following information in the given order of precedence:\n    1. Polarity or lead identification as defined in its detail specification specified in Annex B.\n    2. Part number as defined in its detail specification specified in Annex B, followed by the suffix 1 or 2, depending on the testing level.\n    3. Manufacturing date code, a 4 digit code used where: the first two digits are the last two digits of the calendar year: the last two digits are the number of the week in which the hybrid was encapsulated \n    4. For testing level 1, the serial number, consisting of a sequential number of two or more digits for each selected sub-lot. \n    5. Manufacturer’s name, symbol or trade mark."]
["ECSS-Q-ST-60-05C Rev. 1","ECSS - Current v1.0","10.3.2a","Requirement","ECSS-Q-ST-60-05_0160111",1,"Created","Thermographic test shall be performed only to hybrid circuits where thermal studies or design approval tests during CTA activities have indicated the existence of hot spots at maximum rated power. \n    NOTE This test is destructive."]
["ECSS-Q-ST-60-05C Rev. 1","ECSS - Current v1.0","10.3.7b","Requirement","ECSS-Q-ST-60-05_0160126",1,"Created","The exact test condition shall be as specified in the PID."]
["ECSS-Q-ST-60-05C Rev. 1","ECSS - Current v1.0","10.5.3a","Permission","ECSS-Q-ST-60-05_0160253",1,"Created","Re-bonding may be performed for chip to substrate, substrate to package pins, and substrate pad to substrate pad wires."]
["ECSS-Q-ST-60-05C Rev. 1","ECSS - Current v1.0","10.5.3e","Requirement","ECSS-Q-ST-60-05_0160156",1,"Created","The total number of chip to substrate or substrate pad to substrate pad wire re-bondings shall be limited to a maximum of 10 % of the total number of wires on the hybrid circuit."]
["ECSS-Q-ST-60-05C Rev. 1","ECSS - Current v1.0","12.2.1.1b","Requirement","ECSS-Q-ST-60-05_0160173",1,"Created","For a given type of hybrid, there shall be n-1 samples for the first production lot and n-1 samples for the subsequent production lots of the same hybrid type."]
["ECSS-Q-ST-60-05C Rev. 1","ECSS - Current v1.0","12.3b","Requirement","ECSS-Q-ST-60-05_0160186",1,"Created","For subsequent lots and on condition that the test results for the initial lots are satisfactory, the lot acceptance procedure (category 1 manufacturer, option 1) in conformance with clause 12.2.1 shall be applied for each type."]
["ECSS-Q-ST-60-05C Rev. 1","ECSS - Current v1.0","B.2.2<1>a","Requirement","ECSS-Q-ST-60-05_0160204",1,"Created","This table shall include the limiting electrical, mechanical and thermal parameters. "]
["ECSS-Q-ST-60-05C Rev. 1","ECSS - Current v1.0","B.2.2<7>a","Requirement","ECSS-Q-ST-60-05_0160216",1,"Created","This table shall list the oven temperature and power applied to comply with ECSS-Q-ST-60-05, clause 10.3.9."]
["ECSS-Q-ST-60-12C","ECSS - Current v1.0","5.2c","Requirement","ECSS-Q-ST-60-12_0190009",1,"Created","A foundry manual for each process used, shall be delivered to the customer (provided the current issue is not already available) prior to the design phase. "]
["ECSS-Q-ST-60-12C","ECSS - Current v1.0","7.2.6c","Requirement","ECSS-Q-ST-60-12_0190033",1,"Created","The analysis shall be carried out for all parameters subjected to process variations and include, whenever possible, correlations between the different elements that cause variations. "]
["ECSS-Q-ST-60-12C","ECSS - Current v1.0","7.2.8a","Requirement","ECSS-Q-ST-60-12_0190039",1,"Created","Design stability analysis shall be carried out from the DC to the maximum frequency of the active devices used."]
["ECSS-Q-ST-60-12C","ECSS - Current v1.0","7.2.10c","Requirement","ECSS-Q-ST-60-12_0190054",1,"Created","The circuit layout shall be delivered in GDSII format."]
["ECSS-Q-ST-60-12C","ECSS - Current v1.0","7.3.2b","Requirement","ECSS-Q-ST-60-12_0190069",1,"Created","The manufacturer shall verify that the characteristics are realistic with regard to the domain of the process."]
["ECSS-Q-ST-60-12C","ECSS - Current v1.0","7.3.8b","Requirement","ECSS-Q-ST-60-12_0190084",1,"Created","The manufacturer shall ensure that he has adequate test facilities to perform the tests."]
["ECSS-Q-ST-60-12C","ECSS - Current v1.0","8.2c","Requirement","ECSS-Q-ST-60-12_0190105",1,"Created","It shall not be considered to be a duplication of environmental testing specified in row 7 of Table 8-1 carried out in the context of the hybrid evaluation and qualification activities used for validating the compatibility between the MMIC and hybrid technologies."]
["ECSS-Q-ST-60-12C","ECSS - Current v1.0","10.2.3a","Requirement","ECSS-Q-ST-60-12_0190114",1,"Created","PCM measurements, rules and controls, shall be in conformance with the manufacturer design book requirements. "]
["ECSS-Q-ST-60-12C","ECSS - Current v1.0","10.2.4.3a","Requirement","ECSS-Q-ST-60-12_0190126",1,"Created","All visual inspection sequences shall be performed according to ESCC 2049010 or MIL-STD-883, method 2010 condition A or according to standard professional grade (manufacturer or user procedure) if validated by the customer."]
["ECSS-Q-ST-60-12C","ECSS - Current v1.0","10.3.1b","Requirement","ECSS-Q-ST-60-12_0190143",1,"Created","The testing shall include the following test sequence:\n    1. bondability testing;\n    2. visual inspection;\n    3. electrical characterization."]
["ECSS-Q-ST-60-12C","ECSS - Current v1.0","10.4.1.2f","Requirement","ECSS-Q-ST-60-12_0190159",1,"Created","The number of units that are assembled shall be sufficient to ensure that after screening, the specified number of units as defined in Figure 10-4 are available."]
["ECSS-Q-ST-60-12C","ECSS - Current v1.0","10.4.3h","Requirement","ECSS-Q-ST-60-12_0190177",1,"Created","A DPA shall be performed on 2 parts (either TCV, DEC or MMIC) as per clause 10.4.6.No defect allowed."]
["ECSS-Q-ST-60-12C","ECSS - Current v1.0","10.4.5a","Requirement","ECSS-Q-ST-60-12_0190189",1,"Created","When specified, sequence D in Figure 10-4 shall be applied, prior to the user LAT sequences."]
["ECSS-Q-ST-60-12C","ECSS - Current v1.0","10.4.6a","Requirement","ECSS-Q-ST-60-12_0190198",1,"Created","The following tests shall be performed as part of the DPA:\n    1. External visual inspection MIL-STD-883 Method 2009.8\n    2. Seal test MIL-STD-883 Method 1014 condition A2 - condition C \n    3. Internal visual inspection ESCC 2409010 or equivalent\n    4. Bond pull test MIL-STD-883 Method 2011 condition D\n    5. Die shear test MIL-STD-883 Method 2019\n    6. RGA (option) MIL-STD-883 Method 1018.2."]
["ECSS-Q-ST-60-12C","ECSS - Current v1.0","G.2.1a","Requirement","ECSS-Q-ST-60-12_0190218",1,"Created","The MMIC visual inspection shall include all references for traceability purpose and, as a minimum, the quantities of the following:\n    1. good dies, sorted after DC and RF testing;\n    2. rejected dies after visual inspection;\n    3. accepted dies for each type of MMIC."]
["ECSS-Q-ST-60-14C Rev.1 Corr.1","ECSS - Current v1.0","5c","Requirement","ECSS-Q-ST-60-14_0470060",1,"Created","The maximum lifetime requirements of the EEE parts manufacturers shall be taken into account.\n"]
["ECSS-Q-ST-60-14C Rev.1 Corr.1","ECSS - Current v1.0","6.1.1k","Requirement","ECSS-Q-ST-60-14_0470027",2,"Normative Change","For programmed parts, the total duration, including storage and mission, shall not exceed data retention duration given by the manufacturer.\n"]
["ECSS-Q-ST-60-14C Rev.1 Corr.1","ECSS - Current v1.0","6.2b","Requirement","ECSS-Q-ST-60-14_0470039",1,"Unchanged","Any components not satisfying at least one of the requirements included in this standard shall be considered as not conform.\n"]
["ECSS-Q-ST-60-14C Rev.1 Corr.1","ECSS - Current v1.0","6.3b","Requirement","ECSS-Q-ST-60-14_0470045",1,"Unchanged","This date code shall be assigned independent of the report conclusions.\n"]
["ECSS-Q-ST-60-14C Rev.1 Corr.1","ECSS - Current v1.0","7.2d","Requirement","ECSS-Q-ST-60-14_0470085",1,"Created","In the case specified in 7.2c, the test shall be repeated on a 100 % basis on the whole lot and the causes of the nonconformance investigated and recorded in the relifing report.\n"]
["ECSS-Q-ST-60-14C Rev.1 Corr.1","ECSS - Current v1.0","A.2.1c","Requirement","ECSS-Q-ST-60-14_0470053",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-60-15C Rev.1","ECSS - Current v1.0","5.1q","Requirement","ECSS-Q-ST-60-15_1620018",1,"Created","If Reverse Monte-Carlo codes are used, acceptance criteria shall be as follows:\n1.\tnumber of histories shall be greater than 2000 (NOVICE), or\n2.\tconvergence results are higher than 98 %."]
["ECSS-Q-ST-60-15C Rev.1","ECSS - Current v1.0","5.2c","Requirement","ECSS-Q-ST-60-15_1620033",1,"Created","When the phasing as per ECSS-M-ST-10 is not applicable, final version of mission radiation environment shall be available at proposal time frame."]
["ECSS-Q-ST-60-15C Rev.1","ECSS - Current v1.0","5.2g","Requirement","ECSS-Q-ST-60-15_1620038",1,"Created","Displacement Damage Equivalent Fluence at a given proton energy shall be derived from TNID versus depth curve in mission radiation environment specification using the same NIEL tables than the ones used to define the TNID environment specification."]
["ECSS-Q-ST-60-15C Rev.1","ECSS - Current v1.0","5.3d","Requirement","ECSS-Q-ST-60-15_1620064",1,"Created","No SEE shall cause damage to a system or a subsystem or an equipment, or induce performance anomalies or outages not compliant with mission specifications during its radiation design lifetime."]
["ECSS-Q-ST-60-15C Rev.1","ECSS - Current v1.0","5.3m","Requirement","ECSS-Q-ST-60-15_1620077",1,"Created","Below a LETth level of 60 MeVcm2/mg, SEE analysis shall be performed."]
["ECSS-Q-ST-60-15C Rev.1","ECSS - Current v1.0","5.3hh","Requirement","ECSS-Q-ST-60-15_1620098",1,"Created","A draft radiation analysis report shall be part of equipment PDR data package for category C or D equipment."]
["ECSS-Q-ST-60-15C Rev.1","ECSS - Current v1.0","B.2.1<2>b","Requirement","ECSS-Q-ST-60-15_1620113",1,"Created","The radiation analysis report shall identify the parts submitted to RVT."]
["ECSS-Q-ST-60-15C Rev.1","ECSS - Current v1.0","B.2.1<2>c","Requirement","ECSS-Q-ST-60-15_1620114",1,"Created","The radiation analysis report shall include the description of mechanical model, assumption, method and tools used for ray trace or Monte Carlo analysis, and results obtained."]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","4.1.2.2a","Requirement","ECSS-Q-ST-60_0480004",1,"Unchanged","The supplier shall prepare a Component Control Plan (CCP) in conformance with its DRD in Annex A."]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","4.1.5b","Requirement","ECSS-Q-ST-60_0480020",2,"Unchanged","Flight hardware connector interfaces to GSE shall interface to a flight compatible connector, as per 4.1.5a.","NOTE \tThis connector can be installed on the test harness or can be a saver.\n"]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","4.2.2.2g","Requirement","ECSS-Q-ST-60_0480034",2,"Unchanged","As per 4.2.2.2f., the justification of the use of pure tin shall be presented during a PCB for customer’s approval."]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","4.2.2.4c","Requirement","ECSS-Q-ST-60_0480041",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","4.2.4b","Requirement","ECSS-Q-ST-60_0480068",2,"Unchanged","<<deleted>>"]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","4.2.4e","Requirement","ECSS-Q-ST-60_0480071",2,"Unchanged","In case the evaluation results are changing the procurement conditions documented in the PAD or the JD (as per clause 4.2.3.1), a new revision of PAD or the JD shall be submitted to the customer for approval."]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","4.3.1i","Requirement","ECSS-Q-ST-60_0480554",1,"Created","The supplier shall establish an attrition policy and corresponding rules which consider the specific criticality of each EEE component family."]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","4.3.4a","Requirement","ECSS-Q-ST-60_0480091",3,"Normative Change","The procurement entity shall carry out, at the manufacturer’s premises, a customer precap inspection for non-space qualified parts listed below:\n1.\tCapacitors (ceramic, mica and plastic film)\n2.\tCrystals\n3.\tOscillators\n4.\tDiscrete semiconductors (including diodes and transistors)\n5.\tFilters\n6.\tFuses (cermet)\n7.\tInductors, coils and transformers (not applicable to self-made products)\n8.\tMonolithic microcircuits (including MMICs)\n9.\tHybrid circuits\n10.\tRelays\n11.\tResistors (high precision, fixed, metal foil – RNC90)\n12.\tSwitches (including mechanical and thermal)\n13.\tOptoelectronic devices (e.g. opto-couplers, LEDs, CCDs and sensors).","NOTE \tAs a reminder: Precap inspection is not needed for chip components.\n"]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","4.3.8e","Requirement","ECSS-Q-ST-60_0480109",1,"Unchanged","When RVT is performed in the frame of the project, the supplier shall send the related  report to the customer for information."]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","4.3.10a","Requirement","ECSS-Q-ST-60_0480451",1,"Unchanged","When components from a supplier’s or parts procurement agent’s stock are used, the following criteria shall be met:\n1.\tThe parts are stored according to the minimum conditions given in clause 4.4,\n2.\tThe minimum overall requirements (including screening) are in accordance with the project requirements, \n3.\tThe lot/date code homogeneity and traceability can be demonstrated, \n4.\tThe EEE parts documentation is available and the content is acceptable in accordance with the project requirements (including radiation data, if necessary),\n5.\tThere are no open NCR’s and no unresolved alerts with respect to their date code."]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","4.5.2b","Requirement","ECSS-Q-ST-60_0480131",1,"Unchanged","Any observed deviation of EEE components from requirements as laid down in applicable specifications, procedures and drawings shall be controlled by the nonconformance control system.","NOTE \tThis includes failures, malfunctions, deficiencies and defects.\n"]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","4.5.5a","Requirement","ECSS-Q-ST-60_0480142",2,"Unchanged","If tests are performed by sampling, the sampled parts shall be selected so that they are representative of the lot/date code distribution. "]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","4.6.8b","Requirement","ECSS-Q-ST-60_0480562",1,"Created","Minimum screening of Self made Magnetics parts on a 100 % basis shall include:\n1.\tvisual inspection,\n2.\tinitial electrical measurements,\n3.\tthermal cycling,\n4.\thigh temperature storage (minimum 96h) (optional),\n5.\tfinal electrical measurements."]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","5.1.4g","Requirement","ECSS-Q-ST-60_0480171",2,"Unchanged","The “as built” DCL reflecting the actual EEE parts assembled into the flight hardware and their date code, shall be provided before TRR to the customer for review."]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","5.2.2.2c","Requirement","ECSS-Q-ST-60_0480182",3,"Unchanged","With respect to health and safety, beryllium oxide and lithium (except for the one which is identified in the procurement specification), cadmium, magnesium, mercury, zinc, radioactive material and all material which can cause safety hazard shall not be used."]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","5.2.2.4d","Requirement","ECSS-Q-ST-60_0480191",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","5.2.3.4a","Requirement","ECSS-Q-ST-60_0480213",1,"Unchanged","The evaluation shall determine which inspections or tests are required to provide the confidence that the component type under evaluation, when assembled and tested in accordance with the procurement specification, successfully meets the project requirements."]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","5.2.4g","Requirement","ECSS-Q-ST-60_0480564",1,"Created","The previous use or approval of a part, via PAD or JD, in any other project shall not be considered as an automatic approval for the present program.","NOTE \tThe pertinence of the heritage in terms of mission profile and requirements can be assessed as well as all the deviations (e.g. RFDs, RFWs, special dispositions for a specific space program) previously accepted.\n"]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","5.3.2a","Requirement","ECSS-Q-ST-60_0480227",1,"Unchanged","The supplier shall procure EEE components according to controlled specifications."]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","5.3.4b","Requirement","ECSS-Q-ST-60_0480240",1,"Informative Change","When not covered by MIL or ESCC specifications, methods and accept/reject criteria for customer’s precap inspection shall be documented by a procedure to be presented to the customer, on request, for review.","NOTE \tFor guidance refer to the basic specificaton ESCC 21002.\n"]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","5.3.8d","Requirement","ECSS-Q-ST-60_0480255",1,"Unchanged","The results of RVT shall be documented by a report. "]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","5.4d","Requirement","ECSS-Q-ST-60_0480274",1,"Unchanged","As a minimum, the following areas shall be covered:\n1.\tControl of the environment in accordance with ESCC Basic Specification No. 24900.\n2.\tMeasures and facilities to segregate and protect components during receiving inspection, storage, and delivery to manufacturing. \n3.\tControl measures to ensure that electrostatic discharge susceptible components are identified and handled only by trained personnel using anti static packaging and tools."]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","5.5.3b","Requirement","ECSS-Q-ST-60_0480281",1,"Unchanged","If alerts become available at a later stage, the supplier shall analyse the alerts, analyse the project risk and propose an action plan for customer approval. "]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","5.6.3a","Requirement","ECSS-Q-ST-60_0480290",3,"Normative Change","The hybrids shall be procured in conformance with the specifications listed in Table 7‑2."]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","6.1.2.2a","Requirement","ECSS-Q-ST-60_0480303",1,"Unchanged","The supplier shall prepare a compliance matrix to the clauses of this standard. "]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","6.1.5b","Requirement","ECSS-Q-ST-60_0480314",2,"Unchanged","Flight hardware connectors interfaces to GSE shall interface to a flight compatible connector, as per 6.1.5a.","NOTE \tThis connector can be installed on the test harness or can be a saver.\n"]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","6.2.2.2j","Requirement","ECSS-Q-ST-60_0480544",1,"Unchanged","The following actions shall be performed by the supplier to control the pure-tin risk:\n1.\tCollect and synthesize all information participating to the risk analysis in conformance with Clause 9.\n2.\tBased on the risk analysis, elaborate a mitigation plan.\n3.\tInclude in the JD the risk analysis and mitigation plan for customer approval.\n4.\tBefore retinning of flight parts, document the hot solder dip process by a procedure to be submitted to customer for approval.\n5.\tPerform evaluation tests, lot acceptance tests and screening tests of retinned components after the retinning process.","NOTE\t1\tThe mitigation plan can include one or a combination of the following solutions:\n·\tTin whisker sensitivity evaluation\n·\tRetinning of terminations with complementary evaluation,\n·\tConformal coating,\n·\tDesign modification.\nNOTE\t2\tSolder dip for tin whisker mitigation differs from solder dip for solderability in that for tin whisker mitigation, the termination is coated over its entire length, right up to the package surface (no stand off). As this process is critical it is good practice to evaluate it and control it well.\n"]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","6.2.2.4g","Requirement","ECSS-Q-ST-60_0480335",2,"Unchanged","The supplier shall implement a Radiation Hardness Assurance Programme, in conformance with the requirements of the ECSS-Q-ST-60-15, documented by a plan to be approved by the customer, for radiation sensitive components, covering the collection of all relevant information and specifying the necessary actions in terms of evaluation and procurement testing, planning and control. "]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","6.2.3.1d","Requirement","ECSS-Q-ST-60_0480343",2,"Unchanged","An evaluation plan shall be sent to the customer for approval, and include the following elements:\n1.\tConstructional Analysis (as per clause 6.2.3.3),\n2.\tEvaluation Testing (as per clause 6.2.3.4),\n3.\tRadiation Hardness (as per clause 6.2.3.4b.5). "]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","6.2.4i","Permission","ECSS-Q-ST-60_0480585",1,"Created","For ASICs built on space qualified technologies, the PAD may be replaced, if agreed with the customer, by information embedded in the DCL."]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","6.3.2f","Requirement","ECSS-Q-ST-60_0480371",1,"Unchanged","Upon request, any new procurement specification prepared in the frame of the project, shall be delivered to the customer."]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","6.3.7c","Requirement","ECSS-Q-ST-60_0480384",1,"Unchanged","The incoming inspection shall be documented by a procedure to be presented, on request, to the customer for review."]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","6.3.9h","Requirement","ECSS-Q-ST-60_0480400",3,"Unchanged","For health and safety reasons, any test producing beryllium oxide dust shall be omitted."]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","6.3.11b","Requirement","ECSS-Q-ST-60_0480405",2,"Unchanged","Any other data (i.e. LAT or LVT, QCI or TCI), defined in the applicable procurement documents, shall be available at the manufacturer’s facilities or delivered to the parts’ procurer in line with the purchase order, as a minimum compatible with CSV.  ","NOTE \tCSV is a common file format that can be used to transfer data between database or spreadsheet tables (a spreadsheet program is for example Excel®).\n"]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","6.6.2a","Requirement","ECSS-Q-ST-60_0480425",3,"Normative Change","For the development and re-use of ASICs, ECSS-Q-ST-60-03 shall apply."]
["ECSS-Q-ST-60C Rev.4","ECSS - Current v1.0","6.6.4c","Permission","ECSS-Q-ST-60_0480519",1,"Unchanged","<<deleted>>"]
["ECSS-Q-ST-70-01C Rev.1","ECSS - Current v1.0","5.1.2.1b","Requirement","ECSS-Q-ST-70-01_1650006",1,"Created","The CRS shall be defined as early as possible in the programme to ensure proper consideration during the design phase.","NOTE \tCleanliness is of fundamental importance for the space system’s performance.\n"]
["ECSS-Q-ST-70-01C Rev.1","ECSS - Current v1.0","5.1.2.3.2d","Requirement","ECSS-Q-ST-70-01_1650021",1,"Created","Predictions for contamination sensitive and contamination critical items based on modelling analysis shall be verified and corrected against experimental data.\n1.\tFor in-flight molecular contamination via dedicated or as a part of planned testing activities during MAIT, or in-orbit measurements;\n2.\tFor particulate and molecular contamination during launch via dedicated tests, in situ data provided by the launch provider or heritage data."]
["ECSS-Q-ST-70-01C Rev.1","ECSS - Current v1.0","5.2.1.1a","Requirement","ECSS-Q-ST-70-01_1650023",1,"Created","The level of sensitivity to contamination shall be one of the drivers in the initial design."]
["ECSS-Q-ST-70-01C Rev.1","ECSS - Current v1.0","5.2.2.1b","Requirement","ECSS-Q-ST-70-01_1650039",1,"Created","All elements manufactured in non­controlled areas or under non­clean conditions shall be the object of a cleaning process until the cleanliness requirements are met, before they are packaged for delivery."]
["ECSS-Q-ST-70-01C Rev.1","ECSS - Current v1.0","5.2.3.1b","Requirement","ECSS-Q-ST-70-01_1650057",1,"Created","A dedicated C&CCP shall be provided for the launch campaign by the launch provider."]
["ECSS-Q-ST-70-01C Rev.1","ECSS - Current v1.0","5.3.1.1a","Requirement","ECSS-Q-ST-70-01_1650069",1,"Created","Cleanroom shell, floors, walls and ceiling shall be low shedding and the finish readily cleanable."]
["ECSS-Q-ST-70-01C Rev.1","ECSS - Current v1.0","5.3.1.3e","Requirement","ECSS-Q-ST-70-01_1650084",1,"Created","When molecular absorption filters are used, the initial charge shall be assessed on installation and analysed regularly.","NOTE \tIt can be useful to evaluate the charge in contaminants of the filtering system which can release its charge in contaminants trapped. in order to be able to monitor the evolution and when a failure occurs.\n"]
["ECSS-Q-ST-70-01C Rev.1","ECSS - Current v1.0","5.3.1.5m","Requirement","ECSS-Q-ST-70-01_1650099",1,"Created","The cleanroom shall have an alarm function activated when warning levels are exceeded.","NOTE \t1\tThose warning levels are usually defined well below the out of specification limits in order to prevent their exceedance.\nNOTE \t2\tEnvironmental parameters are temperature, relative humidity and differential pressure.\n"]
["ECSS-Q-ST-70-01C Rev.1","ECSS - Current v1.0","5.3.1.8a","Requirement","ECSS-Q-ST-70-01_1650116",1,"Created","Cleanroom temperature shall be maintained and continuously monitored at nominally 22 °C ± 3 °C .","NOTE \tMore stringent temperature variations conditions can be imposed in case of critical operations.\n"]
["ECSS-Q-ST-70-01C Rev.1","ECSS - Current v1.0","5.3.1.11i","Requirement","ECSS-Q-ST-70-01_1650131",1,"Created","The cleanliness after the cleaning operations shall be verified by inspection by means of UV or high intensity white light."]
["ECSS-Q-ST-70-01C Rev.1","ECSS - Current v1.0","5.3.1.12l","Requirement","ECSS-Q-ST-70-01_1650146",1,"Created","Exhaust systems for grinding, welding or soldering, machining or related operations shall be installed."]
["ECSS-Q-ST-70-01C Rev.1","ECSS - Current v1.0","5.3.2d","Requirement","ECSS-Q-ST-70-01_1650161",1,"Created","An approved declared material list (DML) of the hardware under test, including the test adapter and all connections shall be provided.","NOTE \tIncluding, for example mechanical and electrical connexions.\n"]
["ECSS-Q-ST-70-01C Rev.1","ECSS - Current v1.0","5.4.1.2.2c","Requirement","ECSS-Q-ST-70-01_1650183",1,"Created","For precision cleaning, solvents of high purity shall be used."]
["ECSS-Q-ST-70-01C Rev.1","ECSS - Current v1.0","5.4.2.3a","Requirement","ECSS-Q-ST-70-01_1650192",1,"Created","Monitoring of molecular and particulate contaminants in vacuum facilities shall be achieved using: \n1.\tfor all contamination sensitive and contamination critical items the QCM together with the witness method, including auxiliary items, and\n2.\tfor all non-contamination sensitive and non-contamination critical items the QCM or the witness method or a combination of both."]
["ECSS-Q-ST-70-01C Rev.1","ECSS - Current v1.0","5.4.2.4k","Requirement","ECSS-Q-ST-70-01_1650204",1,"Created","Baking time shall start when the material/item under baking has reached the predefined bakeout temperature."]
["ECSS-Q-ST-70-01C Rev.1","ECSS - Current v1.0","5.4.3l","Requirement","ECSS-Q-ST-70-01_1650222",1,"Created","Only approved materials that were procured as cleaned films shall be used."]
["ECSS-Q-ST-70-01C Rev.1","ECSS - Current v1.0","A.2.1<4>b","Requirement","ECSS-Q-ST-70-01_1650239",1,"Created","The CRS shall specify acceptable contamination levels of MOC and PAC for all on ground and in-flight phases."]
["ECSS-Q-ST-70-01C Rev.1","ECSS - Current v1.0","B.2.1<6>b","Requirement","ECSS-Q-ST-70-01_1650251",1,"Created","References for internal procedures dedicated to area or facilities verification, control and maintenance shall be included."]
["ECSS-Q-ST-70-01C Rev.1","ECSS - Current v1.0","C.2.1<3>a","Requirement","ECSS-Q-ST-70-01_1650267",1,"Created","The C&CCV shall include any additional terms, definitions or abbreviated terms used."]
["ECSS-Q-ST-70-02C","ECSS - Current v1.0","5.1c","Requirement","ECSS-Q-ST-70-02_0510003",1,"Created","The measurement of contamination potential shall be only used in a comparative way and is strictly valid only for collectors at 25 °C with similar sticking coefficients."]
["ECSS-Q-ST-70-02C","ECSS - Current v1.0","5.2.4.1c","Requirement","ECSS-Q-ST-70-02_0510024",1,"Created","The supplier shall use a microbalance from1 ´ 10-6 g to 5 ´ 10-6 g."]
["ECSS-Q-ST-70-02C","ECSS - Current v1.0","5.2.4.2m","Requirement","ECSS-Q-ST-70-02_0510038",1,"Created","A pressure of 10-4 Pa shall be reached within one hour with an unloaded system. "]
["ECSS-Q-ST-70-02C","ECSS - Current v1.0","5.3.2.4b","Requirement","ECSS-Q-ST-70-02_0510053",1,"Created","The supplier shall perform weighing on a microbalance (see 5.2.4.1c.) located in a room conditioned at (22 ± 3) °C and (55 ± 10) % RH just before the loading of the test system."]
["ECSS-Q-ST-70-02C","ECSS - Current v1.0","5.3.2.13a","Requirement","ECSS-Q-ST-70-02_0510069",1,"Created","After each test, the supplier shall clean the heater bar(s), condensor plate(s) and screen(s) of the equipment with a compatible volatile solvent."]
["ECSS-Q-ST-70-02C","ECSS - Current v1.0","5.5.3.4e","Requirement","ECSS-Q-ST-70-02_0510089",1,"Created","For cases where CVCM < 0,05 % is required, the supplier shall implement other types of CVCM measurements.\n    NOTE For Improved sensitivity of CVCM measurements, see clause 5.3.2.14."]
["ECSS-Q-ST-70-02C","ECSS - Current v1.0","5.7.2.2a","Requirement","ECSS-Q-ST-70-02_0510098",1,"Created","The customer shall inspect the following parts of the Micro-VCM apparatus:\n    1. internal dimensions, view factor (sample compartment to collector plates) and cross contamination protection;\n    2. pumping system and associated monitoring equipment;\n    3. temperature regulation of sample and collector plates and associated monitoring equipment;\n    4. thermal contact of the temperature sensors."]
["ECSS-Q-ST-70-02C","ECSS - Current v1.0","5.7.3.1a","Requirement","ECSS-Q-ST-70-02_0510110",1,"Created","Based on the initial test, as described in clause 5.7.2.2, the customer shall perform a review of any modifications made to the test facility or apparatus."]
["ECSS-Q-ST-70-02C","ECSS - Current v1.0","B.2.1<4>a","Requirement","ECSS-Q-ST-70-02_0510128",1,"Created","The Micro-VCM worksheet shall contain the following outgassing screening properties:\n    1. TML\n    2. RML\n    3. WCR\n    4. CVCM.\n        NOTE Table B-1 lists the calculations needed to establish these values.                                     "]
["ECSS-Q-ST-70-02C","ECSS - Current v1.0","D.2.1<2>a","Requirement","ECSS-Q-ST-70-02_0510144",1,"Created","The report shall contain density of substrate in g/cm2 or ratio of material mass to total mass of material plus substrate."]
["ECSS-Q-ST-70-03C","ECSS - Current v1.0","5.2e","Requirement","ECSS-Q-ST-70-03_0520009",1,"Created","If a part contains welded elements, a verification programme shall be set up to qualify the black anodizing on the specific weld which includes a verification of the cleaning method used to rinse off the chemicals used for anodizing."]
["ECSS-Q-ST-70-03C","ECSS - Current v1.0","5.4.2c","Requirement","ECSS-Q-ST-70-03_0520021",1,"Created","The location of the electrical contact shall not interfere with the functional usage of the part to be treated."]
["ECSS-Q-ST-70-03C","ECSS - Current v1.0","5.5.1b","Requirement","ECSS-Q-ST-70-03_0520030",1,"Created","The parts shall be stored in such a way as to prevent any damage or contamination by dust, moisture or grease."]
["ECSS-Q-ST-70-03C","ECSS - Current v1.0","5.6.3.3d","Requirement","ECSS-Q-ST-70-03_0520051",1,"Created","If agreed by the customer, where black-anodized surfaces are welded, the process shall be verified."]
["ECSS-Q-ST-70-03C","ECSS - Current v1.0","5.7.2.4a","Requirement","ECSS-Q-ST-70-03_0520061",1,"Created","Traceability shall be maintained throughout the process from incoming inspection to final test."]
["ECSS-Q-ST-70-04C","ECSS - Current v1.0","5.1.3.3b","Requirement","ECSS-Q-ST-70-04_0530017",1,"Created","During thermal testing, the temperature of the sample (test item) shall be measured."]
["ECSS-Q-ST-70-04C","ECSS - Current v1.0","5.2.2.4c","Requirement","ECSS-Q-ST-70-04_0530032",1,"Created","Coated surfaces shall be shielded from contact by using polyethylene or polypropylene bags or sheets. "]
["ECSS-Q-ST-70-04C","ECSS - Current v1.0","5.2.3d","Requirement","ECSS-Q-ST-70-04_0530038",1,"Created","The specific equipments shall be defined in the thermal cycling test proposal."]
["ECSS-Q-ST-70-05C Rev.2","ECSS - Current v1.0","5.1.1d","Requirement","ECSS-Q-ST-70-05_0540004",1,"Unchanged","Warning and caution notes shall be included in instructions for operation, storage, transport, testing, assembly, maintenance and repair."]
["ECSS-Q-ST-70-05C Rev.2","ECSS - Current v1.0","5.1.2.2a","Requirement","ECSS-Q-ST-70-05_0540010",2,"Normative Change","The environmental conditions for the test, process and work areas shall be \n1.\tRoom temperature (22 ± 3) °C and,\n2.\tRelative humidity (55 ± 10) %. ","NOTE \tAdditional conditions can be imposed for critical operations.\n"]
["ECSS-Q-ST-70-05C Rev.2","ECSS - Current v1.0","5.2.3.3f","Requirement","ECSS-Q-ST-70-05_0540032",2,"Normative Change","The tissue to be analysed shall be immersed for 10 minutes to 15 minutes in a known quantity of spectral grade solvent contained in a suitable container."]
["ECSS-Q-ST-70-05C Rev.2","ECSS - Current v1.0","5.4.3.1d","Requirement","ECSS-Q-ST-70-05_0540046",1,"Unchanged","The supplier shall record any suspected or actual equipment failure as a project nonconformance report in conformance to ECSS-Q-ST-10-09.","NOTE \tThis is to ensure that previous results can be examined to ascertain whether or not re-inspection and retesting is necessary.\n"]
["ECSS-Q-ST-70-05C Rev.2","ECSS - Current v1.0","5.4.3.1g","Requirement","ECSS-Q-ST-70-05_0540049",2,"Normative Change","In case where the calibration curve that is produced using the direct method is used for indirect method the associated transfer efficiency shall be taken into account."]
["ECSS-Q-ST-70-05C Rev.2","ECSS - Current v1.0","5.4.3.3b","Requirement","ECSS-Q-ST-70-05_0540061",1,"Unchanged","The calibration curve shall have a correlation coefficient higher than 0,98 for six sample points.","NOTE \tA typical calibration curve is shown in C.3.3.\n"]
["ECSS-Q-ST-70-05C Rev.2","ECSS - Current v1.0","5.4.3.6.2g","Requirement","ECSS-Q-ST-70-05_0540109",1,"Created","The spectrum in each spectral region shall be fit with a quadratic function of the form:\n \nwhere:\nai, bi, and ci are constants and subscript i is a running number from 1 to 4 highlighting four separate quadratic equations – one for each spectral region of interest. ","NOTE \tAnnex J provides examples of baseline fitting using quadratic functions.\n"]
["ECSS-Q-ST-70-05C Rev.2","ECSS - Current v1.0","5.4.3.7.3a","Requirement","ECSS-Q-ST-70-05_0540120",1,"Created","Each blank measurement for the wipe method shall include the entire process, as presented in Figure 5-1, excluding the wiping of contaminated surface.","NOTE \tThe wiping of contaminated surface is represented by step 3 in the right column of Figure 5-1.\n"]
["ECSS-Q-ST-70-05C Rev.2","ECSS - Current v1.0","5.4.3.7.4g","Requirement","ECSS-Q-ST-70-05_0540135",1,"Created","The control of each area of droplets deposited onto a clean infrared window shall ensure that the droplets are deposited onto the specific area.","NOTE \tThis requirement is in line with 5.2.3.2a.3.\n"]
["ECSS-Q-ST-70-05C Rev.2","ECSS - Current v1.0","5.5.3b","Requirement","ECSS-Q-ST-70-05_0540090",1,"Unchanged","For each nonconformance the supplier shall perform the following actions:\n1.\tdetermine the reasons for the nonconformance, and \n2.\tperform a further test in accordance with clause 5.5.2.","NOTE \tThese actions are necessary before a certificate of conformance is renewed.\n"]
["ECSS-Q-ST-70-05C Rev.2","ECSS - Current v1.0","A.2.1<1>a","Requirement","ECSS-Q-ST-70-05_0540095",1,"Unchanged","The test laboratory shall provide calibration evidence of the quantification method in terms of:\n1.\tdate of last calibration,\n2.\ttype and purity of standard materials,\n3.\tconcentration ranges,\n4.\tdetection limits,\n5.\tcorrelation coefficients of the calibration curves."]
["ECSS-Q-ST-70-06C","ECSS - Current v1.0","5.1.2.4c","Requirement","ECSS-Q-ST-70-06_0550013",1,"Created","Depending on the properties to be measured, the supplier shall use a particles fluxes or an absorbed based simulation."]
["ECSS-Q-ST-70-06C","ECSS - Current v1.0","5.1.4.2c","Requirement","ECSS-Q-ST-70-06_0550027",1,"Created","The UV acceleration factor shall take into account the ASTM-E-490 standard and the incidence effect of sun light on the integrated irradiance received by the materials.\n    NOTE Due to its position on a satellite, a material can receive different irradiances of UV. The consequence is that for the same irradiance of UV at the laboratory, the acceleration factors depend on the materials position on the satellite."]
["ECSS-Q-ST-70-06C","ECSS - Current v1.0","5.2.2e","Requirement","ECSS-Q-ST-70-06_0550042",1,"Created","Samples shall be stored in a clean area."]
["ECSS-Q-ST-70-06C","ECSS - Current v1.0","B.2.1<2>a","Requirement","ECSS-Q-ST-70-06_0550064",1,"Created","The Work proposal shall contain the test procedure for the characterization, control and monitoring of the irradiation source or refer to the source characterization’s report as part of Annex C. "]
["ECSS-Q-ST-70-06C","ECSS - Current v1.0","B.2.1<4>c","Requirement","ECSS-Q-ST-70-06_0550072",1,"Created","The “seen” fluence shall be specified. "]
["ECSS-Q-ST-70-09C","ECSS - Current v1.0","4.1.2.3a","Requirement","ECSS-Q-ST-70-09_0580005",1,"Created","The supplier shall handle the samples with clean nylon or lint-free gloves."]
["ECSS-Q-ST-70-09C","ECSS - Current v1.0","4.4.1a","Requirement","ECSS-Q-ST-70-09_0580021",1,"Created","The customer shall perform the standard audit according to ECSS-Q-ST-10.\n    NOTE 1 The main purpose of a standard audit is to ensure the validity of test results by comparison of the test data on identical materials by different test houses.\n    NOTE 2 The thermo-optical property data from test houses for the projects of the customer, obtained in the manner laid down in this Standard, are only accepted for the projects of the customer if the test house is certified to perform the relevant procedure in this Standard. "]
["ECSS-Q-ST-70-09C","ECSS - Current v1.0","B.2.1d","Requirement","ECSS-Q-ST-70-09_0580040",1,"Created","The audit / review report shall contain the nonconformances."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","5.2j","Requirement","ECSS-Q-ST-70-12_1200007",1,"Unchanged","During the MRR, supplier and PCB manufacturer shall approve the PCB manufacturing dossier, the PCB definition dossier and all Review Items.","NOTE \tThe approvals are recorded in the MRR checklist.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","7.1.1c","Requirement","ECSS-Q-ST-70-12_1200021",2,"Normative Change","In case Molybdenum, CIC layers or AlN is used, it shall be included in the build-up and recorded as a Review Item in the PCB definition dossier. ","NOTE \t1\tSpecific requirements for the build-up are listed in the PCB definition dossier in A.2.1<5>a.3(h).\nNOTE \t2\tOn external layers, copper clad laminate typically achieves better peel strength whereas copper foil achieves better registration.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","7.1.2h","Requirement","ECSS-Q-ST-70-12_1200025",1,"Informative Change","Copper quality “HTE” shall be used for copper clad laminate.","NOTE \tType HTE can be procured in conformance with IPC-4562B Type E, grade 3.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","7.3.3a","Recommendation","ECSS-Q-ST-70-12_1200038",2,"Normative Change","The thickness as-manufactured of a rigid and rigid-flex epoxy PCB should be ≤ 2,4 mm."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","7.4.3g","Permission","ECSS-Q-ST-70-12_1200395",1,"Unchanged","Fine pitch track width and spacing may be used in case:\n1.\tfine pitch tracks are used to route to the footprint of a fine pitch component,\n2.\tthe length of fine pitch tracks is ≤ 20 mm from the solder pad,\n3.\tconformal coating is applied on fine pitch tracks or pads in conformance with the requirement 13.8.4b,\n4.\tthe voltage is ≤ 30V, and\n5.\tit is recorded as a Review Item in the PCB definition dossier.","NOTE \tA long fine pitch track can cause solder pearls.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","7.4.6b","Requirement","ECSS-Q-ST-70-12_1200063",1,"Unchanged","Tracks shall exit from AAD footprint before changing direction to keep the insulation distance to the pad in compliance with normal pitch as specified in Table 7‑5.","NOTE \tSee example of nonconformance indicated by green arrow in Figure 7‑1.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","7.5.3f","Recommendation","ECSS-Q-ST-70-12_1200403",1,"Unchanged","For via holes and component holes on component side the diameter of external pads should be the diameter of as-manufactured hole plus ≥ 0,6 mm."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","7.5.4a","Requirement","ECSS-Q-ST-70-12_1200070",1,"Informative Change","Pads for component holes on external layers shall be circular, except cases specified in the requirement 7.5.4b."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","8.2a","Requirement","ECSS-Q-ST-70-12_1200078",1,"Unchanged","Dynamic applications with flex PCBs shall be project qualified.","NOTE \tThe testing of flex PCBs only covers static applications and the integration of the PCB.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","8.3.4a","Recommendation","ECSS-Q-ST-70-12_1200416",1,"Unchanged","Full copper planes should not be used except the case specified in the requirement 8.3.4b."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","8.4o","Requirement","ECSS-Q-ST-70-12_1200098",1,"Unchanged","When tracks change direction, the angle (p) shall be ≥ 135° as specified in the Figure 8‑2.","NOTE \tIt is recommended to design tracks as straight as possible.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","8.6.2d","Requirement","ECSS-Q-ST-70-12_1200113",1,"Unchanged","Bending of the flex PCB shall be designed not to occur on the termination zone and on an additional distance of 2 mm.","NOTE \t1\tIn the Figure 8‑4 the additional distance is indicated as X.\nNOTE \t2\tEven though no bending is designed to occur on the termination zone, some bending can still occur on the assembled PCB due to the stress on the flex section. A stiffening of the termination zone by implementing double cover layer or adhesive can decrease the bending locally.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","8.7.6c","Requirement","ECSS-Q-ST-70-12_1200128",1,"Informative Change","Bending shall not occur on the full thickness copper.","NOTE \tThe etched track is shown in Figure 8‑6 and copper thickness is specified in Table 8‑2.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","9.3h","Permission","ECSS-Q-ST-70-12_1200432",1,"Unchanged","The rigid-flex PCB may be delivered without a support frame in case the following conditions are met:\n1.\tthe PCB manufacturer delivers the rigid-flex PCB with a support that prevents damage to the PCB during shipment, and\n2.\tthe customer implements a support structure that prevents damage to the rigid-flex PCB during assembly and handling."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","9.6a","Requirement","ECSS-Q-ST-70-12_1200147",1,"Unchanged","The diameter of the pads on flex layers in the rigid section of the PCB shall be ≥ 0,6 mm larger than the diameter of the drilled hole except the case specified in the requirements  9.6b. "]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","10.4.1a","Requirement","ECSS-Q-ST-70-12_1200164",2,"Normative Change","Heat sinks shall be made of copper and inserts of copper-molybdenum-copper, CIC or AlN.","NOTE \t1\tHeat sinks can be foils covering the entire surface of a layer or inserts placed locally under a specific component.\nNOTE \t2\tHeat sinks that consist of a copper layer can be made by using copper foil or copper clad laminate. The advantage of a foil is the ability of prepreg to fill clearances from both sides. The advantages of copper clad laminate is better registration, ease in handling and processing and the possibility of more complex electrical routing in case of split ground planes on heat sinks.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","10.4.3d","Requirement","ECSS-Q-ST-70-12_1200173",1,"Unchanged","The CIC layers shall have a tolerance of ≤ ± 10%."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","11.2c","Requirement","ECSS-Q-ST-70-12_1200186",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","11.4.1n","Permission","ECSS-Q-ST-70-12_1200553",1,"Created","For high speed HDI technology as specified in 11.6b, the build-up of microvia layers may be 3 full and one half microvia layer.","NOTE \tSee Figure 3‑3 for an example of two full and one half microvia layers.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","11.4.2b","Requirement","ECSS-Q-ST-70-12_1200195",1,"Unchanged","The microvia shall be laser drilled."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","11.5.3b","Requirement","ECSS-Q-ST-70-12_1200449",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","11.6a","Requirement","ECSS-Q-ST-70-12_1200564",1,"Created","Polyimide HDI PCB design shall implement the dimensional features from the column \"Polyimide HDI\" in the Table 11‑1, except for specified exceptions in conformance with the requirements 11.4.1k, 11.4.1r + s, 11.4.2h, 11.4.3b, 11.5.1e and 11.5.6c.","NOTE \tAt the time of issuing the revision 1 of this standard, the Polyimide HDI technology is qualified. Exceptions as listed in this requirement are not covered by qualification at the time of issuing. Reliability risks are associated with these exceptions, which can be mitigated for instance by using more stable materials. Therefore, these exceptions are included, and future proof the described technology.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","12.3m","Requirement","ECSS-Q-ST-70-12_1200224",1,"Unchanged","Dedicated representative coupons shall be designed to allow verification of the embedded film resistor values on the etched layer before further lamination."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","12.9a","Permission","ECSS-Q-ST-70-12_1200572",1,"Created","Z-controlled backdrilling of vias may be used in case:\n1.\tthe Z-controlled backdrilling on vias is included on the coupon, and\n2.\tit is recorded as Review Item in the PCB definition dossier.","NOTE \tBackdrilling is done to avoid antenna effect of the via wall of high speed and high frequency applications.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","12.9o","Requirement","ECSS-Q-ST-70-12_1200586",1,"Created","The as-designed backdrilled stub shall be as follows:\n1.\t≥ 150 µm for standard depth tolerance of +/- 100 µm,\n2.\t≥ 100 µm for reduced depth tolerance of +/- 50 µm."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","13.2a","Requirement","ECSS-Q-ST-70-12_1200233",1,"Unchanged","The term “AND” indicates that the largest value of the two shall be used.","NOTE \tThis is explained in Table 13‑1.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","13.6.3h","Requirement","ECSS-Q-ST-70-12_1200248",1,"Unchanged","The current rating of polyimide and epoxy PCBs shall be in conformance with requirements specified in chapter A.4.4 of IPC-2152.","NOTE \tThe chapter A.4.4 in IPC-2152 specifies that there is less than 2% difference.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","13.8.2a","Requirement","ECSS-Q-ST-70-12_1200254",1,"Unchanged","Voltage rating shall apply to the as-manufactured PCB."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","13.8.4a","Recommendation","ECSS-Q-ST-70-12_1200475",1,"Unchanged","Conductors on external layers should be covered with conformal coating."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","13.10d","Requirement","ECSS-Q-ST-70-12_1200588",1,"Created","The single or sequential ‘bond sequence’ specified in the Table 13‑7 for ‘X,Y internal hole wall to hole wall’ shall be determined at the time of drilling."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","13.11.2d","Recommendation","ECSS-Q-ST-70-12_1200483",1,"Unchanged","The controlled impedance tracks should be designed with end-to-end configuration."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","13.12.2d","Requirement","ECSS-Q-ST-70-12_1200302",1,"Unchanged","Ground planes shall be used in high speed digital applications."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","13.12.3.3a","Requirement","ECSS-Q-ST-70-12_1200307",1,"Unchanged","Signals that can affect the performance of the circuit as a result of noise, crosstalk, jitter, ringing or propagation delay, shall be identified as “highly critical”.","NOTE \tExamples of highly critical signals are: PLL signals, low voltage and high frequency LVDS signals.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","13.14c","Permission","ECSS-Q-ST-70-12_1200506",1,"Unchanged","Planes of analog and digital circuitries may be combined in case separation of the planes has an adverse effect on performance or functionality or EMC."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","14.3.3h","Permission","ECSS-Q-ST-70-12_1200512",2,"Normative Change","Test points may be incorporated in the solder pad by extending the pad dimensions so that test probing takes place outside the critical solder joint area in conformance with requirements 12.3.a.21 of the ECSS-Q-ST-70-61. "]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","14.3.4e","Requirement","ECSS-Q-ST-70-12_1200335",1,"Unchanged","The four quadrants of the total footprint of the AAD shall be designed point symmetric such that each quadrant has the asymmetry in four directions.","NOTE \tThis is done to prevent the component drifting away from the footprint during assembly. An example of a point symmetric AAD footprint is given in Figure 14‑5.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","14.5.7a","Requirement","ECSS-Q-ST-70-12_1200352",1,"Unchanged","The pad design for components of type FP and QFP shall be in conformance with the as-manufactured values specified in the Table 14‑10, except for the case specified in 14.5.2c.","NOTE \t1\tAn illustration is given in Figure 14‑12.\nNOTE \t2\tFP means flat pack. QFP means quad flat pack.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","A.2.1<1>a","Requirement","ECSS-Q-ST-70-12_1200361",1,"Unchanged","The PCB definition dossier shall include the following data:\n1.\tDescription, as specified in A.2.1<2>,\n2.\tMechanical layout, as specified in A.2.1<3>,\n3.\tArtwork data , as specified in A.2.1<4>,\n4.\tDrawing, as specified in A.2.1<5>,\n5.\tSpecific electrical test, as specified in A.2.1<6>,\n6.\tReview Items , as specified in A.2.1<7>,\n7.\tCheck list, as specified in A.2.1<8>,"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","5.2f","Requirement","ECSS-Q-ST-70-12_1200004",1,"Unchanged","The PCB manufacturer shall review the PCB definition dossier including Review Items for compliance with the PID."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","6.2.2c","Requirement","ECSS-Q-ST-70-12_1200012",1,"Unchanged","The as-manufactured PCB shall be in conformance with the outgassing requirements of the clause 5.5.3 from the ECSS-Q-ST-70-02 or project specific requirements on cleanliness.","NOTE \tThe outgassing requirements are CVCM<0,1% and RML<1,0%.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","7.1.2d","Recommendation","ECSS-Q-ST-70-12_1200379",1,"Unchanged","Copper distribution within a layer should be homogeneous.","NOTE \tThis is done to ensure even pressure distribution during lamination, which can cause filling voids, cracks or glass compression.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","7.1.3e","Requirement","ECSS-Q-ST-70-12_1200029",2,"Normative Change","The insulation distance as-manufactured between two layers in rigid laminate or prepreg in Z direction shall be in conformance with the values from Table 13‑7.","NOTE \tThis table specifies a minimum projected peak-to-peak distance of 70 µm for non-HDI technology, and 60 µm for HDI, in conformance with 11.4.1h.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","7.4.1a","Recommendation","ECSS-Q-ST-70-12_1200391",1,"Unchanged","A verification should be performed to prevent non-functional changes of direction of tracks.","NOTE \tSome automated routing software can cause unnecessary changes of direction that have no function. \n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","7.4.5b","Requirement","ECSS-Q-ST-70-12_1200056",1,"Unchanged","In case fine pitch tracks are used, this shall be recorded as a Review Item in the PCB definition dossier."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","7.5.2c","Requirement","ECSS-Q-ST-70-12_1200066",2,"Normative Change","When non-functional pads in PTH are removed as specified in the requirement 7.5.2b, the following conditions shall be met:\n1.\tnon-functional pads are present on all copper plane layers,\n2.\tnon-functional pads are present on flex laminate,\n3.\tmaximum half of the non-functional pads in the pad stack are removed,\n4.\tnon-functional pads are removed on maximum two consecutive layers, \n5.\tit is recorded as a Review Item in the PCB definition dossier."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","7.5.3k","Recommendation","ECSS-Q-ST-70-12_1200534",1,"Created","Teardrop reinforcement should be designed on all internal pads.","NOTE \tThis can be implemented by the designer or by the PCB manufacturer. In the latter case it is good practice to review during MRR. An example of teardrop pad design is shown in Figure 11‑4. In this figure “A” is the minimum annular ring between hole and circular pad design; “B” is the effective annular ring with teardrop reinforcement applied.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","7.7a","Requirement","ECSS-Q-ST-70-12_1200072",2,"Normative Change","All areas of the conductive patterns as well as areas of insulating dielectric shall have a dimension of ≥ 0,1 mm in X and Y direction after etch compensation, except for the case of fine pitch track width and spacing as specified in the clause 7.4.5 and 11.5.5.","NOTE \tThis is done to prevent sliver or peelable see Figure 7‑6.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","8.3.2d","Requirement","ECSS-Q-ST-70-12_1200084",1,"Unchanged","The thickness of the polyimide cover layer shall be 25 µm or 50 µm."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","8.4e","Recommendation","ECSS-Q-ST-70-12_1200418",1,"Unchanged","Tracks should be evenly distributed over the entire width of the PCB."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","8.5.2b","Requirement","ECSS-Q-ST-70-12_1200105",1,"Unchanged","Terminal pads shall include PTH.","NOTE \tTerminal pads on single sided board have risk to be damaged during assembly. Terminal pads need to be reinforced by plating.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","8.7.3c","Requirement","ECSS-Q-ST-70-12_1200119",1,"Unchanged","The sculptured shape of the copper shall be manufactured by selective etching of the copper foil."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","8.7.5d","Recommendation","ECSS-Q-ST-70-12_1200429",1,"Informative Change","Component holes with circular pads should have a pad diameter as-designed of ≥ 0,4 mm larger than the drilled diameter.","NOTE \tThis results in an as-designed annular ring of 200 µm.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","9.5a","Requirement","ECSS-Q-ST-70-12_1200143",1,"Unchanged","The hole wall shall be ≥ 2 mm separated from the edge of the rigid part of the PCB.","NOTE \tA larger separation between hole wall and edge of the rigid part is recommended in case it fits within the PCB lay-out.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","10.2a","Requirement","ECSS-Q-ST-70-12_1200149",2,"Normative Change","Design with heat sink or inserts shall be recorded as a Review Item in the PCB definition dossier."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","10.4.2e","Requirement","ECSS-Q-ST-70-12_1200169",2,"Normative Change","The copper foil shall be procured in conformance with the requirements from the IPC-4562B.","NOTE \tTypes of copper foil types commonly used are: HTE grade 3, and JTC grade 1.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","10.4.4a","Requirement","ECSS-Q-ST-70-12_1200177",2,"Normative Change","The mechanical stability of individual clearances of the pattern of the heat sink or insert shall be recorded as a Review Item in the PCB definition dossier.","NOTE \tClearances that are separated by a long straight edge known as ‘thin web’ are a concern for mechanical stability. \n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","11.4.1g","Requirement","ECSS-Q-ST-70-12_1200190",2,"Normative Change","Insulation of microvia layers shall be performed by using 2 sheets of prepreg in conformance with the requirement 7.1.3a, except for the case specified in 11.4.1k."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","11.4.2a","Requirement","ECSS-Q-ST-70-12_1200194",2,"Normative Change","The as-designed aspect ratio of a microvia shall meet the following conditions:\n1.\tit is determined by the sum of the dielectric thickness calculated for the build-up (td) and copper foil thickness (tc), divided by the as-designed drilled diameter (d), in conformance with the formula: (td+tc)/d,\n2.\taspect ratio is ≤ 0,8.","NOTE \t1\tIt is good practice to measure the as-manufactured aspect ratio. This can differ from the as-designed aspect ratio because of resin flow causing local thinner and thicker areas, and copper thickness and etching pattern on the landing layer.\nNOTE \t2\tThe following are two examples of common microvia configurations: In polyimide HDI, microvias of 175 µm diameter are used with 100 µm dielectric thickness and 12 µm copper foil, leading to an aspect ratio of 112/175=0,64. In high speed HDI, microvias of 150 µm diameter are used with 100 µm dielectric thickness and 12 µm copper foil, leading to an aspect ratio of 112/150=0,75.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","11.4.2e","Requirement","ECSS-Q-ST-70-12_1200198",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","11.5.6b","Requirement","ECSS-Q-ST-70-12_1200562",1,"Created","The drill diameter of core vias shall be ≥ 350 µm, except for the case in requirement 11.5.6c."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","12.2c","Permission","ECSS-Q-ST-70-12_1200453",1,"Unchanged","Copper type “electrodeposited - ED” or “rolled and annealed - RA” may be used for copper cladding and copper foils."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","12.5.1a","Requirement","ECSS-Q-ST-70-12_1200226",1,"Unchanged","The spacing and width for external layers of RF PCBs shall be in conformance with the values from Table 7‑4."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","12.9g","Requirement","ECSS-Q-ST-70-12_1200578",1,"Created","The minimum backdrilled diameter is equal to the via diameter + 250 µm."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","12.9h","Requirement","ECSS-Q-ST-70-12_1200579",1,"Created","The minimum diameter of the clearance of a backdrilled hole in planes is equal to the via diameter + 750 µm."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","13.4e","Recommendation","ECSS-Q-ST-70-12_1200465",1,"Unchanged","For power distribution a copper thickness of 35 µm or more should be used.","NOTE \tThin copper tracks of below 35 µm are not suitable for power distribution. Therefore no requirement is specified for thin copper.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","13.7.2b","Recommendation","ECSS-Q-ST-70-12_1200473",1,"Unchanged","Critical tracks should be routed on a single layer."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","13.8.2f","Requirement","ECSS-Q-ST-70-12_1200259",1,"Unchanged","Conductors that are not superimposed in Z direction shall be offset in X,Y direction by the distance for X,Y internal conductor-to-conductor spacing as specified in Table 13‑3 and Table 13‑4. "]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","13.8.4g","Requirement","ECSS-Q-ST-70-12_1200274",1,"Unchanged","Coating types that provide encapsulation of the PCB shall be included as conformal coating.","NOTE \tHigher voltage (> 30 V) PCBs designed without conformal coating are commonly encapsulated by other means, such as potting. Connectors can be potted or coated in similar way. \n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","13.11.3a","Requirement","ECSS-Q-ST-70-12_1200294",1,"Unchanged","Microstrip or stripline shall be used for single ended controlled impedance tracks."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","13.11.3d","Permission","ECSS-Q-ST-70-12_1200485",1,"Unchanged","Differential tracks may be routed non-parallel at the end of the track.","NOTE \tThis is permitted to route to pads.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","13.12.3.1b","Permission","ECSS-Q-ST-70-12_1200495",1,"Unchanged","Non-critical signals specified in the requirement 13.12.3.1a may be routed together in bundles disregarding transients between them.","NOTE \t1\tTransients are temporary anomalies in the electrical signal, such as overshoot, undershoot, ringing, lines reflection, crosstalk.\nNOTE \t2\tTransients are typically expired or reduced to an acceptable level before the sampling time.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","13.13.2.3b","Recommendation","ECSS-Q-ST-70-12_1200499",1,"Unchanged","The length of a track connecting an inverted input of a high speed amplifier with a passive component should be minimised. ","NOTE \tThis reduces the noise coupling to high impedance input of the amplifier. The objective is to guarantee the noise performance of the amplifier.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","14.2d","Requirement","ECSS-Q-ST-70-12_1200319",2,"Normative Change","Assemblies using SnPb solder alloys on gold plated pads shall be in conformance with clause 6.9.2 of ECSS-Q-ST-70-61."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","14.3.4e","Requirement","ECSS-Q-ST-70-12_1200335",1,"Unchanged","The four quadrants of the total footprint of the AAD shall be designed point symmetric such that each quadrant has the asymmetry in four directions.","NOTE \tThis is done to prevent the component drifting away from the footprint during assembly. An example of a point symmetric AAD footprint is given in Figure 14‑5.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","14.5.2a","Requirement","ECSS-Q-ST-70-12_1200341",1,"Unchanged","Insulation distance shall be in conformance with requirements of clauses 13.8, 13.9 and 13.10."]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","15.2b","Recommendation","ECSS-Q-ST-70-12_1200522",1,"Informative Change","In case the PCB design is complex and the coupon cannot be designed with full representativity, the inspection on the coupon should be supplemented by a FAI.","NOTE \tThe different density of a coupon compared to the rest of the PCB can limit the representativity. A higher copper density of the footprint of an AAD compared to a typical coupon design can cause a lower plating thickness. The higher via density of the footprint of an AAD can cause problems with resin flow and filling, which can remain undetected in a coupon of different density. High pressure areas local within the PCB can cause lower dielectric spacing compared to the coupon. Therefore, a specific AAD coupon is specified for HDI technology in conformance with 8.2.3l of ECSS-Q-ST-70-60.\n"]
["ECSS-Q-ST-70-12C Rev.1","ECSS - Current v1.0","A.2.1<7>a","Requirement","ECSS-Q-ST-70-12_1200367",1,"Informative Change","The PCB definition dossier shall include all Review Items.","NOTE \tThe following design features are required to be recorded as Review Items by the present standard:\n1.\tAsymmetric build-up as specified in 7.1.1b,\n2.\tMolybdenum, CIC layers and AlN as specified in 7.1.1c\n3.\tAsymmetric copper cladding as specified in 7.1.2b,\n4.\tTotal copper thickness >700 µm as specified in 7.1.2g, \n5.\tSingle sheet of glass reinforcement in laminate as specified in 7.1.3c,\n6.\t4 mil laminate as specified in 7.1.3f,\n7.\t5 mil laminate at >30V as specified in 7.1.3g,\n8.\tTotal PCB thickness as specified 7.3.2c and 7.3.3c,\n9.\tReduced as-designed track width and spacing as specified in 7.4.3c and 7.4.4c,\n10.\tFine pitch tracks as specified in 7.4.3g, and 7.4.5b,\n11.\tRemoval of non-functional pads as specified in 7.5.2c for PTH and 7.5.2e for core vias, buried vias and through-going vias,\n12.\tReduced as-designed pad dimensions on solder side and component side as specified 7.5.3e and 7.5.3g,\n13.\tPad diameter on rigid laminate <0,3mm larger than drilled hole as specified in 7.5.3j,\n14.\tReduced diameter of internal pads as specified in 7.5.3l,\n15.\tNon-circular pads as specified in 7.5.4b\n16.\tAsymmetric copper planes as specified in 7.6e,\n17.\tMixed surface finish as specified in 7.8.1e,\n18.\t70 µm copper cladding in flex laminate as specified in 8.3.3c,\n19.\tFull copper planes in flex laminate as specified in 8.3.4b,\n20.\t70 µm copper foil in combination with no-flow prepreg as specified in 9.3d,\n21.\tMore than 2 flex laminates as specified in 9.3f, \n22.\tPad diameter on flex laminates <0,6 mm larger than diameter of drilled hole as specified in 9.6b,\n23.\tHeat sinks and their mechanical stability as specified in 10.2a, 10.3.3a and 10.4.4a.\n24.\tConductive surface pattern below external heat sink as specified in 10.3.2g,\n25.\tHDI as specified in 11.2c,\n26.\tBasic copper layer thickness <17 µm as specified in 11.4.1e,\n27.\tDiameter of external capture pad or internal landing pad of microvias that are <0,175 mm larger than the ablated hole for polyimide HDI or <0,15 mm larger for high speed HDI as specified in 11.4.3b,\n28.\tReduced annular ring with teardrop reinforcement as specified in 11.5.2a,\n29.\tDifferential pair routed in AAD footprint as specified in 11.5.5a,\n30.\tAspect ratio of vias >7 as specified in 11.1e,\n31.\tEmbedded film resistors as specified in the requirements 12.3a and 12.3i,\n32.\tThickness of RF PCB >3mm as specified in 12.4b,\n33.\tNumber of layers in RF PCB >8 as specified in 12.4d,\n34.\tReduced insulation distance for RF elements as specified in 12.5.1b,\n35.\tZ-controlled backdrilling as specified in 12.9a,\n36.\tProfiled top layers as specified in 12.8b,\n37.\tProfiled aluminium backing as specified in 12.8c,\n38.\tReduced as–designed insulation distance as specified in 13.10c,\n39.\tControlled impedance tracks as specified in 13.11.2,\n40.\tDesign of test coupon as specified in 15.1b.\n41.\tCopper distribution and thickness after plating of microvia layers with 1 sheet of prepreg as specified in 11.4.1k.7,\n42.\tPossible coverage with SnPb on the side of small SMT pads as specified in 14.2e,\n43.\tPossible tighter tolerances for scaling of external conductors as specified in 6.2.3g of ECSS-Q-ST-70-60,\n44.\tPossible maximum thickness of solder mask on conductor as specified in 8.2.4p of ECSS-Q-ST-70-60,\n45.\tPossible tape testing on PCB as specified in 9.4.5g of ECSS-Q-ST-70-60.\n"]
["ECSS-Q-ST-70-13C Rev. 1","ECSS - Current v1.0","5.1.2.1k","Requirement","ECSS-Q-ST-70-13_0610013",1,"Unchanged","The supplier shall mark all test samples with identification to maintain traceability but in such a way as not to degrade the quality of the sample during testing."]
["ECSS-Q-ST-70-13C Rev. 1","ECSS - Current v1.0","5.1.2.4.2a","Requirement","ECSS-Q-ST-70-13_0610022",1,"Unchanged","The supplier shall identify assemblies submitted for testing, as a minimum, by:\n    1. trade name and batch number;\n    2. name of manufacturer or supplier through whom the purchase was made;\n    3. configuration control status of the assembly."]
["ECSS-Q-ST-70-13C Rev. 1","ECSS - Current v1.0","5.1.4.4b","Requirement","ECSS-Q-ST-70-13_0610037",1,"Unchanged","In case a “top hat” sample support is used, it shall slide into a horizontal fixture slot in such a way that its top surface is parallel to and directly beneath the rubber face of the tape holder."]
["ECSS-Q-ST-70-13C Rev. 1","ECSS - Current v1.0","5.3e","Requirement","ECSS-Q-ST-70-13_0610050",1,"Unchanged","The supplier shall report defects and the appearance of the fracture.\n    ","NOTE 1 Defects for instance can be air bubbles or material inclusions.\nNOTE 2 Appearance of the fracture for instance can be rough, ductile, smooth or brittle."]
["ECSS-Q-ST-70-13C Rev. 1","ECSS - Current v1.0","A.2.1g","Requirement","ECSS-Q-ST-70-13_0610067",1,"Unchanged","The test result sheet shall contain details of equipment used for visual, mechanical, chemical and physical property measurement or inspection, as outlined in Annex B and test specifications where they exist."]
["ECSS-Q-ST-70-14C","ECSS - Current v1.0","5.2g","Requirement","ECSS-Q-ST-70-14_1340011",1,"Created","At the conclusion of testing, the test samples shall be evaluated in accordance with acceptance criteria specified in the requirement 5.2f."]
["ECSS-Q-ST-70-14C","ECSS - Current v1.0","5.4.7b","Requirement","ECSS-Q-ST-70-14_1340024",1,"Created","In Class 6 environments, the corrosion resistance shall be tested for 240 h in accordance with Damp Heat Test at (93 ±3)% RH and (40 ±3)°C.","NOTE \tThe Damp Heat Test method is described in Annex C.\n"]
["ECSS-Q-ST-70-14C","ECSS - Current v1.0","5.5.2j","Requirement","ECSS-Q-ST-70-14_1340037",1,"Created","In case an alkaline etch is used, it shall be followed by an acid neutralization step."]
["ECSS-Q-ST-70-14C","ECSS - Current v1.0","5.6.3a","Requirement","ECSS-Q-ST-70-14_1340046",1,"Created","Chromium plating shall be applied in accordance with specification identified in the DPL specified in the DRD from Annex C from ECSS-Q-ST-70.","NOTE \tISO 6158 or SAE AMS2460 are internationally recognised standards describing chromium plating.\n"]
["ECSS-Q-ST-70-14C","ECSS - Current v1.0","5.9.3b","Requirement","ECSS-Q-ST-70-14_1340064",1,"Created","All designs including fixtures and masking shall prevent of entrapment of water or fluid and ensure drain holes are located for drainage of accumulated fluids. ","NOTE \tRestricting airflow can lead condensation becoming trapped on internal surfaces.\n"]
["ECSS-Q-ST-70-15C","ECSS - Current v1.0","5.1g","Requirement","ECSS-Q-ST-70-15_1470007",1,"Created","The NDT plan prepared by the supplier responsible for the NDT, shall be submitted to the customer for approval."]
["ECSS-Q-ST-70-15C","ECSS - Current v1.0","5.3c","Requirement","ECSS-Q-ST-70-15_1470026",1,"Created","The drawings shall be updated when NDT testing requirements are updated."]
["ECSS-Q-ST-70-15C","ECSS - Current v1.0","6.1.2a","Requirement","ECSS-Q-ST-70-15_1470041",1,"Created","Visual testing of welds shall be performed in accordance with EN ISO 17637:2016."]
["ECSS-Q-ST-70-15C","ECSS - Current v1.0","6.1.3.2c","Requirement","ECSS-Q-ST-70-15_1470048",1,"Created","All devices shall be listed and controlled in the user's measurement instruments calibration list."]
["ECSS-Q-ST-70-15C","ECSS - Current v1.0","6.3.2h","Requirement","ECSS-Q-ST-70-15_1470071",1,"Created","For parts that are shot peened, dry vapour blasted, machine polished or burnished in the testing area the qualification programme shall demonstrate that discontinuities are not closed by the surface processes.","NOTE\tExamples of surface treatments include: shot peened, dry vapour blasted, machine polished or burnished in the testing area.\n"]
["ECSS-Q-ST-70-15C","ECSS - Current v1.0","6.3.6c","Requirement","ECSS-Q-ST-70-15_1470079",1,"Created","Deviations from the procedure shall be reported and subject to the company's NCR process."]
["ECSS-Q-ST-70-15C","ECSS - Current v1.0","6.4.4.2a","Requirement","ECSS-Q-ST-70-15_1470101",1,"Created","The instrument for the eddy-current testing shall be equipped with complex plane and time-synchronous display."]
["ECSS-Q-ST-70-15C","ECSS - Current v1.0","6.4.7.2g","Requirement","ECSS-Q-ST-70-15_1470116",1,"Created","The reference material blocks shall be certified and approved by the Company ET/Level 2 as the minimum."]
["ECSS-Q-ST-70-15C","ECSS - Current v1.0","6.4.8.2d","Permission","ECSS-Q-ST-70-15_1470120",1,"Created","For automated eddy-current testing or testing with signal recording and analysis a reduction of the ratio specified 6.4.8.2c, as approved by the customer, may be applied. "]
["ECSS-Q-ST-70-15C","ECSS - Current v1.0","6.6.4a","Requirement","ECSS-Q-ST-70-15_1470146",1,"Created","For X-ray radiographic testing of welds, the valleys between beads weld ripples or other surface irregularities shall be smooth to a degree such that the resulting X-ray contrast due to surface irregularities cannot mask or confused with any other discontinuities."]
["ECSS-Q-ST-70-15C","ECSS - Current v1.0","6.6.6a","Requirement","ECSS-Q-ST-70-15_1470151",1,"Created","Image quality indicators shall be used to evaluate quality of X-ray images. ","NOTE\tThe diameter of the holes or the diameter of the wires of each IQI is associated to a numerical value indicating the quality and sensitivity of the resultant X-ray.\n"]
["ECSS-Q-ST-70-15C","ECSS - Current v1.0","6.7.4.5a","Requirement","ECSS-Q-ST-70-15_1470176",1,"Created","The ultrasonic test documentation shall be in compliance with NDT report from the DRD from Annex B."]
["ECSS-Q-ST-70-15C","ECSS - Current v1.0","6.7.5.4e","Requirement","ECSS-Q-ST-70-15_1470186",1,"Created","If there is a difference in the acoustic properties between the reference blocks and the part to be tested, a sensitivity correction shall be made to compensate the difference.","NOTE\tThe transfer correction is achieved by noting the difference between the signals received from the same reference reflector, e.g. the back wall, in the reference block and the test object. Back wall reflection is corrected by adding or removing attenuation.\n"]
["ECSS-Q-ST-70-15C","ECSS - Current v1.0","8.3.3a","Requirement","ECSS-Q-ST-70-15_1470205",1,"Created","The following discontinuities depending on their size shall be the cause for rejection of wrought products:\n1.\tInclusions\n2.\tDelamination\n3.\tDoublings\n4.\tFolds\n5.\tCracks\n6.\tLaps"]
["ECSS-Q-ST-70-15C","ECSS - Current v1.0","8.6.3.1b","Requirement","ECSS-Q-ST-70-15_1470221",1,"Created","Laminated composites shall be subjected to ultrasonic testing in accordance with ASTM E2533-17e1 for Aerospace Applications."]
["ECSS-Q-ST-70-15C","ECSS - Current v1.0","8.6.3.2a","Requirement","ECSS-Q-ST-70-15_1470223",1,"Created","The radioscopic testing shall be used for detecting volumetric discontinuities and density variations that are resulting of the presence of gas porosity, delamination cracks or inclusions."]
["ECSS-Q-ST-70-15C","ECSS - Current v1.0","8.6.4.3d","Requirement","ECSS-Q-ST-70-15_1470236",1,"Created","The number of demonstration samples required shall respect any requirement to account for statistical variation of material characteristics during manufacturing and agreed between customer and supplier."]
["ECSS-Q-ST-70-15C","ECSS - Current v1.0","9.2.1c","Requirement","ECSS-Q-ST-70-15_1470258",1,"Created","Personnel performing Special fracture control NDT activities shall be qualified and certified for each Special fracture control NDT method in accordance with NAS 410:2014 Level 2 and EN 4179:2017. "]
["ECSS-Q-ST-70-15C","ECSS - Current v1.0","9.2.2.1d","Requirement","ECSS-Q-ST-70-15_1470265",1,"Created","Standard fracture control NDT shall provide crack detection to at least 90 % probability and 95 % confidence level. ","NOTE\t1\tFor various NDT techniques and part geometries Table 9‑1 gives the largest crack sizes that can remain undetected at these probability and confidence levels.\nNOTE\t2\tDedicated capability demonstration is not needed for the method specified in clause 9.2.3 if not required by 9.2.2.1c.\n"]
["ECSS-Q-ST-70-15C","ECSS - Current v1.0","9.2.2.3a","Requirement","ECSS-Q-ST-70-15_1470281",1,"Created","Crack screening proof testing shall be performed in accordance with requirements from clause 10.4.2.3 of ECSS-E-ST-32-01."]
["ECSS-Q-ST-70-15C","ECSS - Current v1.0","9.3.2.3c","Requirement","ECSS-Q-ST-70-15_1470295",1,"Created","The capability of the testing method shall be investigated on at least five specimens in order to analyse all parameters of discontinuities.","NOTE\t1\tParameters of a discontinuity to be investigated include defect type, position, size, shape and orientation.\nNOTE\t2\tDepending on, for example, the complexity of the part to be tested and the criticality of the discontinuities to be found, the number of samples to be used can be significantly higher than five. Example: human space flight.\n"]
["ECSS-Q-ST-70-15C","ECSS - Current v1.0","B.2.1<2.6>a","Requirement","ECSS-Q-ST-70-15_1470311",1,"Created","The X-ray radiographic test report shall contain information in accordance with documentation requirements from ASTM E 1742/E1742M:2018 or EN ISO 17636:2013-1 and EN ISO 17636-2:2013."]
["ECSS-Q-ST-70-16C","ECSS - Current v1.0","5.2i","Requirement","ECSS-Q-ST-70-16_1460009",1,"Created","For application of adhesive tape for passive thermal control requirements from clause 4 of ECSS-Q-ST-70-09 shall apply for thermo-optical measurements.\n","NOTE\tTape application procedure can have an impact on the tape thermo-optical properties.\n"]
["ECSS-Q-ST-70-16C","ECSS - Current v1.0","6.3b","Requirement","ECSS-Q-ST-70-16_1460019",1,"Created","Date of the bonding process steps shall be recorded.\n"]
["ECSS-Q-ST-70-16C","ECSS - Current v1.0","7.5d","Requirement","ECSS-Q-ST-70-16_1460035",1,"Created","In case a repair process of adhesive bond exists, the test items shall be manufactured and tested according to the verification sequence.\n","NOTE\tTypical examples of repairs are : debonding/breakage of MLI studs, bonding of additional fixtures in cabling.\n"]
["ECSS-Q-ST-70-16C","ECSS - Current v1.0","7.12.2a","Requirement","ECSS-Q-ST-70-16_1460060",1,"Created","Thermal cycling test conditions shall be agreed with the customer.\n"]
["ECSS-Q-ST-70-16C","ECSS - Current v1.0","7.12.2e","Permission","ECSS-Q-ST-70-16_1460064",1,"Created","Thermal vacuum cycling may be omitted in case the robustness of the adhesive bonding to thermal vacuum can be demonstrated by experience from former projects.\n"]
["ECSS-Q-ST-70-16C","ECSS - Current v1.0","8.4a","Requirement","ECSS-Q-ST-70-16_1460081",1,"Created","The supplier shall identify, manage and process materials and parts with hazardous characteristic according to requirements from clause 5 to clause 8 of ECSS-Q-ST-40.\n"]
["ECSS-Q-ST-70-16C","ECSS - Current v1.0","8.7b","Requirement","ECSS-Q-ST-70-16_1460094",1,"Created","Calibration control shall comply with the requirement from clause 5.2.6 of ECSS-Q-ST-20.\n"]
["ECSS-Q-ST-70-16C","ECSS - Current v1.0","8.10d","Requirement","ECSS-Q-ST-70-16_1460116",1,"Created","The inspection shall be performed by an inspector independent of the operators executing the bonding process."]
["ECSS-Q-ST-70-16C","ECSS - Current v1.0","8.11f","Requirement","ECSS-Q-ST-70-16_1460124",1,"Created","Training shall include at least the following points:\n1.\tAdhesive bonding process\n2.\tComplexity of configurations\n3.\tReproducibility\n4.\tHandling of raw materials, process chemicals and equipment\n5.\tCleanliness and contamination control of environment, materials and equipment\n6.\tSafety-related aspects of materials and process chemicals.\n","NOTE\tExamples of complexity of configurations are complex shapes, fragile or sensitive materials, multi-step integration processes.\n"]
["ECSS-Q-ST-70-17C","ECSS - Current v1.0","5.2b","Requirement","ECSS-Q-ST-70-17_1380007",1,"Created","The conditions and methods for coating qualification testing shall conform to the coating procurement specification."]
["ECSS-Q-ST-70-17C","ECSS - Current v1.0","5.3c","Requirement","ECSS-Q-ST-70-17_1380022",1,"Created","Acceptance tests for paints shall be performed in accordance with ECSS-Q-ST-70-31."]
["ECSS-Q-ST-70-17C","ECSS - Current v1.0","6.2f","Requirement","ECSS-Q-ST-70-17_1380039",1,"Created","For gold electrolytic coatings the adhesion test method shall be selected from ISO 4524-5:1985."]
["ECSS-Q-ST-70-17C","ECSS - Current v1.0","6.4c","Requirement","ECSS-Q-ST-70-17_1380054",1,"Created","For metallic coatings > 1 μm, the vacuum shall be omitted","NOTE\tIt is commonly accepted that the adhesion test puts more stress on these coatings than stresses induced by vacuum.\n"]
["ECSS-Q-ST-70-17C","ECSS - Current v1.0","6.7c","Requirement","ECSS-Q-ST-70-17_1380068",1,"Created","The radiation test shall be performed using fully flight representative substrates with known radiation characteristics for the mission environment."]
["ECSS-Q-ST-70-17C","ECSS - Current v1.0","C.2.1a","Requirement","ECSS-Q-ST-70-17_1380082",1,"Created","The coating acceptance test report shall include the following information: \n1.\tList of coated parts with part reference \n2.\tReference to Coating Specification\n3.\tCoating deposition lot \n4.\tQuantity \n5.\tControl report for Acceptance test set and relative results\n6.\tNonconformance Report for NC parts and defect descriptions\n7.\tPerformance measurements\n8.\tStatement of Declaration or Certificate of Conformity\n9.\tSignature or Stamp of QA manager and of inspectors"]
["ECSS-Q-ST-70-18C","ECSS - Current v1.0","5.1.2d","Requirement","ECSS-Q-ST-70-18_0620011",1,"Created","The supplier shall use a filter system to supply fresh air to the room, so that there is a positive pressure difference with respect to adjacent rooms."]
["ECSS-Q-ST-70-18C","ECSS - Current v1.0","5.1.4.6a","Requirement","ECSS-Q-ST-70-18_0620030",1,"Created","The supplier shall use thermal cycling cabinets, ovens, refrigeration units or cold chambers capable of maintaining temperatures between -50 °C and +90 °C\n    NOTE Under certain circumstances (see Table 5-2 step 3.3) greater temperature extremes can be required."]
["ECSS-Q-ST-70-18C","ECSS - Current v1.0","5.2.2c","Requirement","ECSS-Q-ST-70-18_0620042",1,"Created","The supplier shall only use pure rosin flux for spacecraft assembly work.\n    NOTE An example of pure rosin flux is J-STD-004 Type ROL0."]
["ECSS-Q-ST-70-18C","ECSS - Current v1.0","5.3.1a","Requirement","ECSS-Q-ST-70-18_0620060",1,"Created","The supplier shall ensure that the delivered coaxial cables are in the form of straight lengths.\n    NOTE The initial preparation is similar for each cable diameter and each connector type and whether joining is by soldering or crimping."]
["ECSS-Q-ST-70-18C","ECSS - Current v1.0","5.3.4h","Requirement","ECSS-Q-ST-70-18_0620075",1,"Created","The supplier shall prevent wrinkling or cracking when forming the cable."]
["ECSS-Q-ST-70-18C","ECSS - Current v1.0","5.3.6b","Requirement","ECSS-Q-ST-70-18_0620083",1,"Created","The supplier shall cut the cable to size such that when it is assembled it fits with minimum stress."]
["ECSS-Q-ST-70-18C","ECSS - Current v1.0","5.4.2m","Recommendation","ECSS-Q-ST-70-18_0620217",1,"Created","The supplier should perform pretinning just before proceeding with the assembly of the connector on the cable."]
["ECSS-Q-ST-70-18C","ECSS - Current v1.0","5.5.1.1.1d","Requirement","ECSS-Q-ST-70-18_0620114",1,"Created","The supplier shall solder the centre contact to the centre conductor with the solder specified in clause 5.2.1 and the equipment specified in clause 5.1.4.7."]
["ECSS-Q-ST-70-18C","ECSS - Current v1.0","5.5.1.2l","Requirement","ECSS-Q-ST-70-18_0620135",1,"Created","After the solder has solidified and cooled, the supplier shall clean the joint with one of the solvent cleaners specified in clause 5.2.3."]
["ECSS-Q-ST-70-18C","ECSS - Current v1.0","5.5.3f","Requirement","ECSS-Q-ST-70-18_0620150",1,"Created","The storage packaging shall be adequate to protect the cable against deformation, damage and contamination."]
["ECSS-Q-ST-70-18C","ECSS - Current v1.0","5.6.2a","Requirement","ECSS-Q-ST-70-18_0620165",1,"Created","The supplier shall unpack and inspect the cable as defined in requirements 5.6.1a to 5.6.1c.."]
["ECSS-Q-ST-70-18C","ECSS - Current v1.0","5.7.3a","Requirement","ECSS-Q-ST-70-18_0620180",1,"Created","After completion of the temperature cycling, the supplier shall subject the test specimen to vibration."]
["ECSS-Q-ST-70-18C","ECSS - Current v1.0","5.8.2b","Requirement","ECSS-Q-ST-70-18_0620186",1,"Created","If a repair procedure is agreed, the supplier shall perform it in conformance with ECSS-Q-ST-70-28."]
["ECSS-Q-ST-70-20C","ECSS - Current v1.0","5.1.2a","Requirement","ECSS-Q-ST-70-20_0630003",1,"Created","The samples of wires and cables submitted for testing shall be identified by the following:\n    1. Trade name\n    2. Source\n    3. Manufacturer’s code number\n    4. Batch number\n    5. Date of manufacture"]
["ECSS-Q-ST-70-20C","ECSS - Current v1.0","5.2.1i","Requirement","ECSS-Q-ST-70-20_0630014",1,"Created","The length of outer insulation to be removed shall be (20 ± 5) mm from the sample end as shown in Figure 5-1."]
["ECSS-Q-ST-70-20C","ECSS - Current v1.0","A.2.1e","Requirement","ECSS-Q-ST-70-20_0630032",1,"Created","The evaluation report shall contain the date of test completion."]
["ECSS-Q-ST-70-21C","ECSS - Current v1.0","5.1.1.3.1b","Requirement","ECSS-Q-ST-70-21_0640014",1,"Created","The supplier shall filter the air used for ventilation to prevent contamination of the workpieces by moisture, oil or dust."]
["ECSS-Q-ST-70-21C","ECSS - Current v1.0","5.1.2.1b","Requirement","ECSS-Q-ST-70-21_0640017",1,"Created","Materials failing to meet the requirements of the applicable screening test shall be subject to testing in configuration."]
["ECSS-Q-ST-70-21C","ECSS - Current v1.0","5.1.2.2.8b","Requirement","ECSS-Q-ST-70-21_0640043",1,"Created","Timing shall be started at the first visual indication of combustion and stopped when the flame ceases to propagate upwards.\n    NOTE Where appropriate it is acceptable to record the total burn length either directly or by subtraction; In this case, overestimation of the burn length can occur by measuring soot deposits higher up the sample."]
["ECSS-Q-ST-70-21C","ECSS - Current v1.0","5.1.2.2.12a","Requirement","ECSS-Q-ST-70-21_0640052",1,"Created","The supplier shall document the test results in conformance with the DRD in Annex A."]
["ECSS-Q-ST-70-21C","ECSS - Current v1.0","5.1.2.3.2c","Requirement","ECSS-Q-ST-70-21_0640058",1,"Created","The supplier shall carry out the flammability tests with an exhaust connected."]
["ECSS-Q-ST-70-21C","ECSS - Current v1.0","5.1.2.4.1a","Requirement","ECSS-Q-ST-70-21_0640074",1,"Created","The supplier shall use the electrical wire insulation flammability test only for gauges AWG 20 to AWG 10 with copper conductors and for normal pressures with a maximum oxygen concentration of volume fraction 25 %."]
["ECSS-Q-ST-70-21C","ECSS - Current v1.0","5.1.2.4.5b","Requirement","ECSS-Q-ST-70-21_0640089",1,"Created","The external electrical supply shall include voltage and current meters capable of measuring the voltage drop across the wire and the current flowing through it to two decimal places."]
["ECSS-Q-ST-70-21C","ECSS - Current v1.0","5.1.2.4.14a","Requirement","ECSS-Q-ST-70-21_0640103",1,"Created","Prior to flame application there shall be no spontaneous combustion, splitting of the insulation or baring of the conductor."]
["ECSS-Q-ST-70-21C","ECSS - Current v1.0","5.2.3c","Requirement","ECSS-Q-ST-70-21_0640124",1,"Created","The supplier shall notify the customer of the nonconformance details."]
["ECSS-Q-ST-70-21C","ECSS - Current v1.0","A.2.1<1.8>a","Requirement","ECSS-Q-ST-70-21_0640133",1,"Created","The test report shall contain the maximum specified temperature."]
["ECSS-Q-ST-70-22C","ECSS - Current v1.0","4.1.1b","Requirement","ECSS-Q-ST-70-22_0170002",1,"Created","Procedures to control hazards, health and safety to personnel, equipment or materials shall be defined and implemented."]
["ECSS-Q-ST-70-22C","ECSS - Current v1.0","4.1.4a","Requirement","ECSS-Q-ST-70-22_0170014",1,"Created","To extend the shelf-life of a material that has exceeded its shelf-life, the following activities shall be performed:\n    1. Re-certify the material for the first time by using the relevant tests in conformance with clause 4.1.6;\n    2. If the first re-certification is successful, extend the shelf-life equal to half the initial shelf-life;\n    3. Re-certify the material for the second time on a case-by-case basis depending on product, application, storage and user experience;\n    4. If the second re-certification is successful, extend the shelf-life to half of the first extension."]
["ECSS-Q-ST-70-26C Rev.1 Corr.1","ECSS - Current v1.0","5.1.1.2c","Requirement","ECSS-Q-ST-70-26_0130003",1,"Informative Change","Loose material that can cause contamination of the crimped connection shall be removed. ","NOTE \tFor example: Dirt, dust, oils and cut wire strands.\n"]
["ECSS-Q-ST-70-26C Rev.1 Corr.1","ECSS - Current v1.0","5.1.2.1h","Requirement","ECSS-Q-ST-70-26_0130021",2,"Normative Change","Tools used in the crimping operation shall be clean and excess lubricant removed before crimping starts."]
["ECSS-Q-ST-70-26C Rev.1 Corr.1","ECSS - Current v1.0","5.1.2.3e","Requirement","ECSS-Q-ST-70-26_0130031",2,"Normative Change","The cutting edges shall be regularly checked for damage and maintained in a sharp condition."]
["ECSS-Q-ST-70-26C Rev.1 Corr.1","ECSS - Current v1.0","5.2.2c","Requirement","ECSS-Q-ST-70-26_0130045",1,"Unchanged","The supplier shall use high strength copper alloy wire for 24 AWG, 26 AWG and 28 AWG crimped joints.","NOTE \tSoft or annealed copper wire are not acceptable for crimped joints of 24 AWG, 26 AWG and 28 AWG size. \n"]
["ECSS-Q-ST-70-26C Rev.1 Corr.1","ECSS - Current v1.0","5.2.5i","Requirement","ECSS-Q-ST-70-26_0130173",1,"Created","For 28 AWG up to 16 AWG wire sizes the maximum insulation clearance shall be maintained between 0,3 mm and 1,0 mm."]
["ECSS-Q-ST-70-26C Rev.1 Corr.1","ECSS - Current v1.0","5.2.7a","Requirement","ECSS-Q-ST-70-26_0130068",2,"Normative Change","Only tools specified by the manufacturer of the terminals shall be used."]
["ECSS-Q-ST-70-26C Rev.1 Corr.1","ECSS - Current v1.0","5.3.1f","Requirement","ECSS-Q-ST-70-26_0130179",1,"Created","In case the mission environment exceeds the temperature range for which the materials are qualified, a qualification shall be performed and agreed with the customer ","NOTE \tExamples of materials include cables and crimp items.\n"]
["ECSS-Q-ST-70-26C Rev.1 Corr.1","ECSS - Current v1.0","5.4.2b","Requirement","ECSS-Q-ST-70-26_0130087",2,"Deleted","<<deleted>> "]
["ECSS-Q-ST-70-26C Rev.1 Corr.1","ECSS - Current v1.0","5.4.3.4c","Requirement","ECSS-Q-ST-70-26_0130193",1,"Created","In the case of different wire sizes crimped into the same barrel axial strength measurements shall be performed on only one wire per sample from the smallest gauge "]
["ECSS-Q-ST-70-26C Rev.1 Corr.1","ECSS - Current v1.0","5.4.4i","Requirement","ECSS-Q-ST-70-26_0130104",2,"Normative Change","The following acceptance criteria shall be met:\n1.\tEach micro section is free from contamination;\n2.\tThe crimp barrel is evenly deformed;\n3.\tVoids occupy less than 10 % of the cross sectioned area of the wire volume;\n4.\tThe wires and barrel appear as a gas-tight joint and conform to the workmanship sample prepared during qualification;\n5.\tAll  strands are deformed from their circular cross section;\n6.\tThere are no indentations or fracturing of the deformed receptacle barrel or its plated finish.","NOTE\tFor ferrule shield crimping the requirements of 5.4.4i.3. and 5. are not applicable.\n"]
["ECSS-Q-ST-70-26C Rev.1 Corr.1","ECSS - Current v1.0","5.5.3d","Requirement","ECSS-Q-ST-70-26_0130117",2,"Normative Change","The operator shall discard production crimps which are defective."]
["ECSS-Q-ST-70-26C Rev.1 Corr.1","ECSS - Current v1.0","5.5.4.3c","Permission","ECSS-Q-ST-70-26_0130227",1,"Created","Pre-crimp inspection may be performed by an operator who has successfully followed and passed an internal training scheme which has been implemented by QA as specified in 5.5.2."]
["ECSS-Q-ST-70-26C Rev.1 Corr.1","ECSS - Current v1.0","5.5.6.1c","Requirement","ECSS-Q-ST-70-26_0130139",1,"Unchanged","The QA organization of the supplier shall notify the customer of the nonconformance details."]
["ECSS-Q-ST-70-26C Rev.1 Corr.1","ECSS - Current v1.0","5.5.7a","Requirement","ECSS-Q-ST-70-26_0130152",1,"Unchanged","The supplier shall maintain traceability throughout the process from incoming inspection to final test, including details of test equipment, tools and personnel employed in performing the task."]
["ECSS-Q-ST-70-26C Rev.1 Corr.1","ECSS - Current v1.0","5.6b","Requirement","ECSS-Q-ST-70-26_0130158",1,"Unchanged","The format of the documents shall be in accordance with the deliverables item list defined in the business agreement.","NOTE \tNo specific DRD requirements emerge from this Standard.\n"]
["ECSS-Q-ST-70-28C","ECSS - Current v1.0","4.2.2d","Requirement","ECSS-Q-ST-70-28_0150015",1,"Created","Repairs involving epoxy adhesives shall not exceed four to any one area of 25 cm2."]
["ECSS-Q-ST-70-28C","ECSS - Current v1.0","4.6.3a","Requirement","ECSS-Q-ST-70-28_0150034",1,"Created","The solder on the area to be repaired shall be accessible."]
["ECSS-Q-ST-70-28C","ECSS - Current v1.0","4.8.3.2a","Requirement","ECSS-Q-ST-70-28_0150045",1,"Created","After repair, the supplier shall inspect the soldered joints in conformance with the accept/reject criteria of clause 12 in ECSS-ST-Q-70-08. \n    ","NOTE For example: Inspection of the pad or track area to ensure that no lifting has occurred and that no damage has been sustained by the base material is one of the required inspections."]
["ECSS-Q-ST-70-28C","ECSS - Current v1.0","4.10.2b","Requirement","ECSS-Q-ST-70-28_0150055",1,"Created","Before applying method E.3.1 or E.3.2, the supplier shall remove any components or solder that can interfere with the repair of the damaged conductor as described in clauses 4.7 and 4.15 before proceeding."]
["ECSS-Q-ST-70-28C","ECSS - Current v1.0","4.13.2a","Recommendation","ECSS-Q-ST-70-28_0150138",1,"Created","The supplier should use method H.3. "]
["ECSS-Q-ST-70-28C","ECSS - Current v1.0","4.14.3a","Requirement","ECSS-Q-ST-70-28_0150090",1,"Created","After repair, the supplier shall inspect the soldered joints in conformance with the accept/reject criteria of clause 12 in ECSS-Q-ST-70-08. \n    ","NOTE For example: Inspection of the pad or track area to ensure that no lifting has occurred and that no damage has been sustained by the base material is one of the required inspections."]
["ECSS-Q-ST-70-28C","ECSS - Current v1.0","4.17.2f","Recommendation","ECSS-Q-ST-70-28_0150152",1,"Created","The supplier should use method L.3.7 if it is necessary to isolate no more than one third of the leads per side of a DIL package."]
["ECSS-Q-ST-70-28C","ECSS - Current v1.0","4.19.5a","Requirement","ECSS-Q-ST-70-28_0150120",1,"Created","The supplier shall maintain traceability from incoming inspection to final test, including details of test equipment, serial numbers and personnel employed in performing the task."]
["ECSS-Q-ST-70-29C","ECSS - Current v1.0","4.1.1.2c","Requirement","ECSS-Q-ST-70-29_0650004",1,"Created","Coatings and finishes shall be coated on a clean aluminium substrate. "]
["ECSS-Q-ST-70-29C","ECSS - Current v1.0","4.2.2c","Requirement","ECSS-Q-ST-70-29_0650026",1,"Created","The test chamber shall be constructed out of materials that do not offgass beyond the background level.\n    NOTE Refer to the note in 4.3."]
["ECSS-Q-ST-70-29C","ECSS - Current v1.0","4.2.4c","Requirement","ECSS-Q-ST-70-29_0650039",1,"Created","A second gas chromatograph equipped with a gas sampling loop, pneumatic valves, a methanizer and a flame ionization detector shall be used for the determination of carbon monoxide, methane and total organics (screening test).\n    NOTE Packed columns are sufficient in this case."]
["ECSS-Q-ST-70-29C","ECSS - Current v1.0","4.5.2e","Requirement","ECSS-Q-ST-70-29_0650056",1,"Created","The supplier shall assess the possible toxic hazards.\n    NOTE Those toxic hazards due to the volatile contamination evolved from the assembled article under investigation and for impacts on the potential toxicity of the total quantity of offgassed products from all contaminant generating items for a given mission."]
["ECSS-Q-ST-70-30C","ECSS - Current v1.0","5.1.2.3a","Requirement","ECSS-Q-ST-70-30_0120005",1,"Created","Adequate illumination conditions of the wire-wrapping workstations shall be implemented as follows:\n    1. light intensity with a minimum of 1080 lux on the work surface. \n    2. at least 90 % of the work area are shadowless and without severe reflections."]
["ECSS-Q-ST-70-30C","ECSS - Current v1.0","5.1.3.2b","Requirement","ECSS-Q-ST-70-30_0120009",1,"Created","Any tool not conforming with requirement 5.1.3.2a shall be removed from the work area."]
["ECSS-Q-ST-70-30C","ECSS - Current v1.0","5.1.6.2a","Requirement","ECSS-Q-ST-70-30_0120036",1,"Created","The test samples shall undergo 200 temperature cycles in a chamber from room temperature to -55 °C, to +100 °C and back to room temperature (22 ± 3)°C at a rate not exceeding 10 °C per minute. "]
["ECSS-Q-ST-70-30C","ECSS - Current v1.0","5.2.1.2c","Requirement","ECSS-Q-ST-70-30_0120046",1,"Created","Bending, stretching, or other cold working of the wire shall be avoided to preclude damage to the base material or plating."]
["ECSS-Q-ST-70-30C","ECSS - Current v1.0","5.2.1.3a","Requirement","ECSS-Q-ST-70-30_0120051",1,"Created","The insulation shall consist of flexible polymer materials with low out-gassing properties, in conformance with ECSS-Q-ST-70-02.\n    NOTE Recommended insulation materials include ETFE (Tefzel), PFA (Perfluoroalkoxy), PVDF (Kynar), and Kapton polyimide over extruded PTFE."]
["ECSS-Q-ST-70-30C","ECSS - Current v1.0","5.2.2.2e","Requirement","ECSS-Q-ST-70-30_0120067",1,"Created","Bent terminals shall be rejected."]
["ECSS-Q-ST-70-30C","ECSS - Current v1.0","5.3.2.1c","Requirement","ECSS-Q-ST-70-30_0120083",1,"Created","In case of necessary rework, the wrapped wire shall be uncoiled using an approved hand tool (see clause 5.1.3.4), to preserve the corners of the terminal post."]
["ECSS-Q-ST-70-30C","ECSS - Current v1.0","5.3.4c","Requirement","ECSS-Q-ST-70-30_0120096",1,"Created","Disturbed joints shall be rejected and replaced."]
["ECSS-Q-ST-70-30C","ECSS - Current v1.0","5.4.4c","Requirement","ECSS-Q-ST-70-30_0120118",1,"Created","The voltage drop shall be measured between the first turn of uninsulated conductor, and the terminal post, by using probe contacts suitable to the wire size."]
["ECSS-Q-ST-70-30C","ECSS - Current v1.0","5.4.6e","Requirement","ECSS-Q-ST-70-30_0120126",1,"Created","The specimen shall be ground with the aid of grades of silicon carbide papers in order to expose the mid-section of the joint."]
["ECSS-Q-ST-70-30C","ECSS - Current v1.0","5.5.2d","Requirement","ECSS-Q-ST-70-30_0120141",1,"Created","Wire wrapped too high on the terminal post shall be reworked (see Figure 5-4, case C)."]
["ECSS-Q-ST-70-30C","ECSS - Current v1.0","5.6.4a","Requirement","ECSS-Q-ST-70-30_0120155",1,"Created","The supplier shall disposition any nonconformance, which is observed in respect of the process in conformance with the quality assurance requirements of ECSS-Q-ST-20."]
["ECSS-Q-ST-70-30C","ECSS - Current v1.0","5.6.7b","Requirement","ECSS-Q-ST-70-30_0120171",1,"Created","A training programme shall be developed, maintained and implemented to provide for excellence of workmanship and personnel skill, careful and safe operations, and improvement of the quality of wrapped joints."]
["ECSS-Q-ST-70-31C Rev.1","ECSS - Current v1.0","4.1.1d","Requirement","ECSS-Q-ST-70-31_0660004",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-70-31C Rev.1","ECSS - Current v1.0","4.2.2.1d","Requirement","ECSS-Q-ST-70-31_0660015",1,"Unchanged","Coated surfaces shall be shielded from contact by using appropriate bags or sheets.","NOTE \tThe suitable bags are for example plastic bags with desiccators, sheet of tissue-paper, sheet of polyethylene foam.\n"]
["ECSS-Q-ST-70-31C Rev.1","ECSS - Current v1.0","4.2.4.2c","Requirement","ECSS-Q-ST-70-31_0660030",1,"Unchanged","During paint operations the temperature of the workpiece shall not fall below the dew point of the ambient air."]
["ECSS-Q-ST-70-31C Rev.1","ECSS - Current v1.0","4.2.5g","Requirement","ECSS-Q-ST-70-31_0660041",1,"Unchanged","All containers to be used for preparing paints shall be cleaned and dried so that the paint is not contaminated."]
["ECSS-Q-ST-70-31C Rev.1","ECSS - Current v1.0","4.3.2e","Requirement","ECSS-Q-ST-70-31_0660060",1,"Unchanged","Parts shall be coated as soon as possible after cleaning.","NOTE \tWhen using solvents, it is important to take care of the dewpoint.\n"]
["ECSS-Q-ST-70-31C Rev.1","ECSS - Current v1.0","4.3.4.2a","Requirement","ECSS-Q-ST-70-31_0660076",1,"Unchanged","Unmasking shall be performed after the paint is sufficiently dried or cured to avoid damage."]
["ECSS-Q-ST-70-31C Rev.1","ECSS - Current v1.0","4.3.6.2a","Requirement","ECSS-Q-ST-70-31_0660090",1,"Unchanged","For paint brush repairing, cleaning shall consist in:\n1.\tremoving any non adhesive part on the area to repair with a small wooden stick;\n2.\tcutting the edges with a scalpel, to obtain bevelled sides;\n3.\tcleaning the area to repair with a thinner soaked cotton stick;\n4.\tmoistening the adjacent paint with the same thinner."]
["ECSS-Q-ST-70-31C Rev.1","ECSS - Current v1.0","4.5.5a","Requirement","ECSS-Q-ST-70-31_0660107",1,"Unchanged","Traceability shall be maintained throughout the process from incoming inspection to final test, including details of test equipment and personnel employed in performing the task."]
["ECSS-Q-ST-70-36C","ECSS - Current v1.0","5.2.3.3b","Requirement","ECSS-Q-ST-70-36_0670013",1,"Created","Materials listed in Table 5-2 shall not be used for applications involving high installation stress.\n    NOTE Examples of application involving high stress are springs or fasteners"]
["ECSS-Q-ST-70-36C","ECSS - Current v1.0","C.2.1<4>a","Requirement","ECSS-Q-ST-70-36_0670028",1,"Created","The SCEF shall contain the declared material list identification."]
["ECSS-Q-ST-70-36C","ECSS - Current v1.0","C.2.1<11>a","Requirement","ECSS-Q-ST-70-36_0670037",1,"Created","An estimate of stresses shall be carried out. "]
["ECSS-Q-ST-70-37C","ECSS - Current v1.0","5.1c","Requirement","ECSS-Q-ST-70-37_0680003",1,"Created","The test shall be carried out under alternate immersion conditions."]
["ECSS-Q-ST-70-37C","ECSS - Current v1.0","5.2.2.1e","Requirement","ECSS-Q-ST-70-37_0680017",1,"Created","The location of the identification shall be as marked in Figure 5-1 and Figure 5-2."]
["ECSS-Q-ST-70-37C","ECSS - Current v1.0","5.2.3c","Requirement","ECSS-Q-ST-70-37_0680033",1,"Created","In case that the supplier uses an alternative test apparatus, the supplier shall design and use the apparatus in conformance with clause 5.2.4."]
["ECSS-Q-ST-70-37C","ECSS - Current v1.0","5.3.2b","Requirement","ECSS-Q-ST-70-37_0680048",1,"Created","The supplier shall examine the longitudinal microsections at a magnification of ×50 for evidence of stress-corrosion cracking."]
["ECSS-Q-ST-70-37C","ECSS - Current v1.0","5.3.3.3a","Requirement","ECSS-Q-ST-70-37_0680054",1,"Created","The supplier shall classify alloys or weldments as moderate if the following applies:\n    1. none of the three stress-corrosion specimens fails in the thirty-day test. Any failure is disregarded if the tensile strength of the unstressed control specimen removed from test at the time of failure of the stress-corrosion specimen does not exceed the stress-corrosion test stress; and\n    2. the average tensile strength of the two stress-corrosion specimens after the thirty-day test is not less than 90 % of that of the unstressed control specimens; and\n    3. metallographic examination at ×50 magnification shows evidence of stress-corrosion in any of the three stress-corrosion specimens."]
["ECSS-Q-ST-70-39C","ECSS - Current v1.0","6.1a","Requirement","ECSS-Q-ST-70-39_1280007",1,"Created","The manufacturer shall employ a qualified and certified welding supervisor as the responsible and competent authority for welding."]
["ECSS-Q-ST-70-39C","ECSS - Current v1.0","6.2.4a","Requirement","ECSS-Q-ST-70-39_1280017",1,"Created","Mechanised friction stir welding shall be performed by welding operators who have a valid certificate in accordance with ISO 25239-3:2011."]
["ECSS-Q-ST-70-39C","ECSS - Current v1.0","7.2f","Requirement","ECSS-Q-ST-70-39_1280035",1,"Created","The welding supervisor shall approve the re-acceptance of the welding equipment."]
["ECSS-Q-ST-70-39C","ECSS - Current v1.0","7.3.4e","Requirement","ECSS-Q-ST-70-39_1280050",1,"Created","For welding processes where degaussing is necessary, magnetic materials used for tooling shall be degaussed prior to welding."]
["ECSS-Q-ST-70-39C","ECSS - Current v1.0","8.1.4f","Requirement","ECSS-Q-ST-70-39_1280066",1,"Created","The pre-weld joint fit-up shall be under the responsibility of the design authority."]
["ECSS-Q-ST-70-39C","ECSS - Current v1.0","8.1.6c","Requirement","ECSS-Q-ST-70-39_1280078",1,"Created","All discolorations due to tack welding shall be removed prior to welding."]
["ECSS-Q-ST-70-39C","ECSS - Current v1.0","9.1.2d","Requirement","ECSS-Q-ST-70-39_1280085",1,"Created","During visual inspection, the following parameters shall be examined and documented:\n1.\tGeneral appearance and regularity,\n2.\tExcess weld metal,\n3.\tUndercuts and shrinkage groove,\n4.\tCraters, open pores or open cracks,\n5.\tRoot concavity,\n6.\tExcessive penetration,\n7.\tIncomplete penetration,\n8.\tBurn-through,\n9.\tWeld spatter,\n10.\tLack of fusion,\n11.\tWeld discolouration.","NOTE\tIt is possible that not all parameters are accessible."]
["ECSS-Q-ST-70-39C","ECSS - Current v1.0","9.2.1c","Requirement","ECSS-Q-ST-70-39_1280107",1,"Created","For verification, a part or a representative sample shall be cut for inspection."]
["ECSS-Q-ST-70-39C","ECSS - Current v1.0","9.2.4c","Requirement","ECSS-Q-ST-70-39_1280119",1,"Created","When one or more testing methods from the requirements 9.2.4a and 9.2.4b are specified, the engineering authority shall determine an approved standard or other requirements."]
["ECSS-Q-ST-70-39C","ECSS - Current v1.0","11.2c","Requirement","ECSS-Q-ST-70-39_1280140",1,"Created","In the case when at least one measurement on one sample is non-compliant with the requirements of clause 11, the verification shall be rejected."]
["ECSS-Q-ST-70-39C","ECSS - Current v1.0","11.5d","Requirement","ECSS-Q-ST-70-39_1280156",1,"Created","After removal of the defective part, the area shall be visually inspected."]
["ECSS-Q-ST-70-39C","ECSS - Current v1.0","11.6b","Requirement","ECSS-Q-ST-70-39_1280161",1,"Created","Tailoring of the WVTP for other tests shall be agreed with the supplier and customer."]
["ECSS-Q-ST-70-39C","ECSS - Current v1.0","13.1c","Requirement","ECSS-Q-ST-70-39_1280187",1,"Created","Modifications to welding parameters which fall outside the WPS shall lead to the issue of a new weld configuration."]
["ECSS-Q-ST-70-39C","ECSS - Current v1.0","13.2.3e","Requirement","ECSS-Q-ST-70-39_1280198",1,"Created","Malfunctions of the welding equipment shall be documented in the maintenance book."]
["ECSS-Q-ST-70-39C","ECSS - Current v1.0","13.2.4a","Requirement","ECSS-Q-ST-70-39_1280202",1,"Created","Inspection shall be performed on welds to demonstrate that the welds are compliant with the requirements of design and drawing for all weld classes in conformance with the requirements from the clauses 9.1 and 9.2. "]
["ECSS-Q-ST-70-39C","ECSS - Current v1.0","A.2.1<1.8>a","Requirement","ECSS-Q-ST-70-39_1280217",1,"Created","All non-destructive inspection techniques shall be identified in the WPS including the following acceptance criteria:\n1.\tRadiographic Inspection,\n2.\tUltrasonic inspection,\n3.\tX-Ray tomography (CT Scan)."]
["ECSS-Q-ST-70-39C","ECSS - Current v1.0","B.2.1<6>a","Requirement","ECSS-Q-ST-70-39_1280235",1,"Created","The number and type of weld samples to be tested shall be in conformance with the requirements from clause 10.1."]
["ECSS-Q-ST-70-40C","ECSS - Current v1.0","6.2c","Requirement","ECSS-Q-ST-70-40_1500010",1,"Created","Brazing operators shall be trained to demonstrate compliance to the BPS specified in the clause 8 with specific brazing test piece representative for production part."]
["ECSS-Q-ST-70-40C","ECSS - Current v1.0","9.1c","Requirement","ECSS-Q-ST-70-40_1500033",1,"Created","Any acceptance criteria for the NDT, not covered in clause 10.3, shall be agreed with the customer."]
["ECSS-Q-ST-70-40C","ECSS - Current v1.0","10.3a","Requirement","ECSS-Q-ST-70-40_1500040",1,"Created","The acceptance criteria for brazed joints, specified in Table 10-1, shall be applied."]
["ECSS-Q-ST-70-40C","ECSS - Current v1.0","11.5a","Requirement","ECSS-Q-ST-70-40_1500056",1,"Created","After the brazing operation has been completed, visual examination shall be performed by the brazing operator and the brazing inspector."]
["ECSS-Q-ST-70-40C","ECSS - Current v1.0","12.1c","Requirement","ECSS-Q-ST-70-40_1500071",1,"Created","Any brazing performed on flight hardware shall be performed under configuration control."]
["ECSS-Q-ST-70-40C","ECSS - Current v1.0","13.2.2d","Requirement","ECSS-Q-ST-70-40_1500087",1,"Created","Malfunctions of the brazing equipment shall be documented in the maintenance book."]
["ECSS-Q-ST-70-45C","ECSS - Current v1.0","5.2.1b","Requirement","ECSS-Q-ST-70-45_0690003",1,"Created","A minimum number of three tests shall be carried out for each set of material and test conditions."]
["ECSS-Q-ST-70-45C","ECSS - Current v1.0","5.4.1a","Requirement","ECSS-Q-ST-70-45_0690017",1,"Created","Test apparatus, specimens, test procedures, precision and bias shall be in conformance with ASTM E 466."]
["ECSS-Q-ST-70-45C","ECSS - Current v1.0","5.5.1d","Recommendation","ECSS-Q-ST-70-45_0690099",1,"Created","The film replica technique should be used to measure the length of short cracks. "]
["ECSS-Q-ST-70-45C","ECSS - Current v1.0","5.7.2d","Requirement","ECSS-Q-ST-70-45_0690044",1,"Created","Specimens shall be stressed after being brought into contact with the test environment, "]
["ECSS-Q-ST-70-45C","ECSS - Current v1.0","5.12.3a","Requirement","ECSS-Q-ST-70-45_0690062",1,"Created","The supplier shall provide documented evidence that only materials in conformance with the customer specifications are used in the test activity."]
["ECSS-Q-ST-70-45C","ECSS - Current v1.0","A.2.1<5>a","Requirement","ECSS-Q-ST-70-45_0690075",1,"Created","The requested test output shall be specified.\n    NOTE For example: Number of cycles, determined crack length and crack growth rates."]
["ECSS-Q-ST-70-45C","ECSS - Current v1.0","C.2.1<4>c","Requirement","ECSS-Q-ST-70-45_0690092",1,"Created","Estimated values of precision and bias for the test results shall be indicated."]
["ECSS-Q-ST-70-46C Rev. 1","ECSS - Current v1.0","4.1.4c","Requirement","ECSS-Q-ST-70-46_0700012",1,"Created","The manufacturer shall re-treat a batch which, tested as in 4.3.3, did not meet the mechanical property requirements, no more than twice (three times for Titanium alloys)."]
["ECSS-Q-ST-70-46C Rev. 1","ECSS - Current v1.0","4.1.6f","Requirement","ECSS-Q-ST-70-46_0700024",1,"Created","Unless otherwise specified in the customer specification document for threaded fasteners, a single right-hand thread shall be obtained. "]
["ECSS-Q-ST-70-46C Rev. 1","ECSS - Current v1.0","4.2.1a","Requirement","ECSS-Q-ST-70-46_0700039",1,"Created","Dimensional and metallurgical controls shall be carried out in accordance with the sampling procedures and acceptance criteria specified in 4.4.2.1."]
["ECSS-Q-ST-70-46C Rev. 1","ECSS - Current v1.0","4.2.4a","Requirement","ECSS-Q-ST-70-46_0700049",1,"Created","Fasteners shall be free from surface defects such as flaws and inclusions. "]
["ECSS-Q-ST-70-46C Rev. 1","ECSS - Current v1.0","4.3.1a","Requirement","ECSS-Q-ST-70-46_0700069",1,"Created","With the exception of the cases covered in 4.3.6, 4.3.7 and 4.3.8, mechanical testing for quality control purposes shall be performed at room temperature (22 ± 3) °C and laboratory air, (55 ± 10) % relative humidity. "]
["ECSS-Q-ST-70-46C Rev. 1","ECSS - Current v1.0","4.3.3.2e","Requirement","ECSS-Q-ST-70-46_0700084",1,"Created","The bearing face of the threaded part of the jig, Figure 4-6 (a), or of the nut, Figure 4-6 (b), shall be located at least four pitches of distance from the unthreaded portion of the shank. "]
["ECSS-Q-ST-70-46C Rev. 1","ECSS - Current v1.0","4.3.5.1a","Requirement","ECSS-Q-ST-70-46_0700098",1,"Created","Fatigue tests shall be carried out in accordance with ISO 3800. "]
["ECSS-Q-ST-70-46C Rev. 1","ECSS - Current v1.0","4.4.1a","Requirement","ECSS-Q-ST-70-46_0700114",1,"Created","The supplier (contractor or subcontractor) shall implement the quality assurance, inspection and quality control procedures specified herein before any supply activity. "]
["ECSS-Q-ST-70-46C Rev. 1","ECSS - Current v1.0","4.4.2.2c","Requirement","ECSS-Q-ST-70-46_0700121",1,"Created","The supplier shall issue a raw material certificate (RMC) specifying: material standard designation, heat treatment, form, manufacturer, batch number, batch chemical analysis, batch tensile test results (0,2 % proof stress, ultimate stress and elongation) and batch hardness value."]
["ECSS-Q-ST-70-46C Rev. 1","ECSS - Current v1.0","4.4.2.6f","Requirement","ECSS-Q-ST-70-46_0700144",1,"Created","Only qualified test laboratories shall carry out the tests."]
["ECSS-Q-ST-70-50C","ECSS - Current v1.0","5.1.1.3a","Requirement","ECSS-Q-ST-70-50_1140009",1,"Created","The following apparatus shall be used to perform a tape-lift analysis:\n    1. A low-tack, transparent adhesive tape with an adhesive force of less than 0,3 N/mm.\n    2. A tape that is free of particles, voids, bubbles, and other artefacts detrimental to the counting of particles.\n    3. A membrane filter with a pore size less than 1 µm, and a minimum diameter of 5 cm, which provides contrast with the particulate contaminants being analyzed.\n        NOTE The choice of the membrane filter depends upon the nature of the particles being analysed (e.g. a white membrane filter in the case of black particles and a black membrane filter in the case of white particles). Membrane filters can have grids when statistical counting is used.\n    4. A mask or gridded membrane filter to perform statistical counting on squares of pre-defined area.\n    5. Non-shedding and lint-free gloves.\n    6. Tweezers.\n    7. Scissors or a scalpel.\n    8. A clean container for the transport of the tape-lift sample to the measurement facility.","NOTE 1 A clean container is a container devoid of particulate that could influence the measurement of the tape-lift sample.\nNOTE 2 The container can be sealed to prevent external contamination from reaching the internal parts of the container."]
["ECSS-Q-ST-70-50C","ECSS - Current v1.0","5.1.2.2c","Requirement","ECSS-Q-ST-70-50_1140026",1,"Created","The location and orientation of the silicon wafers shall be representative of the items for which this monitoring method applies."]
["ECSS-Q-ST-70-50C","ECSS - Current v1.0","5.1.2.6h","Requirement","ECSS-Q-ST-70-50_1140041",1,"Created","After exposure, the container shall be closed in-situ."]
["ECSS-Q-ST-70-50C","ECSS - Current v1.0","5.1.3.2c","Requirement","ECSS-Q-ST-70-50_1140045",1,"Created","The rinsing or immersion liquid shall be the most effective, or a combination of the most effective, in removing contaminants.\n    ","NOTE 1 Typically, the rinsing or immersion liquid is the agent used for the last cleaning, if applicable.\nNOTE 2 When performed together with NVR analysis, the selection of the rinsing or immersion fluid is usually driven by the required NVR extraction effectiveness."]
["ECSS-Q-ST-70-50C","ECSS - Current v1.0","5.2.2.2a","Requirement","ECSS-Q-ST-70-50_1140068",1,"Created","Any counting of particulate contamination in a gas sample shall be performed in a cleanliness controlled area."]
["ECSS-Q-ST-70-50C","ECSS - Current v1.0","5.2.3.2a","Requirement","ECSS-Q-ST-70-50_1140076",1,"Created","When automatic particle counters are used they shall have demonstrated accuracy and repeatability, which correlates with microscope counting."]
["ECSS-Q-ST-70-50C","ECSS - Current v1.0","5.4.2c","Requirement","ECSS-Q-ST-70-50_1140093",1,"Created","A PFO measurement shall not be carried out if the background count on the sensor plate is greater than 20 mm2/m2."]
["ECSS-Q-ST-70-50C","ECSS - Current v1.0","5.4.7d","Recommendation","ECSS-Q-ST-70-50_1140215",1,"Created","An exposed sensor should not be moved from its measurement position. "]
["ECSS-Q-ST-70-50C","ECSS - Current v1.0","5.4.9g","Requirement","ECSS-Q-ST-70-50_1140119",1,"Created","If an adhesive tape in accordance with 5.4.9f is used to fix a PFO sensor, any contact with the sampling surface shall be avoided."]
["ECSS-Q-ST-70-50C","ECSS - Current v1.0","6.2n","Requirement","ECSS-Q-ST-70-50_1140132",1,"Created","In the case of a major nonconformance being discovered during a visual inspection the following shall be done: \n    1. the customer is immediately informed and the article left in the as-inspected condition;\n    2. a customer representative is invited to verify the results of the inspection."]
["ECSS-Q-ST-70-50C","ECSS - Current v1.0","6.3.1.1.3e","Recommendation","ECSS-Q-ST-70-50_1140219",1,"Created","Highly reflecting surfaces should be illuminated at grazing angle to observe particles with their shadow.\n    ","NOTE 1 The sensitivity of particles detection depends on the surface nature. Particles on a matte black surface are often easier to observe. For transparent or translucent items, side illumination can be used.\nNOTE 2 Fibre optic inspections can be conducted inside cleanrooms and other cleanliness controlled areas. In this case, the background light is reduced in order to increase the contrast."]
["ECSS-Q-ST-70-50C","ECSS - Current v1.0","7.3c","Requirement","ECSS-Q-ST-70-50_1140157",1,"Created","The supplier shall notify the customer of the nonconformance details."]
["ECSS-Q-ST-70-50C","ECSS - Current v1.0","C.2.1<2>a","Requirement","ECSS-Q-ST-70-50_1140169",1,"Created","The report shall contain the name, organization and address of the measurement authority."]
["ECSS-Q-ST-70-50C","ECSS - Current v1.0","C.2.1<5>a","Requirement","ECSS-Q-ST-70-50_1140172",1,"Created","The report shall contain the name and class of the facility where the measurements have been performed."]
["ECSS-Q-ST-70-50C","ECSS - Current v1.0","D.2.1<3>a","Requirement","ECSS-Q-ST-70-50_1140187",1,"Created","The report shall contain the name of the project for which the inspection has been carried out.\n    ","NOTE A project can be either related to the monitoring of spacecraft systems or controlled areas."]
["ECSS-Q-ST-70-53C","ECSS - Current v1.0","5.1.2.1a","Requirement","ECSS-Q-ST-70-53_0990006",1,"Created","The work area shall be at a cleanliness level that does not compromise the functionality of the test items or fulfil the imposed cleanliness requirements of the hardware."]
["ECSS-Q-ST-70-53C","ECSS - Current v1.0","5.2.2.1b","Requirement","ECSS-Q-ST-70-53_0990017",1,"Created","Assemblies shall be representative for its end-function and the flight hardware."]
["ECSS-Q-ST-70-53C","ECSS - Current v1.0","5.2.4f","Requirement","ECSS-Q-ST-70-53_0990037",1,"Created","Margin for number of sterilization cycles: The need of multiple sterilization shall be foreseen."]
["ECSS-Q-ST-70-53C","ECSS - Current v1.0","5.3.3d","Requirement","ECSS-Q-ST-70-53_0990047",1,"Created","The acceptance limits of degradation shall be allocated by the customer as part of the overall degradation budget including e.g. accumulation effects. "]
["ECSS-Q-ST-70-54C","ECSS - Current v1.0","5.1.2.1b","Requirement","ECSS-Q-ST-70-54_1360007",1,"Created","Cleanliness level of a work area shall be in compliance with cleanliness requirements of the hardware agreed with the customer."]
["ECSS-Q-ST-70-54C","ECSS - Current v1.0","5.2.3d","Requirement","ECSS-Q-ST-70-54_1360023",1,"Created","The nature of the representation, specified in 5.2.3b, of real contamination transfer mechanism shall be described.","NOTE \tTransfer mechanism considerations can include e.g. vacuum transfer vs. application from solution for molecular contamination or application from suspension vs. powder for particulate contamination.\n"]
["ECSS-Q-ST-70-54C","ECSS - Current v1.0","5.2.7.1b","Requirement","ECSS-Q-ST-70-54_1360036",1,"Created","An overall cleaning efficacy shall be determined comprising all process steps specified in clause 5.2.7.1a."]
["ECSS-Q-ST-70-54C","ECSS - Current v1.0","C.3.1b","Requirement","ECSS-Q-ST-70-54_1360052",1,"Created","Process records shall be made available in electronic form for incorporation in a database defined by the customer, and contain as a minimum the following: \n1.\tManufacturer. \n2.\tTraceable identification numbers for ultracleaned items. \n3.\tProcess description. \n4.\tConsumables name (trade name, grade, lot number). \n5.\tChemical nature. \n6.\tPurity where gases/liquids are used (particulate; molecular; biological\n7.\tIntended application. \n8.\tProcess method, apparatus, facility, date. \n9.\tNominal/measured analysis parameters \n10.\tPre- and post-ultracleaning storage parameters. \n11.\tPre‐ and post-ultracleaning values of test parameters specified in requirements of clause C.3.1 including date of tests. \n12.\tOccurrence of NCRs. \n13.\tCopy of the final inspection documentation (attached docs in new tab). \n14.\tCopy of process reports (attached docs in new tab).","NOTE \tFor the item 2: batch number, serial number.\nFor the item 10: Traceable identification numbers need to be included on the packaging.\n"]
["ECSS-Q-ST-70-55C","ECSS - Current v1.0","5.1.3.1d","Requirement","ECSS-Q-ST-70-55_1030013",1,"Created","Air sampling shall be applied for continuous clean room monitoring."]
["ECSS-Q-ST-70-55C","ECSS - Current v1.0","5.4.3a","Requirement","ECSS-Q-ST-70-55_1030028",1,"Created","Acceptance criteria shall be defined (beforehand) in common agreement between the test authority and the customer."]
["ECSS-Q-ST-70-56C","ECSS - Current v1.0","5.1e","Requirement","ECSS-Q-ST-70-56_1230005",1,"Created","The supplier shall provide a hydrogen peroxide bioburden reduction report in conformance with the DRD in Annex C."]
["ECSS-Q-ST-70-56C","ECSS - Current v1.0","5.3.1.2a","Requirement","ECSS-Q-ST-70-56_1230022",1,"Created","Procedure for controlled vacuum environment shall be used for a 2 to 6 order of magnitude bioburden reduction.","NOTE A 2 to 6 order of magnitude reduction is achieved by multiplying the respective D-value in requirement 5.3.1.2c by a factor of 2 to 6, respectively."]
["ECSS-Q-ST-70-56C","ECSS - Current v1.0","5.4f","Requirement","ECSS-Q-ST-70-56_1230036",1,"Created","Instrumentation used to monitor the process parameters shall be calibrated. "]
["ECSS-Q-ST-70-57C","ECSS - Current v1.0","5.2.3a","Requirement","ECSS-Q-ST-70-57_1240009",1,"Created","The packaging, if present at the time of bioburden reduction, shall be compatible with the bioburden reduction process.  ","NOTE Pay attention to pressure changes during the bioburden reduction process."]
["ECSS-Q-ST-70-57C","ECSS - Current v1.0","5.4d","Requirement","ECSS-Q-ST-70-57_1240028",1,"Created","Support structures for the product shall be designed and used to allow uniform heating. ","NOTE Support structures are usually racks and holders."]
["ECSS-Q-ST-70-58C","ECSS - Current v1.0","5.1.1.1a","Requirement","ECSS-Q-ST-70-58_1040001",1,"Created","A formal system of bioburden control shall be established, formally approved, implemented, documented in conformance with Annex A, and maintained within bioburden controlled cleanrooms and associated environments.\n    NOTE The formal system assesses and controls factors that can affect the microbiological quality of the controlled environment."]
["ECSS-Q-ST-70-58C","ECSS - Current v1.0","5.2.3.1d","Requirement","ECSS-Q-ST-70-58_1040017",1,"Created","Material flow shall be optimized to prevent unnecessary activities that could increase the potential for introducing contaminants."]
["ECSS-Q-ST-70-58C","ECSS - Current v1.0","5.2.3.3d","Requirement","ECSS-Q-ST-70-58_1040028",1,"Created","Preparatory activities (e.g. adhesive mixing) shall be conducted in dedicated external or peripheral areas, with due regard to requirements for spacecraft microbial contamination requirements."]
["ECSS-Q-ST-70-58C","ECSS - Current v1.0","5.2.5.6b","Requirement","ECSS-Q-ST-70-58_1040047",1,"Created","To assist in interpretation, results shall be reviewed over extended periods to determine trends. Bioburden and biodiversity trend analysis shall be provided."]
["ECSS-Q-ST-70-58C","ECSS - Current v1.0","A.2.1a","Requirement","ECSS-Q-ST-70-58_1040063",1,"Created","The bioburden control formal system description shall include:\n    1. Limits established to ensure control, including alert and action level as established in conformance with requirement 5.1.2.1a.\n    2. Description of the monitoring scheme and schedule established.\n    3. Description of the validation procedures established in conformance with clause 5.1.1.2 to verify that the formal system is working properly.\n    4. Corrective actions established in conformance with requirement 5.1.2.2b.2 to be taken when a monitoring result indicates that a particular factor of the process is not under control.\n    5. Risk assessment for bioburden control. \n        NOTE For example: Process FMECA.\n    6. Description of the training procedures and access constraints established in conformance with clause 5.2.6.\n    7. Documentation to be established and maintained.\n    8. Process implementation documentation.\n        NOTE For example: Logbooks.\n    9. Periodic reviews/audits to be performed.\n    10. Maintenance status of equipment.\n    11. Cleanroom cleaning programme.\n    12. A training programme.\n    13. Description of the sampling plan, including at least:\n        (a) The cleanliness level of the cleanroom to be applied and the appropriate degree of bioburden control for the activity being conducted.\n        (b) The sampling location(s) identified in conformance with clause 5.2.5.3, including the location of the primary “risk zone”; i.e.; the work area immediately adjacent to any contamination-critical hardware and the work activities/personnel associated with this location.\n        (c) The minimum number of samples to be taken in order to ensure representative results.\n            NOTE This number is dependant on the sample size/ volume. For small sample sizes, representativeness of the results cannot be guaranteed if this number is not significantly increased.\n        (d) Frequency of initial monitoring sampling, established in conformance with requirement 5.2.5.2b.1.\n        (e) Frequency of normal routine sampling, established in conformance with requirement 5.2.5.2b.2.\n        (f) Frequency of sampling for specific cases, established in conformance with requirement 5.2.5.2b.3, including at least the following cases:\n\t- Suspected contamination events.\n\t- Action levels are exceeded.\n\t- Alert levels are exceeded (consecutively).\n\t- A change in the biodiversity.\n\t- After prolonged shut-down of activities.\n\t- After any significant maintenance work has been undertaken on the cleanroom.\n\tNOTE 1\tFor example: Maintenance on ventilation system, changes to furnishings or fittings, introduction of significant quantities of new hardware or equipment.\n\t\t- After changes to the process that affect the cleanroom environment.\n\t\t- After recording of unusual results.\n\t\t- After non-routine changes to the cleaning or disinfection procedures.\n\t\t- After unplanned incidents that could contribute to contamination.\n\t\t- After any incidence of non-conformance to cleanroom operational specifications.\n\tNOTE 2\tFor example: Breaches of personnel dress/conduct code; out of specification airborne particulate levels, out of specification temperature or humidity levels, exceeding maximum no. of personnel, or introduction of non-sterile items or hardware."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","5.3.2c","Requirement","ECSS-Q-ST-70-60_1390005",1,"Unchanged","Flexible PCB for harness shall be qualified and procured as per ECSS-Q-ST-70-60 and designed as per ECSS-Q-ST-70-12, except for the cases from requirements 5.3.2d and 5.3.2e."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","5.6a","Requirement","ECSS-Q-ST-70-60_1390021",1,"Unchanged","The quality assurance requirements specified in ECSS-Q-ST-20 shall apply."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","5.7f","Requirement","ECSS-Q-ST-70-60_1390029",1,"Unchanged","Initial qualification of a PCB manufacturer or PCB technology in conformance with requirement 7.2b shall be performed on at least 3 PCBs and the coupons in conformance with Figure 7‑1."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","5.9m","Requirement","ECSS-Q-ST-70-60_1390048",1,"Unchanged","The final conclusion of the audit process shall be provided in the final audit report or minutes of meeting."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","5.13a","Requirement","ECSS-Q-ST-70-60_1390060",1,"Unchanged","Process changes shall include process parameters, chemistry, material, equipment, process flow and inspections."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","5.16a","Requirement","ECSS-Q-ST-70-60_1390072",1,"Unchanged","In case nonconformances are observed during qualification renewal, the PCB manufacturer shall perform the following:\n1.\tInvestigate root cause, implement corrective actions on associated processes and materials, demonstrate repeatability.\n2.\tInvestigate why nonconformance was not detected by outgoing inspection and perform training.\n3.\tVerify how the nonconformance affects the running orders and inform customers.\n4.\tEvaluate a new PCB and provide test report in conformance with 5.15a.6.\n5.\tHave a new PCB sample evaluated by a third-party lab and provide test report.\n6.\tUpon approval from the qualification authority, submit a new sample for qualification renewal.","NOTE \tThird-party evaluation from requirement 5.16a.5 is also specified in requirement 5.8c.\n"]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","6.2.6b","Requirement","ECSS-Q-ST-70-60_1390082",1,"Unchanged","The PCB manufacturer shall perform the MRR in conformance with the requirements 5.2h to 5.2k from ECSS-Q-ST-70-12."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","6.3c","Requirement","ECSS-Q-ST-70-60_1390087",1,"Unchanged","Visual standards that specify the quality characteristics shall be available to each inspector.","NOTE \tVisual standards for final inspection can consist of photos or drawings of microsections, which are given in clause 10.\n"]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","6.5f","Permission","ECSS-Q-ST-70-60_1390740",1,"Unchanged","For requirement 6.5c and 6.5d, newer revisions of the referenced IPC-4101E standard may be used in case\n1.\traw materials can only be procured in conformance to those newer revisions, and\n2.\tit is in conformance with Appendix A from IPC-4101E.","NOTE \tThe text from Appendix A of IPC-4101E is included in Annex I.\n"]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","6.6d","Permission","ECSS-Q-ST-70-60_1390741",1,"Unchanged","Electrolytic hard gold plating may contain 0,3 % cobalt."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","6.7.2g","Recommendation","ECSS-Q-ST-70-60_1390745",1,"Unchanged","Motor parts for any vacuum hovering should be located outside of the room for lay-up.","NOTE \tA vacuum hose can be brought into the room through the wall.\n"]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","6.8m","Requirement","ECSS-Q-ST-70-60_1390138",1,"Unchanged","In case some PCBs within the batch are delivered later, the PCB manufacturer shall at least issue a new declaration of conformance from the CoC in conformance with B.2.1.2.","NOTE \tSpare PCBs can be stored by the PCB manufacturer and delivered to the customer at a later time if re-ordered. In case the lab reports from the original delivered CoC covers the spare ones, a new lab report does not need to be issued. The new declaration of conformance is sufficient to ensure traceability.\n"]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","6.9b","Requirement","ECSS-Q-ST-70-60_1390860",1,"Created","For operator dependant processes, the following shall be specified in the work instructions:\n1.\toperator training;\n2.\tverification;\n3.\tthe method to obtain repeatability;\n4.\tthe number of capable operators, including back-up.","NOTE \tExample of operator dependant processes are SnPb hot oil reflow and manual planarization.\n"]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","6.11j","Requirement","ECSS-Q-ST-70-60_1390157",1,"Unchanged","If desiccant is used, means for indication of moisture content shall be provided."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","6.12d","Permission","ECSS-Q-ST-70-60_1390756",1,"Informative Change","Spare coupons may be stored in an uncontrolled environment.","NOTE \tThis is acceptable because it is considered worst-case. However, it is good practice to store coupons together with PCBs as this ensures representativity in case any test, such as relife testing, is undertaken.\n"]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","6.14p","Requirement","ECSS-Q-ST-70-60_1390179",1,"Unchanged","In case of non-compliance of a technology parameter to the PID, a delta qualification plan shall be submitted to the customer in conformance with requirement 6.14q.","NOTE \tClause 7.6 specifies the requirements of tests, inspections and specimen for delta qualification.\n"]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","7.2b","Requirement","ECSS-Q-ST-70-60_1390186",1,"Unchanged","For initial qualification of a PCB manufacturer or a PCB technology, all tests of groups 1, 2, 3, 4, and 5 shall be performed on PCB and coupon."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","7.2h","Requirement","ECSS-Q-ST-70-60_1390192",1,"Unchanged","For qualification of HDI technology, the following tests shall be performed on PCB and coupons:\n1.\tGroup 1, 3, 4, 5: all;\n2.\tGroup 2: peel strength."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","7.6c","Requirement","ECSS-Q-ST-70-60_1390201",1,"Unchanged","The delta qualification shall be in conformance with clause 5.13 and documented in the process change notice."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","7.7.2q","Requirement","ECSS-Q-ST-70-60_1390872",1,"Created","For project qualification of HDI, a CAF risk assessment shall be performed.","NOTE \tThe CAF risk assessment includes a comparison of insulation distances to the CAF test patterns of Table 9‑2, Table 9‑3 and Table 9‑4 of clause 9.7.3. The risk of CAF is considered to be low in case the insulation is above the one specified for the ECSS pattern from these tables. CAF testing is done for generic qualification but usually not for project qualification. Nevertheless, for project qualification the risk of CAF is assessed.\n"]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","8.2.2e","Requirement","ECSS-Q-ST-70-60_1390227",1,"Unchanged","Coupon A/B shall include at least 4 holes per drilling sequence."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","8.2.4a","Requirement","ECSS-Q-ST-70-60_1390245",1,"Unchanged","All coupons shall be evaluated by visual inspection, in accordance with requirements from clause 9.3.1 and 9.3.2."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","8.2.4j","Permission","ECSS-Q-ST-70-60_1390771",1,"Unchanged","Solderability test need not to be performed for procurement in case all the following conditions are met:\n1.\tThe surface finish is hot oil reflowed SnPb;\n2.\tThe thickness of the SnPb as specified on the CoC of the panel is in conformance with the requirements of Table 10‑12;\n3.\tThe PID does not specify that solderability testing is mandatory for procurement.","NOTE \tIn case the thickness of SnPb is not in conformance with the requirements of Table 10‑12 as determined during qualification (renewal), the PID can specify that solderability test is performed for all procurement. This is usually the case upon request by the qualification authority.\n"]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","8.4a","Requirement","ECSS-Q-ST-70-60_1390260",1,"Unchanged","The procurement authority shall perform incoming inspection as follows:\n1.\tVisual inspection on all PCBs, in conformance with the clause 9.3,\n2.\tMicroscopic inspection on microsections, in conformance with the clause 10, by one of the following institutes:\n(a)\tprocurement authority;\n(b)\texternal third-party lab;\n(c)\tassembly house;\n(d)\tPCB manufacturer using another inspector than the one for outgoing inspection.\n3.\tVerification of the CoC and its lab reports, in conformance with the Annex B,\n4.\tVerification of quantity,\n5.\tVerification of integrity of packaging.","NOTE\t1\tThe PCB manufacturer provides microsections used for the CoC and customer coupons. Both can be used for the incoming inspection. To avoid deterioration of the surface quality of microsections, it is preferred to perform incoming inspection as soon as possible after delivery. \nNOTE\t2\tMicrosection inspection for qualitative aspects is important and detection can be operator dependent. Therefore this requirement specifies to perform an additional verification.\n"]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.2.2b","Permission","ECSS-Q-ST-70-60_1390778",1,"Informative Change","In case the PCB technology or the test criteria are affected by humidity, the bake-out may be tailored to improve its efficiency.","NOTE \tImproving efficiency of the bake-out can be established by a longer duration, vacuum or dry environment or a stepped baking profile. This can be necessary for thick PCBs, a high number of copper plane layers, flex laminate layers or samples stored in non-controlled environment. Tests that can be significantly affected by humidity include thermal excursions and high resistance electrical test. Baking in vacuum or dry nitrogen purge is good practice as this reduces oxidation of surface finish, as well as it improves dehumidification.\n"]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.2.4h","Requirement","ECSS-Q-ST-70-60_1390283",1,"Unchanged","After removing the specimens from the steam generator machine, they shall be dried."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.3.3.2c","Requirement","ECSS-Q-ST-70-60_1390299",1,"Unchanged","The two corners of the measured edge shall be in contact with the horizontal surface."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.3.3.3f","Requirement","ECSS-Q-ST-70-60_1390311",1,"Unchanged","The twist shall be expressed in percentage terms."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.3.7.2d","Requirement","ECSS-Q-ST-70-60_1390324",1,"Unchanged","The sustain time shall be ≥ 5 ms.","NOTE \tIt is common that the sustain time is more than 5 ms to allow the voltage ramp up, especially in case large ground layers are present.\n"]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.4.2c","Requirement","ECSS-Q-ST-70-60_1390344",1,"Unchanged","The detached end of the conductor shall be gripped over its whole width."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.4.2i","Requirement","ECSS-Q-ST-70-60_1390350",1,"Unchanged","Peel strength of copper foil on laminate or prepreg shall be in conformance with the specification from the datasheet from the raw material manufacturer and from IPC-4101E."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.4.4a","Requirement","ECSS-Q-ST-70-60_1390363",1,"Unchanged","Bending test shall be performed only for rigid­flex PCBs.","NOTE \tThe objective of the bending test is to determine the adhesion of flex layers and the rigid-to-flex interface.\n"]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.4.6c","Permission","ECSS-Q-ST-70-60_1390793",1,"Unchanged","Another method resulting in the same degree of precision may be used."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.4.11.2c","Requirement","ECSS-Q-ST-70-60_1390387",1,"Unchanged","The coupon shall include minimum three PTH."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.4.11.4d","Requirement","ECSS-Q-ST-70-60_1390395",1,"Unchanged","The solderability test shall be performed in not less than one minute, and not more than five minutes after application of flux."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.5.2.3f","Recommendation","ECSS-Q-ST-70-60_1390804",1,"Unchanged","Fluorescent dye should be used for potting of the rigid-to-flex interface."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.5.3c","Requirement","ECSS-Q-ST-70-60_1390417",1,"Unchanged","The solder bath float shall be performed to one side of the sample by floating it for 10 s in a solder bath maintained at 288 °C."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.5.4.3d","Requirement","ECSS-Q-ST-70-60_1390429",1,"Unchanged","The wire and PTH shall be fluxed."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.5.5.2.3b","Requirement","ECSS-Q-ST-70-60_1390445",1,"Unchanged","IST shall be performed until 5 % resistance increase is reached or until a maximum of 1500 cycles.","NOTE\t1\tAcceptance criteria are as per clause 9.5.5.4.3. Testing to EOL is performed to provide information about the limits of the robustness.\nNOTE\t2\tAt least 3 IST coupons are used for initial qualification and at least 1 IST coupon is used for delta qualification and qualification renewal, in conformance with clause 5.7.\nNOTE\t3\tFor qualification it is not practical to test microvias after having tested other via types on that coupon to EOL.\n"]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.5.5.4.1f","Requirement","ECSS-Q-ST-70-60_1390450",1,"Unchanged","In uncontrolled conditions, IST coupons shall be submitted to IST testing within 12 hours after baking. "]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.5.5.4.2o","Recommendation","ECSS-Q-ST-70-60_1390889",1,"Created","The T0 reference resistance should be taken prior to preconditioning.","NOTE\t1\tThe T0 reference resistance is the initial resistance of the daisy-chain. The relative resistance change as a function of thermal cycles is determined versus this initial resistance.\nNOTE\t2\tFor 9.5.5.4.2f and 9.5.5.4.2g it is good practice to set the test for a higher resistance threshold than 4% or 5% (such as 10%). This prevents that early failure is triggered in case of high noise or environmental drift. The 4% or 5% acceptance criterion is applied on the data in retrospect to determine the cycles to failure.\n"]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.5.5.4.4e","Requirement","ECSS-Q-ST-70-60_1390891",1,"Created","IST test report shall include results from all tested coupons."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.6.3d","Permission","ECSS-Q-ST-70-60_1390832",1,"Unchanged","The procurement authority may define in the PCB definition dossier specific AC insulation resistance testing on coupons or PCB.","NOTE\t1\tThe majority of applications for space are in DC. It is important to note that DC/DC converters can have some AC sections. \nNOTE\t2\tPeak transient voltages in AC or DC is covered by requirement 13.8.2b. from ECSS-Q-ST-70-12.\nNOTE\t3\tThe failure mechanisms of primary concern in PCB materials are of slow time constant, such as ECM. In this case, DC is deemed worse-case than AC.\n"]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.7.2.2b","Requirement","ECSS-Q-ST-70-60_1390489",1,"Unchanged","The sensitivity S of the pattern shall be calculated using the following formula:\n \nWhere:\nL: length of track\nN: number of gaps between tracks\nD: insulation distance","NOTE\t1\tThe unit of the sensitivity is “number of squares”. This is a dimensionless value representing the interface area, that is proportional to the sum of the length of parallel tracks and inverse proportional to the insulation distance. \nNOTE\t2\tThe pattern in Figure 9‑10 uses 150 μm track width and 150 μm insulation distance over an area of 30 mm length and width. This results in 30/(0,15+0,15)=100 gaps N. Therefore the sensitivity S= 30 x 100 / 0,15 = 20000 number of squares.\n"]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.7.2.4b","Requirement","ECSS-Q-ST-70-60_1390504",1,"Unchanged","Breach of insulation that is demonstrated by microsectioning to be caused by lack of cleanliness shall be evaluated during the audit in conformance with clause 6.7.","NOTE \tThe test can only be treated as nonconform in case contamination is demonstrated to be the cause of breach of insulation. The electrical response only, is not sufficient. Hence, it is not necessary that the environmental parameters are fully representative of operational use. The test only serves to find contamination, if any. Test results of contamination causing breach of insulation are evaluated together with the cleanliness of processes during the audit. \n"]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.7.3.4a","Requirement","ECSS-Q-ST-70-60_1390520",1,"Unchanged","A sudden drop in resistance by an order of magnitude shall be breach of insulation.","NOTE\t1\tBreach of insulation can occur intermittent or continuous. Examples of stable insulation and breach of insulation are shown in Figure 9‑12. Breach of insulation during the first ambient phase or the pre-conditioning phase are considered early failures for which CAF cannot be the failure mechanism.\nNOTE\t2\tAn insulation threshold below 0,1 GΩ is typically considered a breach of insulation. However, such absolute threshold depends on the sensitivity of the sample design.\n"]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","9.8.2e","Permission","ECSS-Q-ST-70-60_1390838",1,"Unchanged","In case of project qualification, the reflow simulation and rework simulation may be tailored to be representative of the assembly processes."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","10.2d","Requirement","ECSS-Q-ST-70-60_1390543",2,"Normative Change","For the technological feature copper plating thickness, the acceptance criteria, the inspection samples and the measurement method shall be in conformance with Table 10‑4."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","10.2p","Requirement","ECSS-Q-ST-70-60_1390555",1,"Unchanged","For the technological feature dimensional verification of the rigid-flex interface the acceptance criteria, the inspection samples and the measurement method shall be in conformance with Table 10‑16."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","10.3q","Requirement","ECSS-Q-ST-70-60_1390588",2,"Normative Change","For the technological feature inhomogeneity in dielectric, the acceptance criteria, the inspection samples and the measurement method shall be in conformance with Table 10‑34."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","10.4h","Requirement","ECSS-Q-ST-70-60_1390621",2,"Normative Change","For the technological feature haloing the acceptance criteria, the inspection samples and the measurement method shall be in conformance with Table 10‑49."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","10.4l","Requirement","ECSS-Q-ST-70-60_1390625",2,"Normative Change","For the technological feature rigid-flex interface fibre protrusion the acceptance criteria, the inspection samples and the measurement method shall be in conformance with Table 10‑53."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","10.6.2d","Requirement","ECSS-Q-ST-70-60_1390678",1,"Unchanged","The height of the pad lift shall include adhesive separation between pad and resin as well as cracks or voids due to cohesive separation inside the dielectric."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","10.6.3b","Requirement","ECSS-Q-ST-70-60_1390686",1,"Unchanged","The plating in microvias shall be evaluated in conformance with Table 10‑11 in high density and low density footprint.","NOTE \tMicrovias in low density footprint are included in coupons from set 1 and set 2. Microvias in high density footprint are included in the IST coupon, which can be microsectioned after IST test. \n"]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","B.2.1.5c","Requirement","ECSS-Q-ST-70-60_1390704",1,"Unchanged","The acceptance criteria for microsection for qualitative aspects shall cover all microsections of coupons in the batch by providing a pass/fail evaluation.","NOTE \tInspection and evaluation of requirements is performed on all microsections of coupons in the batch, whereas the reporting provides a summary.\n"]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","D.2.1.2a","Requirement","ECSS-Q-ST-70-60_1390714",1,"Unchanged","Specific parts of the PID shall include:\n1.\tManufacturing and quality control flow charts with reference to applicable work instructions;\n2.\tList of base materials and chemicals with brand name, type, and supplier;\n3.\tProduction flow­chart, including in-process inspections and reference to work instructions in conformance with D.2.1.1a8;\n4.\tDescription of qualified domain in conformance with the items specified in requirement G.2.1b;\n5.\tDescription of any review items that have been specifically qualified, as specified in clause <7>a of Annex A of ECSS-Q-ST-70-12;\n6.\tSubcontracted processes."]
["ECSS-Q-ST-70-60C Rev.1","ECSS - Current v1.0","E.2.1b","Requirement","ECSS-Q-ST-70-60_1390718",1,"Unchanged","The PCN shall contain the following:\n1.\tCategorisation of process change as “major” or “minor”;\n2.\tJustification for categorisation;\n3.\tDescription of old and new process;\n4.\tJustification for change;\n5.\tReference to work instruction in PID;\n6.\tIn case of minor process change, results of verification tests and inspections;\n7.\tRequest for major process change including qualification test plan;\n8.\tRequest for approval of implementation of the major process change including qualification test report;\n9.\tOptional approval from procurement authority for major process change in conformance with requirement 5.13h."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","5.2b","Requirement","ECSS-Q-ST-70-61_1510009",1,"Created","The soldering area shall have as minimum a cleanliness level of ISO Class 8.2 in accordance with ISO 14644-1 (2015).","NOTE\tParticle concentrations for ISO Class 8.2 are not mentioned in the ISO Standard and can only be calculated with the formula in Annex E of ISO 14644-1 (2015). See Table 5-1.\n"]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","5.4.4e","Requirement","ECSS-Q-ST-70-61_1510030",1,"Created","The normal value of the resistance between the tip of the soldering system and the ground of the ESD protected area shall not exceed 5 Ω.","NOTE\tThe measurement is generally performed at soldering temperature.\n"]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","5.4.5c","Requirement","ECSS-Q-ST-70-61_1510040",1,"Created","If the packaging is not ESD safe, it shall be labelled accordingly.","NOTE\tThe objective of ESD protection is to prevent ESD to the item contained within, to allow for dissipation of charge, and to prevent charging of the ESD item by an external electrostatic field.\n"]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","5.5.3c","Requirement","ECSS-Q-ST-70-61_1510062",1,"Created","No twisting action shall occur during the cutting operation."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","5.5.6.2a","Requirement","ECSS-Q-ST-70-61_1510071",1,"Created","Mechanical strippers shall be of the following types:\n1.\tAutomatic power-driven strippers with precision, factory-set, cutting, and stripping dies and wire guards, or\n2.\tPrecision-type hand strippers with accurately machined and factory-pre-set cutting heads.","NOTE\tFigure 5-2 shows an example of acceptable mechanical strippers.\n"]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","5.5.8.2a","Requirement","ECSS-Q-ST-70-61_1510086",1,"Created","Holding tools used as soldering aids shall not be wetted by the solder during the assembly."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","5.5.9d","Requirement","ECSS-Q-ST-70-61_1510100",1,"Created","The oven shall be equipped with an independent automatic shutdown system to protect from overheating."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","5.5.14.2b","Requirement","ECSS-Q-ST-70-61_1510116",1,"Created","Reflow process parameters for local hot gas reflow machines shall be controlled and documented according to clause 5.5.14.5."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","6.1c","Requirement","ECSS-Q-ST-70-61_1510135",1,"Created","Electronic components, mechanical components, printed boards, selected for assembly shall be compatible with all materials and processes, temperature ratings, used to assemble the product."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","6.2.3c","Requirement","ECSS-Q-ST-70-61_1510147",1,"Created","Purchased premixed paste shall not be used if the use-by date or shelf life recommended by the manufacturer of the paste or paste constituents has expired."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","6.4j","Requirement","ECSS-Q-ST-70-61_1510163",1,"Created","Solvents shall be selected such that they dry completely."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","6.7c","Requirement","ECSS-Q-ST-70-61_1510174",1,"Created","Wires shall be stripped of their insulation in accordance with clause 7.5.1."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","6.10.1i","Requirement","ECSS-Q-ST-70-61_1510193",1,"Created","When components initially designed for insertion-mount application are used for surface mounting, the assembly shall not damage neither the component, its leads nor the substrate to which it is assembled."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","7.2.2a","Requirement","ECSS-Q-ST-70-61_1510209",1,"Created","Bare PCBs shall be stored in accordance with clause 6.12 of ECSS-Q-ST-70-60."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","7.5.1d","Requirement","ECSS-Q-ST-70-61_1510222",1,"Created","Insulation shall not be melted into the wire strands."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","7.5.5b","Requirement","ECSS-Q-ST-70-61_1510239",1,"Created","Restoration of the lay shall be done without contaminating the conductor."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","7.6.2g","Requirement","ECSS-Q-ST-70-61_1510261",1,"Created","The cross-sectional area of terminations shall not be reduced by dissolution into the solder bath below the minimum values of specification."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","7.6.3.3a","Requirement","ECSS-Q-ST-70-61_1510270",1,"Created","For degolding, solder shall be melted inside the solder cup."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","7.6.4.2f","Requirement","ECSS-Q-ST-70-61_1510283",1,"Created","Solder shall not flow under insulation.","NOTE\tIt is good practice to use antiwicking tools to prevent the solder flow.\n"]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","7.7g","Requirement","ECSS-Q-ST-70-61_1510299",1,"Created","Solder tips with cracked platings shall be removed from the soldering area."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","8.2.5a","Requirement","ECSS-Q-ST-70-61_1510318",1,"Created","Stress relief shall be incorporated into leads to be soldered and conductors as well as interfacial connections except for requirement 8.2.5b and requirements from clause 8.2.6.","NOTE\t1\tStress relief provides freedom of movement for component leads or conductors between points of constraint.\nNOTE\t2\tStresses can arise between points of constraint due to mechanical loading or temperature variations.\nNOTE\t3\tExamples of stress relief methods are shown in Figure 8-3 and Figure 8-8.\n"]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","8.2.6d","Requirement","ECSS-Q-ST-70-61_1510331",1,"Created","Components sensitive to vibrations and shock tests shall not be assembled as described in requirement 8.2.6a.","NOTE\tExamples of such sensitive components are: relays, oscillators, crystals. ECSS-E-HB-32-25A is providing a list of components known as sensitive to vibration and shock.\n"]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","8.2.8.3a","Requirement","ECSS-Q-ST-70-61_1510350",1,"Created","Non-bendable leads shall not be clinched."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","8.2.9a","Requirement","ECSS-Q-ST-70-61_1510362",1,"Created","PCB connectors shall be supplied with either:\n1.\tpre-formed leads supporting stress relief bends, or\n2.\tstraight, resin moulded connector."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","8.3.1b","Requirement","ECSS-Q-ST-70-61_1510383",1,"Created","Surface mounting of components shall be parallel to the board surface."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","9.1a","Requirement","ECSS-Q-ST-70-61_1510400",1,"Created","A conductor shall be wrapped onto a terminal in the same direction as the final curvature of the wire."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","9.3c","Requirement","ECSS-Q-ST-70-61_1510413",1,"Created","For side route connections to turret terminals, all conductors shall be confined to the guide slots."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","9.4.3c","Requirement","ECSS-Q-ST-70-61_1510430",1,"Created","When more than one conductor is connected to a terminal, the direction of bend of each additional conductor shall alternate, see Figure 9-3(b) and (d) with the contour of each wire visible."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","9.4.4d","Requirement","ECSS-Q-ST-70-61_1510438",1,"Created","Conductors which do not fill the gap, as shown in Figure 9-4, shall be either:\n1.\taccompanied by a tinned filler solid or stranded wire, such that the combined diameters fill the gap, or\n2.\tbent double, provided that the combined diameters fill the gap."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","9.7g","Requirement","ECSS-Q-ST-70-61_1510463",1,"Created","The solder joints to cup terminals shall meet the solder fillet requirements as illustrated in Figure E-6."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","9.8l","Requirement","ECSS-Q-ST-70-61_1510477",1,"Created","The sleeving shall be shrunk using heated gas or radiant energy."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","9.9.3c","Requirement","ECSS-Q-ST-70-61_1510494",1,"Created","The insulation jacket shall be scored and removed using a sharp cutting tool.","NOTE\tExample: a scalpel.\n"]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","9.9.4k","Requirement","ECSS-Q-ST-70-61_1510509",1,"Created","Insulation overlap shall not be greater than the diameter of the largest conductor of the interconnection as illustrated in Figure E-9."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","9.9.4p","Requirement","ECSS-Q-ST-70-61_1510514",1,"Created","The minimum solder connection shall be 2 mm when binding wire is used."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","10.2.2a","Requirement","ECSS-Q-ST-70-61_1510544",1,"Created","There shall be no relative motion between conductors and terminals during soldering or solder solidification."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","10.2.2g","Requirement","ECSS-Q-ST-70-61_1510552",1,"Created","For assembly sensitive components, the maximum tilt shall be defined based on the assembly verification results and not exceed 10°"]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","10.2.5l","Requirement","ECSS-Q-ST-70-61_1510576",1,"Created","The heated soldering iron tip shall be applied to the PCB pad."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","10.2.6.2b","Requirement","ECSS-Q-ST-70-61_1510587",1,"Created","The fillet shall follow the contour of the cup opening."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","10.3.1c","Permission","ECSS-Q-ST-70-61_1510591",1,"Created","Soldering of components into plated through holes may be performed by pin-in-paste method, provided the following conditions are met: \n1.\tSolder fillets are compliant to clause 10.3.3.\n2.\tSuccessful verification programme according to clause 13 has been carried out, where the repeatability of the pin-in-paste process is also demonstrated. ","NOTE\t1\tIt is good practice to define process design guidelines for solder volume as a function of both pin geometry and volume of plated through hole, so that proper filling of the hole can be achieved. \nNOTE\t2\tIf solder paste volume is not sufficient, solder preforms can also be added.\n"]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","10.4.1a","Requirement","ECSS-Q-ST-70-61_1510607",1,"Created","The footprint shall be such that \n1.\tthe entire termination of the component lies on its associated footprint on the finished board.\n2.\tthe requirements per component type from clause 10.4.2 to 10.4.14 can be fulfilled.\n3.\tthe pad size permits the assembly of hand soldering, when applicable, without touching the component.","NOTE\t1 \tto item 3: It is good practice to increase the pad size to facilitate wires soldering in case of modifications.\nNOTE\t2 \tto item 3: It is good practice to take into account the surrounding components on the PCB to allow access to the solder pad with the solder tip.\n"]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","10.4.6b","Requirement","ECSS-Q-ST-70-61_1510635",1,"Created"," Solder fillet shall show acceptable wetting on all visible sides."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","10.4.9e","Requirement","ECSS-Q-ST-70-61_1510653",1,"Created","When either thermal or electrical ground performances are requested, exposed pad shall be inspected with X-ray according to criteria defined in requirement 12.4a."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","10.5.2c","Requirement","ECSS-Q-ST-70-61_1510687",1,"Created","Rework of soldered PCB assemblies shall be done when the solder joint does not meet the criteria of clause 12."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","10.5.2j","Requirement","ECSS-Q-ST-70-61_1510694",1,"Created","Wiring of chip capacitors type II soldered on its footprint as identified in the ECSS-Q-ST-70-28C shall not be performed due to possible thermal shock."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","11.1.1d","Requirement","ECSS-Q-ST-70-61_1510710",1,"Created","Flux and residue shall be removed within a maximum period of 8 hours after soldering operations.","NOTE\t1\tIt is good practice to remove flux residues directly after the soldering operation because even rosin fluxes are difficult to remove after longer ageing.\nNOTE\t2\tLonger period can be considered with a successful SIR test presented to Approval Authority.\n"]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","11.1.4d","Requirement","ECSS-Q-ST-70-61_1510725",1,"Created","The test boards shall be visually inspected in accordance with flight representative procedures."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","11.2i","Permission","ECSS-Q-ST-70-61_1510740",1,"Created","Spread of staking and bonding material onto surrounding areas may be accepted providing the staking and bonding shape is in accordance with the assembly verification."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","12.5a","Requirement","ECSS-Q-ST-70-61_1510760",1,"Created","The PCB assembly shall be supported during handling and transportation in order to avoid any mechanical stress on the assembly or component damage.","NOTE\tMechanical support can be provided by spacer or frame.\n"]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","13.1.2.1d","Requirement","ECSS-Q-ST-70-61_1510769",1,"Created","The supplier shall provide a listing of the assembly procedures."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","13.1.4c","Requirement","ECSS-Q-ST-70-61_1510785",1,"Created","The schedule of the verification activities shall be provided and updated."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","13.1.6a","Requirement","ECSS-Q-ST-70-61_1510797",1,"Created","The verification report shall be in compliance with DRD from Annex B."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","13.2.1d","Requirement","ECSS-Q-ST-70-61_1510815",1,"Created","Verification of area array components shall be performed in accordance with the requirements in clause 13.3."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","13.2.1u","Requirement","ECSS-Q-ST-70-61_1510832",1,"Created","Verification testing of commercial components shall be performed for each lot in conformance with this clause 13.2.1, except when requirement 13.8.1d can be met."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","13.2.1gg","Requirement","ECSS-Q-ST-70-61_1510844",1,"Created","The supplier shall organise a MIP1 with two weeks notification, with the Approval Authority prior to any conformal coating.","NOTE\tThe Approval Authority can delegate the MIP1 to the supplier.\n"]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","13.3.1b","Requirement","ECSS-Q-ST-70-61_1510861",1,"Created","The capability and verification samples shall be representative of the FM hardware.","NOTE\tFor example, PCB build-up and size, mechanical fixation, component packages.\nNOTE\tIt is recommended to have a successful IST test on PCB to avoid failing the assembly verification due to damaged PCB.\n"]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","13.3.2g","Requirement","ECSS-Q-ST-70-61_1510871",1,"Created","The components shall be submitted to shock testing in conformance with clause 14.9."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","13.4j","Requirement","ECSS-Q-ST-70-61_1510892",1,"Created","All solder terminations shall be continuously electrically monitored throughout the temperature cycling"]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","13.6b","Requirement","ECSS-Q-ST-70-61_1510907",1,"Created","The verification tests shall be performed to show absence of degradation within the solderless interconnection part, PCB and component during all ground and in-orbit mission.","NOTE\tPossible degradations can be creeping of the spring, fretting degradation of the contact.\n"]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","13.7b","Requirement","ECSS-Q-ST-70-61_1510923",1,"Created","The delta verification shall be performed when changes are undertaken as specified in Table 13-1."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","13.8.4a","Requirement","ECSS-Q-ST-70-61_1510944",1,"Created","Verification by similarity for solderless assembly described in 10.7, shall only be applied when all the following conditions are met\n1.\tComponent and interposer lengths are less than Lmax of the verified component and interposer,\n2.\tComponent and interposer widths are less than Wmax of the verified component and interposer,\n3.\tInterposer has the same height as the verified interposer,\n4.\tComponent weight is lower than the verified component,\n5.\tNumber of terminations is lower than the verified component,\n6.\tPitch is the same as the verified component,\n7.\tMaterials for both component and interposer are the same as the verified component,\n8.\tComponent and interposer finishes are the same as the ones verified,\n9.\tManufacturer and technology for the interposer are the same as the one verified,\n10.\tMechanical construction and mounting principle are the same as the one verified and,\n11.\tComponent and interposer have the same body shape (aspect ratio).","NOTE\tto item 7 and 8: In case the interposer connects two PCBs, the component requirements refer to the PCBs.\n"]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","14.6e","Requirement","ECSS-Q-ST-70-61_1510954",1,"Created","The sampling time for the continuous electrical monitoring shall be maximum 10 s."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","14.8e","Requirement","ECSS-Q-ST-70-61_1510970",1,"Created","Minimum vibration levels shall be as specified in Table 14-1, Table 14-2 and Table 14-3."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","14.9a","Requirement","ECSS-Q-ST-70-61_1510985",1,"Created","Mechanical shock test shall be performed in assembly verification for area array components in accordance with requirements in clause 13.3, for solderless assemblies in accordance with requirements in clause 13.6 and for the following components:\n1.\tRelay\n2.\tQuartz\n3.\tMagnetic components (RM)\n4.\tTransformer and self\n5.\tHybrid\n6.\tTantalum capacitor\n7.\tHeavy or large component\n8.\tOptical components\n9.\tLow insertion force DIP socket \n10.\tSemiconductors (IC) components, Hybrid components, relays, capacitors with cavities","NOTE\tThe list of components is taken from Table 17-1 of ECSS-E-HB-32-25A (14July2015) that is reproduced in this Standard as Table 14-4.\n"]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","14.12c","Permission","ECSS-Q-ST-70-61_1511003",1,"Created","The temperature cycling may be performed in several steps, with different conditions in the different steps.","NOTE\tA typical stepwise temperature cycling test is to perform the cycling in 2 steps as follows:\n·\tStep 1: Temperature range tailored so that the minimum and maximum temperature on board level during the on-ground qualification conditions are covered including the minimum and maximum temperatures during cold start, non-operating and operating, as required for the intended mission. Number of cycles in this step tailored such that the on-ground qualification conditions are covered at least with a safety margin of 2.\t \nThe lower temperatures often result in largest stresses, and it is therefore good practice to cover cold start conditions in this first step so that the number of cycles at the larger temperature range are minimized.\t \nExample: 20 cycles between -40°C/+85°C with a gradient of 2°C/min and a dwell time of 15 minutes corresponds to 15,5 cycles of -55°C/+100°C with a gradient of 10°C/min as calculated with the equation in requirement 14.12g.\n·\tStep 2: Temperature range tailored so that the minimum and maximum temperature on board level during the in-orbit conditions are covered. Number of cycles in this step tailored such that steps 1 and 2 in total correspond to the nominal temperature cycling range that is required for the type of components being verified, typically 500 cycles, when re-calculated with the modified Coffin-Manson (Norris-Landzberg) equation.\n\tExample: 981 cycles between -10/+100°C with a gradient of 10°C/min or slightly lower and 15 minutes of dwell time. 981 such cycles correspond to 484,8 cycles -55/+100°C with gradient ~10°C/min, as calculated with the equation in requirement 14.12g.\n\tThus the cycling during step 1 and step 2 in total covers the full 500 cycles (15,5 + 484,8 = 500,3) required for surface mounted components as required by requirement 13.2.1cc.\nNOTE\t2\tThe reason behind dividing the temperature cycling in different steps is to decrease the risk of thermally overstressing the assembly while not prolonging the schedule more than necessary.\nNOTE\t3\tIt is recommended to perform the tailoring of the temperature cycling such that the envelope of all intended mission requirements can be covered. A case-by-case trade-off between cost, schedule and risk is though often needed. \n"]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","14.15.2a","Requirement","ECSS-Q-ST-70-61_1511020",1,"Created","At least one microsection shall be made per assembly configuration after environmental testing on each type of component, size and assembly processes and soldering processes.","NOTE\t1\tDifferent soldering processes and different staking, bonding or conformal coating are examples of different configurations.\nNOTE\t2\tSuccessive polishing planes can be performed.\n"]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","14.15.3.1g","Requirement","ECSS-Q-ST-70-61_1511033",1,"Created","The Approval Authority shall have access to the moulded microsection and pictures. "]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","14.16c","Permission","ECSS-Q-ST-70-61_1511050",1,"Created","Cracks in the dielectrics under SMT footprints, outside the conditions specified in requirement 14.16a, may be accepted provided that the remaining insulation distance of the flight PCB is in conformance with the PCB definition dossier."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","15.1g","Requirement","ECSS-Q-ST-70-61_1511059",1,"Created","The supplier shall be informed about assembly NCRs in the customer assembly line."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","17.2c","Requirement","ECSS-Q-ST-70-61_1511080",1,"Created","The following documents, as a minimum, shall be made available to supplier\n1.\tPID.\n2.\tAudit report established by the Approval Authority.\n3.\tVerification report."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","17.7b","Requirement","ECSS-Q-ST-70-61_1511090",1,"Created","The inspection shall be performed in conformance with clause 12."]
["ECSS-Q-ST-70-61C","ECSS - Current v1.0","C.2.1<4>a","Requirement","ECSS-Q-ST-70-61_1511110",1,"Created","The PID shall contain the following information about Organisation:\n1.\tRepresented as a flow chart: organization of the company, organization of production department and organization of the quality Department.\n2.\tFocal point and PID responsible,\n3.\tOperators and inspectors’ certification methodology. "]
["ECSS-Q-ST-70-71C Rev.1","ECSS - Current v1.0","4.2.3a","Requirement","ECSS-Q-ST-70-71_1260008",1,"Unchanged","For electronic assemblies applications and wirings, materials and processes shall conform to the requirements from clause 5 to clause 15 of ECSS-Q-ST-70-08 and from clause 5 to clause 16 of ECSS-Q-ST-70-38."]
["ECSS-Q-ST-70-71C Rev.1","ECSS - Current v1.0","4.2.5c","Requirement","ECSS-Q-ST-70-71_1260014",1,"Unchanged","Structural applications using titanium shall be designed to avoid fretting."]
["ECSS-Q-ST-70-71C Rev.1","ECSS - Current v1.0","4.2.9e","Requirement","ECSS-Q-ST-70-71_1260038",1,"Unchanged","The design of parts made of beryllium alloys shall include the material’s low impact resistance, notch sensitivity, its anisotropy and sensitivity to surface finish requirements."]
["ECSS-Q-ST-70-71C Rev.1","ECSS - Current v1.0","4.2.10a","Requirement","ECSS-Q-ST-70-71_1260045",1,"Unchanged","The supplier shall demonstrate that the performances of the selected optical glasses or coatings are not degraded below the specified acceptable levels by ionizing radiation, particle, UV radiation and ATOX for the intended application."]
["ECSS-Q-ST-70-71C Rev.1","ECSS - Current v1.0","4.2.12f","Requirement","ECSS-Q-ST-70-71_1260068",1,"Unchanged","It shall be ensured that the tape is not damaged during its application."]
["ECSS-Q-ST-70-71C Rev.1","ECSS - Current v1.0","4.2.14a","Requirement","ECSS-Q-ST-70-71_1260079",1,"Unchanged","The selection of the lubricant shall avoid the contamination of the lubricated part."]
["ECSS-Q-ST-70-71C Rev.1","ECSS - Current v1.0","4.2.14d","Requirement","ECSS-Q-ST-70-71_1260082",1,"Unchanged","When oils and greases are directly exposed to space environment, the supplier shall demonstrate that the selected grade complies with the mission requirements."]
["ECSS-Q-ST-70-71C Rev.1","ECSS - Current v1.0","4.2.16a","Requirement","ECSS-Q-ST-70-71_1260097",1,"Unchanged","The design and verification of fibre-reinforced composite materials used for structural applications shall conform to the requirements from clause 4 of ECSS-E-ST-32-08."]
["ECSS-Q-ST-70-71C Rev.1","ECSS - Current v1.0","4.2.18a","Requirement","ECSS-Q-ST-70-71_1260115",1,"Unchanged","Structural designs using thermoplastic composite materials shall conform to the requirements of clause 4 of ECSS-E-ST-32-08."]
["ECSS-Q-ST-70-71C Rev.1","ECSS - Current v1.0","4.2.18l","Requirement","ECSS-Q-ST-70-71_1260126",1,"Unchanged","Materials that absorb and release water shall be assessed with respect to the effect on the performance of the material and for contamination risk."]
["ECSS-Q-ST-70-71C Rev.1","ECSS - Current v1.0","4.3.1d","Requirement","ECSS-Q-ST-70-71_1260150",1,"Unchanged","Prepared surfaces shall be protected from contaminants."]
["ECSS-Q-ST-70-71C Rev.1","ECSS - Current v1.0","4.3.2b","Requirement","ECSS-Q-ST-70-71_1260155",1,"Unchanged","Tooling materials shall be selected to ensure thermal-expansion matching between the composite over the processing temperatures.","NOTE\tThe rigidity of the tooling is also an important parameter. \n"]
["ECSS-Q-ST-70-71C Rev.1","ECSS - Current v1.0","4.3.6f","Requirement","ECSS-Q-ST-70-71_1260171",1,"Unchanged","The capability of the equipment to meet the specified requirements, the welding process documentation including process variants, the filler material and any supplementary treatments shall be demonstrated through qualification testing of welded specimens representing the materials and the joint configuration of production parts."]
["ECSS-Q-ST-70-71C Rev.1","ECSS - Current v1.0","4.3.8d","Requirement","ECSS-Q-ST-70-71_1260187",1,"Unchanged","The supplier shall demonstrate that when subsequent fusion welding or brazing is applied, it is not affecting any soldered joints in the vicinity."]
["ECSS-Q-ST-70-71C Rev.1","ECSS - Current v1.0","4.3.10c","Requirement","ECSS-Q-ST-70-71_1260201",1,"Unchanged","An post-plating baking process approved by the customer shall be applied to materials with known or suspected susceptibility to hydrogen embrittlement."]
["ECSS-Q-ST-70-71C Rev.1","ECSS - Current v1.0","4.3.14b","Requirement","ECSS-Q-ST-70-71_1260222",1,"Unchanged","Solvents in inks shall not attack substrates."]
["ECSS-Q-ST-70-71C Rev.1","ECSS - Current v1.0","4.3.15.4a","Requirement","ECSS-Q-ST-70-71_1260230",1,"Unchanged","Fabrication processes and controls used in staking and conformal coating of printed circuit boards and electronic assemblies shall conform to the requirements of from clause 5 to clause 15 of ECSS-Q-ST-70-08, from clause 5 of ECSS-Q-ST-70-07 and from clause 5 to clause 16 of ECSS-Q-ST-70-38."]
["ECSS-Q-ST-70-80C","ECSS - Current v1.0","5.1c","Requirement","ECSS-Q-ST-70-80_1480003",1,"Created","The Z-axis shall be perpendicular to the build platform, as specified in Figure 5‑1."]
["ECSS-Q-ST-70-80C","ECSS - Current v1.0","6.3c","Requirement","ECSS-Q-ST-70-80_1480017",1,"Created","If the customer declares the PMCR successful, the supplier shall proceed with further development."]
["ECSS-Q-ST-70-80C","ECSS - Current v1.0","7.4.2a","Requirement","ECSS-Q-ST-70-80_1480035",1,"Created","The AMVP for class 1.1, 1.2 and class 2 parts shall include as a minimum the tests listed in Table 7-2."]
["ECSS-Q-ST-70-80C","ECSS - Current v1.0","7.5.2d","Requirement","ECSS-Q-ST-70-80_1480054",1,"Created","A Powder capture sample shall be produced to satisfy the requirement in clause 12.2."]
["ECSS-Q-ST-70-80C","ECSS - Current v1.0","7.7.2c","Requirement","ECSS-Q-ST-70-80_1480067",1,"Created","If a machine pause is planned to occur during the hardware production phase, dedicated tests to characterise the properties of the interface zone shall be included in the AMVP."]
["ECSS-Q-ST-70-80C","ECSS - Current v1.0","8.2.3.2a","Requirement","ECSS-Q-ST-70-80_1480084",1,"Created","Samples to provide validation of material shall be built as test pieces and undergo all post processing steps as specified in the HFP."]
["ECSS-Q-ST-70-80C","ECSS - Current v1.0","8.3.2.1a","Requirement","ECSS-Q-ST-70-80_1480094",1,"Created","The density shall be measured on the full height blanks in compliance with clause 12.4."]
["ECSS-Q-ST-70-80C","ECSS - Current v1.0","9.3.1a","Requirement","ECSS-Q-ST-70-80_1480113",1,"Created","Only operators holding a valid qualification test certificate for Laser Powder Bed Fusion (L-PBF) in compliance to ISO ASTM 52942:2020 shall perform operations on such equipment."]
["ECSS-Q-ST-70-80C","ECSS - Current v1.0","10.5.2a","Requirement","ECSS-Q-ST-70-80_1480129",1,"Created","As a minimum, maintenance shall be carried out as described in OEM equipment handbook."]
["ECSS-Q-ST-70-80C","ECSS - Current v1.0","11.1a","Requirement","ECSS-Q-ST-70-80_1480143",1,"Created","The AMP and the HFP shall be under configuration control."]
["ECSS-Q-ST-70-80C","ECSS - Current v1.0","12.3h","Requirement","ECSS-Q-ST-70-80_1480164",1,"Created","For X-Ray CT, the voxel size shall be adapted to the smallest acceptable defect size.","NOTE\tIt is best practise to adjust the resolution such that the smallest acceptable defect size can be detected with at least two voxels. Other important parameters include the contrast to noise ratio, the focal spot size, the reference samples for detection of smallest defect size, etc.\n"]
["ECSS-Q-ST-70-80C","ECSS - Current v1.0","12.5.1.1f","Requirement","ECSS-Q-ST-70-80_1480173",1,"Created","The presence of any alpha case layer on the surface of titanium alloys shall be determined in compliance with EN 2003-009:2007."]
["ECSS-Q-ST-70-80C","ECSS - Current v1.0","13.1a","Requirement","ECSS-Q-ST-70-80_1480188",1,"Created","With a test method proposed by the supplier and agreed with the customer, testing of powders shall include as a minimum:\n1.\tChemical composition, including light elements,\n2.\tParticle size distribution,\n3.\tDensity in both apparent and tapped conditions, and\n4.\tFlow properties.","NOTE\t1\tFor requirement 13.1a1: light elements can include carbon, hydrogen, oxygen, and nitrogen.\nNOTE\t2\tFor requirement 13.1a1: the chemical composition can be determined by energy-dispersive spectrometry (EDS) as per ISO 22309:2011 or ASTM E1508 or by atomic emission spectrometry for Aluminium alloys as per ASTM E3061:2017 and for titanium alloys as per ASTM E 2371:2013.\nNOTE\t3\tFor requirement 13.1a1: determination of hydrogen in titanium alloys can be done by inert gas fusion as per ASTM E 1447:2016. Determination of carbon in refractory and reactive metals can be done by combustion analysis as per ASTM E 1941:2016. Determination of oxygen in titanium alloys can be done by reduction-extraction methods as per ISO 4491-4:2019. Oxygen and nitrogen in titanium alloys can be determined by inert gas fusion as per ASTM E 1409:2013.\nNOTE\t4\tFor requirement 13.1a1: increased oxygen content can lead to reduced ductility of IN 718 at elevated temperatures. It is best practice to limit the oxygen content in the base material more strictly than this is done for conventional materials.\nNOTE\t5\tFor requirement 13.1a2: particle size distribution can be analyzed by sieve analysis as per ISO 4497:2020 or ASTM B214:2016, by laser diffraction in compliance with ISO 13320:2020 or ASTM B822:2017 or by image analysis in compliance with ISO 13322:2014.\nNOTE\t6\tFor requirement 13.1a3: the apparent density can be determined according to ISO 3923-1:2018 or ASTM B212:2017 (Funnel Method). The tap density can be determined according to ISO 3953:2011 or ASTM B527.\nNOTE\t7\tFor requirement 13.1a3: testing for porosity in powder particles is not required, but it can be performed by helium pycnometry in compliance with ASTM B923:2020, or through X-Ray CT scanning.\nNOTE\t8\tFor requirement 13.1a4: flow properties can be determined through the Hall Flowmeter test in compliance with ASTM B213:2020, ASTM B 964:2016, or ISO 4490:2018 and tap density as per ASTM B527:2020. Alternatively, “angle of repose” tests according to ISO 4324:1977 can also be used.\nNOTE\t9\tFor requirement 13.1a4: it is best practice to determine powder particle morphology and satellite build-up with an SEM as complementary information.\nNOTE\t10\tAluminium powders are known to pick up moisture, which can degrade flow properties or lead to significant gas porosity in the final AM part. It is best practice to control the humidity level in areas where AM powder is handled or stored. The test can be performed using one of the following methods: capacitive titration (Karl-Fischer) according to ISO 760:1978 or ASTM E203:2016, thermogravimetric according to ASTM E1131:2020, or with a humidity sensor.\n"]
["ECSS-Q-ST-70-80C","ECSS - Current v1.0","13.7a","Requirement","ECSS-Q-ST-70-80_1480201",1,"Created","For class 1.1, 1.2, and 2 parts, no blending of powder lots shall be permitted.","NOTE\tMixing of powder lots is not permitted as traceability of powders is then lost. Opposed to this, mixing of powder batches is permitted.\n"]
["ECSS-Q-ST-70-80C","ECSS - Current v1.0","I.2.1a","Requirement","ECSS-Q-ST-70-80_1480218",1,"Created","The powder management plan shall specify how powders are \n1.\tTested,\n2.\tProcured,\n3.\tSafely handled,\n4.\tStored,\n5.\tLoaded,\n6.\tRecycled,\n7.\tBlended, and\n8.\tDisposed.","NOTE\tThe detailed requirements are specified in clause 13.\n"]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","4.2.2b","Requirement","ECSS-Q-ST-70_0490006",2,"Unchanged","The lists specified in 4.2.2a shall reflect the current design at the time of issue."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","4.2.3j","Requirement","ECSS-Q-ST-70_0490202",1,"Unchanged","The supplier shall demonstrate that the lists specified in the requirements 4.2.3a, 4.2.3b and 4.2.3c have been formally approved prior to their delivery to the customer."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","4.7a","Requirement","ECSS-Q-ST-70_0490203",1,"Unchanged","For the selection of space materials and processes, ECSS-Q-ST-70-71 shall be applied."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","5.1.4b","Requirement","ECSS-Q-ST-70_0490039",2,"Informative Change","Outgassing screening tests shall be carried out in conformance with requirements from clause 5 of ECSS-Q-ST-70-02. ","The screening process applied depends on the application"]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","5.1.11c","Requirement","ECSS-Q-ST-70_0490216",1,"Informative Change","The compatibility of materials which are or can come into contact with LOX or GOX shall be evaluated except the case specified in the requirement 5.1.11d.","See NASA-STD-6001 Tests No. 13 and No. 14."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","5.1.15a","Requirement","ECSS-Q-ST-70_0490056",2,"Unchanged","Moisture absorption shall be prevented during manufacture and storage of hygroscopic materials. "]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","5.2.1g","Requirement","ECSS-Q-ST-70_0490235",1,"Unchanged","The access to the data, specified in requirement 5.2.1f, shall be granted to the customer."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","5.4.2c","Requirement","ECSS-Q-ST-70_0490066",2,"Unchanged","Any critical material shall be subject to a RFA in conformance with Annex D to be submitted to the customer."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","5.5.3a","Requirement","ECSS-Q-ST-70_0490073",2,"Unchanged","For all critical materials, a validation programme, available at PDR, shall be drawn up by the supplier and then implemented to check or confirm that the materials satisfy the mission requirements with the specified margins to obtain validation status."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","5.7.6a","Requirement","ECSS-Q-ST-70_0490095",2,"Unchanged","Nonconformances and alerts shall be managed in conformance with requirements from the clause 5 and clause 6 of ECSS-Q-ST-10-09 and clause 5.2 of ECSS-Q-ST-10."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","6.3a","Requirement","ECSS-Q-ST-70_0490101",1,"Unchanged","The supplier shall establish and maintain a declared mechanical parts list in conformance with Annex B."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","6.6.3a","Requirement","ECSS-Q-ST-70_0490122",2,"Unchanged","For complex mechanical parts related to a specific project development, each supplier shall define the nature and frequency of their own source inspection points. "]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.2a","Requirement","ECSS-Q-ST-70_0490137",2,"Unchanged","<< deleted >>"]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.3a","Requirement","ECSS-Q-ST-70_0490138",2,"Unchanged","Processes shall be chosen from already verified processes according to the following order of preference and priority:\n1.\tprocesses covered by space agencies or other governmental organization certification for identical conditions of use;\n2.\tprocesses for which satisfactory evaluation and verification results are obtained on samples representative of the application with a sufficient margin as regards conditions of use;\n3.\tprocesses already used by the same supplier for other space programmes in the same conditions of use."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.3b","Requirement","ECSS-Q-ST-70_0490139",2,"Unchanged","Whether the processes are already verified or remain to be verified, their selection shall ensure that the following criteria are met:\n1.\treliability;\n2.\tinspectability;\n3.\tre­workability of the process item;\n4.\treproducibility."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.3c","Requirement","ECSS-Q-ST-70_0490252",1,"Unchanged","The supplier shall store and maintain all processes data in an internal database."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.3d","Requirement","ECSS-Q-ST-70_0490253",1,"Unchanged","The access to the data, from requirement 7.3c, shall be granted to the customer."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.3e","Requirement","ECSS-Q-ST-70_0490254",1,"Unchanged","Processes using limited-life materials shall be in conformance with the requirements from clause 4 of ECSS-Q-ST-70-22."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.3f","Requirement","ECSS-Q-ST-70_0490255",1,"Unchanged","Operators shall be trained for all processes."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.3g","Requirement","ECSS-Q-ST-70_0490256",1,"Unchanged","Operators performing special processes shall be certified in conformance with the requirements of the relevant standard."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.3h","Requirement","ECSS-Q-ST-70_0490257",1,"Unchanged","Inspectors shall be trained and certified for all processes."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.3i","Requirement","ECSS-Q-ST-70_0490258",1,"Unchanged","Certification shall be reassessed at least every two years."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.3j","Requirement","ECSS-Q-ST-70_0490259",1,"Unchanged","All training and certification shall only be performed at a school or by certified instructors in conformance with customer requirements."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.3k","Requirement","ECSS-Q-ST-70_0490260",1,"Unchanged","Retraining and recertification of operators shall be applied in the event of a new process, modification to an existing process or a change of the equipment used."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.3l","Requirement","ECSS-Q-ST-70_0490261",1,"Unchanged","Retraining and recertification of inspectors shall be applied in the event of a new inspection procedure, modification to an existing inspection procedure or a change of an existing one."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.3m","Requirement","ECSS-Q-ST-70_0490262",1,"Unchanged","In the case of a process suspension for four months continuously, retraining and recertification shall be performed."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.3n","Requirement","ECSS-Q-ST-70_0490263",1,"Unchanged","Standards relating to the occupational health of operators working with processes resulting in exposure to vapours, dust or debris shall be implemented and controlled."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.4a","Requirement","ECSS-Q-ST-70_0490140",1,"Unchanged","The supplier shall establish and maintain a declared processes list in conformance with Annex C."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.5.2a","Requirement","ECSS-Q-ST-70_0490141",1,"Unchanged","The supplier shall analyse all the processes contained in their preliminary lists with respect to criticality and in correlation with the risk analyses performed."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.5.2b","Requirement","ECSS-Q-ST-70_0490142",1,"Unchanged","Critical processes shall be identified in the DPL and included in the list of critical items."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.5.2c","Requirement","ECSS-Q-ST-70_0490143",2,"Unchanged","Any critical process shall be the subject of an RFA in conformance with Annex D submitted to customer approval."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.5.2d","Requirement","ECSS-Q-ST-70_0490144",1,"Unchanged","Special processes shall be identified and controlled."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.5.2e","Requirement","ECSS-Q-ST-70_0490145",2,"Informative Change","Process control shall be ensured by means of procedures available for customer review.","Best practice is to implement a statistical process control."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.5.2f","Permission","ECSS-Q-ST-70_0490274",1,"Unchanged","<< deleted >>"]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.6.1a","Requirement","ECSS-Q-ST-70_0490147",2,"Unchanged","If so identified by the criticality analysis, the supplier shall perform an evaluation phase before the verification phase for all critical processes which are new or with major changes in the use or in the configuration. "]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.6.1b","Permission","ECSS-Q-ST-70_0490275",1,"Unchanged","In case of an extension of an existing application, the evaluation specified in requirement 7.6.1a need not be performed if so agreed with the customer."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.6.1c","Requirement","ECSS-Q-ST-70_0490149",1,"Informative Change","For confidential processes, the supplier shall prove that the process has been verified.","1\tFor example, by presenting a verification certificate from space agencies or other governmental organization responsible to check the applicability of this verification.\n2\tRefer to Table 4-1 for an explanation of the steps involved."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.6.2a","Requirement","ECSS-Q-ST-70_0490150",2,"Unchanged","The evaluation specified in 7.6.1a shall include the following as a minimum for each critical process:\n1.\tthe limits of use,\n2.\tthe values, determined by test samples or technology samples, of relevant parameters and their tolerances, and\n3.\tacceptance criteria."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.6.2b","Requirement","ECSS-Q-ST-70_0490151",1,"Unchanged","When an evaluation is performed, the supplier shall provide \n1.\tan evaluation plan at PDR, and\n2.\tan evaluation report before CDR."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.6.3a","Requirement","ECSS-Q-ST-70_0490152",1,"Unchanged","For each critical process, the supplier shall implement a verification programme."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.6.3b","Requirement","ECSS-Q-ST-70_0490153",2,"Unchanged","The verification programme shall be defined in conformance with ECSS-E-ST-10-02."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.6.3c","Requirement","ECSS-Q-ST-70_0490154",1,"Unchanged","The supplier shall ensure that the processes satisfy the mission requirements and that the parameters needed for the product design are defined so as to obtain verification status."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.6.3d","Requirement","ECSS-Q-ST-70_0490155",2,"Unchanged","Verification status shall be decided at CDR in view of the available results obtained, written in verification report, and the review of corresponding documentation."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.6.3e","Requirement","ECSS-Q-ST-70_0490264",1,"Unchanged","The verification programme and report shall be approved by the customer."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.6.4a","Requirement","ECSS-Q-ST-70_0490156",2,"Unchanged","A processes shall not receive an approval identification in the declared processes list unless requirements from clauses 7.6.2 and 7.6.3 are satisfied."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.6.4b","Requirement","ECSS-Q-ST-70_0490265",1,"Unchanged","In case approval specified in the requirement 7.6.4a is not granted, the supplier in charge of the item shall either:\n1.\tselect other processes, or\n2.\tpropose a modified evaluation programme and resubmit for approval, or\n3.\tif actions specified in 7.6.4b.1 and 7.6.4b.2 fail to achieve positive results, initiate a deviation procedure."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.6.5a","Requirement","ECSS-Q-ST-70_0490157",2,"Unchanged","For processes not conforming to project requirements, whether at the end of criticality analysis or of evaluation and verification tests, the supplier shall submit a request for deviation in conformance with requirements from clause 5.2.3.5 of ECSS-Q-ST-10-09."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.7.1a","Requirement","ECSS-Q-ST-70_0490158",1,"Unchanged","The supplier shall confirm that all critical processes have been verified before being used in the manufacture of qualification or flight products."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.7.1b","Requirement","ECSS-Q-ST-70_0490159",2,"Informative Change","Any modification, change of condition or configuration of application shall lead to a re-evaluation in conformance with the process.","See Figure 4-1."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.7.2a","Requirement","ECSS-Q-ST-70_0490160",2,"Informative Change","When a process needs to be re­verified, a request for approval (RFA) in conformance with DRD from Annex D shall be established and a re­verification programme shall be implemented.","Any prolonged stoppage in manufacturing, any major change of the facilities or procedures or any transfer of production to another entity can invalidate partially or completely the initial verification of a process."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.7.3a","Requirement","ECSS-Q-ST-70_0490161",2,"Unchanged","Before implementation of a process, the supplier shall ensure that personnel are trained in accordance with the training and certification programme specified in 7.3f, 7.3g and 7.3h and that environment, means and documentation are adequate."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.7.3b","Requirement","ECSS-Q-ST-70_0490162",2,"Informative Change","This verification shall ensure that: \n1.\tmanufacturing and quality control tools associated with the process are adequate, calibrated and properly maintained are used under environmental and cleanliness conditions, in conformance with requirements from clause 4.4,\n2.\tpersonnel is trained and certified in accordance with the training and certification programme specified in 7.3f, 7.3g and 7.3h, and\n3.\tthe processes specifications, manufacturing and inspection procedures and workmanship standards including definition of manufacturing operations and acceptance criteria exist.","1\tPhotographically documented if possible for visual acceptance criteria at the appropriate work and inspection stations.\n2\tFor planning of manufacturing, assembly and integration operation and inspection see ECSS-Q-ST-20."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.7.4a","Requirement","ECSS-Q-ST-70_0490163",2,"Unchanged","Traceability of processes shall be ensured in conformance with requirements from clause 5.2.5 of ECSS-Q-ST-20."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.7.5a","Requirement","ECSS-Q-ST-70_0490164",2,"Unchanged","Process nonconformances and alerts shall be processed in conformance with requirements from clause 5 to clause 6 of ECSS-Q-ST-10-09 and clause 5.2.9 of ECSS-Q-ST-10."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.7.6a","Requirement","ECSS-Q-ST-70_0490165",2,"Unchanged","MIPs shall be defined in conformance with requirements from clause 5.5.8 of ECSS-Q-ST-20."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","7.7.7a","Requirement","ECSS-Q-ST-70_0490166",1,"Unchanged","The supplier shall define provisions for packaging, storage, and removal from storage for products or semi­finished products before and after implementation of processes."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","A.2.1<1>a","Requirement","ECSS-Q-ST-70_0490167",1,"Unchanged","The DML shall contain the following statements:\n1.\t“Materials are classified into 20 groups depending on their type or their main use, see Table A-1”.\n2.\t“Primers are classified in the group of their associated component.”\n3.\t“Where no project requirement exists for a separate DMPL, mechanical parts are entered on the DML as a separate group with the corresponding numbers.”"]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","A.2.1<1>b","Requirement","ECSS-Q-ST-70_0490168",1,"Unchanged","If new groups are created, for a given project, these shall have numbers over 21."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","A.2.1<2>a","Requirement","ECSS-Q-ST-70_0490169",2,"Unchanged","The DML shall include the information stated in Figure A-1, where the header information identifies the list as the declared materials list and includes the issue number and date of issue, as follows:\n1.\tItem number (applicable to equipment manufacturer level only)\n(a)\tThis consists of the material group identifier and the user code. It takes the form of:\n<group number>.<identifier within the group>.<running number>.<user code>\nNOTE \tFor example: 11.5.1.KOF.\n(b)\tCharacteristics of the item number are:\n-\tThe user, identified by an agreed user code for the project.\n-\tOne only per material type.\n-\tDoes not change during the life of the materials list (sub­items are permitted when deemed necessary).\n2.\tCommercial identification or standardized designation\n(a)\tEnter the correct and standard designation, such as the trade name plus number.\n(b)\tIf no trade name exists, enter the manufacturer’s name plus number.\n(c)\tFor metal alloys, the Aluminium Association (AA) system is recommended for aluminium alloys, and the American Iron and Steel Institute (AISI) system for steel. For other metals or alloys, the main constituent is entered first except in the case of a traditional name.\nNOTE \tFor example: brass or bronze.\n(d)\tFor each material, as designated in A.2.1<2>a2(a) to(c), use a unique item number. If several lines are used for different applications or processing, add sub­item numbers.\n3.\tChemical nature and product type\n(a)\tFor metallic materials, add the condition as procured if applicable.\nNOTE \tExamples of such conditions are rolled and heat treatment.\n(b)\tWhere a semi­finished product is procured, give the relevant state. \nNOTE \tExamples of such state are form, plate and sheet.\n(c)\tGive the thickness of the material, that can be an important parameter.\nNOTE \tExamples of chemical nature are: epoxy resin, polyurethane adhesive, Ti6Al4V.\n4.\tProcurement information\n(a)\tManufacturer or distributor: name of the manufacturer and name of the distributor if different.\n(b)\tProcurement specification: provide reference to one of the following:\n-\tthe procurement specification with issue, revision and date\n-\ta national or international specification or standard, if this exists, and identifies the source of procurement (if relevant), with issue, revision and date\n-\tdatasheets, in which case indication of issue or date is not applicable.\n5.\tProcessing parameters\nList here a summary of the process parameters applied by the user of the process.\nNOTE \tE.g. mixture proportions, cure temperature, special cleaning agent, surface treatment, thermal treatment and temperature, and reference to specification number.\n6.\tUse and location\n(a)\tUse codes able to define the location of the material with respect to the:\n-\tsubsystem;\n-\tparticular piece of equipment (box or item);\n-\tuse of the equipment, e.g. a structural element, thermal control, electrical insulation.\nNOTE \tIf the CI number is not included in the list header, then a suitable abbreviation of the relevant subsystem is included.\n(b)\tInclude any restrictions that apply to the use of a particular material in the corresponding comment column.\n7.\tEnvironmental code\nThe environmental code is defined using Table A-2.\n8.\tSize code\nThe size code is indicated by an alphanumeric combination, such as A5, V2 or M3, as in Table A-3.\n9.\tValidation references, justification for approval and prime comments and prime approval\n(a)\tMake reference to relevant test data that demonstrates the acceptability of the material under the environmental conditions and the application relevant to the particular project concerned. Specifically, in column 9.1, corrosion (CORR), stress corrosion (SCC), flammability (FLAM), offgassing (OFFG) and outgassing (OUTG) data or report­references are entered.\n(b)\tUse standard abbreviations to summarize the acceptance status of a material for a particular property.\n(c)\tUse the justification for approval (column 9.2) and prime approval (column 9.3) columns for any additional information to obtain customer approval.\n(d)\tStandard abbreviations are used to summarize the acceptability or otherwise of a material for a specific property. These are defined for the project.\n(e)\tSelect the supplier approval status code from Table A-4.\n10.\tCustomer approval status code and comments\n(a)\tSelect this code from Table A-4.\n(b)\tInclude additional comments where appropriate."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","A.2.1<2>b","Requirement","ECSS-Q-ST-70_0490266",1,"Unchanged","If heritage is used as justification for approval it shall cover the current hardware configuration and mission profile."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","A.2.2a","Requirement","ECSS-Q-ST-70_0490170",1,"Unchanged","The change record shall list the successive issues and their release dates since the first formal issue of the document."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","A.2.2b","Requirement","ECSS-Q-ST-70_0490171",2,"Informative Change","The change record shall include a brief description of the updates which contributed to each issue or revision.","Figure A-1 of this DRD proposes an example of the format and defines the content within the framework of a project or a programme."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","B.2.1<1>a","Requirement","ECSS-Q-ST-70_0490172",1,"Unchanged","The DMPL shall contain the following statements:\n“Mechanical parts are classified into 11 groups depending on their type or their main use” (see Table B-1)."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","B.2.1<1>b","Requirement","ECSS-Q-ST-70_0490173",1,"Unchanged","If, for a given project it is considered necessary to create new groups, these shall have numbers over 61."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","B.2.1<1>c","Recommendation","ECSS-Q-ST-70_0490276",1,"Informative Change","Items that appear in the EEE parts list should not be repeated here.","For example, heaters, some valves, thermostats, relays, transformer coils and solenoids. "]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","B.2.1<2>a","Requirement","ECSS-Q-ST-70_0490175",2,"Unchanged","The DMPL shall include the information in Figure B-1, where the header information identifies the list as the declared mechanical parts  list and includes the issue number and date of issue, as follows:\n1.\tItem number (applicable at equipment supplier level only)\n(a)\tThis consists of the mechanical part identifier and the user code. It takes the form of:\n<group number>.<identifier within the group>.<running number>.<user code>\nNOTE \tFor example: 7.2.1.ACSA.\n(b)\tCharacteristics of the item number are:\n-\tIdentify the subcontractor by an agreed user code for the project.\n-\tOne only per mechanical part type. \n-\tDoes not change during the life of the mechanical parts list.\n2.\tCommercial identification\n(a)\tEnter the correct and standard designation, such as trade name plus number. \n(b)\tIf no trade name exists then enter the manufacturers’ name and number.\n3.\tType of part\nDescribe the material and surface treatment (if applicable).\n4.\tProcurement information\n(a)\tManufacturer or distributor: name of the manufacturer and name of the distributor if different.\n(b)\tProcurement specification: provide reference to one of the following:\n-\tthe procurement specification with issue, revision and date\n-\ta national or international specification or standard, if this exists, and identifies the source of procurement (if relevant), with issue, revision and date.\n5.\tElementary function, main characteristics\n(a)\tEnter the function of the mechanical part.\n(b)\tEnter the main characteristics of the mechanical part.\nNOTE \tFor example, number of revolutions per minute for a ball bearing.\n6.\tUse and location\nUse codes able to define the location of the mechanical part with respect to the:\n(a)\tsubsystem;\n(b)\tparticular piece of equipment (box or item);\n(c)\tuse of the equipment.\n7.\tEnvironmental code\nThe environmental code is defined using Table B-2.\n8.\tCriticality\nEnter “C” for critical or “N” for non­critical. If a mechanical part is considered critical, describe the reason for the criticality and methods of control.\n9.\tSupplier reference, prime comments and prime approval status \n(a)\tUse the supplier reference, prime comments and approval columns to enter all additional information that are necessary in order to obtain customer approval.\n(b)\tThis information comprises reference and issue of the RFA or approval, mechanical parts justification file, evaluation reports and deviation requests.\n(c)\tMake reference to the relevant test data that demonstrates acceptability of the mechanical part under the environment conditions and the application relevant to the particular project concerned.\n(d)\tUse standard abbreviations, defined by the customer, to summarize the acceptance status of a mechanical part for a particular property.\n(e)\tIn order to justify the use of a material for flammability resistance, list here the material thickness and height of oxygen share.\n(f)\tSelect the prime approval status code from Table B-3.\n10.\tThe customer approval status code and comments\n(a)\tSelect this code from Table B-3. \n(b)      Include additional comments where appropriate."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","B.2.2a","Requirement","ECSS-Q-ST-70_0490176",1,"Unchanged","The change record shall list the successive issues and their release dates since the first formal issue of the document."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","B.2.2b","Requirement","ECSS-Q-ST-70_0490177",2,"Informative Change","This record shall include a brief description of the updates which contributed to each issue or revision.","Figure B-1 of this DRD proposes an example of the format and defines the content within the framework of a project or a programme."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","C.2.1<1>a","Requirement","ECSS-Q-ST-70_0490178",1,"Unchanged","The DPL shall contain the following statements:\nProcesses are classified into 17 groups depending on their type or their main use, see Table C-1."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","C.2.1<1>b","Requirement","ECSS-Q-ST-70_0490179",1,"Unchanged","If, for a given project it is considered necessary to create new groups, these shall have numbers over 17."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","C.2.1<2>a","Requirement","ECSS-Q-ST-70_0490180",2,"Unchanged","The DPL shall include the information in Figure C-1, where the header information identifies the list as the declared processes list and includes the issue number and date of issue, as follows\n1.\tItem number (applicable to equipment supplier level only)\n(a)\tThis consists of the process identifier and the user code. It takes the form of \n<group number>.<identifier within the group>.<running number>.<user code>\nNOTE \tFor example: 1.2.1.SSEX\n(b)\tCharacteristics of the item number are:\n-\tIdentify the subcontractor by an agreed user code for the project.\n-\tOne only per process type. \n-\tDoes not change during the life of the process list.\n2.\tProcess identification\nIndicate the correct and standard identification of the process, e.g. the process name or title: bonding, coating or soldering.\n3.\tSpecification\n(a)\tIdentify the name or abbreviation of the process executor.\n(b)\tMake a reference to the associated procedure, together with the issue, revision and date.\nNOTE \tFor example, national, international, EN, ISO, ECSS or company in­house.\n4.\tProcess description\nEnter here a short description of the process.\n5.\tUse and location\nUse codes able to define the location of the process with respect to the:\n(a)\tsubsystem,\n(b)\tparticular piece of equipment (box or item),\n(c)\tuse of the equipment.\nNOTE \tFor example, a structural element, thermal control, electrical insulation).\n6.\tThis column number is not used.\n7.\tAssociated item numbers\nEnter the associated material list (DML) or mechanical parts list (DMPL) with the process.\n8.\tCriticality\n(a)\tEnter “C” for critical or “N” for non­critical.\n(b)\tIf a process is considered to be critical, Enter the references to the relevant RFA.\n9.\tSupplier reference, prime comments and approval\n(a)\tUse the supplier reference and approval columns to enter all additional information that are necessary to obtain customer approval.\n(b)\tSelect the supplier approval status code from Table C-2.\n(c)\tGive reference to qualification programme performed for critical processes.\n10.\tThe customer approval status code and comments\n(a)\tSelect this code from Table C-2.\n(b)\tInclude additional comments where appropriate."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","C.2.1<2>b","Requirement","ECSS-Q-ST-70_0490268",1,"Unchanged","If heritage is used as justification for approval it shall cover the current hardware configuration and mission profile."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","C.2.2a","Requirement","ECSS-Q-ST-70_0490181",1,"Unchanged","The change record shall list the successive issues and their release dates since the first formal issue of the document."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","C.2.2b","Requirement","ECSS-Q-ST-70_0490182",2,"Informative Change","This record shall include a brief description of the updates which contributed to each issue or revision.","Figure C-1 of this DRD proposes an example of the format and define the content within the framework of a project or a programme."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","D.2.1a","Recommendation","ECSS-Q-ST-70_0490277",1,"Unchanged","The RFA should contain the information in Figure D-1 (pages 1 and 2), as follows:\n1.\tThe header information, identifying the document as a request for approval together with the project logo and project name, RFA reference, issue revision and date.\n2.\tOriginator\nOriginator’s name and reference.\n3.\tLocation\nSubsystem and equipment codes.\n4.\tItem description\nBrief description of the item.\n5.\tPMP information\nThe DML, DMPL or DPL item number and list reference.\n6.\tItem status, including the following information:\n(a)\tmanufacturers’ name and qualification reference;\n(b)\tsuppliers’ name and qualification status;\n(c)\tproduct or material specification;\n(d)\tprocurement specification;\n(e)\tprocess or handling specification;\n(f)\tother related process or handling specifications;\n(g)\tverification or qualification specification;\n(h)\treport on verification or qualification.\n7.\tReason for RFA\nEnter the reason for the RFA.\n8.\tApplication and location details\nEnter here the details of the application and exact location of the item.\nGive the reference in the CIL.\n9.\tEvaluation and validation programme\nReference and details of main tests.\n10.\tSubcontractor supplier approval for the first issue of the RFA.\n11.\tCustomer initial decision, to be entered on first issue of the RFA providing:\n(a)\tthe decision concerning the proposed material,\n(b)\tthe requirement to perform tests (deviation request as necessary), and\n(c)\tthe decision concerning the proposed test programme.\n12.\tCustomer’s and final customer’s (if applicable) signature\n13.\tJustification results obtained with reference to the supplier’s validation report and conclusion.\n14.\tSubcontractor supplier approval on RFA final issue.\n15.\tFinal approval status of the RFA by the customer."]
["ECSS-Q-ST-70C Rev.2","ECSS - Current v1.0","D.2.2a","Requirement","ECSS-Q-ST-70_0490184",1,"Unchanged","The RFA shall be completed by the supplier (parts 1 to 10, 13 and 14) and the customer (parts 11, 12 and 15). "]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.1.1a","Requirement","ECSS-Q-ST-80_0720001",1,"Unchanged","The supplier shall ensure that an organizational structure is defined for software development, and that individuals have defined tasks and responsibilities."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.1.2.1a","Requirement","ECSS-Q-ST-80_0720002",1,"Informative Change","The responsibility, the authority and the interrelation of personnel who manage, perform and verify work affecting software quality shall be defined and documented.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; SRR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.1.2.2a","Requirement","ECSS-Q-ST-80_0720003",1,"Informative Change","The responsibilities and the interfaces of each organisation, either external or internal, involved in a project shall be defined and documented.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; SRR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.1.2.3a","Requirement","ECSS-Q-ST-80_0720004",1,"Informative Change","The delegation of software product assurance tasks by a supplier to a lower level supplier shall be done in a documented and controlled way, with the supplier retaining the responsibility towards the customer.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; SRR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.1.3.1a","Requirement","ECSS-Q-ST-80_0720005",1,"Informative Change","The supplier shall provide adequate resources to perform the required software product assurance tasks.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; SRR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.1.3.2a","Requirement","ECSS-Q-ST-80_0720006",1,"Unchanged","Reviews and audits of processes and of products shall be carried out by personnel not directly involved in the work being performed."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.1.4.1a","Requirement","ECSS-Q-ST-80_0720007",1,"Informative Change","The supplier shall identify the personnel responsible for software product assurance for the project (SW PA manager/engineer).\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; SRR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.1.4.2a","Requirement","ECSS-Q-ST-80_0720008",1,"Unchanged","The software product assurance manager/engineer shall\n1.\treport to the project manager (through the project product assurance manager, if any);\n2.\thave organisational authority and independence to propose and maintain a software product assurance programme in accordance with the project software product assurance requirements;\n3.\thave unimpeded access to higher management as necessary to fulfil his/her duties."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.1.5.1a","Requirement","ECSS-Q-ST-80_0720009",1,"Informative Change","The supplier shall review the project requirements to establish and make timely provision for acquiring or developing the resources and skills for the management and technical staff.\nEXPECTED OUTPUT:\tTraining plan [MGT, -; SRR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.1.5.2a","Requirement","ECSS-Q-ST-80_0720010",1,"Informative Change","The supplier shall maintain training records.\nEXPECTED OUTPUT:\tRecords of training and experience [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.1.5.3a","Requirement","ECSS-Q-ST-80_0720011",1,"Unchanged","The supplier shall ensure that the right composition and categories of appropriately trained personnel are available for the planned activities and tasks in a timely manner."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.1.5.4a","Requirement","ECSS-Q-ST-80_0720012",2,"Normative Change","The supplier shall determine the training subjects based on the specific tools, techniques, methodologies, and computer resources to be used in developing and managing software product. ","NOTE \tPersonnel can undergo training to acquire skills and knowledge relevant to the specific field with which the software is to deal.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.1.5.4b","Requirement","ECSS-Q-ST-80_0720314",1,"Created","The supplier shall ensure that personnel involved in the planned activities and tasks are appropriately trained for:\n1.\tsoftware security analysis, security audits;\n2.\tsecurity engineering;\n3.\tsecurity assurance methods and tools;\n4.\tsecurity rules, policies and procedures applicable to the project. ","NOTE \tIt is good practice to make use of security certified organizations performing these types of training.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.1.1a","Requirement","ECSS-Q-ST-80_0720013",1,"Unchanged","The supplier shall develop a software product assurance plan in response to the software product assurance requirements in conformance with DRD in annex B."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.1.1b","Requirement","ECSS-Q-ST-80_0720014",1,"Informative Change","The software product assurance plan shall be either a standalone document or a section of the supplier overall product assurance plan.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.1.2a","Requirement","ECSS-Q-ST-80_0720015",1,"Unchanged","Any internal manuals, standards or procedures referred to by the software product assurance plan shall become an integral part of the supplier’s software product assurance programme."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.1.3a","Requirement","ECSS-Q-ST-80_0720016",1,"Informative Change","The software product assurance plan shall be revisited and updated as needed at each milestone to ensure that the activities to be undertaken in the following phase are fully defined.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.1.4a","Requirement","ECSS-Q-ST-80_0720017",1,"Informative Change","Before acceptance review, the supplier shall either supplement the software product assurance plan to specify the quality measures related to the operations and maintenance processes, or issue a specific software product assurance plan.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; AR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.1.5a","Requirement","ECSS-Q-ST-80_0720018",1,"Informative Change","The supplier shall provide with the software product assurance plan a compliance matrix documenting conformance with the individual software product assurance requirements applicable for the project or business agreement.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.1.5b","Requirement","ECSS-Q-ST-80_0720019",1,"Informative Change","For each software product assurance requirement, the compliance matrix shall provide a reference to the document where the expected output of that requirement is located.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; SRR, PDR].","NOTE \tFor compliance with the required DRDs a general statement of compliance is acceptable.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.2.1a","Requirement","ECSS-Q-ST-80_0720020",1,"Informative Change","The supplier shall report on a regular basis on the status of the software product assurance programme implementation, if appropriate as part of the overall product assurance reporting of the project.\nEXPECTED OUTPUT:\tSoftware product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.2.2a","Requirement","ECSS-Q-ST-80_0720021",1,"Informative Change","The software product assurance report shall include:\n1.\tan assessment of the current quality of the product and processes, based on measured properties, with reference to the metrication as defined in the software product assurance plan;\n2.\tverifications undertaken;\n3.\tproblems detected;\n4.\tproblems resolved. \nEXPECTED OUTPUT:\tSoftware product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.2.3a","Requirement","ECSS-Q-ST-80_0720022",1,"Informative Change","The supplier shall deliver at each milestone review a software product assurance milestone report, covering the software product assurance activities performed during the past project phases.\nEXPECTED OUTPUT:\tSoftware product assurance milestone report [PAF, SPAMR; SRR, PDR, CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.3a","Requirement","ECSS-Q-ST-80_0720023",1,"Informative Change","For software audits, ECSS-Q-ST-10 clause 5.2.3 shall apply.\nEXPECTED OUTPUT:\tAudit plan and schedule [PAF, -; SRR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.4a","Requirement","ECSS-Q-ST-80_0720024",1,"Informative Change","For software alerts, ECSS-Q-ST-10 clause 5.2.9 shall apply.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Preliminary alert information [PAF, -; -];\nb. Alert information [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.5.1a","Requirement","ECSS-Q-ST-80_0720025",1,"Informative Change","The supplier shall define and implement procedures for the logging, analysis and correction of all software problems, encountered during software development.\nEXPECTED OUTPUT:\tSoftware problem reporting procedures [PAF, -; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.5.2a","Requirement","ECSS-Q-ST-80_0720026",1,"Informative Change","The software problem report shall contain the following information:\n1.\tidentification of the software item;\n2.\tdescription of the problem;\n3.\trecommended solution;\n4.\tfinal disposition;\n5.\tmodifications implemented (e.g. documents, code, and tools);\n6.\ttests re-executed.\nEXPECTED OUTPUT:\tSoftware problem reporting procedures [PAF, -; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.5.3a","Requirement","ECSS-Q-ST-80_0720027",1,"Informative Change","The procedures for software problems shall define the interface with the nonconformance system (i.e. the circumstances under which a problem qualifies as a nonconformance).\nEXPECTED OUTPUT:\tSoftware problem reporting procedures [PAF, -; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.5.4a","Requirement","ECSS-Q-ST-80_0720028",1,"Unchanged","The supplier shall ensure the correct application of problem reporting procedures."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.6.1a","Requirement","ECSS-Q-ST-80_0720029",1,"Informative Change","For software nonconformance handling, ECSS-Q-ST-10-09 shall apply. \nEXPECTED OUTPUT:\tThe following outputs are expected:\na. NCR SW procedure as part of the Software product assurance plan [PAF, SPAP; SRR];\nb. Nonconformance reports [DJF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.6.1b","Requirement","ECSS-Q-ST-80_0720030",1,"Informative Change","When dealing with software nonconformance, the NRB shall include, at least, a representative from the software product assurance and the software engineering organizations.\nEXPECTED OUTPUT:\tIdentification of SW experts in NRB [MGT, -; SRR]"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.6.1c","Requirement","ECSS-Q-ST-80_0720312",1,"Informative Change","The NRB shall dispose software nonconformances according to the following criteria:\n1.\tuse “as‐is”, when the software is found to be usable without eliminating the nonconformance;\n2.\tfix, when the software product can be made fully in conformance with all specified requirements, by:\n(a)\tcorrection of the software,\n(b)\taddition of software patches, or\n(c)\tre‐design.\n3.\treturn to supplier, for procured software products (e.g. COTS).\nEXPECTED OUTPUT:\tNonconformance reports [DJF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.6.1d","Requirement","ECSS-Q-ST-80_0720315",1,"Created","When dealing with software nonconformance with a possible security impact, the NRB shall include a representative from the software security engineering organizations."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.6.2a","Requirement","ECSS-Q-ST-80_0720031",1,"Informative Change","The software product assurance plan shall specify the point in the software life cycle from which the nonconformance procedures apply.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.7.1a","Requirement","ECSS-Q-ST-80_0720032",1,"Informative Change","Quality models shall be used to specify the software quality requirements.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.2.7.2a","Requirement","ECSS-Q-ST-80_0720033",1,"Informative Change","The following characteristics shall be used to specify the quality model:\n1.\tfunctionality;\n2.\treliability;\n3.\tmaintainability;\n4.\treusability;\n5.\tsuitability for safety;\n6.\tsecurity;\n7.\tusability;\n8.\tefficiency;\n9.\tportability;\n10.\tsoftware development effectiveness.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; PDR].","NOTE\t1\tQuality models are the basis for the identification of process metrics (see clause 6.2.5) and product metrics (see clause 7.1.4).\nNOTE\t2\tQuality models are also addressed by ISO/IEC 25000 and ECSS-Q-HB-80-04.\nNOTE\t3 \tSoftware security vulnerabilities should be taken into account in the quality model.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.3.1a","Requirement","ECSS-Q-ST-80_0720034",1,"Unchanged","Risk management for software shall be performed by cross-reference to the project risk policy, as specified in ECSS-M-ST-80."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.3.2.1a","Requirement","ECSS-Q-ST-80_0720035",1,"Unchanged","For critical item control, ECSS-Q-ST-10-04 shall apply."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.3.2.2a","Requirement","ECSS-Q-ST-80_0720036",1,"Unchanged","The supplier shall identify the characteristics of the software items that qualify them for inclusion in the Critical Item List."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.4.1.1a","Requirement","ECSS-Q-ST-80_0720037",1,"Informative Change","For supplier selection ECSS-Q-ST-20 clause 5.4.1 shall apply.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Results of pre­award audits and assessments [PAF, -; -];\nb. Records of procurement sources [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.4.1.2a","Requirement","ECSS-Q-ST-80_0720038",2,"Normative Change","For the selection of suppliers of existing software, including software contained in OTS equipment and units, the expected output of clauses 6.2.7.2 to 6.2.7.6 shall be made available.\nEXPECTED OUTPUT:\tSoftware reuse file [DJF, SRF; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.4.2.1a","Requirement","ECSS-Q-ST-80_0720039",1,"Informative Change","The supplier shall establish software product assurance requirements for the next level suppliers, tailored to their role in the project, including a requirement to produce a software product assurance plan.\nEXPECTED OUTPUT:\tSoftware product assurance requirements for suppliers [PAF, -; SRR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.4.2.2a","Requirement","ECSS-Q-ST-80_0720040",1,"Normative Change","The supplier shall provide the software product assurance requirements applicable to the next level suppliers for customer’s acceptance.\nEXPECTED OUTPUT:\tSoftware product assurance requirements for suppliers [PAF, -; SRR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.4.3.1a","Requirement","ECSS-Q-ST-80_0720041",1,"Unchanged","The supplier shall monitor the next lower level suppliers’ conformance to the product assurance requirements. "]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.4.3.2a","Requirement","ECSS-Q-ST-80_0720042",1,"Unchanged","The monitoring process shall include the review and approval of the next lower level suppliers’ product assurance plans, the continuous verification of processes and products, and the monitoring of the final validation of the product."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.4.3.3a","Requirement","ECSS-Q-ST-80_0720043",1,"Informative Change","The supplier shall ensure that software development processes are defined and applied by the next lower level suppliers in conformance with the software product assurance requirements for suppliers.\nEXPECTED OUTPUT:\tNext level suppliers’ software product assurance plan [PAF, SPAP; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.4.3.4a","Requirement","ECSS-Q-ST-80_0720044",1,"Normative Change","The supplier shall provide the next lower level suppliers’ software product assurance plan for customer’s acceptance.\nEXPECTED OUTPUT:\tNext level suppliers’ software product assurance plan [PAF, SPAP; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.4.4a","Requirement","ECSS-Q-ST-80_0720045",1,"Informative Change","The supplier shall provide the lower level suppliers with the relevant results of the safety and dependability analyses performed at higher and his level (ref. clauses 6.2.2.1 and 6.2.2.2), including:\n1.\tthe criticality classification of the software products to be developed;\n2.\tinformation about the failures that can be caused at higher level by the software products to be developed.\nEXPECTED OUTPUT:\tSafety and dependability analyses results for lower level suppliers [RB, -; SRR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.4.5a","Requirement","ECSS-Q-ST-80_0720316",1,"Created","The supplier shall provide its suppliers with the relevant results of the security analyses performed at higher and his level as specified in 6.2.9.2), including:\n1.\tthe security sensitivity of the software products to be developed;\n2.\tinformation about the failures, attacks and related security impacts that can be caused at higher level by the software products during development and operation.\nEXPECTED OUTPUT:\tSecurity analyses results for lower level suppliers [SF,-;SRR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.5.1a","Requirement","ECSS-Q-ST-80_0720046",1,"Unchanged","For procurement documents, ECSS-Q-ST-20 clause 5.4.2 shall apply."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.5.2a","Requirement","ECSS-Q-ST-80_0720047",1,"Informative Change","The choice of procured software shall be described and submitted for customer review.\nEXPECTED OUTPUT:\tSoftware development plan [MGT, SDP; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.5.3a","Requirement","ECSS-Q-ST-80_0720048",2,"Normative Change","For each of the software items the following data shall be provided:\n1.\tordering criteria\n2.\treceiving inspection criteria;\n3.\tback­up solutions if the product becomes unavailable;\n4.\tcontractual arrangements with the supplier for the development, maintenance and upgrades to new releases;\n5.\tcountry source information if required by the customer.\nEXPECTED OUTPUT:\tProcurement data [MGT, -; SRR, PDR].","NOTE \tExamples of ordering criteria are: versions, options, security certifications and extensions.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.5.4a","Requirement","ECSS-Q-ST-80_0720049",1,"Unchanged","All the procured software shall be identified and registered by configuration management."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.5.5a","Requirement","ECSS-Q-ST-80_0720050",1,"Informative Change","The supplier shall subject the procured software to a planned receiving inspection, in accordance with ECSS-Q-ST-20 clause 5.4.4, and the receiving inspection criteria as required by clause 5.5.3.\nEXPECTED OUTPUT:\tReceiving inspection report [PAF, -; PDR, CDR, QR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.5.6a","Requirement","ECSS-Q-ST-80_0720051",1,"Informative Change","Exportability constraints shall be identified.","NOTE \tExportability constraints include constraints concerning applicable security export-control regulations.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.6.1.1a","Requirement","ECSS-Q-ST-80_0720052",1,"Informative Change","Methods and tools to be used for all the activities of the development cycle, (including requirements analysis, software specification, modelling, design, coding, validation, testing, configuration management, verification and product assurance) shall be identified by the supplier and agreed by the customer.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.6.1.2a","Requirement","ECSS-Q-ST-80_0720053",2,"Normative Change","The choice of development methods and tools shall be justified by demonstrating through testing or documented assessment that:\n1.\tthe development team has appropriate experience or training to apply them,\n2.\tthe tools and methods are appropriate for the functional and operational characteristics of the product, and\n3.\tthe tools are available throughout the development and maintenance lifetime of the product,\n4.\tthe tools and methods are appropriate to the security sensitivity of the product as determined by the security analysis and as defined in the software security management plan.\nEXPECTED OUTPUT:\tSoftware product assurance milestone report [PAF, SPAMR; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.6.1.3a","Requirement","ECSS-Q-ST-80_0720054",1,"Informative Change","The correct use of methods and tools shall be verified and reported. \nEXPECTED OUTPUT:\tSoftware product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.6.2.1a","Requirement","ECSS-Q-ST-80_0720055",2,"Normative Change","The software development environment shall be selected according to the following criteria:\n1.\tavailability;\n2.\tcompatibility;\n3.\tperformance;\n4.\tmaintenance;\n5.\tdurability and technical consistency with the operational equipment;\n6.\tthe assessment of the product with respect to requirements, including the criticality category;\n7.\tthe available support documentation;\n8.\tthe acceptance and warranty conditions;\n9.\tthe conditions of installation, preparation, training and use;\n10.\tthe maintenance conditions, including the possibilities of evolutions;\n11.\tcopyright and intellectual property rights constraints;\n12.\tdependence on one specific supplier;\n13.\tthe assessment of the product with respect to the security sensitivity level of the products;\n14.\tcompliance with appropriate security requirements due to organizational or national security regulations, policies or directives.\nEXPECTED OUTPUT:\tSoftware development plan [MGT, SDP; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.6.2.2a","Requirement","ECSS-Q-ST-80_0720056",1,"Informative Change","The suitability of the software development environment shall be justified.\nEXPECTED OUTPUT:\tSoftware development plan [MGT, SDP; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.6.2.3a","Requirement","ECSS-Q-ST-80_0720057",1,"Unchanged","The availability of the software development environment to developers and other users shall be verified before the start of each development phase."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.7.1a","Requirement","ECSS-Q-ST-80_0720058",2,"Normative Change","The supplier shall monitor and control the capability of the processes used during the development of the software, including the relevant processes corresponding to the services called from other organizational entities outside the project team.\nEXPECTED OUTPUT:\tSoftware process assessment records: Overall assessments and improvement programme plan [PAF, -; -].","NOTE\t1\tThe process assessment and improvement performed at organization level can be used to provide evidence of compliance for the project.\nNOTE\t2\tProcess capability is the default process characteristic to be monitored and controlled. It is a characterization of the ability of a process to repeatability, predictability and consistently deliver its defined outcomes.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.7.2.1a","Requirement","ECSS-Q-ST-80_0720059",1,"Informative Change","The process assessment model and method to be used when performing any software process assessment shall be documented. \nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Software process assessment record: assessment model [PAF, -; -];\nb. Software process assessment record: assessment method [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.7.2.2a","Requirement","ECSS-Q-ST-80_0720060",2,"Normative Change","Assessments performed and process assessment models used shall be in conformance with ISO/IEC 33002:2015.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Software process assessment record: evidence of conformance of the process assessment model [PAF, -; -];\nb. Software process assessment record: assessment method [PAF, -; -]. ","NOTE\t1\tCurrently the model and method documented in ECSS-Q-HB-80-02 are not fully conformant to ISO/IEC 33002, however they can also be used with the customer agreement.\nNOTE\t2\tCurrently the CMMI model is not fully conformant to ISO/IEC 15504, however it can be used, provided that the SCAMPI A method is applied.\nNOTE\t3\tOrganisations that meet the requirements to be designated as Very Small Entity (VSE): enterprises, organizations, departments or projects having up to 25 people, can choose to use a model and a method conformant to ISO/IEC 29110-6-1.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.7.2.3a","Requirement","ECSS-Q-ST-80_0720061",2,"Normative Change","The process assessment model, the method, the assessment scope, the results and the assessors shall be\n1.\testablished by the customer, and\n2.\tverified that they are compliant with the project requirements.\nEXPECTED OUTPUT:\tSoftware process assessment record: Software process assessment recognition evidence [PAF, -; -].","NOTE\t1\tExamples of assessment scopes are: organizational unit evaluated, and processes evaluated.\nNOTE\t2\tECSS-Q-HB-80-02 provides space specific process reference model and their indicators.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.7.2.4a","Requirement","ECSS-Q-ST-80_0720062",2,"Normative Change","Assessments, shall be performed by a competent assessor.\nEXPECTED OUTPUT:\tSoftware process assessment record: competent assessor justification [PAF, -; -].","NOTE \tThe competency of assessors could be established by the customer on the basis of ISO/IEC 33001 or through certification.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.7.3.1a","Requirement","ECSS-Q-ST-80_0720063",1,"Unchanged","The results of the assessment shall be used as feedback to improve as necessary the performed processes, to recommend changes in the direction of the project, and to determine technology advancement needs."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.7.3.1b","Requirement","ECSS-Q-ST-80_0720064",1,"Informative Change","The suppliers shall ensure that the results of previous assessments are used in its project activity \nEXPECTED OUTPUT:\tSoftware process assessment records: improvement plan [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.7.3.2a","Requirement","ECSS-Q-ST-80_0720065",1,"Informative Change","The process improvement shall be conducted according to a documented process improvement process.\nEXPECTED OUTPUT:\tSoftware process assessment records: improvement process [PAF, -; -].","NOTE\t1\tFor the definition of the process improvement process, see ECSS-Q-HB-80-02.\nNOTE\t2\tFor CMMI, the process improvement is described in the OPF (Organizational Process Focus) process area.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","5.7.3.3a","Requirement","ECSS-Q-ST-80_0720066",2,"Normative Change","Evidence of the improvement in performed processes shall be provided.\nEXPECTED OUTPUT:\tSoftware process assessment records: evidence of improvements [PAF, -; -].","NOTE\t1\tSee ECSS-Q-HB-80-02.\nNOTE\t2\tDepending on the context, improvements and changes at organisation level can be used to claim process improvement at project level.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.1.1a","Requirement","ECSS-Q-ST-80_0720067",1,"Unchanged","The software development life cycle shall be defined or referenced in the software product assurance plan."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.1.1b","Requirement","ECSS-Q-ST-80_0720068",1,"Informative Change","The following characteristics of the software life cycle shall be defined:\n1.\tphases;\n2.\tinput and output of each phase;\n3.\tstatus of completion of phase output;\n4.\tmilestones;\n5.\tdependencies;\n6.\tresponsibilities;\n7.\trole of the customer at each milestone review, in conformance with ECSS-M-ST-10 and ECSS-M-ST-10-01.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.1.2a","Requirement","ECSS-Q-ST-80_0720069",1,"Unchanged","In the definition of the life cycle and associated milestones and documents, the quality objectives shall be used."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.1.3a","Requirement","ECSS-Q-ST-80_0720070",2,"Normative Change","The software life cycle shall be reviewed against the contractual software engineering, product assurance and security assurance requirements. "]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.1.4a","Requirement","ECSS-Q-ST-80_0720071",1,"Unchanged","The software life cycle shall be reviewed for suitability and for the availability of resources to implement it by all functions involved in its application."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.1.4b","Requirement","ECSS-Q-ST-80_0720317",1,"Created","The disposal and release of the resources used after the software development concludes, shall be performed in accordance with the relevant security requirements."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.1.5a","Requirement","ECSS-Q-ST-80_0720072",2,"Informative Change","A mandatory TRR, as specified in clause 5.3.5.1 of ECSS-E-ST-40, shall be held, in the form of a Project Review as specified in clause 5.3.3.2 ECSS-E-ST-40, before the beginning of the validation against the requirements baseline, to check that:\n1.\tthe software status is compatible with the commencement of validation activities;\n2.\tthe necessary resources, software product assurance plans, test and validation documentation, simulators or other technical means are available and ready for use.\nEXPECTED OUTPUT:\tConfirmation of readiness of test activities [DJF; TRR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.1.1a","Requirement","ECSS-Q-ST-80_0720073",2,"Normative Change","The following activities shall be covered either in software-specific plans or in project general plans:\n1.\tdevelopment;\n2.\tspecification, design and customer documents to be produced;\n3.\tconfiguration and documentation management;\n4.\tverification, testing and validation activities;\n5.\tmaintenance and retirement;\n6.\tsecurity management.\nEXPECTED OUTPUT:\tSoftware project plans [MGT, MF, DJF, SF]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.1.2a","Requirement","ECSS-Q-ST-80_0720074",1,"Informative Change","All plans shall be finalized before the start of the related activities.\nEXPECTED OUTPUT:\tSoftware project plans [MGT, MF, DJF]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.1.3a","Requirement","ECSS-Q-ST-80_0720075",1,"Informative Change","All plans shall be updated for each milestone to reflect any changes during development.\nEXPECTED OUTPUT:\tSoftware project plans [MGT, MF, DJF]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.1.4a","Requirement","ECSS-Q-ST-80_0720076",1,"Informative Change","The software product assurance plan shall identify all plans to be produced and used, the relationship between them and the time­scales for their preparation and update.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.1.5a","Requirement","ECSS-Q-ST-80_0720077",1,"Unchanged","Each plan shall be reviewed against the relevant contractual requirements. "]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.1.6a","Requirement","ECSS-Q-ST-80_0720078",1,"Informative Change","Procedures and project standards shall address all types of software products included in the project.\nEXPECTED OUTPUT:\tProcedures and standards [PAF, -; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.1.7a","Requirement","ECSS-Q-ST-80_0720079",1,"Informative Change","All procedures and project standards shall be finalized before starting the related activities.\nEXPECTED OUTPUT:\tProcedures and standards [PAF, -; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.1.8a","Requirement","ECSS-Q-ST-80_0720080",1,"Unchanged","Each procedure or standard shall be reviewed against the relevant plans and contractual requirements."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.1.9a","Requirement","ECSS-Q-ST-80_0720081",1,"Unchanged","Before any activity is started, each procedure or standard for that activity shall be reviewed by all functions involved in its application, for suitability and for the availability of resources to implement it."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.2.1a","Requirement","ECSS-Q-ST-80_0720082",2,"Informative Change","For the system-level analyses leading to the criticality classification of software products based on the severity of failures consequences, ECSS-Q-ST-40 clause 6.5.6.3, and ECSS-Q-ST-30 clause 5.4, shall apply.\nEXPECTED OUTPUT:\tCriticality classification of software products [PAF, -; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.2.2a","Requirement","ECSS-Q-ST-80_0720083",2,"Informative Change","The supplier shall perform a software dependability and safety analysis of the software products, using the results of system-level safety and dependability analyses, in order to determine the criticality of the individual software components.\nEXPECTED OUTPUT:\tSoftware dependability and safety analysis report [PAF, -; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.2.3a","Requirement","ECSS-Q-ST-80_0720084",1,"Unchanged","The supplier shall identify the methods and techniques for the software dependability and safety analysis to be performed at technical specification and design level."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.2.3b","Requirement","ECSS-Q-ST-80_0720085",1,"Informative Change","Methods and techniques for software dependability and safety analysis shall be agreed between the supplier and customer.\nEXPECTED OUTPUT:\tCriticality classification of software components [PAF, -; PDR].","NOTE \tECSS-Q-HB-80-03 provides indication on methods and techniques that can be applied such as: \n·\tsoftware failure modes and effects analysis (for the performing of this analysis, see also ECSS-Q-ST-30-02);\n·\tsoftware fault tree analysis;\n·\tsoftware common cause failure analysis.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.2.4a","Requirement","ECSS-Q-ST-80_0720086",1,"Unchanged","Based on the results of the software criticality analysis, the supplier shall apply engineering measures to reduce the number of critical software components and mitigate the risks associated with the critical software (ref. clause 6.2.3)."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.2.5a","Requirement","ECSS-Q-ST-80_0720087",1,"Informative Change","The supplier shall report on the status of the implementation and verification of the SW dependability and safety analysis recommendations.\nEXPECTED OUTPUT:\tSoftware dependability and safety analysis report [PAF, -; CDR, QR, AR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.2.6a","Requirement","ECSS-Q-ST-80_0720088",1,"Unchanged","The supplier shall update the software dependability and safety analysis at each software development milestone, to confirm the criticality category of software components.\nEXPECTED OUTPUT:\tSoftware dependability and safety analysis report [PAF, -; CDR, QR, AR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.2.7a","Requirement","ECSS-Q-ST-80_0720089",1,"Unchanged","The supplier shall provide the results of the software dependability and safety analysis for integration into the system-level dependability and safety analyses, addressing in particular:\n1.\tadditional failure modes identified at software design level;\n2.\trecommendations for system-level activities.\nEXPECTED OUTPUT:\tSoftware dependability and safety analysis report [PAF, -; PDR, CDR].","NOTE \tFor example: introduction of hardware inhibits, and modifications of the system architecture.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.2.8a","Requirement","ECSS-Q-ST-80_0720090",1,"Unchanged","As part of the software requirements analysis activities (ref. clause 6.3.2), the supplier shall contribute to the Hardware-Software Interaction Analysis (HSIA) by identifying, for each hardware failure included in the HSIA, the requirements that specify the software behaviour in the event of that hardware failure."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.2.9a","Requirement","ECSS-Q-ST-80_0720091",2,"Unchanged","During the verification and validation of the software requirements resulting from the Hardware-Software Interaction Analysis, the supplier shall verify that the software reacts correctly to hardware failures, and no undesired software behaviour occurs that lead to system failures."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.2.10a","Requirement","ECSS-Q-ST-80_0720313",1,"Informative Change","If it cannot be prevented that software components cause failures of higher criticality components, due to failure propagation or use of shared resources, then all the involved components shall be classified at the highest criticality category among them.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Software product assurance plan [PAF, SPAP; PDR, CDR];\nb. Software dependability and safety analysis report [PAF, -; PDR, CDR, QR, AR].","NOTE \tFailures of higher-criticality software components caused by lower-criticality components can be prevented by design measures such as separate hardware platforms, isolation of software processes or prohibition of shared memory (segregation and partitioning).\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.3.1a","Requirement","ECSS-Q-ST-80_0720092",2,"Unchanged","<<deleted>>"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.3.1b","Requirement","ECSS-Q-ST-80_0720093",2,"Unchanged","<<deleted>>"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.3.2a","Requirement","ECSS-Q-ST-80_0720094",1,"Informative Change","The supplier shall define, justify and apply measures to assure the dependability and safety of critical software.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; PDR, CDR].","NOTE \tThese measures can include:\n·\tuse of software design or methods that have performed successfully in a similar application;\n·\tinsertion of features for failure isolation and handling (ref. ECSS-Q-HB-80-03, software failure modes and effects analysis);\n·\tdefensive programming techniques, such as input verification and consistency checks;\n·\tuse of a “safe subset” of programming language;\n·\tuse of formal design language for formal proof;\n·\t100 % code branch coverage at unit testing level;\n·\tfull inspection of source code;\n·\twitnessed or independent testing;\n·\tgathering and analysis of failure statistics;\n·\tremoving deactivated code or showing through a combination of analysis and testing that the means by which such code can be inadvertently executed are prevented, isolated, or eliminated;\n·\tuse of dynamic code verification techniques.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.3.3a","Requirement","ECSS-Q-ST-80_0720095",1,"Informative Change","The application of the chosen measures to handle the critical software shall be verified.\nEXPECTED OUTPUT:\tSoftware product assurance milestone report [PAF, SPAMR; PDR, CDR, QR, AR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.3.4a","Requirement","ECSS-Q-ST-80_0720096",1,"Informative Change","Critical software shall be subject to regression testing after:\n1.\tany change of functionality of the underlying platform hardware;\n2.\tany change of the tools that affect directly or indirectly the generation of the executable code.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; PDR, CDR].","NOTE\t1\tIn case of minor changes in tools that affect the generation of the executable code, a binary comparison of the executable code generated by the different tools can be used to verify that no modifications are introduced.\nNOTE\t2\tExample for item 1: instruction set of a processor.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.3.5a","Requirement","ECSS-Q-ST-80_0720097",1,"Informative Change","The need for additional verification and validation of critical software shall be analysed after:\n1.\tany change of functionality or performance of the underlying platform hardware;\n2.\tany change in the environment in which the software or the platform hardware operate.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; PDR, CDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.3.6a","Requirement","ECSS-Q-ST-80_0720098",1,"Unchanged","Identified unreachable code shall be removed and the need for re-verification and re-validation shall be analysed. "]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.3.7a","Requirement","ECSS-Q-ST-80_0720099",1,"Unchanged","Unit and integration testing shall be (re-)executed on non-instrumented code."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.3.8a","Requirement","ECSS-Q-ST-80_0720100",1,"Unchanged","Validation testing shall be (re-)executed on non-instrumented code."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.4.1a","Requirement","ECSS-Q-ST-80_0720101",1,"Unchanged","ECSS-M-ST-40 shall be applied for software configuration management, complemented by the following requirements."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.4.2a","Requirement","ECSS-Q-ST-80_0720102",1,"Informative Change","The software configuration management system shall allow any reference version to be re­generated from backups.\nEXPECTED OUTPUT:\tSoftware configuration management plan [MGT, SCMP; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.4.3a","Requirement","ECSS-Q-ST-80_0720103",1,"Informative Change","The software configuration file and the software release document shall be provided with each software delivery.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Software configuration file [DDF, SCF; -];\nb. Software release document [DDF, SRelD; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.4.4a","Requirement","ECSS-Q-ST-80_0720104",1,"Informative Change","The software configuration file shall be available and up to date for each project milestone.\nEXPECTED OUTPUT:\tSoftware configuration file [DDF, SCF; CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.4.5a","Requirement","ECSS-Q-ST-80_0720105",1,"Unchanged","Any components of the code generation tool that are customizable by the user shall be put under configuration control."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.4.5b","Requirement","ECSS-Q-ST-80_0720106",1,"Informative Change","The change control procedures defined for the project shall address the specific aspects of these components.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Software configuration file [DDF, SCF; CDR, QR, AR, ORR];\nb. Software configuration management plan [MGT, SCMP; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.4.6a","Requirement","ECSS-Q-ST-80_0720107",1,"Informative Change","The supplier shall ensure that all authorized changes are implemented in accordance with the software configuration management plan.\nEXPECTED OUTPUT:\tAuthorized changes - Software configuration file [DDF, SCF; CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.4.7a","Requirement","ECSS-Q-ST-80_0720108",2,"Normative Change","The following documents shall be controlled (see ECSS-Q-ST-10 clause 5.2.5):\n1.\tprocedural documents describing the quality system to be applied during the software life cycle;\n2.\tplanning documents describing the planning and progress of the activities;\n3.\tdocuments describing a particular software product, including:\n(a)\tdevelopment phase inputs,\n(b)\tdevelopment phase outputs,\n(c)\tverification and validation plans and results,\n(d)\ttest case specifications, test procedures and test reports,\n(e)\ttraceability matrices,\n(f)\tvalidation control documentation,\n(g)\tdocumentation for the software and system operators and users,\n(h)\tmaintenance documentation, and\n(i)\tRetirement documentation. "]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.4.8a","Requirement","ECSS-Q-ST-80_0720109",1,"Informative Change","The supplier shall identify a method and tool to protect the supplied software against corruption.","NOTE \tFor example: source code, executable and data.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.4.8b","Requirement","ECSS-Q-ST-80_0720318",1,"Created","The supplier shall select methods and tools to protect the supplied software in accordance with the security analysis."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.4.8c","Requirement","ECSS-Q-ST-80_0720319",1,"Created","The security analysis can define security requirements on software integrity checks.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Software product assurance plan [PAF, SPAP; SRR, PDR]; \nb. Software configuration file [DDF, SCF; CDR, QR, AR, ORR];\nc. Software security management plan [SF, SSMP; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.4.9a","Requirement","ECSS-Q-ST-80_0720110",2,"Normative Change","The supplier shall specify the necessary elements and mechanisms to prove integrity and authenticity of the SW product.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Software product assurance plan [PAF, SPAP; SRR, PDR];\nb. Software security management plan, [SF, SSMP; , SRR].","NOTE \tA valid method for integrity verification could be the use of checksum.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.4.10a","Requirement","ECSS-Q-ST-80_0720111",2,"Normative Change","The integrity verification value shall be provided in the software configuration file with each software delivery.\nEXPECTED OUTPUT:\tSoftware configuration file [DDF, SCF; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.4.11a","Requirement","ECSS-Q-ST-80_0720112",2,"Normative Change","For every software delivery from the supplier to the customer, the following information shall be provided as a minimum:\n1.\tthe software name;\n2.\tthe version number;\n3.\tthe reference to the software configuration file;\n4.\tinformation and media in accordance with any requirements for delivery and protective security marking;\n5.\tany annotation and caveats used to indicate or further constraint the distribution limitations.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Software product assurance plan [PAF, SPAP; SRR, PDR];\nb. Labels [DDF, -; -];\nc. Software security management plan [SF, SSMP; SRR];\nd. Protective security markings  [SF,-,-].","NOTE \tProtective security marking, e.g. security classification, is mandated by organisational or national security regulations, policies or directives.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.4.12a","Requirement","ECSS-Q-ST-80_0720320",1,"Created","Procedures shall be established for software branching and merging and the corresponding use of software configuration management tools.\nEXPECTED OUTPUT:\tSoftware configuration management plan [MGT, SCMP; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.5.1a","Requirement","ECSS-Q-ST-80_0720113",1,"Informative Change","Metrics shall be used to manage the development and to assess the quality of the development processes. \nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; SRR, PDR].","NOTE \tProcess metrics are based on quality models (see clause 5.2.7).\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.5.2a","Requirement","ECSS-Q-ST-80_0720114",1,"Informative Change","Process metrics shall be collected, stored and analysed on a regular basis by applying quality models and procedures. \nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.5.3a","Requirement","ECSS-Q-ST-80_0720115",1,"Informative Change","The following basic process metrics shall be used within the supplier’s organization: \n1.\tduration: how phases and tasks are being completed versus the planned schedule;\n2.\teffort: how much effort is consumed by the various phases and tasks compared to the plan.\nEXPECTED OUTPUT:\tInternal metrics report."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.5.4a","Requirement","ECSS-Q-ST-80_0720116",1,"Informative Change","Process metrics shall be used within the supplier’s organization and reported to the customer, including:\n1.\tnumber of problems detected during verification;\n2.\tnumber of problems detected during integration and validation testing and use. \nEXPECTED OUTPUT:\tSoftware product assurance reports [PAF, -; -].","NOTE \tSee also software problem reporting described in clause 5.2.5.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.5.5a","Requirement","ECSS-Q-ST-80_0720117",1,"Unchanged","Metrics reports shall be included in the software product assurance reports.\nEXPECTED OUTPUT:\tSoftware product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.6.1a","Requirement","ECSS-Q-ST-80_0720118",1,"Informative Change","Activities for the verification of the quality requirements shall be specified in the definition of the verification plan. \nEXPECTED OUTPUT:\tSoftware verification plan [DJF, SVerP; SRR, PDR].","NOTE \tVerification includes various techniques such as review, inspection, walk­through, cross-reading, desk-checking, model simulation, and many types of analysis such as traceability analysis, formal proof or fault tree analysis. \n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.6.2a","Requirement","ECSS-Q-ST-80_0720119",1,"Unchanged","The outputs of each development activity shall be verified for conformance against pre-defined criteria."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.6.2b","Requirement","ECSS-Q-ST-80_0720120",1,"Informative Change","Only outputs which have been subjected to planned verifications shall be used as inputs for subsequent activities.\nEXPECTED OUTPUT:\tSoftware product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.6.3a","Requirement","ECSS-Q-ST-80_0720121",1,"Informative Change","A summary of the assurance activities concerning the verification process and their findings shall be included in software product assurance reports.\nEXPECTED OUTPUT:\tSoftware product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.6.4a","Requirement","ECSS-Q-ST-80_0720122",1,"Informative Change","The completion of actions related to software problem reports generated during verification shall be verified and recorded.\nEXPECTED OUTPUT:\tSoftware problem reports [DJF, -; SRR, PDR, CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.6.5a","Requirement","ECSS-Q-ST-80_0720123",1,"Informative Change","Software containing deactivated code shall be verified specifically to ensure that the deactivated code cannot be activated or that its accidental activation cannot harm the operation of the system.\nEXPECTED OUTPUT:\tSoftware verification report [DJF, SVR; CDR, QR, AR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.6.6a","Requirement","ECSS-Q-ST-80_0720124",1,"Informative Change","Software containing configurable code shall be verified specifically to ensure that any unintended configuration cannot be activated at run time or included during code generation.\nEXPECTED OUTPUT:\tSoftware verification report [DJF, SVR; CDR, QR, AR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.6.7a","Requirement","ECSS-Q-ST-80_0720125",1,"Informative Change","The supplier shall ensure that:\n1.\tthe planned verification activities are adequate to confirm that the products of each phase are conformant to the applicable requirements;\n2.\tthe verification activities are performed according to the plan. \nEXPECTED OUTPUT:\tSoftware product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.6.8a","Requirement","ECSS-Q-ST-80_0720126",1,"Unchanged","Reviews and inspections shall be carried out according to defined criteria, and according to the defined level of independence of the reviewer from the author of the reviewed item. "]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.6.9a","Requirement","ECSS-Q-ST-80_0720127",1,"Unchanged","Each review and inspection shall be based on a written plan or procedure.\nEXPECTED OUTPUT:\tReview and inspection plans or procedures [PAF, -; -].","NOTE \tFor projects reviews, ECSS-E-ST-40 clause 5.3.3.3, bullet b and Annex P are applicable.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.6.10a","Requirement","ECSS-Q-ST-80_0720128",1,"Informative Change","The review or inspection plans or procedures shall specify: \n1.\tthe reviewed or inspected items;\n2.\tthe person in charge;\n3.\tthe participants;\n4.\tthe means of review or inspection (e.g. tools or check list);\n5.\tthe nature of the report.\nEXPECTED OUTPUT:\tReview and inspection plans or procedures [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.6.11a","Requirement","ECSS-Q-ST-80_0720129",1,"Informative Change","Review and inspection reports shall:\n1.\trefer to the corresponding review/inspection procedure or plan; \n2.\tidentify the reviewed item, the author, the reviewer, the review criteria and the findings of the review.\nEXPECTED OUTPUT:\tReview and inspection reports [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.6.12a","Requirement","ECSS-Q-ST-80_0720130",1,"Informative Change","Traceability matrices (as defined in ECSS-E-ST-40 clause 5.8) shall be verified at each milestone.\nEXPECTED OUTPUT:\tSoftware product assurance milestone report [PAF, SPAMR; SRR, PDR, CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.6.13a","Requirement","ECSS-Q-ST-80_0720131",1,"Informative Change","Independent software verification shall be performed by a third party.","NOTE \tThis requirement is applicable where the risks associated with the project justify the costs involved. The customer can consider a less rigorous level of independence, e.g. an independent team in the same organization.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.6.13b","Requirement","ECSS-Q-ST-80_0720132",2,"Normative Change","Independent software verification shall be a combination of reviews, inspections, analyses, simulations, and auditing.","NOTE \tGuidance on ISVV purpose, scope, and activities is provided in CSW-ESAISVV-2022-GBK-02897.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.6.13c","Requirement","ECSS-Q-ST-80_0720321",1,"Created","Independent software verification shall be performed in addition to, and shall not fully or partly replace, verification activities to be carried out by the supplier in accordance with ECSS-E-ST-40, clause 5.8.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. ISVV plan [DJF, -; SRR, PDR];\nb. ISVV report [DJF, -; PDR, CDR, QR, AR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.7.2a","Requirement","ECSS-Q-ST-80_0720133",2,"Normative Change","Analyses of the advantages to be obtained with the selection of existing software (ref. 3.2.9) instead of new development shall be carried out.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na.\tSoftware reuse approach, including approach to delta qualification [PAF, SPAP; SRR, PDR];\nb.\tSoftware reuse file [DJF, SRF; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.7.3a","Requirement","ECSS-Q-ST-80_0720134",1,"Informative Change","The existing software shall be assessed with regards to the applicable functional, performance and quality requirements."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.7.3b","Requirement","ECSS-Q-ST-80_0720322",1,"Created","The existing software shall be assessed with regards to the applicable security requirements, addressing the following aspects:\n1.\tAuthorisation for use;\n2.\tSecurity sensitivity;\n3.\tSecurity assurance requirements;\n4.\tSecurity evaluations, certifications and accreditations.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Software reuse approach, including approach to delta qualification [PAF, SPAP; SRR, PDR];\nb. Software reuse file [DJF, SRF; SRR, PDR].","NOTE \tFor example, Common Criteria (CC), FIPS, system accreditation, council approval.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.7.4a","Requirement","ECSS-Q-ST-80_0720135",2,"Normative Change","The quality level of the existing software shall be analysed with respect to the project requirements, according to the criticality and sensitivity of the system function implemented, taking into account the following aspects:\n1.\tsoftware requirements documentation;\n2.\tsoftware architectural and detailed design documentation;\n3.\tforward and backward traceability between system requirements, software requirements, design and code;\n4.\tunit tests documentation and coverage;\n5.\tintegration tests documentation and coverage;\n6.\tvalidation documentation and coverage;\n7.\tverification reports;\n8.\tperformance;\n9.\toperational performances;\n10.\tresidual nonconformances, waivers; and alerts;\n11.\tuser operational documentation;\n12.\tcode quality (adherence to coding standards, metrics);\n13.\tknown security vulnerabilities in the reused product, including vulnerabilities introduced by dependencies at all levels between components.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Software reuse approach, including approach to delta qualification [PAF, SPAP; SRR, PDR];\nb. Software reuse file [DJF, SRF; SRR, PDR].","NOTE\t1\tExamples of performance are memory occupation, CPU load.\nNOTE\t2\tExample of user operation documentation is a user manual.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.7.5a","Requirement","ECSS-Q-ST-80_0720136",1,"Informative Change","The results of the reused software analysis shall be recorded in the software reuse file, together with an assessment of the possible level of reuse and a description of the assumptions and the methods applied when estimating the level of reuse.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Software reuse approach, including approach to delta qualification [PAF, SPAP; SRR, PDR];\nb. Software reuse file [DJF, SRF; SRR, PDR].","NOTE \tResults of the reused software analysis, such as detailed reference to requirement and design documents, test reports and coverage results.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.7.6a","Requirement","ECSS-Q-ST-80_0720137",1,"Informative Change","The analysis of the suitability of existing software for reuse shall be complemented by an assessment of the following aspects:\n1.\tthe acceptance and warranty conditions;\n2.\tthe available support documentation; \n3.\tthe conditions of installation, preparation, training and use; \n4.\tthe identification and registration by configuration management; \n5.\tmaintenance responsibility and conditions, including the possibilities of changes; \n6.\tthe durability and validity of methods and tools used in the initial development, that are envisaged to be used again; \n7.\tthe copyright and intellectual property rights constraints (modification rights); \n8.\tthe licensing conditions;\n9.\texportability constraints.\nEXPECTED OUTPUT:\tSoftware reuse file [DJF, SRF; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.7.7a","Requirement","ECSS-Q-ST-80_0720138",1,"Informative Change","Corrective actions shall be identified, documented in the reuse file and applied to the reused software not meeting the applicable requirements related to the aspects as specified in clauses 6.2.7.2 to 6.2.7.6.\nEXPECTED OUTPUT:\tSoftware reuse file [DJF, SRF; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.7.8a","Requirement","ECSS-Q-ST-80_0720139",1,"Unchanged","Reverse engineering techniques shall be applied to generate missing documentation and to reach the required verification and validation coverage."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.7.8b","Requirement","ECSS-Q-ST-80_0720140",2,"Normative Change","For software products whose life cycle data from previous development are not available and reverse engineering techniques are not fully applicable, the following methods shall be applied:\n1.\tgeneration of validation and verification documents based on the available user documentation (e.g. user manual) and execution of tests in order to achieve the required level of test coverage;\n2.\tuse of the product service history to provide evidence of the product’s suitability for the current application, including information about:\n(a)\trelevance of the product service history for the new operational environment;\n(b)\tconfiguration management and change control of the software product;\n(c)\teffectiveness of problem reporting;\n(d)\tactual error rates and maintenance records;\n(e)\timpact of modifications;\n(f)\tnumber, types, priorities and correction rates of vulnerabilities.\nEXPECTED OUTPUT:\tSoftware reuse file [DJF, SRF; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.7.9a","Requirement","ECSS-Q-ST-80_0720141",1,"Informative Change","The software reuse file shall be updated at project milestones to reflect the results of the identified corrective actions for reused software not meeting the project requirements.\nEXPECTED OUTPUT:\tSoftware reuse file [DJF, SRF; CDR, QR, AR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.7.10a","Requirement","ECSS-Q-ST-80_0720142",1,"Unchanged","All the reused software shall be kept under configuration control."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.7.11a","Requirement","ECSS-Q-ST-80_0720143",1,"Informative Change","The detailed configuration status of the reused software baseline shall be provided to the customer in the reuse file for acceptance.\nEXPECTED OUTPUT:\tSoftware reuse file [DJF, SRF; SRR, PDR, CDR, QR, AR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.8.1a","Requirement","ECSS-Q-ST-80_0720144",1,"Unchanged","For the selection of tools for automatic code generation, the supplier shall evaluate the following aspects:\n1.\tevolution of the tools in relation to the tools that use the generated code as an input;\n2.\tcustomization of the tools to comply with project standards; \n3.\tportability requirements for the generated code; \n4.\tcollection of the required design and code metrics; \n5.\tverification of software components containing generated code; \n6.\tconfiguration control of the tools including the parameters for customisation;\n7.\tcompliance with open standards.","NOTE \tExamples for item 1: compilers or code management systems.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.8.2a","Requirement","ECSS-Q-ST-80_0720145",1,"Informative Change","The requirements on testing applicable to the automatically generated code shall ensure the achievement of the same objectives as those for manually generated code.\nEXPECTED OUTPUT:\tValidation and testing documentation [DJF, SValP; PDR], [DJF, SVS; CDR, QR, AR], [DJF, SUITP; PDR, CDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.8.3a","Requirement","ECSS-Q-ST-80_0720146",1,"Unchanged","The required level of verification and validation of the automatic generation tool shall be at least the same as the one required for the generated code, if the tool is used to skip verification or testing activities on the target code."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.8.4a","Requirement","ECSS-Q-ST-80_0720147",1,"Informative Change","Modelling standards for automatic code generation tools shall be defined and applied.\nEXPECTED OUTPUT:\tModelling standards [PAF, -; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.8.5a","Requirement","ECSS-Q-ST-80_0720148",1,"Informative Change","Adherence to modelling standards shall be verified.\nEXPECTED OUTPUT:\tSoftware product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.8.6a","Requirement","ECSS-Q-ST-80_0720149",1,"Unchanged","Clause 6.3.4 shall apply to automatically generated code, unless the supplier demonstrates that the automatically generated code does not need to be manually modified."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.8.7a","Requirement","ECSS-Q-ST-80_0720150",1,"Informative Change","The verification and validation documentation shall address separately the activities to be performed for manually and automatically generated code.\nEXPECTED OUTPUT:\tValidation and testing documentation [DJF, SValP; PDR], [DJF, SVS; CDR, QR, AR], [DJF, SUITP; PDR, CDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.9.1a","Requirement","ECSS-Q-ST-80_0720323",1,"Created","The software product assurance plan shall include security assurance.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; SRR, PDR, CDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.9.2a","Requirement","ECSS-Q-ST-80_0720324",1,"Created","The supplier shall perform a software security analysis of the software products, using the results of system-level security analyses, where software products are part of a system, in order to determine the sensitivity of the individual software components.\nEXPECTED OUTPUT:\tSoftware security analysis report [SF, -; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.9.3a","Requirement","ECSS-Q-ST-80_0720325",1,"Created","The supplier shall identify the methods and techniques for the software security analysis."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.9.3b","Requirement","ECSS-Q-ST-80_0720326",1,"Created","Methods and techniques for software security analysis shall be agreed between the supplier and customer.","NOTE \tExamples of software security analysis are: Requirements analysis, security risk analysis, design analysis and code analysis.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.9.4a","Requirement","ECSS-Q-ST-80_0720327",1,"Created","Based on the results of the software security analysis, the supplier shall apply engineering measures to reduce the number of security sensitive software components and mitigate the risks associated with security sensitive software (ref. clause 6.2.10)."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.9.5a","Requirement","ECSS-Q-ST-80_0720328",1,"Created","The supplier shall report on the status of the implementation and verification of the software security analysis recommendations.\nEXPECTED OUTPUT:\tSoftware security analysis report [SF, -; CDR, QR, AR]"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.9.6a","Requirement","ECSS-Q-ST-80_0720329",1,"Created","The supplier shall update the software security analysis at each software development milestone, to confirm the security sensitivity and related security risks of software components.\nEXPECTED OUTPUT:\tSoftware security analysis report [SF, -; CDR, QR, AR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.9.7a","Requirement","ECSS-Q-ST-80_0720330",1,"Created","The supplier shall provide the results of the software security analysis for integration into the system-level security analyses, addressing in particular:\n1.\tadditional security failure modes or vulnerabilities identified at software level;\n2.\trecommendations for system-level security activities and changes to the system including requirements\nEXPECTED OUTPUT:\tSoftware security analysis report [SF, -; PDR, CDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.10.1a","Requirement","ECSS-Q-ST-80_0720331",1,"Created","The supplier shall define and implement measures to avoid propagation of failures, including the ones caused by deliberate action, between software components.","NOTE \tThis can be achieved by design measures such as separate hardware platforms, fail secure isolation of software processes or prohibition of shared memory (segregation and partitioning). \n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.10.1b","Requirement","ECSS-Q-ST-80_0720332",1,"Created","The consequences for security of the malfunction of higher criticality components, and the consequences for safety and dependability of the malfunction of higher sensitivity components shall be analysed and any conflict resolved.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Software dependability and safety analysis report [PAF, -; PDR, CDR, QR, AR];\nb. Software security analysis report [SF, -; PDR, CDR, QR, AR].","NOTE    These measures can include:\n·\tuse of secure coding practices;\n·\tuse of security baseline(s);\n·\tuse of fuxxing, static, dynamic security testing;\n·\tuse of vulnerability assessment and penetration testing.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.10.2a","Requirement","ECSS-Q-ST-80_0720333",null,"Created","For security sensitive software, measures shall be defined, justified and applied, in addition to those in clause 6.2.3.2.\nEXPECTED OUTPUT:\tSoftware security management plan [SF, , SSMP;; PDR, CDR, QR, AR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.10.3a","Requirement","ECSS-Q-ST-80_0720334",1,"Created","Security sensitive software shall be subject to regression testing after:\n1.\tany change of functionality of the underlying platform hardware;\n2.\tany change of the tools that affect directly or indirectly the generation of the executable code;\n3.\tany change in the security of the target operating environment.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Software product assurance plan [PAF, SPAP; PDR, CDR];\nb. Software security management plan [SF, SSMP; PDR, CDR].","NOTE\t1\tThis can be the result of changing security characteristics of the existing environment. Alternatively, this can be due to the migration of the software from one operating environment to another.\nNOTE\t2\tIn case of minor changes in tools that affect the generation of the executable code, a binary comparison of the executable code generated by the different tools can be used to verify that no modifications are introduced.\nNOTE\t3\tExample for item 1: instruction set of a processor.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.2.10.4a","Requirement","ECSS-Q-ST-80_0720335",1,"Created","The need for additional V&V of security sensitive software shall be analysed after:\n1.\tany change of functionality or performance of the underlying platform hardware;\n2.\tany change in the environment in which the software or the platform hardware operate;\n3.\tany change in knowledge of security threats, security vulnerabilities or security sensitivity of the system;\n4.\tany change in the infrastructure and tools used to build environment.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Software product assurance plan [PAF, SPAP; PDR, CDR];\nb. Software security management plan [SF, SSMP; PDR, CDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.1.1a","Requirement","ECSS-Q-ST-80_0720151",1,"Unchanged","For the definition of the software related system requirements to be specified in the requirements baseline, ECSS-E-ST-40 clause 5.2 shall apply."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.1.2a","Requirement","ECSS-Q-ST-80_0720152",1,"Unchanged","The requirements baseline shall be subject to documentation control and configuration management as part of the development documentation."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.1.3a","Requirement","ECSS-Q-ST-80_0720153",1,"Unchanged","For the definition of the requirements baseline, all results from the safety and dependability analyses (including results from the HSIA ECSS-Q-ST-30 clause 6.4.2.3) shall be used."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.1.3b","Requirement","ECSS-Q-ST-80_0720336",1,"Created","For the definition of the requirements baseline, all results from the security analysis shall be used."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.2.1a","Requirement","ECSS-Q-ST-80_0720154",1,"Unchanged","The requirements baseline shall be analyzed to fully and unambiguously define the software requirements in the technical specification."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.2.2a","Requirement","ECSS-Q-ST-80_0720155",1,"Unchanged","The technical specification shall be subject to documentation control and configuration management as part of the development documentation."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.2.3a","Requirement","ECSS-Q-ST-80_0720156",1,"Unchanged","For the definition of the technical specification, all results from the safety and dependability analyses (including results from the HSIA ECSS-Q-ST-30 clause 6.4.2.3) shall be used."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.2.3b","Requirement","ECSS-Q-ST-80_0720337",1,"Created","For the definition of the technical specification, all results from the software security analysis shall be used."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.2.4a","Requirement","ECSS-Q-ST-80_0720157",1,"Informative Change","In addition to the functional requirements, the technical specification shall include all non-functional requirements necessary to satisfy the requirements baseline, including, as a minimum, the following:\n1.\tperformance,\n2.\tsafety,\n3.\treliability,\n4.\trobustness,\n5.\tquality,\n6.\tmaintainability,\n7.\tconfiguration management,\n8.\tsecurity,\n9.\tprivacy,\n10.\tmetrication, and\n11.\tverification and validation.\nEXPECTED OUTPUT:\tSoftware requirements specification [TS, SRS; PDR].","NOTE \tPerformance requirements include requirements on numerical accuracy.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.2.5a","Requirement","ECSS-Q-ST-80_0720158",2,"Normative Change","Prior to the technical specification elaboration, customer and supplier shall agree on the following principles and rules as a minimum:\n1.\tassignment of persons (on both sides) responsible for establishing the technical specification;\n2.\tmethods and tools for agreeing on requirements and approving changes;\n3.\tefforts to prevent misunderstandings such as definition of terms, explanations of background of requirements;\n4.\trecording and reviewing discussion results on both sides."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.3.1a","Requirement","ECSS-Q-ST-80_0720159",1,"Unchanged","The design definition file shall be subject to documentation control and configuration management. "]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.3.2a","Requirement","ECSS-Q-ST-80_0720160",1,"Informative Change","Mandatory and advisory design standards shall be defined and applied.\nEXPECTED OUTPUT:\tDesign standards [PAF, -; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.3.3a","Requirement","ECSS-Q-ST-80_0720161",1,"Informative Change","For software in which numerical accuracy is relevant to mission success specific rules on design and code shall be defined to ensure that the specified level of accuracy is obtained.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; PDR].","NOTE \tFor example: for an attitude and orbit control subsystem, scientific data generation components.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.3.4a","Requirement","ECSS-Q-ST-80_0720162",1,"Informative Change","Adherence to design standards shall be verified.\nEXPECTED OUTPUT:\tSoftware product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.3.5a","Requirement","ECSS-Q-ST-80_0720163",1,"Unchanged","The supplier shall define means, criteria and tools to ensure that the complexity and modularity of the design meet the quality requirements."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.3.5b","Requirement","ECSS-Q-ST-80_0720164",1,"Informative Change","The design evaluation shall be performed in parallel with the design process, in order to provide feedback to the software design team.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.3.6a","Requirement","ECSS-Q-ST-80_0720165",1,"Informative Change","Synthesis of the results obtained in the software complexity and modularity evaluation and corrective actions implemented shall be described in the software product assurance reports.\nEXPECTED OUTPUT:\tSoftware product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.3.7a","Requirement","ECSS-Q-ST-80_0720166",1,"Informative Change","The supplier shall review the design documentation to ensure that it contains the appropriate level of information for maintenance activities.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Software product assurance plan [PAF, SPAP; PDR];\nb. Software product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.4.1a","Requirement","ECSS-Q-ST-80_0720167",2,"Normative Change","Coding standards (including security, consistent naming conventions and adequate commentary rules) shall be specified and observed.\nEXPECTED OUTPUT:\tCoding standards [PAF, -; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.4.2a","Requirement","ECSS-Q-ST-80_0720168",1,"Informative Change","The standards shall be consistent with the product quality requirements.\nEXPECTED OUTPUT:\tCoding standards [PAF, -; PDR].","NOTE \tCoding standards depend on the software quality objectives (see clause 5.2.7).\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.4.3a","Requirement","ECSS-Q-ST-80_0720169",1,"Informative Change","The tools to be used in implementing and checking conformance with coding standards shall be identified in the product assurance plan before coding activities start.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.4.4a","Requirement","ECSS-Q-ST-80_0720170",2,"Normative Change","Coding standards shall be reviewed with the customer to ensure that they reflect product quality and security requirements.\nEXPECTED OUTPUT:\tCoding standards and description of tools [PAF, -; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.4.5a","Requirement","ECSS-Q-ST-80_0720171",1,"Informative Change","Use of low-level programming languages shall be justified.\nEXPECTED OUTPUT:\tSoftware development plan [MGT, SDP; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.4.6a","Requirement","ECSS-Q-ST-80_0720172",2,"Normative Change","The supplier shall define measurements, criteria and tools to ensure that the software code meets the quality and security requirements.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.4.6b","Requirement","ECSS-Q-ST-80_0720173",1,"Unchanged","The code evaluation shall be performed in parallel with the coding process, in order to provide feedback to the software programmers."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.4.7a","Requirement","ECSS-Q-ST-80_0720174",1,"Informative Change","Synthesis of the code analysis results and corrective actions implemented shall be described in the software product assurance reports.\nEXPECTED OUTPUT:\tSoftware product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.4.8a","Requirement","ECSS-Q-ST-80_0720175",1,"Unchanged","The code shall be put under configuration control immediately after successful unit testing."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.1a","Requirement","ECSS-Q-ST-80_0720176",1,"Informative Change","Testing shall be performed in accordance with a strategy for each testing level (i.e. unit, integration, validation against the technical specification, validation against the requirements baseline, acceptance), which includes:\n1.\tthe types of tests to be performed;\n2.\tthe tests to be performed in accordance with the plans and procedures;\n3.\tthe means and organizations to perform assurance function for testing and validation.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; PDR, CDR].","NOTE \tFor examples for item 1 are: functional, boundary, performance, security, and usability tests.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.2a","Requirement","ECSS-Q-ST-80_0720177",2,"Normative Change","Based on the dependability and safety criticality, and the security sensitivity of the software, test coverage goals for each testing level shall be agreed between the customer and the supplier and their achievement monitored by metrics: \n1.\tfor unit level testing;\n2.\tfor integration level testing;\n3.\tfor validation against the technical specification and validation against the requirements baseline.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; PDR, CDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.3a","Requirement","ECSS-Q-ST-80_0720178",1,"Normative Change","The supplier shall ensure through internal review that the test procedures and data are adequate, feasible and traceable and that they satisfy the requirements.\nEXPECTED OUTPUT:\tSoftware product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.4a","Requirement","ECSS-Q-ST-80_0720179",2,"Normative Change","Test readiness reviews shall be held before the commencement of test activities, as defined in the software development plan.\nEXPECTED OUTPUT:\tTest readiness review reports [DJF, -; TRR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.5a","Requirement","ECSS-Q-ST-80_0720180",2,"Informative Change","Test coverage shall be checked with respect to the stated goals.\nEXPECTED OUTPUT:\tSoftware product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.5b","Requirement","ECSS-Q-ST-80_0720181",1,"Unchanged","Feedback from the results of test coverage evaluation shall be continuously provided to the software developers."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.6a","Requirement","ECSS-Q-ST-80_0720182",1,"Informative Change","The supplier shall ensure that nonconformances and software problem reports detected during testing are properly documented and reported to those concerned.\nEXPECTED OUTPUT:\tNonconformance reports and software problem reports [DJF, -; CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.7a","Requirement","ECSS-Q-ST-80_0720183",1,"Informative Change","The test coverage of configurable code shall be checked to ensure that the stated requirements are met in each tested configuration.\nEXPECTED OUTPUT:\tStatement of compliance with test plans and procedures [PAF, -; CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.8a","Requirement","ECSS-Q-ST-80_0720184",1,"Informative Change","The completion of actions related to software problem reports generated during testing and validation shall be verified and recorded.\nEXPECTED OUTPUT:\tSoftware problem reports [DJF, -; SRR, PDR, CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.9a","Requirement","ECSS-Q-ST-80_0720185",1,"Unchanged","Provisions shall be made to allow witnessing of tests by the customer."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.10a","Requirement","ECSS-Q-ST-80_0720186",1,"Unchanged","Provisions shall be made to allow witnessing of tests by supplier personnel independent of the development.","NOTE \tFor example: specialist software product assurance personnel.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.11a","Requirement","ECSS-Q-ST-80_0720187",1,"Informative Change","The supplier shall ensure that:\n1.\ttests are conducted in accordance with approved test procedures and data, \n2.\tthe configuration under test is correct, \n3.\tthe tests are properly documented, and \n4.\tthe test reports are up to date and valid. \nEXPECTED OUTPUT:\tStatement of compliance with test plans and procedures [PAF, -; CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.12a","Requirement","ECSS-Q-ST-80_0720188",1,"Informative Change","The supplier shall ensure that tests are repeatable by verifying the storage and recording of tested software, support software, test environment, supporting documents and problems found.\nEXPECTED OUTPUT:\tSoftware product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.13a","Requirement","ECSS-Q-ST-80_0720189",1,"Informative Change","The supplier shall confirm in writing that the tests are successfully completed.\nEXPECTED OUTPUT:\tTesting and validation reports [DJF, -; CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.14a","Requirement","ECSS-Q-ST-80_0720190",1,"Unchanged","Review boards looking to engineering and product assurance aspects shall be convened after the completion of test phases, as defined in the software development plan."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.14b","Requirement","ECSS-Q-ST-80_0720338",1,"Created","Review boards looking to security aspects shall be convened after the completion of test phases, as defined in the software security management plan."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.15a","Requirement","ECSS-Q-ST-80_0720191",1,"Unchanged","Areas affected by any modification shall be identified and re­tested (regression testing)."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.16a","Requirement","ECSS-Q-ST-80_0720192",1,"Informative Change","In case of re­testing, all test related documentation (test procedures, data and reports) shall be updated accordingly.\nEXPECTED OUTPUT:\tUpdated test documentation [DJF, -; CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.17a","Requirement","ECSS-Q-ST-80_0720193",1,"Informative Change","The need for regression testing and additional verification of the software shall be analysed after any change of the platform hardware.\nEXPECTED OUTPUT:\tUpdated test documentation [DJF, -; CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.18a","Requirement","ECSS-Q-ST-80_0720194",1,"Informative Change","The need for regression testing and additional verification of the software shall be analysed after a change or update of any tool used to generate it.\nEXPECTED OUTPUT:\tUpdated test documentation [DJF, -; CDR, QR, AR, ORR].","NOTE \tFor example: source code or object code.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.19a","Requirement","ECSS-Q-ST-80_0720195",1,"Unchanged","Validation shall be carried out by staff who have not taken part in the design or coding of the software being validated.","NOTE \tThis can be achieved at the level of the whole software product, or on a component by component basis.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.20a","Requirement","ECSS-Q-ST-80_0720196",1,"Unchanged","Validation of the flight software against the requirement baseline on the flight equipment model shall be performed on a software version without any patch. "]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.21a","Requirement","ECSS-Q-ST-80_0720197",1,"Unchanged","The supplier shall review the test documentation to ensure that it is up to date and organized to facilitate its reuse for maintenance."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.22a","Requirement","ECSS-Q-ST-80_0720198",1,"Informative Change","Tests shall be organized as activities in their own right in terms of planning, resources and team composition. \nEXPECTED OUTPUT:\tTest and validation documentation [DJF, SValP; PDR], [DJF, SUITP; PDR, CDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.23a","Requirement","ECSS-Q-ST-80_0720199",1,"Informative Change","The necessary resources for testing shall be identified early in the life cycle, taking into account the operating and maintenance requirements. \nEXPECTED OUTPUT:\tTest and validation documentation [DJF, SValP; PDR], [DJF, SUITP; PDR, CDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.24a","Requirement","ECSS-Q-ST-80_0720200",1,"Informative Change","Test tool development or acquisition (hardware and software) shall be planned for in the overall project plan.\nEXPECTED OUTPUT:\tTest and validation documentation [DJF, SValP; PDR], [DJF, SUITP; PDR, CDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.25a","Requirement","ECSS-Q-ST-80_0720201",1,"Informative Change","The supplier shall establish and review the test procedures and data before starting testing activities and also document the constraints of the tests concerning physical, performance, functional, controllability and observability limitations.\nEXPECTED OUTPUT:\tTest and validation documentation [DJF, SValP; PDR], [DJF, SVS; CDR, QR, AR], [DJF, SUITP; PDR, CDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.26a","Requirement","ECSS-Q-ST-80_0720202",1,"Unchanged","Before offering the product for delivery and customer acceptance, the supplier shall validate its operation as a complete product, under conditions similar to the application environment as specified in the requirements baseline."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.27a","Requirement","ECSS-Q-ST-80_0720203",1,"Informative Change","When testing under the operational environment is performed, the following concerns shall be addressed:\n1.\tthe features to be tested in the operational environment;\n2.\tthe specific responsibilities of the supplier and customer for carrying out and evaluating the test;\n3.\trestoration of the previous operational environment (after test).\nEXPECTED OUTPUT:\tTest and validation documentation [DJF, -; AR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.28a","Requirement","ECSS-Q-ST-80_0720204",1,"Informative Change","Independent software validation shall be performed by a third party.","NOTE \tThis requirement is applicable where the risks associated with the project justify the costs involved. The customer can consider a less rigorous level of independence, e.g. an independent team in the same organization.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.28b","Requirement","ECSS-Q-ST-80_0720339",1,"Created","Independent software validation shall be performed in addition to, and not fully or partly replace, validation activities to be carried out by the supplier in accordance with ECSS-E-ST-40, clause 5.6.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. ISVV plan [DJF, -; SRR, PDR];\nb. ISVV report [DJF, -; PDR, CDR, QR, AR].","NOTE \tGuidance on ISVV purpose, scope, and activities is provided in CSW-ESAISVV-2022-GBK-02897.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.29a","Requirement","ECSS-Q-ST-80_0720205",1,"Informative Change","The validation shall include testing in the different configurations possible or in a representative set of them when it is evident that the number of possible configurations is too high to allow validation in all of them.\nEXPECTED OUTPUT:\tTest and validation documentation [DJF, SValP; PDR], [DJF, SVS; CDR, QR, AR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.30a","Requirement","ECSS-Q-ST-80_0720206",1,"Informative Change","Software containing deactivated code shall be validated specifically to ensure that the deactivated code cannot be activated or that its accidental activation cannot harm the operation of the system.\nEXPECTED OUTPUT:\tTesting and validation reports [DJF, -; CDR, QR, AR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.31a","Requirement","ECSS-Q-ST-80_0720207",1,"Informative Change","Software containing configurable code shall be validated specifically to ensure that unintended configuration cannot be activated at run time or included during code generation.\nEXPECTED OUTPUT:\tTesting and validation reports [DJF, -; CDR, QR, AR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.32a","Requirement","ECSS-Q-ST-80_0720208",1,"Informative Change","Activities for the validation of the quality requirements shall be specified in the definition of the validation specification. \nEXPECTED OUTPUT:\tSoftware validation specification [DJF, SVS; CDR, QR, AR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.5.33a","Requirement","ECSS-Q-ST-80_0720340",1,"Created","The software validation control information, as specified in clause 5.6.5 of ECSS-E-ST-40, shall be reviewed by the supplier and made available to the customer at milestone reviews.\nEXPECTED OUTPUT:\tSoftware validation control information [DJF, -; CDR, QR, AR].","NOTE \tThis information is expected to be provided in electronic format.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.6.1a","Requirement","ECSS-Q-ST-80_0720341",1,"Created","The Delivery Review Board convened for software deliveries, as specified in clause 5.3.5.3 of ECSS-E-ST-40, shall include a representative from the software product assurance and the software engineering organizations."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.6.1b","Requirement","ECSS-Q-ST-80_0720342",1,"Created","The software product assurance reporting to be provided to the Delivery Review Board, including product metrics measurement results, shall be defined based on delivery's purpose and scope."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.6.2a","Requirement","ECSS-Q-ST-80_0720209",2,"Normative Change","The roles, responsibilities and obligations of the supplier and customer during installation shall be established.\nEXPECTED OUTPUT:\tInstallation procedure [DDF, SCF; AR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.6.3a","Requirement","ECSS-Q-ST-80_0720343",1,"Created","The customer shall verify that the executable code was regenerated from configuration managed source code components and installed in accordance with predefined procedures on the target environment."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.6.4a","Requirement","ECSS-Q-ST-80_0720210",1,"Unchanged","The installation shall be performed in accordance with the installation procedure."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.7.1a","Requirement","ECSS-Q-ST-80_0720211",1,"Informative Change","The customer shall establish an acceptance test plan specifying the intended acceptance tests including specific tests suited to the target environment (see ECSS-E-ST-40 clause 5.7.3.1).\nEXPECTED OUTPUT:\tAcceptance test plan [DJF, -; QR, AR].","NOTE\t1\tThe acceptance tests can be partly made up of tests used during previous test activities.\nNOTE\t2\tThe acceptance test plan takes into account the requirement for operational demonstration, either as part of acceptance or after acceptance.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.7.1b","Requirement","ECSS-Q-ST-80_0720344",1,"Created","The customer shall confirm whether the residual security risks are acceptable. \nEXPECTED OUTPUT:\tJoint review report [DJF, -; AR].","NOTE \tThe confirmation could be based on acceptance testing and other software analysis techniques: for example, analysis and penetration testing.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.7.2a","Requirement","ECSS-Q-ST-80_0720212",1,"Unchanged","The customer shall ensure that the acceptance tests are performed in accordance with the approved acceptance test plan (see ECSS-E-ST-40 clause 5.7.3.2)."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.7.3a","Requirement","ECSS-Q-ST-80_0720213",1,"Unchanged","Before the software is presented for customer acceptance, the supplier shall ensure that:\n1.\tthe delivered software complies with the contractual requirements (including any specified content of the software acceptance data package);\n2.\tthe source and object code supplied correspond to each other;\n3.\tall agreed changes are implemented;\n4.\tall nonconformances are either resolved or declared."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.7.4a","Requirement","ECSS-Q-ST-80_0720214",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.7.5a","Requirement","ECSS-Q-ST-80_0720215",1,"Informative Change","Any discovered problems shall be documented in nonconformance reports.\nEXPECTED OUTPUT:\tNonconformance reports [DJF, -; AR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.7.6a","Requirement","ECSS-Q-ST-80_0720216",1,"Informative Change","On completion of the acceptance tests, a report shall be drawn up and be signed by the supplier’s representatives, the customer’s representatives, the software quality engineers of both parties and the representative of the organization charged with the maintenance of the software product.\nEXPECTED OUTPUT:\tAcceptance test report [DJF, -; AR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.7.7a","Requirement","ECSS-Q-ST-80_0720217",1,"Informative Change","The customer shall certify conformance to the procedures and state the conclusion concerning the test result for the software product under test (accepted, conditionally accepted, rejected).\nEXPECTED OUTPUT:\tAcceptance test report [DJF, -; AR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.8.1a","Requirement","ECSS-Q-ST-80_0720218",1,"Informative Change","During operations, the quality of the mission products related to software shall be agreed with the customer and users.\nEXPECTED OUTPUT:\tSoftware operation support plan [OP, -; ORR].","NOTE \tQuality of mission products can include parameters such as: error­free data, availability of data and permissible outages; permissible information degradation.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.8.2a","Requirement","ECSS-Q-ST-80_0720219",1,"Informative Change","During the demonstration that the software conforms to the operational requirements, the following shall be covered as a minimum:\n1.\tavailability and maintainability of the host system (including reboot after maintenance interventions);\n2.\tsafety features;\n3.\thuman-computer interface;\n4.\toperating procedures;\n5.\tability to meet the mission product quality requirements.\nEXPECTED OUTPUT:\tValidation of the operational requirements [PAF, -; ORR].","NOTE \tOperating procedures can include specific security operating procedures (SECOPS).\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.8.3a","Requirement","ECSS-Q-ST-80_0720220",1,"Informative Change","The product assurance plan for system operations shall include consideration of software.\nEXPECTED OUTPUT:\tInput to product assurance plan for systems operation [PAF, -; ORR]"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.9.1a","Requirement","ECSS-Q-ST-80_0720221",1,"Informative Change","The organization responsible for maintenance shall be identified to allow a smooth transition into the operations and maintenance.\nEXPECTED OUTPUT:\tMaintenance plan [MF, -; QR, AR, ORR].","NOTE \tAn organization, with representatives from both supplier and customer, can be set up to support the maintenance activities. Attention is drawn to the importance of the flexibility of this organization to cope with the unexpected occurrence of problems and the identification of facilities and resources to be used for the maintenance activities.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.9.2a","Requirement","ECSS-Q-ST-80_0720222",2,"Normative Change","The maintenance organization shall specify the assurance, verification, validation and security analysis activities applicable to maintenance interventions.\nEXPECTED OUTPUT:\tMaintenance plan [MF, -; QR, AR, ORR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.9.3a","Requirement","ECSS-Q-ST-80_0720223",1,"Unchanged","The maintenance plans shall be verified against specified requirements for maintenance of the software product.","NOTE \tThe maintenance plans and procedures can address corrective, improving, adaptive and preventive maintenance, differentiating between “routine” and “emergency” maintenance activities.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.9.4a","Requirement","ECSS-Q-ST-80_0720224",2,"Normative Change","The maintenance plans and procedures shall include the following as a minimum:\n1.\tscope of maintenance;\n2.\tidentification of the first version of the software product for which maintenance is to be done;\n3.\tsupport organization;\n4.\tmaintenance life cycle;\n5.\tmaintenance activities;\n6.\tquality measures to be applied during the maintenance;\n7.\tsecurity measures to be applied during the maintenance.\n8.\tmaintenance records and reports.\nEXPECTED OUTPUT:\tMaintenance plan [MF, -; QR, AR, ORR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.9.5a","Requirement","ECSS-Q-ST-80_0720225",1,"Informative Change","Rules for the submission of maintenance reports shall be established and agreed as part of the maintenance plan.\nEXPECTED OUTPUT:\tMaintenance plan [MF, -; QR, AR, ORR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.9.6a","Requirement","ECSS-Q-ST-80_0720226",1,"Informative Change","All maintenance activities shall be logged in predefined formats and retained. \nEXPECTED OUTPUT:\tMaintenance records [MF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","6.3.9.7a","Requirement","ECSS-Q-ST-80_0720227",2,"Normative Change","Maintenance records shall be established for each software product, including, as a minimum, the following information,:\n1.\tlist of requests for assistance or problem reports that have been received and the current status of each;\n2.\tsecurity related aspects of requests for assistance or problem reports and the current status of each;\n3.\torganization responsible for responding to requests for assistance or implementing the appropriate corrective actions;\n4.\tpriorities assigned to the corrective actions;\n5.\tresults of the corrective actions;\n6.\tstatistical data on failure occurrences and maintenance activities.\nEXPECTED OUTPUT:\tMaintenance records [MF, -; -].","NOTE\t1\tThe record of the maintenance activities can be utilized for evaluation and enhancement of the software product and for improvement of the quality system itself.\nNOTE\t2\tRelated to item 2, problem reports include evidence of specific security issues (for example data leakage and presence of malware) and incident description while preserving the privacy of the case.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.1.1a","Requirement","ECSS-Q-ST-80_0720228",1,"Informative Change","The software quality requirements (including security, safety and dependability requirements) shall be derived from the requirements defined at system level.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Requirement baseline [RB, SSS; SRR];\nb. Technical specification [TS, SRS; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.1.2a","Requirement","ECSS-Q-ST-80_0720229",1,"Informative Change","Quality requirements shall be expressed in quantitative terms or constraints.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Requirement baseline [RB, SSS; SRR];\nb. Technical specification [TS, SRS; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.1.3a","Requirement","ECSS-Q-ST-80_0720230",1,"Informative Change","The supplier shall define assurance activities to ensure that the product meets the quality requirements as specified in the technical specification.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.1.4a","Requirement","ECSS-Q-ST-80_0720231",1,"Informative Change","In order to verify the implementation of the product quality requirements, the supplier shall define a metrication programme based on the identified quality model (see clause 5.2.7), specifying:\n1.\tthe metrics to be collected and stored;\n2.\tthe means to collect metrics (measurements);\n3.\tthe target values, with reference to the product quality requirements;\n4.\tthe analyses to be performed on the collected metrics, including the ones to derive:\n(a)\tdescriptive statistics;\n(b)\ttrend analysis (such as trends in software problems).\n5.\thow the results of the analyses performed on the collected metrics are fed back to the development team and used to identify corrective actions;\n6.\tthe schedule of metrics collection, storing, analysis and reporting, with reference to the whole software life cycle.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; SRR, PDR].","NOTE\t1\tGuidance for software metrication programme implementation can be found in ECSS-Q-HB-80-04. \nNOTE\t2\tExample to item 4(a): the number of units at each level of complexity.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.1.5a","Requirement","ECSS-Q-ST-80_0720232",1,"Informative Change","The following basic products metrics shall be used:\n1.\tsize (code);\n2.\tcomplexity (design, code);\n3.\tfault density and failure intensity;\n4.\ttest coverage;\n5.\tnumber of failures.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.1.6a","Requirement","ECSS-Q-ST-80_0720233",1,"Informative Change","The results of metrics collection and analysis shall be included in the software product assurance reports, in order to provide the customer with an insight into the level of quality obtained.\nEXPECTED OUTPUT:\tSoftware product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.1.7a","Requirement","ECSS-Q-ST-80_0720234",1,"Informative Change","Numerical accuracy shall be estimated and verified.\nEXPECTED OUTPUT:\tNumerical accuracy analysis [DJF, SVR; PDR, CDR, QR]. "]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.1.8a","Requirement","ECSS-Q-ST-80_0720235",1,"Informative Change","The supplier shall define the organization and means implemented to collect and analyse data required for the study of software maturity.\nEXPECTED OUTPUT:\tSoftware product assurance reports [PAF, -; -].","NOTE \tFor example: failures, corrections, duration of runs.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.2.1.1a","Requirement","ECSS-Q-ST-80_0720236",1,"Informative Change","The software quality requirements shall be documented in the requirements baseline and technical specification.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Requirement baseline [RB, SSS; SRR];\nb. Technical specification [TS, SRS; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.2.1.2a","Requirement","ECSS-Q-ST-80_0720237",1,"Unchanged","The software requirements shall be: \n1.\tcorrect;\n2.\tunambiguous;\n3.\tcomplete;\n4.\tconsistent;\n5.\tverifiable;\n6.\ttraceable."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.2.1.3a","Requirement","ECSS-Q-ST-80_0720238",1,"Informative Change","For each requirement the method for verification and validation shall be specified.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Requirement baseline [RB, SSS; SRR];\nb. Technical specification [TS, SRS; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.2.2.1a","Requirement","ECSS-Q-ST-80_0720239",1,"Unchanged","The software design shall meet the non-functional requirements as documented in the technical specification."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.2.2.2a","Requirement","ECSS-Q-ST-80_0720240",1,"Unchanged","The software shall be designed to facilitate testing."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.2.2.3a","Requirement","ECSS-Q-ST-80_0720241",1,"Informative Change","Software with a long planned lifetime shall be designed with minimum dependency on the operating system and the hardware, in order to aid portability.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Software product assurance plan [PAF, SPAP; SRR, PDR];\nb. Justification of design choices [DDF, SDD; PDR, CDR].","NOTE \tThis requirement is applicable to situations where the software lifetime can lead to the obsolescence and non-availability of the original operating system and/or hardware, thereby jeopardizing the maintainability of the software.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.2.3.1a","Requirement","ECSS-Q-ST-80_0720242",1,"Unchanged","Detailed test and validation documentation (data, procedures and expected results) defined in the ECSS-E-ST-40 DJF shall be consistent with the defined test and validation strategy (see clause 6.3.5 and ECSS-E-ST-40 clauses 5.5.3, 5.5.4, 5.6 and 5.8)."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.2.3.2a","Requirement","ECSS-Q-ST-80_0720243",1,"Unchanged","The test documentation shall cover the test environment, tools and test software, personnel required and associated training requirements."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.2.3.3a","Requirement","ECSS-Q-ST-80_0720244",1,"Unchanged","The criteria for completion of each test and any contingency steps shall be specified."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.2.3.4a","Requirement","ECSS-Q-ST-80_0720245",1,"Unchanged","Test procedures, data and expected results shall be specified."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.2.3.5a","Requirement","ECSS-Q-ST-80_0720246",1,"Unchanged","The hardware and software configuration shall be identified and documented as part of the test documentation."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.2.3.6a","Requirement","ECSS-Q-ST-80_0720247",1,"Informative Change","For any requirements not covered by testing a verification report shall be drawn up documenting or referring to the verification activities performed.\nEXPECTED OUTPUT:\tSoftware verification report [DJF, SVR; CDR, QR, AR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.3.1a","Requirement","ECSS-Q-ST-80_0720248",1,"Unchanged","For the development of software intended for reuse, ECSS-E-ST-40 clauses 5.2.4.7 and 5.4.3.6 shall apply."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.3.2a","Requirement","ECSS-Q-ST-80_0720249",1,"Unchanged","The information related to the components developed for reuse shall be separated from the others in the technical specification, design justification file, design definition file and product assurance file. "]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.3.3a","Requirement","ECSS-Q-ST-80_0720250",1,"Unchanged","The information related to components developed for reuse in the technical specification, the design justification file, the design definition file and the product assurance file shall be self-contained."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.3.4a","Requirement","ECSS-Q-ST-80_0720251",1,"Informative Change","The technical specification of components developed for reuse shall include requirements for maintainability, portability and verification of those components.\nEXPECTED OUTPUT:\tTechnical specification for reusable components [TS, -; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.3.5a","Requirement","ECSS-Q-ST-80_0720252",2,"Informative Change","The configuration management system shall include provisions for handling specific aspects of software developed for reuse, such as:\n1.\tlonger lifetime of the components developed for reuse compared to the other components of the project;\n2.\tevolution or change of the development environment for the next project that intends to use the components;\n3.\ttransfer of the configuration and documentation management information to the next project reusing the software.\nEXPECTED OUTPUT:\tSoftware configuration management plan [MGT, SCMP; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.3.6a","Requirement","ECSS-Q-ST-80_0720253",1,"Informative Change","Where the components developed for reuse are developed to be reusable on different platforms, the testing of the software shall be performed on all those platforms. \nEXPECTED OUTPUT:\tVerification and validation documentation for reusable components [DJF, -; CDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.3.7a","Requirement","ECSS-Q-ST-80_0720254",1,"Informative Change","The supplier shall provide a certificate of conformance that the tests have been successfully completed on all the relevant platforms.\nEXPECTED OUTPUT:\tVerification and validation documentation for reusable components [DJF, -; CDR].","NOTE \tIn case not all platforms are available, the certificate of conformance states the limitations of the validation performed.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.4.1a","Requirement","ECSS-Q-ST-80_0720255",2,"Informative Change","The subcontracting and procurement of hardware shall be carried out according to the requirements of ECSS-Q-ST-20 clause 5.4.\nEXPECTED OUTPUT:\tThe following outputs are expected:\na. Justification of selection of operational ground equipment [DJF, -; SRR, PDR];\nb. Receiving inspection reports [PAF, -; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.4.2a","Requirement","ECSS-Q-ST-80_0720256",1,"Informative Change","The procurement of support services to be used in operational phases shall be justified as covering service level agreements, quality of services and escalation procedures, as needed for system exploitation and maintenance.\nEXPECTED OUTPUT:\tJustification of selection of operational support services [DJF, -; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.4.3a","Requirement","ECSS-Q-ST-80_0720257",1,"Informative Change","The choice of procured hardware and services shall address the constraints associated with both the development and the actual use of the software.\nEXPECTED OUTPUT:\tJustification of selection of operational ground equipment [DJF, -; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.4.4a","Requirement","ECSS-Q-ST-80_0720258",2,"Normative Change","The ground computer equipment and supporting services for implementing the final system shall be selected according to the project requirements regarding:\n1.\tperformance;\n2.\tmaintenance;\n3.\tdurability and technical consistency with the operational equipment;\n4.\tthe assessment of the product with respect to requirements, including the criticality category;\n5.\tthe assessment of the product with respect to security sensitivity of the product;\n6.\tcompliance with applicable organizational, national or international standards, security regulations, policies or directives;\n7.\tthe available support documentation;\n8.\tthe acceptance and warranty conditions;\n9.\tthe conditions of installation, preparation, training and use;\n10.\tthe maintenance conditions, including the possibilities of evolutions;\n11.\tcopyright constraints;\n12.\tavailability;\n13.\tcompatibility;\n14.\tsite operational constraints.\nEXPECTED OUTPUT:\tJustification of selection of operational ground equipment [DJF, -; SRR, PDR].","NOTE \tto item 5: The security sensitivity of the product is determined by the security analysis.\n"]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.4.5a","Requirement","ECSS-Q-ST-80_0720259",1,"Unchanged","Taking account of the provider’s maintenance and product policy, it shall be ensured that the hardware and support services can be maintained throughout the specified life of the software product within the operational constraints."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.5.1a","Requirement","ECSS-Q-ST-80_0720260",2,"Normative Change","The supplier shall establish procedures for device programming and duplication of programmed services.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.5.2a","Requirement","ECSS-Q-ST-80_0720261",2,"Normative Change","The programmed device shall be indelibly marked to allow the identification (by reference) of the hardware component and of the software component."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.5.2b","Requirement","ECSS-Q-ST-80_0720345",1,"Created","Where protective security marking is required, devices and all software configuration items shall be marked accordingly.\nEXPECTED OUTPUT:\tSoftware product assurance plan [PAF, SPAP; PDR]."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","7.5.3a","Requirement","ECSS-Q-ST-80_0720262",2,"Normative Change","The supplier shall ensure that the programming equipment is calibrated."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<1>a","Requirement","ECSS-Q-ST-80_0720263",1,"Unchanged","The SPAP shall contain a description of the purpose, objective, content and the reason prompting its preparation."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<2>a","Requirement","ECSS-Q-ST-80_0720264",1,"Unchanged","The SPAP shall list the applicable and reference documents to support the generation of the document."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<3>a","Requirement","ECSS-Q-ST-80_0720265",1,"Unchanged","The SPAP shall include any additional terms, definition or abbreviated terms used."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<4>a","Requirement","ECSS-Q-ST-80_0720266",1,"Unchanged","The SPAP shall include or refer to a description of the system and software products being developed."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<5.1>a","Requirement","ECSS-Q-ST-80_0720267",1,"Unchanged","The SPAP shall describe the organization of software product assurance activities, including responsibility, authority and the interrelation of personnel who manage, perform and verify work affecting software quality."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<5.1>b","Requirement","ECSS-Q-ST-80_0720268",1,"Unchanged","The following topics shall be included:\n1.\torganizational structure;\n2.\tinterfaces of each organisation, either external or internal, involved in the project; \n3.\trelationship to the system level product assurance and safety;\n4.\tindependence of the software product assurance function;\n5.\tdelegation of software product assurance tasks to a lower level supplier, if any."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<5.2>a","Requirement","ECSS-Q-ST-80_0720269",1,"Unchanged","The SPAP shall describe the responsibilities of the software product assurance function."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<5.3>a","Requirement","ECSS-Q-ST-80_0720270",1,"Unchanged","The SPAP shall describe the resources to be used to perform the software product assurance function."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<5.3>b","Requirement","ECSS-Q-ST-80_0720271",1,"Unchanged","The description in B.2.1<5.3>a. shall include human resources and skills, hardware and software tools."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<5.4>a","Requirement","ECSS-Q-ST-80_0720272",1,"Unchanged","The SPAP shall describe the reporting to be performed by software product assurance."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<5.5>a","Requirement","ECSS-Q-ST-80_0720273",1,"Unchanged","The SPAP shall describe the quality models applicable to the project and how they are used to specify the quality requirements."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<5.6>a","Requirement","ECSS-Q-ST-80_0720274",1,"Unchanged","The SPAP shall describe the contribution of the software product assurance function to the project risk management."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<5.7>a","Requirement","ECSS-Q-ST-80_0720275",1,"Unchanged","The SPAP shall describe the contribution of the software product assurance function to the next level suppliers selection and control."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<5.8>a","Requirement","ECSS-Q-ST-80_0720276",1,"Unchanged","The SPAP shall describe the methods and tools used for all the activities of the development cycle, and their level of maturity."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<5.9>a","Requirement","ECSS-Q-ST-80_0720277",2,"Unchanged","The SPAP shall state the scope and objectives of process assessment."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<5.9>b","Requirement","ECSS-Q-ST-80_0720278",2,"Unchanged","The SPAP shall describe the methods and tools to be used for process assessment and improvement."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<5.10>a","Requirement","ECSS-Q-ST-80_0720279",1,"Unchanged","The SPAP shall specify the quality measures related to the operations and maintenance processes (alternatively, a separate SPAP is produced)."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<6.1>a","Requirement","ECSS-Q-ST-80_0720280",1,"Unchanged","The SPAP shall refer to the software development cycle description in the software development plan. "]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<6.1>b","Requirement","ECSS-Q-ST-80_0720281",1,"Unchanged","If not covered in the software development plan, the life cycle shall be described."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<6.1>c","Requirement","ECSS-Q-ST-80_0720282",1,"Unchanged","The life cycle shall include a milestone immediately before the starting of the software validation."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<6.2>a","Requirement","ECSS-Q-ST-80_0720283",1,"Unchanged","The SPAP shall describe all plans to be produced and used in the project."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<6.2>b","Requirement","ECSS-Q-ST-80_0720284",1,"Unchanged","The relationship between the project plans and a timely planning for their preparation and update shall be described."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<6.3>a","Requirement","ECSS-Q-ST-80_0720285",2,"Normative Change","The SPAP shall contain a description and justification of the measures to be applied for the handling of critical software, including the dependability and safety analyses to be performed and the standards applicable for critical software."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<6.4>a","Requirement","ECSS-Q-ST-80_0720346",1,"Created","The SPAP shall contain a description of and justification of the measures to be applied for handling of security related software, including the security analysis to be performed and the standards applicable to sensitive software. "]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<6.4>b","Requirement","ECSS-Q-ST-80_0720347",1,"Created","The SPAP shall contain at least a security assurance section containing at least references to the documents and section titles that capture the related security and any additional security assurance activities documented in the security file."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<6.5>a","Requirement","ECSS-Q-ST-80_0720286",1,"Unchanged","The SPAP shall describe the contribution of the software product assurance function to the proper implementation of documentation and configuration management."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<6.5>b","Requirement","ECSS-Q-ST-80_0720287",1,"Unchanged","The nonconformance control system shall be described or referenced. The point in the software life cycle from which the nonconformance procedures apply shall be specified."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<6.5>c","Requirement","ECSS-Q-ST-80_0720288",1,"Unchanged","The SPAP shall identify method and tool to protect the supplied software, a checksum-type key calculation for the delivered operational software, and a labelling method for the delivered media."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<6.6>a","Requirement","ECSS-Q-ST-80_0720289",1,"Unchanged","The SPAP shall describe the process metrics derived from the defined quality models, the means to collect, store and analyze them, and the way they are used to manage the development processes."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<6.7>a","Requirement","ECSS-Q-ST-80_0720290",1,"Unchanged","The SPAP shall describe the approach for the reuse of existing software, including delta qualification. "]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<6.8>a","Requirement","ECSS-Q-ST-80_0720291",1,"Unchanged","The following processes and activities shall be covered, taking into account the project scope and life cycle:\n1.\tsoftware requirements analysis;\n2.\tsoftware architectural design and design of software items;\n3.\tcoding;\n4.\ttesting and validation (including regression testing);\n5.\tverification;\n6.\tsoftware delivery and acceptance;\n7.\toperations and maintenance."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<6.9>a","Requirement","ECSS-Q-ST-80_0720292",1,"Unchanged","The SPAP shall describe or list by reference all procedures and standards applicable to the development of the software in the project."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<6.9>b","Requirement","ECSS-Q-ST-80_0720293",1,"Unchanged","The software product assurance measures to ensure adherence to the project procedures and standards shall be described. "]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<6.9>c","Requirement","ECSS-Q-ST-80_0720294",2,"Normative Change","The standards and procedures to be described or listed in accordance with B.2.1<6.9>a shall be as a minimum those covering the following aspects:\n1.\tproject management;\n2.\trisk management;\n3.\tconfiguration and documentation management;\n4.\tverification and validation;\n5.\trequirements engineering;\n6.\tdesign;\n7.\tcoding;\n8.\tmetrication;\n9.\tnonconformance control;\n10.\taudits;\n11.\talerts;\n12.\tprocurement;\n13.\treuse of existing software;\n14.\tuse of methods and tools;\n15.\tnumerical accuracy;\n16.\tdelivery, installation and acceptance;\n17.\toperations;\n18.\tmaintenance;\n19.\tdevice programming and marking."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<7>a","Requirement","ECSS-Q-ST-80_0720295",1,"Unchanged","The SPAP shall describe the approach taken to ensure the quality of the software product. "]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<7>b","Requirement","ECSS-Q-ST-80_0720296",1,"Unchanged","The description of the approach specified in B.2.1<7>a shall include the:\n1.\tspecification of the product metrics, their target values and the means to collect them;\n2.\tdefinition of a timely metrication programme;\n3.\tanalyses to be performed on the collected metrics;\n4.\tway the results are fed back to the development team;\n5.\tdocumentation quality requirements;\n6.\tassurance activities meant to ensure that the product meets the quality requirements."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<8>a","Requirement","ECSS-Q-ST-80_0720297",1,"Unchanged","The SPAP shall include the compliance matrix to the applicable software product assurance requirements (e.g. ECSS-Q-ST-80 clauses, as tailored by a product assurance requirements document), or provide a reference to it."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","B.2.1<8>b","Requirement","ECSS-Q-ST-80_0720298",1,"Unchanged","For each software product assurance requirement, the following information shall be provided:\n1.\trequirement identifier;\n2.\tcompliance \n(C = compliant, NC = non–compliant, NA = not applicable);\n3.\treference to the project documentation covering the requirement (e.g. section of the software product assurance plan);\n4.\tremarks."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","C.2.1<1>a","Requirement","ECSS-Q-ST-80_0720299",1,"Unchanged","The SPAMR shall contain a description of the purpose, objective, content and the reason prompting its preparation."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","C.2.1<2>a","Requirement","ECSS-Q-ST-80_0720300",1,"Unchanged","The SPAMR shall list the applicable and reference documents to support the generation of the document."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","C.2.1<3>a","Requirement","ECSS-Q-ST-80_0720301",1,"Unchanged","The SPAMR shall include any additional terms, definition or abbreviated terms used."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","C.2.1<4>a","Requirement","ECSS-Q-ST-80_0720302",1,"Unchanged","The SPAMR shall contain reporting on verification activities performed by the product assurance function, including:\n1.\treviews;\n2.\tinspections;\n3.\twalk-throughs;\n4.\treview of traceability matrices;\n5.\tdocuments reviewed."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","C.2.1<4>b","Requirement","ECSS-Q-ST-80_0720303",1,"Unchanged","The SPAMR shall contain reporting on the verification of the measures applied for the handling of critical software."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","C.2.1<5>a","Requirement","ECSS-Q-ST-80_0720304",1,"Unchanged","The SPAMR shall include or reference a justification of the suitability of the methods and tools applied in all the activities of the development cycle, including requirements analysis, software specification, design, coding, validation, testing, configuration management, verification and product assurance."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","C.2.1<5>b","Requirement","ECSS-Q-ST-80_0720305",1,"Unchanged","The SPAMR shall include reporting on the correct use of methods and tools."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","C.2.1<6>a","Requirement","ECSS-Q-ST-80_0720306",1,"Unchanged","The SPAMR shall include reporting on the adherence of software products to the applicable modelling, design and coding standards, including:\n1.\treporting on the application of measures meant to ensure that the design complexity and modularity meet the quality requirements;\n2.\treporting on design documentation w.r.t. suitability for maintenance."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","C.2.1<7>a","Requirement","ECSS-Q-ST-80_0720307",1,"Unchanged","The SPAMR shall include reporting on the collected product and process metrics, the relevant analyses performed, the corrective actions undertaken and the status of these actions."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","C.2.1<7>b","Requirement","ECSS-Q-ST-80_0720308",1,"Unchanged","The results of the software maturity analysis shall also be reported."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","C.2.1<8>a","Requirement","ECSS-Q-ST-80_0720309",1,"Unchanged","The SPAMR shall include reporting on adequacy of the testing and validation documentation (including feasibility, traceability repeatability), and on the achieved test coverage w.r.t. stated goals."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","C.2.1<9>a","Requirement","ECSS-Q-ST-80_0720310",1,"Unchanged","The SPAMR shall include reporting on the status of software problem reports and nonconformances relevant to software."]
["ECSS-Q-ST-80C Rev.2","ECSS - Current v1.0","C.2.1<10>a","Requirement","ECSS-Q-ST-80_0720311",1,"Unchanged","Whenever relevant and up-to-date information has been already delivered as part of the regular PA progress reporting, a representative summary shall be provided, together with a detailed reference to the progress report(s) containing that information."]
["ECSS-S-ST-00C Rev.1","ECSS - Current v1.0","9.2a","Requirement","ECSS-S-ST-00_1000001",1,"Unchanged","The customer shall select which ECSS Standards to make applicable and to use to establish the project/product requirements, including use of ECSS-S-ST-00-01 for terms and definitions.\n"]
["ECSS-S-ST-00C Rev.1","ECSS - Current v1.0","9.2b","Requirement","ECSS-S-ST-00_1000002",1,"Unchanged","The customer shall define, as part of the project requirements documentation (PRD), the set of requirements tailored from ECSS documents to the project specificities which are made applicable.\n"]
["ECSS-S-ST-00C Rev.1","ECSS - Current v1.0","9.2c","Requirement","ECSS-S-ST-00_1000003",1,"Unchanged","The customer shall produce, as part of the PRD, a documentation identifying the ECSS requirements applicable to the project.\n","NOTE \tAn “ECSS applicable requirements matrix” (EARM) is a recommended method for this component of the PRD.\n"]
["ECSS-S-ST-00C Rev.1","ECSS - Current v1.0","9.2d","Requirement","ECSS-S-ST-00_1000004",1,"Unchanged","The documentation identifying the requirements applicable to the project shall include following data (e.g. EARM):\n1.\tThe complete list of ECSS standards either fully or partially applicable to the project/product, including any standard (ECSS or not) made applicable via the chain of normative references;\n2.\tFor each partially applicable standard, the status of each requirement:\napplicable without modification\napplicable with modification\nnot applicable\n3.\tThe complete list of additional requirements\n4.\tFor modified and additional requirements, their complete formulation \n"]
["ECSS-S-ST-00C Rev.1","ECSS - Current v1.0","9.3a","Requirement","ECSS-S-ST-00_1000005",1,"Unchanged","The supplier shall demonstrate compliance with the PRD requirements.\n","NOTE \tAn “ECSS compliance matrix” (ECM) is a recommended method to document the demonstration of this compliance. The ECM is part of the project compliance matrix, addressing compliance to the applicable ECSS requirements (e.g. EARM).\n"]
["ECSS-S-ST-00C Rev.1","ECSS - Current v1.0","9.3b","Requirement","ECSS-S-ST-00_1000006",1,"Unchanged","The documentation identifying the compliance to ECSS requirements applicable to the project (e.g. the ECM) shall include following data:\n1.\tThe complete list of ECSS requirements applicable to the project (e.g. in the EARM).\n2.\tFor each requirement, the actual indication of compliance. When deviation is identified the justification is provided.\n"]
["ECSS-U-AS-10C Rev.2","ECSS - Current v1.0","3a","Requirement","ECSS-U-AS-10_1300001",3,"Normative Change","ISO 24113:2023, Space systems - Space debris mitigation requirements, fourth edition 2023-05 shall apply with the modifications and clarifications listed in Table 3‑1."]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.1a","Requirement","ECSS-U-ST-20_1430001",1,"Created","The PPAA shall provide to the supplier planetary protection related obligations of relevant external authorities.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.1b","Requirement","ECSS-U-ST-20_1430002",1,"Created","The supplier shall prepare a preliminary Planetary Protection Requirements document in conformance with the DRD in Annex A during the Phase A and no later than the PRR.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.1c","Requirement","ECSS-U-ST-20_1430003",1,"Created","For missions that target or encounter multiple Solar system bodies, the preliminary Planetary Protection Requirements document shall include requirements for all the protected Solar system bodies.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.1d","Requirement","ECSS-U-ST-20_1430004",1,"Created","The Planetary Protection Requirements document shall be subject to approval by the PPAA and released at the latest at SRR.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.1e","Requirement","ECSS-U-ST-20_1430005",1,"Created","The delivery of hardware and services to a third-party mission with planetary protection constraints shall be subject to approval by the PPAA.\n","NOTE \tThe customer of the mission lead of the third-part mission bears the overall planetary protection responsibility at mission level, including assigning, monitoring, reviewing and approving planetary protection categories and associated requirements.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.1f","Requirement","ECSS-U-ST-20_1430006",1,"Created","Impact of significant changes in the mission concept on the planetary protection requirements and implementation approach shall be assessed by the supplier and are subject to approval by the PPAA.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.1g","Requirement","ECSS-U-ST-20_1430007",1,"Created","The PPAA, or its designated entity, shall conduct independent verification assays on flight hardware and controlled environments, including launch site, during the course of the project at times and intervals planned and agreed with the supplier.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.2.1a","Requirement","ECSS-U-ST-20_1430008",1,"Created","Except as specified in 5.3.2.1d, all flight hardware subject to planetary protection constraints shall be assembled and maintained until and including launch in ISO class 8 cleanrooms “in operation”, or better, as specified in ECSS-Q-ST-70-01.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.2.2a","Requirement","ECSS-U-ST-20_1430009",1,"Created","A probability of impact analysis on protected Solar system bodies shall be performed and a report delivered for customer and PPAA review.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.2.2b","Requirement","ECSS-U-ST-20_1430010",1,"Created","The probability of impact analysis specified in 5.2.2a shall include:\n1.\tSingle and multiple pass analysis;\n2.\tHardware, software and operational reliability;\n3.\tMeteoroid impacts and effects on spacecraft reliability;\n(a)\tMeteoroid model (e.g., IMEM 1.1) and parameters (fluence, directionality, velocity, density and margins) as defined in the project applicable environmental specifications\n(b)\tDamage equations in IADC-WD-00-03 for the damage assessment\n4.\tSpacecraft state including location, and velocity vector;\n5.\tManoeuvre and planet and satellite ephemeris uncertainty;\n6.\tStochastic variability of the atmospheric density with the amplitude of the Solar cycle estimated for the mission and sun epoch.\n","NOTE \t1\tDifferent meteoroid models are used depending on the mission profile; dedicated models are currently developed for the Jovian system.\nNOTE \t2\tRequirements that need a probability of impact analysis to demonstrate compliance are described in 5.3.2.1d, 5.3.2.1e.1, and 5.3.3.1b.4.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.2.3a","Requirement","ECSS-U-ST-20_1430011",1,"Created","Except where numerical requirements are otherwise specified in this document, the probability of contaminating a Solar system body with viable terrestrial organisms shall be ≤ 1x10-3 over a period of 50 years after the arrival of the mission at the protected Solar system body.\n","NOTE \tDescription how compliance to this requirement will be demonstrated needs to be described in the Planetary Protection Plan DRD in B.2.1a.3.(e).\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.1a","Requirement","ECSS-U-ST-20_1430012",1,"Created","An organic materials inventory of bulk constituents present in quantities above the limit agreed with the PPAA shall be provided by the project in conformance with DRD in Annex H.\n","NOTE \tThis also applies to missions not going to the Moon but having a final disposition that would end up on the Moon.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.1a","Requirement","ECSS-U-ST-20_1430013",1,"Created","An organic materials inventory of bulk constituents present on the spacecraft in quantities ≥1 kg shall be provided by the supplier in conformance with DRD in Annex H.\n","NOTE \tThis requirement is not applicable in case requirement 5.3.2.1e.1 is met.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.1b","Requirement","ECSS-U-ST-20_1430014",1,"Created","A 50 gram sample for each organic material used on the spacecraft in quantities ≥25 kg shall be provided by the supplier and stored by the customer under controlled conditions for 50 years after launch.\n","NOTE \tThis requirement is not applicable in case requirement  5.3.2.1e.1 is met.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.1c","Requirement","ECSS-U-ST-20_1430015",1,"Created","Compliance to all bioburden requirements shall be verified pre-launch.\n","NOTE \tThis verification is usually done on last physical access of the flight hardware or hardware elements, i.e., at delivery of flight hardware to next level contractor, delivery to launch site, and at the launch site prior to fairing closure.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.1d","Requirement","ECSS-U-ST-20_1430016",1,"Created","The probability of impact on Mars by any element not assembled and maintained in at least ISO class 8 conditions shall be ≤ 1x10-4 for the first 50 years after launch for nominal and off-nominal flight conditions.\n","NOTE \tExamples are upper stages.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.1e","Requirement","ECSS-U-ST-20_1430017",1,"Created","One of the following conditions shall be met:\n1.\tThe probability of impact on Mars by any part of a spacecraft assembled and maintained in ISO class 8 conditions, or better, is ≤ 1x10-2 for the first 20 years after launch, and ≤ 5x10-2 for the time period from 20 to 50 years after launch for nominal and off-nominal flight conditions.\n2.\tThe total bioburden of the spacecraft on Mars, including surface, mated, and encapsulated bioburden, is ≤ 5x105 bacterial spores.\n","NOTE \tThis requirement is also applicable for fly-by and gravity assist manoeuvres.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.2.2a","Requirement","ECSS-U-ST-20_1430018",1,"Created","The bioburden of the landed system on Mars shall be ≤ 3x105 bacterial spores on exposed internal and external surfaces.\n","NOTE \tAttention – for bioburden allocations to hardware and payload suppliers take into account re-contamination during different on-ground phases (e.g., testing at sub-system and system level, launch).\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.2.2b","Requirement","ECSS-U-ST-20_1430019",1,"Created","The average bioburden of the landed system on Mars shall be ≤ 300 bacterial spores/m2 on exposed internal and external surfaces.\n","NOTE \t1\tAttention – for bioburden allocations to hardware and payload suppliers take into account re-contamination during different on ground phases (e.g., testing at sub-system and system level, launch).\nNOTE \t2\tAttention – for large spacecraft systems the average bioburden to meet requirement 5.3.2.2.2a needs to be much lower than 300 bacterial spore/m2.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.2.2c","Requirement","ECSS-U-ST-20_1430020",1,"Created","The supplier shall provide an analysis or assessment whether the spacecraft during nominal and off-nominal conditions has the potential to modify the local martian environment in a way that can create a Mars special region.\n","NOTE \tSuch an analysis or assessment is in particular important for spacecraft using radioisotope heat sources targeting areas with surface or sub-surface water ice.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.2.2d","Requirement","ECSS-U-ST-20_1430021",1,"Created","Planned 3-sigma pre-launch landing ellipses shall be evaluated and documented on a case-by-case basis as part of the landing site selection process to determine whether the mission can land or come within contamination range of areas or volumes meeting the parameter definition for Mars Special Regions or impinge on already described features that can be treated as Mars Special Regions. \n","NOTE \tThis means at least no areas or volumes meeting the parameter definition for Mars Special Regions or already described features that can be treated as Mars Special Regions can be within the 3-sigma landing ellipse.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.2.2e","Requirement","ECSS-U-ST-20_1430022",1,"Created","The evaluations specified in 5.3.2.2.2c and 5.3.2.2.2d shall be based on the latest scientific evidence and include an assessment of the extent to which the temperature and water activity values specified for Mars Special Regions are separated in time. \n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.2.2f","Requirement","ECSS-U-ST-20_1430023",1,"Created","The evaluation specified in 5.3.2.2.2d shall be updated during the mission whenever new evidence indicates that the landing ellipse and the operational environment contain, or are in contamination range of areas or volumes meeting the parameter definition for Mars Special Regions.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.2.3a","Requirement","ECSS-U-ST-20_1430024",1,"Created","For surface mission with life detection one of the following conditions shall be met:\n1.\tThe bioburden of the surface system on Mars is ≤ 30 bacterial spores on exposed internal and external surfaces, or at a contamination level driven by the nature and sensitivity of the particular life-detection investigations.\n2.\tThe average bioburden of the subsystems that are involved in the acquisition, delivery, and analysis of samples used for life-detection investigations is either:\n(a)\t≤ 0,03 bacterial spores/m2, or\n(b)\tat a contamination level driven by the nature and sensitivity of the particular life-detection investigations.\n","NOTE \tThe contamination level driven by the particular life-detection investigation needs to be described in the Planetary Protection Plan DRR, Annex B.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.2.3b","Requirement","ECSS-U-ST-20_1430025",1,"Created","The specific contamination level driven by the nature and sensitivity of the particular life-detection investigation described in 5.3.2.2.3a.1 and 5.3.2.2.3a.2(b) shall be subject to review and approval by the PPAA.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.2.3c","Requirement","ECSS-U-ST-20_1430026",1,"Created","Recontamination prevention of the subsystems specified in 5.3.2.2.3a.2 and the samples to be analysed shall be in place until the end of the life-detection investigations.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.2.4a","Requirement","ECSS-U-ST-20_1430027",1,"Created","If a Mars special region is within the 3-sigma landing ellipse, the bioburden of the entire surface system on Mars shall be ≤ 30 bacterial spores on exposed internal and external surfaces.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.2.4b","Requirement","ECSS-U-ST-20_1430028",1,"Created","If a Mars special region is accessed through horizontal or vertical mobility, one of the following conditions shall be met:\n1.\tThe bioburden of the entire surface system on Mars is ≤ 30 bacterial spores on exposed internal and external surfaces.\n2.\tThe subsystems which directly contact the Mars special region are sterilized to levels specified in 5.3.2.2.4b.1, and a method of preventing their recontamination prior to accessing the Mars special region is in place.\n","NOTE \tExample of accessing Mars special regions are by roving (horizontal mobility) or by drilling (vertical mobility).\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.2.4c","Requirement","ECSS-U-ST-20_1430029",1,"Created","If an off-nominal condition can cause a high probability of inadvertent biological contamination of a Mars special region by the spacecraft the bioburden shall be the following:\n1.\tThe bioburden of the entire surface system on Mars is ≤ 30 bacterial spores on exposed internal and external surfaces, and \n2.\tThe total surface, mated, and encapsulated bioburden level on Mars is ≤ 30 + 1,5 x 104 bacterial spores.\n","NOTE \tExample for off-nominal condition is a hard landing.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.3a","Requirement","ECSS-U-ST-20_1430030",1,"Created","Requirements in clause 5.3.2.2.3 shall be applied to the outbound leg of a Mars sample return mission.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.3b","Requirement","ECSS-U-ST-20_1430031",1,"Created","The severity of potential consequences of releasing unsterilized material from Mars and flight hardware that has been exposed to unsterilized material from Mars into the terrestrial environment shall be categorised as catastrophic in accordance with ECSS-Q-ST-40.\n","NOTE \tThe categorization of this severity level is not because a catastrophic consequence is expected but only following the precautionary principle due to the large number of unknowns.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.3c","Requirement","ECSS-U-ST-20_1430032",1,"Created","Safety critical functions as defined in 3.2.19 shall be treated as severity function criticality level 1 in accordance with ECSS-Q-ST-40.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.3d","Requirement","ECSS-U-ST-20_1430033",1,"Created","The probability that a single unsterilized martian particle of ≥ 0,01 μm in diameter is released into the terrestrial environment shall be ≤ 1x10-6 for the first 100 years after launch from Mars.\n","NOTE \t1\tRational for this requirement is to “break the chain of contact” between Mars and Earth.\nNOTE \t2\tSource and context for numerical values in [5].\nNOTE \t3\tThe term ‘particle’ includes material from Mars and flight hardware exposed to material from Mars.\nNOTE \t4\tIf the size requirement of 0,01 μm cannot be met without decreasing the overall level of assurance for the non-release of such a particle, the release of a single unsterilised particle of up to 0,05 μm can be considered as a potentially tolerable systems-level adjustment, assuming that it has been demonstrated that this size is the lowest achievable at a reasonable cost (BAT approach) and it has been independently reviewed.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.3e","Requirement","ECSS-U-ST-20_1430034",1,"Created","A quantitative PRA shall be conducted as part of evaluating the risk of releasing unsterilized material from Mars and flight hardware that has been exposed to unsterilized material from Mars into the terrestrial environment.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.2.3f","Requirement","ECSS-U-ST-20_1430035",1,"Created","No unsterilised portion of the materials returned from Mars shall be released from containment unless approved by the PPAA.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.3.1a","Requirement","ECSS-U-ST-20_1430036",1,"Created","The probability of inadvertent contamination of a subsurface ocean by viable terrestrial organisms shall be ≤ 1 x 10-4 per mission.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.3.1b","Requirement","ECSS-U-ST-20_1430037",1,"Created","The calculation of the probability specified in 5.3.3.1a of inadvertent contamination shall address the following factors, at a minimum:\n1.\tBioburden at launch;\n2.\tCruise survival for bioburden;\n3.\tBioburden survival in the respective radiation environment;\n4.\tProbability of landing on Solar system body;\n5.\tThe mechanisms and timescales of transport to the subsurface;\n6.\tBioburden survival and proliferation before, during, and after subsurface transfer.\n","NOTE \tMethods of bioburden reduction reflect the type of environments found on Europa or Enceladus, focusing on terrestrial organisms most likely to survive on Europa or Enceladus, such with cold, desiccation and radiation tolerance. \n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.3.1c","Requirement","ECSS-U-ST-20_1430038",1,"Created","When computing the calculation of requirement 5.3.3.1b the estimate for poorly known parameters shall be subject to approval by the customer and the PPAA.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.3.2.2a","Requirement","ECSS-U-ST-20_1430039",1,"Created","Requirements in clause 5.3.2.2.3, shall be applied to the outbound leg of a sample return mission.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.3.2.2b","Requirement","ECSS-U-ST-20_1430040",1,"Created","The severity of potential consequences of releasing unsterilized material from Europa or Enceladus and flight hardware that were exposed to unsterilized material from Europa or Enceladus into the terrestrial environment shall be categorised as catastrophic in accordance with ECSS-Q-ST-40.\n","NOTE \tThe categorization of this severity level is not because a catastrophic consequence is expected but only following the precautionary principle due to the large number of unknowns.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.3.2.2c","Requirement","ECSS-U-ST-20_1430041",1,"Created","Safety critical functions as defined in 3.2.19 shall be treated as severity function criticality level 1 in accordance with ECSS-Q-ST-40.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.3.2.2d","Requirement","ECSS-U-ST-20_1430042",1,"Created","No unsterilised portion of the materials returned from Europa or Enceladus shall be released from containment unless approved by the PPAA.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.4.1a","Requirement","ECSS-U-ST-20_1430043",1,"Created","Categorization of missions to small Solar system bodies shall be made on a case-by-case basis.\n","NOTE \tThe small Solar system bodies (SB) not elsewhere discussed in this document represent a large class of objects. Most missions to SB are classified as Category I or Category II missions for forward contamination, and Category V, unrestricted Earth return, for backward contamination.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.4.1b","Requirement","ECSS-U-ST-20_1430044",1,"Created","The mission shall be categorized as “restricted Earth return” if the answer to all the following six questions is \"no\" or “uncertain”, otherwise the mission is categorized as “unrestricted”:\n1.\tDoes scientific evidence indicate that there was never liquid water in or on the target body?\n2.\tDoes scientific evidence indicate that metabolically useful energy sources were never present?\n3.\tDoes scientific evidence indicate that there was never sufficient organic matter or CO2 or carbonates and an appropriate source of reducing equivalents in or on the target body to support life?\n4.\tDoes scientific evidence indicate that subsequent to the disappearance of liquid water, the target body has been subjected to extreme temperatures >160 °C?\n5.\tDoes scientific evidence indicate that there is or was sufficient radiation for sterilization of terrestrial life forms?\n6.\tDoes scientific evidence indicate that there has been a natural influx to Earth, via meteorites, of material equivalent to a sample returned from the target body?\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.4.1c","Requirement","ECSS-U-ST-20_1430045",1,"Created","If a mission is categorized as “restricted Earth return” in accordance with 5.3.4.1b, procedures shall be applied to the mission as specified in requirements from clause 5.3.4.2\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.4.2.2a","Requirement","ECSS-U-ST-20_1430046",1,"Created","Category IVb requirements in clause 5.3.2.2.3, shall be applied to the outbound leg of a sample return mission.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.4.2.2b","Requirement","ECSS-U-ST-20_1430047",1,"Created","The severity of potential consequences of releasing unsterilized material from specific small solar system bodies and flight hardware that has been exposed to unsterilized material from specific small solar system bodies into the terrestrial environment shall be categorised as catastrophic in accordance with ECSS-Q-ST-40.\n","NOTE \tThe categorization of this severity level is not because a catastrophic consequence is expected but only following the precautionary principle due to the large number of unknowns..\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.4.2.2c","Requirement","ECSS-U-ST-20_1430048",1,"Created","Safety critical functions as defined in 3.2.19 shall be treated as severity function criticality level 1 in accordance with ECSS-Q-ST-40.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.3.4.2.2d","Requirement","ECSS-U-ST-20_1430049",1,"Created","No unsterilised portion of the materials returned from Mars shall be released from containment unless approved by the PPAA.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.4.1a","Requirement","ECSS-U-ST-20_1430050",1,"Created","Requirements from clause 5 of ECSS-Q-ST-70-58 shall be applied for bioburden controlled environments.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.4.2a","Requirement","ECSS-U-ST-20_1430051",1,"Created","Bioburden assessment on flight hardware shall be performed, using procedures \"Swab assay 1 (standard swab assay)\" or \"Wipe assay 1 (standard wipe assay) \"as per procedures D.1 and E.1 from Annex D and Annex E of ECSS-Q-ST-70-55.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.4.2b","Requirement","ECSS-U-ST-20_1430052",1,"Created","If direct assays are not possible, estimation of the flight hardware bioburden using the highest number in the respective category of Table 5‑1 shall be used.\n","NOTE \tThe encapsulated bioburden values in Table 5‑1 cannot be used for ALM produced hardware.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.4.2c","Requirement","ECSS-U-ST-20_1430054",1,"Created","Use of assay procedures not described in Annex D, Annex E, Annex F and Annex G of ECSS-Q-ST-70-55 shall be approved by the PPAA.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.4.2d","Requirement","ECSS-U-ST-20_1430055",1,"Created","The number of samples to evaluate the bioburden for the flight hardware shall be agreed with the PPAA and meet the following conditions:\n1.\tFive swabs for each surface area on flight hardware of 0,1 m2;\n2.\tA proportionate number, but at least one swab, for each surface area on flight hardware smaller than 0,1 m2;\n3.\tOne wipe for each surface area on flight hardware in the size range of 1 m2;\n4.\tTwo wipes for each individual surface area on flight hardware per 10 m2.\n","NOTE \tAlthough the sampling plan is specific to the size and geometry of the sampled hardware, sampling at least 20 % of the surface area is a reasonable guideline. To reduce the conservatism in the overall bioburden calculations it is better to sample larger surface areas.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.4.2e","Requirement","ECSS-U-ST-20_1430056",1,"Created","The methods for calculation surface bioburden and bioburden densities shall be agreed with PPAA. \n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.4.2f","Requirement","ECSS-U-ST-20_1430057",1,"Created","Bioburden prior to the application of a bioburden reduction procedure shall be established by using procedures specified in requirements 5.4.2a or 5.4.2b.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.4.3a","Requirement","ECSS-U-ST-20_1430058",1,"Created","Biodiversity assessment on flight hardware and bioburden controlled environment(s) shall be performed using procedures D.3-D.6 for Swab assays and procedures E.3-E.6 for Wipe assays as per Annex D and Annex E of ECSS-Q-ST-70-55.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.4.4a","Requirement","ECSS-U-ST-20_1430059",1,"Created","Dry heat microbial reduction shall be performed in compliance with requirements from clause 5 of ECSS-Q-ST-70-57.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.4.4b","Requirement","ECSS-U-ST-20_1430060",1,"Created","Hydrogen peroxide microbial reduction shall be performed in compliance with requirements from clause 5 of ECSS-Q-ST-70-56.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.4.4c","Requirement","ECSS-U-ST-20_1430061",1,"Created","Use of other bioburden reduction procedures shall be approved by the PPAA.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.4.4d","Requirement","ECSS-U-ST-20_1430062",1,"Created","Evaluation of material and hardware compatibility with bioburden reduction procedures shall be performed in compliance with requirements from clause 5 of ECSS-Q-ST-70-53.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.5a","Requirement","ECSS-U-ST-20_1430063",1,"Created","Planetary protection documentation shall be provided according to the matrix in Table 5‑2.\n","NOTE \t1\tTable 5‑2 can be tailored to the respective project.\nNOTE \t2\tDocumenting the implementation of planetary protection requirements is not limited to the dedicated planetary protection documents but needs to be reflected in the affected project documentation, e.g., management plan, quality plan, AIV and AIT plan, VCD.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.5b","Requirement","ECSS-U-ST-20_1430064",1,"Created","The supplier shall support the PPAA, for the preparation of the customer level planetary protection report of a mission.\n","NOTE \t1\tThe report is delivered no later than nine months after launch to the President of COSPAR and the chair of the COSPAR panel on planetary protection.\nNOTE \t2\tContent of the customer level planetary protection report to COSPAR is described in the COSPAR Planetary Protection Policy [2].\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.6a","Requirement","ECSS-U-ST-20_1430066",1,"Created","Planetary protection implementation activities and applicable planetary protection documentation specified in Table 5‑2, including any documentation to support conclusions of analysis, shall be reviewed during regular reviews to which PPAA participates.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.6b","Requirement","ECSS-U-ST-20_1430067",1,"Created","Planetary protection reviews shall be held for Earth return missions to authorize the different segments of the return phase:\n1.\tSubsequent to sample collection and prior to a manoeuvre to enter a Earth return trajectory;\n2.\tPrior to commitment for Earth entry.\n","NOTE \t1\tThe objective of these reviews is to demonstrate that the mission continues to meet the planetary protection requirements in general, and Earth safety in particular.\nNOTE \t2\tThe planetary protection reviews can be part of regular project reviews.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.7a","Requirement","ECSS-U-ST-20_1430068",1,"Created","ECSS-Q-ST-10-09 shall be applied for nonconformances and waivers.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.7b","Requirement","ECSS-U-ST-20_1430069",1,"Created","All nonconformance related to planetary protection shall be specified as major nonconformance.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.7c","Requirement","ECSS-U-ST-20_1430070",1,"Created","The disposition of nonconformances related to planetary protection requirements shall be subject to approval by the PPAA.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","5.7d","Requirement","ECSS-U-ST-20_1430071",1,"Created","The approval of waivers related to planetary protection requirements shall be subject to approval by the PPAA.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","A.2.1a","Requirement","ECSS-U-ST-20_1430072",1,"Created","The planetary protection requirements document shall include at least the following items:\n1.\tMission description\n(a)\tScientific objectives and payload description\n(b)\tMission type fly-by, orbiter, lander, Earth return\n(c)\tDescription of mission phases\n(d)\tDescription of launch vehicle and launch site\n(e)\tIdentification of targeted and encountered Solar system bodies\n(f)\tIdentification and use of nuclear heat and power sources\n(g)\tIdentification and use of aerobraking and aerocapture manoeuvres\n(h)\tDescription of entry, descent and landing phases\n(i)\tDescription of intended landing site and expected landing accuracy\n(j)\tIntended final disposition of all launched hardware\n(k)\tDescription of international cooperation\n2.\tPlanetary protection category\n3.\tPlanetary protection management requirements, tailored ECSS-U-ST-20\n4.\tTechnical planetary protection requirements, tailored ECSS-U-ST-20\n5.\tPlanetary protection methods and procedures, tailored ECSS-U-ST-20\n6.\tPlanetary protection documentation and reviews, tailored ECSS-U-ST-20\n","NOTE \tPlanetary protection requirements for the payload are usually described in the payload interface requirements.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","A.2.2a","Permission","ECSS-U-ST-20_1430073",1,"Created","The Mission description, specified in A.2.1a.1, may be covered by a reference to another project document.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","B.2.1a","Requirement","ECSS-U-ST-20_1430074",1,"Created","The planetary protection plan shall include the following items:\n1.\tMission description.\n2.\tAssessment of the consequences to implement the planetary protection requirements with respect to design, development, schedule and operations.\n3.\tGeneral implementation approach:\n(a)\tPlanetary protection management and organisation.\n(b)\tDescription of bioburden control approach for all major flight hardware elements, including payload and launch recontamination.\n(c)\tDescription of bioburden allocations with identified margins and uncertainties for all major flight hardware elements.\n(d)\tDescription of bioburden control approach and/or contamination control approach for life-detection investigation, in accordance with ECSS-U-ST-20 requirement 5.3.2.2.3a.\n(e)\tDescription of probability of impact analysis, in accordance with ECSS-U-ST-20 requirements 5.2.2a, 5.2.2b, 5.3.2.1d, 5.3.2.1e including: \n(1)\tImpact analysis for launcher and spacecraft elements against target bodies identified in the “planetary protection requirements” document, with analysis supporting the conclusions providing evidence that the selected approach is feasible for the specific mission; \n(1)\tIf probability of impact approach is not possible or selected, break-up, burn-up and general atmospheric entry heating analysis providing evidence that the selected approach is feasible for the specific mission.\n(f)\tDescription of probability of contamination analysis, in accordance with ECSS-U-ST-20 requirements 5.2.3a, 5.3.2.2.2c, d, e, f, 5.3.2.2.3c and 5.3.3.2.2a.\n(g)\tDescription for methods and procedures to be used, in accordance with ECSS-U-ST-20 requirements in clause 5.4.\n(h)\tDescription of planned requests for using methods, procedures or values not described in this standard, in accordance with ECSS-U-ST-20 requirements in clause 5.7.\n4.\tPlanetary protection documentation and reviews, in accordance with ECSS-U-ST-20 requirements in clauses 5.5 and 5.6.\n5.\tIdentify planetary protection activities and events in the project schedule.\n6.\tCompliance matrix against the planetary protection requirements.\n7.\tAnalysis and conclusions of consequences for planned non-conformances or waivers.\n8.\tVerification matrix against the planetary protection requirements.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","B.2.2a","Permission","ECSS-U-ST-20_1430075",1,"Created","The Mission description, as per B.2.1a.1. may be covered by a reference to another project document.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","B.2.2b","Permission","ECSS-U-ST-20_1430076",1,"Created","The Assessment of the consequences, as per B.2.1a.2. may summarize the consequences with references to other project documentation for detailed descriptions.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","B.2.2c","Permission","ECSS-U-ST-20_1430077",1,"Created","The compliance matrix, as per B.2.1a.6. may be included in a project level compliance and verification matrix.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","B.2.2d","Permission","ECSS-U-ST-20_1430078",1,"Created","The Verification matrix as per B.2.1a.8. may be included in a project level compliance and verification matrix.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","C.2.1a","Requirement","ECSS-U-ST-20_1430079",1,"Created","The planetary protection implementation plan shall include the following items:\n1.\tFlight system description\n(a)\tHardware description\n(1)\tSystem and sub-system description, including payload\n(2)\tPlanetary protection description vs. subsystem names\n(b)\tCriteria for exposed surfaces and planetary protection accountable volumes\n(c)\tMission planetary protection issues as they are intended to be implemented, accounting for the following data: \n(1)\tProbability of impact analysis, in accordance with ECSS-U-ST-20 requirements 5.2.2a, 5.2.2b, 5.3.2.1d, 5.3.2.1e; \n(2)\tProbability of contamination analysis in accordance with ECSS-U-ST-20 requirements 5.2.3a, 5.3.3.2.2a;\n(3)\tSpacecraft induced special regions, in accordance with ECSS-U-ST-20 requirement 5.3.2.2.2c; \n(4)\tLanding site selection; \n(5)\tDraft organic material inventory in accordance with ECSS-U-ST-20 requirements 5.3.1a, 5.3.2.1a.\n2.\tDescription of Facilities\n(a)\tFormal system including \n(1)\tRisk assessment;\n(2)\tAlerts and action levels;\n(3)\tControl approach.\n(b)\tCommissioning\n(c)\tOperation\n3.\tBioburden control plan for the flight system\n(a)\tBioburden allocation including:\n(1)\tExposed surface bioburden allocation; \n(2)\tTotal bioburden allocation;\n(3)\tHardware exceptions.\n(b)\tSampling and Assay plan including:\n(1)\tFraction of exposed surfaces sampled;\n(2)\tNumber of samples; \n(3)\tSampling site selection;\n(4)\tSampling schedule.\n(c)\tStatistical treatment of the assay results including:\n(1)\tCase for total spore count greater than one;\n(2)\tCase for total spore count of zero or one;\n(3)\tCase for treatment of bulk assay;\n(4)\tBasis for bioburden density standard deviation;\n(5)\tAssay results acceptance guidelines.\n(d)\tBioburden assessment, in accordance with ECSS-U-ST-20 requirements 5.4.1a, and requirements from clause 5.4.2 including: \n(1)\tCalculation of surface bioburden density and number of spores from assay data;\n(2)\tSurface bioburden density and number of spores without assay data;\n(3)\tSurface bioburden density and number of spores for hardware treated by a bioburden reduction procedures;\n(4)\tEncapsulated bioburden density and number of spores with assay data;\n(5)\tEncapsulated bioburden density and number of spores without assay data.\n(e)\tBiodiversity assessment, in accordance with ECSS-U-ST-20 requirement 5.4.3a.\n4.\tBioburden reduction plan for the flight system, in accordance with ECSS-U-ST-20 requirements in clause 5.4.4\n(a)\tSpacecraft hardware subject to bioburden reduction processes;\n(b)\tProcess analysis;\n(c)\tProcess verification and control;\n(d)\tRecontamination prevention approach.\n5.\tGeneral implementation approach for the flight system\n(a)\tPre-AIV, AIT and launch operations including: \n(1)\tGeneral approach at hardware manufacturing sites;\n(2)\tGeneral approach at Customer, supplier and instrument provider site.\n(b)\tAIV, AIT and launch operations including: \n(1)\tAcceptance criteria; \n(2)\tGeneral approach at Customer and supplier and payload provider site; \n(3)\tGeneral approach at test site; \n(4)\tGeneral approach at launch site.\n(c)\tInside surface of the launch vehicle fairing, launch vehicle air conditioning, and white room air conditioning.\n(d)\tUpper stage and propulsion module.\n6.\tUpdated list of the foreseen waivers and NCRs and the associated impact analysis.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","D.2.1a","Requirement","ECSS-U-ST-20_1430080",1,"Created","The pre-launch planetary protection report shall include the following items:\n1.\tDeviation from planetary protection requirements and plan;\n2.\tDeviation from the planetary protection implementation plan;\n3.\tResults of contamination control measures, including raw and processed data of bioburden assays for the entire product tree;\n4.\tUpdate of probability of impact analysis, in accordance with ECSS-U-ST-20 requirements 5.2.2a, 5.2.2b, 5.3.2.1d, 5.3.2.1e;\n5.\tUpdate for probability of contamination analysis in accordance with ECSS-U-ST-20 requirements 5.2.3a, 5.3.3.2.2a;\n6.\tOrganic materials inventory, in accordance with ECSS-U-ST-20 requirements 5.3.1a, 5.3.2.1a;\n7.\tConclusions of the report.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","E.2.1a","Requirement","ECSS-U-ST-20_1430081",1,"Created","The post-launch planetary protection report shall include the following items:\n1.\tGround processing affecting bioburden control;\n2.\tLast verification assay results;\n3.\tLaunch events affecting bioburden control;\n4.\tPost Launch effects within the deployment and in orbit commissioning timeframe;\n5.\tConclusions of the report.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","F.2.1a","Requirement","ECSS-U-ST-20_1430082",1,"Created","The extended mission planetary protection report shall include the following items:\n1.\tDeviation from planetary protection requirements and plan;\n2.\tDeviation from the planetary protection implementation plan;\n3.\tUpdate of probability of impact analysis, in accordance with ECSS-U-ST-20 requirements 5.2.2a, 5.2.2b, 5.3.2.1d, 5.3.2.1e;\n4.\tUpdate for probability of contamination analysis, in accordance with ECSS-U-ST-20 requirements 5.2.3a, 5.3.3.2.2a;\n5.\tConclusions of the report.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","G.2.1a","Requirement","ECSS-U-ST-20_1430083",1,"Created","The end-of-mission planetary protection report shall include the following items:\n1.\tDisposition and condition of all launched flight hardware including the launcher upper stage, either in space describing the orbital parameters or for landed or impacting elements by position on the target body;\n2.\tDeviation from planetary protection requirements and plan;\n3.\tDeviation from the planetary protection implementation plan;\n4.\tUpdate of probability of impact analysis in accordance with ECSS-U-ST-20 requirements 5.2.2a, 5.2.2b, 5.3.2.1d, 5.3.2.1e;\n5.\tUpdate for probability of contamination analysis, in accordance with ECSS-U-ST-20 requirements 5.2.3a, 5.3.3.2.2a;\n6.\tConclusions of the report.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","H.2.1a","Requirement","ECSS-U-ST-20_1430084",1,"Created","The organic material inventory shall include the following for each organic material present above a specified limit agreed with PPAA:\n1.\tIdentity;\n2.\tChemical composition;\n3.\tUsage, with respect to product tree;\n4.\tMass estimate using the mass codes specified in ECSS-Q-ST-70-01;\n5.\tRating and reference for outgassing for each item using ECSS-Q-ST-70-01;\n6.\tSupplier for each item.\n"]
["ECSS-U-ST-20C","ECSS - Current v1.0","H.2.1b","Requirement","ECSS-U-ST-20_1430085",1,"Created","For missions to the Moon, including fly-by-gravity assist, a description of the products released by the propulsion and life-support system, as applicable, into the lunar environment shall be provided, including:\n1.\tA quantitative and qualitative description of the major chemical species, and\n2.\tAn indication of the minor chemical species and quantity.\n"]

{"sheet":"DOORS v.1.0 Superseded_Nov2025","index":1,"n_rows":19350,"n_cols":12,"rows_kept":4500,"cut":true,"bounds":{"rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0}}
[{"$nulls":9},"EARM"]
["ECSS Source Reference","DOORS Project","ECSS Req. Identifier","Type","IE PUID","RCM Version","ECSS Change Status","Original requirement","Text of Note of Original requirement","4. Applicability\n(A/M/D/N)","5. Modified or New requirement\n(full text)","6. Justification\n(only in case of M, D or N in colum 4)"]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","4a","Requirement","ECSS-Q-ST-30-11_0140001",1,"Created","The user of this Standard shall verify that the ordered assurance level of procured components is compatible with the intended application."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","5.3.2a","Requirement","ECSS-Q-ST-30-11_0140002",1,"Created","Derating shall be applied in consideration of temperature limits recommended."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","5.3.2b","Requirement","ECSS-Q-ST-30-11_0140003",1,"Created","The derating requirements of this Standard shall not be used as a justification to upgrade the quality level of components."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","5.3.2c","Requirement","ECSS-Q-ST-30-11_0140004",1,"Created","The derating requirements shall be taken into account at the beginning of the design cycle of an equipment for any consequential design trade-off to be made. Specific attention shall be paid to, for example, breadboards and engineering models where parameter derating was not considered."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","5.3.2d","Requirement","ECSS-Q-ST-30-11_0140005",1,"Created","Component families and groups excluded in this Standard are due to the lack of experimental data and failure history. For these components, the user shall consult a component design and reliability specialist to apply the requirements of this Standard."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","5.3.2e","Requirement","ECSS-Q-ST-30-11_0140006",1,"Created","Components may be excluded from this Standard if they are used for short durations of less than one month provided the device ratings are not exceeded; for example, components used in solar generator deployment systems, redundancy commutation and launchers (except in some specific cases, noted family by family). In these cases, the designer shall ensure that the applied stress level does not exceed the component maximum rating. "]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","5.3.2f","Requirement","ECSS-Q-ST-30-11_0140007",1,"Created","In the same way, during a test (e.g. qualification and EMC), derating requirements are applied on operating conditions and not on test conditions, even if during some periods, the temperature range reached is higher than the derated value. However, the specified maximum ratings shall not be exceeded. "]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","5.3.2g","Requirement","ECSS-Q-ST-30-11_0140008",1,"Created","Derating shall be applied on normal operating conditions and not on the fault condition. "]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","5.3.2h","Requirement","ECSS-Q-ST-30-11_0140009",1,"Created","Where components are required to operate in protection mode or in fail-safe mode in order to prevent failure propagation (e.g. short-circuit protection), the components concerned shall meet the derating requirements and application rules when performing the protection or fail-safe function under the worst failure case (i.e. highest stress applied to the components that can last throughout the mission)."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","5.4.2a","Requirement","ECSS-Q-ST-30-11_0140010",1,"Created","If ratings are provided for transients or surge conditions, the same derating figures as for steady-state equivalent parameters shall be used."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","5.4.2b","Requirement","ECSS-Q-ST-30-11_0140011",1,"Created","If ratings are not provided for transient or surge conditions, then it shall be assured that the transient or surge values are below the steady-state specified maximum ratings."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","5.4.2c","Requirement","ECSS-Q-ST-30-11_0140012",1,"Created","Repetitive transients, e.g. in a switching DC/DC converter operation, and clock transmission lines, shall not exceed the derated steady-state values, superseded by no more than 90 % of the rated manufacturer values if not compatible."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","5.4.2d","Requirement","ECSS-Q-ST-30-11_0140013",1,"Created","Where radiation sensitive components are identified, it is the user’s responsibility that the chosen component technologies are suitable and that the mitigation factors, such as shielding, meet the customer’s requirement. The electrical derating shall be in accordance with this Standard."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","5.5.2a","Requirement","ECSS-Q-ST-30-11_0140014",1,"Created","For hybrids, individual components shall be in conformance with their respective derating rules."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.2.1a","Requirement","ECSS-Q-ST-30-11_0140015",1,"Created","The capacitor stress sum value of steady-state voltage, AC voltage shall not exceed the load ratios specified hereunder. For transients refer to clause 5.4."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.2.1b","Permission","ECSS-Q-ST-30-11_0140079",1,"Created","Multilayer capacitors with a DC voltage rating less than 100 V may be used in low voltage (less than 10 V) continuous applications provided they have been submitted to a low voltage (1,5 V) 85 % humidity at 85 °C test or other approved method. "]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.2.1c","Recommendation","ECSS-Q-ST-30-11_0140080",1,"Created","Physical limitation for type II: maximum surge dV/dt approximate to 100 V/ms. This should be verified with the manufacturer."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.2.1d","Recommendation","ECSS-Q-ST-30-11_0140081",1,"Created","Internal heating due to ESR can increase ageing and should be taken into account by applying a margin in temperature. Where ESR is not known at the frequency of a ripple current, an extrapolation of the ESR value and resonance (from manufacturer’s or test data) should be made where possible."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.3.1a","Requirement","ECSS-Q-ST-30-11_0140019",1,"Created","The capacitor stress sum value of steady-state voltage and AC voltage shall not exceed the load ratio specified hereunder. For transients refer to clause 5.4."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.3.1b","Requirement","ECSS-Q-ST-30-11_0140020",1,"Created","100 % surge current screening shall be applied for all surface mounted capacitors types."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.3.1c","Requirement","ECSS-Q-ST-30-11_0140021",1,"Created","Surge current shall be derated to 75 % of the Isurge max. Isurge max is defined as Vrated/(ESR+Rs). Vrated is the maximum rated voltage, ESR is the maximum specified value and Rs is the value of series resistance specified in the circuit for surge current testing as defined in the applicable procurement specification."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.3.1d","Requirement","ECSS-Q-ST-30-11_0140022",1,"Created","Reverse voltage shall not exceed 75 % of the manufacturer’s specified maximum value for the reverse voltage."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.3.1e","Requirement","ECSS-Q-ST-30-11_0140023",1,"Created","Ripple power shall never exceed 50 % of the manufacturer’s specified maximum value."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.3.1f","Recommendation","ECSS-Q-ST-30-11_0140082",1,"Created","Internal heating due to ESR can increase ageing and should be taken into account by applying a margin in temperature. Where ESR is not known at the frequency of a ripple current, an extrapolation of the ESR value and resonance (from manufacturer’s or test data) should be made where possible."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.4.1a","Requirement","ECSS-Q-ST-30-11_0140025",1,"Created","Reverse voltage shall not exceed 75 % of the manufacturer’s specified maximum value for the reverse voltage."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.4.1b","Requirement","ECSS-Q-ST-30-11_0140026",1,"Created","Manufacturer’s ratings for ripple power or current shall never be exceeded. "]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.4.1c","Recommendation","ECSS-Q-ST-30-11_0140083",1,"Created","Internal heating due to ESR can increase ageing and should be taken into account by applying a margin in temperature. Where ESR is not known at the frequency of a ripple current, an extrapolation of the ESR value and resonance (from manufacturer’s or test data) should be made where possible."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.5.1a","Requirement","ECSS-Q-ST-30-11_0140028",1,"Created","Self healing requirements for polyethylene terepthalate (PET, polyester) film:\n    1. To have a clearing process in any case, the minimum energy available shall be greater than the manufacturer’s specified value (typical self healing energy is 5 mJ minimum).\n    2. To prevent any risk of destruction during self healing, capacitor banks shall not provide energy greater than 15 J."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.5.1b","Requirement","ECSS-Q-ST-30-11_0140029",1,"Created","For other films, clearing recommendations from manufacturers shall be followed."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.5.1c","Recommendation","ECSS-Q-ST-30-11_0140084",1,"Created","Internal heating due to ESR can increase ageing and should be taken into account by applying a margin in temperature. Where ESR is not known at the frequency of a ripple current, an extrapolation of the ESR value and resonance (from manufacturer’s or test data) should be made where possible."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.6.1a","Recommendation","ECSS-Q-ST-30-11_0140085",1,"Created","Internal heating due to ESR can increase ageing and should be taken into account by applying a margin in temperature. Where ESR is not known at the frequency of a ripple current, an extrapolation of the ESR value and resonance (from manufacturer’s or test data) should be made where possible."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.7.1a","Recommendation","ECSS-Q-ST-30-11_0140086",1,"Created","Internal heating due to ESR can increase ageing and should be taken into account by applying a margin in temperature. Where ESR is not known at the frequency of a ripple current, an extrapolation of the ESR value and resonance (from manufacturer’s or test data) should be made where possible."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.8.1a","Recommendation","ECSS-Q-ST-30-11_0140087",1,"Created","Internal heating due to ESR can increase ageing and should be taken into account by applying a margin in temperature. Where ESR is not known at the frequency of a ripple current, an extrapolation of the ESR value and resonance (from manufacturer’s or test data) should be made where possible."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.9.1a","Recommendation","ECSS-Q-ST-30-11_0140088",1,"Created","Internal heating due to ESR can increase ageing and should be taken into account by applying a margin in temperature. Where ESR is not known at the frequency of a ripple current, an extrapolation of the ESR value and resonance (from manufacturer’s or test data) should be made where possible."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.10.1a","Recommendation","ECSS-Q-ST-30-11_0140089",1,"Created","Internal heating due to ESR can increase ageing and should be taken into account by applying a margin in temperature. Where ESR is not known at the frequency of a ripple current, an extrapolation of the ESR value and resonance (from manufacturer’s or test data) should be made where possible."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.11.1a","Requirement","ECSS-Q-ST-30-11_0140036",1,"Created","For power connectors, power and return lines shall be separated by at least one unassigned contact to reduce the short-circuit risk."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.11.1b","Requirement","ECSS-Q-ST-30-11_0140037",1,"Created","Connector savers shall be used during testing of equipment to minimize number of mating and demating cycles."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.11.1c","Requirement","ECSS-Q-ST-30-11_0140038",1,"Created","When multi-pin connectors are close to one another, they shall be configured such that mating with a wrong connector is not possible or the contact assignments shall be chosen such that mating with a wrong connector does not cause damage to the unit itself nor to any other element of the system."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.11.1d","Requirement","ECSS-Q-ST-30-11_0140039",1,"Created","The connector and its constituent parts shall be from the same manufacturer."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.12.1a","Requirement","ECSS-Q-ST-30-11_0140040",1,"Created","Connector savers shall be used during testing of equipment to minimize number of mating and demating cycles."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.14.1a","Requirement","ECSS-Q-ST-30-11_0140041",1,"Created","Some diodes can be radiation sensitive: the issue shall be recorded in the design file and the components selection shall be reviewed and approved as described in ECSS-Q-ST-60. Where power cycling is critical this should be considered."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.15.1a","Requirement","ECSS-Q-ST-30-11_0140042",1,"Created","Some diodes can be radiation sensitive: the issue shall be recorded in the design file and the components selection shall be reviewed and approved as described in ECSS-Q-ST-60."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.17.1a","Requirement","ECSS-Q-ST-30-11_0140043",1,"Created","Fuses shall be avoided whenever possible. The derating requirements in 6.17.2 (below) are only applicable to Cermet types. The application and the deratings of other fuse technologies shall be justified."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.17.1b","Requirement","ECSS-Q-ST-30-11_0140044",1,"Created","The largest fuse rating compatible with the source capability shall be used."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.17.1c","Requirement","ECSS-Q-ST-30-11_0140045",1,"Created","The power supply shall be capable of delivering three times the specified fuse rated current in order to obtain short fusing times."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.18.1a","Requirement","ECSS-Q-ST-30-11_0140046",1,"Created","For custom-made inductors and transformers, the maximum rated temperature shall be evaluated taking into consideration the temperature characteristics of the materials used."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.19.1a","Requirement","ECSS-Q-ST-30-11_0140047",1,"Created","Some devices can be radiation sensitive: this shall be recorded and approved in accordance with ECSS-Q-ST-60."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.20.1a","Requirement","ECSS-Q-ST-30-11_0140048",1,"Created","Some devices can be radiation sensitive: this shall be recorded and approved in accordance with ECSS-Q-ST-60."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.21.1a","Requirement","ECSS-Q-ST-30-11_0140049",1,"Created","Some linear circuits can be radiation sensitive: the issue shall be recorded in the design file and the components selection shall be reviewed and approved as described in ECSS-Q-ST-60."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.21.1b","Requirement","ECSS-Q-ST-30-11_0140050",1,"Created","Additional margins can be applied for radiation effects."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.22.1a","Requirement","ECSS-Q-ST-30-11_0140051",1,"Created","Some linear circuits can be radiation sensitive: the issue shall be recorded in the design file and the components selection shall be reviewed and approved as described in ECSS-Q-ST-60."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.23.1a","Requirement","ECSS-Q-ST-30-11_0140052",1,"Created","Some MMICs can be radiation sensitive: the choice of MMICs shall be based on suitability and application. Justification shall be in accordance with ECSS-Q-ST-60 and provided in accordance with this Standard, and at the design reviews."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.23.2a","Requirement","ECSS-Q-ST-30-11_0140053",1,"Created","Each discrete cell (capacitors, resistors, diodes and transistors) constituting analogue custom MMICs shall be derated in accordance with this document’s requirements for the applicable family. For digital cells, apply the derating rules applicable to integrated circuits."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.23.2b","Requirement","ECSS-Q-ST-30-11_0140054",1,"Created","When operational reliability data is available, the compression level shall be derated to 2 dB under the highest compression level showing no drift. MMICs having no compression data shall not be submitted to more than 1 dB of compression."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.24.1a","Requirement","ECSS-Q-ST-30-11_0140055",1,"Created","For all ICs not considered in the previous subgroups, the following derating rules shall be followed:\n    1. Manufacturer’s derating values.\n    2. Maximum junction temperature: 110 °C or Tj max - 40 °C, whichever is lower.\n    3. For the part of the IC similar to logic ICs, apply the derating rules for logic subgroups, for the part similar to linear ICs, apply the derating rules for linear subgroups and so forth."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.24.1b","Requirement","ECSS-Q-ST-30-11_0140056",1,"Created","Some integrated circuits can be radiation sensitive: this shall be recorded and approved in accordance with ECSS-Q-ST-60."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.25.1a","Requirement","ECSS-Q-ST-30-11_0140057",1,"Created","The coil supply voltage shall be within the specified voltage range or between the specified rated and the maximum coil voltage."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.25.1b","Requirement","ECSS-Q-ST-30-11_0140058",1,"Created","The minimum coil pulse duration for latching relays shall be 10 times the sum of latch time (tL) and bounce time (tB) or 30 ms, whichever is greater."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.25.1c","Requirement","ECSS-Q-ST-30-11_0140059",1,"Created","Current derating does not apply to contacts that only carry current and do not switch it or to contacts that switch at zero current. In the latter case, the number of operations is limited to the qualified number of operations."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.25.1d","Requirement","ECSS-Q-ST-30-11_0140060",1,"Created","Rated contact load voltage should not be exceeded since it has a strong impact on the contact current: this shall be recorded and approved in accordance with ECSS-Q-ST-60."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.25.1e","Requirement","ECSS-Q-ST-30-11_0140061",1,"Created","A double throw contact shall not be used to switch a load (movable contact) between a power supply and ground (stationary contacts). This type of configuration may be accepted in the following conditions:\n    1. when switching off the power supply the other stationary contact is not connected to ground, or\n    2. the potential difference between stationary contacts is less than 10 V and the switched current less than 0,1 A."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.25.1f","Requirement","ECSS-Q-ST-30-11_0140062",1,"Created","Paralleled relays shall not be used to increase current switching capabilities of contacts. When relays are paralleled for redundancy, in order to increase the system’s reliability, the sum of the paralleled currents shall not exceed the contact current rating. "]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.25.1g","Requirement","ECSS-Q-ST-30-11_0140063",1,"Created","Suppression diodes shall not be used inside relays. "]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.26.1.1a","Requirement","ECSS-Q-ST-30-11_0140064",1,"Created","The mentioned temperatures cited below refer to case temperatures."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.26.1.9a","Requirement","ECSS-Q-ST-30-11_0140065",1,"Created","Average power < 50 % of nominal rating\n \nwhere\nVp\tis the pulse amplitude\nR\tis the resistance\ntp\tis the pulse width\nT\tis the cycle duration"]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.26.1.10a","Requirement","ECSS-Q-ST-30-11_0140066",1,"Created","If ratings are provided for transient or surge condition, the same derating figures as for steady-state equivalent parameters shall be used."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.26.1.10b","Requirement","ECSS-Q-ST-30-11_0140067",1,"Created","If ratings are not provided for transient or surge condition, then it shall be assured that the transient or surge values are below the steady-state specified ratings."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.26.2a","Requirement","ECSS-Q-ST-30-11_0140068",1,"Created","Actual rated power shall be specified in the applicable heater design drawing. It shall be determined from the specified heating area (s) in cm2 taking into account the thermal properties of the mounted heater in the application."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.28.1a","Requirement","ECSS-Q-ST-30-11_0140069",1,"Created","Some transistors can be radiation sensitive: the issue shall be recorded in the design file and the components selection shall be reviewed and approved as described in ECSS-Q-ST-60."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.29.1a","Requirement","ECSS-Q-ST-30-11_0140070",1,"Created","Only SEE radiation characterized MOSFETs shall be used in space applications."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.29.1b","Requirement","ECSS-Q-ST-30-11_0140071",1,"Created","The user shall consider power cycling when this is critical to his application."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.30.1a","Requirement","ECSS-Q-ST-30-11_0140072",1,"Created","Some transistors can be radiation sensitive: the issue shall be recorded in the design file and the components selection shall be reviewed and approved as described in ECSS-Q-ST-60."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.31.1a","Requirement","ECSS-Q-ST-30-11_0140073",1,"Created","Some transistors can be radiation sensitive: this issue shall be recorded in the design file and the components selection shall be reviewed and approved as described in ECSS-Q-ST-60."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.33.1a","Requirement","ECSS-Q-ST-30-11_0140074",1,"Created","Light emitting diodes can be radiation sensitive, in particular, there is a high sensitivity to proton displacement damage: this issue shall be recorded in the design file and the components selection shall be reviewed and approved as described in ECSS-Q-ST-60."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.33.1b","Requirement","ECSS-Q-ST-30-11_0140075",1,"Created","Opto-couplers can be radiation sensitive, in particular, operation at low diode currents increases radiation sensitivity: this issue shall be recorded in the design file and the components selection shall be reviewed and approved as described in ECSS-Q-ST-60."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.33.1c","Requirement","ECSS-Q-ST-30-11_0140076",1,"Created","Photo-transistors can be radiation sensitive: this issue shall be recorded in the design file and the components selection shall be reviewed and approved as described in ECSS-Q-ST-60."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.34.1a","Requirement","ECSS-Q-ST-30-11_0140077",1,"Created","For connectorized components, connector savers shall be used during testing of equipment to minimize number of mating and demating cycles."]
["ECSS-Q-ST-30-11C","ECSS - Superseded v1.0","6.36a","Requirement","ECSS-Q-ST-30-11_0140078",1,"Created","For hybrids, individual components shall be in conformance with their respective derating rules."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.1a","Requirement","ECSS-Q-ST-70-13_0610001",1,"Created","The supplier shall identify, manage and process materials and parts with hazardous characteristics according to ECSS-Q-ST-40."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.1b","Requirement","ECSS-Q-ST-70-13_0610002",1,"Created","The supplier shall keep the health and safety precautions according to the supplier’s national safety regulations."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.2.1a","Requirement","ECSS-Q-ST-70-13_0610003",1,"Created","The supplier shall prepare the material samples according to the process specifications or manufacturer’s data."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.2.1b","Requirement","ECSS-Q-ST-70-13_0610004",1,"Created","The material samples shall be representative of batch variance."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.2.1c","Requirement","ECSS-Q-ST-70-13_0610005",1,"Created","If it is not practicable to test completed assemblies, the supplier shall submit samples made from the same materials and by the same processes as those used in the manufacture of the assemblies."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.2.1d","Requirement","ECSS-Q-ST-70-13_0610006",1,"Created","The sample for testing shall have clean flat surfaces which do not overlap the sample holder described in clause 5.1.4."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.2.1e","Requirement","ECSS-Q-ST-70-13_0610007",1,"Created","The width of the test sample surface face shall be at least equal to the width of the tape used in the test procedure."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.2.1f","Requirement","ECSS-Q-ST-70-13_0610008",1,"Created","The nominal tape width shall be 20 mm."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.2.1g","Requirement","ECSS-Q-ST-70-13_0610009",1,"Created","The supplier shall specify the number of samples to be taken from a qualification batch, test programme, or production batch at the start of the test in conformance with the DRD in Annex A.."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.2.1h","Requirement","ECSS-Q-ST-70-13_0610010",1,"Created","The supplier shall test at least ten test samples."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.2.1i","Requirement","ECSS-Q-ST-70-13_0610011",1,"Created","If it is not practicable to obtain test samples from the finished article, the supplier shall furnish bonded test samples for the test.\n    ","NOTE These samples are not used for any other purpose than the designated test."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.2.1j","Requirement","ECSS-Q-ST-70-13_0610012",1,"Created","The supplier shall furnish a certificate of conformity for the purpose of traceability.\n    ","NOTE This certificate of conformity is delivered by the manufacturer in order to provide evidence that the product is compliant with the manufacturer’s process."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.2.1k","Requirement","ECSS-Q-ST-70-13_0610013",1,"Created","The supplier shall mark all test samples with identification to maintain traceability but in such a way as not to degrade the quality of the sample during testing."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.2.2a","Requirement","ECSS-Q-ST-70-13_0610014",1,"Created","The suppler shall perform the same cleaning and other treatments of the sample as that applied to the finished article, which the sample is intended to represent, prior to integration into the spacecraft."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.2.2b","Requirement","ECSS-Q-ST-70-13_0610015",1,"Created","The supplier shall not carry out further cleaning or other treatments."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.2.3a","Requirement","ECSS-Q-ST-70-13_0610016",1,"Created","The supplier shall handle the samples only with clean nylon or lint-free gloves."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.2.3b","Requirement","ECSS-Q-ST-70-13_0610017",1,"Created","The supplier shall store the samples in a controlled area, with an ambient temperature of (22 ± 3) °C and relative humidity of (55 ± 10) %."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.2.3c","Requirement","ECSS-Q-ST-70-13_0610018",1,"Created","The supplier shall shield coated surfaces from contact by using polyethylene or polypropylene bags or sheets."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.2.3d","Requirement","ECSS-Q-ST-70-13_0610019",1,"Created","The supplier shall avoid physical damage by packing the polyethylene or polypropylene-wrapped workpieces in clean, dust- and lint-free material."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.2.3e","Requirement","ECSS-Q-ST-70-13_0610020",1,"Created","The supplier shall label limited-life materials with their shelf lives and dates of manufacture, or date of delivery if date of manufacture is not known."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.2.4.1a","Requirement","ECSS-Q-ST-70-13_0610021",1,"Created","The supplier shall identify materials submitted for testing in conformance to annex A of ECSS-Q-ST-70-02."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.2.4.2a","Requirement","ECSS-Q-ST-70-13_0610022",1,"Created","The supplier shall identify assemblies submitted for testing, as a minimum, by:\n    1. trade name and batch number;\n    2. name of manufacturer or supplier through whom the purchase was made;\n    3. configuration control status of the assembly."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.3.1a","Requirement","ECSS-Q-ST-70-13_0610023",1,"Created","The work area shall be clean and free of dust."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.3.1b","Requirement","ECSS-Q-ST-70-13_0610024",1,"Created","The supplier shall filter the air used for ventilation to prevent contamination of the sample."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.3.2a","Requirement","ECSS-Q-ST-70-13_0610025",1,"Created","The supplier shall environmentally condition the sample for a nominal 24 hour period at (22 ± 3) °C with a relative humidity of (55 ± 10) %.\n    ","NOTE 1 The humidity requirement can be achieved either in a conditioning room, or by dessicators filled with silica gel or a saturated salt solution.\nNOTE 2 A saturated salt solution of calcium nitrate gives approximately 51 % relative humidity at the testing temperature.\n"]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.4.1a","Requirement","ECSS-Q-ST-70-13_0610026",1,"Created","The supplier shall use the equipment as detailed in clauses 5.1.4.2 and 5.1.4.3."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.4.2a","Requirement","ECSS-Q-ST-70-13_0610027",1,"Created","The supplier shall employ a power-driven machine capable of maintaining a specified constant rate of loading and able to be used for both tensile and compressive testing."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.4.2b","Requirement","ECSS-Q-ST-70-13_0610028",1,"Created","The machine shall have a fixed or essentially stationary member supporting a load cell and the tape holder."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.4.2c","Requirement","ECSS-Q-ST-70-13_0610029",1,"Created","A movable member shall carry the sample holder."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.4.2d","Requirement","ECSS-Q-ST-70-13_0610030",1,"Created","The applied compressive and tensile loads, as measured and recorded, shall be accurate within 1 percent of the load."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.4.2e","Requirement","ECSS-Q-ST-70-13_0610031",1,"Created","The rate of travel of the sample holder shall be at a nominal rate of 0,2 cm/min."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.4.3a","Recommendation","ECSS-Q-ST-70-13_0610074",1,"Created","The tape holder should be of a design similar to that depicted in Figure 5-1."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.4.3b","Requirement","ECSS-Q-ST-70-13_0610033",1,"Created","The part shall be screwed into the fixed member of the testing machine or be located firmly on it."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.4.3c","Requirement","ECSS-Q-ST-70-13_0610034",1,"Created","The supplier shall clamp a length of pressure-sensitive tape from one tape holder over the rubber block to the other tape holder."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.4.3d","Requirement","ECSS-Q-ST-70-13_0610035",1,"Created","The surface of the pressure-sensitive tape in contact with the flat surface of the rubber block shall be 4 cm2 ± 5 %."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.4.4a","Requirement","ECSS-Q-ST-70-13_0610036",1,"Created","The sample holder shall be firmly located beneath the tape holder on the movable member of the testing machine.\n    ","NOTE 1 A suitable design is seen in Figure 5-1.\nNOTE 2 This preferred system utilizes “top hat” supports onto which individual samples can be mechanically clamped or bonded in such a way that there is no relative movement between the support and the test sample at any time during the test cycle."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.4.4b","Requirement","ECSS-Q-ST-70-13_0610037",1,"Created","In case a “top hat” sample support is used, it shall slide into a horizontal fixture slot in such a way that its top surface is parallel to and directly beneath the rubber face of the tape holder."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.1.4.5a","Requirement","ECSS-Q-ST-70-13_0610038",1,"Created","The supplier shall employ a range of pressure-sensitive tapes for the tests with peel adhesion strengths of 220, 330, 440 and 670 g/cm, all with a tolerance of ± 10 %."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.2.1.1a","Requirement","ECSS-Q-ST-70-13_0610039",1,"Created","The supplier shall locate the test sample on the sample holder in conformance with the requirements stated in clause 5.1.4.3."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.2.1.1b","Requirement","ECSS-Q-ST-70-13_0610040",1,"Created","If an adhesive bond is used between the sample and the sample support, this shall in no way interfere with the area under test."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.2.1.1c","Requirement","ECSS-Q-ST-70-13_0610041",1,"Created","The supplier shall ensure that there is no physical or chemical interaction between any adhesive employed during sample preparation and the sample materials."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.2.1.2a","Requirement","ECSS-Q-ST-70-13_0610042",1,"Created","The supplier shall condition the loaded sample support for a nominal 24 hours in conformance with the requirements stated in clause 5.1.3.2 before the test starts."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.2.2a","Recommendation","ECSS-Q-ST-70-13_0610076",1,"Created","The supplier should run the peel and pull-off test as described in Annex B."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.2.2b","Requirement","ECSS-Q-ST-70-13_0610044",1,"Created","If the supplier uses a different procedure, the supplier shall submit it for customer approval."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.2.3a","Requirement","ECSS-Q-ST-70-13_0610045",1,"Created","The supplier shall apply the conditions specified in clause 5.1.2.3 unless other post test disposal instructions are given."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.3a","Requirement","ECSS-Q-ST-70-13_0610046",1,"Created","The supplier shall classify samples which have been tested and are not seen to be disturbed in any way by the processing described in clause 5.2.2 as having passed this test."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.3b","Requirement","ECSS-Q-ST-70-13_0610047",1,"Created","The supplier shall examine samples in detail, which have been disturbed during the test sequence."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.3c","Requirement","ECSS-Q-ST-70-13_0610048",1,"Created","The supplier shall carry out a visual examination for sample defects at ×7 magnification."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.3d","Recommendation","ECSS-Q-ST-70-13_0610077",1,"Created","In case defects are detected at ×7 magnification, the supplier should use higher magnifications during further analysis for locating microscopic defects on any fracture surfaces."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.3e","Requirement","ECSS-Q-ST-70-13_0610050",1,"Created","The supplier shall report defects and the appearance of the fracture.\n    ","NOTE 1 Defects for instance can be air bubbles or material inclusions.\nNOTE 2 Appearance of the fracture for instance can be rough, ductile, smooth or brittle."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.3f","Requirement","ECSS-Q-ST-70-13_0610051",1,"Created","The supplier shall state the particular material or interface along which the fracture path has propagated through the test sample.\n    ","NOTE This can be wholly or partly an adhesion fracture, a cohesive separation or an adherent fracture as schematically drawn in Figure C-1."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.3g","Requirement","ECSS-Q-ST-70-13_0610052",1,"Created","The supplier shall take a photographic record of the tested samples at appropriate level of magnification.\n    ","NOTE Typical topographical features are recorded at ×2, ×20, ×50, ×100, ×250, ×500 or ×1000 magnifications."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.3h","Requirement","ECSS-Q-ST-70-13_0610053",1,"Created","The supplier shall agree with the customer on the granularity level of failure analysis to be performed on failed samples, prior to the test."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.3i","Requirement","ECSS-Q-ST-70-13_0610054",1,"Created","The supplier shall perform the failure analysis as agreed with the customer.\n    ","NOTE This failure analysis can include metallographic studies, chemical analysis or scanning electronic microscopy."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.4.1a","Requirement","ECSS-Q-ST-70-13_0610055",1,"Created","The supplier shall retain the quality records for at least ten years or in conformance with project business agreement requirements, and in conformance with the Test result sheet - DRD in Annex A.\n    ","NOTE Example of such quality records are logbooks."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.4.2a","Requirement","ECSS-Q-ST-70-13_0610056",1,"Created","The supplier shall disposition any nonconformance which is observed in respect of the test process in conformance with the quality assurance requirements specified in ECSS-Q-ST-10-09."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.4.3a","Requirement","ECSS-Q-ST-70-13_0610057",1,"Created","The supplier shall use only measuring equipment calibrated to traceable reference standard."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.4.3b","Requirement","ECSS-Q-ST-70-13_0610058",1,"Created","The supplier shall record any suspected or actual equipment failure as a project nonconformance report according to ECSS-Q-ST-20.\n    ","NOTE This is to ensure that previous results can be examined to ascertain whether or not re-inspection and retesting is required."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.4.3c","Requirement","ECSS-Q-ST-70-13_0610059",1,"Created","The supplier shall notify the customer of the nonconformance details."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","5.4.4a","Requirement","ECSS-Q-ST-70-13_0610060",1,"Created","The supplier shall maintain traceability throughout the process from incoming inspection to final test, including details of test equipment and personnel employed in performing the task."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","A.2.1a","Requirement","ECSS-Q-ST-70-13_0610061",1,"Created","The test result sheet shall contain the trade names of the materials under test."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","A.2.1b","Requirement","ECSS-Q-ST-70-13_0610062",1,"Created","The test result sheet shall contain the batch numbers of the materials under test."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","A.2.1c","Requirement","ECSS-Q-ST-70-13_0610063",1,"Created","The test result sheet shall contain name of manufacturer or supplier through whom the purchase was made."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","A.2.1d","Requirement","ECSS-Q-ST-70-13_0610064",1,"Created","The test result sheet shall contain summary of the preparation and conditioning schedule.\n    ","NOTE This can be for instance the mixing proportions, coating thickness, cure time and temperature, post-cure or cleaning procedure."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","A.2.1e","Requirement","ECSS-Q-ST-70-13_0610065",1,"Created","The test result sheet shall contain details of the testing room environment conditions and test equipment."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","A.2.1f","Requirement","ECSS-Q-ST-70-13_0610066",1,"Created","The test result sheet shall contain details of the test parameters outlined in Annex B.\n    ","NOTE This also includes any variation in testing environment conditions."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","A.2.1g","Requirement","ECSS-Q-ST-70-13_0610067",1,"Created","The test result sheet shall contain details of equipment used for visual, mechanical, chemical and physical property measurement or inspection, as outlined in Annex B and test specifications where they exist."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","A.2.1h","Requirement","ECSS-Q-ST-70-13_0610068",1,"Created","The test result sheet shall contain the number of sample tests."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","A.2.1i","Requirement","ECSS-Q-ST-70-13_0610069",1,"Created","The test result sheet shall contain the results of the values obtained for peel or pull-off strength."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","A.2.1j","Requirement","ECSS-Q-ST-70-13_0610070",1,"Created","The test result sheet shall contain the peel strength indicated by the manufacturer of the pressure-sensitive tape used."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","A.2.1k","Requirement","ECSS-Q-ST-70-13_0610071",1,"Created","The test result sheet shall contain the results of any failure analysis carried out according to clause 5.3."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","A.2.1l","Requirement","ECSS-Q-ST-70-13_0610072",1,"Created","The test result sheet shall contain the mode of fracture and any photographic records.\n    ","NOTE An indication of the various fracture line is given in Figure C-1."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0","A.2.1m","Requirement","ECSS-Q-ST-70-13_0610073",1,"Created","In case of failures, the test result sheet shall contain the following details of failure mode:\n    1. deficient design;\n    2. poor workmanship;\n    3. wrong fabrication or application procedure;\n    4. wrong choice of materials;\n    5. others."]
["ECSS-Q-ST-70-13C","ECSS - Superseded v1.0",null,"Permission","ECSS-Q-ST-70-13_0610078",1,"Created","The supplier may use the template given in Figure A-1."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.1.1a","Requirement","ECSS-Q-ST-60_0480001",1,"Created","The supplier shall establish and implement throughout the duration of the business agreement a component programme which ensures that the requirements of the project as defined by the customer and the supplier in the related business agreement are in compliance with this standard."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.1.2.1a","Requirement","ECSS-Q-ST-60_0480002",1,"Created","The supplier shall identify the organization responsible for the management of the component programme, and describe the organization’s approaches (including the procurement system and its rationale) and capability to efficiently implement, manage, and control the component requirements."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.1.2.1b","Requirement","ECSS-Q-ST-60_0480003",1,"Created","The supplier’s organization shall comply with all the requirements of ECSS-M-ST-10."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.1.2.2a","Requirement","ECSS-Q-ST-60_0480004",1,"Created","The supplier shall prepare a Component Control Plan (CCP) in conformance with its DRD in Annex A."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.1.2.2b","Permission","ECSS-Q-ST-60_0480446",1,"Created","The CCP may be part of the overall project PA plan."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.1.2.2c","Requirement","ECSS-Q-ST-60_0480006",1,"Created","The supplier shall submit the CCP to the customer for approval."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.1.3a","Requirement","ECSS-Q-ST-60_0480007",1,"Created","At supplier's level, the Parts Control Board (PCB) shall be chaired by a member of the supplier’s PA team with designated responsibility for components management. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.1.3b","Requirement","ECSS-Q-ST-60_0480008",1,"Created","The composition of the PCB shall as a minimum include additionally the suppliers’ parts engineer, the customer’s representative and the lower tier subcontractor parts engineers.\n    ","NOTE The approval of the selection and usage of EEE parts are implemented through Parts Control Boards (PCBs) held between the customer and the supplier (or lower tier subcontractor)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.1.3c","Permission","ECSS-Q-ST-60_0480447",1,"Created","Other pertinent experts from the customer or suppliers may also participate, on request."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.1.3d","Requirement","ECSS-Q-ST-60_0480010",1,"Created","Depending on the progress of the program, the main PCB activities shall be:\n    1. Review and approval of the supplier's EEE component control plan and any associated documents,\n    2. Parts type reduction and standardization,\n    3. Parts approval including evaluation activities,\n    4. Problem assessment (e.g. alerts, nonconformances, RFD, RFW and delivery delays)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.1.4a","Requirement","ECSS-Q-ST-60_0480011",1,"Created","For each equipment, its supplier shall issue a DCL in an editable electronic format, identifying all component types needed. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.1.4b","Requirement","ECSS-Q-ST-60_0480012",1,"Created","This list shall be kept under configuration control (issue and identification of changes). "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.1.4c","Requirement","ECSS-Q-ST-60_0480013",1,"Created","The DCL shall be issued as a minimum at PDR and CDR (as designed) and at flight hardware delivery (as built)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.1.4d","Requirement","ECSS-Q-ST-60_0480014",1,"Created","After equipment CDR, all modifications affecting the PAD information shall be implemented, in the \"as design\" DCL, through the CN / CR process and submitted to the customer for approval.\n    ","NOTE For PAD generation, see 4.2.4d."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.1.4e","Requirement","ECSS-Q-ST-60_0480015",1,"Created","The “as design” DCL shall be sent to the customer for approval."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.1.4f","Requirement","ECSS-Q-ST-60_0480016",1,"Created","Any change of parts during equipment manufacturing (e.g. type and manufacturer) shall be handled through RFWs submitted to the customer for approval."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.1.4g","Requirement","ECSS-Q-ST-60_0480017",1,"Created","The “as built” DCL reflecting the actual EEE parts assembled into the flight hardware and their date code, shall be provided to the customer for review at the delivery of the flight hardware."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.1.4h","Requirement","ECSS-Q-ST-60_0480018",1,"Created","The content of the DCL shall be in conformance with its DRD in Annex B."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.1.5a","Requirement","ECSS-Q-ST-60_0480019",1,"Created","EEE components used in GSE, which are physically and directly interfacing to flight hardware, shall meet the requirements of this document."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.1.5b","Requirement","ECSS-Q-ST-60_0480020",1,"Created","Flight hardware connectors interfaces to GSE shall be protected by connector savers."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.1a","Requirement","ECSS-Q-ST-60_0480021",1,"Created","The supplier shall ensure that the following requirements are met during his selection process:\n    1. Project requirements (e.g. quality levels, component policy, manufacturing and delivery schedules and budgets, quantities),\n    2. Design requirements (e.g. component type, case, dimensions, materials),\n    3. Production requirements (e.g. packaging, thermal and storage constraints, component mounting process),\n    4. Operational requirements (e.g. electrical, mechanical, radiation, reliability, assembly, and lifetime).\n        ","NOTE The supplier of each product is responsible for the selection of components, which enable the performance, lifetime, environmental, material, safety, quality and reliability requirements of the product of which they form a part, to be satisfied in all respects."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.1a","Requirement","ECSS-Q-ST-60_0480022",1,"Created","The supplier shall establish and maintain in his own facility, and ensure that his suppliers also establish and maintain, procedures for selecting and controlling all components intended for use in deliverable products. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.1b","Requirement","ECSS-Q-ST-60_0480023",1,"Created","Components shall be selected on the basis of proven qualification, characterization, and previous space experience and data, relevant with regard to the requirements for the programme, from manufacturers or sources (preferably European) employing effective Product Assurance Programmes in manufacturing and test."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.1c","Requirement","ECSS-Q-ST-60_0480024",1,"Created","Preference shall be given to components which necessitate the least evaluation or qualification effort. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.1d","Requirement","ECSS-Q-ST-60_0480025",1,"Created","Starting with the design phase of the project the supplier shall ensure maximum use of preferred (see 4.2.2.3) and qualified components to achieve an effective component reduction and standardization. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.1e","Requirement","ECSS-Q-ST-60_0480026",1,"Created","When selecting items, the supplier shall check the current data, applicability of the basis of qualification, problem notifications and alerts, and adequacy of specifications. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.1f","Requirement","ECSS-Q-ST-60_0480027",1,"Created","The supplier shall implement a type reduction activity."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.2a","Requirement","ECSS-Q-ST-60_0480028",1,"Created","The supplier shall ensure that non-hermetically sealed materials of components meet the requirements of ECSS-Q-ST-70 regarding off-gassing, out-gassing, flammability, toxicity and any other criteria specified for the intended use. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.2b","Requirement","ECSS-Q-ST-60_0480029",1,"Created","The supplier shall evaluate the robustness of selected EEE components against the stresses induced by the assembly techniques to be employed."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.2c","Requirement","ECSS-Q-ST-60_0480030",1,"Created","With respect to health and safety, beryllium oxide (except if identified in the procurement specification), cadmium, lithium, magnesium, mercury, zinc, radioactive material and all material which may cause safety hazards shall not be used."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.2d","Requirement","ECSS-Q-ST-60_0480031",1,"Created","For limited life duration, known instability, safety hazards or reliability risk reasons, EEE components listed below shall not be used:\n    1. EEE components with pure tin (less than 3% Pb in case of SnPb alloy) used as a finish on the leads, terminations and external surfaces of components and packages.\n    2. Hollow core resistors,\n    3. Potentiometers (except for mechanism position monitoring),\n    4. Non-metallurgically bonded diodes,\n    5. Semiconductor dice with unglassivated active area,\n    6. Wet slug tantalum capacitors other than capacitor construction using double seals and a tantalum case,\n    7. Any component whose internal construction uses metallurgic bonding with a melting temperature not compatible with the end-application mounting conditions,\n    8. Wire link fuses < 5A,\n    9. TO5 relays without double welding of the mechanism to the header or with any type of integrated diodes inside,"]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.2e","Requirement","ECSS-Q-ST-60_0480032",1,"Created","For limited life duration, known instability, safety hazards or reliability risk reasons, EEE components listed below shall not be used for new designs:\n    1. RNC90 > 100 kW,\n    2. TO3 and DO4/DO5 packages."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.2f","Permission","ECSS-Q-ST-60_0480448",1,"Created","The use of pure tin in internal cavities may be authorized, on a case-by-case basis, based on the demonstration that there is no alternative product and there is no risk (supported by a technical justification)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.2g","Requirement","ECSS-Q-ST-60_0480034",1,"Created","As per clause 4.2.2.2e, the justification of the use of pure tin shall be presented during a PCB for customer’s approval."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.2h","Requirement","ECSS-Q-ST-60_0480035",1,"Created","The use of pure tin (inside or outside the part) shall be declared in the PAD."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.3a","Requirement","ECSS-Q-ST-60_0480036",1,"Created","Parts shall be chosen from the EPPL part I."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.3b","Requirement","ECSS-Q-ST-60_0480037",1,"Created","For parts not selected from the EPPL part I, the following sources shall be considered in the following order of precedence:\n    1. EPPL part II (when compatible with the project requirements)\n    2. ESCC QPL and QML, \n    3. NPSL level 1 (with disposition of the associated application notes) and level 2 or 3 (when compatible with the project requirements),\n    4. MIL QPL's and QML's."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.3c","Requirement","ECSS-Q-ST-60_0480038",1,"Created","Parts subject to export restrictions or regulations shall not be preferred. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.4a","Requirement","ECSS-Q-ST-60_0480039",1,"Created","The radiation requirements for EEE components are project specific."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.4b","Requirement","ECSS-Q-ST-60_0480040",1,"Created","The supplier who is responsible for the design of the piece of hardware shall demonstrate the compliance of its components selection with the radiation constraints of the project."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.4c","Requirement","ECSS-Q-ST-60_0480041",1,"Created","For this demonstration, the supplier shall consider all types of radiation including cosmic (Heavy Ions), electromagnetic, trapped (charged particles - electrons, protons - in radiation belts) and solar (flares). "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.4d","Requirement","ECSS-Q-ST-60_0480042",1,"Created","Due consideration shall be given to the mission orbit and trajectory, the duration, the associated spatial and temporal variations of the radiation environment as well as all protective factors such as shielding. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.4e","Requirement","ECSS-Q-ST-60_0480043",1,"Created","The supplier shall assess the actual radiation tolerance of the selected components for compliance with the radiation requirements in term of total dose, displacement damage and Single Events Effects (SEE). "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.4f","Requirement","ECSS-Q-ST-60_0480044",1,"Created","The supplier shall identify components which are not compliant with the radiation requirements as critical radiation sensitive components. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.4g","Requirement","ECSS-Q-ST-60_0480045",1,"Created","The supplier shall implement a Radiation Hardness Assurance Programme, documented by a plan to be approved by the customer, for radiation sensitive components, covering the collection of all relevant information and specifying the necessary actions in terms of evaluation and procurement testing, planning and control. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.4h","Requirement","ECSS-Q-ST-60_0480046",1,"Created","The supplier shall issue an Equipment Radiation Analysis document identifying all sensitive components w.r.t. the relevant radiation effects, possibly their impact and giving an adequate engineering solution (e.g. local shielding, design solution, specific test, and RVT) for the relevant equipment."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.4i","Requirement","ECSS-Q-ST-60_0480047",1,"Created","The Equipment Radiation Analysis document shall be submitted to the customer for approval.\n    ","NOTE More detailed information about the above requirements is given in ECSS-E-ST-10-12."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.5a","Requirement","ECSS-Q-ST-60_0480048",1,"Created","The supplier shall implement derating rules for components used in his designs in accordance with the requirements of ECSS-Q-ST-30-11."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.2.5b","Requirement","ECSS-Q-ST-60_0480049",1,"Created","For wire link fuses, the current derating factor shall be 50 % with an additional derating of 0,2 %/°C for an increase in the temperature of fuse body above 25 °C."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.3.1a","Requirement","ECSS-Q-ST-60_0480050",1,"Created","The supplier shall perform a component evaluation in absence of an approved demonstration that a component has the ability to conform to the requirements for functional performance, quality, dependability, and environmental resistance as required for the project."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.3.1b","Requirement","ECSS-Q-ST-60_0480051",1,"Created","The supplier shall plan and carry out the evaluation."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.3.1c","Requirement","ECSS-Q-ST-60_0480052",1,"Created","The scope and planning of the component evaluation shall be derived from the results of an assessment of the design and intended application of the component. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.3.1d","Requirement","ECSS-Q-ST-60_0480053",1,"Created","An evaluation plan shall be sent to the customer for approval, and include the following elements:\n    1. Component Manufacturer Assessment,\n    2. Constructional Analysis,\n    3. Evaluation Testing,\n    4. Radiation Hardness. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.3.1e","Requirement","ECSS-Q-ST-60_0480054",1,"Created","In the definition of the evaluation programme any information including pertinent reliability, analysis and test data from the manufacturer of the component and previous use in comparable applications shall be considered."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.3.1f","Requirement","ECSS-Q-ST-60_0480055",1,"Created","Omission of any of these elements, or the introduction of alternative activities, shall be justified."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.3.1g","Requirement","ECSS-Q-ST-60_0480056",1,"Created","All tests and inspections shall be carried out on representative samples of the component type from the current production of the manufacturer selected for the component procurement for the flight hardware."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.3.1h","Requirement","ECSS-Q-ST-60_0480057",1,"Created","For programmable devices, the representativeness shall include the programming hardware tools and the compatibility of the software."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.3.1i","Requirement","ECSS-Q-ST-60_0480058",1,"Created","The supplier shall review the evaluation results to determine their impact on the content of the procurement specification which shall be amended as necessary."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.3.1j","Requirement","ECSS-Q-ST-60_0480059",1,"Created","The supplier shall summarize the evaluation results in the evaluation report and send it to the customer for approval.\n    ","NOTE For guidance for the assessment of the space environmental aspects refer to ECSS-E-ST-10-04 and ECSS-E-ST-10-12."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.3.2.2a","Requirement","ECSS-Q-ST-60_0480060",1,"Created","The supplier shall perform an evaluation against the ESCC basic specification no. 20200 and the ancillary specifications for dedicated component families and shall include, but not necessarily be limited to, a survey of:\n    1. The overall manufacturing facility and its organization and management,\n    2. The manufacturer’s system for inspection and manufacturing control including all relevant specifications, procedures, and internal documents,\n    3. The production line used for the component."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.3.2.2b","Requirement","ECSS-Q-ST-60_0480061",1,"Created","The complete manufacturer assessment, including the survey report and the associated corrective actions, shall be part of the evaluation report."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.3.3a","Requirement","ECSS-Q-ST-60_0480062",1,"Created","Constructional analysis shall be carried out on representative components. \n    ","NOTE The primary aim is to provide an early indication of a component’s constructional suitability for meeting the specified performances of the space project application."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.3.3b","Requirement","ECSS-Q-ST-60_0480063",1,"Created","The Constructional Analysis shall comprise destructive and non-destructive inspections, analyses, and testing, to identify:\n    1. Design and construction technology,\n    2. Materials used,\n    3. Inherent reliability aspects,\n    4. Quality of workmanship,\n    5. Potential hazards."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.3.3c","Requirement","ECSS-Q-ST-60_0480064",1,"Created","The findings of the analysis shall be contained within a Constructional Analysis Report and shall be included in the Evaluation Report."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.3.4a","Requirement","ECSS-Q-ST-60_0480065",1,"Created","The evaluation shall determine which inspections or tests are required to provide the confidence that the component type under evaluation, when assembled and tested in accordance with the procurement specification, successfully meets the project requirements."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.3.4b","Requirement","ECSS-Q-ST-60_0480066",1,"Created","The supplier shall review the already existing data in order to adapt and minimize the content of the evaluation testing while ensuring that there are inputs and pertinent results covering the following topics:\n    1. Endurance test (operating at elevated temperature and electrical stress),\n    2. Mechanical stress (shock, vibration, constant acceleration),\n    3. Environmental stress (thermal shock, temperature cycling, high and low temperature storage, humidity),\n    4. Assembly capability testing,\n    5. Radiation testing, for total dose and single event effects sensitivity.\n        ","NOTE For guidance refer to ESCC basic specification no. 22600 and the ancillary specifications for dedicated component families. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.4a","Requirement","ECSS-Q-ST-60_0480067",1,"Created","The supplier shall document the procedure for approval of each component type intended for use in flight products. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.4b","Requirement","ECSS-Q-ST-60_0480068",1,"Created","The approval of components shall be based on consideration of all pertinent data including both the electrical and environmental performance as well as the established quality and the dependability assurance requirements."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.4c","Requirement","ECSS-Q-ST-60_0480069",1,"Created","The supplier shall maintain a system of traceability of the acceptance and approval of each component used in flight products."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.4d","Requirement","ECSS-Q-ST-60_0480070",1,"Created","The approval process by the customer shall be organized as follows:\n    1. All space qualified parts by listing them in the DCL,\n    2. A PAD in conformance with Annex D is required for any other part,\n    3. A PAD in conformance with Annex D is required for space qualified parts when:\n        (a) additional controls are required (e.g. precap, buy-off, LAT or LVT, RVT, DPA),\n        (b) used outside the specified limits,\n        (c) specific tests are required during procurement as per Table 7-1,\n        (d) pure tin is used inside or outside the part."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.2.4e","Requirement","ECSS-Q-ST-60_0480071",1,"Created","When a PAD is required, the customer’s approval process shall include 2 steps:\n    1. step 1: approval of the part type and attached action plan, through the PAD process for the PDR.\n    2. step 2: approval of the results of the action plan defined during step 1 through the final approval of the PAD."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.1a","Requirement","ECSS-Q-ST-60_0480072",1,"Created","The supplier shall ensure that all procured components meet the programme requirements with respect to inspection, screening and tests."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.1b","Requirement","ECSS-Q-ST-60_0480073",1,"Created","Class 1 components shall meet the quality levels ands supplementary conditions specified in Table 7-1."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.1c","Requirement","ECSS-Q-ST-60_0480074",1,"Created","The supplier shall be responsible for manufacturer surveillance and control throughout the procurement programme."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.1d","Requirement","ECSS-Q-ST-60_0480075",1,"Created","For non qualified parts, the supplier shall put in place a configuration control system to ensure that any change of the product (e.g. mask, manufacturing and assembly process) affecting evaluation, performance, quality, reliability and interchangeability is communicated to him by the manufacturer (e.g. PCN)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.1e","Requirement","ECSS-Q-ST-60_0480076",1,"Created","The supplier shall ensure the compatibility of the change with its application."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.1f","Requirement","ECSS-Q-ST-60_0480077",1,"Created","The change shall be submitted to the customer for approval."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.1g","Requirement","ECSS-Q-ST-60_0480078",1,"Created","To reduce the risk of procuring counterfeit components, when parts are not directly procured from the manufacturer, the supplier shall procure parts only from distributors duly franchised by the parts manufacturer."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.2a","Requirement","ECSS-Q-ST-60_0480079",1,"Created","The supplier shall procure EEE components according to controlled specifications."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.2b","Requirement","ECSS-Q-ST-60_0480080",1,"Created","International specifications systems, recognized as suitable for space applications (e.g. ESCC, MIL), shall be used by the supplier. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.2c","Requirement","ECSS-Q-ST-60_0480081",1,"Created","Any new specification shall be prepared and designed by the supplier as per existing international specification systems (ESCC, MIL). Preference shall be given to ESCC format when agreed to by the manufacturer."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.2d","Requirement","ECSS-Q-ST-60_0480082",1,"Created","The content of any new specification shall be in conformance with Annex C."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.2e","Requirement","ECSS-Q-ST-60_0480083",1,"Created","The use of any new specification shall be submitted to the customer for approval through the approval process (see clause 4.2.4) "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.2f","Requirement","ECSS-Q-ST-60_0480084",1,"Created","Upon request, any new procurement specification prepared in the frame of the project, shall be delivered to the customer."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.2g","Requirement","ECSS-Q-ST-60_0480085",1,"Created","The supplier shall keep each procurement specification under configuration control."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.3a","Requirement","ECSS-Q-ST-60_0480086",1,"Created","All components to be incorporated into flight standard hardware shall be subjected to screening. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.3b","Requirement","ECSS-Q-ST-60_0480087",1,"Created","The screening test requirements shall be so designed that accumulated stress does not jeopardize component reliability. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.3c","Requirement","ECSS-Q-ST-60_0480088",1,"Created","All screening tests shall be performed at the component manufacturer’s premises or at a facility approved either by the qualification approval authority, where applicable (e.g. ESCC), or otherwise by the supplier."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.3d","Requirement","ECSS-Q-ST-60_0480089",1,"Created","The applicable quality levels defined in Table 7-1 shall apply."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.3e","Requirement","ECSS-Q-ST-60_0480090",1,"Created","For active parts (transistors, diodes) packaged in TO3, DO4 or DO5, the PIND test method shall be submitted to the customer’s approval."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.4a","Requirement","ECSS-Q-ST-60_0480091",1,"Created","The procurement entity shall carry out, at the manufacturer’s premises, a customer precap inspection for non-space qualified parts listed below:\n    1. Capacitors (ceramic, mica and plastic film)\n    2. Crystals\n    3. Oscillators\n    4. Discrete semiconductors (including diodes and transistors)\n    5. Filters\n    6. Fuses (cermet)\n    7. Inductors, coils (not applicable to in-house products)\n    8. Monolithic microcircuits (including MMICs)\n    9. Hybrid circuits\n    10. Relays\n    11. Resistors (high precision, fixed, metal foil - RNC90)\n    12. Switches (including mechanical and thermal)\n    13. Optoelectronic devices (e.g. opto-couplers, LEDs, CCDs and sensors)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.4b","Requirement","ECSS-Q-ST-60_0480092",1,"Created","The procurement entity shall carry out, at the manufacturer’s premises, a customer precap inspection on critical space qualified parts , including as a minimum relays, crystals, oscillators and hybrids."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.4c","Requirement","ECSS-Q-ST-60_0480093",1,"Created","When not covered by MIL or ESCC specifications, methods and accept/reject criteria for customer’s precap inspection shall be documented by a procedure to be presented to the customer, on request, for review."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.5a","Requirement","ECSS-Q-ST-60_0480094",1,"Created","The supplier shall ensure that any lot or datecode of EEE parts is submitted to a lot acceptance procedure (in line with applied normative systems) according to the following rules:\n    1. Space qualified parts: \n        (a) ESCC: user’s lot acceptance on the procured lot is not required due to periodic lot validation testing performed by the manufacturer.\n        (b) MIL: QCI or TCI performed by the manufacturer is in accordance with the quality level of the MIL specification.\n    2. Non-space qualified parts: \n        (a) The content of the lot acceptance is ESCC level LAT1 or level LAT2 or LVT (subgroups 1, 2 and 3) or comparable QCI. \n        (b) The lot acceptance may be replaced by the review of available data less than 2 years old and provided there have been no changes to the manufacturing process and no changes to the part design and construction.\n        (c) In case of partial available data, any complementary lot acceptance content is defined by the supplier within the PCB.\n        (d) The PCB documents and justifies any reduced lot acceptance based on available data for customer approval."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.5b","Requirement","ECSS-Q-ST-60_0480095",1,"Created","The sample size for lot acceptance which may be reduced in some cases, shall be submitted to the customer for approval through the approval process (see clause 4.2.4). "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.6a","Requirement","ECSS-Q-ST-60_0480096",1,"Created","The procurement entity shall carry out, at the manufacturer’s premises, a final customer source inspection for non-space qualified parts, based on inspections, tests and review activities to verify that the requirements of the purchase order are met prior to shipment of the flight parts."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.6b","Requirement","ECSS-Q-ST-60_0480097",1,"Created","The buy-off shall include:\n    1. External visual inspection,\n    2. Witnessing electrical measurements,\n    3. Verifying mechanical dimensions,\n    4. Review and verification of the data-package."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.6c","Permission","ECSS-Q-ST-60_0480449",1,"Created","The buy-off may be replaced by an incoming inspection at the procurement entity's facilities."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.6d","Requirement","ECSS-Q-ST-60_0480099",1,"Created","If the buy-off is replaced by an incoming inspection at the procurement entity's facilities, it shall be reported in the PAD submitted to the customer for approval."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.7a","Requirement","ECSS-Q-ST-60_0480100",1,"Created","The procurement entity shall perform incoming inspection at his premises on all components to verify conformance with the purchase order requirements."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.7b","Requirement","ECSS-Q-ST-60_0480101",1,"Created","The incoming inspection shall include the following items:\n    1. Marking control,\n    2. Quantity verification,\n    3. Packing checking,\n    4. Review of the manufacturer delivered documentation,\n    5. Additional tests based on the type of component, criticality and heritage with the manufacturer (e.g. solderability tests, electrical tests)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.7c","Requirement","ECSS-Q-ST-60_0480102",1,"Created","The incoming inspection shall be documented by a procedure to be sent, on request, to the customer for review."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.7d","Requirement","ECSS-Q-ST-60_0480103",1,"Created","If the parts have passed successfully a final CSI (or buy-off), the incoming inspection may be reduced. The minimum shall be:\n    1. Verification of the manufacturer’s CoC\n    2. Packing checking,\n    3. Quantity verification."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.7e","Requirement","ECSS-Q-ST-60_0480104",1,"Created","In case the incoming inspection has been performed by a procurement agent, the incoming inspection performed by the end-user, may be reduced. The minimum shall be:\n    1. Packing checking,\n    2. Quantity verification."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.8a","Requirement","ECSS-Q-ST-60_0480105",1,"Created","Radiation sensitive components, as defined in clause 4.2.2.4, and for which applicable existing test data is insufficient shall be subjected to RVT."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.8b","Requirement","ECSS-Q-ST-60_0480106",1,"Created","RVT shall be performed in accordance with internationally recognized standards, such as ESCC Basic Specifications No. 22900 and No 25100.\n    ","NOTE Additional information on test methods is given in MIL-STD-750 Test Method 1080, MIL-STD-883 Test Method 1019 and JEDEC JESD57."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.8c","Requirement","ECSS-Q-ST-60_0480107",1,"Created","In such a case, a PAD in conformance with Annex D shall be issued and processed as per clause 4.2.4."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.8d","Requirement","ECSS-Q-ST-60_0480108",1,"Created","The results of RVT shall be documented by a report. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.8e","Requirement","ECSS-Q-ST-60_0480109",1,"Created","When RVT is performed in the frame of the project, the supplier shall send the related report to the customer for information."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.9a","Requirement","ECSS-Q-ST-60_0480110",1,"Created","The DPA shall be performed on 3 samples per lot for non-space qualified parts belonging to the following categories:\n    1. Capacitors (ceramic, tantalum and variable)\n    2. Crystals\n    3. Oscillators\n    4. Discrete semiconductors (including diodes and transistors)\n    5. Filters\n    6. Monolithic microcircuits (including MMICs)\n    7. Hybrid circuits\n    8. Relays\n    9. Switches (including mechanical and thermal)\n    10. Optoelectronic devices (e.g. opto-couplers, LED’s, CCD’s and sensors)\n    11. Passive microwave devices (e.g. mixers, couplers, isolators and switches)"]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.9b","Requirement","ECSS-Q-ST-60_0480111",1,"Created","The DPA shall be performed on 3 samples per lot on critical space qualified parts, including as a minimum relays and oscillators. For other space qualified parts families, DPA is not required."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.9c","Requirement","ECSS-Q-ST-60_0480112",1,"Created","DPA may be carried out on representative samples of the components families when procured from the same manufacturer and same package without major change in the process, with a limited datecode range of 13 weeks. Such reductions shall be submitted to the customer for approval through the PAD process.\n    ","NOTE In complement of above conditions, for series of integrated circuits, series of thermal switches, series of active discrete and series of passive components (e.g. 54xxxx, 1N63xx, …), representative samples can be from the same family considering technology limit and their complexity."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.9d","Requirement","ECSS-Q-ST-60_0480113",1,"Created","The DPA sample size may be reduced in some cases which shall be submitted to the customer for approval through the PAD process."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.9e","Requirement","ECSS-Q-ST-60_0480114",1,"Created","The DPA process shall be documented by a procedure to be sent, on request, to the customer for review."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.9f","Requirement","ECSS-Q-ST-60_0480115",1,"Created","The supplier shall verify that the outcome of the DPA is satisfactory prior to the installation of the components into flight hardware."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.9g","Permission","ECSS-Q-ST-60_0480450",1,"Created","Independent laboratories may perform DPA when approved by the customer."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.9h","Permission","ECSS-Q-ST-60_0480451",1,"Created","DPA may be performed by the manufacturer if witnessed by the supplier (or approved representative)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.9i","Requirement","ECSS-Q-ST-60_0480118",1,"Created","For health and safety reasons, any test producing beryllium oxide dust shall be omitted."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.9j","Requirement","ECSS-Q-ST-60_0480119",1,"Created","The results of DPA shall be documented by a report sent to the customer, on request, for information."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.10a","Permission","ECSS-Q-ST-60_0480452",1,"Created","Components from a supplier’s or parts procurement agent’s stock may be used provided the following criteria are met:\n    1. The parts are stored according to the minimum conditions given in clause 4.4 ,\n    2. The minimum overall requirements (including screening) are in accordance with the project requirements, \n    3. The lot homogeneity and traceability can be demonstrated, \n    4. The EEE parts documentation is available and the content is acceptable in accordance with the project requirements (including radiation data, if necessary), \n    5. There are no open NCR’s and no unresolved alerts with respect to their date code."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.10b","Requirement","ECSS-Q-ST-60_0480121",1,"Created","For components meeting the above criteria, and which have a lot / date code exceeding the period defined in ECSS-Q-ST-60-14 clause 5, the relifing procedure ECSS-Q-ST-60-14 shall apply."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.11a","Requirement","ECSS-Q-ST-60_0480122",1,"Created","The manufacturer’s CoC shall be delivered to the parts procurer. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.11b","Requirement","ECSS-Q-ST-60_0480123",1,"Created","Any other data (i.e. LAT or LVT, QCI orTCI), defined in the applicable procurement documents, shall be available at the manufacturer’s facilities or delivered to the parts’ procurer in line with the purchase order. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.3.11c","Requirement","ECSS-Q-ST-60_0480124",1,"Created","For non qualified parts, the documentation minimum storage period shall be 10 years after delivery of components by the manufacturer. \n    ","NOTE For qualified parts, the documentation storage period is under the responsibility of the manufacturer and the qualifying authority."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.4a","Requirement","ECSS-Q-ST-60_0480125",1,"Created","The supplier shall establish and implement procedures for handling and storage of components in order to prevent possible degradation. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.4b","Requirement","ECSS-Q-ST-60_0480126",1,"Created","The procedures shall be applicable at any facility dealing with components for flight application."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.4c","Requirement","ECSS-Q-ST-60_0480127",1,"Created","On request, handling and storage procedures shall be sent to the customer for review."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.4d","Requirement","ECSS-Q-ST-60_0480128",1,"Created","As a minimum, the following areas shall be covered:\n    1. Control of the environment in accordance with ESCC Basic Specification No. 24900.\n    2. Measures and facilities to segregate and protect components during receiving inspection, storage, and delivery to manufacturing. \n    3. Control measures to ensure that electrostatic discharge susceptible components are identified and handled only by trained personnel using anti static packaging and tools."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.5.1a","Requirement","ECSS-Q-ST-60_0480129",1,"Created","The supplier shall establish and implement the requirements of this document including methods, organizations and documents used to control the selection and procurement of components in accordance with the requirements of ECSS-Q-ST-20."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.5.2a","Requirement","ECSS-Q-ST-60_0480130",1,"Created","The supplier shall establish and maintain a nonconformance control system in accordance with the general requirements in ECSS-Q-ST-20."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.5.2b","Requirement","ECSS-Q-ST-60_0480131",1,"Created","Any observed deviation of EEE components from requirements as laid down in applicable specifications, procedures and drawings shall be controlled by the nonconformance control system.\n    ","NOTE This includes failures, malfunctions, deficiencies and defects."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.5.2c","Requirement","ECSS-Q-ST-60_0480132",1,"Created","The nonconformance control system shall handle all nonconformances occurring on EEE components during:\n    1. Manufacture (if available), screening and acceptance tests, \n    2. Incoming inspection,\n    3. Integration and test of equipment,\n    4. Storage and handling."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.5.2d","Requirement","ECSS-Q-ST-60_0480133",1,"Created","For ESCC qualified components the supplier shall apply the ESCC basic specification no 22800."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.5.3a","Requirement","ECSS-Q-ST-60_0480134",1,"Created","The supplier shall take into account all received alerts from international alert systems, from manufacturers or sent by the customer and shall validate that there are no alerts on the proposed parts with respect to the batch information (including date-code). "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.5.3b","Requirement","ECSS-Q-ST-60_0480135",1,"Created","If alerts become available at a later stage, the supplier shall analyse the alerts, analyse the project risk and propose an action plan for customer approval."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.5.3c","Requirement","ECSS-Q-ST-60_0480136",1,"Created","The supplier shall initiate and distribute within the project notifications for all major problems arising on EEE parts during procurement, incoming inspection or during all levels of equipment manufacturing or testing, which are of general concern."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.5.4a","Requirement","ECSS-Q-ST-60_0480137",1,"Created","The traceability of individual components during manufacturing and testing shall be maintained as required by the procurement specifications."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.5.4b","Requirement","ECSS-Q-ST-60_0480138",1,"Created","The traceability shall be maintained through incoming, storage, and installation at the procurer and user of the component in accordance with programme PA requirements. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.5.4c","Requirement","ECSS-Q-ST-60_0480139",1,"Created","In any case, the traceability requirements imposed by the supplier on the EEE parts manufacturer or distributor shall allow managing the adequacy of the tests performed by the supplier (i.e. evaluation, lot validation, any additional test or inspection). "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.5.4d","Requirement","ECSS-Q-ST-60_0480140",1,"Created","The traceability of EEE parts during installation in equipment, shall be ensured by the supplier through maintaining the traceability to the manufacturer’s lot/datecode number of the EEE parts actually mounted. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.5.4e","Requirement","ECSS-Q-ST-60_0480141",1,"Created","If the as built DCL has not yet been delivered, the supplier shall be able to provide this information (part type actually installed with its relevant lot/datecode number) within one week."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.5.5a","Requirement","ECSS-Q-ST-60_0480142",1,"Created","If tests are performed by sampling, the sampled parts shall be selected so that they are representative of the lot distribution. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.5.5b","Requirement","ECSS-Q-ST-60_0480143",1,"Created","For radiation tests, the set of test samples used shall be a representative distribution for the wafer lot. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.6.1a","Requirement","ECSS-Q-ST-60_0480144",1,"Created","For the specific component types identified in clauses 4.6.2, 4.6.3, 4.6.4 and 4.6.5 reference shall be made to applicable standards, in addition to the requirements of this standard."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.6.2a","Requirement","ECSS-Q-ST-60_0480145",1,"Created","ECSS-Q-ST-60-02 shall apply for the design development."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.6.3a","Requirement","ECSS-Q-ST-60_0480146",1,"Created","ECSS-Q-ST-60-05 shall apply."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.6.4a","Requirement","ECSS-Q-ST-60_0480147",1,"Created","For FPGA, ECSS-Q-ST-60-02, shall apply for the design development. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.6.4b","Requirement","ECSS-Q-ST-60_0480148",1,"Created","The PAD shall allow traceability to the information related to the procurement of blank parts, the programming process and the acceptance of the programmed parts."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.6.4c","Permission","ECSS-Q-ST-60_0480453",1,"Created","The programming process and the acceptance of the programmed parts may be part of PCB, for customer approval, if not indicated in the PAD."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.6.4d","Requirement","ECSS-Q-ST-60_0480150",1,"Created","One time programmable components shall be submitted to a post-programming sequence. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.6.4e","Requirement","ECSS-Q-ST-60_0480151",1,"Created","A dynamic post-programming burn-in shall be applied to FPGA’s, in conformance with ESCC9000 subclause 8.21, except for the duration, that is 160 h minimum."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.6.4f","Requirement","ECSS-Q-ST-60_0480152",1,"Created","The supplier shall prepare a post-programming procedure for customer’s approval, depending on part types (including when necessary electrical tests, programming conditions and equipment, burn-in conditions, additional screening tests and specific marking after programming). "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.6.4g","Requirement","ECSS-Q-ST-60_0480153",1,"Created","The lot acceptance procedure, as defined in clause 4.3.5, shall be performed on devices coming from the flight lot and programmed using on the same kind of the hardware tools and compatible software."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.6.4h","Permission","ECSS-Q-ST-60_0480454",1,"Created","In case of several designs based on the same lot of blank parts, the lot acceptance procedure, as defined in clause,4.3.5, may be limited to one representative flight programmed design."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.6.5a","Requirement","ECSS-Q-ST-60_0480155",1,"Created","ECSS-Q-ST-60-12 shall apply."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","4.7a","Requirement","ECSS-Q-ST-60_0480156",1,"Created","Any result from inspection or control shall be documented (including, precap, lot acceptance, buy-off, incoming, relifing and complementary tests)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.1.1a","Requirement","ECSS-Q-ST-60_0480157",1,"Created","The supplier shall establish and implement throughout the duration of the business agreement a component programme which ensures that the requirements of the project as defined by the customer and the supplier in the related business agreement are in compliance with this standard."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.1.2.1a","Requirement","ECSS-Q-ST-60_0480158",1,"Created","The supplier shall identify the organization responsible for the management of the component programme, and describe the organization’s approaches (including the procurement system and its rationale) and capability to efficiently implement, manage, and control the component requirements."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.1.2.2a","Requirement","ECSS-Q-ST-60_0480159",1,"Created","The supplier shall prepare a compliance matrix to the clauses of this standard. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.1.2.2b","Requirement","ECSS-Q-ST-60_0480160",1,"Created","The supplier shall submit his compliance matrix to the customer for approval."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.1.3a","Requirement","ECSS-Q-ST-60_0480161",1,"Created","At supplier's level, the Parts Control Board (PCB) shall be chaired by a member of the supplier’s PA team with designated responsibility for components management. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.1.3b","Requirement","ECSS-Q-ST-60_0480162",1,"Created","The composition of the PCB shall as a minimum include additionally the suppliers’ parts engineer, the customer’s representative and the lower tier subcontractor parts engineers.\n    ","NOTE The approval of the selection and usage of EEE parts are implemented through Parts Control Boards (PCBs) held between the customer and the supplier (or lower tier subcontractor). "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.1.3c","Permission","ECSS-Q-ST-60_0480455",1,"Created","Other pertinent experts from the customer or suppliers may also participate, on request."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.1.3d","Requirement","ECSS-Q-ST-60_0480164",1,"Created","Depending on the progress of the program, the main PCB activities shall be:\n    1. Review and approval of the supplier's EEE component control plan and any associated documents\n    2. Parts approval including evaluation activities,\n    3. Problem assessment (e.g. alerts, nonconformances, RFD, RFW and delivery delays)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.1.4a","Requirement","ECSS-Q-ST-60_0480165",1,"Created","For each equipment, its supplier shall issue a DCL in an editable electronic format, identifying all component types needed. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.1.4b","Requirement","ECSS-Q-ST-60_0480166",1,"Created","This list shall be kept under configuration control (issue and identification of changes). "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.1.4c","Requirement","ECSS-Q-ST-60_0480167",1,"Created","The DCL shall be issued as a minimum at PDR and CDR (as designed) and at flight hardware delivery (as built)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.1.4d","Requirement","ECSS-Q-ST-60_0480168",1,"Created","After equipment CDR, all modifications affecting the PAD information shall be implemented, in the \"as design\" DCL, through the CN / CR process and submitted to the customer for approval.\n    ","NOTE For PAD generation, see 5.2.4."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.1.4e","Requirement","ECSS-Q-ST-60_0480169",1,"Created","The “as design” DCL shall be sent to the customer for approval."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.1.4f","Requirement","ECSS-Q-ST-60_0480170",1,"Created","Any change of parts during equipment manufacturing (e.g. type and manufacturer) shall be handled through RFWs submitted to the customer for approval."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.1.4g","Requirement","ECSS-Q-ST-60_0480171",1,"Created","The “as built” DCL reflecting the actual EEE parts assembled into the flight hardware and their date code, shall be provided to the customer for review at the delivery of the flight hardware."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.1.4h","Requirement","ECSS-Q-ST-60_0480172",1,"Created","The content of the DCL shall be in conformance with its DRD in Annex B."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.1.5a","Requirement","ECSS-Q-ST-60_0480173",1,"Created","EEE components used in GSE, which are physically and directly interfacing to flight hardware, shall meet the requirements of this document."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.1.5b","Requirement","ECSS-Q-ST-60_0480174",1,"Created","Flight hardware connectors interfaces to GSE shall be protected by connector savers."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.1a","Requirement","ECSS-Q-ST-60_0480175",1,"Created","The supplier shall ensure that the following requirements are met during his selection process:\n    1. Project requirements (e.g. quality levels, component policy, manufacturing and delivery schedules and budgets, and quantities), \n    2. Design requirements (e.g. component type, case, dimensions, and materials), \n    3. Production requirements (e.g. packaging, thermal and storage constraints, component mounting and process), \n    4. Operational requirements (e.g. electrical, mechanical, radiation, reliability, assembly, and lifetime).\n        ","NOTE The supplier of each product is responsible for the selection of components, which enable the performance, lifetime, environmental, material, safety, quality and reliability requirements of the product of which they forms a part, to be satisfied in all respects."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.1a","Requirement","ECSS-Q-ST-60_0480176",1,"Created","The supplier shall establish and maintain in his own facility, and ensure that his suppliers also establish and maintain, procedures for selecting and controlling all components intended for use in deliverable products. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.1b","Requirement","ECSS-Q-ST-60_0480177",1,"Created","Components shall be selected on the basis of proven qualification, characterization, and previous space experience and data, relevant with regard to the requirements for the programme, from manufacturers or sources (preferably European) employing effective Product Assurance Programmes in manufacturing and test. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.1c","Requirement","ECSS-Q-ST-60_0480178",1,"Created","Preference shall be given to components which necessitate the least evaluation or qualification effort. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.1d","Requirement","ECSS-Q-ST-60_0480179",1,"Created","When selecting items, the supplier shall check the current data, applicability of the basis of qualification, problem notifications and alerts, and adequacy of specifications. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.2a","Requirement","ECSS-Q-ST-60_0480180",1,"Created","The supplier shall ensure that non-hermetically sealed materials of components meet the requirements of ECSS-Q-ST-70 regarding off-gassing, out-gassing, flammability, toxicity and any other criteria specified for the intended use. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.2b","Requirement","ECSS-Q-ST-60_0480181",1,"Created","The supplier shall evaluate the robustness of selected EEE components against the stresses induced by the assembly techniques to be employed."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.2c","Requirement","ECSS-Q-ST-60_0480182",1,"Created","With respect to health and safety, beryllium oxide (except if identified in the procurement specification), cadmium, lithium, magnesium, mercury, zinc, radioactive material and all material which may cause safety hazard shall not be used."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.2d","Requirement","ECSS-Q-ST-60_0480183",1,"Created","For limited life duration, known instability, safety hazard or reliability risk reasons, the use of EEE components listed below shall not be used:\n    1. EEE components with pure tin (less than 3% Pb in case of SnPb alloy) used as a finish on the leads, terminations and external surfaces of components and packages. \n    2. Hollow core resistors,\n    3. Potentiometers (except for mechanism position monitoring),\n    4. Non-metallurgically bonded diodes,\n    5. Semiconductor dice with unglassivated on active area,\n    6. Wet slug tantalum capacitors other than capacitor construction using double seals and a tantalum case,\n    7. Any component whose internal construction uses metallurgic bonding with a melting temperature not compatible with the end-application mounting conditions,\n    8. Wire link fuses < 5A,\n    9. TO5 relays without double welding of the mechanism to the header or with any type of integrated diodes inside."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.2e","Requirement","ECSS-Q-ST-60_0480184",1,"Created","For limited life duration, known instability, safety hazards or reliability risk reasons, EEE components listed below shall not be used for new designs:\n    1. RNC90 > 100 kW,\n    2. TO3 and DO4/DO5 packages."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.2f","Permission","ECSS-Q-ST-60_0480456",1,"Created","The use of pure tin in internal cavities may be authorized, on a case-by-case basis, based on the demonstration that there is no alternative product and there is no risk (supported by a technical justification)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.2g","Requirement","ECSS-Q-ST-60_0480186",1,"Created","As per 5.2.2.2e., the justification of the use of pure tin shall be presented during a PCB for customer’s approval,"]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.2h","Requirement","ECSS-Q-ST-60_0480187",1,"Created","The use of pure tin (inside or outside the part) shall be declared in the PAD."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.3a","Requirement","ECSS-Q-ST-60_0480188",1,"Created","The radiation requirements for EEE components are project specific."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.3b","Requirement","ECSS-Q-ST-60_0480189",1,"Created","The supplier who is responsible for the design of the piece of hardware shall demonstrate the compliance of its components selection with the radiation constraints of the project. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.3c","Requirement","ECSS-Q-ST-60_0480190",1,"Created","For this demonstration, the supplier shall consider all types of radiation including cosmic (Heavy Ions), electromagnetic, trapped (charged particles - electrons, protons - in radiation belts) and solar (flares). "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.3d","Requirement","ECSS-Q-ST-60_0480191",1,"Created","Due consideration shall be given to the mission orbit and trajectory, the duration, the associated spatial and temporal variations of the radiation environment as well as all protective factors such as shielding. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.3e","Requirement","ECSS-Q-ST-60_0480192",1,"Created","The supplier shall assess the actual radiation tolerance of the selected components for compliance with the radiation requirements in term of total dose, displacement damage and Single Events Effects (SEE). "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.3f","Requirement","ECSS-Q-ST-60_0480193",1,"Created","The supplier shall identify components which are not compliant with the radiation requirements as critical radiation sensitive components. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.3g","Requirement","ECSS-Q-ST-60_0480194",1,"Created","The supplier shall implement a Radiation Hardness Assurance Programme, documented by a plan to be approved by the customer, for radiation sensitive components, covering the collection of all relevant information and specifying the necessary actions in terms of evaluation and procurement testing, planning and control. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.3h","Requirement","ECSS-Q-ST-60_0480195",1,"Created","The supplier shall issue an Equipment Radiation Analysis document identifying all sensitive components w.r.t. the relevant radiation effects, possibly their impact and giving an adequate engineering solution (e.g. local shielding, design solution, specific test, RVT) for the relevant equipment."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.3i","Requirement","ECSS-Q-ST-60_0480196",1,"Created","The Equipment Radiation Analysis document shall be submitted to the customer for approval.\n    ","NOTE More detailed information about the above requirements is given in ECSS-E-ST-10-12."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.4a","Requirement","ECSS-Q-ST-60_0480197",1,"Created","The supplier shall implement derating rules for components used in his designs in accordance with the requirements of ECSS-Q-ST-30-11. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.2.4b","Requirement","ECSS-Q-ST-60_0480198",1,"Created","For wire link fuses, the current derating factor shall be 50% with an additional derating of 0,2%/°C for an increase in the temperature of fuse body above 25°C."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.3.1a","Requirement","ECSS-Q-ST-60_0480199",1,"Created","The supplier shall perform a component evaluation in absence of an approved demonstration that a component has the ability to conform to the requirements for functional performance, quality, dependability, and environmental resistance as required for the project."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.3.1b","Requirement","ECSS-Q-ST-60_0480200",1,"Created","The supplier shall plan and carry out the evaluation."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.3.1c","Requirement","ECSS-Q-ST-60_0480201",1,"Created","The scope and planning of the component evaluation actions shall be derived from the results of an assessment of the design and intended application of the component. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.3.1d","Requirement","ECSS-Q-ST-60_0480202",1,"Created","An evaluation plan shall be sent to the customer for approval, and include the following elements:\n    1. Constructional Analysis,\n    2. Evaluation Testing,\n    3. Radiation Hardness. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.3.1e","Requirement","ECSS-Q-ST-60_0480203",1,"Created","In the definition of the evaluation programme any information including pertinent reliability, analysis and test data from the manufacturer of the component and previous use in comparable application shall be considered."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.3.1f","Requirement","ECSS-Q-ST-60_0480204",1,"Created","Omission of any of these elements, or the introduction of alternative activities, shall be justified."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.3.1g","Requirement","ECSS-Q-ST-60_0480205",1,"Created","All tests and inspections shall be carried out on representative samples of the component type from the current production of the manufacturer selected for the component procurement for the flight hardware."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.3.1h","Requirement","ECSS-Q-ST-60_0480206",1,"Created","For programmable devices, the representativeness shall include the programming hardware tools and the compatibility of the software."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.3.1i","Requirement","ECSS-Q-ST-60_0480207",1,"Created","The supplier shall review the evaluation results to determine their impact on the content of the procurement specification which shall be amended as necessary."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.3.1j","Requirement","ECSS-Q-ST-60_0480208",1,"Created","The supplier shall summarize the evaluation results in the evaluation report and sent it to the customer for approval.\n    ","NOTE For guidance for the assessment of the environmental aspects refer to ECSS-E-ST-10-04 and ECSS-E-ST-10-12."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.3.2a","Requirement","ECSS-Q-ST-60_0480209",1,"Created","A component manufacturer assessment is not required. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.3.3a","Requirement","ECSS-Q-ST-60_0480210",1,"Created","Constructional analysis shall be carried out on representative components. \n    ","NOTE The primary aim of constructional analysis is to provide an early indication of a component’s constructional suitability for meeting the specified performances of the space project application."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.3.3b","Requirement","ECSS-Q-ST-60_0480211",1,"Created","The Constructional Analysis shall comprise destructive and non-destructive inspections, analyses, and testing, to identify:\n    1. Design and construction technology,\n    2. Materials used,\n    3. Inherent reliability aspects,\n    4. Quality of workmanship,\n    5. Potential hazards."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.3.3c","Requirement","ECSS-Q-ST-60_0480212",1,"Created","The findings of the analysis shall be contained within a Constructional Analysis Report and shall be included in the Evaluation Report."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.3.4a","Requirement","ECSS-Q-ST-60_0480213",1,"Created","The evaluation shall determine which inspections or tests are required to provide the confidence that the component type under evaluation, when assembled and tested in accordance with the procurement specification, successfully meets the project requirements."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.3.4b","Requirement","ECSS-Q-ST-60_0480214",1,"Created","The supplier shall review the already existing data in order to adapt and minimize the content of the evaluation testing while ensuring that there are inputs and pertinent results covering the following topics:\n    1. Endurance test (operating at elevated temperature and electrical stress),\n    2. Mechanical stress (shock, vibration, constant acceleration),\n    3. Environmental stress (thermal shock, temperature cycling, high and low temperature storage, humidity),\n    4. Assembly capability testing,\n    5. Radiation testing, for total dose and single event effects sensitivity.\n        ","NOTE For guidance refer to ESCC basic specification no. 22600 and the ancillary specifications for dedicated component families. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.4a","Requirement","ECSS-Q-ST-60_0480215",1,"Created","The supplier shall document the procedure for approval of each component type intended for use in flight products. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.4b","Requirement","ECSS-Q-ST-60_0480216",1,"Created","The approval of components shall be based on consideration of all pertinent data including both the electrical and environmental performances as well as the established quality and the dependability assurance requirements."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.4c","Requirement","ECSS-Q-ST-60_0480217",1,"Created","The supplier shall maintain a system of traceability of the acceptance and approval of each component used in flight products."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.4d","Requirement","ECSS-Q-ST-60_0480218",1,"Created","The approval process by the customer shall be organized as follows:\n    1. All parts belonging to EPPL, NPSL or qualified according to quality levels defined in Table 7-2 are approved by listing them in the DCL,\n    2. A PAD in conformance with Annex D is required for any other part (including CECC parts),\n    3. A PAD in conformance with Annex D is also required for EPPL, NPSL or qualified parts when:\n        (a) additional controls are required (e.g. precap, buy-off, LAT or LVT, RVT, DPA),\n        (b) used outside the specified limits,\n        (c) specific tests are required during procurement as per Table 7-2,\n        (d) pure tin is used inside or outside the part.\n    4. A Justification Document is required for any commercial part, instead of PAD."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.2.4e","Requirement","ECSS-Q-ST-60_0480219",1,"Created","When a PAD or a Justification Document is required, the customer’s approval process shall include 2 steps:\n    1. step 1: approval of the part type and attached action plan, through the PAD or Justification Document process for the PDR.\n    2. step 2: approval of the results of the action plan defined during step 1 through the final approval of the PAD or the Justification Document."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.1a","Requirement","ECSS-Q-ST-60_0480220",1,"Created","The supplier shall ensure that all procured components meet the programme requirements with respect to inspection, screening and tests."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.1b","Requirement","ECSS-Q-ST-60_0480221",1,"Created","Class 2 components shall meet the quality levels and supplementary conditions specified in Table 7-2."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.1c","Requirement","ECSS-Q-ST-60_0480222",1,"Created","The supplier shall be responsible for manufacturer surveillance and control throughout the procurement programme."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.1d","Requirement","ECSS-Q-ST-60_0480223",1,"Created","For non qualified parts, the supplier shall put in place a configuration control system to ensure that any change of the product (e.g. mask, manufacturing and assembly process) affecting evaluation, performance, quality, reliability and interchangeability is communicated to him by the manufacturer (e.g. PCN)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.1e","Requirement","ECSS-Q-ST-60_0480224",1,"Created","The supplier shall ensure the compatibility of the change with its application."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.1f","Requirement","ECSS-Q-ST-60_0480225",1,"Created","The change shall be submitted to the customer for approval."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.1g","Requirement","ECSS-Q-ST-60_0480226",1,"Created","To reduce the risk of procuring counterfeit components, when parts are not directly procured from the manufacturer, the supplier shall procure parts only from distributors duly franchised by the parts manufacturer."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.2a","Requirement","ECSS-Q-ST-60_0480227",1,"Created","The supplier shall procure EEE components according to controlled specifications."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.2b","Requirement","ECSS-Q-ST-60_0480228",1,"Created","International specifications systems, new specifications or manufacturer’s datasheets under configuration shall be used by the supplier. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.2c","Requirement","ECSS-Q-ST-60_0480229",1,"Created","Any new specification shall be prepared and designed by the supplier as per existing international specification systems (ESCC, MIL). Preference shall be given to ESCC format when agreed to by the manufacturer."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.2d","Requirement","ECSS-Q-ST-60_0480230",1,"Created","The content of any new specification shall be in conformance with Annex C."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.2e","Requirement","ECSS-Q-ST-60_0480231",1,"Created","The use of any new specification or datasheet shall be submitted to the customer for approval through the approval process (see clause 5.2.4)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.2f","Requirement","ECSS-Q-ST-60_0480232",1,"Created","Upon request, any new procurement specification prepared in the frame of the project, shall be delivered to the customer."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.2g","Requirement","ECSS-Q-ST-60_0480233",1,"Created","The supplier shall keep each procurement specification or manufacturer’s datasheet under configuration control. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.3a","Requirement","ECSS-Q-ST-60_0480234",1,"Created","All components to be incorporated into flight standard hardware shall be subjected to screening. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.3b","Requirement","ECSS-Q-ST-60_0480235",1,"Created","The screening test requirements shall be so designed that accumulated stress does not jeopardize component reliability. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.3c","Requirement","ECSS-Q-ST-60_0480236",1,"Created","All screening tests shall be performed at the component manufacturer’s premises or at facility approved either by the qualification approval authority, where applicable (e.g. ESCC), or otherwise by the supplier.."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.3d","Requirement","ECSS-Q-ST-60_0480237",1,"Created","The applicable quality levels defined in Table 7-2 shall apply."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.3e","Requirement","ECSS-Q-ST-60_0480238",1,"Created","For active parts (transistors, diodes) packaged in TO3, DO4 or DO5, the PIND test method shall be submitted to the customer’s review. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.4a","Requirement","ECSS-Q-ST-60_0480239",1,"Created","The procurement entity shall carry out, at the manufacturer’s premises, a customer precap inspection for the following non-space qualified parts types: relays, crystals, oscillators and hybrids."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.4b","Requirement","ECSS-Q-ST-60_0480240",1,"Created","When not covered by MIL or ESCC specifications, methods and accept/reject criteria for customer’s precap inspection shall be documented by a procedure to be presented to the customer, on request, for review."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.5a","Requirement","ECSS-Q-ST-60_0480241",1,"Created","The supplier shall ensure that any lot or datecode of EEE parts is submitted to a lot acceptance procedure (in line with applied normative systems) according to the following rules:\n    1. Space qualified parts: \n        (a) ESCC: user’s lot acceptance on the procured lot is not required due to periodic lot validation testing performed by the manufacturer.\n        (b) MIL: QCI or TCI performed by the manufacturer is in accordance with the quality level of the MIL specification.\n    2. Non-space qualified parts: \n        (a) The content of the lot acceptance is defined according to the available data. \n        (b) The proposed lot acceptance is approved through the approval process (see clause 5.2.4). \n    3. Commercial parts:\n        (a) The content of the lot acceptance is defined according to information provided by the justification document. \n        (b) The proposed lot acceptance is approved through the approval process (see clause 5.2.4). "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.5b","Permission","ECSS-Q-ST-60_0480457",1,"Created","The sample size for lot acceptance which may be reduced in some cases is submitted to the customer for approval through the approval process (see clause 5.2.4)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.6a","Requirement","ECSS-Q-ST-60_0480243",1,"Created","The procurement entity shall carry out, at the manufacturer’s premises, a final customer source inspection for non-space qualified parts based on inspections, tests and review activities to verify that the requirements of the purchase order are met prior to shipment of the flight parts."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.6b","Requirement","ECSS-Q-ST-60_0480244",1,"Created","The buy-off shall include:\n    1. External visual inspection,\n    2. Witnessing electrical measurements,\n    3. Verifying mechanical dimensions,\n    4. Review and verification of the data-package."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.6c","Permission","ECSS-Q-ST-60_0480458",1,"Created","The buy-off may be replaced by an incoming inspection at the procurement entity's facilities; "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.6d","Requirement","ECSS-Q-ST-60_0480246",1,"Created","If the buy-off is replaced by an incoming inspection at the procurement entity's facilities; it shall be reported in the PAD which is submitted to the customer for approval."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.7a","Requirement","ECSS-Q-ST-60_0480247",1,"Created","The procurement entity shall perform incoming inspection at his premises on all components to verify conformance with the purchase order requirements."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.7b","Requirement","ECSS-Q-ST-60_0480248",1,"Created","The incoming inspection shall include the following items:\n    1. Marking control,\n    2. Quantity verification,\n    3. Packing checking,\n    4. Review of the manufacturer delivered documentation,\n    5. Additional tests based on the type of component, criticality and heritage with the manufacturer (e.g. solderability tests, electrical tests)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.7c","Requirement","ECSS-Q-ST-60_0480249",1,"Created","The incoming inspection shall be documented by a procedure to be presented, on request, to the customer for review."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.7d","Requirement","ECSS-Q-ST-60_0480250",1,"Created","If the parts have passed successfully a final CSI (or buy-off), the incoming inspection may be reduced. The minimum shall be:\n    1. Verification of the manufacturer’s CoC,\n    2. Packing checking,\n    3. Quantity verification."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.7e","Requirement","ECSS-Q-ST-60_0480251",1,"Created","In case the incoming inspection has been performed by a procurement agent, the incoming inspection performed by the end-user, may be reduced. The minimum shall be:\n    1. Packing checking,\n    2. Quantity verification"]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.8a","Requirement","ECSS-Q-ST-60_0480252",1,"Created","Radiation sensitive components, as defined in clause, 5.2.2.3 and for which applicable existing test data is insufficient shall be subjected to RVT."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.8b","Requirement","ECSS-Q-ST-60_0480253",1,"Created","RVT shall be performed in accordance with internationally recognized standards, such as ESCC Basic Specifications No. 22900 and No.25100.\n    ","NOTE Additional information on test methods is given in MIL-STD-750 Test Method 1080, MIL-STD-883 Test Method 1019 and JEDEC JESD57."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.8c","Requirement","ECSS-Q-ST-60_0480254",1,"Created","In such a case, a PAD in conformance with Annex D shall be issued and processed as per clause 5.2.4. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.8d","Requirement","ECSS-Q-ST-60_0480255",1,"Created","The results of RVT shall be documented by a report. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.8e","Requirement","ECSS-Q-ST-60_0480256",1,"Created","When RVT is performed in the frame of the project, the supplier shall send the related report to the customer for information."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.9a","Requirement","ECSS-Q-ST-60_0480257",1,"Created","The DPA shall be performed on 3 samples per lot for the following non-space qualified parts types: as a minimum relays, oscillators and commercial parts."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.9b","Requirement","ECSS-Q-ST-60_0480258",1,"Created","DPA may be carried out on representative samples of the components families when procured from the same manufacturer and same package without major change in the process, with a limited datecode range of 13 weeks. Such reductions shall be submitted to the customer for approval through the PAD (or Justification document) process.\n    ","NOTE In complement of above conditions, for series of integrated circuits, series of thermal switches, series of active discrete and series of passive components (e.g. 54xxxx, 1N63xx, …), representative samples can be from the same family considering technology limit and their complexity."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.9c","Requirement","ECSS-Q-ST-60_0480259",1,"Created","The DPA sample size may be reduced in some cases which shall be submitted to the customer for approval through the PAD (or Justification document) process."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.9d","Requirement","ECSS-Q-ST-60_0480260",1,"Created","The DPA process shall be documented by a procedure to be sent, on request, to the customer for review."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.9e","Requirement","ECSS-Q-ST-60_0480261",1,"Created","The supplier shall verify that the outcome of the DPA is satisfactory prior to the installation of the components into flight hardware."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.9f","Permission","ECSS-Q-ST-60_0480459",1,"Created","Independent laboratories may perform DPA when approved by the customer."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.9g","Permission","ECSS-Q-ST-60_0480460",1,"Created","DPA may be performed by the manufacturer if witnessed by the supplier (or approved representative)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.9h","Requirement","ECSS-Q-ST-60_0480264",1,"Created","For health and safety reasons, any test producing beryllium oxide dust shall be omitted."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.9i","Requirement","ECSS-Q-ST-60_0480265",1,"Created","The results of DPA shall be documented by a report sent to the customer, on request, for information."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.10a","Permission","ECSS-Q-ST-60_0480461",1,"Created","Components from a supplier’s or parts procurement agent’s stock may be used provided the following criteria are met:\n    1. The parts are stored according to the minimum conditions given in clause 5.4,\n    2. The minimum overall requirements (including screening) are in accordance with the project requirements, \n    3. The lot homogeneity and traceability can be demonstrated, \n    4. The EEE parts documentation is available and the content is acceptable in accordance with the project requirements (including radiation data, if necessary), \n    5. There are no open NCR’s and no unresolved alerts with respect to their date code."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.10b","Requirement","ECSS-Q-ST-60_0480267",1,"Created","For components meeting the above criteria, and which have a lot / date code exceeding the period defined in ECSS-Q-ST-60-14 clause 5, the relifing procedure ECSS-Q-ST-60-14 shall apply."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.11a","Requirement","ECSS-Q-ST-60_0480268",1,"Created","The manufacturer’s CoC shall be delivered to the parts procurer. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.11b","Requirement","ECSS-Q-ST-60_0480269",1,"Created","Any other data (i.e. LAT or LVT, QCI or TCI), defined in the applicable procurement documents, shall be available at the manufacturer’s facilities or delivered to the parts’ procurer in line with the purchase order. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.3.11c","Requirement","ECSS-Q-ST-60_0480270",1,"Created","For non qualified parts, the documentation minimum storage period shall be 10 years after delivery of components by the manufacturer. \n    ","NOTE For qualified parts, the documentation storage period is under the responsibility of the manufacturer and the qualifying authority."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.4a","Requirement","ECSS-Q-ST-60_0480271",1,"Created","The supplier shall establish and implement procedures for handling and storage of components in order to prevent possible degradation. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.4b","Requirement","ECSS-Q-ST-60_0480272",1,"Created","The procedures shall be applicable at any facility dealing with components for flight application."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.4c","Requirement","ECSS-Q-ST-60_0480273",1,"Created","On request, handling and storage procedures shall be sent to the customer for review."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.4d","Requirement","ECSS-Q-ST-60_0480274",1,"Created","As a minimum, the following areas shall be covered:\n    1. Control of the environment in accordance with ESCC Basic Specification No. 24900.\n    2. Measures and facilities to segregate and protect components during receiving inspection, storage, and delivery to manufacturing. \n    3. Control measures to ensure that electrostatic discharge susceptible components are identified and handled only by trained personnel using anti static packaging and tools."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.5.1a","Requirement","ECSS-Q-ST-60_0480275",1,"Created","The supplier shall establish and implement the requirements of this document including methods, organizations and documents used to control the selection and procurement of components in accordance with the requirements of ECSS-Q-ST-20."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.5.2a","Requirement","ECSS-Q-ST-60_0480276",1,"Created","The supplier shall establish and maintain a nonconformance control system in accordance with the general requirements in ECSS-Q-ST-20."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.5.2b","Requirement","ECSS-Q-ST-60_0480277",1,"Created","Any observed deviation of EEE components from requirements as laid down in applicable specifications, procedures and drawings shall be controlled by the nonconformance control system.\n    ","NOTE This includes failures, malfunctions, deficiencies and defects."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.5.2c","Requirement","ECSS-Q-ST-60_0480278",1,"Created","The nonconformance control system shall handle all nonconformances occurring on EEE components during: \n    1. Manufacture (if available), screening and acceptance tests, \n    2. Incoming inspection,\n    3. Integration and test of equipment,\n    4. Storage and handling."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.5.2d","Requirement","ECSS-Q-ST-60_0480279",1,"Created","For ESCC qualified components the supplier shall apply the ESCC basic specification no 22800."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.5.3a","Requirement","ECSS-Q-ST-60_0480280",1,"Created","The supplier shall take into account all received alerts from international alert systems, from manufacturers or sent by the customer and shall validate that there are no alert on the proposed parts with respect to the batch information (including date-code). "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.5.3b","Requirement","ECSS-Q-ST-60_0480281",1,"Created","If alerts become available at a later stage, the supplier shall analyse the alerts, analyse the project risk and propose an action plan for customer approval. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.5.4a","Requirement","ECSS-Q-ST-60_0480282",1,"Created","The traceability of individual components during manufacturing and testing shall be maintained as required by the procurement specifications."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.5.4b","Requirement","ECSS-Q-ST-60_0480283",1,"Created","The traceability shall be maintained through incoming, storage, and installation at the procurer and user of the component in accordance with programme PA requirements. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.5.4c","Requirement","ECSS-Q-ST-60_0480284",1,"Created","In any case, the traceability requirements imposed by the supplier on the EEE parts manufacturer or distributor shall allow managing the adequacy of the tests performed by the supplier (i.e. evaluation, lot validation, any additional test or inspection). "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.5.4d","Requirement","ECSS-Q-ST-60_0480285",1,"Created","The traceability of EEE parts during installation in equipment, shall be ensured by the supplier through maintaining traceability to the manufacturer lot/datecode number of the EEE parts actually mounted. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.5.4e","Requirement","ECSS-Q-ST-60_0480286",1,"Created","If the as built DCL has not yet been delivered, the supplier shall be able to provide this information (part type actually installed with its relevant lot/datecode number) within one week. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.5.5a","Requirement","ECSS-Q-ST-60_0480287",1,"Created","For radiation tests, the set of test samples used shall be a representative distribution for the wafer lot."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.6.1a","Requirement","ECSS-Q-ST-60_0480288",1,"Created","For the specific component types identified in clauses, 5.6.2, 5.6.3, 5.6.4 and 5.6.5 reference shall be made to applicable standards, in addition to the requirements of this standard."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.6.2a","Requirement","ECSS-Q-ST-60_0480289",1,"Created","ECSS-Q-ST-60-02 shall apply for the design development. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.6.3a","Requirement","ECSS-Q-ST-60_0480290",1,"Created","ECSS-Q-ST-60-05 shall apply. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.6.4a","Requirement","ECSS-Q-ST-60_0480291",1,"Created","For FPGA, ECSS-Q-ST-60-02, shall apply for the design development. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.6.4b","Requirement","ECSS-Q-ST-60_0480292",1,"Created","The PAD shall allow traceability to the information related to the procurement of blank parts, the programming and the acceptance of the programmed parts."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.6.4c","Permission","ECSS-Q-ST-60_0480462",1,"Created","The programming and the acceptance of the programmed parts may be part of PCB, for customer approval, if not indicated in the PAD."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.6.4d","Requirement","ECSS-Q-ST-60_0480294",1,"Created","One time programmable components shall be submitted to a post-programming sequence. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.6.4e","Requirement","ECSS-Q-ST-60_0480295",1,"Created","A dynamic post-programming burn-in shall be applied to FPGA’s, in conformance with ESCC9000 subclause 8.21, except for the duration, that is 160 h minimum."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.6.4f","Requirement","ECSS-Q-ST-60_0480296",1,"Created","The supplier shall prepare a post-programming procedure for customer’s approval, depending on part types (including when necessary electrical tests, programming conditions and equipment, burn-in conditions, additional screening tests and specific marking after programming)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.6.4g","Requirement","ECSS-Q-ST-60_0480297",1,"Created","The lot acceptance procedure, as defined in clause 5.3.5, shall be performed on devices coming from the flight lot and programmed using on the same kind of hardware tools and compatible software."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.6.4h","Permission","ECSS-Q-ST-60_0480463",1,"Created","In case of several designs based on the same lot of blank parts, the lot acceptance procedure, as defined in clause 5.3.5, may be limited to one representative flight programmed design."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.6.5a","Requirement","ECSS-Q-ST-60_0480299",1,"Created","ECSS-Q-ST-60-12 shall apply. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","5.7a","Requirement","ECSS-Q-ST-60_0480300",1,"Created","Any result from inspection or control shall be documented (including, precap, lot acceptance, buy-off, incoming, relifing and complementary tests)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.1.1a","Requirement","ECSS-Q-ST-60_0480301",1,"Created","The supplier shall establish and implement throughout the duration of the business agreement a component programme which ensures that the requirements of the project as defined by the customer and the supplier in the related business agreement are in compliance with this standard."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.1.2.1a","Requirement","ECSS-Q-ST-60_0480302",1,"Created","The supplier shall identify the organization responsible for the management of the component programme, and describe the organization’s approaches (including the procurement system and its rationale) and capability to efficiently implement, manage, and control the component requirements."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.1.2.2a","Requirement","ECSS-Q-ST-60_0480303",1,"Created","The supplier shall prepare a compliance matrix to the clauses of this standard. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.1.2.2b","Requirement","ECSS-Q-ST-60_0480304",1,"Created","The supplier shall submit his compliance matrix to the customer for approval."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.1.3a","Requirement","ECSS-Q-ST-60_0480305",1,"Created","A PCB is not required."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.1.4a","Requirement","ECSS-Q-ST-60_0480306",1,"Created","For each equipment, its supplier shall issue a DCL in an editable electronic format, identifying all component types needed. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.1.4b","Requirement","ECSS-Q-ST-60_0480307",1,"Created","The DCL shall be kept under configuration control (issue and identification of changes). "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.1.4c","Requirement","ECSS-Q-ST-60_0480308",1,"Created","The DCL shall be issued as a minimum at PDR and CDR (as designed) ."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.1.4d","Requirement","ECSS-Q-ST-60_0480309",1,"Created","After equipment CDR, all modifications affecting the PAD information shall be implemented, in the \"as design\" DCL, through the CN / CR process and submitted to the customer for approval.\n    ","NOTE For PAD generation, see 6.2.4d."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.1.4e","Requirement","ECSS-Q-ST-60_0480310",1,"Created","The “as design” DCL shall be sent to the customer for approval. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.1.4f","Requirement","ECSS-Q-ST-60_0480311",1,"Created","Any change of parts during equipment manufacturing (e.g. type and manufacturer) shall be handled through RFWs submitted to the customer for approval."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.1.4g","Requirement","ECSS-Q-ST-60_0480312",1,"Created","The content of the DCL shall be in conformance with the DRD in Annex B."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.1.5a","Requirement","ECSS-Q-ST-60_0480313",1,"Created","EEE components used in GSE, which are physically and directly interfacing to flight hardware, shall meet the requirements of this document."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.1.5b","Requirement","ECSS-Q-ST-60_0480314",1,"Created","Flight hardware connectors interfaces to GSE shall be protected by connector savers."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.1a","Requirement","ECSS-Q-ST-60_0480315",1,"Created","The supplier shall ensure that the following requirements are met during his selection process:\n    1. Project requirements (e.g. quality levels, component policy, manufacturing and delivery schedules and budgets, quantities),\n    2. Design requirements (e.g. component type, case, dimensions, materials),\n    3. Production requirements (e.g. packaging, thermal and storage constraints, component mounting process),\n    4. Operational requirements (e.g. electrical, mechanical, radiation, reliability, assembly, lifetime).\n        ","NOTE The supplier of each product is responsible for the selection of components, which enable the performance, lifetime, environmental, material, safety, quality and reliability requirements of the product of which they form a part, to be satisfied in all respects."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.1a","Requirement","ECSS-Q-ST-60_0480316",1,"Created","The supplier shall establish and maintain in his own facility, and ensure that his suppliers also establish and maintain, procedures for selecting and controlling all components intended for use in deliverable products. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.1b","Requirement","ECSS-Q-ST-60_0480317",1,"Created","Components shall be selected on the basis of proven qualification, characterization, and previous space experience and data, relevant with regard to the requirements for the programme, from manufacturers or sources (preferably European) employing effective Product Assurance Programmes in manufacturing and test. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.1c","Requirement","ECSS-Q-ST-60_0480318",1,"Created","Preference shall be given to components which necessitate the least evaluation or qualification effort. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.1d","Requirement","ECSS-Q-ST-60_0480319",1,"Created","When selecting items, the supplier shall check the current data, applicability of the basis of qualification, problem notifications and alerts, and adequacy of specifications. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.2a","Requirement","ECSS-Q-ST-60_0480320",1,"Created","The supplier shall ensure that non-hermetically sealed materials of components meet the requirements of ECSS-Q-ST-70 regarding off-gassing, out-gassing, flammability, toxicity and any other criteria specified for the intended use. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.2b","Requirement","ECSS-Q-ST-60_0480321",1,"Created","The supplier shall evaluate the robustness of selected EEE components against the stresses induced by the assembly techniques to be employed."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.2c","Requirement","ECSS-Q-ST-60_0480322",1,"Created","With respect to health and safety, beryllium oxide (except if identified in the procurement specification), cadmium, lithium, magnesium, mercury, zinc, radioactive material and all material which may cause safety hazard shall not be used."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.2d","Requirement","ECSS-Q-ST-60_0480323",1,"Created","For limited life duration , known instability, safety hazard or reliability risk reasons, the use of EEE components listed below shall not be used:\n    1. EEE components with pure tin (less than 3% Pb in case of SnPb alloy) used as a finish on the leads, terminations and external surfaces of components and packages,\n    2. Hollow core resistors,\n    3. Potentiometers (except for mechanism position monitoring),\n    4. Non-metallurgically bonded diodes,\n    5. Semiconductor dice with unglassivated active area,\n    6. Wet slug tantalum capacitors other than capacitor construction using double seals and a tantalum case,\n    7. Any component whose internal construction uses metallurgic bonding with a melting temperature not compatible with the end-application mounting conditions,\n    8. Wire link fuses < 5 A,\n    9. TO5 relays without double welding of the mechanism to the header or with any type of integrated diodes inside."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.2e","Requirement","ECSS-Q-ST-60_0480324",1,"Created","For limited life duration, known instability, safety hazard or reliability risk reasons, the use of EEE components listed below shall not be used for new designs:\n    1. RNC90 > 100 kW,\n    2. TO3 and DO4/DO5 packages."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.2f","Permission","ECSS-Q-ST-60_0480464",1,"Created","The use of pure tin in internal cavities may be authorized, on a case-by-case basis, based on the demonstration that there is no alternative product and there is no risk (supported by a technical justification)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.2g","Requirement","ECSS-Q-ST-60_0480326",1,"Created","As per 6.2.2.2e, the justification of the use of pure tin shall be presented during a PCB for customer’s approval."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.2h","Requirement","ECSS-Q-ST-60_0480327",1,"Created","The use of pure tin (inside or outside the part) shall be declared in the PAD."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.3a","Requirement","ECSS-Q-ST-60_0480328",1,"Created","Reference documents for the selection of components are not prescribed."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.4a","Requirement","ECSS-Q-ST-60_0480329",1,"Created","The radiation requirements for EEE components are project specific."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.4b","Requirement","ECSS-Q-ST-60_0480330",1,"Created","The supplier who is responsible for the design of the piece of hardware shall demonstrate the compliance of its components selection with the radiation constraints of the project. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.4c","Requirement","ECSS-Q-ST-60_0480331",1,"Created","For this demonstration, the supplier shall consider all types of radiation including cosmic (Heavy Ions), electromagnetic, trapped (charged particles - electrons, protons - in radiation belts) and solar (flares). "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.4d","Requirement","ECSS-Q-ST-60_0480332",1,"Created","Due consideration shall be given to the mission orbit and trajectory, the duration, the associated spatial and temporal variations of the radiation environment as well as all protective factors such as shielding. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.4e","Requirement","ECSS-Q-ST-60_0480333",1,"Created","The supplier shall assess the actual radiation tolerance of the selected components for compliance with the radiation requirements in term of total dose, displacement damage and Single Events Effects (SEE). "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.4f","Requirement","ECSS-Q-ST-60_0480334",1,"Created","The supplier shall identify components which are not compliant with the radiation requirements as critical radiation sensitive components. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.4g","Requirement","ECSS-Q-ST-60_0480335",1,"Created","The supplier shall implement a Radiation Hardness Assurance Programme, documented by a plan to be approved by the customer, for radiation sensitive components, covering the collection of all relevant information and specifying the necessary actions in terms of evaluation and procurement testing, planning and control. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.4h","Requirement","ECSS-Q-ST-60_0480336",1,"Created","The supplier shall issue an Equipment Radiation Analysis document identifying all sensitive components w.r.t. the relevant radiation effects, possibly their impact and giving an adequate engineering solution (e.g. shielding, design solution, specific test, and RVT) or the relevant equipment."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.4i","Requirement","ECSS-Q-ST-60_0480337",1,"Created","The Equipment Radiation Analysis document shall be submitted to the customer for approval.\n    ","NOTE More detailed information about the above requirements is given in ECSS-E-ST-10-12."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.5a","Requirement","ECSS-Q-ST-60_0480338",1,"Created","The supplier shall implement derating rules for components used in his designs in accordance with the requirements of ECSS-Q-ST-30-11."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.2.5b","Requirement","ECSS-Q-ST-60_0480339",1,"Created","For wire link fuses, the current derating factor shall be 50% with an additional derating of 0,2%/°C for an increase in the temperature of fuse body above 25°C."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.3.1a","Requirement","ECSS-Q-ST-60_0480340",1,"Created","The supplier shall perform a component evaluation in absence of an approved demonstration that a component has the ability to conform to the requirements for functional performance, quality, dependability, and environmental resistance as required for the project."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.3.1b","Requirement","ECSS-Q-ST-60_0480341",1,"Created","The supplier shall plan and carry out the evaluation."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.3.1c","Requirement","ECSS-Q-ST-60_0480342",1,"Created","The scope and planning of the component evaluation actions shall be derived from the results of an assessment of the design and intended application of the needed component. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.3.1d","Requirement","ECSS-Q-ST-60_0480343",1,"Created","An evaluation plan shall be sent to the customer for approval, and include the following elements:\n    1. Constructional Analysis,\n    2. Evaluation Testing,\n    3. Radiation Hardness. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.3.1e","Requirement","ECSS-Q-ST-60_0480344",1,"Created","In the definition of the evaluation programme any information including pertinent reliability, analysis and test data from the manufacturer of the component and previous use in comparable application shall be considered."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.3.1f","Requirement","ECSS-Q-ST-60_0480345",1,"Created","Omission of any of these elements, or the introduction of alternative activities, shall be justified."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.3.1g","Requirement","ECSS-Q-ST-60_0480346",1,"Created","All tests and inspections shall be carried out on representative samples of the component type from the current production of the manufacturer selected for the component procurement for the flight hardware."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.3.1h","Requirement","ECSS-Q-ST-60_0480347",1,"Created","For programmable devices, the representativeness shall include the programming hardware tools and the compatibility of the software."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.3.1i","Requirement","ECSS-Q-ST-60_0480348",1,"Created","The supplier shall review the evaluation results to determine their impact on the content of the procurement specification which shall be amended as necessary."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.3.1j","Requirement","ECSS-Q-ST-60_0480349",1,"Created","The supplier shall summarize the evaluation results in the evaluation report and sent it to the customer for approval."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.3.1k","Requirement","ECSS-Q-ST-60_0480350",1,"Created","It shall be reviewed to determine if they will have an impact on the content of the procurement specification.\n    ","NOTE For guidance for the assessment of the environmental aspects refer to ECSS-E-ST-10-04 and ECSS E-ST-10-12."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.3.2a","Requirement","ECSS-Q-ST-60_0480351",1,"Created","A component manufacturer assessment is not required. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.3.3a","Requirement","ECSS-Q-ST-60_0480352",1,"Created","Constructional analysis shall be carried out on representative components.\n    ","NOTE The primary aim is to provide an early indication of a component’s constructional suitability for meeting the specified performances of the space project application."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.3.3b","Requirement","ECSS-Q-ST-60_0480353",1,"Created","The Constructional Analysis shall comprise destructive and non-destructive inspections, analyses, and testing, to identify:\n    1. Design and construction technology,\n    2. Materials used,\n    3. Inherent reliability aspects,\n    4. Quality of workmanship,\n    5. Potential hazards."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.3.3c","Requirement","ECSS-Q-ST-60_0480354",1,"Created","The findings of the analysis shall be contained within a Constructional Analysis Report and shall be included in the Evaluation Report."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.3.4a","Requirement","ECSS-Q-ST-60_0480355",1,"Created","The evaluation shall determine which inspections or tests are required to provide the confidence that the component type under evaluation, when assembled and tested in accordance with the procurement specification, successfully meets the project requirements."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.3.4b","Requirement","ECSS-Q-ST-60_0480356",1,"Created","The supplier shall review the already existing data in order to adapt and minimize the content of the evaluation testing while ensuring that there are inputs and pertinent results covering the following topics:\n    1. Endurance test (operating at elevated temperature and electrical stress),\n    2. Mechanical stress (shock, vibration, constant acceleration),\n    3. Environmental stress (thermal shock, temperature cycling, high and low temperature storage, humidity),\n    4. Assembly capability testing,\n    5. Radiation testing, for total dose and single event effects sensitivity.\n        ","NOTE For guidance refer to ESCC basic specification no. 22600 and the ancillary specifications for dedicated component families. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.4a","Requirement","ECSS-Q-ST-60_0480357",1,"Created","The supplier shall document the procedure for approval of each component type intended for use in flight products. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.4b","Requirement","ECSS-Q-ST-60_0480358",1,"Created","The approval of components shall be based on consideration of all pertinent data including both the electrical and environmental performances as well as the established quality and the dependability assurance requirements."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.4c","Requirement","ECSS-Q-ST-60_0480359",1,"Created","The supplier shall maintain a system of traceability of the acceptance and approval of each component used in flight products."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.4d","Requirement","ECSS-Q-ST-60_0480360",1,"Created","The approval process by the customer shall be organized as follows:\n    1. All parts are approved by listing then in the DCL,\n    2. A PAD in conformance with Annex D is required for parts when:\n        (a) additional controls are required (e.g. precap, buy-off, LAT or LVT, RVT, DPA),\n        (b) used outside the specified limits,\n        (c) specific tests are required during procurement as per Table 7-3.\n        (d) pure tin is used inside or outside the part\n    3. Justification Document is required for any commercial part, instead of PAD."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.2.4e","Requirement","ECSS-Q-ST-60_0480361",1,"Created","When a PAD or a Justification Document is required, the customer’s approval process shall include 2 steps:\n    1. step 1: approval of the part type and attached action plan, through the PAD or Justification Document process for the PDR.\n    2. step 2: approval of the results of the action plan defined during step 1 through the final approval of the PAD or the Justification Document."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.1a","Requirement","ECSS-Q-ST-60_0480362",1,"Created","The supplier shall ensure that all procured components meet the programme requirements with respect to inspection, screening and tests."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.1b","Requirement","ECSS-Q-ST-60_0480363",1,"Created","Class 3 components shall meet the quality levels and supplementary conditions specified in Table 7-3."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.1c","Requirement","ECSS-Q-ST-60_0480364",1,"Created","The supplier shall be responsible for manufacturer surveillance and control throughout the procurement programme."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.1d","Requirement","ECSS-Q-ST-60_0480365",1,"Created","To reduce the risk of procuring counterfeit components, when parts are not directly procured from the manufacturer, the supplier shall procure parts only from distributors duly franchised by the parts manufacturer."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.2a","Requirement","ECSS-Q-ST-60_0480366",1,"Created","The supplier shall procure EEE components according to controlled specifications."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.2b","Requirement","ECSS-Q-ST-60_0480367",1,"Created","International specifications systems, new specifications or manufacturer’s datasheets under configuration shall be used by the supplier. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.2c","Requirement","ECSS-Q-ST-60_0480368",1,"Created","Any new specification shall be prepared and designed by the supplier as per existing international specification systems (ESCC, MIL). Preference shall be given to ESCC format when agreed to by the manufacturer."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.2d","Requirement","ECSS-Q-ST-60_0480369",1,"Created","The content of any new specification shall be in conformance with the procurement specification DRD in Annex C."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.2e","Requirement","ECSS-Q-ST-60_0480370",1,"Created","The use of any new specification or datasheet shall be submitted to the customer for review through the approval process (see clause 6.2.4)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.2f","Requirement","ECSS-Q-ST-60_0480371",1,"Created","Upon request, any new procurement specification prepared in the frame of the project, shall be delivered to the customer."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.2g","Requirement","ECSS-Q-ST-60_0480372",1,"Created","The supplier shall keep each procurement specification or manufacturer’s datasheet under configuration control."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.3a","Requirement","ECSS-Q-ST-60_0480373",1,"Created","All components to be incorporated into flight standard hardware shall be subjected to screening."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.3b","Requirement","ECSS-Q-ST-60_0480374",1,"Created","The screening test requirements shall be so designed that accumulated stress does not jeopardize component reliability. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.3c","Requirement","ECSS-Q-ST-60_0480375",1,"Created","All screening tests shall be performed at the component manufacturer’s premises or at a facility approved either by the qualification approval authority, where applicable (e.g. ESCC), or otherwise by the supplier ."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.3d","Requirement","ECSS-Q-ST-60_0480376",1,"Created","The applicable quality levels defined in Table 7-3 shall apply."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.3e","Requirement","ECSS-Q-ST-60_0480377",1,"Created","For active parts (transistors, diodes) packaged in TO3, DO4 or DO5, the PIND test method shall be submitted to the customer’s review. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.4a","Requirement","ECSS-Q-ST-60_0480378",1,"Created","A customer precap is not required."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.5a","Requirement","ECSS-Q-ST-60_0480379",1,"Created","The supplier shall ensure that any lot or datecode of EEE parts is submitted to a lot acceptance procedure (in line with applied normative systems) according to the following rules:\n    1. Space qualified parts: \n        (a) ESCC: user’s lot acceptance on the procured lot is not required due to periodic lot validation testing performed by the manufacturer.\n        (b) MIL: QCI or TCI performed by the manufacturer is in accordance with the quality level of the MIL specification.\n    2. Non-space qualified parts: \n        (a) The content of the lot acceptance is defined according to the available data. \n        (b) The proposed lot acceptance is approved through the approval process (see clause 6.2.4).\n    3. Commercial parts:\n        (a) The content of the lot acceptance is defined according to information provided by the justification document.\n        (b) The proposed lot acceptance is approved through the approval process (see clause 6.2.4)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.5b","Requirement","ECSS-Q-ST-60_0480380",1,"Created","The sample size for lot acceptance which may be reduced in some cases, shall be submitted to the customer approval through the approval process (see clause 6.2.4)"]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.6a","Requirement","ECSS-Q-ST-60_0480381",1,"Created","A buy-off is not required."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.7a","Requirement","ECSS-Q-ST-60_0480382",1,"Created","The procurement entity shall perform incoming inspection at his premises on all components to verify conformance with the purchase order requirements."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.7b","Requirement","ECSS-Q-ST-60_0480383",1,"Created","The incoming inspection shall include the following items:\n    1. Marking control,\n    2. Quantity verification,\n    3. Packing checking,\n    4. Review of the manufacturer delivered documentation,\n    5. Additional tests based on the type of component, criticality and heritage with the manufacturer (e.g. solderability tests, electrical tests)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.7c","Requirement","ECSS-Q-ST-60_0480384",1,"Created","The incoming inspection shall be documented by a procedure to be presented, on request, to the customer for review."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.7d","Requirement","ECSS-Q-ST-60_0480385",1,"Created","If the parts have passed successfully a final CSI (or buy-off), the incoming inspection may be reduced. The minimum shall be :\n    1. Verification of the manufacturer’s CoC,\n    2. Packing checking,\n    3. Quantity verification."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.7e","Requirement","ECSS-Q-ST-60_0480386",1,"Created","In case the incoming inspection has been performed by a procurement agent, the incoming inspection performed by the end-user, may be reduced. The minimum shall be : :\n    1. Packing checking,\n    2. Quantity verification."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.8a","Requirement","ECSS-Q-ST-60_0480387",1,"Created","Radiation sensitive components, as defined in clause 6.2.2.4 and for which applicable existing test data is insufficient shall be subjected to RVT."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.8b","Requirement","ECSS-Q-ST-60_0480388",1,"Created","RVT shall be performed in accordance with internationally recognized standards, such as ESCC Basic Specifications No. 22900 and No.25100. \n    ","NOTE Additional information on test methods is given in MIL-STD-750 Test Method 1080, MIL-STD-883 Test Method 1019 and JEDEC JESD57."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.8c","Requirement","ECSS-Q-ST-60_0480389",1,"Created","In such a case, a PAD in conformance with Annex D shall be issued and processed as per clause 6.2.4."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.8d","Requirement","ECSS-Q-ST-60_0480390",1,"Created","The results of RVT shall be documented by a report. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.8e","Requirement","ECSS-Q-ST-60_0480391",1,"Created","When RVT is performed in the frame of the project, the supplier shall send the related report to the customer for information."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.9a","Requirement","ECSS-Q-ST-60_0480392",1,"Created","The DPA shall be performed on 3 samples per lot for the following non-space qualified part types, as a minimum relays and commercial parts."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.9b","Requirement","ECSS-Q-ST-60_0480393",1,"Created","DPA may be carried out on representative samples of the components families when procured from the same manufacturer and same package without major change in the process, with a limited datecode range of 13 weeks. Such reductions shall be submitted to the customer for approval through the PAD (or Justification document) process.\n    ","NOTE In complement of above conditions, for series of integrated circuits, series of thermal switches, series of active discrete and series of passive components (e.g. 54xxxx, 1N63xx, …), representative samples can be from the same family considering technology limit and their complexity."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.9c","Requirement","ECSS-Q-ST-60_0480394",1,"Created","The DPA sample size may be reduced in some cases which shall be submitted to the customer for approval through the PAD process."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.9d","Requirement","ECSS-Q-ST-60_0480395",1,"Created","The DPA process shall be documented by a procedure to be sent, on request, to the customer for review."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.9e","Requirement","ECSS-Q-ST-60_0480396",1,"Created","The supplier shall verify that the outcome of the DPA is satisfactory prior to the installation of the components into flight hardware."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.9f","Permission","ECSS-Q-ST-60_0480465",1,"Created","Independent laboratories may perform DPA when approved by the customer."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.9g","Permission","ECSS-Q-ST-60_0480466",1,"Created","DPA may be performed by the manufacturer if witnessed by the supplier (or approved representative)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.9h","Requirement","ECSS-Q-ST-60_0480399",1,"Created","Methods and accept/reject criteria for inspection component (material, design, construction, workmanship) shall be documented by a procedure to be presented to the customer, on request, for review."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.9i","Requirement","ECSS-Q-ST-60_0480400",1,"Created","For health and safety reasons, any test producing beryllium oxide dust shall be omitted."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.9j","Requirement","ECSS-Q-ST-60_0480401",1,"Created","The results of DPA shall be documented by a report sent to the customer, on request, for information."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.10a","Permission","ECSS-Q-ST-60_0480467",1,"Created","Components from a supplier’s or parts procurement agent’s stock may be used provided the following criteria are met:\n    1. The parts are stored according to the minimum conditions given in clause 6.4, \n    2. The minimum overall requirements (including screening) are in accordance with the project requirements, \n    3. The lot homogeneity and traceability can be demonstrated, \n    4. The EEE parts documentation is available and the content is acceptable in accordance with the project requirements (including radiation data, if necessary), \n    5. There are no open NCR’s and no unresolved alerts with respect to their date code."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.10b","Requirement","ECSS-Q-ST-60_0480403",1,"Created","For components meeting the above criteria, and which have a lot / date code exceeding the period defined in ECSS-Q-ST-60-14 clause 5, the relifing procedure ECSS-Q-ST-60-14 shall apply."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.11a","Requirement","ECSS-Q-ST-60_0480404",1,"Created","The manufacturer’s CoC shall be delivered to the parts procurer. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.11b","Requirement","ECSS-Q-ST-60_0480405",1,"Created","Any other data (i.e. LAT or LVT, QCI or TCI), defined in the applicable procurement documents, shall be available at the manufacturer’s facilities or delivered to the parts’ procurer in line with the purchase order. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.3.11c","Requirement","ECSS-Q-ST-60_0480406",1,"Created","For non qualified parts, the documentation minimum storage period shall be 10 years after delivery of components by the manufacturer. \n    ","NOTE For qualified parts, the documentation storage period is under the responsibility of the manufacturer and the qualifying authority."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.4a","Requirement","ECSS-Q-ST-60_0480407",1,"Created","The supplier shall establish and implement procedures for handling and storage of components in order to prevent possible degradation."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.4b","Requirement","ECSS-Q-ST-60_0480408",1,"Created","The procedures shall be applicable at any facility dealing with components for flight application."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.4c","Requirement","ECSS-Q-ST-60_0480409",1,"Created","On request, these procedures shall be sent to the customer for review."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.4d","Requirement","ECSS-Q-ST-60_0480410",1,"Created","As a minimum, the following areas shall be covered:\n    1. Control of the environment in accordance with ESCC Basic Specification No. 24900.\n    2. Measures and facilities to segregate and protect components during receiving inspection, storage, and delivery to manufacturing. \n    3. Control measures to ensure that electrostatic discharge susceptible components are identified and handled only by trained personnel using anti static packaging and tools."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.5.1a","Requirement","ECSS-Q-ST-60_0480411",1,"Created","The supplier shall establish and implement the requirements of this document including methods, organizations and documents used to control the selection and procurement of components in accordance with the requirements of ECSS-Q-ST-20."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.5.2a","Requirement","ECSS-Q-ST-60_0480412",1,"Created","The supplier shall establish and maintain a nonconformance control system in accordance with the general requirements in ECSS-Q-ST-20."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.5.2b","Requirement","ECSS-Q-ST-60_0480413",1,"Created","Any observed deviation of EEE components from requirements as laid down in applicable specifications, procedures and drawings shall be controlled by the nonconformance control system.\n    ","NOTE This includes failures, malfunctions, deficiencies and defects."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.5.2c","Requirement","ECSS-Q-ST-60_0480414",1,"Created","The nonconformance control system shall handle all nonconformances occurring on EEE components during: \n    1. Manufacture (if available), screening and acceptance tests, \n    2. Incoming inspection,\n    3. Integration and test of equipment,\n    4. Storage and handling."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.5.2d","Requirement","ECSS-Q-ST-60_0480415",1,"Created","For ESCC qualified components the supplier shall apply the ESCC basic specification no 22800."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.5.3a","Requirement","ECSS-Q-ST-60_0480416",1,"Created","The supplier shall take into account all received alerts from international alert systems, from manufacturers or sent by the customer and shall validate that there are no alerts on the proposed parts with respect to the batch information (including date-code). "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.5.3b","Requirement","ECSS-Q-ST-60_0480417",1,"Created","If alerts become available at a later stage, the supplier shall analyse the alerts, analyse the project risk and propose an action plan for customer approval. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.5.4a","Requirement","ECSS-Q-ST-60_0480418",1,"Created","The traceability of individual components during manufacturing and testing shall be maintained as required by the procurement specifications."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.5.4b","Requirement","ECSS-Q-ST-60_0480419",1,"Created","The traceability shall be maintained through incoming, storage, and installation at the procurer and user of the component in accordance with programme PA requirements. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.5.4c","Requirement","ECSS-Q-ST-60_0480420",1,"Created","In any case, the traceability requirements imposed by the supplier on the EEE parts manufacturer or distributor shall allow managing the adequacy of the tests performed by the supplier (i.e. evaluation, lot validation, any additional test or inspection). "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.5.4d","Requirement","ECSS-Q-ST-60_0480421",1,"Created","The traceability of EEE parts during installation in equipment, shall be ensured by the supplier through maintaining the traceability to the manufacturer’s lot/datecode number of the EEE parts actually mounted. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.5.4e","Requirement","ECSS-Q-ST-60_0480422",1,"Created","The supplier shall be able to provide these information (part type actually installed with its relevant lot/datecode number) within one working day (when the flight system is on launch pad) or within one week (in the other cases)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.5.5a","Requirement","ECSS-Q-ST-60_0480423",1,"Created","For radiation tests, the set of test samples used shall be a representative distribution for the wafer lot. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.6.1a","Requirement","ECSS-Q-ST-60_0480424",1,"Created","For the specific component types identified in clauses 6.6.2, 6.6.3, 6.6.4, and 6.6.5 reference shall be made to applicable standards, in addition to the requirements of this standard."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.6.2a","Requirement","ECSS-Q-ST-60_0480425",1,"Created","ECSS-Q-60-02 shall apply for the design development."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.6.3a","Requirement","ECSS-Q-ST-60_0480426",1,"Created","ECSS-Q-ST-60-05 shall apply."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.6.4a","Requirement","ECSS-Q-ST-60_0480427",1,"Created","For FPGA, ECSS-Q-ST-60-02, shall apply for the design development. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.6.4b","Requirement","ECSS-Q-ST-60_0480428",1,"Created","The PAD shall allow traceability to the information related to the procurement of blank parts, the programming and the acceptance of the programmed parts."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.6.4c","Permission","ECSS-Q-ST-60_0480468",1,"Created","The programming and the acceptance of the programmed parts may be part of a separate document, for customer approval, if not indicated in the PAD."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.6.4d","Requirement","ECSS-Q-ST-60_0480430",1,"Created","One time programmable components shall be submitted to a post-programming sequence. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.6.4e","Requirement","ECSS-Q-ST-60_0480431",1,"Created","A dynamic post-programming burn-in shall be applied to FPGA’s, in conformance with ESCC9000 subclause 8.21, except for the duration, that is 160 h minimum."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.6.4f","Requirement","ECSS-Q-ST-60_0480432",1,"Created","The supplier shall prepare a post-programming procedure for customer’s approval, depending on part types (including when necessary electrical tests, programming conditions and equipment, burn-in conditions, additional screening tests and specific marking after programming)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.6.4g","Requirement","ECSS-Q-ST-60_0480433",1,"Created","The lot acceptance procedure, as defined in clause 6.3.5, shall be performed on devices coming from the flight lot and programmed using on the same kind of hardware tools and compatible software."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.6.4h","Permission","ECSS-Q-ST-60_0480469",1,"Created","In case of several designs based on the same lot of blank parts, the lot acceptance procedure, as defined in clause 6.3.5, may be limited to one representative flight programmed design."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.6.5a","Requirement","ECSS-Q-ST-60_0480435",1,"Created","ECSS-Q-ST-60-12 shall apply. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","6.7a","Requirement","ECSS-Q-ST-60_0480436",1,"Created","Any result from inspection or control shall be documented (including, precap, lot acceptance, buy-off, incoming, relifing and complementary tests)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","A.2.1a","Requirement","ECSS-Q-ST-60_0480437",1,"Created","The CCP shall include or refer to the following information:\n    1. A description of the purpose, content and the reason prompting its preparation,\n    2. A list of the applicable and reference documents,\n    3. Any additional terms, definitions and abbreviations,\n    4. The organizational breakdown structure, responsibility descriptions, management approach and concurrent engineering,\n    5. Control of lower level suppliers, procurement agents (if any) and manufacturers,\n    6. Procurement system,\n    7. Radiation control programme,\n    8. Component selection and standardization,\n    9. Component data acquisition and assessment,\n    10. Component evaluation and related testing approach,\n    11. Component approval,\n    12. Component testing, inspection and storage,\n    13. Component quality assurance activities,\n    14. Assessment of problem notifications and alerts,\n    15. Programme planning with schedule of tasks linked to programme milestones,\n    16. Specific components control and back-up plans whenever there is evidence of possible schedule, quality or technical problems,\n    17. Reporting and deliverables, \n    18. Compliance matrix to the clauses of this standard. "]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","A.2.2a","Permission","ECSS-Q-ST-60_0480470",1,"Created","In conformance with 4.2.2.1b the CCP may be part of the overall project PA plan."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","B.2.1a","Requirement","ECSS-Q-ST-60_0480439",1,"Created","The DCL shall include or refer to the following information:\n    1. A description of the purpose, content and the reason prompting its preparation, \n    2. A list of the applicable and reference documents,\n    3. Any additional terms, definitions or abbreviations,\n    4. Component number (commercial equivalent designation),\n    5. Family (ESCC group code),\n    6. Package,\n    7. Value or range of values with tolerance for non qualified parts,\n    8. Component manufacturer (name, country),\n    9. Generic procurement specification, \n    10. Detail procurement specification (with issue and revision for non qualified parts),\n    11. Specification amendment (including issue and revision),\n    12. Name of the procurement agent (CPPA, supplier, distributor),\n    13. Quality level and lot test (ESCC LAT or LVT, MIL TCI or QCI or CI),\n    14. Space qualified status (yes or no),\n    15. RVT (yes or no),\n    16. Reference of the PAD or Justification Document, where required,\n    17. Approval status of the part,\n    18. Change identification between each DCL issue,\n    19. Date-code (only for “as built” DCL)."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","C.2.1a","Requirement","ECSS-Q-ST-60_0480440",1,"Created","The procurement specification shall include or refer to the following information:\n    1. A description of the purpose, content and the reason prompting its preparation, \n    2. A list of the applicable and reference documents,\n    3. Any additional terms, definitions or abbreviations,\n    4. Absolute maximum ratings,\n    5. Electrical and mechanical parameters and limits,\n    6. Screening, burn-in, and acceptance requirements,\n    7. Package material and lead finish,\n    8. Documentation/data requirements,\n    9. Delta limits when applicable,\n    10. Criteria for percent defective allowable,\n    11. LAT or LVT, QCI or TCI,\n    12. Marking,\n    13. Storage requirements,\n    14. Requirements for lot homogeneity,\n    15. Serialization (when applicable),\n    16. Protective packaging and handling requirements,\n    17. Radiation Verification Testing requirements, when applicable."]
["ECSS-Q-ST-60C Rev. 1","ECSS - Superseded v1.0","D.2a","Requirement","ECSS-Q-ST-60_0480441",1,"Created","The information given in Table D-1 shall be provided."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.1.1a","Requirement","ECSS-Q-ST-20_0380001",1,"Created","The supplier shall prepare, maintain and implement a QA plan in conformance with the DRD in Annex A."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.1.1b","Requirement","ECSS-Q-ST-20_0380002",1,"Created","The QA plan shall be submitted to the customer for approval.\n    NOTE Information on the schedule for delivery of the QA plan is given in Annex I."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.1.2a","Requirement","ECSS-Q-ST-20_0380003",1,"Created","The supplier shall establish a documented training programme for the personnel whose performance determines or affects product quality."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.1.2b","Requirement","ECSS-Q-ST-20_0380004",1,"Created","Personnel performing special processes shall be trained and certified by internal or external training programmes.\n    NOTE The term “special process” is defined in ECSS-S-ST-00-01, Note 3 of the definition of “process”."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.1.2c","Requirement","ECSS-Q-ST-20_0380005",1,"Created","Personnel inspecting or controlling special processes, or performing non-destructive testing and evaluation, shall be trained and certified according to training programmes and standards accepted by the customer."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.1.2d","Requirement","ECSS-Q-ST-20_0380006",1,"Created","The supplier shall maintain records of the training."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.1a","Requirement","ECSS-Q-ST-20_0380007",1,"Created","The supplier shall implement Critical-items control in conformance with ECSS-Q-ST-10-04."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.2a","Requirement","ECSS-Q-ST-20_0380008",1,"Created","The supplier shall implement a nonconformance control system in conformance with ECSS-Q-ST-10-09."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.3a","Requirement","ECSS-Q-ST-20_0380009",1,"Created","The supplier shall manage alerts in conformance with ECSS-Q-ST-10, clause 5.2.9."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.4a","Requirement","ECSS-Q-ST-20_0380010",1,"Created","The supplier shall establish and maintain a documented stamp control system to ensure the correct and legitimate use of all fabrication and inspection stamps."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.4b","Requirement","ECSS-Q-ST-20_0380011",1,"Created","Stamps shall be used to:\n    1. signify the completion of operations and processes, and\n    2. indicate inspection performance at source and incoming inspection, in process inspection and tests, final inspection, end point testing, storage and shipment."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.4c","Requirement","ECSS-Q-ST-20_0380012",1,"Created","The use of stamps shall be restricted to authorized personnel as identified in the stamp control system."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.4d","Requirement","ECSS-Q-ST-20_0380013",1,"Created","Stamps shall be traceable to individuals responsible for their use."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.4e","Requirement","ECSS-Q-ST-20_0380014",1,"Created","Stamps shall be applied directly to parts and materials, when specified by engineering drawings and specifications, and associated documents, records, labels."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.4f","Requirement","ECSS-Q-ST-20_0380015",1,"Created","Stamping materials and methods shall be compatible with the articles and their use."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.4g","Permission","ECSS-Q-ST-20_0380225",1,"Created","Signatures instead of stamps may be used provided that similar traceability and responsibility records are maintained and available."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.5a","Requirement","ECSS-Q-ST-20_0380017",1,"Created","The supplier shall ensure that a bidirectional and unequivocal relationship between parts, materials or products and associated documentation or records is established and maintained."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.5b","Requirement","ECSS-Q-ST-20_0380018",1,"Created","The supplier shall be capable to trace data, personnel and equipment related to procurement, manufacturing, inspection, test, assembly, integration and operations activities."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.5c","Requirement","ECSS-Q-ST-20_0380019",1,"Created","The supplier shall be capable to trace backward the locations of materials, parts, sub-assemblies."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.5d","Requirement","ECSS-Q-ST-20_0380020",1,"Created","The supplier shall be capable to trace forward the locations of materials from raw stock."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.5e","Requirement","ECSS-Q-ST-20_0380021",1,"Created","The supplier shall establish controls to ensure that:\n    1. identification numbers are assigned in a systematic and consecutive manner,\n    2. identification numbers of scrapped or destroyed items are not used again,\n    3. identification numbers, once allocated, are not changed, unless the change is authorized by the customer.\n        NOTE Requirements for identification are addressed in ECSS-M-ST-40."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.6a","Requirement","ECSS-Q-ST-20_0380022",1,"Created","The supplier shall control, calibrate and maintain inspection, measuring and test equipment, whether owned by the supplier, on loan, or provided by the customer to demonstrate the conformance of product to the specified requirements."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.6b","Requirement","ECSS-Q-ST-20_0380023",1,"Created","The supplier shall use equipment in a manner which ensures that measurement uncertainty is known and is consistent with the specified measurement capability."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.6c","Requirement","ECSS-Q-ST-20_0380024",1,"Created","The supplier shall include in the calculations of all measurements the total error in the measurement process attributable to the cumulative error from the calibration chain, measuring equipment and those contributed by personnel, procedures and the environment."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.6d","Requirement","ECSS-Q-ST-20_0380025",1,"Created","The supplier shall record the basis for the calculation of the cumulative errors as specified in requirement 5.2.6c."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.6e","Requirement","ECSS-Q-ST-20_0380026",1,"Created","The supplier shall select inspection, measuring and test equipment in conformance with the required measurement accuracy and precision."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.6f","Requirement","ECSS-Q-ST-20_0380027",1,"Created","The supplier shall identify, calibrate and adjust all inspection, measuring and test equipment and devices that can affect product quality at prescribed intervals, or prior to use, against certified equipment."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.6g","Requirement","ECSS-Q-ST-20_0380028",1,"Created","The supplier shall establish, document and maintain calibration procedures, including details of equipment type, identification number, location, frequency of checks, check method, acceptance criteria and the action to be taken when results exceed the specified accuracy."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.6h","Requirement","ECSS-Q-ST-20_0380029",1,"Created","The supplier shall ensure that the inspection, measuring and test equipment is capable of the specified accuracy and precision."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.6i","Requirement","ECSS-Q-ST-20_0380030",1,"Created","The supplier shall identify inspection, measuring and test equipment with a suitable indicator or approved identification record to show the calibration status."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.6j","Requirement","ECSS-Q-ST-20_0380031",1,"Created","The supplier shall maintain calibration records for inspection, measuring and test equipment."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.6k","Requirement","ECSS-Q-ST-20_0380032",1,"Created","The supplier shall assess and document the validity of previous inspection and test results when inspection, measuring or test equipment is found to be out of calibration."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.6l","Requirement","ECSS-Q-ST-20_0380033",1,"Created","The supplier shall ensure that the environmental conditions are suitable for the calibrations, inspections, measurements and tests being carried out."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.6m","Requirement","ECSS-Q-ST-20_0380034",1,"Created","The supplier shall ensure that inspection, measuring and test facilities, including both test hardware and test software are protected against adjustments, which can invalidate the calibration setting."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.6n","Requirement","ECSS-Q-ST-20_0380035",1,"Created","The supplier shall ensure that the inspection, measuring and test equipment is handled, preserved and stored such that the accuracy and fitness for use is maintained."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.6o","Requirement","ECSS-Q-ST-20_0380036",1,"Created","The supplier shall check the test hardware or test software used for inspection to prove that it is capable of verifying the acceptability of the product prior to release for use during production and installation, and recheck it at specified intervals. \n    NOTE 1 Examples of test hardware are: jigs, fixtures, templates and patterns. \n    NOTE 2 Test aids such as test leads, break-out boxes, mains leads and similar items are not subject to the entire set of requirements defined in this clause, but are validated in a way appropriate to their usage."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.6p","Requirement","ECSS-Q-ST-20_0380037",1,"Created","The supplier shall establish the extent and frequency of such checks and shall maintain records as evidence of control."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.6q","Requirement","ECSS-Q-ST-20_0380038",1,"Created","The supplier shall make the measurement design data available to the customer upon request."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.7.1a","Requirement","ECSS-Q-ST-20_0380039",1,"Created","The supplier shall prevent handling damage during all phases of manufacturing, assembly, integration, testing, storage, transportation and operation.\n    NOTE Possible prevention measures are:\n\ta. protection of items during handling,\n\tb. handling devices, or\n\tc. procedures and instructions."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.7.2a","Requirement","ECSS-Q-ST-20_0380040",1,"Created","The supplier shall place the following items in secure storage areas:\n    1. incoming materials,\n    2. intermediate items needing temporary storage, and\n    3. end items before shipping."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.7.2b","Requirement","ECSS-Q-ST-20_0380041",1,"Created","The supplier shall place the following items in designated segregated areas:\n    1. limited life materials,\n    2. suspended limited life materials,\n    3. nonconforming items awaiting NRB disposition,\n    4. scraped items,\n    5. items designated to be stored separately for health or safety reasons."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.7.2c","Requirement","ECSS-Q-ST-20_0380042",1,"Created","Each segregated area shall be identified and labelled for its intended use."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.7.2d","Requirement","ECSS-Q-ST-20_0380043",1,"Created","The supplier shall maintain control over acceptance into and withdrawal from storage areas."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.7.2e","Requirement","ECSS-Q-ST-20_0380044",1,"Created","The supplier shall maintain records to ensure that all stored items are within the usable life limits, controlled and retested, and to provide traceability within the storage or segregated area."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.7.3a","Requirement","ECSS-Q-ST-20_0380045",1,"Created","The supplier shall ensure that items subject to deterioration, corrosion or contamination through exposure to any environmental elements are preserved by methods that ensure maximum protection consistent with life and usage.\n    NOTE Examples of such environmental elements are: air and moisture."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.8.1a","Requirement","ECSS-Q-ST-20_0380046",1,"Created","Statistical quality control and analysis methods shall be used to maintain or improve the specified control of quality, when statistically significant with respect to the product characteristics and to quantities produced.\n    NOTE Examples of statistical quality control and analysis methods are sample inspection plans, determination of quality levels, statistical process control and process capabilities studies."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.8.1b","Requirement","ECSS-Q-ST-20_0380047",1,"Created","When employing statistical quality control and analysis methods, the supplier shall ensure that all the conditions for use are enforced.\n    NOTE Example of such conditions are sample significance, recording and elaboration of data, and formulation of clear decision rules."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.8.1c","Requirement","ECSS-Q-ST-20_0380048",1,"Created","Statistical quality control applications, when used by the supplier for acceptance of materials, parts, processes and products, shall be submitted to the customer for approval. "]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.8.2a","Requirement","ECSS-Q-ST-20_0380049",1,"Created","When sampling plans are used the supplier shall define and justify the following:\n    1. sample size, sample selection methods and criteria for inspection severity, \n    2. acceptance / rejection criteria, and \n    3. screening of rejected lots."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.2.8.2b","Requirement","ECSS-Q-ST-20_0380050",1,"Created","The supplier shall maintain records of the sampling tests, together with the identification of the characteristics to which sampling is applied."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.1.1a","Requirement","ECSS-Q-ST-20_0380051",1,"Created","The supplier shall ensure that the product is designed such that it can be produced with the specified level of quality.\n    NOTE Produceability includes provisions for the following aspects:\n\t· Design simplification and standardization, reduction in part types and part number.\n\t· Guidelines for selection of preferred parts, materials and processes.\n\t· Unambiguous definitions of the requirements and limits to be used.\n\t· Definition of tolerance build-up methods, in order to simplify manufacturing, assembly, inspection.\n\t· Standardization of interfaces.\n\t· Part accessibility for assembly and inspection.\n\t· Definition of design criteria consistent with the capability of manufacturing processes.\n\t· Definition of design methods to ensure that the cleanliness requirements are compatible with the capability of related cleanliness procedures and facilities."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.1.2a","Requirement","ECSS-Q-ST-20_0380052",1,"Created","The supplier shall ensure that the product is designed such that its performances and characteristics can be reproduced over different models and serial production.\n    NOTE Repeatability includes provisions for the following aspects:\n\t• Definition of standard tolerances generally applicable.\n\t• Recommended design concepts and solutions to ensure repeatability.\n\t• Recommended manufacturing processes having proven repeatability.\n\t• Design criteria that optimize implementation of automated manufacturing methods, or computer-aided manufacturing."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.1.3a","Requirement","ECSS-Q-ST-20_0380053",1,"Created","The supplier shall ensure that the product is designed such that it can be inspected and tested under representative conditions, for production, AIV and operational environment.\n    NOTE Inspectability and testability include provisions for the following aspects:\n\t• Definition of inspection and test requirements, including acceptance or rejection criteria, expressed in an unambiguous and quantified manner.\n\t• Part and component accessibility for inspection and test.\n\t• Definition of tolerance methods for dimensional inspection performance (e.g. functional tolerances).\n\t• Definition of recommended design techniques to facilitate fault detection, identification and location (e.g. test points, modularity, built-in test software, and feedback loops)."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.1.4a","Requirement","ECSS-Q-ST-20_0380054",1,"Created","The supplier shall ensure that the product is designed such that it can be operated in accordance with programme constraints and requirements, throughout its whole life cycle including handling, storage, transportation, integration and operations."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.2.1a","Requirement","ECSS-Q-ST-20_0380055",1,"Created","The supplier shall ensure that requirement verification is performed progressively, as each stage of the project is completed, and provides the organized base of data upon which qualification and acceptance is incrementally declared."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.2.1b","Requirement","ECSS-Q-ST-20_0380056",1,"Created","The supplier shall ensure that top-down requirement allocations and bottom-up requirement verifications are complete and consistent."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.2.1c","Requirement","ECSS-Q-ST-20_0380057",1,"Created","The supplier shall ensure that a system for tracking requirements and verification of results is established and maintained during the whole project life cycle."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.2.1d","Requirement","ECSS-Q-ST-20_0380058",1,"Created","The supplier shall ensure that verification methods are adequate and consistent with the type and criticality of the requirements."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.2.1e","Requirement","ECSS-Q-ST-20_0380059",1,"Created","The supplier shall ensure that appropriate reference to the verification documentation is recorded and status updated at project reviews up to final acceptance."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.2.2a","Requirement","ECSS-Q-ST-20_0380060",1,"Created","The supplier shall ensure that the objectives of the analysis are defined in relation with the development logic defined in the verification plan."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.2.2b","Requirement","ECSS-Q-ST-20_0380061",1,"Created","The following items shall be identified:\n    1. reference of the configuration item definition under analysis;\n    2. environmental constraints considered in the analysis;\n    3. basic assumptions, analysis methods, mathematical models."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.2.3a","Requirement","ECSS-Q-ST-20_0380062",1,"Created","The supplier shall ensure that design reviews are conducted in accordance with project requirements and written procedures.\n    NOTE Design reviews address the following items:\n\t• Quality requirements and criteria for design, produceability, repeatability, testability and operability are adequately considered in design documentation.\n\t• Methods and data required for procurement, manufacturing, inspection and test are available and validated.\n\t• Risks of not achieving requirements are highlighted and adequately controlled."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.2.4.1a","Requirement","ECSS-Q-ST-20_0380063",1,"Created","The supplier shall ensure that all configuration items and their constituent items, either off-the-shelf or specifically designed, are properly qualified with margins commensurate with the application and use environment."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.2.4.1b","Requirement","ECSS-Q-ST-20_0380064",1,"Created","The supplier QA shall review and approve the qualification plan."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.2.4.1c","Requirement","ECSS-Q-ST-20_0380065",1,"Created","The supplier QA shall review and approve the qualification results."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.2.4.2a","Requirement","ECSS-Q-ST-20_0380066",1,"Created","Qualification by similarity with an identical or similar product shall be justified by providing evidence that the new application is within the limits of the previously qualified design."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.2.4.2b","Requirement","ECSS-Q-ST-20_0380067",1,"Created","Any difference in definition with respect to the reference product and any difference in the required qualification tests shall be identified."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.2.4.2c","Requirement","ECSS-Q-ST-20_0380068",1,"Created","The need for complementary qualification tests shall be analysed and the decision justified and submitted to the customer for approval."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.2.4.2d","Requirement","ECSS-Q-ST-20_0380069",1,"Created","For this purpose the supplier shall:\n    1. evaluate the as-designed or as-built configuration and related nonconformances,\n    2. ensure that qualification requirements and qualification ranges are compatible with project requirements,\n    3. ensure that qualification test results meet the requirements and any nonconformances are available for evaluation, and\n    4. ensure that a logbook of the selected model is available for review."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.2.4.3a","Requirement","ECSS-Q-ST-20_0380070",1,"Created","The product used for qualification testing shall be produced in accordance with a full and clearly identified manufacturing and inspection file. "]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.2.4.3b","Requirement","ECSS-Q-ST-20_0380071",1,"Created","To obtain authorization to initiate qualification tests the supplier shall demonstrate that:\n    1. the qualification model is fully representative of the flight model and any differences have been analysed to evaluate their effect on the qualification status;\n    2. inspection and test requirements are expressed in an unambiguous and quantified manner including:\n        (a) test sequence;\n        (b) test conditions;\n        (c) test standards, if any;\n        (d) applicable test levels, durations and tolerances;\n        (e) accuracy in measurement.\n    3. the qualification test procedures and facilities are defined, available and conforming to requirements of clause 5.6."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.2.4.4a","Requirement","ECSS-Q-ST-20_0380072",1,"Created","The supplier shall report the qualification status in conformance with the “Qualification status list” DRD as defined in ECSS-Q-ST-10."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.2.4.5a","Requirement","ECSS-Q-ST-20_0380073",1,"Created","Once the design is qualified, the supplier shall assess all subsequent changes, deviations and anomalies for their impact on the qualification status and shall perform requalification as necessary."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.3.2.5a","Requirement","ECSS-Q-ST-20_0380074",1,"Created","The supplier shall ensure that all design changes and modifications are identified, documented, reviewed and approved before their implementation."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.4.1.1a","Requirement","ECSS-Q-ST-20_0380075",1,"Created","The supplier QA shall participate in the approval and the selection of procurement sources.\n    NOTE The selection of procurement sources for EEE components is defined in ECSS-Q-ST-60."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.4.1.2a","Requirement","ECSS-Q-ST-20_0380076",1,"Created","The supplier shall select its suppliers on the basis of one of the following criteria:\n    1. The supplier has been certified by the final customer, and has a current approval to furnish items or services of the type and quality level being procured.\n        NOTE Third party certification (for instance against ISO 9001) can be also considered.\n    2. The supplier is furnishing, or has furnished within the past two years, items or services of the type and quality level being procured under other contracts with the final customer.\n    3. The supplier has demonstrated continuous capability to furnish items or services of the type and quality level being procured, supported by objective documentation.\n        NOTE This criterion does not apply if the supplier has not furnished items or services of the type being procured for more than two years.\n    4. Supplier’s capability of satisfying business agreement requirements is demonstrated by a pre-award audit by the relevant customer."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.4.1.2b","Requirement","ECSS-Q-ST-20_0380077",1,"Created","The supplier shall document and maintain on file results of supplier selection process."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.4.1.3a","Requirement","ECSS-Q-ST-20_0380078",1,"Created","The supplier shall establish and maintain records of all procurement sources involved in business agreement performance."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.4.1.3b","Requirement","ECSS-Q-ST-20_0380079",1,"Created","The supplier shall submit to the customer, upon request, the list of procurement sources, including all the information in the records 5.4.1.3a, for information."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.4.2a","Requirement","ECSS-Q-ST-20_0380080",1,"Created","The supplier shall ensure that supplies are identified and that all applicable requirements are defined in the procurement documents."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.4.2b","Requirement","ECSS-Q-ST-20_0380081",1,"Created","The supplier shall ensure that requirements to those contained in lower tier procurement documents are traceable."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.4.2c","Requirement","ECSS-Q-ST-20_0380082",1,"Created","The procurement documents shall contain, by statement or reference:\n    1. comprehensive technical descriptions of the items and services to be procured,\n    2. details of the applicable requirements, such as requirements for preservation, packaging, marking, shipping, accompanying documentation and provisions for limited-life items,\n    3. details of QA activities to be performed, such as inspection and test characteristics, records and reports,\n    4. details of supplier’s QA activities at source, and\n    5. special acceptance conditions."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.4.2d","Requirement","ECSS-Q-ST-20_0380083",1,"Created","The supplier’s quality assurance organization shall review procurement documents prior to release, to verify the correct selection of procurement sources and appropriateness of their content."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.4.3a","Requirement","ECSS-Q-ST-20_0380084",1,"Created","The supplier shall exercise surveillance over all the activities carried out by lower level suppliers during business agreement performance."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.4.3b","Requirement","ECSS-Q-ST-20_0380085",1,"Created","The surveillance programme shall include audits, reviews, mandatory inspection points, as well as direct supervision by supplier’s resident personnel at his suppliers’ facilities and source inspection.\n    NOTE Example of review is the manufacturing readiness review."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.4.3c","Requirement","ECSS-Q-ST-20_0380086",1,"Created","The supplier shall select among the following criteria to define the type and extent of surveillance:\n    1. Testing or inspections cannot be accomplished by the supplier.\n        NOTE For example, environments or test equipment not available at supplier’s facility.\n    2. Verification tests are destructive in nature and the quality cannot be verified solely by inspection or test at supplier’s facility.\n    3. Supplies are designated for direct shipment from source to a customer site or the using site.\n    4. Manufacturing and AIV of complex equipment or subsystems.\n        NOTE For example, payloads.\n    5. Past performance or quality history of the lower level supplier is marginal.\n    6. Functional criticality and technical complexity of the supplies.\n    7. The degree of responsibility placed on the procurement source."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.4.3d","Requirement","ECSS-Q-ST-20_0380087",1,"Created","The supplier shall ensure that each of his suppliers implements surveillance on their lower level suppliers, in accordance with the same criteria."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.4.3e","Permission","ECSS-Q-ST-20_0380226",1,"Created","Surveillance may be delegated by the customer to third parties."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.4.4.1a","Requirement","ECSS-Q-ST-20_0380089",1,"Created","The supplier shall ensure that all incoming supplies, including documentation and packaging, whether delivered on his own premises or elsewhere, conform to the requirements of the procurement documents."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.4.4.1b","Requirement","ECSS-Q-ST-20_0380090",1,"Created","The supplier shall perform inspections in accordance with established procedures and instructions, to ensure that quality level is properly determined. \n    NOTE 1 Sampling plans in receiving inspection are defined in 5.2.8.2\n    NOTE 2 Receiving inspection of components is defined in ECSS-Q-ST-60.\n    NOTE 3 Lot or batch acceptance of materials and mechanical parts is defined in ECSS-Q-ST-70."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.4.4.1c","Requirement","ECSS-Q-ST-20_0380091",1,"Created","Receiving inspectors shall have available the procurement documents, specifications, drawings and any other document relevant to incoming supplies as required in the procurement documents."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.4.4.2a","Requirement","ECSS-Q-ST-20_0380092",1,"Created","Receiving inspection activities shall include:\n    1. verification of the packaging conditions and of the status of environmental sensors,\n    2. visual inspection of the delivered items,\n    3. verification of correct identification and, where appropriate, configuration identification for conformance to the ordering data,\n    4. verification of the evidence of inspection and tests performed by the supplier and associated documentation,\n    5. verification of the performance of supplier’s source inspection, when required,\n    6. performance of inspections and tests on selected characteristics of incoming supplies or test specimens submitted with the supplies,\n    7. identification of the shelf life of limited-life items,\n    8. identification of the inspection status and physical separation of the supplies in the receiving inspection area according to the following categories:\n        (a) items for which the receiving inspection has not been completed;\n        (b) conforming items;\n        (c) nonconforming items.\n    9. prevention of unauthorized use of uninspected items,\n    10. identification of the items to be released for production with conformance status and traceability data to be recorded in manufacturing documents,\n    11. maintenance of receiving inspection records in conformance with 5.4.4.4."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.4.4.3a","Requirement","ECSS-Q-ST-20_0380093",1,"Created","Receiving inspection of items supplied by the customer shall consist of the verification of identity and integrity after transportation.\n    NOTE Additional inspections and tests, if any, are specified in the business agreement."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.4.4.4a","Requirement","ECSS-Q-ST-20_0380094",1,"Created","The supplier shall maintain receiving inspection records to ensure traceability and the availability of historical data to monitor supplier performance and quality trends."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.1a","Requirement","ECSS-Q-ST-20_0380095",1,"Created","The supplier shall document the planning of manufacturing, assembly and integration operations and inspections in the manufacturing plan or flow chart for the product, including the sequence of operations and associated inspections and tests."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.1b","Requirement","ECSS-Q-ST-20_0380096",1,"Created","The planning shall include the identification of MIPs in conformance with 5.5.8, together with the reference to the procedures by which the various activities are performed and the required cleanliness levels and temperature and humidity requirements of the facilities."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.1c","Requirement","ECSS-Q-ST-20_0380097",1,"Created","Instructions shall direct the actual performance of manufacturing, assembly and integration operations and inspections, to ensure that the activities proceed in an orderly manner and according to the planned sequence.\n    NOTE For example: shop travellers."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.1d","Requirement","ECSS-Q-ST-20_0380098",1,"Created","The supplier shall issue and maintain manufacturing, assembly and integration documents in accordance with established and formal procedures."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.1e","Requirement","ECSS-Q-ST-20_0380099",1,"Created","The QA organization shall review and approve such documents, and any modifications thereof, to ensure that they include or refer to:\n    1. Identification of the item to be manufactured or equipment to be used.\n    2. Configuration data, including parts lists, drawings, changes and specifications.\n    3. Identification of the production and inspection equipment to be used for the manufacturing, assembly and integration of the item.\n        NOTE Examples of production and inspection equipment are tools, jigs and fixtures.\n    4. Identification of critical characteristics.\n        NOTE Critical characteristics are defined in ECSS-Q-ST-30.\n    5. Detailed definition, by description or reference, of manufacturing, assembly, integration, inspections and test operations to be performed, and special conditions to be maintained.\n    6. Provisions for inspections and tests to be witnessed by customer representative.\n    7. Accept or reject criteria (with tolerances) and workmanship standards.\n    8. Details of sampling inspection procedures to be used, if any.\n    9. Detailed procedures for the activities to be performed."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.1f","Requirement","ECSS-Q-ST-20_0380100",1,"Created","Only “first off” shop travellers shall be reviewed unless subsequent travellers incorporate a significant change of inspection requirements or order of events."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.1g","Requirement","ECSS-Q-ST-20_0380101",1,"Created","The supplier shall also provide for detail support documents and instructions, such as drawings, procedure and instruction sheets, to enable operations to be correctly performed."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.2a","Requirement","ECSS-Q-ST-20_0380102",1,"Created","The supplier shall perform an internal review of the readiness for manufacturing, prior to starting the manufacture of the first flight-standard product."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.2b","Requirement","ECSS-Q-ST-20_0380103",1,"Created","The manufacturing readiness review shall evaluate the following aspects:\n    1. status of product definition and requirements, differences with the status of the qualification model, and impacts of these differences;\n    2. status of manufacturing, assembly, inspection and test documentation, differences with the status of the qualification model, and impacts of these differences;\n    3. validation status of manufacturing processes, with particular emphasis on critical processes;\n    4. implementation of dispositions for risk reduction, as defined by risk assessment, into the manufacturing, assembly, integration, inspection and test procedures;\n    5. availability of specified production, measuring and inspection equipment, and calibration status, when relevant;\n    6. cleanliness of facilities, with respect to the specified cleanliness levels;\n    7. facility temperature and humidity with respect to requirements.\n"]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.3.1a","Requirement","ECSS-Q-ST-20_0380104",1,"Created","The supplier shall monitor all processes used for manufacturing, assembly and integration, and enforce all applicable process requirements."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.3.1b","Requirement","ECSS-Q-ST-20_0380105",1,"Created","The supplier shall ensure that all manufacturing processes are covered by documented process specifications or standards.\n    NOTE Manufacturing process specifications are defined in ECSS-Q-ST-70."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.3.1c","Requirement","ECSS-Q-ST-20_0380106",1,"Created","Process specifications shall include QA provisions, methods for inspection and test, number of samples, accept or reject criteria."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.3.1d","Requirement","ECSS-Q-ST-20_0380107",1,"Created","Process witness samples shall be stored in controlled conditions."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.3.2a","Requirement","ECSS-Q-ST-20_0380108",1,"Created","The supplier shall establish and implement procedures and controls for special processes, to ensure that:\n    1. Special processes are validated for the intended application.\n        NOTE Validation of special processes is defined in ECSS-Q-ST-70.\n    2. Personnel who perform special processes or evaluate the process performance are trained and certified or can demonstrate their proficiency through their regular activity.\n    3. Materials, equipment, computer systems and software, and procedures involved in the performance of the special process are validated and monitored.\n    4. Coordination is maintained with the cognizant engineering function to ensure proper selection of the non-destructive or destructive methods for the evaluation of process performance."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.3.3a","Recommendation","ECSS-Q-ST-20_0380227",1,"Created","Statistical methods for process control should be used for early detection of significant variations in manufacturing processes, in order to determine, analyse and eliminate the causes of undesirable variations."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.4a","Requirement","ECSS-Q-ST-20_0380110",1,"Created","The supplier shall employ workmanship standards throughout all phases of manufacturing, assembly and integration, to ensure acceptable and consistent workmanship quality levels."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.4b","Requirement","ECSS-Q-ST-20_0380111",1,"Created","Workmanship standards shall identify acceptance or rejection criteria."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.4c","Requirement","ECSS-Q-ST-20_0380112",1,"Created","Physical samples or visual aids shall be reviewed and agreed by the customer when they are used for the purpose of acceptance or rejection of items."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.5a","Requirement","ECSS-Q-ST-20_0380113",1,"Created","The supplier shall ensure that only conforming items are released and used, and that those not required for the operation involved are removed from work operation areas."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.5b","Requirement","ECSS-Q-ST-20_0380114",1,"Created","Items having limited-life or definite characteristics of quality degradation or drift with age or use shall be marked to indicate the dates, test times or cycles at which life was initiated and at which the useful life expires."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.5c","Requirement","ECSS-Q-ST-20_0380115",1,"Created","Sensitive items shall be processed or manufactured, inspected and tested in a controlled environment to prevent any degradation.\n    NOTE Requirements for the selection and control of materials and parts are defined in ECSS-Q-ST-70."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.6.1a","Requirement","ECSS-Q-ST-20_0380116",1,"Created","The supplier shall make provisions for accountability, identification and maintenance of manufacture, assembly and integration tooling."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.6.1b","Requirement","ECSS-Q-ST-20_0380117",1,"Created","Manufacture, assembly and integration tooling shall be checked for its dimensional accuracy, regarding the product drawings, and correct function."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.6.1c","Requirement","ECSS-Q-ST-20_0380118",1,"Created","The QA organization shall approve tooling prior to use."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.6.1d","Requirement","ECSS-Q-ST-20_0380119",1,"Created","The approval shall be stamped in conformance with 5.2.4, and recorded."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.6.1e","Requirement","ECSS-Q-ST-20_0380120",1,"Created","Tools shall be checked for accuracy during the production life at adequate intervals."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.6.1f","Requirement","ECSS-Q-ST-20_0380121",1,"Created","Tools shall be submitted to re-approval following modification."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.6.1g","Requirement","ECSS-Q-ST-20_0380122",1,"Created","Tools shall be properly stored to prevent misuse, damage and deterioration."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.6.1h","Requirement","ECSS-Q-ST-20_0380123",1,"Created","Unnecessary tools shall be removed from working areas."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.6.1i","Requirement","ECSS-Q-ST-20_0380124",1,"Created","Records shall be kept of all manufacturing equipment. "]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.6.2a","Requirement","ECSS-Q-ST-20_0380125",1,"Created","The supplier shall ensure that computer-aided techniques and data for processing and machining are validated prior to use and controlled during their use in manufacturing."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.6.2b","Requirement","ECSS-Q-ST-20_0380126",1,"Created","The supplier shall ensure that provisions are made for the testing, approval and configuration control of the software involved and prevention of its being tampered with."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.7.1a","Requirement","ECSS-Q-ST-20_0380127",1,"Created","The supplier shall establish controls for cleanliness of spacecraft hardware and facilities, and the limitation of sources of contamination.\n    NOTE Cleanliness and contamination control methods and processes are detailed in ECSS-Q-ST-70-01."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.7.2a","Requirement","ECSS-Q-ST-20_0380128",1,"Created","Contamination-sensitive items shall be cleaned, controlled and maintained to the required cleanliness levels."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.7.2b","Requirement","ECSS-Q-ST-20_0380129",1,"Created","The required cleanliness levels for all levels of flight hardware shall be indicated on drawings, specifications, procedures, or other documents controlling the manufacture, assembly, integration and test of the items. "]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.7.3a","Requirement","ECSS-Q-ST-20_0380130",1,"Created","The supplier shall develop detailed methods for attaining the cleanliness levels specified for the hardware."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.7.4a","Requirement","ECSS-Q-ST-20_0380131",1,"Created","Contamination shall be minimized by operating in clean working areas and by proper handling, preservation, packaging and storage."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.7.4b","Requirement","ECSS-Q-ST-20_0380132",1,"Created","Contamination-sensitive items fabricated or processed in contamination-controlled environments shall be inspected, tested, modified or repaired in identical or cleaner environments, unless specific precautions are taken to protect the items concerned from contamination."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.7.4c","Requirement","ECSS-Q-ST-20_0380133",1,"Created","Specific protection measures, such as protective dust covers, shall be implemented to protect contamination-sensitive items when they are integrated in a higher level of assembly."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.7.5a","Requirement","ECSS-Q-ST-20_0380134",1,"Created","Fabrication, assembly and integration of contamination sensitive items shall be conducted in facilities that provide cleanliness levels compatible with the specified product cleanliness."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.8a","Requirement","ECSS-Q-ST-20_0380135",1,"Created","Inspection and tests shall be planned at the points of the manufacturing, assembly and integration flow where maximum assurance for correct processing and prevention of unrecoverable or costly nonconformances can be obtained."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.8b","Requirement","ECSS-Q-ST-20_0380136",1,"Created","All identified critical characteristics shall be inspected as defined in the critical-item control programme."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.8c","Requirement","ECSS-Q-ST-20_0380137",1,"Created","Self-inspection by the operators performing the associated manufacturing, assembly and integration activities shall not be considered sufficient for critical characteristics."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.8d","Requirement","ECSS-Q-ST-20_0380138",1,"Created","Among the inspections and tests as part of the manufacturing, assembly and integration flow, mandatory inspection points (MIPs) shall be performed with participation of the customer."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.8e","Requirement","ECSS-Q-ST-20_0380139",1,"Created","MIPs shall be agreed with the customer."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.8f","Requirement","ECSS-Q-ST-20_0380140",1,"Created","MIPs shall be selected in accordance with the criteria as defined below, when one or more of the following conditions apply:\n    1. When maximum visibility of quality is given.\n    2. When critical processes are performed.\n    3. Where the next step of the manufacturing sequence:\n        (a) is irreversible, or\n        (b) makes the item difficult and costly to disassemble for inspection, or\n        (c) renders the location inaccessible for inspection.\n    4. When the item, once installed in the next higher assembly damages by its failure the higher assembly.\n    5. When previous failure history of the item indicates a need for inspection.\n    6. When a potential adverse impact on the properties and integrity of the end product could result, owing to the criticality or complexity of the manufacturing step.\n    7. When testing or critical inspections cannot be accomplished by the supplier.\n        NOTE For example, environments or test equipment not available at supplier’s facility.\n    8. When verification tests are destructive in nature and the quality cannot be verified solely by inspection or test at the supplier’s facility.\n    9. When manufacturing and AIV of complex equipment or subsystems is planned.\n        NOTE For example, for payloads.\n    10. When past performance or quality history of the lower level supplier is marginal.\n    11. When an item is going to final inspection."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.8g","Requirement","ECSS-Q-ST-20_0380141",1,"Created","Criteria 5.5.8f.7 to 10 shall be considered together with the criticality and complexity of the supplies and the supplier’s experience with the lower level supplier."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.8h","Requirement","ECSS-Q-ST-20_0380142",1,"Created","A MIP shall require an invitation with the agreed notice before the event, and the participation of the customer, or their written agreement to proceed without their participation."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.8i","Requirement","ECSS-Q-ST-20_0380143",1,"Created","The supplier shall make provisions for a positive identification of the inspection and test status of any items at any stage of the manufacturing, assembly and integration cycle, starting from the incoming inspection up to shipping of the end item."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.9.1a","Requirement","ECSS-Q-ST-20_0380144",1,"Created","The supplier shall ensure the control of flight items which are temporarily removed or non-flight items which are temporarily installed to facilitate assembly, integration, testing, handling or preservation of the end item."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.9.1b","Requirement","ECSS-Q-ST-20_0380145",1,"Created","The control shall be initiated upon installation or removal of the first temporarily installed or removed item and be maintained through delivery and use of the end item."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.9.1c","Requirement","ECSS-Q-ST-20_0380146",1,"Created","The supplier shall establish and maintain records of temporary installations and removals."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.9.1d","Requirement","ECSS-Q-ST-20_0380147",1,"Created","Temporarily installed items shall be accounted for to prevent their being incorporated in the final flight configuration."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.9.2a","Requirement","ECSS-Q-ST-20_0380148",1,"Created","The supplier shall prepare and maintain system, subsystem and equipment logbooks in conformance with the DRD in Annex C for all operations and tests performed on the item during the period to be covered by the logbook."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.9.2b","Requirement","ECSS-Q-ST-20_0380149",1,"Created","Equipment logbooks shall start with the first qualification or acceptance test after assembly."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.9.2c","Requirement","ECSS-Q-ST-20_0380150",1,"Created","Subsystem and system logbooks shall follow-on from the individual equipment logbooks to form a full record."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.9.2d","Requirement","ECSS-Q-ST-20_0380151",1,"Created","The logbook shall accompany the hardware whenever it is placed in the custody of another organization"]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.9.2e","Requirement","ECSS-Q-ST-20_0380152",1,"Created","The receiving organization shall maintain the logbook up-to-date."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.5.10a","Requirement","ECSS-Q-ST-20_0380153",1,"Created","The supplier shall establish and maintain manufacturing, assembly and integration records to provide all manufacturing, assembly, integration and inspection data required for traceability."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.6.1a","Requirement","ECSS-Q-ST-20_0380154",1,"Created","The supplier shall ensure that test facilities, either internal or external, conform to specified requirements."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.6.2a","Requirement","ECSS-Q-ST-20_0380155",1,"Created","The supplier shall ensure that computer-aided testing techniques and data are validated prior to use and controlled during their use in testing."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.6.2b","Requirement","ECSS-Q-ST-20_0380156",1,"Created","The supplier shall ensure that provisions are made for testing, approval and configuration control of the software involved and prevention of its being tampered with."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.6.2c","Requirement","ECSS-Q-ST-20_0380157",1,"Created","The supplier shall ensure that test equipment are designed such that their correct operation can be verified without having to apply them to the test item."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.6.3.1a","Requirement","ECSS-Q-ST-20_0380158",1,"Created","The supplier shall ensure that tests are performed in accordance with documented procedures, which shall include, as a minimum:\n    1. scope of the test, including the identification of the requirement being verified,\n    2. identification of the test object,\n    3. applicable documents, with their revision status,\n    4. test flow,\n    5. test organization,\n    6. test conditions,\n    7. test equipment and set-up,\n    8. step-by-step procedure, including definition of specific steps to be witnessed by QA personnel,\n    9. recording of data,\n    10. pass or fail criteria and test data evaluation requirements, and\n    11. guidelines or criteria for deviation from test procedure and for retest."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.6.3.1b","Requirement","ECSS-Q-ST-20_0380159",1,"Created","The QA organization shall review and approve test procedures."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.6.3.2a","Requirement","ECSS-Q-ST-20_0380160",1,"Created","The supplier shall ensure that all tests are comprehensively documented in test reports, and that they include, as a minimum:\n    1. reference to the applicable test procedure, and description of the deviations from it during the actual testing,\n    2. test data records and evaluation, and\n    3. summary of test results."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.6.3.2b","Requirement","ECSS-Q-ST-20_0380161",1,"Created","The QA organization shall review and approve test reports."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.6.4a","Requirement","ECSS-Q-ST-20_0380162",1,"Created","On the basis of an analysis of the test plan, the QA organization shall define within the test plan the most appropriate way to monitor the performance of test activities, to ensure the adherence to the test procedures, and that any deviations are properly documented and treated."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.6.4b","Requirement","ECSS-Q-ST-20_0380163",1,"Created","Test witnessing by QA personnel shall be considered when manual intervention is performed, at the setting-up, start and end of continuous fully automated test sequences, or when no automatic recording of test parameters or results is available."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.6.4c","Requirement","ECSS-Q-ST-20_0380164",1,"Created","All testing activities related to critical characteristics as identified in the critical-items control programme shall be certified."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.6.4d","Requirement","ECSS-Q-ST-20_0380165",1,"Created","Self-certification by the operators performing the test activities shall not be considered sufficient for critical characteristics."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.6.4e","Requirement","ECSS-Q-ST-20_0380166",1,"Created","Testing activities or results to be subject to QA certification shall be identified as such in the relevant test procedure."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.6.4f","Requirement","ECSS-Q-ST-20_0380167",1,"Created","Testing shall be subject to the requirements for the control of hazardous operations.\n    NOTE Definition of hazardous operations is given in ECSS-Q-ST-40."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.6.4g","Requirement","ECSS-Q-ST-20_0380168",1,"Created","Where safety of personnel or damage to items or associated test equipment is possible, QA personnel shall have the authority to stop the test."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.6.5a","Requirement","ECSS-Q-ST-20_0380169",1,"Created","The supplier shall ensure that formal reviews are performed before and after major portions of qualification or acceptance tests."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.6.5b","Requirement","ECSS-Q-ST-20_0380170",1,"Created","The QA organization shall be represented in the formal boards established for the review of readiness for testing and testing accomplishment."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.7.1a","Requirement","ECSS-Q-ST-20_0380171",1,"Created","The supplier shall establish a formal acceptance process for all deliverable items, at any contractual level, to ensure that conformance of the items to be delivered is fully assessed and documented."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.7.1b","Requirement","ECSS-Q-ST-20_0380172",1,"Created","The supplier shall ensure that the preparation of the items for delivery and the physical delivery itself are performed in such a way that quality degradation is prevented."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.7.2a","Requirement","ECSS-Q-ST-20_0380173",1,"Created","The supplier shall provide an EIDP for each deliverable end item in conformance with the DRD in Annex B."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.7.2b","Requirement","ECSS-Q-ST-20_0380174",1,"Created","The EIDP shall constitute the basis for formal acceptance reviews."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.7.2c","Requirement","ECSS-Q-ST-20_0380175",1,"Created","EIDPs shall be maintained and integrated into higher level EIDPs during subsystem or system integration and testing. "]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.7.3a","Requirement","ECSS-Q-ST-20_0380176",1,"Created","The supplier shall ensure that a DRB is convened prior to the delivery of equipment, separately assembled subsystems, test equipment or handling equipment for higher level activities.\n    NOTE “Acceptance Review Board” (ARB) defined in ECSS-M-ST-10 is referred to as “Delivery Review Board” (DRB) in this document."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.7.3b","Requirement","ECSS-Q-ST-20_0380177",1,"Created","The DRB functions at system level shall be fulfilled by the final acceptance review and chaired by the customer."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.7.3c","Requirement","ECSS-Q-ST-20_0380178",1,"Created","The DRB shall be composed, at least, of the following members:\n    1. Representatives of the receiving organization:\n        (a) Project manager, or authorized representative, as chairman;\n        (b) PA manager, or authorized representative;\n        (c) Engineering or design manager, or authorized representative.\n    2. Submitting supplier’s representatives:\n        (a) Project manager, or authorized representative;\n        (b) PA manager, or authorized representative;\n        (c) Engineering or design manager, or authorized representative.\n    3. Higher level customers’ representative(s), as observers (not required for separate subsystems)."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.7.3d","Requirement","ECSS-Q-ST-20_0380179",1,"Created","If the final customer reserves the right to attend DRBs at any lower level as an observer, he shall be given due notice of such a DRB meeting."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.7.3e","Requirement","ECSS-Q-ST-20_0380180",1,"Created","The DRB shall be responsible for authorising the shipment of the items under acceptance, and certifying in writing that:\n    1. the items conform to the contractual requirements and to an approved design configuration;\n    2. the items are free from material and workmanship deficiencies;\n    3. all nonconformances are closed-out, or corresponding plans, compatible with the delivery, are accepted;\n    4. the relevant EIDP is complete and accurate."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.7.3f","Requirement","ECSS-Q-ST-20_0380181",1,"Created","Delivery shall only be authorized by the unanimous agreement of the DRB members."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.7.3g","Requirement","ECSS-Q-ST-20_0380182",1,"Created","For the delivery a certificate of conformity, in conformance with Annex D, shall be made available and signed by the supplier."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.7.4.1a","Requirement","ECSS-Q-ST-20_0380183",1,"Created","The supplier shall ensure that packaging materials, methods, procedures and instructions provide for protection of items while at the supplier’s plant, during transportation, and after their arrival at destination."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.7.4.2a","Requirement","ECSS-Q-ST-20_0380184",1,"Created","The supplier shall ensure that appropriate marking and labelling for packaging, storage, transportation and shipping of items are performed in accordance with the applicable specifications."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.7.5.1a","Requirement","ECSS-Q-ST-20_0380185",1,"Created","The supplier shall ensure that the items to be shipped from his plant are inspected before release and found to be complete, adequately preserved and packaged, correctly marked and accompanied by all the required documentation."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.7.5.1b","Requirement","ECSS-Q-ST-20_0380186",1,"Created","Accompanying documentation shall include the EIDP and, attached to the outside of the shipping container, the handling and packing or unpacking procedure and any relevant safety procedures."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.7.5.2a","Requirement","ECSS-Q-ST-20_0380187",1,"Created","The supplier shall make provisions for the prevention of damage to items during transportation."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.8.1.1.1a","Requirement","ECSS-Q-ST-20_0380188",1,"Created","The supplier shall ensure that internal design and verification standards are used or developed corresponding with the techniques to be used and fitting with the level of complexity of the items to be developed."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.8.1.1.1b","Requirement","ECSS-Q-ST-20_0380189",1,"Created","The supplier shall ensure that development risks are identified and appropriate back-up solutions are identified."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.8.1.1.1c","Requirement","ECSS-Q-ST-20_0380190",1,"Created","The supplier shall ensure that the verification method and process are tailored to the:\n    1. complexity of the item to be verified;\n    2. criticality of the function to be implemented by the GSE item;\n    3. inherent criticality of the item itself."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.8.2a","Requirement","ECSS-Q-ST-20_0380191",1,"Created","The supplier shall ensure that GSE is configuration controlled."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.8.3.1a","Requirement","ECSS-Q-ST-20_0380192",1,"Created","The supplier shall ensure that selected GSE suppliers have a demonstrated ability to conform to requirements, through:\n    1. previous supply of items similar or more complex in the same field of techniques and technologies,\n    2. certification covering similar design, development and production as applicable for similar items in conformance with 5.4.1.2, or\n    3. evidence, documented by existing design, development, production and quality standards, of having similar experience associated with known success."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.8.3.1b","Requirement","ECSS-Q-ST-20_0380193",1,"Created","Procurement documents shall identify validation and receiving inspection requirements, and conform to the requirements in clause 5.4.2."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.8.3.2a","Recommendation","ECSS-Q-ST-20_0380228",1,"Created","The supplier and his lower level suppliers should not deviate from their standard practices when these are already documented and recognized for similar items."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.8.4.1a","Requirement","ECSS-Q-ST-20_0380195",1,"Created","The acceptance data package shall include :\n    1. information regarding interfaces,\n    2. deviations from contractual requirements,\n    3. certification of conformance to an identified baseline,\n    4. description of the functioning of the item, and instructions to operate and maintain it, and\n    5. safety data or safety certification(s)."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.8.5a","Requirement","ECSS-Q-ST-20_0380196",1,"Created","Acceptance shall be achieved through a formal review process \n    NOTE Review process is defined in ECSS-M-ST-10-01."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.8.5b","Requirement","ECSS-Q-ST-20_0380197",1,"Created","The acceptance process shall include:\n    1. acceptance plan,\n    2. inspection and test procedures, and\n    3. inspection and test reports."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.8.5c","Permission","ECSS-Q-ST-20_0380229",1,"Created","Acceptance may be achieved through a simple inspection process if agreed between customer and supplier."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.8.6a","Requirement","ECSS-Q-ST-20_0380199",1,"Created","The supplier shall propose GSE elements for which acceptance is granted by a delivery board and agree these with his customer."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.8.6b","Requirement","ECSS-Q-ST-20_0380200",1,"Created","The delivery board shall include QA representatives from the supplier and the customer."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.8.7a","Requirement","ECSS-Q-ST-20_0380201",1,"Created","The requirements of the following clauses shall be applied to the delivery of ground items and handling, storage, packing and shipping activities:\n    1. preparation for delivery, in conformance with 5.7.4,\n    2. delivery, in conformance with 5.7.5, and\n    3. handling, storage and preservation, in conformance with 5.2.7."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.8.8a","Requirement","ECSS-Q-ST-20_0380202",1,"Created","The following requirements shall be tailored in accordance with the complexity and criticality of the GSE item:\n    1. traceability requirements in 5.2.5, and\n    2. metrology and calibration requirements in 5.2.6."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.8.9a","Requirement","ECSS-Q-ST-20_0380203",1,"Created","The supplier shall ensure that maintenance activities are planned."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","5.8.9b","Requirement","ECSS-Q-ST-20_0380204",1,"Created","The supplier shall ensure that maintenance demonstration is performed in order to prove that maintainability requirements are satisfied in the real operational environment."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","A.2.1<1>a","Requirement","ECSS-Q-ST-20_0380205",1,"Created","The Quality Assurance Plan shall introduce the purpose, objective and the reason prompting its preparation "]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","A.2.1<2>a","Requirement","ECSS-Q-ST-20_0380206",1,"Created","The Quality Assurance Plan shall list the applicable and reference documents in support of the generation of the document."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","A.2.1<3>a","Requirement","ECSS-Q-ST-20_0380207",1,"Created","The Quality Assurance Plan shall describe the activities to be applied to fulfil the applicable quality assurance general requirements defined in ECSS-Q-ST-20 clause 5.1."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","A.2.1<4>a","Requirement","ECSS-Q-ST-20_0380208",1,"Created","The Quality Assurance Plan shall describe the activities to be applied to fulfil the applicable Quality assurance requirements for design and verification defined in ECSS-Q-ST-20 clause 5.3."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","A.2.1<5>a","Requirement","ECSS-Q-ST-20_0380209",1,"Created","The Quality Assurance Plan shall describe the activities to be applied to fulfil the applicable Quality assurance requirements for procurement defined in ECSS-Q-ST-20 clause 5.4"]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","A.2.1<6>a","Requirement","ECSS-Q-ST-20_0380210",1,"Created","The Quality Assurance Plan shall describe the activities to be applied to fulfil the applicable Quality assurance requirements for manufacturing, assembly and integration defined in ECSS-Q-ST-20 clause 5.5."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","A.2.1<7>a","Requirement","ECSS-Q-ST-20_0380211",1,"Created","The Quality Assurance Plan shall describe the activities to be applied to fulfil the applicable Quality assurance requirements for testing defined in ECSS-Q-ST-20 clause 5.6."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","A.2.1<8>a","Requirement","ECSS-Q-ST-20_0380212",1,"Created","The Quality Assurance Plan shall describe the activities to be applied to fulfil the applicable Quality assurance requirements for acceptance and delivery defined in ECSS-Q-ST-20 clause 5.7."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","A.2.2a","Permission","ECSS-Q-ST-20_0380230",1,"Created","The response to this DRD may be combined with the response to the product assurance plan, as defined in ECSS-Q-ST-10."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","B.2.1a","Requirement","ECSS-Q-ST-20_0380214",1,"Created","The EIDP shall include the following information and documentation:\n    1. The DRB minutes\n    2. The customer acceptance certificate if not covered in DRB minutes\n    3. Cover page\n        NOTE An example is given in Annex F.\n    4. Table of contents\n        NOTE An example is given in Annex G.\n    5. Change record\n    6. The product certificate of conformity in conformance with Annex D.\n    7. NCR list\n    8. ABCL\n    9. Summary and status of RFDs and RFWs raised and processed on the product\n    10. The product logbook\n    11. Product definition documents to be used for further integration, testing and operation in higher level assemblies including the software used to operate the item and the product user or operating manuals.\n    12. Procedures to be used for the proper handling of the product after its final delivery, including procedures for:\n        (a) packing,\n        (b) handling,\n        (c) storage,\n        (d) transportation,\n        (e) safety, and\n        (f) cleanliness.\n    13. Copies of the product test reports, or as a minimum the list of the documents with the identification of their location.\n    14. List of delivered ground support equipment (e.g.: MGSE, EGSE, FGSE, OGSE) with the reference to their corresponding EIDPs and software product.\n    15. List of EIDPs or logbooks of units and subsystem supplied by lower tier suppliers.\n    16. List of the loose items and not installed items supplied with the product.\n    17. Any additional useful information or data relevant to the product.\n        NOTE For example, cleanliness certification when cleanliness is a requirement."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","C.2.1a","Requirement","ECSS-Q-ST-20_0380215",1,"Created","The logbook cover page shall contain the following:\n    1. general information,\n    2. contents,\n    3. approvals of the relevant authorities (QA, PA, PM), and\n    4. customer acceptance (if required by the business agreement).\n        NOTE An example of a logbook cover page is given in Annex E."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","C.2.1b","Requirement","ECSS-Q-ST-20_0380216",1,"Created","The logbook shall contain the “hardware configuration and traceability” table, which reports all the identification references of single elements composing the CI. "]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","C.2.1c","Requirement","ECSS-Q-ST-20_0380217",1,"Created","The logbook shall contain the “hardware configuration change and status” table, which reports for each singe element of the CI all the events relevant to integration, removal and replacement on the higher level."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","C.2.1d","Requirement","ECSS-Q-ST-20_0380218",1,"Created","The logbook shall contain the summary list of the integration and test instructions, including for each entry, the action start date, action performed date and action close-out date shall also be reported.\n    NOTE Example: shop traveller"]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","C.2.1e","Requirement","ECSS-Q-ST-20_0380219",1,"Created","The logbook shall contain the summary list of nonconformances with relevant identification references, issue date, closure dates, and status."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","C.2.1f","Requirement","ECSS-Q-ST-20_0380220",1,"Created","The logbook shall contain all the electrical connector (or other limited cycles items) mate and demate cycles in order to ensure the conformance with the project requirements."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","C.2.1g","Requirement","ECSS-Q-ST-20_0380221",1,"Created","The logbook shall contain the records of total operating hours for each limited-life element identified in the test procedures."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","C.2.1h","Requirement","ECSS-Q-ST-20_0380222",1,"Created","The logbook shall contain, in chronological order, the events related to the integration and test activities performed on the relevant item (i.e. system, subsystem, and equipment), including the following:\n    1. Action requested form, reporting all the operations performed with the references to the applicable documents or procedures, start date, completion date and quality inspection stamps.\n    2. Step-by-step procedures and results, in which copies of the as-run procedures are included in a suitable format.\n    3. Procedures variation form, in which copies of modified procedures (red marked) identified with a procedure variation number and duly approved by responsible authorities, are included. "]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","C.2.1i","Requirement","ECSS-Q-ST-20_0380223",1,"Created","The logbook shall contain the list of open action or open test at the time of the product shipment to the customer, test facility or launch pad."]
["ECSS-Q-ST-20C","ECSS - Superseded v1.0","D.2.1a","Requirement","ECSS-Q-ST-20_0380224",1,"Created","The DoC shall contain the following elements:\n    1. Title including references to identify the product and the relevant applicable documents\n        NOTE Examples for references are item name, project, serial number, part number, customer, contract number.\n    2. Document no. in accordance with project configuration control rules;\n    3. EIDP reference number;\n    4. Intended use, specifying the item objective (i.e. BB, QM, FM)\n    5. Reference of conformity, calling for example the following documents:\n        (a) Business agreement requirements: reference number of design spec., ICD or other contractual documents;\n        (b) Operational documents: reference number of drawings, procedures, and electrical schemes;\n        (c) Deliverable documents: reference number of EIDP, logbooks, and manuals.\n    6. Statement of conformity.\n    7. List of waivers or deviations or other remarks."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.1.2a","Requirement","ECSS-Q-ST-70_0490001",1,"Created","The supplier shall prepare, maintain and implement a MMPP plan, as part of the overall PA plan in conformance to ECSS-Q-ST-10 and this Standard or as a separate document."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.1.2b","Requirement","ECSS-Q-ST-70_0490002",1,"Created","The MMPP plan shall be submitted to the customer for approval."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.1.3a","Requirement","ECSS-Q-ST-70_0490003",1,"Created","To obtain the validation status for materials and qualification status for parts and verification status for processes, the MMPP manager shall present to the customer those activities which were performed in order to comply with this Standard together with results obtained."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.1.3b","Requirement","ECSS-Q-ST-70_0490004",1,"Created","The MMPP manager shall organize technical review meetings with his suppliers at all levels."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.2.2a","Requirement","ECSS-Q-ST-70_0490005",1,"Created","Each supplier and sub-supplier shall establish, collect, review and deliver the declared materials, mechanical parts and processes lists including all the items intended for use in the flight equipment."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.2.2b","Requirement","ECSS-Q-ST-70_0490006",1,"Created","The lists shall reflect the current design at the time of issue."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.2.2c","Requirement","ECSS-Q-ST-70_0490007",1,"Created","These lists shall contain the materials, mechanical parts and processes used in the current design in order to: \n    1. demonstrate compliance with all requirements of the programme;\n    2. verify the results of equipment supplier activities;\n    3. control and monitor the status of materials, mechanical parts and processes in accordance with programme milestones.\n        NOTE See Annex F."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.2.2d","Recommendation","ECSS-Q-ST-70_0490194",1,"Created","The following constraints should apply:\n    1. maximum use of the materials and processes described in approved data sources and items already approved on similar projects;\n        NOTE For approved data sources see for example ECSS-Q-ST-70-71.\n    2. use of project related preferred lists, if available."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.2.2e","Requirement","ECSS-Q-ST-70_0490009",1,"Created","The following constraints shall be taken into account: \n    1. requirements originating from the initial technical specification;\n    2. programmatic project requirements and conditions;"]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.2.2f","Requirement","ECSS-Q-ST-70_0490010",1,"Created","An analysis of the criticality of these preliminary lists shall, after checking the conformity of the materials, mechanical parts and processes, against all the project requirements, allow them to be classified into three categories:\n    1. Critical items, subject to evaluation, validation, qualification, or verification programmes.\n    2. Items that are not critical but which do not conform to one or more project requirements (a justified deviation request should be drafted for this category).\n    3. Non-critical items."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.2.2g","Requirement","ECSS-Q-ST-70_0490011",1,"Created","For critical items a request for approval shall be submitted in conformance with Annex D."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.2.3a","Requirement","ECSS-Q-ST-70_0490012",1,"Created","The supplier shall document all materials in the Declared materials list in conformance with Annex A."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.2.3b","Requirement","ECSS-Q-ST-70_0490013",1,"Created","The supplier shall document all mechanical parts in the Declared mechanical parts list in conformance with Annex B."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.2.3c","Requirement","ECSS-Q-ST-70_0490014",1,"Created","The supplier shall document all processes in the Declared process list in conformance with Annex C."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.2.3d","Requirement","ECSS-Q-ST-70_0490015",1,"Created","The supplier shall process the lists of lower level suppliers to ensure exchangeabililty, searchability, sortability, storability and retrievability for that set of lists, before submitting it to the customer."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.2.3e","Requirement","ECSS-Q-ST-70_0490016",1,"Created","These lists shall be updated during the course of the project."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.2.3f","Requirement","ECSS-Q-ST-70_0490017",1,"Created","The preliminary lists shall include the items from suppliers’ preliminary needs.\n    NOTE They are used to identify critical items (available for the PDR)."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.2.3g","Requirement","ECSS-Q-ST-70_0490018",1,"Created","The as-designed lists shall include the items from the baselines various design files (available for the CDR)."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.2.3h","Requirement","ECSS-Q-ST-70_0490019",1,"Created","Any change after CDR or QR shall be reflected in the list and shall be in accordance with Figure 4-1 (Part 2).\n    NOTE 1 The MMPP manager is responsible within the programme to ensure that all the information needed is given and that the approval status is consistent with technical and scheduling objectives and data is exchangeable.\n    NOTE 2 Where no project requirements exist for a separate DMPL, the mechanical parts can be entered into a separate section of the DML.\n    NOTE 3 The materials of, for example, screws and nuts that are made up of a few materials can be listed in the DMPL. The materials (metals and plastics) of complex parts can be listed in the DML with, for example, outgassing, toxicity, flammability, corrosion and stress corrosion values and reference to the DMPL item."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.2.4a","Requirement","ECSS-Q-ST-70_0490020",1,"Created","The supplier shall perform the following tasks:\n    1. obtaining the correct and complete lists from lower level suppliers;\n    2. providing provisional and, later, definitive approval for each list;\n    3. submitting the project declared lists for approval prior to initiation of the hardware phase (before critical design review)."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.2.4b","Requirement","ECSS-Q-ST-70_0490021",1,"Created","The lists established by the suppliers shall include all the information described in this Standard."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.2.4c","Requirement","ECSS-Q-ST-70_0490022",1,"Created","Amendments to the lists shall be implemented only through established change procedures."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.2.4d","Requirement","ECSS-Q-ST-70_0490023",1,"Created","The following documentation shall be delivered to the customer upon request:\n    1. RFA (reference and issue);\n    2. evaluation reports;\n    3. deviation requests."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.2.4e","Requirement","ECSS-Q-ST-70_0490024",1,"Created","The material, mechanical parts or process justification files shall be made available to the customer upon request either on the supplier site, or by any other process agreed by both parties.\n    NOTE For example, by non-disclosure agreement."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.3a","Requirement","ECSS-Q-ST-70_0490025",1,"Created","Parts and materials shall satisfy the mission’s functional constraints."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.3b","Requirement","ECSS-Q-ST-70_0490026",1,"Created","Parts and materials shall satisfy both ground environment constraints and flight constraints.\n    NOTE Examples are:\n        · Ground environment constraints: manufacture, tests, storage, maintenance, transport and integration\n        · Flight constraints: launch and orbit."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.3c","Requirement","ECSS-Q-ST-70_0490027",1,"Created","The technical criteria from clause 5.1 shall be taken into account, according to the mission."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.3d","Requirement","ECSS-Q-ST-70_0490028",1,"Created","The estimated availability of the parts and products obtained from materials and processes used shall be compatible with the final system’s life cycle (tests, storage and mission)."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.4a","Requirement","ECSS-Q-ST-70_0490029",1,"Created","The supplier shall establish and maintain a contamination and cleanliness control programme including, as a minimum:\n    1. cleaning procedures, and\n    2. cleanliness monitoring procedures or methods."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.4b","Requirement","ECSS-Q-ST-70_0490030",1,"Created","The risks of chemical or particle pollution generated by parts, materials or processes used shall be identified and reduced in accordance with mission requirements (cleanliness or contamination analysis)."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.4c","Requirement","ECSS-Q-ST-70_0490031",1,"Created","For cleanliness- or contamination-critical applications, a requirement specification (chemical and particle) and a specific cleanliness control plan and shall be established in conformance with Annex A (CRS DRD) and Annex B (C&CCP DRD) of ECSS-Q-ST-70-01."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.5a","Requirement","ECSS-Q-ST-70_0490032",1,"Created","Parts and materials with hazardous characteristics shall be identified, managed and processed in conformance with ECSS-Q-ST-40."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","4.6a","Requirement","ECSS-Q-ST-70_0490033",1,"Created","When optical, mechanical or electrical GSE materials are used in thermal vacuum or interfacing with flight hardware, possible degradation shall be taken into account.\n    NOTE For example, contamination, surface degradation, electro-mechanical and chemical effects."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.2a","Requirement","ECSS-Q-ST-70_0490034",1,"Created","Material properties shall be compatible with the thermal environment to which they are exposed."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.3a","Requirement","ECSS-Q-ST-70_0490035",1,"Created","Materials subject to thermal cycling shall be assessed for their ability to withstand induced thermal stress."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.3b","Requirement","ECSS-Q-ST-70_0490036",1,"Created","The following materials shall be tested in conformance with ECSS-Q-ST-70-04:\n    1. Materials susceptible to thermal vacuum effect.\n        NOTE For a non-exhaustive list of such materials, see ECSS-Q-ST-70-04 Clause 1.\n    2. Materials of unknown characteristics in respect to thermal vacuum."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.3c","Requirement","ECSS-Q-ST-70_0490037",1,"Created","Materials subject to thermal cycling other than those covered by 5.1.3b, shall be tested in accordance with a procedure approved by the customer."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.4a","Requirement","ECSS-Q-ST-70_0490038",1,"Created","Materials selection shall be made in conformance with ECSS-Q-ST-70-71."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.4b","Requirement","ECSS-Q-ST-70_0490039",1,"Created","Outgassing tests shall be carried out in conformance with ECSS-Q-ST-70-02.\n    NOTE The need for retest of materials used for an extended period of time at a temperature higher than 50 °C should be mutually agreed with the customer."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.5a","Requirement","ECSS-Q-ST-70_0490040",1,"Created","Spacecraft and associated equipment shall be manufactured from materials and by processes that do not cause a hazard to personnel or hardware, whether on the ground or in space."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.5b","Requirement","ECSS-Q-ST-70_0490041",1,"Created","ECSS-Q-ST-70-29 shall apply for the characterization of offgassing products.\n    NOTE MAPTIS and MIL-HDBK-454 test method is not space relevant."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.6a","Requirement","ECSS-Q-ST-70_0490042",1,"Created","The materials flammability resistance shall be evaluated in conformance with ECSS-Q-ST-70-21 for the most hazardous environment envisaged for their use.\n    NOTE For NASA STS payloads see NASA STD-6001."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.7a","Requirement","ECSS-Q-ST-70_0490043",1,"Created","Materials used on the spacecraft external surfaces shall be assessed in conformance with ECSS-Q-ST-70-06 in order to determine their resistance to the radiation dosage expected during the mission."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.8a","Requirement","ECSS-Q-ST-70_0490044",1,"Created","External surfaces of the spacecraft shall be sufficiently conductive, interconnected and grounded to the spacecraft structure to avoid the build-up of differential charges in conformance with ECSS-E-ST-20-06."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.9a","Requirement","ECSS-Q-ST-70_0490045",1,"Created","For all materials that come into contact with atmospheric gases, cleaning fluids or other chemicals, it shall be demonstrated that the degradation of properties during their anticipated service-life is acceptable in terms of the performance and integrity requirements."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.10a","Requirement","ECSS-Q-ST-70_0490046",1,"Created","Materials used for structural and load-bearing applications (subject to tensile stress) shall be chosen in conformance with ECSS-Q-ST-70-36."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.10b","Requirement","ECSS-Q-ST-70_0490047",1,"Created","Any material not covered by standard ECSS-Q-ST-70-36 shall be tested in conformance with ECSS-Q-ST-70-37."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.11a","Requirement","ECSS-Q-ST-70_0490048",1,"Created","Materials within the system exposed to liquid oxygen (LOX), gaseous oxygen (GOX) or other reactive fluids, both directly and as a result of single point failures when failure propagation effects cause hazardous operation of interfacing hardware shall be compatible with that fluid in their application."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.11b","Requirement","ECSS-Q-ST-70_0490049",1,"Created","The possibility of hydrogen embrittlement occurring during component manufacture or use shall be assessed, and an material evaluation be undertaken, including the assessment of adequate protection and control."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.12a","Requirement","ECSS-Q-ST-70_0490050",1,"Created","When bimetallic contacts are used, the choice of the pair of metallic materials used shall be agreed with the customer. \n    NOTE This also includes metal-to-conductive fibre-reinforced materials contacts."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.12b","Requirement","ECSS-Q-ST-70_0490051",1,"Created","Galvanic compatibilities shall be selected in conformance with Table 5-1."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.12c","Requirement","ECSS-Q-ST-70_0490052",1,"Created","Materials not listed in Table 5-1 shall be evaluated in a flight-simulated configuration using an accelerated environment to be agreed by the customer."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.13a","Requirement","ECSS-Q-ST-70_0490053",1,"Created","All materials considered for use on the external surfaces of spacecraft intended for use in Low Earth Orbit (LEO) altitudes (between 200 km and 700 km) shall be evaluated for their resistance to atomic oxygen (ATOX)."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.13b","Requirement","ECSS-Q-ST-70_0490054",1,"Created","Test procedures shall be subject to the approval of the customer."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.14a","Requirement","ECSS-Q-ST-70_0490055",1,"Created","The effect of impacts by micrometeoroids and debris on materials shall\n    1. be reviewed and assessed on a case by case basis, and\n    2. their use comply with safety evaluation and assessment results concerning design and application criteria or details."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.15a","Requirement","ECSS-Q-ST-70_0490056",1,"Created","Precautions shall be taken to avoid moisture absorption during manufacture and storage of CFRP-type materials in conformance with ECSS-Q-ST-70-01 and ECSS-Q-ST-70-22."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.16a","Requirement","ECSS-Q-ST-70_0490057",1,"Created","For all solid surfaces in moving contact with other solid surfaces, it shall be demonstrated that the degradation of surface properties over the complete mission is acceptable from a performance point of view."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.1.17a","Requirement","ECSS-Q-ST-70_0490058",1,"Created","Materials shall be selected to ensure sufficient life with respect to the intended application."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.2.1a","Requirement","ECSS-Q-ST-70_0490059",1,"Created","Materials shall be chosen giving preference to the following:\n    1. those successfully used for an identical application in other space programmes similar with respect to environment constraints and lifetime to the proposed application;\n    2. those for which satisfactory evaluation results are obtained on samples representative of the application with a sufficient margin as regards conditions of use;\n    3. those included in approved data sources.\n        NOTE For example: ECSS-Q-ST-70-71, ESA and NASA data banks."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.2.1b","Requirement","ECSS-Q-ST-70_0490060",1,"Created","Whether the materials are already validated or remain to be validated, their selection shall take into account the following criteria:\n    1. continuity of supply;\n    2. reproducibility of characteristics."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.2.2a","Requirement","ECSS-Q-ST-70_0490061",1,"Created","Pure tin finish with more than 97 % purity shall not be used.\n    NOTE This is due to the possibility of whisker growth and transformation to grey tin powder at low temperatures."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.2.2b","Requirement","ECSS-Q-ST-70_0490062",1,"Created","The incoming inspection of each component batch shall include the verification of the termination composition (to avoid assembly of pure tin finish)."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.3a","Requirement","ECSS-Q-ST-70_0490063",1,"Created","The supplier shall establish and maintain a declared materials list in conformance with Annex A."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.4.2a","Requirement","ECSS-Q-ST-70_0490064",1,"Created","The supplier shall analyse all the materials contained in his preliminary lists with respect to criticality and in correlation with the risk analysis performed. "]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.4.2b","Requirement","ECSS-Q-ST-70_0490065",1,"Created","Any material not meeting the project requirements shall be subject to a RFD to be submitted to the next customer."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.4.2c","Requirement","ECSS-Q-ST-70_0490066",1,"Created","Any critical material shall be subject to a RFA to be submitted to the customer."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.4.2d","Requirement","ECSS-Q-ST-70_0490067",1,"Created","For any material not meeting the project requirements the supplier shall submit a RFA in conformance with Annex D.\n    NOTE Any material when specifically required, marking inks can be excluded."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.5.1a","Requirement","ECSS-Q-ST-70_0490068",1,"Created","Depending on the results of the criticality analysis, the supplier shall perform an evaluation phase before the validation phase for all critical materials with unknown characteristics (new materials) or with major changes in the use or in the configuration"]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.5.1b","Permission","ECSS-Q-ST-70_0490195",1,"Created","In case of an extension of an existing application, the evaluation indicated in 5.5.1a need not be performed if so agreed with the customer."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.5.1c","Requirement","ECSS-Q-ST-70_0490070",1,"Created","Guarantied characteristics of materials and material supplier inspection methods, together with associated documents, shall be available for review at the supplier’s premises before the start of evaluation or qualification phases."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.5.2a","Requirement","ECSS-Q-ST-70_0490071",1,"Created","The evaluation shall consider the following as a minimum:\n    1. the limits of use;\n    2. the materials physical, chemical or functional characteristics along with their values and tolerances;\n    3. behavioural tendencies and degradation processes depending on environmental parameters (including sensitivity to pollution);\n    4. acceptance criteria."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.5.2b","Requirement","ECSS-Q-ST-70_0490072",1,"Created","When evaluation is performed, an evaluation programme (available at PDR, according to Figure 4-1) shall be drawn up, implemented and an evaluation report (available before CDR, according to Figure 4-1 and Table 4-1) shall be drawn up."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.5.3a","Requirement","ECSS-Q-ST-70_0490073",1,"Created","For all critical materials, a validation programme (available at PDR) shall be drawn up by the supplier and then implemented to check or confirm that the materials satisfy the mission requirements with appropriate margins as necessary to obtain validation status."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.5.3b","Requirement","ECSS-Q-ST-70_0490074",1,"Created","Validation status shall depend on the results obtained (validation report) and the review of corresponding documentation (available at CDR)."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.5.4a","Requirement","ECSS-Q-ST-70_0490075",1,"Created","The material shall not receive an approval identification in the declared material list for the project unless the requirements in 5.5.2 and 5.5.3 are satisfied."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.5.4b","Requirement","ECSS-Q-ST-70_0490076",1,"Created","If approval is not granted, the supplier in charge of the item shall either:\n    1. select another material, or\n    2. propose a modified evaluation programme and resubmit for approval, or\n    3. if actions 5.5.4b.1 and 5.5.4b.2 fail to achieve positive results, initiate a deviation procedure."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.5.5a","Requirement","ECSS-Q-ST-70_0490077",1,"Created","For materials not conforming to project requirements, whether at the end of criticality analysis or of evaluation and validation tests, the supplier shall submit a request for deviation in conformance with ECSS-Q-ST-10-09."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.6.1a","Requirement","ECSS-Q-ST-70_0490078",1,"Created","All materials shall be procured to an internationally or nationally recognized specification or an in-house fully configured procurement specification which defines the materials properties, the materials requirements, the test methods, the acceptance criteria for the specific applications, source inspection (if any) and material supplier inspection."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.6.1b","Requirement","ECSS-Q-ST-70_0490079",1,"Created","Where material suppliers do not accept specifications and procurement is by means of a datasheet the supplier shall introduce internal, in-house receipt inspection to ensure that the validation status of the material is maintained during the subsequent procurements."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.6.1c","Requirement","ECSS-Q-ST-70_0490080",1,"Created","Materials with long lead times or long procurement delays (versus the project schedule) shall be identified before the formal subsystem PDR. "]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.6.1d","Requirement","ECSS-Q-ST-70_0490081",1,"Created","Procurement shall be thoroughly planned, documented and implemented in a timely manner to obtain reliable product assurance provision at CDR. "]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.6.1e","Requirement","ECSS-Q-ST-70_0490082",1,"Created","Back-up plans shall be prepared and initiated whenever there is evidence of delays or technical problems."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.6.1f","Requirement","ECSS-Q-ST-70_0490083",1,"Created","The material requirements shall be explicitly accepted by the material supplier or manufacturer."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.6.2a","Requirement","ECSS-Q-ST-70_0490084",1,"Created","All materials shall be submitted to an incoming inspection."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.6.2b","Requirement","ECSS-Q-ST-70_0490085",1,"Created","An incoming inspection procedure shall define the inspections and tests to be carried out, particularly for materials that are known to be variable in their final properties."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.7.1a","Requirement","ECSS-Q-ST-70_0490086",1,"Created","The supplier shall verify that all critical materials are validated before being used in the manufacture of qualification or flight products."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.7.1b","Requirement","ECSS-Q-ST-70_0490087",1,"Created","Any modification, change of condition or configuration of application shall lead to a re-evaluation in conformance with the process shown in Figure 4-1."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.7.2a","Requirement","ECSS-Q-ST-70_0490088",1,"Created","The supplier shall apply the traceability rules defined in ECSS-Q-ST-20 to all materials."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.7.2b","Recommendation","ECSS-Q-ST-70_0490196",1,"Created","Materials should be identified by a unique reference number, code or a lot number to provide traceability should there be an incident or nonconformance, or a need for a technical investigation following failure or damage, to reconstruct the materials history, either individually (individual traceability) or by the manufacturing lot of which it was a part (lot traceability)."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.7.3a","Requirement","ECSS-Q-ST-70_0490090",1,"Created","The supplier shall define provisions for packaging, storage and removal from storage for materials."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.7.3b","Requirement","ECSS-Q-ST-70_0490091",1,"Created","Measurements and inspections used to guarantee the material integrity and monitoring during storage and removal from storage shall be identified."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.7.4a","Requirement","ECSS-Q-ST-70_0490092",1,"Created","The supplier shall ensure that all materials which have limited-life characteristics have their date of manufacture (when available, otherwise date of delivery) and shelf-life expiry date accurately identified and clearly marked on each lot or batch."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.7.4b","Permission","ECSS-Q-ST-70_0490197",1,"Created","Materials which have exceeded their shelf-life expiry date may be re-certified only after the physical and chemical characteristics are inspected and the parameters, subject to deterioration, are evaluated for continued acceptability according to the accept and reject criteria in conformance with ECSS-Q-ST-70-22."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.7.5a","Requirement","ECSS-Q-ST-70_0490094",1,"Created","Materials with limited-life after implementation (such as propellant) shall be identified and controlled in conformance with ECSS-Q-ST-10-04.\n    NOTE Storage and mission life are criteria for the assessment and control of those materials."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.7.6a","Requirement","ECSS-Q-ST-70_0490095",1,"Created","Nonconformances and alerts shall be managed in conformance with ECSS-Q-ST-10."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","5.7.7a","Requirement","ECSS-Q-ST-70_0490096",1,"Created","Material safety data sheet or equivalent shall be available for all materials."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.1a","Requirement","ECSS-Q-ST-70_0490097",1,"Created","The supplier shall verify that all materials and processes used in the manufacture of parts satisfy the mission technical requirements."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.2a","Requirement","ECSS-Q-ST-70_0490098",1,"Created","Parts shall be chosen from those successfully used for an identical application in other space programmes similar with respect to environment constraints and lifetime whenever those parts exist."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.2b","Requirement","ECSS-Q-ST-70_0490099",1,"Created","Type reduction actions shall be implemented at all levels of the programme."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.2c","Requirement","ECSS-Q-ST-70_0490100",1,"Created","Whether the parts are already qualified or remain to be qualified, their selection shall take into account the following criteria:\n    1. durability of supply;\n    2. reproducibility of characteristics."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.3a","Requirement","ECSS-Q-ST-70_0490101",1,"Created","The supplier shall establish and maintain a declared mechanical parts list in conformance with Annex B."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.4.2a","Requirement","ECSS-Q-ST-70_0490102",1,"Created","The supplier shall analyse all the parts contained in their preliminary lists with respect to criticality and in correlation with the risk analyses performed in conformance with ECSS-Q-ST-10-04."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.4.2b","Requirement","ECSS-Q-ST-70_0490103",1,"Created","Critical parts shall be identified in the DMPL and included in the critical items list."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.4.2c","Requirement","ECSS-Q-ST-70_0490104",1,"Created","Any critical part shall be the subject of a RFA."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.5.1a","Requirement","ECSS-Q-ST-70_0490105",1,"Created","Depending on the results of the criticality analysis, the supplier shall perform an evaluation phase before the validation phase for all critical parts with unknown characteristics or with major changes in the use or in the configuration."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.5.1b","Permission","ECSS-Q-ST-70_0490198",1,"Created","In case of an extension of an existing application, the evaluation indicated in 6.5.1a need not be performed if so agreed with the customer."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.5.1c","Requirement","ECSS-Q-ST-70_0490107",1,"Created","Guarantied characteristics of materials and material supplier inspection methods, together with associated documents, shall be available for review at the suppliers premises before the start of evaluation or qualification phases.\n    NOTE Refer to Table 4-1 for an explanation of the steps involved."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.5.2a","Requirement","ECSS-Q-ST-70_0490108",1,"Created","The evaluation shall consider the following, as a minimum, for each critical part:\n    1. the limits of use,\n    2. the part’s physical or functional characteristics, along with its values and tolerances,\n    3. behavioural tendencies and degradation processes depending on environment parameters (including sensitivity to pollution), and\n    4. acceptance criteria."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.5.2b","Requirement","ECSS-Q-ST-70_0490109",1,"Created","When an evaluation is performed an evaluation programme (available at PDR) shall be drawn up, implemented, and an evaluation report (available before CDR) shall be drawn up."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.5.2c","Requirement","ECSS-Q-ST-70_0490110",1,"Created","The behaviour of the parameters to be monitored which were also recorded during the evaluation programme tests, shall serve as a reference for the analysis of qualification test results.\n    NOTE Example of such behaviour is variation and change over time."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.5.3a","Requirement","ECSS-Q-ST-70_0490111",1,"Created","For each critical part a qualification programme shall be drawn up by the supplier (of the equipment using the critical part) and then implemented to check or confirm whether the parts satisfy mission requirements with appropriate margins."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.5.3b","Requirement","ECSS-Q-ST-70_0490112",1,"Created","Qualification status shall depend on the results obtained (qualification report) and the reviews of corresponding documentation (available at CDR)."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.5.4a","Requirement","ECSS-Q-ST-70_0490113",1,"Created","The mechanical parts shall not receive an approval identification in the declared mechanical parts list for the project unless the requirements in 6.5.2 and 6.5.3 are satisfied."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.5.4b","Requirement","ECSS-Q-ST-70_0490114",1,"Created","If approval is not granted, the supplier in charge of the item shall either:\n    1. select another mechanical part, or\n    2. propose a modified evaluation programme and resubmit for approval, or\n    3. if actions 6.5.4b.1 and 6.5.4b.2 fail to achieve positive results, initiate a deviation procedure."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.5.5a","Requirement","ECSS-Q-ST-70_0490115",1,"Created","For parts not conforming to project requirements, whether at the end of criticality analysis or of evaluation and qualification tests, the supplier shall submit a request for deviation in conformance with ECSS-Q-ST-10-09."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.6.1a","Requirement","ECSS-Q-ST-70_0490116",1,"Created","Mechanical parts with long lead times or procurement delays (versus the project schedule) shall be identified before the subsystem PDR."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.6.1b","Requirement","ECSS-Q-ST-70_0490117",1,"Created","Procurement shall be planned, documented and implemented in a timely manner to obtain reliable product assurance provision at CDR."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.6.1c","Requirement","ECSS-Q-ST-70_0490118",1,"Created","Back-up plans shall be prepared and initiated whenever there is evidence of possible delays or technical problems."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.6.2a","Requirement","ECSS-Q-ST-70_0490119",1,"Created","Each part shall be covered by a procurement specification or a standard."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.6.2b","Requirement","ECSS-Q-ST-70_0490120",1,"Created","The procurement specifications shall define the part characteristics, requirements, tests methods, acceptance criteria, lot acceptance testing, source inspection (if any) and material supplier inspection."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.6.2c","Requirement","ECSS-Q-ST-70_0490121",1,"Created","The procurement specifications shall be explicitly accepted by the part supplier or manufacturer."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.6.3a","Requirement","ECSS-Q-ST-70_0490122",1,"Created","For complex parts related to a specific project development, each supplier shall define the nature and frequency of their own source inspection points. "]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.6.3b","Requirement","ECSS-Q-ST-70_0490123",1,"Created","Source inspection shall be carried out by the customer on the premises of the supplier (part manufacturer) in conformance with ECSS-Q-ST-20."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.6.4a","Requirement","ECSS-Q-ST-70_0490124",1,"Created","Each part or batch of parts shall be submitted to an incoming inspection."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.6.4b","Requirement","ECSS-Q-ST-70_0490125",1,"Created","An incoming inspection procedure shall be established defining the inspections and tests to be carried out."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.7.1a","Requirement","ECSS-Q-ST-70_0490126",1,"Created","The supplier shall ensure that all critical parts are qualified before being used in the manufacture of qualification or flight products."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.7.1b","Requirement","ECSS-Q-ST-70_0490127",1,"Created","Any modification, change in condition or configuration of application shall lead to a re-evaluation in conformance with the process shown in Figure 4-1."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.7.2a","Requirement","ECSS-Q-ST-70_0490128",1,"Created","The supplier shall apply the traceability rules defined in ECSS-Q-ST-20 to his parts."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.7.2b","Recommendation","ECSS-Q-ST-70_0490199",1,"Created","Parts should be identified by a unique reference number or code and a lot number to provide traceability - where there is an incident or nonconformance, or for the purposes of technical investigations following failure or damage - to reconstruct the parts history, either individually (individual traceability) or by the manufacturing lot it was part of (lot traceability)."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.7.3a","Requirement","ECSS-Q-ST-70_0490130",1,"Created","The supplier shall define provisions for packaging, storage and removal from storage for parts."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.7.3b","Requirement","ECSS-Q-ST-70_0490131",1,"Created","Measurements and inspections used to guarantee the part integrity and monitoring during storage and removal from storage shall be identified."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.7.4a","Requirement","ECSS-Q-ST-70_0490132",1,"Created","Limited-life parts after implementation or subject to wear out shall be identified and controlled, taking into account storage and mission life.\n    NOTE Examples of such parts are mechanisms, pyro initiators and O-rings."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.7.4b","Requirement","ECSS-Q-ST-70_0490133",1,"Created","Limited-life parts shall be assessed as candidates to the critical items list in conformance with ECSS-Q-ST-10-04."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","6.7.5a","Requirement","ECSS-Q-ST-70_0490134",1,"Created","Management of nonconformances and alerts shall be in conformance with ECSS-Q-ST-10."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.1a","Requirement","ECSS-Q-ST-70_0490135",1,"Created","Each process to be used in the manufacturing or assembly of a product shall be identified by a specification or procedure."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.1b","Requirement","ECSS-Q-ST-70_0490136",1,"Created","Reference shall be made to accept and reject criteria."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.2a","Requirement","ECSS-Q-ST-70_0490137",1,"Created","The supplier shall verify that the materials and the mechanical parts used during the implementation of processes satisfy the requirements of this Standard."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.3a","Requirement","ECSS-Q-ST-70_0490138",1,"Created","Processes shall be chosen from those already verified according to the following order of preference and priority:\n    1. those covered by space agencies or other governmental organization certification for identical conditions of use;\n    2. those for which satisfactory evaluation and verification results are obtained on samples representative of the application with a sufficient margin as regards conditions of use;\n    3. those already successfully used by the same supplier for other space programmes in the same conditions of use."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.3b","Requirement","ECSS-Q-ST-70_0490139",1,"Created","Whether the processes are already verified or remain to be verified, their selection shall take into account the following criteria:\n    1. reliability;\n    2. inspectability;\n    3. re-workability of the process item;\n    4. reproducibility."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.4a","Requirement","ECSS-Q-ST-70_0490140",1,"Created","The supplier shall establish and maintain a declared processes list in conformance with Annex C."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.5.2a","Requirement","ECSS-Q-ST-70_0490141",1,"Created","The supplier shall analyse all the processes contained in their preliminary lists with respect to criticality and in correlation with the risk analyses performed."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.5.2b","Requirement","ECSS-Q-ST-70_0490142",1,"Created","Critical processes shall be identified in the DPL and included in the list of critical items."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.5.2c","Requirement","ECSS-Q-ST-70_0490143",1,"Created","Any critical process shall be the subject of an RFA."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.5.2d","Requirement","ECSS-Q-ST-70_0490144",1,"Created","Special processes shall be identified and controlled."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.5.2e","Requirement","ECSS-Q-ST-70_0490145",1,"Created","Process control shall be ensured by means of procedures or personnel certification or inline process control."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.5.2f","Permission","ECSS-Q-ST-70_0490200",1,"Created","Whenever feasible a statistical process may be carried out."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.6.1a","Requirement","ECSS-Q-ST-70_0490147",1,"Created","Depending on the results of the criticality analysis, the supplier shall perform an evaluation phase before the validation phase for all critical processes which are new or with major changes in the use or in the configuration. "]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.6.1b","Permission","ECSS-Q-ST-70_0490201",1,"Created","In case of an extension of an existing application, the evaluation indicated in 7.6.1a need not be performed if so agreed with the customer."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.6.1c","Requirement","ECSS-Q-ST-70_0490149",1,"Created","For confidential processes, the supplier shall prove that the process has been verified.\n    NOTE 1 For example, by presenting a verification certificate from space agencies or other governmental organization responsible to check the applicability of this verification.\n    NOTE 2 Refer to Table 4-1 for an explanation of the steps involved."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.6.2a","Requirement","ECSS-Q-ST-70_0490150",1,"Created","The evaluation shall consider the following as a minimum for each critical process:\n    1. the limits of use,\n    2. the values, determined by test samples or technology samples, of relevant parameters and their tolerances, and\n    3. acceptance criteria."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.6.2b","Requirement","ECSS-Q-ST-70_0490151",1,"Created","When an evaluation is performed, the supplier shall provide \n    1. an evaluation plan at PDR and\n    2. an evaluation report before CDR."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.6.3a","Requirement","ECSS-Q-ST-70_0490152",1,"Created","For each critical process, the supplier shall implement a verification programme."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.6.3b","Requirement","ECSS-Q-ST-70_0490153",1,"Created","The verification programme shall be defined in conformance with existing ECSS or national agency standards of verification."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.6.3c","Requirement","ECSS-Q-ST-70_0490154",1,"Created","The supplier shall ensure that the processes satisfy the mission requirements and that the parameters needed for the product design are defined so as to obtain verification status."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.6.3d","Requirement","ECSS-Q-ST-70_0490155",1,"Created","Verification status shall depend on the results obtained (verification report) and the review of corresponding documentation (available at CDR)."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.6.4a","Requirement","ECSS-Q-ST-70_0490156",1,"Created","The processes shall not receive an approval identification in the declared processes list unless requirements in 7.6.2 and 7.6.3 are satisfied. If approval is not granted, the supplier in charge of the item shall either\n    1. select other processes, or\n    2. propose a modified evaluation programme and resubmit for approval, or\n    3. if actions 7.6.4a.1 and 7.6.4a.2 fail to achieve positive results, initiate a deviation procedure."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.6.5a","Requirement","ECSS-Q-ST-70_0490157",1,"Created","For processes not conforming to project requirements, whether at the end of criticality analysis or of evaluation and verification tests, the supplier shall submit a request for deviation in conformance with ECSS-Q-ST-10-09."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.7.1a","Requirement","ECSS-Q-ST-70_0490158",1,"Created","The supplier shall confirm that all critical processes have been verified before being used in the manufacture of qualification or flight products."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.7.1b","Requirement","ECSS-Q-ST-70_0490159",1,"Created","Any modification, change of condition or configuration of application shall lead to a re-evaluation in conformance with the process shown in Figure 4-1."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.7.2a","Requirement","ECSS-Q-ST-70_0490160",1,"Created","When a process needs to be re-verified, a request for approval (RFA) shall be established and a re-verification programme shall be implemented.\n    NOTE Any prolonged stoppage in manufacturing, any major change of the facilities or procedures or any transfer of production to another entity can invalidate partially or completely the initial verification of a process."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.7.3a","Requirement","ECSS-Q-ST-70_0490161",1,"Created","Before implementation of a process, the supplier shall ensure that personnel are trained and that environment, means and documentation are adequate."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.7.3b","Requirement","ECSS-Q-ST-70_0490162",1,"Created","This verification shall ensure that: \n    1. manufacturing and quality control tools associated with the process are adequate, calibrated and properly maintained are used under appropriate environmental and cleanliness conditions, see clause 4.4,\n    2. personnel are properly trained and certified, and\n    3. the processes specifications, manufacturing and inspection procedures and workmanship standards including clear definition of manufacturing operations and clear acceptance criteria exist.\n        NOTE 1 Photographically documented if possible for visual acceptance criteria at the appropriate work and inspection stations.\n        NOTE 2 For planning of manufacturing, assembly and integration operation and inspection see ECSS-Q-ST-20."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.7.4a","Requirement","ECSS-Q-ST-70_0490163",1,"Created","Traceability of processes shall be ensured in conformance with ECSS-Q-ST-20."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.7.5a","Requirement","ECSS-Q-ST-70_0490164",1,"Created","Nonconformances and alerts shall be processed in conformance with ECSS-Q-ST-10."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.7.6a","Requirement","ECSS-Q-ST-70_0490165",1,"Created","MIPs shall be defined in conformance with ECSS-Q-ST-20."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","7.7.7a","Requirement","ECSS-Q-ST-70_0490166",1,"Created","The supplier shall define provisions for packaging, storage, and removal from storage for products or semi-finished products before and after implementation of processes."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","A.2.1<1>a","Requirement","ECSS-Q-ST-70_0490167",1,"Created","The DML shall contain the following statements:\n    1. “Materials are classified into 20 groups depending on their type or their main use, see Table A-1”.                                         \n    2. “Primers are classified in the group of their associated component.”\n    3. “Where no project requirement exists for a separate DMPL, mechanical parts are entered on the DML as a separate group with the corresponding numbers.”"]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","A.2.1<1>b","Requirement","ECSS-Q-ST-70_0490168",1,"Created","If new groups are created, for a given project, these shall have numbers over 21."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","A.2.1<2>a","Requirement","ECSS-Q-ST-70_0490169",1,"Created","The DML shall include the information stated in Figure A-1, where the header information identifies the list as the declared materials list and includes the issue number and date of issue, as follows:\n    1. Item number (applicable to equipment manufacturer level only)\n        (a) This consists of the material group identifier and the user code. It takes the form of:\n<group number>.<identifier within the group>.<running number>.<user code>\n            NOTE For example: 11.5.1.KOF.\n        (b) Characteristics of the item number are:\n              - The user, identified by an agreed user code for the project.\n              - One only per material type.\n              - Does not change during the life of the materials list (sub-items are permitted when deemed necessary).\n    2. Commercial identification or standardized designation\n        (a) Enter the correct and standard designation, such as the trade name plus number.\n        (b) If no trade name exists, enter the manufacturer’s name plus number.\n        (c) For metal alloys, the Aluminium Association (AA) system is recommended for aluminium alloys, and the American Iron and Steel Institute (AISI) system for steel. For other metals or alloys, the main constituent is entered first except in the case of a traditional name.\n            NOTE For example: brass or bronze.\n        (d) For each material, as designated in A.2.1<2>a2(a) to(c), use a unique item number. If several lines are used for different applications or processing, add sub-item numbers.\n    3. Chemical nature and product type\n        (a) For metallic materials, add the condition as procured if applicable.\n            NOTE Example of such conditions are rolled and heat treatment.\n        (b) Where a semi-finished product is procured, give the relevant state. \n            NOTE Example of such state are form, plate and sheet.\n        (c) Give the thickness of the material, that can be an important parameter.\n            NOTE Examples of chemical nature are: epoxy resin, polyurethane adhesive, Ti6Al4V.\n    4. Procurement information\n        (a) Manufacturer or distributor: name of the manufacturer and name of the distributor if different.\n        (b) Procurement specification: reference of the procurement specification with issue, revision and date. It may be replaced by a national or international specification or standard, if this exists, and identifies the source of procurement, if relevant. Indication of issue or date is not applicable when datasheets are used\n    5. Processing parameters\nList here a summary of the process parameters applied by the user of the process.\n        NOTE E.g. mixture proportions, cure temperature, special cleaning agent, surface treatment, thermal treatment and temperature, and reference to specification number.\n    6. Use and location\n        (a) Use codes able to define the location of the material with respect to the:\n            • subsystem;\n            • particular piece of equipment (box or item);\n            • use of the equipment, e.g. a structural element, thermal control, electrical insulation.\n            NOTE If the CI number is not included in the list header, then a suitable abbreviation of the relevant subsystem is included.\n        (b) Include any restrictions that apply to the use of a particular material in the corresponding comment column.\n    7. Environmental code\nThe environmental code is defined using Table A-2.\n    8. Size code\nThe size code is indicated by an alphanumeric combination, such as A5, V2 or M3, as in Table A-3.\n    9. Validation references, justification for approval and prime comments and prime approval\n        (a) Make reference to relevant test data that demonstrates the acceptability of the material under the environmental conditions and the application relevant to the particular project concerned. Specifically, in column 9.1, corrosion (CORR), stress corrosion (SCC), flammability (FLAM), offgassing (OFFG) and outgassing (OUTG) data or report-references are entered.\n        (b) Use standard abbreviations to summarize the acceptance status of a material for a particular property.\n        (c) Use the justification for approval (column 9.2) and prime approval (column 9.3) columns for any additional information to obtain customer approval.\n        (d) Standard abbreviations are used to summarize the acceptability or otherwise of a material for a specific property. These are defined for the project.\n        (e) Select the supplier approval status code from Table A-4.\n    10. Customer approval status code and comments\n        (a) Select this code from Table A-4.\n        (b) Include additional comments where appropriate."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","A.2.2a","Requirement","ECSS-Q-ST-70_0490170",1,"Created","The change record shall list the successive issues and their release dates since the first formal issue of the document."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","A.2.2b","Requirement","ECSS-Q-ST-70_0490171",1,"Created","The change record shall include a brief description of the updates which contributed to each issue or revision.\n    NOTE This DRD recommends the format and define the content within the framework of a project or a programme."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","B.2.1<1>a","Requirement","ECSS-Q-ST-70_0490172",1,"Created","The DMPL shall contain the following statements:\n“Mechanical parts are classified into 11 groups depending on their type or their main use” (see Table B-1)."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","B.2.1<1>b","Requirement","ECSS-Q-ST-70_0490173",1,"Created","If, for a given project it is considered necessary to create new groups, these shall have numbers over 61."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","B.2.1<1>c","Recommendation","ECSS-Q-ST-70_0490202",1,"Created","Items that appear in the EEE parts list should not be repeated here.\n    NOTE For example, heaters, some valves, thermostats, relays, transformer coils and solenoids."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","B.2.1<2>a","Requirement","ECSS-Q-ST-70_0490175",1,"Created","The DMPL shall include the information in Figure B-1, where the header information identifies the list as the declared mechanical parts list and includes the issue number and date of issue, as follows:\n    1. Item number (applicable at equipment supplier level only)\n        (a) This consists of the mechanical part identifier and the user code. It takes the form of:\n<group number>.<identifier within the group>.<running number>.<user code>\n            NOTE For example: 7.2.1.ACSA.\n        (b) Characteristics of the item number are:\n             - Identify the subcontractor by an agreed user code for the project.\n             - One only per mechanical part type.\n             - Does not change during the life of the mechanical parts list.\n    2. Commercial identification\n        (a) Enter the correct and standard designation, such as trade name plus number. \n        (b) If no trade name exists then enter the manufacturers’ name and number.\n    3. Type of part\nDescribe the material and surface treatment (if applicable).\n    4. Procurement information\n        (a) Manufacturer or distributor: name of the manufacturer and name of the distributor if different.\n        (b) Procurement specification: reference of the procurement specification with issue, revision and date. It may be replaced by a national or international specification or standard if this exists and identifies the source of procurement if relevant.\n    5. Elementary function, main characteristics\n        (a) Enter the function of the mechanical part.\n        (b) Enter the main characteristics of the mechanical part.\n            NOTE For example, number of revolutions per minute for a ball bearing.\n    6. Use and location\nUse codes able to define the location of the mechanical part with respect to the:\n        (a) subsystem;\n        (b) particular piece of equipment (box or item);\n        (c) use of the equipment.\n    7. Environmental code\nThe environmental code is defined using Table B-2.\n    8. Criticality\nEnter “C” for critical or “N” for non-critical. If a mechanical part is considered critical, describe the reason for the criticality and methods of control.\n    9. Supplier reference, prime comments and prime approval status \n        (a) Use the supplier reference, prime comments and approval columns to enter any additional information that can be necessary in order to obtain customer approval.\n        (b) This information comprises reference and issue of the RFA or approval, mechanical parts justification file, evaluation reports and deviation requests.\n        (c) Make reference to the relevant test data that demonstrates acceptability of the mechanical part under the environment conditions and the application relevant to the particular project concerned. \n        (d) Use standard abbreviations, defined by the customer, to summarize the acceptance status of a mechanical part for a particular property.\n        (e) In order to justify the use of a material for flammability resistance, list here the material thickness and height of oxygen share.\n        (f) Select the prime approval status code from Table B-3.\n    10. The customer approval status code and comments\n        (a) Select this code from Table B-3.   \n        (b) Include additional comments where appropriate."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","B.2.2a","Requirement","ECSS-Q-ST-70_0490176",1,"Created","The change record shall list the successive issues and their release dates since the first formal issue of the document."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","B.2.2b","Requirement","ECSS-Q-ST-70_0490177",1,"Created","This record shall include a brief description of the updates which contributed to each issue or revision.\n    NOTE This DRD recommends the format and defines the content within the framework of a project or a programme."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","C.2.1<1>a","Requirement","ECSS-Q-ST-70_0490178",1,"Created","The DPL shall contain the following statements:\nProcesses are classified into 17 groups depending on their type or their main use, see Table C-1."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","C.2.1<1>b","Requirement","ECSS-Q-ST-70_0490179",1,"Created","If, for a given project it is considered necessary to create new groups, these shall have numbers over 17."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","C.2.1<2>a","Requirement","ECSS-Q-ST-70_0490180",1,"Created","The DPL shall include the information in Figure C-1, where the header information identifies the list as the declared processes list and includes the issue number and date of issue, as follows\n    1. Item number (applicable to equipment supplier level only)\n        (a) This consists of the process identifier and the user code. It takes the form of \n<group number>.<identifier within the group>.<running number>.<user code>\n            NOTE For example: 1.2.1.SSEX\n        (b) Characteristics of the item number are:\n             - Identify the subcontractor by an agreed user code for the project.\n             - One only per process type.\n             - Does not change during the life of the process list.\n    2. Process identification\nIndicate the correct and standard identification of the process, e.g. the process name or title: bonding, coating or soldering.\n    3. Specification\n        (a) Identify the name or abbreviation of the process executor.\n        (b) Make a reference to the associated procedure, together with the issue, revision and date.\n            NOTE For example, national, international, EN, ISO, ECSS or company in-house.\n    4. Process description\nEnter here a short description of the process.\n    5. Use and location\nUse codes able to define the location of the process with respect to the:\n        (a) subsystem,\n        (b) particular piece of equipment (box or item),\n        (c) use of the equipment.\n            NOTE For example, a structural element, thermal control, electrical insulation).\n    6. This column number is not used.\n    7. Associated item numbers\nEnter the associated material list (DML) or mechanical parts list (DMPL) with the process.\n    8. Criticality\n        (a) Enter “C” for critical or “N” for non-critical.\n        (b) If a process is considered to be critical, Enter the references to the relevant RFA.\n    9. Supplier reference, prime comments and approval\n        (a) Use the supplier reference and approval columns to enter any additional information that can be necessary to obtain customer approval.\n        (b) Select the supplier approval status code from Table C-2.\n    10. The customer approval status code and comments\n        (a) Select this code from Table C-2.\n        (b) Include additional comments where appropriate."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","C.2.2a","Requirement","ECSS-Q-ST-70_0490181",1,"Created","The change record shall list the successive issues and their release dates since the first formal issue of the document."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","C.2.2b","Requirement","ECSS-Q-ST-70_0490182",1,"Created","This record shall include a brief description of the updates which contributed to each issue or revision.\n    NOTE This DRD recommends the format and define the content within the framework of a project or a programme."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","D.2.1a","Recommendation","ECSS-Q-ST-70_0490203",1,"Created","The RFA should contain the information in Figure D-1 (pages 1 and 2), as follows:\n    1. The header information, identifying the document as a request for approval together with the project logo and project name, RFA reference, issue revision and date.\n    2. Originator\nOriginator’s name and reference.\n    3. Location\nSubsystem and equipment codes.\n    4. Item description\nBrief description of the item.\n    5. PMP information\nThe DML, DMPL or DPL item number and list reference.\n    6. Item status, including the following information:\n        (a) manufacturers’ name and qualification reference;\n        (b) suppliers’ name and qualification status;\n        (c) product or material specification;\n        (d) procurement specification;\n        (e) process or handling specification;\n        (f) other related process or handling specifications;\n        (g) verification or qualification specification;\n        (h) report on verification or qualification.\n    7. Reason for RFA\nEnter the reason for the RFA.\n    8. Application and location details\nEnter here the details of the application and exact location of the item.\nGive the reference in the CIL.\n    9. Evaluation and validation programme\nReference and details of main tests.\n    10. Subcontractor supplier approval for the first issue of the RFA.\n    11. Customer initial decision, to be entered on first issue of the RFA providing:\n        (a) the decision concerning the proposed material,\n        (b) the requirement to perform tests (deviation request as necessary), and\n        (c) the decision concerning the proposed test programme.\n    12. Customer’s and final customer’s (if applicable) signature\n    13. Justification results obtained with reference to the supplier’s validation report and conclusion.\n    14. Subcontractor supplier approval on RFA final issue.\n    15. Final approval status of the RFA by the customer."]
["ECSS-Q-ST-70C","ECSS - Superseded v1.0","D.2.2a","Requirement","ECSS-Q-ST-70_0490184",1,"Created","The RFA shall be completed by the supplier (parts 1 to 10, 13 and 14) and the customer (parts 11 12 and 15)."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.1.1.1a","Requirement","ECSS-Q-ST-10_0360001",1,"Created","The supplier shall identify the personnel responsible for implementing and performing PA management and other PA disciplines."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.1.1.1b","Requirement","ECSS-Q-ST-10_0360002",1,"Created","The supplier shall assign a project PA manager reporting to the project manager and having unimpeded access to higher management."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.1.1.1c","Requirement","ECSS-Q-ST-10_0360003",1,"Created","The appointed project PA manager, irrespective of other responsibilities, shall have organizational authority to establish and implement a product assurance programme in accordance with the project product assurance requirements."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.1.1.1d","Requirement","ECSS-Q-ST-10_0360004",1,"Created","The project PA Manager shall act as the focal point of contact within the project concerning Product Assurance matters.\n    NOTE The project PA manager is referred to as “PA manager” in the rest of this document."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.1.1.2a","Requirement","ECSS-Q-ST-10_0360005",1,"Created","The supplier shall define and document the responsibility, the authority and the interrelation of personnel who manage, perform and verify work affecting product assurance."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.1.1.2b","Requirement","ECSS-Q-ST-10_0360006",1,"Created","The supplier shall define and document the responsibilities and the interfaces of the PA functions, either external or internal, involved in a project."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.1.1.2c","Requirement","ECSS-Q-ST-10_0360007",1,"Created","When the supplier's PA organization delegates product assurance tasks to another organization it shall be done in a documented and controlled way monitored by the PA organization.\n    NOTE The supplier PA organization retains the responsibility towards the Customer"]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.1.1.3a","Requirement","ECSS-Q-ST-10_0360008",1,"Created","The supplier shall identify the PA resources needed to implement the PA programme."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.1.1.3b","Requirement","ECSS-Q-ST-10_0360009",1,"Created","The supplier shall provide resources capable to perform the PA tasks identified in the PA programme."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.1.1.3c","Requirement","ECSS-Q-ST-10_0360010",1,"Created","Reviews and audits of the product assurance programme, of processes or of product shall be carried out by personnel not directly involved in the work being performed."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.1.2a","Requirement","ECSS-Q-ST-10_0360011",1,"Created","The PA manager shall interface with project management, ensuring that the contractual provision and schedule planning for the definition and phasing of PA activities are met."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.1.2b","Requirement","ECSS-Q-ST-10_0360012",1,"Created","The PA manager shall interface with risk management, configuration management, engineering, procurement and AIV for the definition and execution of tasks in which PA activities are involved."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.1.2c","Requirement","ECSS-Q-ST-10_0360013",1,"Created","The PA manager shall interface with the customer regarding all Product Assurance matters."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.1.2d","Requirement","ECSS-Q-ST-10_0360014",1,"Created","The PA manager shall interface with lower-tier suppliers regarding all Product Assurance matters."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.1.3a","Requirement","ECSS-Q-ST-10_0360015",1,"Created","The supplier shall prepare, maintain and implement a plan of the PA activities in accordance with the customer PA requirements."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.1.3b","Requirement","ECSS-Q-ST-10_0360016",1,"Created","The Product Assurance plan shall be prepared in conformance with DRD in Annex A."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.1.3c","Requirement","ECSS-Q-ST-10_0360017",1,"Created","The Product Assurance plan shall be submitted to the customer for approval.\n    NOTE 1 The Product Assurance plan can refer to Clauses of the Company Quality Manual and to in-house procedures.\n    NOTE 2 Information on the schedule for delivery of PA management documents is given in Annex C"]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.1a","Requirement","ECSS-Q-ST-10_0360018",1,"Created","The PA manager shall ensure that PA disciplines are organized at the beginning of the project according to customer contractual requirements."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.1b","Requirement","ECSS-Q-ST-10_0360019",1,"Created","The PA manager shall ensure that the inputs used by the PA disciplines are consistent and complete, and available in line with the project schedule."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.1c","Requirement","ECSS-Q-ST-10_0360020",1,"Created","The PA manager shall ensure that the PA disciplines perform the tasks described in the PA Plan in line with the project schedule."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.1d","Requirement","ECSS-Q-ST-10_0360021",1,"Created","The PA manager shall ensure that the outputs produced by the PA disciplines are consistent and complete, and delivered in line with the project schedule."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.1e","Requirement","ECSS-Q-ST-10_0360022",1,"Created","The PA manager shall ensure the application of processes defined in applicable project plans and documents. "]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.1f","Requirement","ECSS-Q-ST-10_0360023",1,"Created","The PA manager shall control the quality of his supplier’s products by:\n    1. issuing product assurance requirements applicable to the supplier \n    2. ensuring the implementation of the PA requirements by the supplier."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.1g","Requirement","ECSS-Q-ST-10_0360024",1,"Created","The PA manager shall ensure that PA contributions to verification are defined and provided."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.1h","Requirement","ECSS-Q-ST-10_0360025",1,"Created","The PA manager shall ensure that a qualification programme is defined, approved and maintained by the relevant organization.\n    NOTE Requirement for the qualification programme are addressed in ECSS-Q-ST-20, ECSS-Q-ST-60, ECSS-Q-ST-70, ECSS-E-ST-10-02 and ECSS-E-ST-10-03."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.1i","Requirement","ECSS-Q-ST-10_0360026",1,"Created","The PA manager shall ensure that the qualification programme is implemented and the qualification results are recorded, evaluated and documented."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.1j","Requirement","ECSS-Q-ST-10_0360027",1,"Created","The PA manager shall ensure that a Qualification Status List of the programme items is maintained in conformance with Annex B."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.1k","Requirement","ECSS-Q-ST-10_0360028",1,"Created","The PA manager shall review and approve the achieved qualification status."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.1l","Requirement","ECSS-Q-ST-10_0360029",1,"Created","The PA manager shall approve the product acceptance during the Acceptance or Delivery Review.\n    NOTE The PA manager approval is based on the outputs of the Acceptance or Delivery Review."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.2a","Requirement","ECSS-Q-ST-10_0360030",1,"Created","The supplier shall report on the status and progress of the product assurance program implementation."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.2b","Requirement","ECSS-Q-ST-10_0360031",1,"Created","The PA report shall include at least the following items for the reporting period:\n    • Progress and accomplishment of each major product assurance task including resolved and new problems, future planning of major activities and events\n    • Status of PA reviews, Audits and MIPs, Waiver requests, Non conformances (minor and major), Critical items (including mitigation action plan status), Qualification status, EEE component status, Material and processes status, Alerts status."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.2c","Permission","ECSS-Q-ST-10_0360066",1,"Created","The PA progress report may be part of the project progress report. \n    NOTE The general contents of the project progress report are detailed in ECSS-M-ST-10 Annex E."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.3a","Requirement","ECSS-Q-ST-10_0360033",1,"Created","The supplier shall perform audits on his own performance to verify the implementation and effectiveness of the provisions defined in the PA plan.\n    NOTE 1 Audits can be performed by sampling on various projects or by periodic audits of the supplier quality system.\n    NOTE 2 The general contents of project audits are detailed in ECSS-M-ST-10 clause 5.2.3."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.3b","Requirement","ECSS-Q-ST-10_0360034",1,"Created","The supplier shall establish and maintain an audit plan for procurement activities on the project, designating the lower tier suppliers to be audited, the current status and the schedule for auditing."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.3c","Requirement","ECSS-Q-ST-10_0360035",1,"Created","In addition to the planned audits, extra audits shall be performed when necessary to overcome failure, consistent poor quality, or other problems. "]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.3d","Requirement","ECSS-Q-ST-10_0360036",1,"Created","The supplier shall plan and perform audits using established and maintained procedures."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.4a","Requirement","ECSS-Q-ST-10_0360037",1,"Created","The supplier shall establish a critical items control programme in conformance with ECSS-Q-ST-10-04."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.4b","Requirement","ECSS-Q-ST-10_0360038",1,"Created","The PA manager shall identify and evaluate critical items in support of the overall project risk management activities."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.4c","Requirement","ECSS-Q-ST-10_0360039",1,"Created","The PA manager shall ensure that a critical item control programme is implemented to eliminate or mitigate associated risks."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.5a","Requirement","ECSS-Q-ST-10_0360040",1,"Created","The PA manager shall ensure that the applicable issues of all documents and data are available at all locations where activities required for the implementation of the PA programme are performed."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.5b","Requirement","ECSS-Q-ST-10_0360041",1,"Created","The PA manager shall ensure that invalid or obsolete documents and data are removed from all points of issue or use, or assured against unintended use."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.5c","Requirement","ECSS-Q-ST-10_0360042",1,"Created","The PA manager shall ensure that obsolete documents and data retained for legal or knowledge preservation purposes are identified as such."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.5d","Requirement","ECSS-Q-ST-10_0360043",1,"Created","The PA manager shall identify the project documents requiring approval including those requiring approval by PA."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.6a","Requirement","ECSS-Q-ST-10_0360044",1,"Created","The supplier shall establish and maintain quality records to provide objective evidence of complete and successful performance of all PA discipline tasks and to demonstrate compliance with requirements.\n    NOTE Requirements for the storage, retrieval and archiving of quality records are addressed in ECSS-M-ST-40."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.7a","Requirement","ECSS-Q-ST-10_0360045",1,"Created","The PA manager shall verify during Configuration Control Boards the suitability for release of drawings, plans, specifications, procedures and changes thereto.\n    NOTE The operation of Configuration Control Boards is detailed in ECSS-M-ST-40"]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.7b","Requirement","ECSS-Q-ST-10_0360046",1,"Created","The PA manager shall ensure that:\n    1. the as designed status is defined and released prior to manufacturing;\n    2. the as-built documentation is properly defined, identified and maintained in order to reflect approved modifications; and\n    3. items delivered comply with the as-built documentation."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.8a","Requirement","ECSS-Q-ST-10_0360047",1,"Created","The supplier shall establish and maintain a nonconformance control system in conformance with ECSS-Q-ST-10-09."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.9a","Requirement","ECSS-Q-ST-10_0360048",1,"Created","The supplier shall notify its customer of preliminary information on failures or problems that can result in an alert.\n    NOTE 1 The above is applicable to failure or problems detected by the supplier or by one of his lower tier suppliers.\n    NOTE 2 The above is only applicable to failures or problems meeting all of the following criteria:\n        · The item with the observed failure or problem has multiple applications, which can have implications for more than one project, thus requiring prompt action.\n        · The failure or problem has occurred in the application of an item within the specified design and usage limitations. \n        · Failures or problems due to usage within reasonably expected limits of performance, but where these limits were not specified precisely.\n        · A preliminary investigation has provided evidence of the root cause of the failure or problem.\n        · Failure or problems are confirmed not to be of a random nature."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.9b","Requirement","ECSS-Q-ST-10_0360049",1,"Created","The supplier shall investigate in cooperation with the originator of the failure or problem to define the immediate measures to be taken, to identify the causes, and to recommend corrective actions for similar items."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.9c","Requirement","ECSS-Q-ST-10_0360050",1,"Created","The PA manager shall ensure:\n    1. the assessment of any failure having the potential to lead to an alert by the customer,\n    2. the investigation, until disposition of the items subject of the potential alert, and\n    3. the assessment of incoming alerts for the definition, implementation and follow-up of necessary actions."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","5.2.9d","Requirement","ECSS-Q-ST-10_0360051",1,"Created","The supplier shall participate in the alert system organized by the customer or other sources, by:\n    1. assessment of the impact of incoming alerts to project work, and definition, implementation and follow-up of necessary corrective actions at any contractual level.\n    2. distribution of incoming alerts to the possible affected users within the project.\n        NOTE The alert system is set up for the prompt interchange of information on failures or problems which can affect more than one user, or can recur in other projects or circumstances, if no preventive actions are taken."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","A.2.1<1>a","Requirement","ECSS-Q-ST-10_0360052",1,"Created","The PAP shall introduce the purpose, objective and the reason prompting its preparation.\n    NOTE For example: programme or project reference and phase."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","A.2.1<2>a","Requirement","ECSS-Q-ST-10_0360053",1,"Created","The PAP shall list the applicable and reference documents in support of the generation of the document."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","A.2.1<3.1>a","Requirement","ECSS-Q-ST-10_0360054",1,"Created","The PAP shall describe the organization (including responsibilities and authorities), the activities, processes and procedures to be applied by the supplier to fulfil the applicable product assurance planning requirements defined in clause 5.1 of ECSS-Q-ST-10C."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","A.2.1<3.2>a","Requirement","ECSS-Q-ST-10_0360055",1,"Created","The PAP shall describe the activities, processes and procedures to be applied by the supplier to fulfil the applicable product assurance implementation requirements defined in clause 5.2 of ECSS-Q-ST-10C."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","A.2.1<4>a","Requirement","ECSS-Q-ST-10_0360056",1,"Created","The PAP shall describe the activities, processes and procedures to be applied by the supplier to fulfil the applicable quality assurance requirements."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","A.2.1<5>a","Requirement","ECSS-Q-ST-10_0360057",1,"Created","The PAP shall describe the activities, processes and procedures to be applied by the supplier to fulfil the applicable dependability requirements."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","A.2.1<6>a","Requirement","ECSS-Q-ST-10_0360058",1,"Created","The PAP shall describe the activities, processes and procedures to be applied by the supplier to fulfil the applicable safety requirements."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","A.2.1<7>a","Requirement","ECSS-Q-ST-10_0360059",1,"Created","The PAP shall describe the activities, processes and procedures to be applied by the supplier to fulfil the applicable EEE Component requirements."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","A.2.1<8>a","Requirement","ECSS-Q-ST-10_0360060",1,"Created","The PAP shall describe the activities, processes and procedures to be applied by the supplier to fulfil the applicable Material and Processes requirements."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","A.2.1<9>a","Requirement","ECSS-Q-ST-10_0360061",1,"Created","The PAP shall describe the activities, processes and procedures to be applied by the supplier to fulfil the applicable Software product assurance requirements."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","A.2.1<10>a","Requirement","ECSS-Q-ST-10_0360062",1,"Created","The PAP shall describe the activities, processes and procedures to be applied by the supplier to fulfil all other applicable PA requirements not covered in the clause A.2.1<3> to clause A.2.1<9> (e.g. Security, Planetary Protection, Off-The-Shelf, Customer Furnished equipment).\n    NOTE The order of the sections is not mandatory."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","A.2.2a","Permission","ECSS-Q-ST-10_0360067",1,"Created","The response to this DRD may be combined with the response to the project management plan, as defined in ECSS-M-ST-10."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","A.2.2b","Permission","ECSS-Q-ST-10_0360068",1,"Created","The response to this DRD may be performed by reference to separate discipline plans addressing some of the above clauses of this DRD."]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","B.2.1a","Requirement","ECSS-Q-ST-10_0360065",1,"Created","The QSL shall include or refer to the following information:\n    1. Equipment designation:\n        (a) Identification of hardware by name, \n        (b) Configuration Item number and model.\n    2. Next higher assembly level :\n        (a) Identification of next higher assembly.\n    3. Manufacturer's name :\n        (a) Identification of Item Supplier.\n    4. Reference of requirements documents\n        (a) Reference numbers of applicable requirement specifications.\n    5. Design heritage:\n        (a) Specify if the design is “New”, otherwise identification of the project in which the design was used.\n        (b) Summary of current qualification status:\n            • Basis for qualification (qualification test results, heritage, and qualification on other projects) programme on which the qualification test was conducted;\n            • Project on which the test was conducted.\n    6. Proposed category A, B, C, or D (related to Design heritage):\n        NOTE Qualification approach as defined in the ECSS-E-ST-10-02.\n    7. Reference of Qualification plan document:\n        (a) Current qualification status/screening and applicability of qualification test versus requirements.\n        (b) Reference numbers of Qualification Plan(s).\n        (c) Identification of developments models (EM, EQM, QM, PFM) to be manufactured and tested for the project.\n    8. Reports:\n        (a) Reference to Verification Control Document and/or reference to Analyses, Test and Inspection Reports;\n        (b) Qualification Authority: Organization in charge of the item qualification (if any).\n    9. The qualification status:\n        • QUALIFIED,\n        • TO BE QUALIFIED,\n        • QUALIFICATION IN PROGRESS\n    10. Open Actions / Due dates/Remarks:\n        (a) For an open action: summary of missing qualification actions and planned dates for the closure of such actions.\n        (b) List of major NCRs and associated waivers to the qualification items"]
["ECSS-Q-ST-10C","ECSS - Superseded v1.0","B.2.2a","Permission","ECSS-Q-ST-10_0360069",1,"Created","The form may be a table which contains the here above information of B.2.1 or reference to separate document.\n    NOTE An example of such a table is shown in Figure B-1."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","4.1a","Requirement","ECSS-Q-ST-30_0410001",1,"Created","The dependability assurance shall be implemented by means of a systematic process for specifying requirements for dependability and demonstrating that these requirements are achieved. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","4.1b","Requirement","ECSS-Q-ST-30_0410002",1,"Created","The dependability assurance process shall be in conformance with the dependability assurance programme plan for the project."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","4.2a","Requirement","ECSS-Q-ST-30_0410003",1,"Created","The supplier shall coordinate, implement and integrate the dependability programme management with the PA programme management."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","4.3a","Requirement","ECSS-Q-ST-30_0410004",1,"Created","The supplier shall develop, maintain and implement a dependability plan for all project phases in conformance with the DRD in Annex C."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","4.3b","Requirement","ECSS-Q-ST-30_0410005",1,"Created","The plan shall address the applicable requirements of this document.\n    ","NOTE The plan can be included in the PA programme plan."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","4.3c","Requirement","ECSS-Q-ST-30_0410006",1,"Created","The extent that dependability assurance is applied shall take account of the severity (as defined in Table 5-1) of the consequences of failures."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","4.3d","Requirement","ECSS-Q-ST-30_0410007",1,"Created","The establishment and implementation of the dependability programme plan shall be considered in conjunction with the safety aspects of the programme. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","4.3e","Requirement","ECSS-Q-ST-30_0410008",1,"Created","The Supplier shall ensure that any potential conflict between dependability and safety requirements are managed. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","4.3f","Requirement","ECSS-Q-ST-30_0410009",1,"Created","Responsibilities for carrying out all dependability tasks within each phase of the lifecycle shall be defined."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","4.4a","Requirement","ECSS-Q-ST-30_0410010",1,"Created","As part of the risk management process implemented on the project, the Dependability engineer shall be responsible for identifying and reporting dependability associated risks .\n    ","NOTE ECSS-M-ST-80 describes the risk management process."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","4.4b","Requirement","ECSS-Q-ST-30_0410011",1,"Created","Dependability risk analysis reduction and control shall include the following steps:\n    1. identification and classification of undesirable events according to the severity of their consequences;\n    2. analysis of failure scenarios, determination of related failure modes, failure origins or causes;\n    3. classification of the criticality of the functions and associated products according to the severity of relevant failure consequences;\n    4. definition of actions and recommendations for detailed risk assessment, risk elimination, or risk reduction and control to an acceptable level;\n    5. status of risk reduction and risk acceptance;\n    6. implementation of risk reduction;\n    7. verification of risk reduction and assessment of residual risks.\n        ","NOTE The process of risk identification and assessment implies both qualitative and quantitative approaches."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","4.4c","Requirement","ECSS-Q-ST-30_0410012",1,"Created","Risk reduction measures that are proposed for dependability shall be assessed at system level in order to select the optimum solution to reduce the system level risk."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","4.5a","Requirement","ECSS-Q-ST-30_0410013",1,"Created","Dependability critical items shall be identified by dependability analyses performed to support the risk reduction and control process performed on the project. \n    ","NOTE The criteria for identifying dependability critical items are given in clause 6.5."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","4.5b","Requirement","ECSS-Q-ST-30_0410014",1,"Created","Dependability critical items, as part of the Critical Items List, shall be subject to risk assessment and critical items control in conformance with ECSS-Q-ST-10-04."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","4.5c","Requirement","ECSS-Q-ST-30_0410015",1,"Created","The control measures shall include:\n    1. a review of all design, manufacturing and test documentation related to critical functions, critical items and procedures;\n    2. dependability representation on relevant Review Boards to ensure that the disposition takes account of their criticality level."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","4.5d","Requirement","ECSS-Q-ST-30_0410016",1,"Created","The dependability aspects shall be considered during the entire verification process for dependability critical items until closeout."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","4.6a","Requirement","ECSS-Q-ST-30_0410017",1,"Created","The supplier shall ensure that all dependability data for a design review are presented to the customer in accordance with the project review schedule. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","4.6b","Requirement","ECSS-Q-ST-30_0410018",1,"Created","All dependability data submitted shall indicate the design baseline and shall be coherent with all other supporting technical documentation."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","4.6c","Requirement","ECSS-Q-ST-30_0410019",1,"Created","All design changes shall be assessed for their impact on dependability and a reassessment of the dependability shall be performed"]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","4.7a","Requirement","ECSS-Q-ST-30_0410020",1,"Created","Dependability lessons learnt shall be collected during the project life cycle including operational and disposal phases.\n    ","NOTE Dependability lessons learnt consider:\n        · the impact of newly imposed requirements;\n        · assessment of all malfunctions, anomalies, deviations and waivers;\n        · effectiveness of strategies of the project;\n        · new dependability tools and methods that have been developed or demonstrated;\n        · effective versus ineffective verifications that have been performed."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","4.8a","Requirement","ECSS-Q-ST-30_0410021",1,"Created","The supplier shall report dependability progress to the customer as part of product assurance activities in conformance with ECSS-Q-ST-10."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","4.9a","Requirement","ECSS-Q-ST-30_0410022",1,"Created","The supplier shall maintain all data used for the dependability programme."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.1a","Requirement","ECSS-Q-ST-30_0410023",1,"Created","Dependability shall be integrated as part of the design process. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.1b","Requirement","ECSS-Q-ST-30_0410024",1,"Created","The dependability characteristics shall be traded off with other system attributes such as mass, size, cost and performance during the optimization of the design in all phases of the project. \n    ","NOTE Dependability is an inherent characteristic of a system or product."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.1c","Requirement","ECSS-Q-ST-30_0410025",1,"Created","Manufacture, assembly, integration, test and operations shall not degrade dependability attributes introduced into the design."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.2a","Requirement","ECSS-Q-ST-30_0410026",1,"Created","The dependability requirement specification shall be part of the overall project requirements."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.2b","Requirement","ECSS-Q-ST-30_0410027",1,"Created","Dependability requirements shall be apportioned, in a top-down process, to establish dependability requirements for lower level elements. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.2c","Requirement","ECSS-Q-ST-30_0410028",1,"Created","Dependability requirements shall be applied during the preparation and review of design and test specifications. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.2d","Requirement","ECSS-Q-ST-30_0410029",1,"Created","The dependability requirements shall be included into the technical specifications. \n    ","NOTE The technical specifications typically include:\n        · functional, operational and environmental requirements,\n        · test requirements including stress levels, test parameters, and accept or reject criteria,\n        · design performance margins, derating factors, quantitative dependability requirements, and qualitative dependability requirements (identification and classification of undesirable events), under specified environmental conditions,\n        · the identification of human factors and how they can influence dependability during the project lifecycle,\n        · the identification of external, internal and installation factors that can influence dependability during the project lifecycle, \n        · the degree of tolerance to hardware failures or software malfunctions, \n        · the detection, isolation, diagnosis, and recovery of the system from failures and its restoration to an acceptable state,\n        · the requirement for the prevention of failures crossing interfaces with unacceptable consequences,\n        · definition of the maintenance concept,\n        · maintenance tasks and requirements for special skills, \n        · requirements for preventive maintenance, special tools, and special test equipment,\n        · requirements for process and technology margin demonstration and qualification,\n        · requirement on sampling strategy in serial production and for periodical demonstration of qualification preservation."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.3.1a","Requirement","ECSS-Q-ST-30_0410030",1,"Created","The identification of critical areas of design and the assessment of the severity of failure consequences shall be interpreted by the level at which the analysis is made. \n    ","NOTE The Space System level can be broken down into Space Segment and Ground Segment where separate requirements can be provided. The Space Segment and Ground Segment can be further broken down, dependant on particular contractual requirements, into lower levels elements (e.g. subsystem, equipment…). "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.3.1b","Requirement","ECSS-Q-ST-30_0410031",1,"Created","The success criteria (sometimes referred to as “mission success criteria”) shall be defined at each level to be analysed. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.3.2a","Requirement","ECSS-Q-ST-30_0410032",1,"Created","A severity classification (either severity name or level) shall be assigned in accordance with Table 5-1 to each identified failure mode analysed according to the failure effect (consequence). "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.3.2b","Requirement","ECSS-Q-ST-30_0410033",1,"Created","Severity categories shall be assigned without consideration of existing compensating provisions to provide a qualitative measure of the worst potential consequences resulting from item failure."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.3.2c","Requirement","ECSS-Q-ST-30_0410034",1,"Created","For analyses lower than system level, the severity due to possible failure propagation shall be identified as level 1 for dependability. \n    ","NOTE For example, for analysis at subsystem, and equipment level"]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.3.2d","Requirement","ECSS-Q-ST-30_0410035",1,"Created","The number identifying the severity category shall be followed by a suffix to indicate either redundancy (R) single point failures (SP) or safety hazards (SH)."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.3.2e","Requirement","ECSS-Q-ST-30_0410036",1,"Created","An understanding to these criteria identified in table 1 shall be agreed between customer and supplier."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.3.3a","Requirement","ECSS-Q-ST-30_0410037",1,"Created","Failure tolerance requirements shall be defined in the performance specifications."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.3.3b","Requirement","ECSS-Q-ST-30_0410038",1,"Created","The verification of the failure tolerance shall address all failure modes whose severity of consequence is classified as catastrophic, critical and major."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.3.4a","Requirement","ECSS-Q-ST-30_0410039",1,"Created","The supplier shall confirm that reliability is built into the design using fault tolerance and design margins. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.3.4b","Requirement","ECSS-Q-ST-30_0410040",1,"Created","The supplier shall analyse the failure characteristics of systems in order to identify areas of design weakness and propose corrective solutions. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.3.4c","Requirement","ECSS-Q-ST-30_0410041",1,"Created","In order to implement dependability aspects into the design, the following approaches shall apply:\n    1. functional design:\n        (a) the preferred use of software designs or methods that have performed successfully in similar applications\n        (b) the implementation of failure tolerance;\n        (c) the implementation of fault detection, isolation and recovery, allowing proper failure processing by dedicated flight and ground measures, and considering detection or reconfiguration times in relation with propagation times of events under worst case conditions;\n        (d) the implementation of monitoring of the parameters that are essential for mission performance, considering the failure modes of the system in relation to the actual capability of the detection devices, and considering the acceptable environmental conditions to be maintained on the product.\n    2. physical design:\n        (a) the application of proven design rules;\n        (b) the selective use of designs that have performed successfully in the same intended mission environment;\n        (c) the selection of parts having a quality level in accordance with project specification;\n        (d) the use of EEE parts derating and stress margins for mechanical parts;\n        (e) the use of design techniques for optimising redundancy (while keeping system design complexity as low as possible);\n        (f) the assurance that built-in equipment can be inspected and tested;\n        (g) the provision of accessibility to equipment.\n            ","NOTE Functional design is intended to imply non-physical design which includes software. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.4a","Requirement","ECSS-Q-ST-30_0410042",1,"Created","During the preliminary design phase, the contractor shall classify functions, operations and products in accordance with their criticality level."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.4b","Requirement","ECSS-Q-ST-30_0410043",1,"Created","Classification shall be approved by the customer."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.4c","Requirement","ECSS-Q-ST-30_0410044",1,"Created","The criticality of functions (hardware and/or software) and operations shall be directly related to the severity of the consequences resulting from failure of the function as defined in Table 5-1.\n    ","NOTE For example, a function whose failure induces a catastrophic consequence is required to be classified with the highest criticality level."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.4d","Requirement","ECSS-Q-ST-30_0410045",1,"Created","The criticality of a product (hardware and software) shall be identified at the highest criticality of the functions associated to that product."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.4e","Requirement","ECSS-Q-ST-30_0410046",1,"Created","The classification shall be used to focus efforts on the most critical areas during the project phases."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.5a","Requirement","ECSS-Q-ST-30_0410047",1,"Created","The supplier shall ensure that dependability aspects are covered in all development, qualification and acceptance test planning and reviews, including the preparation of test specifications and procedures and the evaluation of test results. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.5b","Requirement","ECSS-Q-ST-30_0410048",1,"Created","The dependability discipline shall support:\n    1. definition of test characteristics and test objectives,\n    2. selection of measurement parameters, and\n    3. statistical evaluation of test results."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.6a","Requirement","ECSS-Q-ST-30_0410049",1,"Created","The supplier shall ensure that dependability cognizant and qualified staff:\n    1. contribute to definition of operations manual and procedures, \n    2. review operations manual and procedures for verification of consistency with dependability analyses."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.6b","Requirement","ECSS-Q-ST-30_0410050",1,"Created","Procedures for operations shall be analysed to identify and assess the risks associated with operations, sequences and situations that can affect dependability performance."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.6c","Requirement","ECSS-Q-ST-30_0410051",1,"Created","The analyses mentioned in 5.6b shall take into account the technical and human environment, and verify that the procedures:\n    1. include dispositions to face abnormal situations and supply the necessary safeguard measures;\n    2. do not compromise equipment reliability;\n    3. are in accordance with established maintenance dispositions; \n    4. include dispositions to minimize failures due to human errors."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.7a","Requirement","ECSS-Q-ST-30_0410052",1,"Created","The supplier shall establish and maintain a system to track the dependability recommendations, in order to support the risk reduction process. \n    ","NOTE These recommendations are derived from the dependability analyses, and trade-off studies (typically during Phases A and B). The dependability recommendations can be tracked in combination with safety recommendations."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.7b","Requirement","ECSS-Q-ST-30_0410053",1,"Created","All recommendations from 5.7a shall be justified, documented and tracked."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.7c","Requirement","ECSS-Q-ST-30_0410054",1,"Created","Formal evidence of acceptance or rejection of the recommendation by the supplier’s management shall be provided."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","5.7d","Requirement","ECSS-Q-ST-30_0410055",1,"Created","An accepted dependability recommendation shall be implemented into the relevant corresponding documentation .\n    ","NOTE Example of corresponding documentation are: design documents, and operation manuals."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.1a","Requirement","ECSS-Q-ST-30_0410056",1,"Created","The supplier shall identify undesirable events that lead to the loss or degradation of product performances, together with their classification into categories related to the severity of their failures consequences (see Table 5-1)."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.1b","Requirement","ECSS-Q-ST-30_0410057",1,"Created","Preliminary identification and classification of undesirable events shall be determined from analysis of criteria for mission success, during conceptual and preliminary design phases. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.1c","Requirement","ECSS-Q-ST-30_0410058",1,"Created","All undesirable events, whose occurrence can jeopardize, compromise, or degrade the mission success shall be assessed at the highest product level (overall system including space and ground segments). "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.1d","Requirement","ECSS-Q-ST-30_0410059",1,"Created","The undesirable events, at lower levels of the product tree, shall be the product failure effects which can induce the undesirable events identified for the highest product level. \n    ","NOTE For example, at space segment, ground segment, subsystem, and equipment level."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.1e","Requirement","ECSS-Q-ST-30_0410060",1,"Created","Identification and classification of undesirable events shall be finalised after assessment of failure scenarios (see clause 6.2)."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.2a","Requirement","ECSS-Q-ST-30_0410061",1,"Created","The supplier shall analyse the possible scenarios leading to the occurrence of undesirable events, "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.2b","Requirement","ECSS-Q-ST-30_0410062",1,"Created","The supplier shall identify failure modes, failure origins and causes, detailed failure effects leading to undesirable events."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.3a","Requirement","ECSS-Q-ST-30_0410063",1,"Created","Dependability analyses shall be performed on all space projects throughout the project life cycle to support the tasks and requirements specified in clause 5."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.3b","Requirement","ECSS-Q-ST-30_0410064",1,"Created","Dependability analyses shall be performed initially to contribute to the definition of the conceptual design and the system requirements. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.3c","Requirement","ECSS-Q-ST-30_0410065",1,"Created","The analyses shall be performed to support the conceptual, preliminary and detailed development and optimization of the design, including the testing phase that leads to design qualification. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.3d","Requirement","ECSS-Q-ST-30_0410066",1,"Created","Dependability analyses shall be implemented in order to:\n    1. ensure conformance to reliability, availability and maintainability requirements, and\n    2. identify all potential failure modes and technical risks with respect to functional requirements that can lead to non-compliance to the dependability requirements, \n    3. provide inputs to risk assessment and risk reduction and their control measures in line with the risk management process implemented on the project."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.3e","Requirement","ECSS-Q-ST-30_0410067",1,"Created","The results of dependability analyses shall be incorporated into the design justification file in order to support improvements to the design."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.1a","Requirement","ECSS-Q-ST-30_0410068",1,"Created","Dependability analyses shall be conducted on all levels of the space system and be performed in respect of the level that is being assessed i.e. System, Subsystem and Equipment levels.\n    ","NOTE The main purpose of all dependability analyses is to improve the design by providing timely feedback to the designer, to reduce risks within the processes used to realize the products and to verify conformance to the specified dependability requirement."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.1b","Requirement","ECSS-Q-ST-30_0410069",1,"Created","The analyses identified in clauses 6.4.2 to 6.4.4 shall be:\n    1. conducted as required by the contract, \n    2. tailored to match the generic requirements on each project, \n    3. taking into account the hardware, software and human functions comprising the system. \n        ","NOTE As it is not possible to quantitatively assess the software functions, only a qualitative assessment can be made as the dependability of software is influenced by the software development process."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.1c","Requirement","ECSS-Q-ST-30_0410070",1,"Created","A set of analyses selected from clauses 6.4.2 to 6.4.4 shall be defined as part of the contract requirement."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.1a","Requirement","ECSS-Q-ST-30_0410071",1,"Created","Reliability prediction techniques shall be used with the following objectives:\n    1. to optimize the reliability of a design against competing constraints such as cost and mass, \n    2. to predict the in–service reliability of a product,\n    3. to provide failure probability data for purposes such as risk assessment. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.1b","Requirement","ECSS-Q-ST-30_0410072",1,"Created","The reliability data sources and methods used in reliability predictions shall be as specified by the customer. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.1c","Requirement","ECSS-Q-ST-30_0410073",1,"Created","If the reliability data sources and methods are not specified by the customer, the supplier shall justify the selected data sources and methods used, for customer approval. \n    ","NOTE ECSS-Q-HB-30-08 is a guideline for the selection of reliability data sources and their use."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.1d","Requirement","ECSS-Q-ST-30_0410074",1,"Created","Reliability models shall be prepared to support predictions and FMEA/FMECA. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.2a","Requirement","ECSS-Q-ST-30_0410075",1,"Created","Failure Modes and Effects Analysis (FMEA) / Failure Modes, Effects and Criticality Analysis (FMECA) shall be performed on the functional and physical design (Functional FMECA and Product FMECA respectively) and, if required by the contract, the processes used to realize the final product (Process FMECA). "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.2b","Requirement","ECSS-Q-ST-30_0410076",1,"Created","All potential failure modes shall be identified and classified according to the severity (FMEA) or criticality (FMECA) of their consequences."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.2c","Requirement","ECSS-Q-ST-30_0410077",1,"Created","Measures shall be proposed in the analysis and introduced in the product design and in the control of processes to render all such consequences acceptable to the project."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.2d","Requirement","ECSS-Q-ST-30_0410078",1,"Created","When any design or process changes are made, the FMEA/FMECA shall be updated and the effects of new failure modes introduced by the changes shall be assessed."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.2e","Requirement","ECSS-Q-ST-30_0410079",1,"Created","Provisions for failure detection and recovery actions shall be identified as part of the FMEA/FMECA."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.2f","Requirement","ECSS-Q-ST-30_0410080",1,"Created","The FMEA/FMECA shall be used to support the verification of the reliability modelling, the reliability and safety analyses, maintainability analysis, logistic support activity, test and maintenance planning, and the Failure Detection, Isolation and Recovery (FDIR) policy."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.2g","Requirement","ECSS-Q-ST-30_0410081",1,"Created","As part of the FMEA/FMECA, potential failure propagation shall be assessed.\n    ","NOTE For FMEA/FMECA refer to ECSS-Q-ST-30-02."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.3a","Requirement","ECSS-Q-ST-30_0410082",1,"Created","HSIA shall be performed to ensure that the software reacts in an acceptable way to hardware failure. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.3b","Requirement","ECSS-Q-ST-30_0410083",1,"Created","HSIA shall be performed at the level of the technical specification of the software. \n    ","NOTE HSIA can be included in the FMEA/FMECA (refer to ECSS-Q-ST-30-02)."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.4a","Requirement","ECSS-Q-ST-30_0410084",1,"Created","Contingency analysis shall be performed in conformance with Annex D in order to:\n    1. identify the failure, identify the cause, control the effect and indicate how recovery of the mission integrity can be achieved\n    2. identify the methods of recovery of the nominal or degraded functionalities, with respect to project dependability policy,\n        ","NOTE 1 For example, availability targets.\nNOTE 2 The contingency analysis is typically a system level task.\nNOTE 3 FMEA/FMECA is an input to contingency analysis."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.5a","Requirement","ECSS-Q-ST-30_0410085",1,"Created","A Fault Tree Analysis shall be performed to ensure that the design conforms to the failure tolerance requirements for combinations of failures. \n    ","NOTE 1 ECSS-Q-ST-40-12 is a guideline for FTA.\nNOTE 2 The system supplier performs FTA to identify possible event combinations leading to the undesirable end event (e.g. “loss of mission”). Subsystem supplier provides input to this activity by establishing FTA at subsystem level with respect to the top events:\n        · loss of function of the subsystem, and\n        · inadvertent activation of the subsystem function."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.6a","Requirement","ECSS-Q-ST-30_0410086",1,"Created","Common-cause analyses shall be performed on reliability and safety critical items in conformance with Annex I, to identify the root cause of failures that have a potential to negate failure tolerance levels (see clause 5.3.3). \n    ","NOTE 1 The analyses can be accomplished as part of FMEA/FMECA or FTA. \nNOTE 2 An example of check list of generic common-cause parameters is provided in Annex L                                                 "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.7a","Requirement","ECSS-Q-ST-30_0410087",1,"Created","Worst case analysis shall be performed on electrical equipment in conformance with Annex J, to demonstrate that it performs within specification despite variations in its constituent part parameters and the imposed environment."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.7b","Requirement","ECSS-Q-ST-30_0410088",1,"Created","The WCA report shall contain all baseline information (assumptions, methods and techniques) used for the preparation of the analysis, the results obtained and a comparison of the specified parameters as derived from the specification of the equipment or module."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.7c","Requirement","ECSS-Q-ST-30_0410089",1,"Created","If not specified in the project requirement, the supplier shall propose the component aging parameter drifts for customer approval.\n    ","NOTE 1 The document ECSS-Q-TM-30-12 is a source for component aging parameter drifts, but is to be complemented with others inputs as it does not cover exhaustively the EEE parts.\nNOTE 2 ECSS-Q-HB-30-01 describes the WCA methodology."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.8a","Requirement","ECSS-Q-ST-30_0410090",1,"Created","Part derating shall be implemented in conformance with ECSS-Q-ST-30-11 to assure that the stress levels applied to all EEE parts are within the limits. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.8b","Requirement","ECSS-Q-ST-30_0410091",1,"Created","Part stress analyses shall be performed at part level to verify that the derating rules have been implemented."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.9a","Requirement","ECSS-Q-ST-30_0410092",1,"Created","Zonal analysis shall be performed in conformance with Annex G, in order to evaluate the consequences due to potential subsystem-to-subsystem interactions inherent in the system installation."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.2.10a","Requirement","ECSS-Q-ST-30_0410093",1,"Created","FDIR analysis shall be performed at System level in conformance with Annex F, to ensure that the autonomy and failure tolerance requirements are fulfilled.\n    ","NOTE ECSS-E-ST-70-11 provides the description of FDIR process."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.3a","Requirement","ECSS-Q-ST-30_0410094",1,"Created","Maintainability requirements shall be apportioned to set maintainability requirements for lower level products to conform to the maintenance concept and maintainability requirements of the system."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.3b","Requirement","ECSS-Q-ST-30_0410095",1,"Created","Maintainability prediction shall be performed at system level in conformance with Annex H, and used as a design tool to assess and compare design alternatives with respect to specified maintainability quantitative requirements:\n    1. the time to diagnose (i.e. detect and isolate) item failures,\n    2. the time to remove and replace the defective item, \n    3. the time to return the system or subsystem to its nominal configuration and to perform the necessary checks, and\n    4. the item failure rates. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.3c","Requirement","ECSS-Q-ST-30_0410096",1,"Created","Preventive maintenance analysis shall be performed at system level to determine the maintenance plan. \n    ","NOTE Each preventive maintenance action is based on the results of the application of systematic decision logic approved by the customer."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.3d","Requirement","ECSS-Q-ST-30_0410097",1,"Created","The maintainability analysis shall identify maintainability critical items.\n    ","NOTE Maintainability critical items include:\n        · products that cannot be checked and tested after integration, \n        · limited-life products, \n        · products that do not meet, or cannot be validated as compliant to the maintainability requirements."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.4a","Requirement","ECSS-Q-ST-30_0410098",1,"Created","The supplier shall perform availability analysis or simulations in order to assess the availability of the system. \n    ","NOTE The results are used to:\n        · optimize the system concept with respect to design, operations and maintenance,\n        · verify conformance to availability requirements, \n        · provide inputs to estimate the overall cost of operating the system."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.4b","Requirement","ECSS-Q-ST-30_0410099",1,"Created","The supplier shall perform an analysis of outages in order to supply input data for availability analysis. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.4c","Requirement","ECSS-Q-ST-30_0410100",1,"Created","The availability analysis output shall include a list of all potential outages identified (as defined in the project), their causes, probabilities of occurrence and duration. \n    ","NOTE Instead of outage probabilities, failure rates associated with outages can be provided."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.4d","Requirement","ECSS-Q-ST-30_0410101",1,"Created","The means of outage detection and the recovery methods shall be identified in the analysis."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.4.4e","Requirement","ECSS-Q-ST-30_0410102",1,"Created","The availability analysis shall be carried out at system level using the system reliability and maintainability models as well as the data from the outages. \n    ","NOTE For availability analysis, refer to ECSS-Q-ST-30-09."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.5a","Requirement","ECSS-Q-ST-30_0410103",1,"Created","The Dependability critical items identified by the dependability analyses shall be documented in conformance with ECSS-Q-ST-10-04."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.5b","Requirement","ECSS-Q-ST-30_0410104",1,"Created","Items identified as single-point failure with at least a failure consequence severity classified as catastrophic, critical or major, shall be included in the dependability critical items list."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.5c","Requirement","ECSS-Q-ST-30_0410105",1,"Created","Items that have a criticality number greater than or equal to 6 shall be included in the dependability critical items list in conformance with ECSS-Q-ST-30-02."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.5d","Requirement","ECSS-Q-ST-30_0410106",1,"Created","All items that have failure consequences classified as catastrophic shall be included in the dependability critical items list."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.5e","Requirement","ECSS-Q-ST-30_0410107",1,"Created","Products that cannot be checked and tested after integration, limited–life products, products that do not meet - or cannot be verified as meeting - applicable maintainability requirements, shall be included in the dependability critical items list."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","6.5f","Requirement","ECSS-Q-ST-30_0410108",1,"Created","The documentation for each dependability critical item shall include a justification for retention of that item and be subject to approval by the customer.\n    ","NOTE Further criteria for the classification of dependability critical items can be specified by the customer in line with the risk management policy defined on the project."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","7.1a","Requirement","ECSS-Q-ST-30_0410109",1,"Created","Reliability testing and demonstration shall be performed according to the project requirements in order to:\n    1. validate failure modes and effects,\n    2. check failure tolerance, failure detection and recovery,\n    3. obtain statistical failure data to support predictions and risk assessment,\n    4. consolidate reliability assessments,\n    5. validate the capability of the hardware to operate with software or to be operated by a human being in accordance with the specifications,\n    6. demonstrate the reliability of critical items, and\n    7. validate or justify data bases used for theoretical demonstrations."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","7.2a","Requirement","ECSS-Q-ST-30_0410110",1,"Created","Availability testing and demonstration shall be performed according to the project requirements in order to validate or justify data bases used for theoretical demonstrations (duration of outages and probability of occurrence)."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","7.3a","Requirement","ECSS-Q-ST-30_0410111",1,"Created","Maintainability demonstration shall be performed by performing the verification of the applicable maintainability requirements and by ensuring that preventive and corrective maintenance activities are successfully performed within the scope of the maintenance concept. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","7.3b","Requirement","ECSS-Q-ST-30_0410112",1,"Created","“The maintainability demonstration” shall verify the ability to:\n    1. detect, diagnose and isolate each faulty line replaceable unit or orbit replaceable unit;\n    2. remove and replace each line replaceable unit or orbit replaceable unit;\n    3. perform mission-essential repairs on units that are not intended to be replaced;\n    4. check that the product is fully functional after maintenance actions have been completed;\n    5. demonstrate that no safety hazard is introduced as a result of maintenance actions;\n    6. demonstrate that the maintenance operations can be performed within the applicable constraints, including the operations necessary to prepare a system during the launch campaign \n        ","NOTE 1 xample of such a constraints are time and volume or accessibility. \nNOTE 2 Example of such operations are “remove-before-flight” items or replacement of batteries. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","7.4a","Requirement","ECSS-Q-ST-30_0410113",1,"Created","Dependability data as specified in the contract, shall be collected for a period agreed with the customer from sources such as non-conformance and problem or failure reports, and maintenance reports. \n    ","NOTE Dependability data can be used for dependability performances monitoring through agreed or specified models. "]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","C.7a","Requirement","ECSS-Q-ST-30_0410114",1,"Created","The dependability plan shall include as a minimum:\n    • list of the applicable and reference documents,\n    • applicable dependability requirements,\n    • description of the dependability organisation and management,\n    • contractor / supplier management,\n    • details of the dependability tasks for each phase,\n    • dependability activities status reporting."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","D.7a","Requirement","ECSS-Q-ST-30_0410115",1,"Created","The contingency analysis document shall include:\n    • a description of the system,\n    • a description of the method to perform contingency analysis,\n    • details of the failure detection method,\n    • details of the diagnostics,\n    • details of the recovery actions or procedures,\n    • actions and recommendations for project team."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","E.7a","Requirement","ECSS-Q-ST-30_0410116",1,"Created","The reliability prediction document shall include:\n    • a clear identification of the design being analysed,\n    • reliability block diagrams,\n    • the methodology used with rationales,\n    • an analysis of the results,\n    • recommendations for project decision."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","F.7a","Requirement","ECSS-Q-ST-30_0410117",1,"Created","The FDIR analysis document shall include:\n• a description of the system\n• a description of the method to perform FDIR (e.g. FMEA/FMECA synthesis, FDIR reviews),\n• details of considered failures,\n• symptoms of failures (e.g. TM, observables),\n• detailed failure impact on the system,\n• the recovery actions (e.g. TC, automatic on board mechanism),\n• actions and recommendations for project team."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","G.7a","Requirement","ECSS-Q-ST-30_0410118",1,"Created","The zonal analysis document shall include:\n    • an identification of the perimeter under investigation, \n    • a detailed definition of the interface(s),\n    • the description of the potential interaction(s),\n    • the list of actions and recommendations for project decision."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","H.7a","Requirement","ECSS-Q-ST-30_0410119",1,"Created","The document shall contain, as a minimum:\n    • maintenance levels: for corrective and preventive actions,\n    • identification of FDIR policy,\n    • mathematical model description,\n    • the maintenance indicators (e.g. MTTR, maintenance time per year, maintenance frequency),\n    • the sparing recommendations (e.g. number of spares, weight and volume of up and downloading spares),\n    • identification of Maintainability Critical Items."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","I.7a","Requirement","ECSS-Q-ST-30_0410120",1,"Created","The common-cause analysis document shall include:\n    • a description of the perimeter of the design being analysed,\n    • the list of the ‘common-cause’ parameters and their effects,\n    • actions and recommendations for project team.\n\t","NOTE See check lists parameters examples in Annex L."]
["ECSS-Q-ST-30C","ECSS - Superseded v1.0","J.7a","Requirement","ECSS-Q-ST-30_0410121",1,"Created","The WCA document shall include:\n    • assumptions applicable to the environmental condition,\n    • a list of the selected parts database with the worst case parameters,\n    • a description of the general methodology, \n    • an explanation of the numerical analysis technique, \n    • results and conclusion of the WCA."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.1a","Requirement","ECSS-Q-ST-40_0440001",1,"Created","The supplier shall establish and maintain a safety programme to assure conformance with project safety policy and requirements."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.1b","Requirement","ECSS-Q-ST-40_0440002",1,"Created","The safety programme shall establish a safety management system to implement provisions of this Standard - commensurate with the programme requirements and tailored by the customer \n    NOTE 1 For tailoring, refer to clause 1                                         \n    NOTE 2 The system safety programme requirements are subject to tailoring, without diminishing the intent to protect flight and ground personnel, the launch vehicle, associated payloads, ground support equipment, the general public, public and private property, the space system and associated segments and the environment from hazards associated with space systems.\n    NOTE 3 As support to tailoring, informative Annex F provides a guideline for determining the applicability of this standard depending on the type of project."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.2a","Requirement","ECSS-Q-ST-40_0440003",1,"Created","The supplier shall establish and maintain a safety programme plan in conformance with the DRD in Annex B.\n    NOTE The plan can either be included as part of an overall project product assurance plan or as a separate safety programme plan."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.2b","Requirement","ECSS-Q-ST-40_0440004",1,"Created","The supplier shall cover, in his safety programme plan, the safety tasks for the project phases in conformance with 5.7.1."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.3a","Requirement","ECSS-Q-ST-40_0440005",1,"Created","The supplier shall comply with all applicable national or international safety regulations."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.3b","Requirement","ECSS-Q-ST-40_0440006",1,"Created","The launch site safety regulations and rules shall be applied."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.3c","Requirement","ECSS-Q-ST-40_0440007",1,"Created","The implementation of safety requirements shall not be compromised by other requirements.\n    NOTE For example: security requirements."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.4.1a","Requirement","ECSS-Q-ST-40_0440008",1,"Created","Each supplier shall appoint a safety manager who has appropriate training or experience."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.4.1b","Requirement","ECSS-Q-ST-40_0440009",1,"Created","The safety manager shall have organisational authority and independence to:\n    1. establish and maintain a safety programme in accordance with the project safety requirements,\n    2. manage all safety assurance aspects of the design of the system (including software) and its operation in accordance with the Safety Plan,\n    3. coordinate the interfaces:\n        (a) with the relevant bodies involved in the project in accordance with the safety plan,\n        (b) with the safety launcher authority.\n            NOTE Depending on the project safety criticality, the safety manager can be combined with other functions (e.g. PA manager) when agreed with the customer."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.4.2.1a","Requirement","ECSS-Q-ST-40_0440010",1,"Created","The safety manager shall:\n    1. have the right of access to safety-related data relevant to project safety in conformance with ECSS-M-ST-40, \n    2. have unimpeded access to any management level without organizational constraint on any aspect of project safety."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.4.2.2a","Requirement","ECSS-Q-ST-40_0440011",1,"Created","The safety manager or safety relevant authority shall have the authority to:\n    1. reject any project document, or to stop any project activity that does not conform to approved safety requirements or procedures,\n    2. interrupt hazardous operations when it becomes clear by the Safety Manager that the operation does not conform to the agreed measures defined in the corresponding hazard report and derived approved hazard procedure."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.4.3a","Requirement","ECSS-Q-ST-40_0440012",1,"Created","The supplier shall perform safety audits or reviews to verify compliance to project safety policy and requirements."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.4.3b","Requirement","ECSS-Q-ST-40_0440013",1,"Created","The safety audits shall be in accordance with ECSS-M-ST-10 and ECSS-Q-ST-10.\n    NOTE The safety audits can be part of the project audits."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.4.3c","Requirement","ECSS-Q-ST-40_0440014",1,"Created","The customer shall be informed of the audit schedule."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.4.4a","Requirement","ECSS-Q-ST-40_0440015",1,"Created","Documentation related to safety shall be approved by the safety manager upon his verification of completeness, compliance with stated safety requirements and formal closeout of open safety verification items (as defined and agreed during safety audits and reviews)."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.4.5a","Requirement","ECSS-Q-ST-40_0440016",1,"Created","The safety manager (or a designated representative) shall have concluded the review of, and approved, any hazardous operation before it is executed."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.4.6a","Requirement","ECSS-Q-ST-40_0440017",1,"Created","The safety manager or designated delegate shall be represented at configuration control boards (CCBs), nonconformance review boards (NRBs), test review board (TRBs), and at qualification, and acceptance reviews, where safety requirements and safety-critical functions are involved."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.4.6b","Requirement","ECSS-Q-ST-40_0440018",1,"Created","The safety function shall be further represented at all boards dealing with health matters where exposure or endurance limits are defined for flight and ground crews."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.4.7a","Requirement","ECSS-Q-ST-40_0440019",1,"Created","The safety approval authority shall:\n    1. review and disposes the safety data submittals,\n    2. approve the close-out of hazards,\n    3. decide on deviations and waivers, and finally\n    4. accept the statement of safety compliance."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.5a","Requirement","ECSS-Q-ST-40_0440020",1,"Created","The safety risk identification, reduction and control shall be part of the project's risk management process as specified in ECSS-M-ST-80."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.5b","Requirement","ECSS-Q-ST-40_0440021",1,"Created","Safety risk identification, reduction and control shall be a continuous and iterative process throughout the project life cycle, encompassing\n    1. allocation of safety requirements;\n    2. hazard and safety risk identification;\n    3. evaluation (including categorisation) of consequence severity;\n    4. hazard and safety risk reduction and control;\n    5. close out and acceptance of residual risk."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.5c","Requirement","ECSS-Q-ST-40_0440022",1,"Created","For the identification of hazards and associated safety risks, consideration shall be given to past experience, studies, ground and flight tests, reviews, the industrial process as well as the operational use."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.6a","Requirement","ECSS-Q-ST-40_0440023",1,"Created","The safety critical items shall be part of the project's overall critical items control programme as specified in ECSS-Q-ST-10-04."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.1.1a","Requirement","ECSS-Q-ST-40_0440024",1,"Created","Safety analysis shall support the identification of sources of safety risk as well as the performance of preliminary trade-off analyses between alternative system concepts."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.1.1b","Requirement","ECSS-Q-ST-40_0440025",1,"Created","The following safety programme tasks shall apply for human spaceflight programmes and safety critical systems:\n    1. Analyse safety requirements and lessons-learnt associated with similar previous missions;\n    2. Perform preliminary hazard analysis of the proposed system and operations concept to support concept trade-offs;\n    3. Perform comparative safety risk assessment of the concept options;\n    4. Identify the relevant project safety requirements;\n    5. Plan safety activities for the feasibility phase;\n    6. Support the mission definition review.\n        NOTE These tasks should also serve as a guideline for other space programmes."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.1.2a","Requirement","ECSS-Q-ST-40_0440026",1,"Created","Safety analysis shall support trade-off analyses in arriving at the concept that has acceptable safety risk considering the project and mission constraints. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.1.2b","Requirement","ECSS-Q-ST-40_0440027",1,"Created","The design technology selected and the operational concept to be implemented shall be selected based on the analysis data for the safest system architecture to eliminate or reduce hazards to acceptable levels."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.1.2c","Requirement","ECSS-Q-ST-40_0440028",1,"Created","The following safety programme tasks shall apply for human spaceflight programmes and safety critical systems:\n    1. Commence hazard analyses of the design and operations concepts in order to identify applicable system level hazards, hazardous conditions, and potential hazardous events and consequences; \n    2. Support concept trades by identifying safety critical aspects of the concept options;\n    3. Apply hazard elimination and minimization and make safety recommendations; \n    4. Perform comparative safety risk assessments of the concept options; \n    5. Identify system level safety critical functions;\n    6. Identify system level project specific safety requirements; \n    7. Plan safety activities for the project definition phase; \n    8. Support the preliminary requirements review. \n        NOTE These tasks should also serve as a guideline for other space programmes."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.1.3a","Requirement","ECSS-Q-ST-40_0440029",1,"Created","The safety analysis shall support a continued and more detailed safety optimization of the system design and operations and the identification of technical safety requirements and their applicability."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.1.3b","Requirement","ECSS-Q-ST-40_0440030",1,"Created","The analysis shall also provide inputs to safety risk assessment in support of safety risk evaluation, the identification of risk contributors in the design and in the operational concept."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.1.3c","Requirement","ECSS-Q-ST-40_0440031",1,"Created","The following safety programme tasks shall apply for human spaceflight programmes and safety critical systems:\n    1. Update hazard analysis in support of design and mission concept definition activities; identify additional project specific safety requirements; \n    2. Update safety critical functions identification, and define the failure tolerance requirements; \n    3. Identify emergency, warning, and caution situations;\n    4. Update the system safety risk assessment as part of the contribution provided by the safety domain to the risk management process;\n    5. Identify project safety requirements; \n    6. Ensure that project requirement documentation and activities comply with project safety requirements;\n    7. Support a system requirements review and preliminary design review; \n    8. Plan verification of safety requirements implementation; \n    9. Prepare the safety plan for the detailed definition, production and qualification phase. \n        NOTE These tasks should also serve as a guideline for other space programmes."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.1.4a","Requirement","ECSS-Q-ST-40_0440032",1,"Created","Safety analysis shall support detailed design, production, qualification, testing."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.1.4b","Requirement","ECSS-Q-ST-40_0440033",1,"Created","Safety analysis shall also support operational safety optimization, safety requirements implementation evaluation, risk reduction verification, and hazard and risk acceptance."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.1.4c","Requirement","ECSS-Q-ST-40_0440034",1,"Created","Analysis of operations shall also support the identification of emergency and contingency response planning and training requirements, and the development of procedures."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.1.4d","Requirement","ECSS-Q-ST-40_0440035",1,"Created","The following safety programme tasks shall apply for human spaceflight programmes and safety critical systems:\n    1. Perform detailed system level hazard analysis; \n    2. Perform supporting safety analysis;\n    3. Update the project technical safety requirements to incorporate the results of safety analyses; \n    4. Ensure that the project implementation and verification programme covers identified hazard control verification activities; \n        NOTE For example: reviews, inspections, analyses and tests.\n    5. Update safety critical functions identification, failure tolerance requirements, and identify safety critical items; \n    6. Implement control programme for safety critical items; \n    7. Perform safety risk assessment in support of design improvement, project resource apportionment, control programme for safety critical items and project reviews; \n    8. Monitor verification of safety requirements implementation; \n    9. Verify and document hazard control implementation; \n    10. Check that all open verification items are recorded and agreed procedures are in place;\n    11. Support the critical design review, the qualification review and the acceptance review;\n    12. Perform project internal safety reviews and internal audits; \n    13. Identify, monitor and control project assembly, integration, testing and handling operations which are potentially hazardous to personnel or hardware; \n    14. Review and approve hazardous and safety critical operational procedures;\n    15. Perform accident-incident reporting and investigation; \n    16. Support customer safety reviews at defined programme milestones;\n    17. Prepare a project safety “lessons-learned” report; \n    18. Prepare operational phase safety plan. \n        NOTE These tasks should also serve as a guideline for other space programmes."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.1.5a","Requirement","ECSS-Q-ST-40_0440036",1,"Created","Safety analysis shall evaluate design and operational changes for impact to safety, assuring that safety margins are maintained and that operations are conducted within accepted risk."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.1.5b","Requirement","ECSS-Q-ST-40_0440037",1,"Created","The analysis shall also support the evaluation of operational anomalies for impact to safety, and the continued evaluation of risk trends."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.1.5c","Requirement","ECSS-Q-ST-40_0440038",1,"Created","The following safety programme tasks shall apply for human spaceflight programmes and safety critical systems:\n    1. Issue the operational phase safety plan;\n    2. Review operational procedures; \n    3. Approve safety critical operational procedures; \n    4. Identify and monitor hazardous operations; \n    5. Support the flight readiness review, operational readiness review, launch readiness review and flight qualification reviews;\n    6. Support ground and flight operations; \n    7. Perform safety critical items control; \n    8. Monitor and assess evolution of the system configuration and operations resulting from design fixes and updates;\n    9. Update hazard analyses and implement additional hazard controls as necessary; \n    10. Investigate safety related flight anomalies and trends; \n    11. Update safety risk assessment as necessary to support operational decisions;\n    12. Prepare disposal phase safety plan. \n        NOTE These tasks should also serve as a guideline for other space programmes."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.1.6a","Requirement","ECSS-Q-ST-40_0440039",1,"Created","Safety analysis shall evaluate all disposal operations and associated hazards. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.1.6b","Requirement","ECSS-Q-ST-40_0440040",1,"Created","Disposal solutions shall be identified which meet the project's safety requirements."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.1.6c","Requirement","ECSS-Q-ST-40_0440041",1,"Created","The following safety programme tasks shall apply for human spaceflight programmes and safety critical systems:\n    1. Perform hazard analysis with respect to the disposal operations;\n    2. Check that the disposal operation conforms to international safety regulations by performing the necessary safety analysis;\n    3. Review the procedures of the disposal operations;\n    4. Support the mission close-out review.\n        NOTE These tasks should also serve as a guideline for other space programmes."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.2a","Requirement","ECSS-Q-ST-40_0440042",1,"Created","The supplier shall hold regular safety status and progress meetings with the customer and his lower tier suppliers as part of the project progress meetings as specified in ECSS-M-ST-10. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.2b","Requirement","ECSS-Q-ST-40_0440043",1,"Created","The relevant customer and supplier specialists shall attend the meetings."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.3a","Requirement","ECSS-Q-ST-40_0440044",1,"Created","The customer shall define, conduct and chair the safety reviews to ensure satisfactory implementation of safety programme and technical safety requirements. \n    NOTE A supplier is considered as a customer vis-à-vis its lower tier suppliers (as defined in ECSS-S-ST-00)."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.3b","Requirement","ECSS-Q-ST-40_0440045",1,"Created","The supplier shall support safety reviews by the customer and the relevant safety approval authority, as specified in the relevant review plans. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.3c","Requirement","ECSS-Q-ST-40_0440046",1,"Created","Each supplier participating in a safety review shall prepare, and submit for review, the safety data package."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.7.3d","Requirement","ECSS-Q-ST-40_0440047",1,"Created","Safety reviews shall be performed, and the review objectives achieved, in conformance with clause 5.7.1."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.8a","Requirement","ECSS-Q-ST-40_0440048",1,"Created","The supplier shall provide a statement of safety compliance to demonstrate that the space system elements conform to stated safety requirements. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.8b","Requirement","ECSS-Q-ST-40_0440049",1,"Created","The supplier shall include in his statement of compliance a statement that open verifications are followed up in the safety verification tracking log (SVTL), as defined in clause 8.5.1, and do not affect further safe processing."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.8c","Requirement","ECSS-Q-ST-40_0440050",1,"Created","The project shall provide to the safety approval authority all safety-related information for their acceptance of the statement of safety compliance."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.9.1a","Requirement","ECSS-Q-ST-40_0440051",1,"Created","Safety training shall be part of the overall training in accordance with ECSS-Q-ST-20."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.9.1b","Requirement","ECSS-Q-ST-40_0440052",1,"Created","All safety related training of any personnel working - permanently or occasionally - with system elements that can have hazardous properties shall have three major aspects:\n    1. general awareness briefings on safety measures to be taken at a given location or working environment;\n    2. basic technical training in the required safety techniques and skills which is a prerequisite to fulfil the job function under consideration;\n        NOTE For example: inspection, test, maintenance or integration.\n    3. product specific training that focuses on the hazards related to the specific system element."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.9.2a","Requirement","ECSS-Q-ST-40_0440053",1,"Created","The supplier shall identify the need for product specific safety training and implement the corresponding safety training programme for all relevant parties. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.9.2b","Requirement","ECSS-Q-ST-40_0440054",1,"Created","The supplier shall inform the customer of any safety training identified by him as necessary for the flight operations crew or mission control personnel, together with a definition of the type of training required and its scope."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.9.2c","Requirement","ECSS-Q-ST-40_0440055",1,"Created","The supplier shall support the implementation of the customer's training programme for the flight operations crew or mission control personnel."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.9.3a","Requirement","ECSS-Q-ST-40_0440056",1,"Created","All personnel accessing the area where the product is processed shall participate previously in the general safety awareness briefing."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.9.4a","Requirement","ECSS-Q-ST-40_0440057",1,"Created","The supplier shall provide basic technical training to all project engineering and safety personnel working with hazardous products."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.9.5a","Requirement","ECSS-Q-ST-40_0440058",1,"Created","The supplier shall maintain records of personnel having received safety training in accordance with ECSS-Q-ST-20."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.10a","Requirement","ECSS-Q-ST-40_0440059",1,"Created","The supplier shall report to the customer all accidents and incidents occurred during project activities under the control of the supplier or his lower tier suppliers that affect the system element. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.10b","Requirement","ECSS-Q-ST-40_0440060",1,"Created","The supplier shall support - at request - project related accident and incident investigations that occur outside of the supplier’s control or facility."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.10c","Requirement","ECSS-Q-ST-40_0440061",1,"Created","The supplier shall coordinate the investigation activities in cooperation with other supplier functional departments and lower tier suppliers."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.10d","Requirement","ECSS-Q-ST-40_0440062",1,"Created","The accident or incident investigation report shall be formally closed by the supplier upon approval by the customer."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.10e","Requirement","ECSS-Q-ST-40_0440063",1,"Created","If the conclusion of the assessment is that the accident-incident has had an effect on the project, i.e. the safety of the product or its operation, the organisations safety representative shall be informed."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.10f","Requirement","ECSS-Q-ST-40_0440064",1,"Created","In case of 5.10e., the accident-incident report shall become part of the project's safety data and is documented in the safety data package."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.11.1a","Requirement","ECSS-Q-ST-40_0440065",1,"Created","The supplier shall maintain, as part of the project documentation, all safety-related data to support reviews and safety compliance demonstration."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.11.1b","Requirement","ECSS-Q-ST-40_0440066",1,"Created","The customer shall be given access to this data on request during audits, safety reviews and meetings held at the supplier’s premises in accordance with ECSS-M-ST-40."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.11.2a","Requirement","ECSS-Q-ST-40_0440067",1,"Created","The supplier shall submit a safety data package (SDP) to support reviews.\n    NOTE This can be a stand-alone package or be integrated into the overall data package if the safety review is part of an overall project review."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.11.2b","Requirement","ECSS-Q-ST-40_0440068",1,"Created","The safety data package shall contain at least the following safety related documentation:\n    1. Safety analysis report (in accordance with Annex D);\n    2. Supporting analysis (if applicable);\n    3. Safety risk assessment (if applicable);\n    4. Hazardous ground operations list and procedures;\n    5. Safety verification tracking log (SVTL, in accordance with Annex C)."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.11.2c","Requirement","ECSS-Q-ST-40_0440069",1,"Created","The contents of the safety data packages for the planned safety reviews of a project or programme shall be specified by the Safety Approval Authority to assure they support the objectives of the safety reviews for which they are delivered (in conformance with clause 5.7.2). "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.11.2d","Requirement","ECSS-Q-ST-40_0440070",1,"Created","The supplier shall use the actual configuration baseline, as defined by ECSS-M-ST-40, as the design and operational baseline that is the subject of the safety data package."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.11.2e","Requirement","ECSS-Q-ST-40_0440071",1,"Created","The supplier shall integrate safety data related to the various subsystems or equipment that makes up the system into the safety data package that is presented at the review."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.11.2f","Requirement","ECSS-Q-ST-40_0440072",1,"Created","All safety data shall be traceable from the safety data package and available for review."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.11.3.1a","Requirement","ECSS-Q-ST-40_0440073",1,"Created","Safety requirements that cannot be met shall be identified as specified in ECSS-M-ST-40."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.11.3.1b","Requirement","ECSS-Q-ST-40_0440074",1,"Created","A request for deviation or waiver shall be generated and tracked according to the requirements of ECSS-M-ST-40. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.11.3.2a","Requirement","ECSS-Q-ST-40_0440075",1,"Created","All RFD/RFW shall be assessed in order to identify those which impact safety. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.11.3.2b","Requirement","ECSS-Q-ST-40_0440076",1,"Created","The accumulated deviations and waivers that affect safety shall be assessed to ensure that the effects of individual deviations do not invalidate the rationale used for the acceptance of other deviations."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.11.3.3a","Requirement","ECSS-Q-ST-40_0440077",1,"Created","Safety deviations and waivers shall be subject to safety approval authority acceptance."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.11.3.4a","Requirement","ECSS-Q-ST-40_0440078",1,"Created","Deviations and waivers that affect project safety requirements or safety-critical functions which the supplier considers acceptable shall be subject of review and disposition by the customer and the safety approval authority."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.11.4a","Requirement","ECSS-Q-ST-40_0440079",1,"Created","Safety lessons learned shall be collected during the project and used during the project, as far as they are relevant.\n    NOTE Safety lessons learned should consider as a minimum:\n        a. the impact of newly imposed requirements;\n        b. assessment of all malfunctions, accidents, anomalies, deviations and waivers;\n        c. effectiveness of safety strategies of the project;\n        d. new safety tools and methods that have been developed or demonstrated;\n        e. effective versus ineffective verifications that have been performed;\n        f. changes proposed to safety policy, strategy or technical requirements with rationale."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.11.4b","Requirement","ECSS-Q-ST-40_0440080",1,"Created","The safety lessons learned information shall be made available to the customer and suppliers, particularly to project and safety managers as well as design and safety engineers upon request for use on other projects. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","5.11.5a","Requirement","ECSS-Q-ST-40_0440081",1,"Created","The safety critical items identified by the safety analysis shall be documented in accordance with ECSS-Q-ST-10-04."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.2a","Requirement","ECSS-Q-ST-40_0440082",1,"Created","Safety requirements shall be identified and traced from the system level into the design and then allocated to the lower levels."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.2b","Requirement","ECSS-Q-ST-40_0440083",1,"Created","When specified by the project, the identified safety requirements shall be justified in the design and presented in an appropriate document."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.2a","Requirement","ECSS-Q-ST-40_0440084",1,"Created","Appropriate design features shall be selected to ensure inherent safety.\n    NOTE Such features are fail safe design solutions, damage control, containment and isolation of potential hazards. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.3.1a","Requirement","ECSS-Q-ST-40_0440085",1,"Created","The following sequence of activities shall be applied to identified hazards, hazardous conditions, and functions whose failures have hazardous consequences:\n    1. Hazard elimination\n    2. Hazard minimization\n    3. Hazard control."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.3.2a","Requirement","ECSS-Q-ST-40_0440086",1,"Created","Hazards and hazardous conditions shall, consistent with the project constraints and mission objectives, be eliminated from the design and operational concepts by the selection of design technology, architecture and operational characteristics. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.3.3a","Requirement","ECSS-Q-ST-40_0440087",1,"Created","Where hazards and hazardous conditions are not eliminated, the severity of the associated hazardous events and consequences shall, consistent with the project constraints and mission objectives, be reduced to an accepted level through the change of the design architecture, technologies, and operational characteristics allowing the substitution of those hazards by other hazards with lower potential threat."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.3.4.1a","Requirement","ECSS-Q-ST-40_0440088",1,"Created","Hazards that have not been eliminated and have been subjected to hazard minimization (as defined in 6.3.3.3a) shall be controlled through preventative or mitigation measures, associated to hazard scenarios, which are introduced into the system design and operation to avoid the events or to interrupt their propagation to consequences."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.3.4.1b","Requirement","ECSS-Q-ST-40_0440089",1,"Created","The following measures shall be applied in order of precedence:\n    1. Design selection\n    2. Automatic safety devices\n    3. Warning devices\n    4. Special procedures."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.3.4.2a","Requirement","ECSS-Q-ST-40_0440090",1,"Created","Failure tolerance is the basic safety requirement that shall be used to control most hazards. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.3.4.2b","Requirement","ECSS-Q-ST-40_0440091",1,"Created","The design shall tolerate a minimum number of credible failures and/or operator errors determined by the hazard consequence."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.3.4.2c","Requirement","ECSS-Q-ST-40_0440092",1,"Created","The supplier shall establish the list of failures to be considered as \"non credible\" for customer approval as early as possible in development."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.3.4.3a","Requirement","ECSS-Q-ST-40_0440093",1,"Created","Hazard which cannot be controlled by compliance to failure tolerance shall be reduced to an accepted level by compliance with specific safety related properties and characteristics of the design. \n    NOTE Examples are: structures, pressures vessels, mechanisms, material compatibility, flammability."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.3.4.4a","Requirement","ECSS-Q-ST-40_0440094",1,"Created","Hazards that are not eliminated through design selection shall be reduced and made controllable through the use of automatic safety devices as part of the system, subsystem or equipment. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.3.4.4b","Requirement","ECSS-Q-ST-40_0440095",1,"Created","The safety devices, specified in 6.3.3.4.4a, shall not be dependant on human performance."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.3.4.4c","Recommendation","ECSS-Q-ST-40_0440320",1,"Created","Use of software in automatic safety devices should be avoided."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.3.4.4d","Requirement","ECSS-Q-ST-40_0440097",1,"Created","If software is used in automatic safety devices, justification shall be provided."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.3.4.5a","Requirement","ECSS-Q-ST-40_0440098",1,"Created","When it is not practical to preclude the existence or occurrence of known hazards or to use automatic safety devices, devices shall be used for the timely detection of the condition and the generation of a warning signal."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.3.4.5b","Requirement","ECSS-Q-ST-40_0440099",1,"Created","This shall be coupled with emergency controls of corrective action for operators to safe or shut down the affected subsystem."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.3.4.6a","Requirement","ECSS-Q-ST-40_0440100",1,"Created","When it is not possible to reduce the magnitude of a hazard through the design, the use of safety devices or the use of warning devices, special procedures shall be developed to control the hazardous conditions for the enhancement of safety."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.3.4.6b","Requirement","ECSS-Q-ST-40_0440101",1,"Created","Special procedures shall be verified by test and appropriate training be provided for personnel."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.3.4.6c","Requirement","ECSS-Q-ST-40_0440102",1,"Created","Hazard detection shall be implemented if alternative means cannot be used."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.3.4.6d","Requirement","ECSS-Q-ST-40_0440103",1,"Created","To permit the use of real time monitoring, hazard detection and safing systems for hazard control, the availability of sufficient response time shall be verified and corresponding safing procedures be developed and verified and the personnel trained.\n    NOTE Special procedures are the least effective of the hazard control and risk reduction measures available. They can include emergency and contingency procedures, procedural constraints, or the application of a controlled maintenance programme. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.4a","Requirement","ECSS-Q-ST-40_0440104",1,"Created","The system design shall meet the safety requirements under the worst-case natural and induced environments defined for the project."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.4b","Requirement","ECSS-Q-ST-40_0440105",1,"Created","Design and performance margins shall be established and applied for worst-case combinations of induced and natural environments and operating characteristics."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.5a","Requirement","ECSS-Q-ST-40_0440106",1,"Created","Loss, malfunctioning, and sudden restoration of external services shall be defined as an input to the development phase."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.5b","Requirement","ECSS-Q-ST-40_0440107",1,"Created","The system design shall be defined so that catastrophic or critical consequences are not induced by loss, malfunctioning, and sudden restoration of external services."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.6a","Requirement","ECSS-Q-ST-40_0440108",1,"Created","Safety monitoring, display, alarm and safing capabilities shall be incorporated for manned space systems."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.6b","Requirement","ECSS-Q-ST-40_0440109",1,"Created","These capabilities shall provide the information to allow the crew and system operators to take actions to protect personnel from the consequences of failures within safety-critical functions and the failure of hazard control measures."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.6c","Requirement","ECSS-Q-ST-40_0440110",1,"Created","The system design shall provide the capability for detecting failures that result in degradation of failure tolerance with respect to the hazard detection, signalling and safing function."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.6d","Requirement","ECSS-Q-ST-40_0440111",1,"Created","The performance of these functions shall be verifiable during flight and ground operational phases."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.6e","Requirement","ECSS-Q-ST-40_0440112",1,"Created","The emergency, caution and warning function shall detect and notify the crew and system operators of emergency, warning and caution situations."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.6f","Requirement","ECSS-Q-ST-40_0440113",1,"Created","Safing functions and capabilities shall be included that provide for the containment or control of emergency, warning and caution situations. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.6g","Requirement","ECSS-Q-ST-40_0440114",1,"Created","Provisions shall be included for the monitoring of safing function execution. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.6h","Requirement","ECSS-Q-ST-40_0440115",1,"Created","Dedicated safing functions shall be provided for emergency situations."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.6i","Requirement","ECSS-Q-ST-40_0440116",1,"Created","Control of warning and caution situations shall be acceptable by system reconfiguration or by dedicated safing functions."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.6j","Requirement","ECSS-Q-ST-40_0440117",1,"Created","A single failure shall not cause loss of the emergency and warning function."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.6k","Requirement","ECSS-Q-ST-40_0440118",1,"Created","Where the operation of a safing system introduces a new hazard, inadvertent activation of the safing system shall be controlled in accordance with the failure tolerance requirements."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.6l","Requirement","ECSS-Q-ST-40_0440119",1,"Created","A single failure shall not cause loss of the emergency and warning functions together with the monitored functions. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.6m","Requirement","ECSS-Q-ST-40_0440120",1,"Created","Emergency, warning and caution data, out of limit annunciation and safing commands shall be given priority over other data processing and command functions."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.6n","Requirement","ECSS-Q-ST-40_0440121",1,"Created","When systems or elements are integrated into, or docked with the other systems or elements, the emergency, warning, caution, and safing function shall enable the areas of control responsibility to monitor and display the applicable parameters, and to control the related safing functions. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.6o","Requirement","ECSS-Q-ST-40_0440122",1,"Created","Emergency, warning, and caution parameter status information shall be available and displayed at the launch control and mission control centres in “near real time” during the operational phases. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.6p","Requirement","ECSS-Q-ST-40_0440123",1,"Created","It shall be possible for the crew to ascertain and monitor in “real time” the status of emergency, warning and caution parameters of non-crewed systems or elements prior to docking with crewed systems."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.7a","Requirement","ECSS-Q-ST-40_0440124",1,"Created","The design and the operational characteristics of the space system shall be such that the generation of space debris is minimized consistent with the project constraints and mission objectives."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.8a","Requirement","ECSS-Q-ST-40_0440125",1,"Created","The space vehicle shall be designed and operated (post-mission disposal manoeuvres) such that, where applicable, the risk of a catastrophic event does not exceed the level of acceptable risk specified by the project and by the launch base safety authority.\n    NOTE Hardware of a space system that is returned from orbit presents a potential threat to the Earth's population due to the risk of debris entering the atmosphere in an uncontrolled manner."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.9a","Requirement","ECSS-Q-ST-40_0440126",1,"Created","Biological contamination (including organic-constituents) resulting from the introduction of extraterrestrial matter shall be avoided."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.9b","Requirement","ECSS-Q-ST-40_0440127",1,"Created","The introduction of extraterrestrial matter shall not affect the environmental conditions on Earth."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.9c","Requirement","ECSS-Q-ST-40_0440128",1,"Created","Extraterrestrial matter shall be treated as hazardous substances until proven otherwise."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.9d","Requirement","ECSS-Q-ST-40_0440129",1,"Created","A containment function for hazardous substances of the spacecraft, which prevents release in case of accidents until recovery or arrival at a dedicated containment facility, shall be provided. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.9e","Requirement","ECSS-Q-ST-40_0440130",1,"Created","If containment cannot be verified, the hazardous substances (and any part of the space system that has potentially been exposed) shall not be returned to Earth (unless sterilized in space)."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.10a","Requirement","ECSS-Q-ST-40_0440131",1,"Created","A mission abort capability shall be provided."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.10b","Requirement","ECSS-Q-ST-40_0440132",1,"Created","Safing and safe heaven functions shall be provided. \n    NOTE These functions can be implemented through measures such as resource conservation, increased shielding (solar flares, meteoroids and radiation), vehicle or systems reconfiguration and trajectory changes. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.10c","Requirement","ECSS-Q-ST-40_0440133",1,"Created","Escape and rescue functions shall be provided. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.10d","Requirement","ECSS-Q-ST-40_0440134",1,"Created","The capability to reconfigure the system to restore the functional capability of safety critical functions in case of failures or accidents shall be provided. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.10e","Requirement","ECSS-Q-ST-40_0440135",1,"Created","The capability to monitor, detect and assess hazards and effects of slow insidious events with hazardous consequences shall be detailed according to project constraints and mission objectives.\n    NOTE Such hazards include fatigue, corrosion, micro-organisms, aging, deterioration, contamination. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.10f","Requirement","ECSS-Q-ST-40_0440136",1,"Created","The space system shall provide an on-board medical facility and the capability for handling a permanently impaired or deceased crewmember."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.3.11a","Requirement","ECSS-Q-ST-40_0440137",1,"Created","System shall be designed such that any required access to system elements during flight or ground operations can be accomplished with an accepted level of risk to personnel. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.1a","Requirement","ECSS-Q-ST-40_0440138",1,"Created","The severity of potential consequences of identified hazardous events shall be categorized as shown in Table 6-1."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.1b","Requirement","ECSS-Q-ST-40_0440139",1,"Created","An understanding of the criteria defined in Table 6-1 shall be agreed between customer and supplier."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.1c","Requirement","ECSS-Q-ST-40_0440140",1,"Created","Detrimental environmental effects, from the point of view of severe hazardous consequences to the global public, shall be included in the consequence severity evaluation.\n    NOTE 1 Table 6-1 is used both in ECSS-Q-ST-30 and ECSS-Q-ST-40.\n    NOTE 2 This impact can be immediate and personal. It also can be on a broader scale not limited to a single person only. The hazardous consequences can be short term or long term.\n    NOTE 3 In space flight, the environment concerned can be outer space, including the Moon and the planets, geostationary orbit (GEO), low Earth orbit (LEO) as well as the Earth’s atmosphere."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.1d","Requirement","ECSS-Q-ST-40_0440141",1,"Created","The availability of the following shall not be used as rationale for the reduction of the severity: \n    1. design features which reduce the probability of a hazardous event occurring, but which do not affect its severity; \n    2. warning devices, crew safe haven, or crew escape capabilities. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.1e","Requirement","ECSS-Q-ST-40_0440142",1,"Created","For international programmes, a coherent set of consequence severity shall be established for joint operational phases."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.1f","Requirement","ECSS-Q-ST-40_0440143",1,"Created","These categories shall not violate the safety policy and principles as defined in clause 4.2.1 for the protection of human life or the principles of categorization in accordance with the definition of consequence severity categories in Table 6-1."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.1g","Requirement","ECSS-Q-ST-40_0440144",1,"Created","The expert assessment on determining limits for exposures that do not create a hazard, those that create critical hazards and those that create catastrophic hazards shall be performed by the responsible authority, early in the design process.\n    NOTE Examples of responsible authority are medical boards or radiation protection committees."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.1h","Requirement","ECSS-Q-ST-40_0440145",1,"Created","The detailed safety requirements and measures shall be derived from allowed exposure levels.\n    NOTE For example: maximum allowable concentrations, maximum emission concentrations or radiation doses."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.2.1a","Requirement","ECSS-Q-ST-40_0440146",1,"Created","Failure tolerance shall be the basic safety requirement used to control hazards."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.2.1b","Requirement","ECSS-Q-ST-40_0440147",1,"Created","No single system failure or single operator error shall have critical or catastrophic consequences. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.2.1c","Requirement","ECSS-Q-ST-40_0440148",1,"Created","No combination of two independent system failures or operator errors shall have catastrophic consequences."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.2.1d","Requirement","ECSS-Q-ST-40_0440149",1,"Created","Safety inhibits shall be independent, verifiable, stable and stay in a safe position even in case of energy failure."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.2.1e","Requirement","ECSS-Q-ST-40_0440150",1,"Created","Multiple failures, which result from common-cause or common-mode failure mechanisms, shall be analysed as single failures for determining failure tolerance."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.2.2a","Requirement","ECSS-Q-ST-40_0440151",1,"Created","The system design shall:\n    1. include the capability for on-board redundancy management of safety-critical functions, \n    2. provide failure tolerance and redundancy status information to the flight and ground crews, including immediate crew notification in the case of failure detection, redundancy switch-over, or loss of operational redundancy,\n    3. include failure detection, failure isolation and switching of redundant items."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.2.2b","Requirement","ECSS-Q-ST-40_0440152",1,"Created","The capability shall be provided to the flight crew and mission control to override automatic safing and redundancy switch-over."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.2.2c","Requirement","ECSS-Q-ST-40_0440153",1,"Created","Alternate or redundant safety-critical functions shall be physically and functionally separated or protected in such a way that any event that causes the loss of one path does not result in the loss of alternative or redundant paths."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.2.3a","Requirement","ECSS-Q-ST-40_0440154",1,"Created","Hardware failures or software errors shall not cause additional failures with hazardous effects or propagate to cause the hazardous operation of interfacing hardware."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.3.1a","Requirement","ECSS-Q-ST-40_0440155",1,"Created","Technical requirements for areas of design for minimum risk shall be identified and approved by the relevant safety approval authorities\n    NOTE “Design for minimum risk” is a safety requirement used to control hazards by specifying safety-related properties and characteristics of the design."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.3.2a","Requirement","ECSS-Q-ST-40_0440156",1,"Created","Structural safety factors shall be defined and applied in accordance with ECSS-E-ST-32-10 or higher safety factor where applicable."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.3.2b","Requirement","ECSS-Q-ST-40_0440157",1,"Created","Safety margins shall be based on worst credible combinations of environmental conditions."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.3.3a","Requirement","ECSS-Q-ST-40_0440158",1,"Created","For manned systems, where structural failure can have catastrophic or critical consequences, structures, pressure vessels, fasteners and load-bearing paths within mechanisms shall be designed in accordance with ECSS-E-ST-32-01."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.3.3b","Requirement","ECSS-Q-ST-40_0440159",1,"Created","For unmanned systems, only pressure vessels shall be designed in accordance with ECSS-E-ST-32-01, when required by launch site safety authority."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.3.4a","Requirement","ECSS-Q-ST-40_0440160",1,"Created","Materials shall be selected and controlled in accordance with ECSS-Q-ST-70."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.3.4b","Requirement","ECSS-Q-ST-40_0440161",1,"Created","Material selection shall assure that hazards associated with material characteristics are either eliminated or controlled.\n    NOTE Examples of these material properties to be characterized are: toxicity, flammability, resistance to stress corrosion, outgassing, offgassing, resistance to radiation, resistance to thermal cycling, arc tracking, thermal degradation, resistance to cleaning fluid and microbiological growth."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.3.4c","Requirement","ECSS-Q-ST-40_0440162",1,"Created","If requirement 6.4.3.4b. is not feasible, the system design shall include the necessary provisions to control hazardous events associated with material characteristics in accordance with the requirements of this Standard.\n    NOTE An example of provisions to be included by the system design is containment of hazardous substances. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.4a","Requirement","ECSS-Q-ST-40_0440163",1,"Created","When given, the probabilistic safety targets shall be used for\n    1. identifying and ranking major risk contributors,\n    2. making the acceptable risk decision for each identified hazard,\n    3. supporting the disposition making for those cases where nonconformance to the qualitative requirements is identified.\n        NOTE Probabilistic safety targets can be established by the customer for hazardous consequences at system level for each project or programme. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.4.4b","Requirement","ECSS-Q-ST-40_0440164",1,"Created","Probabilistic safety targets shall conform to the requirements given by launch safety authorities and national and international regulations.\n    NOTE Informative Annex E provides criteria for the establishing of probabilistic safety targets."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.5.1a","Requirement","ECSS-Q-ST-40_0440165",1,"Created","A safety critical function that, if lost or degraded, or through incorrect or inadvertent operation, can result in a catastrophic or critical hazardous consequence, shall be identified as a safety-critical function.\n    NOTE As an example, a series of operational events that can result in a hazard if they occur inadvertently or are operated out of order."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.5.1b","Requirement","ECSS-Q-ST-40_0440166",1,"Created","Identification shall be done without taking into account hazards controls to be or already implemented."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.5.2a","Requirement","ECSS-Q-ST-40_0440167",1,"Created","Inadvertent operation of a safety-critical function shall be prevented by\n    1. two independent inhibits, if it induces critical consequences, or\n    2. three independent inhibits, if it induces catastrophic consequences."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.5.3a","Requirement","ECSS-Q-ST-40_0440168",1,"Created","The system shall provide failure tolerance and redundancy status information of safety-critical functions."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.5.3b","Requirement","ECSS-Q-ST-40_0440169",1,"Created","The system shall provide the status of at least two inhibits on functions that, if inadvertently operated, can lead to catastrophic consequences, including\n    1. notification in real time in case of failure detection,\n    2. announcement of any loss of operational redundancy, \n    3. notification of redundancy switch-over, or \n    4. changes of inhibit status."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.5.4a","Requirement","ECSS-Q-ST-40_0440170",1,"Created","The design shall either provide the capability for the safe shutdown of safety-critical functions prior to in-flight maintenance operations or conform to the failure tolerance requirements during maintenance operations."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.5.5a","Requirement","ECSS-Q-ST-40_0440171",1,"Created","Electronic, electrical, electromechanical (EEE) components used to support safety-critical functions in flight standard hardware shall be selected and procured in accordance with the applicable programme requirements of ECSS-Q-ST-60."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.5.6.1a","Requirement","ECSS-Q-ST-40_0440172",1,"Created","Safety aspects associated with the software function shall be an integral part of the overall system safety efforts and not be assessed in isolation."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.5.6.1b","Requirement","ECSS-Q-ST-40_0440173",1,"Created","A software component shall be considered safety-critical if the loss or degradation of its function, or its incorrect or inadvertent operation, can result in catastrophic or critical consequences. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.5.6.2a","Requirement","ECSS-Q-ST-40_0440174",1,"Created","During the project life cycle, safety analysis shall be carried out to:\n    1. identify the criticality of software components in accordance with the severity of the consequences as defined in Table 6-1,\n    2. determine where and under what conditions the system can trigger hazardous events caused by the software,\n    3. define verification methods for hazard controls involving software,\n    4. provide verification evidence of hazard control implementation. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.5.6.3a","Requirement","ECSS-Q-ST-40_0440175",1,"Created","The criticality of a software component shall be evaluated taking into account the overall system design which can provide for, e.g. back-up or emergency procedures, hardware inhibits and certain time to effect."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.5.6.4a","Requirement","ECSS-Q-ST-40_0440176",1,"Created","A safety-critical software component shall be designed, implemented, verified and operated according to the engineering and product assurance requirements defined in ECSS-E-ST-40 and ECSS-Q-ST-80."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.5.6.4b","Requirement","ECSS-Q-ST-40_0440177",1,"Created","Safety-critical software shall be analysed for the identification and verification of adequate software controls and inhibits and validated accordingly. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.5.6.4c","Requirement","ECSS-Q-ST-40_0440178",1,"Created","The level of required software product assurance effort shall be determined in accordance with the criticality of the software component."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.1a","Requirement","ECSS-Q-ST-40_0440179",1,"Created","Safety involvement in the operational phase shall be planned."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.1b","Requirement","ECSS-Q-ST-40_0440180",1,"Created","Responsibilities, rules and contingency procedures shall be established prior to operation for hazardous “limit” conditions that can occur during ground and in-flight operations."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.1c","Requirement","ECSS-Q-ST-40_0440181",1,"Created","Operating ranges and performance limits for safe operation shall be established and specified."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.1d","Requirement","ECSS-Q-ST-40_0440182",1,"Created","The design shall not require continuous active control by personnel in order to stay within the established operating ranges and performance limits."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.1e","Requirement","ECSS-Q-ST-40_0440183",1,"Created","Man-machine interfaces shall be designed and the personnel tasks shall be scoped to reduce the potential for hazardous events resulting from human error to an accepted level."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.1f","Requirement","ECSS-Q-ST-40_0440184",1,"Created","Limits for crew exposure to natural and system-induced environments shall be established and maintained by design features or operational constraints that cover nominal, contingency, and emergency operational modes, in order to preclude crew injury or inability to perform safety-critical functions."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.2.1a","Requirement","ECSS-Q-ST-40_0440185",1,"Created","Hazards to the humans, public and private property and the environment, resulting from launcher system operation or malfunction shall be precluded by compliance with the regulations of the launch safety authority."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.2.2a","Requirement","ECSS-Q-ST-40_0440186",1,"Created","Normal or abort operations shall not result in contamination of the Earth’s environment that endangers human health, crops or natural resources or that exceed limits set by national or international regulations."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.2.3a","Requirement","ECSS-Q-ST-40_0440187",1,"Created","Flight rules shall be prepared for each mission that outline pre-planned decisions in case of off-nominal situations and consistent with safety requirements."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.2.4a","Requirement","ECSS-Q-ST-40_0440188",1,"Created","Hazardous commanding control shall ensure that all hazardous commands are identified."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.2.4b","Requirement","ECSS-Q-ST-40_0440189",1,"Created","Hazardous commanding control shall ensure that failure modes, associated with flight and ground operation - including hardware, software and procedures - used in commanding from control centres or other ground equipment, are included in the safety assessment."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.2.4c","Requirement","ECSS-Q-ST-40_0440190",1,"Created","Hazardous commanding control shall ensure that the system design provides protection to avoid the erroneous acceptance of commands that can result in catastrophic or critical consequences."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.2.4d","Requirement","ECSS-Q-ST-40_0440191",1,"Created",".Hazardous commanding control shall ensure that commands, which can result in catastrophic or critical hazardous consequences, are not performed until they are authorized and verified."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.2.5a","Requirement","ECSS-Q-ST-40_0440192",1,"Created","Mission operation change control shall ensure that all changes, which are desired or become necessary during mission, are reviewed for safety impact."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.2.5b","Requirement","ECSS-Q-ST-40_0440193",1,"Created","Mission operation change control shall ensure that the responsible safety approval authority approves all operational change requests with safety impact."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.2.6a","Requirement","ECSS-Q-ST-40_0440194",1,"Created","Safety status parameters shall be identified."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.2.6b","Requirement","ECSS-Q-ST-40_0440195",1,"Created","Safety status parameters shall be monitored."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.2.6c","Requirement","ECSS-Q-ST-40_0440196",1,"Created","Deviation from specified limits shall be managed."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.2.7a","Requirement","ECSS-Q-ST-40_0440197",1,"Created","In the case of a deviation from the planned launch trajectory during ascent, launch vehicle stages shall be remotely destroyed or have their propulsion engines shut off to prevent stages or debris from falling outside pre-defined safe areas."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.2.7b","Requirement","ECSS-Q-ST-40_0440198",1,"Created","The launch vehicle and spent stage trajectories shall be monitored to determine vehicle, stage or debris impact points."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.2.7c","Requirement","ECSS-Q-ST-40_0440199",1,"Created","Residual propellants contained in spent or aborted suborbital stages shall be safely dispersed."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.3.1a","Requirement","ECSS-Q-ST-40_0440200",1,"Created","Safety requirements of the clause shall be applied during the following ground operations:\n    1. development, qualification or acceptance testing;\n    2. assembly, integration or test operations;\n    3. launch site operations;\n    4. servicing or turn-around operations; and\n    5. transportation or handling operations,"]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.3.2a","Requirement","ECSS-Q-ST-40_0440201",1,"Created","The supplier shall establish procedures to perform safety readiness reviews and inspections prior to the performance of any applicable operation."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.3.3a","Requirement","ECSS-Q-ST-40_0440202",1,"Created","To verify conformance to safety requirements, readiness reviews and inspections shall include safety review and assessment of facilities, equipment (incl. GSE), test articles, operating, test and contingency procedures, access controls, and personnel capabilities to comply with the safety requirements."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.3.4a","Requirement","ECSS-Q-ST-40_0440203",1,"Created","Hazardous operations shall be monitored for conforming to safety requirements and procedures, and for the possible development of unforeseen hazardous situations. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.3.4b","Requirement","ECSS-Q-ST-40_0440204",1,"Created","Where necessary, contingency and emergency plans or procedures shall be established and verified prior to the commencement of the operation. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.3.4c","Requirement","ECSS-Q-ST-40_0440205",1,"Created","The safety manager or safety relevant authority shall have the authority to stop any operation that does not conform to safety requirements. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.3.5a","Requirement","ECSS-Q-ST-40_0440206",1,"Created","Launch, landing, turn-around and mission operations shall be subject to hazard analysis."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.3.5b","Requirement","ECSS-Q-ST-40_0440207",1,"Created","For ground operations, the analysis shall address the:\n    1. potential hazardous consequences of human error and procedural deficiencies;\n    2. adequacy and maintenance of operational margins;\n    3. potential for human exposure to hazards and hazardous effects;\n    4. requirements for operator and flight crew training;\n    5. adequacy of information and data provided by the flight hardware, ground support equipment (GSE), or test equipment, as appropriate, to support the performance of the operations in accordance with all applicable safety requirements (including all safety regulations)."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.3.6a","Requirement","ECSS-Q-ST-40_0440208",1,"Created","All Ground support equipment (GSE) shall be subjected to hazard analysis."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.3.6b","Requirement","ECSS-Q-ST-40_0440209",1,"Created","All GSE shall conform to the ‘Essential Health & Safety Requirements’ of all applicable EU ‘New Approach directives’. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.3.6c","Requirement","ECSS-Q-ST-40_0440210",1,"Created","Conformance to 6.6.3.6b. shall be shown by the addition of the ‘CE’ mark to the product and the issuing of a ‘Declaration of Conformity’."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","6.6.3.6d","Requirement","ECSS-Q-ST-40_0440211",1,"Created","Conformance to any other product related directives shall be demonstrated.\n    NOTE Further guidance is given in Annex G."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.2a","Requirement","ECSS-Q-ST-40_0440212",1,"Created","Safety analysis shall be performed in a systematic manner as a basis for all applicable phases and to ensure that hazards are identified, eliminated or minimized and controlled and safety risks are assessed and reduced."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.2b","Requirement","ECSS-Q-ST-40_0440213",1,"Created","Safety analyses shall be initiated early in the design process and provide concurrent support to project engineering in the selection of the least hazardous design and operational options that are compatible with the project mission and programme constraints and conform to the requirements."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.2c","Requirement","ECSS-Q-ST-40_0440214",1,"Created","The results of safety analyses shall also be used to support project management in the assessment of the overall risks, verification of risk reduction, ranking of risk sources, support to project resource allocation, monitoring of risk trends, and residual risk acceptance. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.2d","Requirement","ECSS-Q-ST-40_0440215",1,"Created","Analysis shall always be made with reference to a defined configuration baseline as defined by ECSS-M-ST-40."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.3.1a","Requirement","ECSS-Q-ST-40_0440216",1,"Created","The supplier shall respond to and comply with the applicable safety requirements for the project."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.3.2a","Requirement","ECSS-Q-ST-40_0440217",1,"Created","The supplier shall identify additional safety requirements, where applicable, through the use of lessons learned from previous projects and the safety analyses performed during the project."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.3.3a","Requirement","ECSS-Q-ST-40_0440218",1,"Created","The supplier shall define the safety requirements for the various functions of the system."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.3.4a","Requirement","ECSS-Q-ST-40_0440219",1,"Created","The supplier shall define the safety requirements associated with the various subsystems and lower levels."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.3.5a","Requirement","ECSS-Q-ST-40_0440220",1,"Created","The supplier shall justify to the customer the proposed allocation of safety requirements at the latest at the end of the detailed definition phase."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.3.6a","Requirement","ECSS-Q-ST-40_0440221",1,"Created","The supplier shall ensure that the function and subsystem safety requirements are included in the relevant functional and subsystem specification."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.4a","Requirement","ECSS-Q-ST-40_0440222",1,"Created","Safety analysis shall be refined and updated in an iterative manner as the design process proceeds, to ensure that hazards and hazardous events are assessed, and that the relevant detailed design and operational requirements, hazard controls, and verification activities are defined and implemented.\n    NOTE Refer to 5.7 for detailed safety programme tasks in the different project phases"]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.1a","Requirement","ECSS-Q-ST-40_0440223",1,"Created","The safety analysis report shall be established in conformance with the DRD in Annex D in order to gather results of safety analyses, which use deterministic and probabilistic methods which are described in the clauses 7.5.2 to 7.5.4."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.2a","Requirement","ECSS-Q-ST-40_0440224",1,"Created","Hazard analysis shall be performed in a systematic manner, beginning in the concept phase and continuing through the operational phase, including end-of-life and disposal."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.2b","Requirement","ECSS-Q-ST-40_0440225",1,"Created","Hazard analysis shall support the hazard reduction process."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.2c","Requirement","ECSS-Q-ST-40_0440226",1,"Created","Hazard analysis shall identify and evaluate:\n    1. hazards associated with system design, its operation (both on ground and in flight) and the operation environment; \n    2. the hazardous effects resulting from the physical and functional propagation of initiator events;\n    3. the hazardous events resulting from the failure of system functions and functional components;\n    4. time critical situations. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.2d","Requirement","ECSS-Q-ST-40_0440227",1,"Created","The following potential initiator events shall be considered:\n    1. hardware failure (random or time dependent);\n    2. latent software error;\n    3. operator error;\n    4. design inadequacies, including:\n        (a) inadequate margins;\n        (b) unintended operating modes caused by sneak-circuits;\n        (c) material inadequacies and incompatibilities;\n        (d) hardware-software interactions;\n    5. natural and induced environmental effects;\n    6. procedural deficiencies."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.2e","Requirement","ECSS-Q-ST-40_0440228",1,"Created","Hazard analysis includes a systematic analysis of the “system” operations and operating procedures that shall be performed in the detailed design and operational stages of a project. \n    NOTE This analysis evaluates the capability of the system to be operated safely, to determine the safest operating modes, and to evaluate the acceptability of the operating procedures."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.2f","Requirement","ECSS-Q-ST-40_0440229",1,"Created","The systematic analysis of system operation and operating procedures shall be repeated as the design and operational detail evolves, including the system’s operational modes and man-machine interfaces."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.3a","Requirement","ECSS-Q-ST-40_0440230",1,"Created","Safety risk assessment shall \n    1. comprise the identification, classification and ranking of safety risks and their contributors,\n    2. be based on deterministic hazard analysis by combining the consequence severity and the likelihood of occurrence of the consequence,\n    3. be used to facilitate effective and efficient safety risk reduction and control, \n    4. support project risk management as defined in ECSS-M-ST-80, \n    5. assess compliance with probabilistic safety targets.\n        NOTE 1 The estimation of event likelihoods is based on the use of different sources of data i.e.: \n            · previous experience on the particular system (i.e. measured or observed directly relevant test or experience data), \n            · data from other systems or projects (i.e. extrapolation from generic data, similarity data, or physical models), and \n            · expert judgment (i.e. direct estimation of likelihoods by domain specialists).\n        NOTE 2 The determination of likelihood is not a mean to downgrade the severity of function (see 6.4.1d)                                                     "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.3b","Requirement","ECSS-Q-ST-40_0440231",1,"Created","Safety risk assessment shall be started early in the design process and performed in progressive steps during the implementation of the safety programme. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.4.1a","Requirement","ECSS-Q-ST-40_0440232",1,"Created","Following supporting assessment and analysis methods shall be used as necessary (tailored by project) to support hazards analysis and safety risk assessment.\n    NOTE 1 Example of tailoring by project is when the supporting assessment and analysis methods are not applicable in e.g. unmanned missions.\n    NOTE 2 Assessments and analyses from ECSS-Q-ST-30 can be used to support safety assessment."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.4.1b","Requirement","ECSS-Q-ST-40_0440233",1,"Created","Supporting analyses shall be agreed with all relevant parties."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.4.2a","Requirement","ECSS-Q-ST-40_0440234",1,"Created","Warning time analysis shall be performed during the concept definition phase and the design and development phase in order to evaluate time-critical situations identified in the hazard analysis and to support the implementation of hazardous-situation detection and warning devices or contingency procedures. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.4.2b","Requirement","ECSS-Q-ST-40_0440235",1,"Created","The analysis shall determine the\n    1. time interval during which the event is detected and the response action taken; \n    2. detection capability of the proposed design with respect to detection sensitivity and detection time; \n    3. resultant time available for response;\n    4. adequacy of the proposed design or contingency procedures, including emergency evacuation, rescue, system reconfiguration, redundancy switching, and maintenance."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.4.2c","Requirement","ECSS-Q-ST-40_0440236",1,"Created","The detection times shall be determined from the\n    1. occurrence of the initiating event to the time when a hazardous consequence occurs (propagation time); \n    2. occurrence of the initiating event to the time of earliest detection or annunciation; and \n    3. time taken for corrective action to be implemented."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.4.3a","Requirement","ECSS-Q-ST-40_0440237",1,"Created","Caution and warning analysis shall be performed during the concept definition phase and the design and development phase of human space flight programmes in order to identify\n    1. emergency, warning, and caution parameters;\n    2. the required safing functions and capabilities;\n    3. limit sensing requirements;\n    4. the applicability of the individual “caution and warning” functions to the different mission phases. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.4.3b","Requirement","ECSS-Q-ST-40_0440238",1,"Created","The caution and warning analysis shall utilize the results of the warning time and hazards analyses as appropriate."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.4.4.1a","Requirement","ECSS-Q-ST-40_0440239",1,"Created","Multiple failures, which result from common-cause or common-mode failure mechanisms, shall be analysed as single failures for determining failure tolerance. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.4.4.2a","Requirement","ECSS-Q-ST-40_0440240",1,"Created","The supplier shall identify the requirement for and the scope of dedicated common-cause and common-mode analyses by means of the review of the results of the other safety analyses, such as FTA and hazard analysis, and of the characteristic of the system and of its environment."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.4.4.3a","Requirement","ECSS-Q-ST-40_0440241",1,"Created","The supplier shall identify potential common-cause failures by assessment of the effects of common-causes. \n    NOTE For example: radiation, thermal environment and fires."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.4.4.3b","Requirement","ECSS-Q-ST-40_0440242",1,"Created","The common-cause failure analysis shall be performed in coordination with the FTA and the hazard analysis.\n    NOTE The analysis of common-cause failures can require that use be made of the result of dedicated engineering analyses, e.g. thermal analyses, meteorite or debris impact analysis."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.4.4.4a","Requirement","ECSS-Q-ST-40_0440243",1,"Created","Common-mode failures shall be analysed by means of the use of check-lists (to be established by the supplier) that list potential common-modes for system components during the manufacturing, integration, test, operation and maintenance phases. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.4.4.4b","Requirement","ECSS-Q-ST-40_0440244",1,"Created","The common-mode analysis shall be coordinated with the FMEA/FMECA."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.4.4.5a","Requirement","ECSS-Q-ST-40_0440245",1,"Created","Results of common-cause and common-mode analysis shall be integrated with the results of the system level safety analyses (fault tree analysis, hazard analysis)."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.4.5a","Requirement","ECSS-Q-ST-40_0440246",1,"Created","The fault tree analysis shall be used to establish the systematic link between the system-level hazard and the contributing hazardous events and subsystem, equipment or piece part failure."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.4.5b","Requirement","ECSS-Q-ST-40_0440247",1,"Created","A fault tree analysis, or its equivalent, shall be performed to verify the failure tolerance requirements.\n    NOTE Refer to ECSS-Q-ST-40-12 “Fault tree analysis - Adoption notice ECSS/IEC 61025” for further instructions on fault tree analyses."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.4.6a","Requirement","ECSS-Q-ST-40_0440248",1,"Created","Whenever safety analyses identify operator errors as a cause of catastrophic or critical hazards, a dedicated analysis shall be carried out."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.4.6b","Requirement","ECSS-Q-ST-40_0440249",1,"Created","The human error analysis shall be used to support the safety analysis for the identification of human operator error modes and their effects and for the definition of adequate countermeasures to prevent or control human operator errors."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.4.6c","Requirement","ECSS-Q-ST-40_0440250",1,"Created","The human error analysis shall be developed from the early phases of the project onwards in order to define recommendations for the hardware and software design, procedure development and training preparation programme."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.4.7a","Requirement","ECSS-Q-ST-40_0440251",1,"Created","The results of failure modes and effects analysis (FMEA) or failure modes, effects and criticality analysis (FMECA) shall be used to support the hazard analysis in the evaluation of the effects of failures. FMEA/FMECA and hazard analysis are complementary analyses.\n    NOTE Refer to ECSS-Q-ST-30-02 for further instructions on FMEA/FMECA."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.4.8a","Requirement","ECSS-Q-ST-40_0440252",1,"Created","Zonal analysis shall be performed where redundancy is used to reduce the probability of losing a function or of inadvertently actuating a safety-critical function."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","7.5.4.8b","Requirement","ECSS-Q-ST-40_0440253",1,"Created","The objectives of the zonal analysis shall ensure that equipment installation meets the adequate safety requirements regarding:\n    1. basic installation rules and space practices;\n    2. interaction between subsystems;\n    3. implication of operator errors;\n    4. effects of external events.\n        NOTE Zonal analysis is the systematic inspection of the topology of a system, the evaluation of potential component-to-component interactions with and without failure, and the assessment of the severity of potential hazards inherent in the system installation."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.1a","Requirement","ECSS-Q-ST-40_0440254",1,"Created","A system shall be in place that tracks all hazards and related risks, to relate all verifications of the corresponding hazard uniquely to unambiguous causes and controls."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.1b","Requirement","ECSS-Q-ST-40_0440255",1,"Created","For common techniques for verification of design features used to control hazards, the requirements of ECSS-E-ST-10 shall apply. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.1c","Requirement","ECSS-Q-ST-40_0440256",1,"Created","To successfully complete the safety process, positive feedback shall be provided on completion results for all verification items associated with a given hazard."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.2.1a","Requirement","ECSS-Q-ST-40_0440257",1,"Created","The supplier shall establish a hazard reporting system for tracking the status of all identified hazards."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.2.1b","Requirement","ECSS-Q-ST-40_0440258",1,"Created","The system shall be applied for all hazards with potentially catastrophic or critical consequences."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.2.1c","Requirement","ECSS-Q-ST-40_0440259",1,"Created","The supplier shall report, and provide evidence, that\n    1. controls are defined and agreed;\n    2. verification methods are defined and agreed; \n    3. verification is completed."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.2.1d","Requirement","ECSS-Q-ST-40_0440260",1,"Created","If verification cannot be completed, the supplier shall establish a Safety Verification Tracking Log (SVTL) (refer to clause 8.5.1a.)."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.2.2a","Requirement","ECSS-Q-ST-40_0440261",1,"Created","Status of hazard control and risk reduction activities shall be reviewed at safety progress meetings and project safety reviews for compliance with decisions taken and achievement of intended results."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.2.3a","Requirement","ECSS-Q-ST-40_0440262",1,"Created","All hazard documentation shall be formally issued for each safety review and major project review, as specified in clause 5.11). "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.3.1a","Requirement","ECSS-Q-ST-40_0440263",1,"Created","Verification engineering shall select the verification methods consistent:\n    1. with the verification requirements documented in the hazard report,\n    2. with the launch base safety rules."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.3.1b","Requirement","ECSS-Q-ST-40_0440264",1,"Created","Verification planning shall commence in an integrated manner upon selection of the control method."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.3.2a","Requirement","ECSS-Q-ST-40_0440265",1,"Created","Safety verification methods shall include alternatively or in combination review of design, analysis, inspection and test."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.3.2b","Requirement","ECSS-Q-ST-40_0440266",1,"Created","For all safety verifications traceability shall be provided."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.3.3a","Requirement","ECSS-Q-ST-40_0440267",1,"Created","All relevant technical safety and engineering analyses performed or updated with analysis in respect to the as-built configuration shall be used for verification. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.3.3b","Requirement","ECSS-Q-ST-40_0440268",1,"Created","When similarity analysis is provided, for tracking purposes it shall contain a copy of (or a unique reference to) the referenced previous verification, verification procedure and requirement valid at the time of the first verification."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.3.4.1a","Requirement","ECSS-Q-ST-40_0440269",1,"Created","Inspections which are considered as necessary in order to meet safety requirements of the system shall be identified and included in user manuals and procedures."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.3.4.2a","Requirement","ECSS-Q-ST-40_0440270",1,"Created","All preflight safety inspections shall be assessed for inclusion in the MIP list. \n    NOTE If preflight safety inspections are included on the MIP list, closeout is feasible by MIP reporting or individual reporting as appropriate."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.3.4.2b","Requirement","ECSS-Q-ST-40_0440271",1,"Created","Launch preparation inspections shall be entered into the launch base procedure. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.3.4.2c","Requirement","ECSS-Q-ST-40_0440272",1,"Created","The closeout shall be given by the approved launch authority procedure."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.3.4.2d","Requirement","ECSS-Q-ST-40_0440273",1,"Created","Late access procedures shall be the subject of training and be performed by qualified personnel. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.3.4.2e","Requirement","ECSS-Q-ST-40_0440274",1,"Created","Training for flight crew and mission operation teams shall be performed, including specific safety briefing, training and mission simulation. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.3.4.2f","Requirement","ECSS-Q-ST-40_0440275",1,"Created","Close-out shall be by safety-approved procedure, documented training session and simulations."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.3.4.3a","Requirement","ECSS-Q-ST-40_0440276",1,"Created","Inflight inspections shall be entered into flight procedures and operation manuals."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.3.5a","Requirement","ECSS-Q-ST-40_0440277",1,"Created","The supplier shall select, and propose to the safety approval authority, the safety verification methods to be used in conformance to the applicable safety requirements."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.3.5b","Requirement","ECSS-Q-ST-40_0440278",1,"Created","The results of safety verification shall be submitted for approval to the relevant safety approval authority."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.4.1a","Requirement","ECSS-Q-ST-40_0440279",1,"Created","Safety-critical functions shall be verified by testing which include application of the operating procedures, the “man-in-the-loop”, and the verification of the effectiveness of applicable failure tolerance requirements."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.4.1b","Requirement","ECSS-Q-ST-40_0440280",1,"Created","The tests shall include the demonstration of nominal, contingency and emergency operational modes."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.4.2a","Requirement","ECSS-Q-ST-40_0440281",1,"Created","The safety-critical characteristics of all safety-critical functions shall be qualified by test."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.4.2b","Requirement","ECSS-Q-ST-40_0440282",1,"Created","Safety-critical function qualification testing shall include the determination of performance margins considering worst case combinations of induced and natural environments and operating conditions. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.4.2c","Requirement","ECSS-Q-ST-40_0440283",1,"Created","Qualification “by similarity” shall not be applied except after customer approval on a case-by-case basis. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.4.3a","Requirement","ECSS-Q-ST-40_0440284",1,"Created","Induced failure tests shall be performed when required by safety analysis for evaluating failure effects, and for demonstrating failure tolerance conformance in safety-critical functions. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.4.4a","Requirement","ECSS-Q-ST-40_0440285",1,"Created","Verification of unique safety required design or operational characteristics shall form part of the development, qualification or acceptance testing programmes as appropriate. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.4.5a","Requirement","ECSS-Q-ST-40_0440286",1,"Created","Where full-scale testing is not performed, equivalent safety verification method based on technically representative hardware or models shall be justified, approved and performed. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.4.5b","Requirement","ECSS-Q-ST-40_0440287",1,"Created","For the verification of hazard controls in catastrophic hazards where non-flight equipment replaces part of the flight equipment to test a flight function the verification shall be performed independently by a third party which was not involved in the design and qualification of the flight model (FM)."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.5.1a","Requirement","ECSS-Q-ST-40_0440288",1,"Created","A safety verification tracking log (SVTL) shall be established, in conformance with the DRD in Annex C, to collect all the open verification items of the different hazard reports from the safety analysis."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.5.1b","Requirement","ECSS-Q-ST-40_0440289",1,"Created","In time for acceptance by the customer, and in preparation of transfer to the next stage of system integration, the safety manager shall verify that: \n    1. hazard close-outs performed so far by the responsible engineer are still valid; \n    2. the verifications reflect the as-built or as-modified status of the hardware;\n    3. all open verifications at this time are acceptable for transfer to the next stage of system integration; \n    4. all open verifications are entered into the verification tracking log (SVTL);\n    5. the verification tracking log is maintained to reflect the current status."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.5.1c","Requirement","ECSS-Q-ST-40_0440290",1,"Created","If the safety verification constrains any ground operations, the safety manager shall give notification to the safety review panel."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.5.2a","Requirement","ECSS-Q-ST-40_0440291",1,"Created","The safety manager shall assure that each hazard considered for closure has the approval by the safety approval authority, verifying that\n    1. hazards not eliminated are controlled in accordance with the applicable requirements and associated verification activities are successfully completed, or, when applicable,\n    2. deviations from, or waivers of requirements, are granted by the safety approval authority."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","8.6a","Requirement","ECSS-Q-ST-40_0440292",1,"Created","All ground equipment that falls into the scope of an applicable ‘New Approach directive’ shall be ‘CE’ marked and supplied with a supporting ‘Declaration of Conformity’ and User Manual detailing all safety warnings.\"\n    NOTE Additional information is provided in Informative Annex G. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","B.2.1<1>a","Requirement","ECSS-Q-ST-40_0440293",1,"Created","The safety programme plan shall include a description of the project safety organization, responsibilities, and its working relationship and interfaces with product assurance disciplines (reliability, maintainability, software product assurance, parts, materials and processes and quality assurance according to ECSS-Q-ST-10, -20, -30, -60, -70 and -80), with configuration management according to ECSS-M-ST-40, system engineering according to ECSS-E-ST-10, design and other project functions and departments of organizations."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","B.2.1<1>b","Requirement","ECSS-Q-ST-40_0440294",1,"Created","The safety programme plan shall describe how the provisions of ECSS-Q-ST-40 are implemented:\n    1. Safety programme and organization;\n    2. Safety engineering;\n    3. Safety analysis requirements and techniques;\n    4. Safety verification;\n    5. Operational safety."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","B.2.1<2>a","Requirement","ECSS-Q-ST-40_0440295",1,"Created","The plan shall show how the project safety organization implements concurrent safety and project engineering activities in continuous support of the project design and development process."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","B.2.1<3>a","Requirement","ECSS-Q-ST-40_0440296",1,"Created","The plan shall describe how safety-related activities and requirements are defined for and controlled at suppliers’ and lower tier suppliers’ premises."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","B.2.1<4>a","Requirement","ECSS-Q-ST-40_0440297",1,"Created","The plan shall make provisions for assuring conformance to safety requirements and regulations that are applicable to any other facilities and service that are utilized during the course of the project. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","B.2.2a","Permission","ECSS-Q-ST-40_0440321",1,"Created","The safety programme plan may be incorporated within the Product Assurance Plan when agreed between the relevant parties."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","C.2.1<1>a","Requirement","ECSS-Q-ST-40_0440299",1,"Created","The SVTL shall identify the following general information:\n    1. name of the project for which it has been established;\n    2. project documentation identification number;\n    3. applicability for flight or ground safety verifications;\n    4. indication of the specific page number followed by the total number of pages;\n    5. name of the equipment, payload or experiment for which the SVTL has been established;\n    6. mission or flight to which the equipment, payload or experiment has been manifested;\n    7. dates of issue and update."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","C.2.1<2>a","Requirement","ECSS-Q-ST-40_0440300",1,"Created","For each verification item to be tracked a unique identifier shall be used."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","C.2.1<2>b","Requirement","ECSS-Q-ST-40_0440301",1,"Created","The SVTL shall use the designations assigned by the safety manager."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","C.2.1<3>a","Requirement","ECSS-Q-ST-40_0440302",1,"Created","The identification number of the hazard report containing the verification item shall be indicated."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","C.2.1<4>a","Requirement","ECSS-Q-ST-40_0440303",1,"Created","The verification method or the verification means shall be transferred from the hazard report including the procedures by number and title."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","C.2.1<5>a","Requirement","ECSS-Q-ST-40_0440304",1,"Created","The input of “yes” or “no” shall indicate whether this safety verification constrains any ground operations."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","C.2.1<5>b","Requirement","ECSS-Q-ST-40_0440305",1,"Created","If “yes” for flight tracking log: an attachment shall be provided that identifies which ground operation is constrained."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","C.2.1<5>c","Requirement","ECSS-Q-ST-40_0440306",1,"Created","If “yes” for ground tracking log: the ground operation constrained by this verification shall be indicated specifically in the user manual and included as a step in a procedure."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","C.2.1<6>a","Requirement","ECSS-Q-ST-40_0440307",1,"Created","The input of \"yes\" or \"no\" shall indicate whether the verification has to be performed independently (in accordance with 8.4.5b). "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","C.2.1<7>a","Requirement","ECSS-Q-ST-40_0440308",1,"Created","The planned date for the completion of the verification shall be indicated."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","C.2.1<8>a","Requirement","ECSS-Q-ST-40_0440309",1,"Created","The SVTL log shall indicate the title and serial number of the tests, review of designs, inspections and analyses by which this verification is formally closed."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","C.2.1<8>b","Permission","ECSS-Q-ST-40_0440322",1,"Created","Any appropriate information or remarks may be added."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","D.2.1<1>a","Requirement","ECSS-Q-ST-40_0440311",1,"Created","Title - The title of the safety analysis report shall identify the applicable project. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","D.2.1<1>b","Requirement","ECSS-Q-ST-40_0440312",1,"Created","Title page - A title page shall be provided."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","D.2.1<1>c","Requirement","ECSS-Q-ST-40_0440313",1,"Created","Contents - A contents list shall be provided. "]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","D.2.1<1>d","Requirement","ECSS-Q-ST-40_0440314",1,"Created","Foreword - A foreword shall be provided."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","D.2.1<1>e","Requirement","ECSS-Q-ST-40_0440315",1,"Created","Introduction - An introduction shall be provided."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","D.2.1<2>a","Requirement","ECSS-Q-ST-40_0440316",1,"Created","The safety analysis report shall identify the following general information:\n    1. the project documentation identification number, the title of the safety analysis report, date of release and release authority;\n    2. the project phase;\n    3. identification of which organizational entity prepared the document;\n    4. information regarding the approval of the document;\n    5. a statement of effectivity identifying which other documents have been cancelled and replaced in whole or in part."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","D.2.1<2>b","Requirement","ECSS-Q-ST-40_0440317",1,"Created","The safety analysis report shall contain the following analysis specific information:\n    1. objective of safety analysis;\n    2. applicable requirements relevant to the safety analysis;\n    3. description of system design & operation from a safety point of view;\n    4. description of safety analysis process and methods;\n    5. detailed results of safety analysis documented in form of a set of hazard reports (see D.2.1<2>c.);\n    6. list of safety critical functions;\n    7. safety critical item list;\n    8. safety input to risk management;\n    9. support analyses used (e.g. FTA, FMEA/FMECA);\n    10. overall conclusions from safety assessment."]
["ECSS-Q-ST-40C","ECSS - Superseded v1.0","D.2.1<2>c","Requirement","ECSS-Q-ST-40_0440318",1,"Created","Each hazard report shall contain as a minimum the following data:\n    1. title;\n    2. types of hazards and description of their manifestation in the system design and operational configuration and environment;\n    3. identified hazard scenario with description of causes (associated with the hazard manifestation), hazardous events (physical and functional propagation) and consequences; \n    4. consequence severity category;\n    5. propagation time from cause to consequence;\n    6. likelihood of hazard scenario and magnitude of safety risk (optional);\n    7. applicable safety requirements;\n    8. hazard reduction measures (implementation of safety requirements, hazard elimination or minimization and control);\n    9. verification measures;\n    10. safety risk trend after hazard reduction (optional); \n    11. status (safety verification actions open or closed, non-conformances and waivers);\n    12. approval;\n    13. acceptance of safety risk (optional).\n        NOTE Example of formats that can be used for “Hazard and safety risk register”, and “Ranked hazard and safety risk log” are given in the annexes of ECSS-Q-ST-40-02. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.1.2a","Requirement","ECSS-Q-ST-70-26_0130001",1,"Created","The supplier shall provide cleaning services for production facilities of high reliability crimping."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.1.2b","Requirement","ECSS-Q-ST-70-26_0130002",1,"Created","The areas, in which crimping is carried out, shall be maintained in an orderly fashion."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.1.2c","Requirement","ECSS-Q-ST-70-26_0130003",1,"Created","Loose material that can cause contamination of the crimped connection shall be removed. \n    NOTE For example: Dirt, dust, oils and clipped wires."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.1.2d","Requirement","ECSS-Q-ST-70-26_0130004",1,"Created","Furniture shall be kept to a minimum in the work areas and be arranged to allow easy and thorough cleaning of the floor."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.1.2e","Requirement","ECSS-Q-ST-70-26_0130005",1,"Created","Working surfaces shall be covered with an easily cleaned hard top or have a replaceable surface of clean, non-corrosive silicone-free paper."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.1.3a","Requirement","ECSS-Q-ST-70-26_0130006",1,"Created","The crimping area shall have a controlled environment, which limits entry of contamination. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.1.3b","Requirement","ECSS-Q-ST-70-26_0130007",1,"Created","The area shall be continuously controlled as follows:\n    1. room temperature:(22 ± 3) °C;\n    2. relative humidity: (55 ± 10) %."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.1.3c","Requirement","ECSS-Q-ST-70-26_0130008",1,"Created","The workstations shall not be exposed to draughts."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.1.3d","Requirement","ECSS-Q-ST-70-26_0130009",1,"Created","Fresh air shall be supplied to the room through a filtering system with positive pressure difference with regard to adjacent rooms."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.1.3e","Requirement","ECSS-Q-ST-70-26_0130010",1,"Created","The exhaust air shall be suitably restricted."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.1.4a","Requirement","ECSS-Q-ST-70-26_0130011",1,"Created","The supplier shall ensure adequate illumination conditions of the crimp workstations."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.1.4b","Requirement","ECSS-Q-ST-70-26_0130012",1,"Created","The light intensity shall be 1 080 lux on the work surface. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.1.4c","Requirement","ECSS-Q-ST-70-26_0130013",1,"Created","90 % of the work area shall be shadowless and without severe reflections."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.2.1a","Requirement","ECSS-Q-ST-70-26_0130014",1,"Created","The supplier shall provide the tooling necessary for continued high quality crimping."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.2.1b","Requirement","ECSS-Q-ST-70-26_0130015",1,"Created","Tools used shall employ an integral mechanism, which controls the crimping operation in conformance to MIL-DTL-22520G.\n    NOTE The mechanism ensures that, once the operation is started, the tool cannot be opened until the crimping cycle is complete."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.2.1c","Requirement","ECSS-Q-ST-70-26_0130016",1,"Created","Tools shall be marked to show the size and type of termination for which it is calibrated."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.2.1d","Requirement","ECSS-Q-ST-70-26_0130017",1,"Created","Tool calibration shall be verified once each shift in conformance with the clause 5.5.5 requirements."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.2.1e","Requirement","ECSS-Q-ST-70-26_0130018",1,"Created","Proper operation of the integral ratcheting mechanism or the positive stops on pneumatic tools shall be verified as defined in clause 5.5.6."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.2.1f","Requirement","ECSS-Q-ST-70-26_0130019",1,"Created","Before starting a crimping process on a new terminal size and wire type, tools used for crimping of the previous wire type shall be returned to the tool facility."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.2.1g","Requirement","ECSS-Q-ST-70-26_0130020",1,"Created","If the tool settings seals are broken, the tool shall be returned immediately for recalibration."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.2.1h","Requirement","ECSS-Q-ST-70-26_0130021",1,"Created","Tools used in the crimping operation shall be clean; excess lubricants shall be removed before crimping starts."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.2.2a","Requirement","ECSS-Q-ST-70-26_0130022",1,"Created","The supplier shall provide the tooling necessary to avoid damage to the conductor."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.2.2b","Requirement","ECSS-Q-ST-70-26_0130023",1,"Created","The selection of thermal or precision cutting devices, manual or automatic power-driven, shall provide protection of the conductor strands. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.2.2c","Requirement","ECSS-Q-ST-70-26_0130024",1,"Created","Wire stretching by use of mechanical strippers shall be avoided."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.2.2d","Requirement","ECSS-Q-ST-70-26_0130025",1,"Created","The conductor shall not be twisted, ringed, nicked, cut or scored by stripping operation."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.2.2e","Requirement","ECSS-Q-ST-70-26_0130026",1,"Created","Both thermal and mechanical stripping tools shall be calibrated periodically on sample evaluation during a production run."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.2.3a","Requirement","ECSS-Q-ST-70-26_0130027",1,"Created","The supplier shall provide the tooling necessary for precision wire trimming and cutting."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.2.3b","Requirement","ECSS-Q-ST-70-26_0130028",1,"Created","The cutter used for trimming conductor wire shall shear sharply and consistently produce a clean, flat, smooth-cut surface along the entire cutting edge. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.2.3c","Requirement","ECSS-Q-ST-70-26_0130029",1,"Created","Twisting action during cutting operation shall be avoided. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.2.3d","Requirement","ECSS-Q-ST-70-26_0130030",1,"Created","Smooth, long-nose pliers or tweezers shall be used for attaching or removing conductor wire."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.2.3e","Requirement","ECSS-Q-ST-70-26_0130031",1,"Created","The cutting edges of pliers shall be regularly checked for damage and maintained in a sharp condition."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.1.2.4a","Requirement","ECSS-Q-ST-70-26_0130032",1,"Created","The supplier shall provide the equipment specified in Table 5-1 necessary for verification activities specified in clauses 5.4.2 and 5.4.3. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.1a","Requirement","ECSS-Q-ST-70-26_0130033",1,"Created","The supplier shall visually examine wire, terminal and connector contacts for cleanliness, absence of oil films and freedom from tarnish or corrosion before assembly."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.1b","Requirement","ECSS-Q-ST-70-26_0130034",1,"Created","The supplier shall perform cleaning of the work pieces in conformance with ECSS-Q-ST-70-08. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.1c","Requirement","ECSS-Q-ST-70-26_0130035",1,"Created","Further cleaning or other treatment shall not be carried out."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.1d","Requirement","ECSS-Q-ST-70-26_0130036",1,"Created","The supplier shall handle work pieces with clean lint free gloves or finger cots."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.1e","Requirement","ECSS-Q-ST-70-26_0130037",1,"Created","Before a crimping activity, tools at the operator’s station shall be verified to conform to those selected in accordance with the applicable PID."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.1f","Requirement","ECSS-Q-ST-70-26_0130038",1,"Created","All conductor strands shall be inserted cleanly into the barrel without any buckling. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.1g","Requirement","ECSS-Q-ST-70-26_0130039",1,"Created","Strands shall not be left outside or cut back to reduce the conductor diameter to fit an undersized barrel. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.1h","Requirement","ECSS-Q-ST-70-26_0130040",1,"Created","The supplier shall use tools specified in MIL-DTL-22520.\n    NOTE Examples of crimping parameters are given in Table A-2 and Table A-3"]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.1i","Requirement","ECSS-Q-ST-70-26_0130041",1,"Created","The supplier shall take provisions to avoid degradation of the silver plated wire caused by tarnish during storage. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.1j","Requirement","ECSS-Q-ST-70-26_0130042",1,"Created","In cases when the same wire is joined later by soldering, the solder fluxes prescribed in ECSS-Q-ST-70-08 shall be used to avoid degradation.\n    NOTE For shift performance inspection requirements see clause 5.5.5."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.2a","Requirement","ECSS-Q-ST-70-26_0130043",1,"Created","The supplier shall use silver plated copper multi stranded wire and braided shield cable in crimp type connectors. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.2b","Requirement","ECSS-Q-ST-70-26_0130044",1,"Created","Exceptional cases when nickel- or tin-plated wires are used shall be approved by the customer through a request for approval (RFA), in conformance with ECSS-Q-ST-70, clause 5.1.4."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.2c","Requirement","ECSS-Q-ST-70-26_0130045",1,"Created","The supplier shall use high strength copper alloy wire for 24 AWG, 26 AWG and 28 AWG crimped joints.\n    NOTE Soft or annealed copper wire are not acceptable for crimped joints of 24 AWG, 26 AWG and 28 AWG size. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.2d","Requirement","ECSS-Q-ST-70-26_0130046",1,"Created","The supplier shall use space-qualified components having gold plated terminals in conformance with ECSS-Q-ST-60."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.2e","Requirement","ECSS-Q-ST-70-26_0130047",1,"Created","Specific terminals such as ferrules, splices and lugs shall be purchased to MIL or SAE-AS-7928 specifications. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.2f","Requirement","ECSS-Q-ST-70-26_0130048",1,"Created","When gold plating is not available the finish shall be in conformance with ECSS-Q-ST-70-71."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.2g","Requirement","ECSS-Q-ST-70-26_0130049",1,"Created","Cadmium, chromate-coated cadmium and non-fused tin-plating shall not be used."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.3a","Requirement","ECSS-Q-ST-70-26_0130050",1,"Created","The supplier shall perform a review of all the materials, tools and techniques planned to be used to ensure conformance to requirements of this standard and as a means of identifying potential problems.\n    NOTE Type of wire includes number of strands, plating metal, type and thickness of insulation."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.3b","Requirement","ECSS-Q-ST-70-26_0130051",1,"Created","Dies, setting of controls for the length of strip in automatic stripping machines and the selection of specific locators or positioners, shall be selected to meet process requirements.\n    NOTE The requirement is valid for power driven and manual crimping processes as well as for size and tolerance for crimping tools"]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.3c","Requirement","ECSS-Q-ST-70-26_0130052",1,"Created","The results of the review shall be documented in a PID in conformance with DRD of ECSS-Q-ST-70-38."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.4a","Requirement","ECSS-Q-ST-70-26_0130053",1,"Created","The supplier shall give preference to the selection of single wire interconnections."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.4b","Requirement","ECSS-Q-ST-70-26_0130054",1,"Created","The supplier shall not use strands of wire doubled backed to increase the conductor diameter."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.4c","Requirement","ECSS-Q-ST-70-26_0130055",1,"Created","The supplier shall use additional stranded wires to increase the cross-sectional area up to a selected barrel size; \n    NOTE The requirement is applied for cases where the insulation is prepared as normal and transparent “shrink-fit insulation” to cover the loose end of the wire to prevent any risk of a short circuit."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.4d","Requirement","ECSS-Q-ST-70-26_0130056",1,"Created","For 28 AWG up to 16 AWG wire sizes, the maximum insulation clearance shall be equal to the outside diameter (over the insulation) of the wire being used. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.4e","Requirement","ECSS-Q-ST-70-26_0130057",1,"Created","The gaps for larger size wires shall not exceed 2 mm.\n    NOTE No minimum gap is specified except that the conductor wire shall be visible to permit inspection."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.4f","Requirement","ECSS-Q-ST-70-26_0130058",1,"Created","Where the terminal or contact is supplied with insulation support, the wire insulation shall enter the support to the extent that no bare wire is exposed. \n    NOTE An example of a typical connector barrel and single wire crimping is shown Figure 5-1."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.5a","Requirement","ECSS-Q-ST-70-26_0130059",1,"Created","Requirements of this clause shall be applied when single wire crimping cannot be used."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.5b","Requirement","ECSS-Q-ST-70-26_0130060",1,"Created","The maximum number of wires in one crimp barrel shall be two."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.5c","Requirement","ECSS-Q-ST-70-26_0130061",1,"Created","The sum of the two nominal conductor sections shall be compatible with the crimp barrel used \n    NOTE 2 ´ 24 AWG is approximately equal to 1 ´ 20 AWG."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.5d","Requirement","ECSS-Q-ST-70-26_0130062",1,"Created","Both conductors shall be of the same material and support the same plating finish.\n    NOTE 1 For example: Both are silver and not a combination of silver and nickel\n    NOTE 2 Before introduction into the barrel wires or conductors can be twisted to obtain a “single” conductor."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.5e","Requirement","ECSS-Q-ST-70-26_0130063",1,"Created","Axial strength measurements shall be performed on the two associated wires and the axial strength shall be 75 % of the sum of the two wires axial strength requirements."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.5f","Requirement","ECSS-Q-ST-70-26_0130064",1,"Created","For separate conductors introduced into the barrel the following shall apply: \n    1. the actual strength measurement is performed on one of the wires (the smaller, if two different sizes are used);\n    2. the axial strength requirement is as quoted in Table 5-3 for the actual size of wire pulled, assuming a barrel size equal to that wire’s gauge.\n        NOTE Examples of crimping parameters are given in Table A-1 and an example of a typical connector barrel and multi-wire crimping is shown in Figure 5-2."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.6a","Requirement","ECSS-Q-ST-70-26_0130065",1,"Created","The shielded wires on coaxial cables shall be braided."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.6b","Requirement","ECSS-Q-ST-70-26_0130066",1,"Created","Axial strength measurements shall be performed only on the shield after removal of the core dielectric."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.6c","Requirement","ECSS-Q-ST-70-26_0130067",1,"Created","Following crimping, the assembly shall be protected by shrink tubing.\n    NOTE Examples of crimping parameters are given in Table A-3 and an example of a typical ferrule shield crimping is shown in Figure 5-3."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.7a","Requirement","ECSS-Q-ST-70-26_0130068",1,"Created","Tools specified by the manufacturer of the terminals shall be used."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.7b","Requirement","ECSS-Q-ST-70-26_0130069",1,"Created","The maximum number of wires shall be ten."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.7c","Requirement","ECSS-Q-ST-70-26_0130070",1,"Created","Seven wires maximum shall be on the same side."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.7d","Requirement","ECSS-Q-ST-70-26_0130071",1,"Created","All conductors shall be of the same material and within a size range of 4 wire gauges on the same side."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.7e","Requirement","ECSS-Q-ST-70-26_0130072",1,"Created","All conductors shall be positioned parallel in the terminal before crimping."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.7f","Requirement","ECSS-Q-ST-70-26_0130073",1,"Created","Axial strength measurements shall be performed on \n    1. all of the grouped wires for groups with equal wire sizes\n    2. on the smallest wire for groups with different wire sizes."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.7g","Requirement","ECSS-Q-ST-70-26_0130074",1,"Created","In the case where opposed wires are tested a specifically designed test fixture shall be used. \n    NOTE A typical test fixture is shown in Figure A-6."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.2.7h","Requirement","ECSS-Q-ST-70-26_0130075",1,"Created","Following crimping, the assembly shall be protected by shrink tubing.\n    NOTE Examples of typical lug and splice wire crimping are shown in Figure 5-4."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.3.1a","Requirement","ECSS-Q-ST-70-26_0130076",1,"Created","Requirement of this clause shall be applied to crimp configurations that are not specified in clauses 5.2.4 to 5.2.7"]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.3.1b","Requirement","ECSS-Q-ST-70-26_0130077",1,"Created","The supplier shall document the data of successful process qualification in the PID format to ensure continued high quality of production performance."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.3.1c","Requirement","ECSS-Q-ST-70-26_0130078",1,"Created","An approved PID and additional relevant data from a previous project shall be presented to substantiate a RFA."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.3.2a","Requirement","ECSS-Q-ST-70-26_0130079",1,"Created","The supplier shall perform tensile strength and voltage drop tests on samples prepared at a number of tool settings, in conformance with the methods defined in clause 5.4 and in conformance with the following process:\n    1. Ten samples prepared at the point specified by the crimping tool manufacturer as a starting point for calibrating tools and pulled (in conformance with Table A-1, Table A-2 and Table A-3).\n    2. The tool indenter opening is then adjusted in convenient increments above and below this point, and ten samples pulled at each increment. \n    3. Voltage drop tests are then performed on five samples for each tool setting.\n    4. A plot is made with increments being close enough together to obtain a smooth curve.\n    5. The minimum in voltage drop and maximum in tensile strength is then determined and evaluated as per Table 5-2 and Table 5-3.\n    6. The design value or operating point should lie approximately in the middle of the flat top portion of the tensile-strength plot, as per Figure 5-5"]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.3.2b","Requirement","ECSS-Q-ST-70-26_0130080",1,"Created","The supplier shall validate satisfactory results achieved from the final tool setting at the operating point in conformance with the methods defined in clause 5.4 and according to the following process: \n    1. Tensile strength tests are performed on five samples corresponding to the operating point.\n    2. Voltage drop tests are performed on five samples corresponding to the operating point.\n    3. Metallographic tests are performed on a minimum of three of these samples corresponding to the operating point.\n    4. Not tested samples are retained for reference.\n        NOTE This approach is conducted from the variation of the main parameter involved to the relevant terminal crimping.\n            a. Connector barrel crimping: selector setting;\n            b. Ferrule crimping: die selection;\n            c. Lug and splice crimping: total cross-section of stranded wires."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.3.2c","Requirement","ECSS-Q-ST-70-26_0130081",1,"Created","Test data shall be recorded for PID justification."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.3.3a","Requirement","ECSS-Q-ST-70-26_0130082",1,"Created","The supplier shall seal and mark calibrated tools in conformance with clause 5.5.6.3 requirements."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.4.1a","Requirement","ECSS-Q-ST-70-26_0130083",1,"Created","The supplier shall submit samples to the tests detailed below. \n    NOTE The number of samples is dependent on the specific process requirement (in conformance with clauses 5.3.2 , 5.5.5 and 5.5.6.2 requirements). "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.4.1b","Requirement","ECSS-Q-ST-70-26_0130084",1,"Created","Test samples shall meet the requirements of clause 5.5.4.1. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.4.1c","Requirement","ECSS-Q-ST-70-26_0130085",1,"Created","Records of all results shall be tabulated in conformance with 5.5.7. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.4.2a","Requirement","ECSS-Q-ST-70-26_0130086",1,"Created","The supplier shall measure the voltage drop from a point on the positioning shoulder of the contact to another point 14 mm distant on the attached wire (in conformance with the Table 5-2). "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.4.2b","Requirement","ECSS-Q-ST-70-26_0130087",1,"Created","In cases of two or more wires being crimped in the same contact, lug or splice, the voltage drop measurement shall be performed on each wire. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.4.2c","Requirement","ECSS-Q-ST-70-26_0130088",1,"Created","The voltage drop of the contact crimp joint shall not exceed the value specified in Table 5-2 for each wire tested."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.4.3.1a","Requirement","ECSS-Q-ST-70-26_0130089",1,"Created","The supplier shall use a tensile testing device with characteristics in conformance with Table 5-1. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.4.3.1b","Requirement","ECSS-Q-ST-70-26_0130090",1,"Created","The connections shall be loaded until failure occurs. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.4.3.1c","Requirement","ECSS-Q-ST-70-26_0130091",1,"Created","The value at failure shall be recorded, together with the information as to whether the failure was “pull-out”, “broke in crimp” or “break in wire”. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.4.3.1d","Requirement","ECSS-Q-ST-70-26_0130092",1,"Created","The required ultimate axial strengths for compacted and dispersive crimped joints shall be as shown in Table 5-3 and in clauses 5.4.3.2 and 5.4.3.3.\n    NOTE 1 The insulation may be stripped approximately 2 cm on test specimens to promote visual inspection of the mode of failure in the tensile test.\n    NOTE 2 The required ultimate axial strength values for crimped copper alloy wire are calculated based on the requirement of a minimum wire strength of 343 N/mm\n    NOTE 3 A typical test fixture for testing lug and splice crimps is shown in Figure A-6"]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.4.3.2a","Requirement","ECSS-Q-ST-70-26_0130093",1,"Created","The required axial strength shall be 75 % of the wire strength."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.4.3.2b","Requirement","ECSS-Q-ST-70-26_0130094",1,"Created","Axial strength for copper and copper-alloy wires having either silver-, tin- or nickel-plated finishes shall be as specified in Table 5-3."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.4.3.3a","Requirement","ECSS-Q-ST-70-26_0130095",1,"Created","The required axial strength shall be:\n    1. 70 % of the shield strength,\n    2. 70 % of one of the smallest gauge wires within the connection if pulled individually, or\n    3. 70 % of the sum of all the wires axial strength requirements if all wires are pulled together."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.4.4a","Requirement","ECSS-Q-ST-70-26_0130096",1,"Created","The supplier shall employ a certified laboratory to perform the metallographic tests described below."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.4.4b","Requirement","ECSS-Q-ST-70-26_0130097",1,"Created","The customer shall approve the certification status of the laboratory."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.4.4c","Requirement","ECSS-Q-ST-70-26_0130098",1,"Created","The joint to be sectioned shall be mounted in a low exotherm resin capable of being moulded without the application of external pressure. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.4.4d","Requirement","ECSS-Q-ST-70-26_0130099",1,"Created","The joint shall be oriented that the wire is perpendicular to the polishing surface. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.4.4e","Requirement","ECSS-Q-ST-70-26_0130100",1,"Created","The specimen shall be ground with the aid of appropriate grades of silicon carbide papers, in order to expose the mid-section of the joint. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.4.4f","Requirement","ECSS-Q-ST-70-26_0130101",1,"Created","This section shall then be polished with successively finer grades of diamond paste down to 1 µm. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.4.4g","Requirement","ECSS-Q-ST-70-26_0130102",1,"Created","To aid microscopic examination, the polished section shall be very lightly etched with an accepted chemical reagent specific to the composition of the materials being crimped."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.4.4h","Requirement","ECSS-Q-ST-70-26_0130103",1,"Created","The section shall be examined in both as-polished and etched states using a metallographic microscope at a magnification up to ´400."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.4.4i","Requirement","ECSS-Q-ST-70-26_0130104",1,"Created","The following acceptance criteria shall be met:\n    1. Each micro section is free from contamination;\n    2. The crimp barrel is evenly deformed;\n    3. Voids occupy less than 10 % of the cross sectioned area of the wire volume;\n    4. The wires and barrel appear as a gas-tight joint and conform to the workmanship sample prepared during qualification;\n    5. All wires are deformed from their circular cross section;\n    6. There are no indentations or fracturing of the deformed receptacle barrel or its plated finish.\n        NOTE 1 For ferrule shield crimping the requirements of 5.4.4i.3. and 5. are not applicable.\n        NOTE 2 For wire barrel contact size 20 - 18 the requirement 5.4.4i.3. is not applicable due to localized voiding at the crimp corners."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.1a","Requirement","ECSS-Q-ST-70-26_0130105",1,"Created","The supplier shall install a Quality Assurance (QA) function in conformance with the requirements as defined in ECSS-Q-ST-20. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.1b","Requirement","ECSS-Q-ST-70-26_0130106",1,"Created","The quality control process shall be as specified in Figure 5-7."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.2.1a","Requirement","ECSS-Q-ST-70-26_0130107",1,"Created","The supplier shall employ trained and competent personnel for all crimping operations. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.2.1b","Requirement","ECSS-Q-ST-70-26_0130108",1,"Created","The supplier shall develop, maintain and implement a training programme, in conformance with ECSS-Q-ST-20. \n    NOTE The aim of the training programme is to provide for excellence of workmanship and personnel skills, careful and safe operations, and improvement of the quality of crimped joints."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.2.2a","Requirement","ECSS-Q-ST-70-26_0130109",1,"Created","Trained personnel, performing crimping operations, shall be certified according to a customer approved process "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.2.2b","Requirement","ECSS-Q-ST-70-26_0130110",1,"Created","The certification of personnel shall be based upon objective evidence of crimp quality, resulting from test and inspection of the crimped joints. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.2.2c","Requirement","ECSS-Q-ST-70-26_0130111",1,"Created","Operators or inspectors shall be re-certified in cases of repeatedly unacceptable quality levels and changes in crimping techniques, parameters or required skills."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.2.2d","Requirement","ECSS-Q-ST-70-26_0130112",1,"Created","The supplier shall perform training and certification at a school authorized by the customer."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.2.3a","Requirement","ECSS-Q-ST-70-26_0130113",1,"Created","The supplier shall maintain records of the training and certification status of crimping operators and inspection personnel."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.3a","Requirement","ECSS-Q-ST-70-26_0130114",1,"Created","The supplier shall prepare standards consisting of satisfactory work samples (in conformance with the Figure 5-8 and Figure 5-9)"]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.3b","Requirement","ECSS-Q-ST-70-26_0130115",1,"Created","The supplier shall have readily available visual aids, which clearly illustrate the quality characteristics of all crimped connections utilized. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.3c","Requirement","ECSS-Q-ST-70-26_0130116",1,"Created","Defects such as those listed in clause 5.5.4.2 and shown in Figure 5-8 shall be included as examples."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.3d","Requirement","ECSS-Q-ST-70-26_0130117",1,"Created","The operator shall discard production crimps which in his judgement are defective."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.3e","Requirement","ECSS-Q-ST-70-26_0130118",1,"Created","Defective test samples shall not be discarded."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.4.1a","Requirement","ECSS-Q-ST-70-26_0130119",1,"Created","The operator shall examine the wire for nicks, rings, broken strands, untwisted lay or not-removed insulation in the area of the crimp before the stripped wire is inserted into the contact or terminal barrel. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.4.1b","Requirement","ECSS-Q-ST-70-26_0130120",1,"Created","Damaged wires where the base material is exposed shall not be used. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.4.1c","Requirement","ECSS-Q-ST-70-26_0130121",1,"Created","Contacts and terminal barrels that show evidence of the presence of tarnish, corrosion or physical damage, including bent contacts, shall not be used."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.4.1d","Requirement","ECSS-Q-ST-70-26_0130122",1,"Created","Inspection shall verify that wire size and type, the contact and terminal are as specified in the drawing or control document."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.4.2a","Requirement","ECSS-Q-ST-70-26_0130123",1,"Created","The QA inspector shall carry out inspection with the aid of a binocular microscope having an initial linear magnification of ´7. \n    NOTE Further examination of surface characteristics can be performed at higher magnifications. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.4.2b","Requirement","ECSS-Q-ST-70-26_0130124",1,"Created","The inspector shall not physically disturb parts and conductor leads to aid inspection. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.4.2c","Requirement","ECSS-Q-ST-70-26_0130125",1,"Created","The following acceptance criteria shall be met; \n    1. Insulation is not damaged by the crimping tool or the terminal;\n    2. The conductor is visible in the inspection hole when an inspection hole is provided;\n    3. The crimp barrel has no unintentional sharp edges, peeled metal, burrs, cracked platings or cuts after crimping;\n    4. All functional parts, including all retention clips or locking devices, are operational after the crimp has been made;\n    5. No tarnished or corroded contacts are present;\n    6. No misplaced crimps, as determined by marks found on areas not designed to take crimping, are present;\n    7. No undercrimps or overcrimps are present;\n        NOTE An undercrimp is detected by a loose conductor and an overcrimp by broken strands or deformed wire at end of terminal.\n    8. If undercrimps or overcrimps are detected this is cause to stop \n        · operations at that station, \n        · reject all production crimps made since the last verification or pull test, \n        · investigate tool, wire and terminals for the cause of failure.\n    9. No bent contacts are present."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.4.2d","Requirement","ECSS-Q-ST-70-26_0130126",1,"Created","Failure to meet the acceptance criteria of 5.5.4.2c shall be cause for rejection."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.5a","Requirement","ECSS-Q-ST-70-26_0130127",1,"Created","Each operator shall prepare four samples at the beginning of a shift or before a series of crimping operations."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.5b","Requirement","ECSS-Q-ST-70-26_0130128",1,"Created","At the end of the operation four further samples shall be crimped. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.5c","Requirement","ECSS-Q-ST-70-26_0130129",1,"Created","Alternatively the supplier shall keep a logbook for each tool. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.5d","Requirement","ECSS-Q-ST-70-26_0130130",1,"Created","The logbook shall show the quantity of parts crimped since each calibration and since each go/no-go operation. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.5e","Requirement","ECSS-Q-ST-70-26_0130131",1,"Created","Four samples shall be crimped after each 100 crimping operations have been performed."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.5f","Requirement","ECSS-Q-ST-70-26_0130132",1,"Created","A tool shall be changed whenever a wire size or contact size is changed. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.5g","Requirement","ECSS-Q-ST-70-26_0130133",1,"Created","The operator shall prepare four samples at the start of the operation after such a change.\n    NOTE This can be omitted if samples have already been prepared by the tool during the shift."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.5h","Requirement","ECSS-Q-ST-70-26_0130134",1,"Created","In each case, the operator shall submit three samples to the tensile strength test detailed in clause 5.4.3. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.5i","Requirement","ECSS-Q-ST-70-26_0130135",1,"Created","The fourth sample shall be retained for reference and traceability purposes (in conformance with clause 5.5.6.2 requirements)."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.5j","Requirement","ECSS-Q-ST-70-26_0130136",1,"Created","The supplier shall perform an analysis of shift performance test results, in comparison with initial tool calibration results, to determine any drift in tool performance."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.6.1a","Requirement","ECSS-Q-ST-70-26_0130137",1,"Created","The QA organization of the supplier shall ensure that each crimping tool and piece of measuring equipment is calibrated as indicated in the subsequent sub clauses. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.6.1b","Requirement","ECSS-Q-ST-70-26_0130138",1,"Created","The QA organization of the supplier shall record any suspected and actual equipment failure as a project nonconformance report \n    NOTE Based on past nonconformance reports previous results can be examined to ascertain whether or not re-inspection or retesting is required. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.6.1c","Requirement","ECSS-Q-ST-70-26_0130139",1,"Created","The QA organization of the supplier shall notify the customer of the nonconformance details."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.6.1d","Requirement","ECSS-Q-ST-70-26_0130140",1,"Created","The supplier’s calibration procedure shall include the requirements specified in this clause for tool calibration."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.6.2a","Requirement","ECSS-Q-ST-70-26_0130141",1,"Created","The QA organization of the supplier shall ensure that crimping tools, both manual and powered, are calibrated when initially set up for each specific wire size, connection size and type prior to first use. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.6.2b","Requirement","ECSS-Q-ST-70-26_0130142",1,"Created","Calibration shall be verified in conformance with the following check-list:\n    1. cleanliness control of the active part of the tool (e.g. indenters);\n    2. set up with the aid of the “go/no-go” gauge in conformance with specified conditions;\n    3. tests in conformance with the clause 5.4 requirements on not less than four samples."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.6.2c","Requirement","ECSS-Q-ST-70-26_0130143",1,"Created","After satisfactory calibration the tool status shall be documented in a “tool calibration sheet” to ensure tool traceability."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.6.2d","Requirement","ECSS-Q-ST-70-26_0130144",1,"Created","This traceability shall be established by periodic analysis of the corresponding data from the shift performance inspection and tests (in conformance with clause 5.5.5 requirements), \n    NOTE The frequency of analysis is defined in relation to production activity such as six months or 2 500 crimping operations."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.6.2e","Requirement","ECSS-Q-ST-70-26_0130145",1,"Created","A significant drift in test results shall result in tool rejection.\n    NOTE Such a tool is generally labelled \"out-of-calibration tool\" (in conformance with clause 5.5.6.4 requirements)."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.6.3a","Requirement","ECSS-Q-ST-70-26_0130146",1,"Created","The supplier shall provide sealing for calibrated crimping tools to ensure against unauthorized alteration of adjustment settings. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.6.3b","Requirement","ECSS-Q-ST-70-26_0130147",1,"Created","A wire and lead seal method shall be used if the tool has provisions for it; "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.6.3c","Requirement","ECSS-Q-ST-70-26_0130148",1,"Created","Alternatively, the tool shall be sealed by a non-reusable decal seal, which, if the calibrated setting is altered, is visibly damaged. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.6.3d","Requirement","ECSS-Q-ST-70-26_0130149",1,"Created","Seals shall be placed on all external adjustment points of the tool."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.6.4a","Requirement","ECSS-Q-ST-70-26_0130150",1,"Created","Tools that are out of calibration shall be returned to the tool facility for readjustment and calibration. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.6.4b","Requirement","ECSS-Q-ST-70-26_0130151",1,"Created","Tools that are worn or damaged shall be identified as rejected and removed from the fabrication area."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.7a","Requirement","ECSS-Q-ST-70-26_0130152",1,"Created","The supplier shall maintain traceability throughout the process from incoming inspection to final test, including details of test equipment, tools and personnel employed in performing the task."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.7b","Requirement","ECSS-Q-ST-70-26_0130153",1,"Created","Quality records and logbooks shall be retained for at least ten years "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.7c","Requirement","ECSS-Q-ST-70-26_0130154",1,"Created","Quality records and logbooks shall contain the following information:\n    1. the as-built and test configuration list (waiver and deviation summary);\n    2. non conformance reports and corrective actions;\n    3. copy of the visual inspection and shift performance test results with reference to the relevant procedure, personnel and tools used;\n    4. records of the training, testing and certification status of crimping operators (in conformance with clause 5.5.3 requirements) and ECSS-Q-ST-70-08."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.8a","Requirement","ECSS-Q-ST-70-26_0130155",1,"Created","The QA organization of the supplier shall disposition any nonconformance which is observed in respect of the process in conformance with the quality assurance requirements, in conformance with ECSS-Q-ST-20-09. "]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.5.8b","Requirement","ECSS-Q-ST-70-26_0130156",1,"Created","Failure of a crimping tool to pass any requirement specified in clause 5.1.2.1 shall require rejection of all crimps made by that tool since it was last tested successfully for acceptance."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.6a","Requirement","ECSS-Q-ST-70-26_0130157",1,"Created","The supplier shall produce documentation for: \n    1. Process identification, PID and RFA,\n    2. Inspection,\n    3. Traceability,\n    4. Testing, both procedures and records,\n    5. Logbooks, and\n    6. Calibration."]
["ECSS-Q-ST-70-26C","ECSS - Superseded v1.0","5.6b","Requirement","ECSS-Q-ST-70-26_0130158",1,"Created","The format of the documents shall be in accordance with the deliverables item list defined in the business agreement.\n    NOTE No specific DRD requirements emerge from this Standard."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.1.1a","Requirement","ECSS-Q-ST-80_0720001",1,"Created","The supplier shall ensure that an organizational structure is defined for software development, and that individuals have defined tasks and responsibilities."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.1.2.1a","Requirement","ECSS-Q-ST-80_0720002",1,"Created","The responsibility, the authority and the interrelation of personnel who manage, perform and verify work affecting software quality shall be defined and documented.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; SRR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.1.2.2a","Requirement","ECSS-Q-ST-80_0720003",1,"Created","The responsibilities and the interfaces of each organisation, either external or internal, involved in a project shall be defined and documented.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; SRR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.1.2.3a","Requirement","ECSS-Q-ST-80_0720004",1,"Created","The delegation of software product assurance tasks by a supplier to a lower level supplier shall be done in a documented and controlled way, with the supplier retaining the responsibility towards the customer.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; SRR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.1.3.1a","Requirement","ECSS-Q-ST-80_0720005",1,"Created","The supplier shall provide adequate resources to perform the required software product assurance tasks.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; SRR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.1.3.2a","Requirement","ECSS-Q-ST-80_0720006",1,"Created","Reviews and audits of processes and of products shall be carried out by personnel not directly involved in the work being performed."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.1.4.1a","Requirement","ECSS-Q-ST-80_0720007",1,"Created","The supplier shall identify the personnel responsible for software product assurance for the project (SW PA manager/engineer).\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; SRR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.1.4.2a","Requirement","ECSS-Q-ST-80_0720008",1,"Created","The software product assurance manager/engineer shall\n    1. report to the project manager (through the project product assurance manager, if any);\n    2. have organisational authority and independence to propose and maintain a software product assurance programme in accordance with the project software product assurance requirements;\n    3. have unimpeded access to higher management as necessary to fulfil his/her duties."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.1.5.1a","Requirement","ECSS-Q-ST-80_0720009",1,"Created","The supplier shall review the project requirements to establish and make timely provision for acquiring or developing the resources and skills for the management and technical staff.\n","EXPECTED OUTPUT: Training plan [MGT, -; SRR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.1.5.2a","Requirement","ECSS-Q-ST-80_0720010",1,"Created","The supplier shall maintain training records.\n","EXPECTED OUTPUT: Records of training and experience [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.1.5.3a","Requirement","ECSS-Q-ST-80_0720011",1,"Created","The supplier shall ensure that the right composition and categories of appropriately trained personnel are available for the planned activities and tasks in a timely manner."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.1.5.4a","Requirement","ECSS-Q-ST-80_0720012",1,"Created","The supplier shall determine the training subjects based on the specific tools, techniques, methodologies and computer resources to be used in the development and management of the software product. \n    NOTE Personnel can undergo training to acquire skills and knowledge relevant to the specific field with which the software is to deal."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.2.1.1a","Requirement","ECSS-Q-ST-80_0720013",1,"Created","The supplier shall develop a software product assurance plan in response to the software product assurance requirements in conformance with DRD in annex B."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.2.1.1b","Requirement","ECSS-Q-ST-80_0720014",1,"Created","The software product assurance plan shall be either a standalone document or a section of the supplier overall product assurance plan.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.2.1.2a","Requirement","ECSS-Q-ST-80_0720015",1,"Created","Any internal manuals, standards or procedures referred to by the software product assurance plan shall become an integral part of the supplier’s software product assurance programme."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.2.1.3a","Requirement","ECSS-Q-ST-80_0720016",1,"Created","The software product assurance plan shall be revisited and updated as needed at each milestone to ensure that the activities to be undertaken in the following phase are fully defined.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.2.1.4a","Requirement","ECSS-Q-ST-80_0720017",1,"Created","Before acceptance review, the supplier shall either supplement the software product assurance plan to specify the quality measures related to the operations and maintenance processes, or issue a specific software product assurance plan. \n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; AR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.2.1.5a","Requirement","ECSS-Q-ST-80_0720018",1,"Created","The supplier shall provide with the software product assurance plan a compliance matrix documenting conformance with the individual software product assurance requirements applicable for the project or business agreement.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.2.1.5b","Requirement","ECSS-Q-ST-80_0720019",1,"Created","For each software product assurance requirement, the compliance matrix shall provide a reference to the document where the expected output of that requirement is located.\n    NOTE For compliance with the required DRDs a general statement of compliance is acceptable.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.2.2.1a","Requirement","ECSS-Q-ST-80_0720020",1,"Created","The supplier shall report on a regular basis on the status of the software product assurance programme implementation, if appropriate as part of the overall product assurance reporting of the project.\n","EXPECTED OUTPUT: Software product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.2.2.2a","Requirement","ECSS-Q-ST-80_0720021",1,"Created","The software product assurance report shall include:\n    1. an assessment of the current quality of the product and processes, based on measured properties, with reference to the metrication as defined in the software product assurance plan;\n    2. verifications undertaken;\n    3. problems detected;\n    4. problems resolved. \n","EXPECTED OUTPUT: Software product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.2.2.3a","Requirement","ECSS-Q-ST-80_0720022",1,"Created","The supplier shall deliver at each milestone review a software product assurance milestone report, covering the software product assurance activities performed during the past project phases.\n","EXPECTED OUTPUT: Software product assurance milestone report [PAF, SPAMR; SRR, PDR, CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.2.3a","Requirement","ECSS-Q-ST-80_0720023",1,"Created","For software audits, ECSS-Q-ST-10 clause 5.2.3 shall apply.\n","EXPECTED OUTPUT: Audit plan and schedule [PAF, -; SRR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.2.4a","Requirement","ECSS-Q-ST-80_0720024",1,"Created","For software alerts, ECSS-Q-ST-10 clause 5.2.9 shall apply.\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Preliminary alert information [PAF, -; -];\n          b.Alert information [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.2.5.1a","Requirement","ECSS-Q-ST-80_0720025",1,"Created","The supplier shall define and implement procedures for the logging, analysis and correction of all software problems encountered during software development.\n","EXPECTED OUTPUT: Software problem reporting procedures [PAF, -; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.2.5.2a","Requirement","ECSS-Q-ST-80_0720026",1,"Created","The software problem report shall contain the following information:\n    1. identification of the software item;\n    2. description of the problem;\n    3. recommended solution;\n    4. final disposition;\n    5. modifications implemented (e.g. documents, code, and tools);\n    6. tests re-executed.\n","EXPECTED OUTPUT: Software problem reporting procedures [PAF, -; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.2.5.3a","Requirement","ECSS-Q-ST-80_0720027",1,"Created","The procedures for software problems shall define the interface with the nonconformance system (i.e. the circumstances under which a problem qualifies as a nonconformance).\n","EXPECTED OUTPUT: Software problem reporting procedures [PAF, -; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.2.5.4a","Requirement","ECSS-Q-ST-80_0720028",1,"Created","The supplier shall ensure the correct application of problem reporting procedures."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.2.6.1a","Requirement","ECSS-Q-ST-80_0720029",1,"Created","For software nonconformance handling, ECSS-Q-ST-10-09 shall apply \n","EXPECTED OUTPUT: The following outputs are expected:\n          a.NCR SW procedure as part of the Software product assurance plan [PAF, SPAP; SRR];\n          b.Nonconformance reports [DJF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.2.6.1b","Requirement","ECSS-Q-ST-80_0720030",1,"Created","When dealing with software nonconformance, the NRB shall include, at least, a representative from the software product assurance and the software engineering organizations.\n","EXPECTED OUTPUT: Identification of SW experts in NRB [MGT, -; SRR]"]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.2.6.2a","Requirement","ECSS-Q-ST-80_0720031",1,"Created","The software product assurance plan shall specify the point in the software life cycle from which the nonconformance procedures apply.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.2.7.1a","Requirement","ECSS-Q-ST-80_0720032",1,"Created","Quality models shall be used to specify the software quality requirements.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.2.7.2a","Requirement","ECSS-Q-ST-80_0720033",1,"Created","The following characteristics shall be used to specify the quality model:\n    1. functionality;\n    2. reliability;\n    3. maintainability;\n    4. reusability;\n    5. suitability for safety;\n    6. security;\n    7. usability;\n    8. efficiency;\n    9. portability;\n    10. software development effectiveness.\n        NOTE 1 Quality models are the basis for the identification of process metrics (see clause 6.2.5) and product metrics (see clause 7.1.4).\n        NOTE 2 quality models are also addressed by ISO/IEC 9126 or ECSS-Q-HB-80-04.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.3.1a","Requirement","ECSS-Q-ST-80_0720034",1,"Created","Risk management for software shall be performed by cross-reference to the project risk policy, as specified in ECSS-M-ST-80."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.3.2.1a","Requirement","ECSS-Q-ST-80_0720035",1,"Created","For critical item control, ECSS-Q-ST-10-04 shall apply."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.3.2.2a","Requirement","ECSS-Q-ST-80_0720036",1,"Created","The supplier shall identify the characteristics of the software items that qualify them for inclusion in the Critical Item List."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.4.1.1a","Requirement","ECSS-Q-ST-80_0720037",1,"Created","For supplier selection ECSS-Q-ST-20 clause 5.4.1 shall apply.\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Results of pre-award audits and assessments [PAF, -; -];\n          b.Records of procurement sources [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.4.1.2a","Requirement","ECSS-Q-ST-80_0720038",1,"Created","For the selection of suppliers of existing software, including software contained in OTS equipments and units, the expected output of clauses 6.2.7.2 to 6.2.7.6 shall be made available.\n","EXPECTED OUTPUT: Software reuse file [DJF, SRF; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.4.2.1a","Requirement","ECSS-Q-ST-80_0720039",1,"Created","The supplier shall establish software product assurance requirements for the next level suppliers, tailored to their role in the project, including a requirement to produce a software product assurance plan.\n","EXPECTED OUTPUT: Software product assurance requirements for suppliers [PAF, -; SRR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.4.2.2a","Requirement","ECSS-Q-ST-80_0720040",1,"Created","The supplier shall provide the software product assurance requirements applicable to the next level suppliers for customer’s acceptance.\n","EXPECTED OUTPUT: Software product assurance requirements for suppliers [PAF, -; SRR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.4.3.1a","Requirement","ECSS-Q-ST-80_0720041",1,"Created","The supplier shall monitor the next lower level suppliers’ conformance to the product assurance requirements. "]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.4.3.2a","Requirement","ECSS-Q-ST-80_0720042",1,"Created","The monitoring process shall include the review and approval of the next lower level suppliers’ product assurance plans, the continuous verification of processes and products, and the monitoring of the final validation of the product."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.4.3.3a","Requirement","ECSS-Q-ST-80_0720043",1,"Created","The supplier shall ensure that software development processes are defined and applied by the next lower level suppliers in conformance with the software product assurance requirements for suppliers.\n","EXPECTED OUTPUT: Next level suppliers’ software product assurance plan [PAF, SPAP; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.4.3.4a","Requirement","ECSS-Q-ST-80_0720044",1,"Created","The supplier shall provide the next lower level suppliers’ software product assurance plan for customer’s acceptance.\n","EXPECTED OUTPUT: Next level suppliers’ software product assurance plan [PAF, SPAP; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.4.4a","Requirement","ECSS-Q-ST-80_0720045",1,"Created","The supplier shall provide the lower level suppliers with the relevant results of the safety and dependability analyses performed at higher and his level (ref. clauses 6.2.2.1 and 6.2.2.2), including:\n    1. the criticality classification of the software products to be developed;\n    2. information about the failures that can be caused at higher level by the software products to be developed.\n","EXPECTED OUTPUT: Safety and dependability analyses results for lower level suppliers [RB, -; SRR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.5.1a","Requirement","ECSS-Q-ST-80_0720046",1,"Created","For procurement documents, ECSS-Q-ST-20 clause 5.4.2 shall apply."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.5.2a","Requirement","ECSS-Q-ST-80_0720047",1,"Created","The choice of procured software shall be described and submitted for customer review.\n","EXPECTED OUTPUT: Software development plan [MGT, SDP; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.5.3a","Requirement","ECSS-Q-ST-80_0720048",1,"Created","For each of the software items the following data shall be provided:\n    1. ordering criteria\n        NOTE For example: versions, options and extensions.\n    2. receiving inspection criteria;\n    3. back-up solutions if the product becomes unavailable;\n    4. contractual arrangements with the supplier for the development, maintenance and upgrades to new releases.\n","EXPECTED OUTPUT: Procurement data [MGT, -; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.5.4a","Requirement","ECSS-Q-ST-80_0720049",1,"Created","All the procured software shall be identified and registered by configuration management."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.5.5a","Requirement","ECSS-Q-ST-80_0720050",1,"Created","The supplier shall subject the procured software to a planned receiving inspection, in accordance with ECSS-Q-ST-20 clause 5.4.4, and the receiving inspection criteria as required by clause 5.5.3.\n","EXPECTED OUTPUT: Receiving inspection report [PAF, -; PDR, CDR, QR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.5.6a","Requirement","ECSS-Q-ST-80_0720051",1,"Created","Exportability constraints shall be identified."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.6.1.1a","Requirement","ECSS-Q-ST-80_0720052",1,"Created","Methods and tools to be used for all the activities of the development cycle, (including requirements analysis, software specification, modelling, design, coding, validation, testing, configuration management, verification and product assurance) shall be identified by the supplier and agreed by the customer.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.6.1.2a","Requirement","ECSS-Q-ST-80_0720053",1,"Created","The choice of development methods and tools shall be justified by demonstrating through testing or documented assessment that:\n    1. the development team has appropriate experience or training to apply them,\n    2. the tools and methods are appropriate for the functional and operational characteristics of the product, and\n    3. the tools are available (in an appropriate hardware environment) throughout the development and maintenance lifetime of the product.\n","EXPECTED OUTPUT: Software product assurance milestone report [PAF, SPAMR; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.6.1.3a","Requirement","ECSS-Q-ST-80_0720054",1,"Created","The correct use of methods and tools shall be verified and reported. \n","EXPECTED OUTPUT: Software product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.6.2.1a","Requirement","ECSS-Q-ST-80_0720055",1,"Created","The software development environment shall be selected according to the following criteria:\n    1. availability;\n    2. compatibility;\n    3. performance;\n    4. maintenance;\n    5. durability and technical consistency with the operational equipment;\n    6. the assessment of the product with respect to requirements, including the criticality category;\n    7. the available support documentation;\n    8. the acceptance and warranty conditions;\n    9. the conditions of installation, preparation, training and use;\n    10. the maintenance conditions, including the possibilities of evolutions;\n    11. copyright and intellectual property rights constraints;\n    12. dependence on one specific supplier.\n","EXPECTED OUTPUT: Software development plan [MGT, SDP; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.6.2.2a","Requirement","ECSS-Q-ST-80_0720056",1,"Created","The suitability of the software development environment shall be justified.\n","EXPECTED OUTPUT: Software development plan [MGT, SDP; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.6.2.3a","Requirement","ECSS-Q-ST-80_0720057",1,"Created","The availability of the software development environment to developers and other users shall be verified before the start of each development phase."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.7.1a","Requirement","ECSS-Q-ST-80_0720058",1,"Created","The supplier shall monitor and control the effectiveness of the processes used during the development of the software, including the relevant processes corresponding to the services called from other organizational entities outside the project team.\n    NOTE The process assessment and improvement performed at organization level can be used to provide evidence of compliance for the project.\n","EXPECTED OUTPUT: Software process assessment records: Overall assessments and improvement programme plan [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.7.2.1a","Requirement","ECSS-Q-ST-80_0720059",1,"Created","The process assessment model and method to be used when performing any software process assessment shall be documented. \n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Software process assessment record: assessment model [PAF, -; -];\n          b.Software process assessment record: assessment method [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.7.2.2a","Requirement","ECSS-Q-ST-80_0720060",1,"Created","Assessments performed and process assessment models used shall be in conformance with ISO/IEC 15504 (Part 2).\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Software process assessment record: evidence of conformance of the process assessment model [PAF, -; -];\n          b.Software process assessment record: assessment method [PAF, -; -]. \n    NOTE 1 The model and method documented in ECSS-Q-HB-80-02 are conformant to ISO/IEC 15504 (Part 2).\n    NOTE 2 Currently the CMMI model is not fully conformant to ISO/IEC 15504, however it can be used, provided that the SCAMPI A method is applied."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.7.2.3a","Requirement","ECSS-Q-ST-80_0720061",1,"Created","The process assessment model, the method, the assessment scope, the results and the assessors shall be verified as complying with the project requirements.\n    NOTE 1 Examples of assessment scopes are: organizational unit evaluated, and processes evaluated.\n    NOTE 2 ECSS-Q-HB-80-02 provides space specific process reference model and their indicators.\n","EXPECTED OUTPUT: Software process assessment record: Software process assessment recognition evidence [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.7.2.4a","Requirement","ECSS-Q-ST-80_0720062",1,"Created","Assessments, carried out in accordance with ECSS-Q-HB-80-02, shall be performed by a competent assessor, whereas the other assessment team members can be either competent assessor or provisional assessor.\n    NOTE 1 For other assessment schemes conformant to ISO/IEC 15504 (Part 2), assessors certified under INTRSA are competent assessors.\n    NOTE 2 When using CMMI/SCAMPI A, SEI authorized lead appraisers are competent assessors.\n","EXPECTED OUTPUT: Software process assessment record: competent assessor justification [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.7.3.1a","Requirement","ECSS-Q-ST-80_0720063",1,"Created","The results of the assessment shall be used as feedback to improve as necessary the performed processes, to recommend changes in the direction of the project, and to determine technology advancement needs."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.7.3.1b","Requirement","ECSS-Q-ST-80_0720064",1,"Created","The suppliers shall ensure that the results of previous assessments are used in its project activity \n","EXPECTED OUTPUT: Software process assessment records: improvement plan [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.7.3.2a","Requirement","ECSS-Q-ST-80_0720065",1,"Created","The process improvement shall be conducted according to a documented process improvement process.\n    NOTE 1 For the definition of the process improvement process, see ECSS-Q-HB-80-02.\n    NOTE 2 For CMMI, the process improvement is described in the OPF (Organizational Process Focus) process area.\n","EXPECTED OUTPUT: Software process assessment records: improvement process [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","5.7.3.3a","Requirement","ECSS-Q-ST-80_0720066",1,"Created","Evidence of the improvement in performed processes or in project documentation shall be provided.\n    NOTE See ECSS-Q-HB-80-02.\n","EXPECTED OUTPUT: Software process assessment records: evidence of improvements [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.1.1a","Requirement","ECSS-Q-ST-80_0720067",1,"Created","The software development life cycle shall be defined or referenced in the software product assurance plan."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.1.1b","Requirement","ECSS-Q-ST-80_0720068",1,"Created","The following characteristics of the software life cycle shall be defined:\n    1. phases;\n    2. input and output of each phase;\n    3. status of completion of phase output;\n    4. milestones;\n    5. dependencies;\n    6. responsibilities;\n    7. role of the customer at each milestone review, in conformance with ECSS-M-ST-10 and ECSS-M-ST-10-01.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.1.2a","Requirement","ECSS-Q-ST-80_0720069",1,"Created","In the definition of the life cycle and associated milestones and documents, the quality objectives shall be used."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.1.3a","Requirement","ECSS-Q-ST-80_0720070",1,"Created","The software life cycle shall be reviewed against the contractual software engineering and product assurance requirements. "]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.1.4a","Requirement","ECSS-Q-ST-80_0720071",1,"Created","The software life cycle shall be reviewed for suitability and for the availability of resources to implement it by all functions involved in its application."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.1.5a","Requirement","ECSS-Q-ST-80_0720072",1,"Created","A milestone (SW TRR as defined in ECSS-E-ST-40 clause 5.3.5.1) shall be scheduled immediately before the software validation process starts, to check that:\n    1. the software status is compatible with the commencement of validation activities;\n    2. the necessary resources, software product assurance plans, test and validation documentation, simulators or other technical means are available and ready for use.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.1.1a","Requirement","ECSS-Q-ST-80_0720073",1,"Created","The following activities shall be covered either in software-specific plans or in project general plans:\n    1. development;\n    2. specification, design and customer documents to be produced;\n    3. configuration and documentation management;\n    4. verification, testing and validation activities;\n    5. maintenance.\n","EXPECTED OUTPUT: Software project plans [MGT, MF, DJF]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.1.2a","Requirement","ECSS-Q-ST-80_0720074",1,"Created","All plans shall be finalized before the start of the related activities.\n","EXPECTED OUTPUT: Software project plans [MGT, MF, DJF]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.1.3a","Requirement","ECSS-Q-ST-80_0720075",1,"Created","All plans shall be updated for each milestone to reflect any changes during development.\n","EXPECTED OUTPUT: Software project plans [MGT, MF, DJF]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.1.4a","Requirement","ECSS-Q-ST-80_0720076",1,"Created","The software product assurance plan shall identify all plans to be produced and used, the relationship between them and the time-scales for their preparation and update.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.1.5a","Requirement","ECSS-Q-ST-80_0720077",1,"Created","Each plan shall be reviewed against the relevant contractual requirements. "]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.1.6a","Requirement","ECSS-Q-ST-80_0720078",1,"Created","Procedures and project standards shall address all types of software products included in the project.\n","EXPECTED OUTPUT: Procedures and standards [PAF, -; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.1.7a","Requirement","ECSS-Q-ST-80_0720079",1,"Created","All procedures and project standards shall be finalized before starting the related activities.\n","EXPECTED OUTPUT: Procedures and standards [PAF, -; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.1.8a","Requirement","ECSS-Q-ST-80_0720080",1,"Created","Each procedure or standard shall be reviewed against the relevant plans and contractual requirements."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.1.9a","Requirement","ECSS-Q-ST-80_0720081",1,"Created","Before any activity is started, each procedure or standard for that activity shall be reviewed by all functions involved in its application, for suitability and for the availability of resources to implement it."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.2.1a","Requirement","ECSS-Q-ST-80_0720082",1,"Created","For the system-level analyses leading to the criticality classification of software products based on the severity of failures consequences, ECSS-Q-ST-40 Table 6-1, and ECSS-Q-ST-30 Table 5-1, shall apply.\n","EXPECTED OUTPUT: Criticality classification of software products [PAF, -; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.2.2a","Requirement","ECSS-Q-ST-80_0720083",1,"Created","The supplier shall perform a software dependability and safety analysis of the software products, in accordance with the requirements of ECSS-Q-ST-30 and ECSS-Q-ST-40 and using the results of system-level safety and dependability analyses, in order to determine the criticality of the individual software components.\n","EXPECTED OUTPUT: Software dependability and safety analysis report [PAF, -; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.2.3a","Requirement","ECSS-Q-ST-80_0720084",1,"Created","The supplier shall identify the methods and techniques for the software dependability and safety analysis to be performed at technical specification and design level."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.2.3b","Requirement","ECSS-Q-ST-80_0720085",1,"Created","Methods and techniques for software dependability and safety analysis shall be agreed between the supplier and customer.\n    NOTE ECSS-Q-HB-80-03 provides indication on methods and techniques that can be applied such as: \n        · software failure modes, effects and criticality analysis (for the performing of this analysis, see also ECSS-Q-ST-30-02);\n        · software fault tree analysis;\n        · software common cause failure analysis.\n","EXPECTED OUTPUT: Criticality classification of software components [PAF, -; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.2.4a","Requirement","ECSS-Q-ST-80_0720086",1,"Created","Based on the results of the software criticality analysis, the supplier shall apply engineering measures to reduce the number of critical software components and mitigate the risks associated with the critical software (ref. clause 6.2.3)."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.2.5a","Requirement","ECSS-Q-ST-80_0720087",1,"Created","The supplier shall report on the status of the implementation and verification of the SW dependability and safety analysis recommendations.\n","EXPECTED OUTPUT: Software dependability and safety analysis report [PAF, -; CDR, QR, AR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.2.6a","Requirement","ECSS-Q-ST-80_0720088",1,"Created","The supplier shall update the software dependability and safety analysis at each software development milestone, to confirm the criticality category of software components.\n","EXPECTED OUTPUT: Software dependability and safety analysis report [PAF, -; CDR, QR, AR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.2.7a","Requirement","ECSS-Q-ST-80_0720089",1,"Created","The supplier shall provide the results of the software dependability and safety analysis for integration into the system-level dependability and safety analyses, addressing in particular:\n    1. additional failure modes identified at software design level;\n    2. recommendations for system-level activities.\n        NOTE For example: introduction of hardware inhibits, and modifications of the system architecture.\n","EXPECTED OUTPUT: Software dependability and safety analysis report [PAF, -; PDR, CDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.2.8a","Requirement","ECSS-Q-ST-80_0720090",1,"Created","As part of the software requirements analysis activities (ref. clause 6.3.2), the supplier shall contribute to the Hardware-Software Interaction Analysis (HSIA) by identifying, for each hardware failure included in the HSIA, the requirements that specify the software behaviour in the event of that hardware failure."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.2.9a","Requirement","ECSS-Q-ST-80_0720091",1,"Created","During the verification and validation of the software requirements resulting from the Hardware-Software Interaction Analysis, the supplier shall verify that the software reacts correctly to hardware failures, and no undesired software malfunctions occur that may lead to system failures."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.3.1a","Requirement","ECSS-Q-ST-80_0720092",1,"Created","The supplier shall define and implement measures to avoid propagation of failures between software components of different criticality.\n    NOTE This can be achieved by design measures such as separate hardware platforms, isolation of software processes or prohibition of shared memory (segregation and partitioning). "]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.3.1b","Requirement","ECSS-Q-ST-80_0720093",1,"Created","Software components whose malfunction may cause failures of higher criticality components shall be classified in accordance with the consequences of those failures.\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Software product assurance plan [PAF, SPAP; PDR, CDR];\n          b.Software dependability and safety analysis report [PAF, -; PDR, CDR, QR, AR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.3.2a","Requirement","ECSS-Q-ST-80_0720094",1,"Created","The supplier shall define, justify and apply measures to assure the dependability and safety of critical software.\n    NOTE These measures can include:\n        · use of software design or methods that have performed successfully in a similar application;\n        · insertion of features for failure isolation and handling (ref. ECSS-Q-HB-80-03, software failure modes, effects and criticality analysis);\n        · defensive programming techniques, such as input verification and consistency checks;\n        · use of a “safe subset” of programming language;\n        · use of formal design language for formal proof;\n        · 100 % code branch coverage at unit testing level;\n        · full inspection of source code;\n        · witnessed or independent testing;\n        · gathering and analysis of failure statistics;\n        · removing deactivated code or showing through a combination of analysis and testing that the means by which such code can be inadvertently executed are prevented, isolated, or eliminated.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; PDR, CDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.3.3a","Requirement","ECSS-Q-ST-80_0720095",1,"Created","The application of the chosen measures to handle the critical software shall be verified.\n","EXPECTED OUTPUT: Software product assurance milestone report [PAF, SPAMR; PDR, CDR, QR, AR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.3.4a","Requirement","ECSS-Q-ST-80_0720096",1,"Created","Critical software shall be subject to regression testing after:\n    1. any change of functionality of the underlying platform hardware;\n        NOTE For example: instruction set of a processor.\n    2. any change of the tools that affect directly or indirectly the generation of the executable code.\n        NOTE In case of minor changes in tools that affect the generation of the executable code, a binary comparison of the executable code generated by the different tools can be used to verify that no modifications are introduced.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; PDR, CDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.3.5a","Requirement","ECSS-Q-ST-80_0720097",1,"Created","The need for additional verification and validation of critical software shall be analysed after:\n    1. any change of functionality or performance of the underlying platform hardware;\n    2. any change in the environment in which the software or the platform hardware operate.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; PDR, CDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.3.6a","Requirement","ECSS-Q-ST-80_0720098",1,"Created","Identified unreachable code shall be removed and the need for re-verification and re-validation shall be analysed. "]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.3.7a","Requirement","ECSS-Q-ST-80_0720099",1,"Created","Unit and integration testing shall be (re-)executed on non-instrumented code."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.3.8a","Requirement","ECSS-Q-ST-80_0720100",1,"Created","Validation testing shall be (re-)executed on non-instrumented code."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.4.1a","Requirement","ECSS-Q-ST-80_0720101",1,"Created","ECSS-M-ST-40 shall be applied for software configuration management, complemented by the following requirements."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.4.2a","Requirement","ECSS-Q-ST-80_0720102",1,"Created","The software configuration management system shall allow any reference version to be re-generated from backups.\n","EXPECTED OUTPUT: Software configuration management plan [MGT, SCMP; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.4.3a","Requirement","ECSS-Q-ST-80_0720103",1,"Created","The software configuration file and the software release document shall be provided with each software delivery.\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Software configuration file [DDF, SCF; -];\n          b.Software release document [DDF, SRelD; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.4.4a","Requirement","ECSS-Q-ST-80_0720104",1,"Created","The software configuration file shall be available and up to date for each project milestone.\n","EXPECTED OUTPUT: Software configuration file [DDF, SCF; CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.4.5a","Requirement","ECSS-Q-ST-80_0720105",1,"Created","Any components of the code generation tool that are customizable by the user shall be put under configuration control."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.4.5b","Requirement","ECSS-Q-ST-80_0720106",1,"Created","The change control procedures defined for the project shall address the specific aspects of these components.\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Software configuration file [DDF, SCF; CDR, QR, AR, ORR];\n          b.Software configuration management plan [MGT, SCMP; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.4.6a","Requirement","ECSS-Q-ST-80_0720107",1,"Created","The supplier shall ensure that all authorized changes are implemented in accordance with the software configuration management plan.\n","EXPECTED OUTPUT: Authorized changes - Software configuration file [DDF, SCF; CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.4.7a","Requirement","ECSS-Q-ST-80_0720108",1,"Created","The following documents shall be controlled (see ECSS-Q-ST-10 clause 5.2.5):\n    1. procedural documents describing the quality system to be applied during the software life cycle;\n    2. planning documents describing the planning and progress of the activities;\n    3. documents describing a particular software product, including:\n        (a) development phase inputs,\n        (b) development phase outputs,\n        (c) verification and validation plans and results,\n        (d) test case specifications, test procedures and test reports,\n        (e) traceability matrices,\n        (f) documentation for the software and system operators and users, and\n        (g) maintenance documentation."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.4.8a","Requirement","ECSS-Q-ST-80_0720109",1,"Created","The supplier shall identify a method and tool to protect the supplied software against corruption.\n    NOTE For example: source, executable and data.\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Software product assurance plan [PAF, SPAP; SRR, PDR]; \n          b.Software configuration file [DDF, SCF; CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.4.9a","Requirement","ECSS-Q-ST-80_0720110",1,"Created","The supplier shall define a checksum-type key calculation for the delivered operational software.\n    NOTE For example: executable binary, database. \n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.4.10a","Requirement","ECSS-Q-ST-80_0720111",1,"Created","The checksum value shall be provided in the software configuration file with each software delivery.\n","EXPECTED OUTPUT: Software configuration file [DDF, SCF; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.4.11a","Requirement","ECSS-Q-ST-80_0720112",1,"Created","The media through which the software is delivered to the customer shall be marked by the supplier indicating the following information as a minimum:\n    1. the software name;\n    2. the version number;\n    3. the reference to the software configuration file.\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Software product assurance plan [PAF, SPAP; SRR, PDR];\n          b.Labels [DDF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.5.1a","Requirement","ECSS-Q-ST-80_0720113",1,"Created","Metrics shall be used to manage the development and to assess the quality of the development processes. \n    NOTE Process metrics are based on quality models (see clause 5.2.7).\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.5.2a","Requirement","ECSS-Q-ST-80_0720114",1,"Created","Process metrics shall be collected, stored and analysed on a regular basis by applying quality models and procedures. \n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.5.3a","Requirement","ECSS-Q-ST-80_0720115",1,"Created","The following basic process metrics shall be used within the supplier’s organization: \n    1. duration: how phases and tasks are being completed versus the planned schedule;\n    2. effort: how much effort is consumed by the various phases and tasks compared to the plan.\n","EXPECTED OUTPUT: Internal metrics report."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.5.4a","Requirement","ECSS-Q-ST-80_0720116",1,"Created","Process metrics shall be used within the supplier’s organization and reported to the customer, including:\n    1. number of problems detected during verification;\n    2. number of problems detected during integration and validation testing and use. \n        NOTE See also software problem reporting described in clause 5.2.5.\n","EXPECTED OUTPUT: Software product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.5.5a","Requirement","ECSS-Q-ST-80_0720117",1,"Created","Metrics reports shall be included in the software product assurance reports.\n","EXPECTED OUTPUT: Software product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.6.1a","Requirement","ECSS-Q-ST-80_0720118",1,"Created","Activities for the verification of the quality requirements shall be specified in the definition of the verification plan. \n    NOTE Verification includes various techniques such as review, inspection, testing, walk-through, cross-reading, desk-checking, model simulation, and many types of analysis such as traceability analysis, formal proof or fault tree analysis. \n","EXPECTED OUTPUT: Software verification plan [DJF, SVerP; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.6.2a","Requirement","ECSS-Q-ST-80_0720119",1,"Created","The outputs of each development activity shall be verified for conformance against pre-defined criteria."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.6.2b","Requirement","ECSS-Q-ST-80_0720120",1,"Created","Only outputs which have been subjected to planned verifications shall be used as inputs for subsequent activities.\n","EXPECTED OUTPUT: Software product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.6.3a","Requirement","ECSS-Q-ST-80_0720121",1,"Created","A summary of the assurance activities concerning the verification process and their findings shall be included in software product assurance reports.\n","EXPECTED OUTPUT: Software product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.6.4a","Requirement","ECSS-Q-ST-80_0720122",1,"Created","The completion of actions related to software problem reports generated during verification shall be verified and recorded.\n","EXPECTED OUTPUT: Software problem reports [DJF, -; SRR, PDR, CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.6.5a","Requirement","ECSS-Q-ST-80_0720123",1,"Created","Software containing deactivated code shall be verified specifically to ensure that the deactivated code cannot be activated or that its accidental activation cannot harm the operation of the system.\n","EXPECTED OUTPUT: Software verification report [DJF, SVR; CDR, QR, AR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.6.6a","Requirement","ECSS-Q-ST-80_0720124",1,"Created","Software containing configurable code shall be verified specifically to ensure that any unintended configuration cannot be activated at run time or included during code generation.\n","EXPECTED OUTPUT: Software verification report [DJF, SVR; CDR, QR, AR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.6.7a","Requirement","ECSS-Q-ST-80_0720125",1,"Created","The supplier shall ensure that:\n    1. the planned verification activities are adequate to confirm that the products of each phase are conformant to the applicable requirements;\n    2. the verification activities are performed according to the plan. \n","EXPECTED OUTPUT: Software product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.6.8a","Requirement","ECSS-Q-ST-80_0720126",1,"Created","Reviews and inspections shall be carried out according to defined criteria, and according to the defined level of independence of the reviewer from the author of the reviewed item. "]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.6.9a","Requirement","ECSS-Q-ST-80_0720127",1,"Created","Each review and inspection shall be based on a written plan or procedure.\n    NOTE For projects reviews, ECSS-E-ST-40 clause 5.3.3.3, bullet b and Annex P are applicable.\n","EXPECTED OUTPUT: Review and inspection plans or procedures [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.6.10a","Requirement","ECSS-Q-ST-80_0720128",1,"Created","The review or inspection plans or procedures shall specify: \n    1. the reviewed or inspected items;\n    2. the person in charge;\n    3. the participants;\n    4. the means of review or inspection (e.g. tools or check list);\n    5. the nature of the report.\n","EXPECTED OUTPUT: Review and inspection plans or procedures [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.6.11a","Requirement","ECSS-Q-ST-80_0720129",1,"Created","Review and inspection reports shall:\n    1. refer to the corresponding review/inspection procedure or plan; \n    2. identify the reviewed item, the author, the reviewer, the review criteria and the findings of the review.\n","EXPECTED OUTPUT: Review and inspection reports [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.6.12a","Requirement","ECSS-Q-ST-80_0720130",1,"Created","Traceability matrices (as defined in ECSS-E-ST-40 clause 5.8) shall be verified at each milestone.\n","EXPECTED OUTPUT: Software product assurance milestone report [PAF, SPAMR; SRR, PDR, CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.6.13a","Requirement","ECSS-Q-ST-80_0720131",1,"Created","Independent software verification shall be performed by a third party."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.6.13b","Requirement","ECSS-Q-ST-80_0720132",1,"Created","Independent software verification shall be a combination of reviews, inspections, analyses, simulations, testing and auditing.\n    NOTE This requirement is applicable where the risks associated with the project justify the costs involved. The customer can consider a less rigorous level of independence, e.g. an independent team in the same organization.\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.ISVV plan [DJF, -; SRR, PDR];\n          b.ISVV report [DJF, -; PDR, CDR, QR, AR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.7.2a","Requirement","ECSS-Q-ST-80_0720133",1,"Created","Analyses of the advantages to be obtained with the selection of existing software (ref. 3.2.11) instead of new development shall be carried out.\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Software reuse approach, including approach to delta qualification [PAF, SPAP; SRR, PDR];\n          b.Software reuse file [DJF, SRF; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.7.3a","Requirement","ECSS-Q-ST-80_0720134",1,"Created","The existing software shall be assessed with regards to the applicable functional, performance and quality requirements.\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Software reuse approach, including approach to delta qualification [PAF, SPAP; SRR, PDR];\n          b.Software reuse file [DJF, SRF; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.7.4a","Requirement","ECSS-Q-ST-80_0720135",1,"Created","The quality level of the existing software shall be analysed with respect to the project requirements, according to the criticality of the system function implemented, taking into account the following aspects:\n    1. software requirements documentation;\n    2. software architectural and detailed design documentation;\n    3. forward and backward traceability between system requirements, software requirements, design and code;\n    4. unit tests documentation and coverage;\n    5. integration tests documentation and coverage;\n    6. validation documentation and coverage;\n    7. verification reports;\n    8. performance;\n        NOTE For example: memory occupation, CPU load.\n    9. operational performances;\n    10. residual nonconformances and waivers;\n    11. user operational documentation;\n        NOTE For example: user manual.\n    12. code quality (adherence to coding standards, metrics).\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Software reuse approach, including approach to delta qualification [PAF, SPAP; SRR, PDR];\n          b.Software reuse file [DJF, SRF; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.7.5a","Requirement","ECSS-Q-ST-80_0720136",1,"Created","The results of the reused software analysis shall be recorded in the software reuse file, together with an assessment of the possible level of reuse and a description of the assumptions and the methods applied when estimating the level of reuse.\n    NOTE Results of the reused software analysis, such as detailed reference to requirement and design documents, test reports and coverage results.\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Software reuse approach, including approach to delta qualification [PAF, SPAP; SRR, PDR];\n          b.Software reuse file [DJF, SRF; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.7.6a","Requirement","ECSS-Q-ST-80_0720137",1,"Created","The analysis of the suitability of existing software for reuse shall be complemented by an assessment of the following aspects:\n    1. the acceptance and warranty conditions;\n    2. the available support documentation; \n    3. the conditions of installation, preparation, training and use; \n    4. the identification and registration by configuration management; \n    5. maintenance responsibility and conditions, including the possibilities of changes; \n    6. the durability and validity of methods and tools used in the initial development, that are envisaged to be used again; \n    7. the copyright and intellectual property rights constraints (modification rights); \n    8. the licensing conditions;\n    9. exportability constraints.\n","EXPECTED OUTPUT: Software reuse file [DJF, SRF; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.7.7a","Requirement","ECSS-Q-ST-80_0720138",1,"Created","Corrective actions shall be identified, documented in the reuse file and applied to the reused software not meeting the applicable requirements related to the aspects as specified in clauses 6.2.7.2 to 6.2.7.6.\n","EXPECTED OUTPUT: Software reuse file [DJF, SRF; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.7.8a","Requirement","ECSS-Q-ST-80_0720139",1,"Created","Reverse engineering techniques shall be applied to generate missing documentation and to reach the required verification and validation coverage."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.7.8b","Requirement","ECSS-Q-ST-80_0720140",1,"Created","For software products whose life cycle data from previous development are not available and reverse engineering techniques are not fully applicable, the following methods shall be applied:\n    1. generation of validation and verification documents based on the available user documentation (e.g. user manual) and execution of tests in order to achieve the required level of test coverage;\n    2. use of the product service history to provide evidence of the product’s suitability for the current application, including information about:\n        (a) relevance of the product service history for the new operational environment;\n        (b) configuration management and change control of the software product;\n        (c) effectiveness of problem reporting;\n        (d) actual error rates and maintenance records;\n        (e) impact of modifications.\n","EXPECTED OUTPUT: Software reuse file [DJF, SRF; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.7.9a","Requirement","ECSS-Q-ST-80_0720141",1,"Created","The software reuse file shall be updated at project milestones to reflect the results of the identified corrective actions for reused software not meeting the project requirements.\n","EXPECTED OUTPUT: Software reuse file [DJF, SRF; CDR, QR, AR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.7.10a","Requirement","ECSS-Q-ST-80_0720142",1,"Created","All the reused software shall be kept under configuration control."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.7.11a","Requirement","ECSS-Q-ST-80_0720143",1,"Created","The detailed configuration status of the reused software baseline shall be provided to the customer in the reuse file for acceptance.\n","EXPECTED OUTPUT: Software reuse file [DJF, SRF; SRR, PDR, CDR, QR, AR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.8.1a","Requirement","ECSS-Q-ST-80_0720144",1,"Created","For the selection of tools for automatic code generation, the supplier shall evaluate the following aspects:\n    1. evolution of the tools in relation to the tools that use the generated code as an input;\n        NOTE For example: compilers or code management systems.\n    2. customization of the tools to comply with project standards; \n    3. portability requirements for the generated code; \n    4. collection of the required design and code metrics; \n    5. verification of software components containing generated code; \n    6. configuration control of the tools including the parameters for customisation;\n    7. compliance with open standards."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.8.2a","Requirement","ECSS-Q-ST-80_0720145",1,"Created","The requirements on testing applicable to the automatically generated code shall ensure the achievement of the same objectives as those for manually generated code.\n","EXPECTED OUTPUT: Validation and testing documentation [DJF, SValP; PDR], [DJF, SVS; CDR, QR, AR], [DJF, SUITP; PDR, CDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.8.3a","Requirement","ECSS-Q-ST-80_0720146",1,"Created","The required level of verification and validation of the automatic generation tool shall be at least the same as the one required for the generated code, if the tool is used to skip verification or testing activities on the target code."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.8.4a","Requirement","ECSS-Q-ST-80_0720147",1,"Created","Modelling standards for automatic code generation tools shall be defined and applied.\n","EXPECTED OUTPUT: Modelling standards [PAF, -; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.8.5a","Requirement","ECSS-Q-ST-80_0720148",1,"Created","Adherence to modelling standards shall be verified.\n","EXPECTED OUTPUT: Software product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.8.6a","Requirement","ECSS-Q-ST-80_0720149",1,"Created","Clause 6.3.4 shall apply to automatically generated code, unless the supplier demonstrates that the automatically generated code does not need to be manually modified."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.2.8.7a","Requirement","ECSS-Q-ST-80_0720150",1,"Created","The verification and validation documentation shall address separately the activities to be performed for manually and automatically generated code.\n","EXPECTED OUTPUT: Validation and testing documentation [DJF, SValP; PDR], [DJF, SVS; CDR, QR, AR], [DJF, SUITP; PDR, CDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.1.1a","Requirement","ECSS-Q-ST-80_0720151",1,"Created","For the definition of the software related system requirements to be specified in the requirements baseline, ECSS-E-ST-40 clause 5.2 shall apply."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.1.2a","Requirement","ECSS-Q-ST-80_0720152",1,"Created","The requirements baseline shall be subject to documentation control and configuration management as part of the development documentation."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.1.3a","Requirement","ECSS-Q-ST-80_0720153",1,"Created","For the definition of the requirements baseline, all results from the safety and dependability analyses (including results from the HSIA ECSS-Q-ST-30 clause 6.4.2.3) shall be used."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.2.1a","Requirement","ECSS-Q-ST-80_0720154",1,"Created","The requirements baseline shall be analyzed to fully and unambiguously define the software requirements in the technical specification."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.2.2a","Requirement","ECSS-Q-ST-80_0720155",1,"Created","The technical specification shall be subject to documentation control and configuration management as part of the development documentation."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.2.3a","Requirement","ECSS-Q-ST-80_0720156",1,"Created","For the definition of the technical specification, all results from the safety and dependability analyses (including results from the HSIA ECSS-Q-ST-30 clause 6.4.2.3) shall be used."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.2.4a","Requirement","ECSS-Q-ST-80_0720157",1,"Created","In addition to the functional requirements, the technical specification shall include all non-functional requirements necessary to satisfy the requirements baseline, including, as a minimum, the following:\n    1. performance,\n    2. safety,\n    3. reliability,\n    4. robustness,\n    5. quality,\n    6. maintainability,\n    7. configuration management,\n    8. security,\n    9. privacy,\n    10. metrication, and\n    11. verification and validation.\n        NOTE Performance requirements include requirements on numerical accuracy.\n","EXPECTED OUTPUT: Software requirements specification [TS, SRS; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.2.5a","Requirement","ECSS-Q-ST-80_0720158",1,"Created","Prior to the technical specification elaboration, customer and supplier shall agree on the following principles and rules as a minimum:\n    1. assignment of persons (on both sides) responsible for establishing the technical specification;\n    2. methods for agreeing on requirements and approving changes;\n    3. efforts to prevent misunderstandings such as definition of terms, explanations of background of requirements;\n    4. recording and reviewing discussion results on both sides."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.3.1a","Requirement","ECSS-Q-ST-80_0720159",1,"Created","The design definition file shall be subject to documentation control and configuration management. "]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.3.2a","Requirement","ECSS-Q-ST-80_0720160",1,"Created","Mandatory and advisory design standards shall be defined and applied.\n","EXPECTED OUTPUT: Design standards [PAF, -; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.3.3a","Requirement","ECSS-Q-ST-80_0720161",1,"Created","For software in which numerical accuracy is relevant to mission success specific rules on design and code shall be defined to ensure that the specified level of accuracy is obtained.\n    NOTE For example: for an attitude and orbit control subsystem, scientific data generation components.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.3.4a","Requirement","ECSS-Q-ST-80_0720162",1,"Created","Adherence to design standards shall be verified.\n","EXPECTED OUTPUT: Software product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.3.5a","Requirement","ECSS-Q-ST-80_0720163",1,"Created","The supplier shall define means, criteria and tools to ensure that the complexity and modularity of the design meet the quality requirements."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.3.5b","Requirement","ECSS-Q-ST-80_0720164",1,"Created","The design evaluation shall be performed in parallel with the design process, in order to provide feedback to the software design team.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.3.6a","Requirement","ECSS-Q-ST-80_0720165",1,"Created","Synthesis of the results obtained in the software complexity and modularity evaluation and corrective actions implemented shall be described in the software product assurance reports.\n","EXPECTED OUTPUT: Software product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.3.7a","Requirement","ECSS-Q-ST-80_0720166",1,"Created","The supplier shall review the design documentation to ensure that it contains the appropriate level of information for maintenance activities.\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Software product assurance plan [PAF, SPAP; PDR];\n          b.Software product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.4.1a","Requirement","ECSS-Q-ST-80_0720167",1,"Created","Coding standards (including consistent naming conventions and adequate commentary rules) shall be specified and observed.\n","EXPECTED OUTPUT: Coding standards [PAF, -; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.4.2a","Requirement","ECSS-Q-ST-80_0720168",1,"Created","The standards shall be consistent with the product quality requirements.\n    NOTE Coding standards depend on the software quality objectives (see clause 5.2.7).\n","EXPECTED OUTPUT: Coding standards [PAF, -; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.4.3a","Requirement","ECSS-Q-ST-80_0720169",1,"Created","The tools to be used in implementing and checking conformance with coding standards shall be identified in the product assurance plan before coding activities start.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.4.4a","Requirement","ECSS-Q-ST-80_0720170",1,"Created","Coding standards shall be reviewed with the customer to ensure that they reflect product quality requirements.\n","EXPECTED OUTPUT: Coding standards and description of tools [PAF, -; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.4.5a","Requirement","ECSS-Q-ST-80_0720171",1,"Created","Use of low-level programming languages shall be justified.\n","EXPECTED OUTPUT: Software development plan [MGT, SDP; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.4.6a","Requirement","ECSS-Q-ST-80_0720172",1,"Created","The supplier shall define measurements, criteria and tools to ensure that the software code meets the quality requirements.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.4.6b","Requirement","ECSS-Q-ST-80_0720173",1,"Created","The code evaluation shall be performed in parallel with the coding process, in order to provide feedback to the software programmers."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.4.7a","Requirement","ECSS-Q-ST-80_0720174",1,"Created","Synthesis of the code analysis results and corrective actions implemented shall be described in the software product assurance reports.\n","EXPECTED OUTPUT: Software product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.4.8a","Requirement","ECSS-Q-ST-80_0720175",1,"Created","The code shall be put under configuration control immediately after successful unit testing."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.1a","Requirement","ECSS-Q-ST-80_0720176",1,"Created","Testing shall be performed in accordance with a strategy for each testing level (i.e. unit, integration, validation against the technical specification, validation against the requirements baseline, acceptance), which includes:\n    1. the types of tests to be performed;\n        NOTE For example: functional, boundary, performance, and usability tests.\n    2. the tests to be performed in accordance with the plans and procedures;\n    3. the means and organizations to perform assurance function for testing and validation.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; PDR, CDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.2a","Requirement","ECSS-Q-ST-80_0720177",1,"Created","Based on the criticality of the software, test coverage goals for each testing level shall be agreed between the customer and the supplier and their achievement monitored by metrics: \n    1. for unit level testing;\n    2. for integration level testing;\n    3. for validation against the technical specification and validation against the requirements baseline.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; PDR, CDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.3a","Requirement","ECSS-Q-ST-80_0720178",1,"Created","The supplier shall ensure through internal review that the test procedures and data are adequate, feasible and traceable and that they satisfy the requirements.\n","EXPECTED OUTPUT: Software product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.4a","Requirement","ECSS-Q-ST-80_0720179",1,"Created","Test readiness reviews shall be held before the commencement of test activities, as defined in the software development plan.\n","EXPECTED OUTPUT: Test readiness review reports [DJF, -; TRR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.5a","Requirement","ECSS-Q-ST-80_0720180",1,"Created","Test coverage shall be checked with respect to the stated goals.\n","EXPECTED OUTPUT: Software product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.5b","Requirement","ECSS-Q-ST-80_0720181",1,"Created","Feedback from the results of test coverage evaluation shall be continuously provided to the software developers."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.6a","Requirement","ECSS-Q-ST-80_0720182",1,"Created","The supplier shall ensure that nonconformances and software problem reports detected during testing are properly documented and reported to those concerned.\n","EXPECTED OUTPUT: Nonconformance reports and software problem reports [DJF, -; CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.7a","Requirement","ECSS-Q-ST-80_0720183",1,"Created","The test coverage of configurable code shall be checked to ensure that the stated requirements are met in each tested configuration.\n","EXPECTED OUTPUT: Statement of compliance with test plans and procedures [PAF, -; CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.8a","Requirement","ECSS-Q-ST-80_0720184",1,"Created","The completion of actions related to software problem reports generated during testing and validation shall be verified and recorded.\n","EXPECTED OUTPUT: Software problem reports [DJF, -; SRR, PDR, CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.9a","Requirement","ECSS-Q-ST-80_0720185",1,"Created","Provisions shall be made to allow witnessing of tests by the customer."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.10a","Requirement","ECSS-Q-ST-80_0720186",1,"Created","Provisions shall be made to allow witnessing of tests by supplier personnel independent of the development.\n    NOTE For example: specialist software product assurance personnel."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.11a","Requirement","ECSS-Q-ST-80_0720187",1,"Created","The supplier shall ensure that:\n    1. tests are conducted in accordance with approved test procedures and data, \n    2. the configuration under test is correct, \n    3. the tests are properly documented, and \n    4. the test reports are up to date and valid. \n","EXPECTED OUTPUT: Statement of compliance with test plans and procedures [PAF, -; CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.12a","Requirement","ECSS-Q-ST-80_0720188",1,"Created","The supplier shall ensure that tests are repeatable by verifying the storage and recording of tested software, support software, test environment, supporting documents and problems found.\n","EXPECTED OUTPUT: Software product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.13a","Requirement","ECSS-Q-ST-80_0720189",1,"Created","The supplier shall confirm in writing that the tests are successfully completed.\n","EXPECTED OUTPUT: Testing and validation reports [DJF, -; CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.14a","Requirement","ECSS-Q-ST-80_0720190",1,"Created","Review boards looking to engineering and product assurance aspects shall be convened after the completion of test phases, as defined in the software development plan."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.15a","Requirement","ECSS-Q-ST-80_0720191",1,"Created","Areas affected by any modification shall be identified and re-tested (regression testing)."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.16a","Requirement","ECSS-Q-ST-80_0720192",1,"Created","In case of re-testing, all test related documentation (test procedures, data and reports) shall be updated accordingly.\n","EXPECTED OUTPUT: Updated test documentation [DJF, -; CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.17a","Requirement","ECSS-Q-ST-80_0720193",1,"Created","The need for regression testing and additional verification of the software shall be analysed after any change of the platform hardware.\n","EXPECTED OUTPUT: Updated test documentation [DJF, -; CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.18a","Requirement","ECSS-Q-ST-80_0720194",1,"Created","The need for regression testing and additional verification of the software shall be analysed after a change or update of any tool used to generate it.\n    NOTE For example: source code or object code.\n","EXPECTED OUTPUT: Updated test documentation [DJF, -; CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.19a","Requirement","ECSS-Q-ST-80_0720195",1,"Created","Validation shall be carried out by staff who have not taken part in the design or coding of the software being validated.\n    NOTE This can be achieved at the level of the whole software product, or on a component by component basis."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.20a","Requirement","ECSS-Q-ST-80_0720196",1,"Created","Validation of the flight software against the requirement baseline on the flight equipment model shall be performed on a software version without any patch. "]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.21a","Requirement","ECSS-Q-ST-80_0720197",1,"Created","The supplier shall review the test documentation to ensure that it is up to date and organized to facilitate its reuse for maintenance."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.22a","Requirement","ECSS-Q-ST-80_0720198",1,"Created","Tests shall be organized as activities in their own right in terms of planning, resources and team composition. \n","EXPECTED OUTPUT: Test and validation documentation [DJF, SValP; PDR], [DJF, SUITP; PDR, CDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.23a","Requirement","ECSS-Q-ST-80_0720199",1,"Created","The necessary resources for testing shall be identified early in the life cycle, taking into account the operating and maintenance requirements. \n","EXPECTED OUTPUT: Test and validation documentation [DJF, SValP; PDR], [DJF, SUITP; PDR, CDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.24a","Requirement","ECSS-Q-ST-80_0720200",1,"Created","Test tool development or acquisition (hardware and software) shall be planned for in the overall project plan.\n","EXPECTED OUTPUT: Test and validation documentation [DJF, SValP; PDR], [DJF, SUITP; PDR, CDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.25a","Requirement","ECSS-Q-ST-80_0720201",1,"Created","The supplier shall establish and review the test procedures and data before starting testing activities and also document the constraints of the tests concerning physical, performance, functional, controllability and observability limitations.\n","EXPECTED OUTPUT: Test and validation documentation [DJF, SValP; PDR], [DJF, SVS; CDR, QR, AR], [DJF, SUITP; PDR, CDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.26a","Requirement","ECSS-Q-ST-80_0720202",1,"Created","Before offering the product for delivery and customer acceptance, the supplier shall validate its operation as a complete product, under conditions similar to the application environment as specified in the requirements baseline."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.27a","Requirement","ECSS-Q-ST-80_0720203",1,"Created","When testing under the operational environment is performed, the following concerns shall be addressed:\n    1. the features to be tested in the operational environment;\n    2. the specific responsibilities of the supplier and customer for carrying out and evaluating the test;\n    3. restoration of the previous operational environment (after test).\n","EXPECTED OUTPUT: Test and validation documentation [DJF, -; AR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.28a","Requirement","ECSS-Q-ST-80_0720204",1,"Created","Independent software validation shall be performed by a third party.\n    NOTE This requirement is applicable where the risks associated with the project justify the costs involved. The customer can consider a less rigorous level of independence, e.g. an independent team in the same organization.\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.ISVV plan [DJF, -; SRR, PDR];\n          b.ISVV report [DJF, -; PDR, CDR, QR, AR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.29a","Requirement","ECSS-Q-ST-80_0720205",1,"Created","The validation shall include testing in the different configurations possible or in a representative set of them when it is evident that the number of possible configurations is too high to allow validation in all of them.\n","EXPECTED OUTPUT: Test and validation documentation [DJF, SValP; PDR], [DJF, SVS; CDR, QR, AR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.30a","Requirement","ECSS-Q-ST-80_0720206",1,"Created","Software containing deactivated code shall be validated specifically to ensure that the deactivated code cannot be activated or that its accidental activation cannot harm the operation of the system.\n","EXPECTED OUTPUT: Testing and validation reports [DJF, -; CDR, QR, AR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.31a","Requirement","ECSS-Q-ST-80_0720207",1,"Created","Software containing configurable code shall be validated specifically to ensure that unintended configuration cannot be activated at run time or included during code generation.\n","EXPECTED OUTPUT: Testing and validation reports [DJF, -; CDR, QR, AR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.5.32a","Requirement","ECSS-Q-ST-80_0720208",1,"Created","Activities for the validation of the quality requirements shall be specified in the definition of the validation specification. \n","EXPECTED OUTPUT: Software validation specification [DJF, SVS; CDR, QR, AR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.6.1a","Requirement","ECSS-Q-ST-80_0720209",1,"Created","The roles, responsibilities and obligations of the supplier and customer during installation shall be established.\n","EXPECTED OUTPUT: Installation procedure [DDF, SCF; AR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.6.2a","Requirement","ECSS-Q-ST-80_0720210",1,"Created","The installation shall be performed in accordance with the installation procedure."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.6.3a","Requirement","ECSS-Q-ST-80_0720211",1,"Created","The customer shall establish an acceptance test plan specifying the intended acceptance tests including specific tests suited to the target environment (see ECSS-E-ST-40 clause 5.7.3.1).\n    NOTE 1 The acceptance tests can be partly made up of tests used during previous test activities.\n    NOTE 2 The acceptance test plan takes into account the requirement for operational demonstration, either as part of acceptance or after acceptance.\n","EXPECTED OUTPUT: Acceptance test plan [DJF, -; QR, AR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.6.4a","Requirement","ECSS-Q-ST-80_0720212",1,"Created","The customer shall ensure that the acceptance tests are performed in accordance with the approved acceptance test plan (see ECSS-E-ST-40 clause 5.7.3.2)."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.6.5a","Requirement","ECSS-Q-ST-80_0720213",1,"Created","Before the software is presented for customer acceptance, the supplier shall ensure that:\n    1. the delivered software complies with the contractual requirements (including any specified content of the software acceptance data package);\n    2. the source and object code supplied correspond to each other;\n    3. all agreed changes are implemented;\n    4. all nonconformances are either resolved or declared."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.6.6a","Requirement","ECSS-Q-ST-80_0720214",1,"Created","The customer shall verify that the executable code was regenerated from configuration managed source code components and installed in accordance with predefined procedures on the target environment."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.6.7a","Requirement","ECSS-Q-ST-80_0720215",1,"Created","Any discovered problems shall be documented in nonconformance reports.\n","EXPECTED OUTPUT: Nonconformance reports [DJF, -; AR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.6.8a","Requirement","ECSS-Q-ST-80_0720216",1,"Created","On completion of the acceptance tests, a report shall be drawn up and be signed by the supplier’s representatives, the customer’s representatives, the software quality engineers of both parties and the representative of the organization charged with the maintenance of the software product.\n","EXPECTED OUTPUT: Acceptance test report [DJF, -; AR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.6.9a","Requirement","ECSS-Q-ST-80_0720217",1,"Created","The customer shall certify conformance to the procedures and state the conclusion concerning the test result for the software product under test (accepted, conditionally accepted, rejected).\n","EXPECTED OUTPUT: Acceptance test report [DJF, -; AR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.7.1a","Requirement","ECSS-Q-ST-80_0720218",1,"Created","During operations, the quality of the mission products related to software shall be agreed with the customer and users.\n    NOTE Quality of mission products can include parameters such as: error-free data, availability of data and permissible outages; permissible information degradation.\n","EXPECTED OUTPUT: Software operation support plan [OP, -; ORR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.7.2a","Requirement","ECSS-Q-ST-80_0720219",1,"Created","During the demonstration that the software conforms to the operational requirements, the following shall be covered as a minimum:\n    1. availability and maintainability of the host system (including reboot after maintenance interventions);\n    2. safety features;\n    3. human-computer interface;\n    4. operating procedures;\n    5. ability to meet the mission product quality requirements.\n","EXPECTED OUTPUT: Validation of the operational requirements [PAF, -; ORR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.7.3a","Requirement","ECSS-Q-ST-80_0720220",1,"Created","The product assurance plan for system operations shall include consideration of software.\n","EXPECTED OUTPUT: Input to product assurance plan for systems operation [PAF, -; ORR]"]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.8.1a","Requirement","ECSS-Q-ST-80_0720221",1,"Created","The organization responsible for maintenance shall be identified to allow a smooth transition into the operations and maintenance.\n    NOTE An organization, with representatives from both supplier and customer, can be set up to support the maintenance activities. Attention is drawn to the importance of the flexibility of this organization to cope with the unexpected occurrence of problems and the identification of facilities and resources to be used for the maintenance activities.\n","EXPECTED OUTPUT: Maintenance plan [MF, -; QR, AR, ORR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.8.2a","Requirement","ECSS-Q-ST-80_0720222",1,"Created","The maintenance organization shall specify the assurance, verification and validation activities applicable to maintenance interventions.\n","EXPECTED OUTPUT: Maintenance plan [MF, -; QR, AR, ORR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.8.3a","Requirement","ECSS-Q-ST-80_0720223",1,"Created","The maintenance plans shall be verified against specified requirements for maintenance of the software product.\n    NOTE The maintenance plans and procedures can address corrective, improving, adaptive and preventive maintenance, differentiating between “routine” and “emergency” maintenance activities."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.8.4a","Requirement","ECSS-Q-ST-80_0720224",1,"Created","The maintenance plans and procedures shall include the following as a minimum:\n    1. scope of maintenance;\n    2. identification of the first version of the software product for which maintenance is to be done;\n    3. support organization;\n    4. maintenance life cycle;\n    5. maintenance activities;\n    6. quality measures to be applied during the maintenance;\n    7. maintenance records and reports.\n","EXPECTED OUTPUT: Maintenance plan [MF, -; QR, AR, ORR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.8.5a","Requirement","ECSS-Q-ST-80_0720225",1,"Created","Rules for the submission of maintenance reports shall be established and agreed as part of the maintenance plan.\n","EXPECTED OUTPUT: Maintenance plan [MF, -; QR, AR, ORR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.8.6a","Requirement","ECSS-Q-ST-80_0720226",1,"Created","All maintenance activities shall be logged in predefined formats and retained. \n","EXPECTED OUTPUT: Maintenance records [MF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","6.3.8.7a","Requirement","ECSS-Q-ST-80_0720227",1,"Created","Maintenance records shall be established for each software product, including, as a minimum, the following information,:\n    1. list of requests for assistance or problem reports that have been received and the current status of each;\n    2. organization responsible for responding to requests for assistance or implementing the appropriate corrective actions;\n    3. priorities assigned to the corrective actions;\n    4. results of the corrective actions;\n    5. statistical data on failure occurrences and maintenance activities.\n        NOTE The record of the maintenance activities can be utilized for evaluation and enhancement of the software product and for improvement of the quality system itself.\n","EXPECTED OUTPUT: Maintenance records [MF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.1.1a","Requirement","ECSS-Q-ST-80_0720228",1,"Created","The software quality requirements (including safety and dependability requirements) shall be derived from the requirements defined at system level.\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Requirement baseline [RB, SSS; SRR];\n          b.Technical specification [TS, SRS; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.1.2a","Requirement","ECSS-Q-ST-80_0720229",1,"Created","Quality requirements shall be expressed in quantitative terms or constraints.\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Requirement baseline [RB, SSS; SRR];\n          b.Technical specification [TS, SRS; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.1.3a","Requirement","ECSS-Q-ST-80_0720230",1,"Created","The supplier shall define assurance activities to ensure that the product meets the quality requirements as specified in the technical specification.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.1.4a","Requirement","ECSS-Q-ST-80_0720231",1,"Created","In order to verify the implementation of the product quality requirements, the supplier shall define a metrication programme based on the identified quality model (see clause 5.2.7), specifying:\n    1. the metrics to be collected and stored;\n    2. the means to collect metrics (measurements);\n    3. the target values, with reference to the product quality requirements;\n    4. the analyses to be performed on the collected metrics, including the ones to derive:\n        (a) descriptive statistics;\n            NOTE For example: the number of units at each level of complexity.\n        (b) trend analysis (such as trends in software problems).\n    5. how the results of the analyses performed on the collected metrics are fed back to the development team and used to identify corrective actions;\n    6. the schedule of metrics collection, storing, analysis and reporting, with reference to the whole software life cycle.\n        NOTE Guidance for software metrication programme implementation can be found in ECSS-Q-HB-80-04. \n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.1.5a","Requirement","ECSS-Q-ST-80_0720232",1,"Created","The following basic products metrics shall be used:\n    1. size (code);\n    2. complexity (design, code);\n    3. fault density and failure intensity;\n    4. test coverage;\n    5. number of failures.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.1.6a","Requirement","ECSS-Q-ST-80_0720233",1,"Created","The results of metrics collection and analysis shall be included in the software product assurance reports, in order to provide the customer with an insight into the level of quality obtained.\n","EXPECTED OUTPUT: Software product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.1.7a","Requirement","ECSS-Q-ST-80_0720234",1,"Created","Numerical accuracy shall be estimated and verified.\n","EXPECTED OUTPUT: Numerical accuracy analysis [DJF, SVR; PDR, CDR, QR]. "]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.1.8a","Requirement","ECSS-Q-ST-80_0720235",1,"Created","The supplier shall define the organization and means implemented to collect and analyse data required for the study of software maturity.\n    NOTE For example: failures, corrections, duration of runs.\n","EXPECTED OUTPUT: Software product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.2.1.1a","Requirement","ECSS-Q-ST-80_0720236",1,"Created","The software quality requirements shall be documented in the requirements baseline and technical specification.\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Requirement baseline [RB, SSS; SRR];\n          b.Technical specification [TS, SRS; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.2.1.2a","Requirement","ECSS-Q-ST-80_0720237",1,"Created","The software requirements shall be: \n    1. correct;\n    2. unambiguous;\n    3. complete;\n    4. consistent;\n    5. verifiable;\n    6. traceable."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.2.1.3a","Requirement","ECSS-Q-ST-80_0720238",1,"Created","For each requirement the method for verification and validation shall be specified.\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Requirement baseline [RB, SSS; SRR];\n          b.Technical specification [TS, SRS; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.2.2.1a","Requirement","ECSS-Q-ST-80_0720239",1,"Created","The software design shall meet the non-functional requirements as documented in the technical specification."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.2.2.2a","Requirement","ECSS-Q-ST-80_0720240",1,"Created","The software shall be designed to facilitate testing."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.2.2.3a","Requirement","ECSS-Q-ST-80_0720241",1,"Created","Software with a long planned lifetime shall be designed with minimum dependency on the operating system and the hardware, in order to aid portability.\n    NOTE This requirement is applicable to situations where the software lifetime can lead to the obsolescence and non-availability of the original operating system and/or hardware, thereby jeopardizing the maintainability the software.\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Software product assurance plan [PAF, SPAP; SRR, PDR];\n          b.Justification of design choices [DDF, SDD; PDR, CDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.2.3.1a","Requirement","ECSS-Q-ST-80_0720242",1,"Created","Detailed test and validation documentation (data, procedures and expected results) defined in the ECSS-E-ST-40 DJF shall be consistent with the defined test and validation strategy (see clause 6.3.5 and ECSS-E-ST-40 clauses 5.5.3, 5.5.4, 5.6 and 5.8)."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.2.3.2a","Requirement","ECSS-Q-ST-80_0720243",1,"Created","The test documentation shall cover the test environment, tools and test software, personnel required and associated training requirements."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.2.3.3a","Requirement","ECSS-Q-ST-80_0720244",1,"Created","The criteria for completion of each test and any contingency steps shall be specified."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.2.3.4a","Requirement","ECSS-Q-ST-80_0720245",1,"Created","Test procedures, data and expected results shall be specified."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.2.3.5a","Requirement","ECSS-Q-ST-80_0720246",1,"Created","The hardware and software configuration shall be identified and documented as part of the test documentation."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.2.3.6a","Requirement","ECSS-Q-ST-80_0720247",1,"Created","For any requirements not covered by testing a verification report shall be drawn up documenting or referring to the verification activities performed.\n","EXPECTED OUTPUT: Software verification report [DJF, SVR; CDR, QR, AR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.3.1a","Requirement","ECSS-Q-ST-80_0720248",1,"Created","For the development of software intended for reuse, ECSS-E-ST-40 clauses 5.2.4.7 and 5.4.3.6 shall apply."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.3.2a","Requirement","ECSS-Q-ST-80_0720249",1,"Created","The information related to the components developed for reuse shall be separated from the others in the technical specification, design justification file, design definition file and product assurance file. "]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.3.3a","Requirement","ECSS-Q-ST-80_0720250",1,"Created","The information related to components developed for reuse in the technical specification, the design justification file, the design definition file and the product assurance file shall be self-contained."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.3.4a","Requirement","ECSS-Q-ST-80_0720251",1,"Created","The technical specification of components developed for reuse shall include requirements for maintainability, portability and verification of those components.\n","EXPECTED OUTPUT: Technical specification for reusable components [TS, -; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.3.5a","Requirement","ECSS-Q-ST-80_0720252",1,"Created","The configuration management system shall include provisions for handling specific aspects of software developed for reuse, such as:\n    • longer lifetime of the components developed for reuse compared to the other components of the project;\n    • evolution or change of the development environment for the next project that intends to use the components;\n    • transfer of the configuration and documentation management information to the next project reusing the software.\n","EXPECTED OUTPUT: Software configuration management plan [MGT, SCMP; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.3.6a","Requirement","ECSS-Q-ST-80_0720253",1,"Created","Where the components developed for reuse are developed to be reusable on different platforms, the testing of the software shall be performed on all those platforms. \n","EXPECTED OUTPUT: Verification and validation documentation for reusable components [DJF, -; CDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.3.7a","Requirement","ECSS-Q-ST-80_0720254",1,"Created","The supplier shall provide a certificate of conformance that the tests have been successfully completed on all the relevant platforms.\n    NOTE In case not all platforms are available, the certificate of conformance states the limitations of the validation performed.\n","EXPECTED OUTPUT: Verification and validation documentation for reusable components [DJF, -; CDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.4.1a","Requirement","ECSS-Q-ST-80_0720255",1,"Created","The subcontracting and procurement of hardware shall be carried out according to the requirements of ECSS-Q-ST-20 clause 7.\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Justification of selection of operational ground equipment [DJF, -; SRR, PDR];\n          b.Receiving inspection reports [PAF, -; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.4.2a","Requirement","ECSS-Q-ST-80_0720256",1,"Created","The procurement of support services to be used in operational phases shall be justified as covering service level agreements, quality of services and escalation procedures, as needed for system exploitation and maintenance.\n","EXPECTED OUTPUT: Justification of selection of operational support services [DJF, -; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.4.3a","Requirement","ECSS-Q-ST-80_0720257",1,"Created","The choice of procured hardware and services shall address the constraints associated with both the development and the actual use of the software.\n","EXPECTED OUTPUT: Justification of selection of operational ground equipment [DJF, -; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.4.4a","Requirement","ECSS-Q-ST-80_0720258",1,"Created","The ground computer equipment and supporting services for implementing the final system shall be selected according to the project requirements regarding:\n    1. performance;\n    2. maintenance;\n    3. durability and technical consistency with the operational equipment;\n    4. the assessment of the product with respect to requirements, including the criticality category;\n    5. the available support documentation;\n    6. the acceptance and warranty conditions;\n    7. the conditions of installation, preparation, training and use;\n    8. the maintenance conditions, including the possibilities of evolutions;\n    9. copyright constraints;\n    10. availability;\n    11. compatibility;\n    12. site operational constraints.\n","EXPECTED OUTPUT: Justification of selection of operational ground equipment [DJF, -; SRR, PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.4.5a","Requirement","ECSS-Q-ST-80_0720259",1,"Created","Taking account of the provider’s maintenance and product policy, it shall be ensured that the hardware and support services can be maintained throughout the specified life of the software product within the operational constraints."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.5.1a","Requirement","ECSS-Q-ST-80_0720260",1,"Created","The supplier shall establish procedures for firmware device programming and duplication of firmware devices.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.5.2a","Requirement","ECSS-Q-ST-80_0720261",1,"Created","The firmware device shall be indelibly marked to allow the identification (by reference) of the hardware component and of the software component.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; PDR]."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","7.5.3a","Requirement","ECSS-Q-ST-80_0720262",1,"Created","The supplier shall ensure that the firmware programming equipment is calibrated."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<1>a","Requirement","ECSS-Q-ST-80_0720263",1,"Created","The SPAP shall contain a description of the purpose, objective, content and the reason prompting its preparation."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<2>a","Requirement","ECSS-Q-ST-80_0720264",1,"Created","The SPAP shall list the applicable and reference documents to support the generation of the document."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<3>a","Requirement","ECSS-Q-ST-80_0720265",1,"Created","The SPAP shall include any additional terms, definition or abbreviated terms used."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<4>a","Requirement","ECSS-Q-ST-80_0720266",1,"Created","The SPAP shall include or refer to a description of the system and software products being developed."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<5.1>a","Requirement","ECSS-Q-ST-80_0720267",1,"Created","The SPAP shall describe the organization of software product assurance activities, including responsibility, authority and the interrelation of personnel who manage, perform and verify work affecting software quality."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<5.1>b","Requirement","ECSS-Q-ST-80_0720268",1,"Created","The following topics shall be included:\n    1. organizational structure;\n    2. interfaces of each organisation, either external or internal, involved in the project; \n    3. relationship to the system level product assurance and safety;\n    4. independence of the software product assurance function;\n    5. delegation of software product assurance tasks to a lower level supplier, if any."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<5.2>a","Requirement","ECSS-Q-ST-80_0720269",1,"Created","The SPAP shall describe the responsibilities of the software product assurance function."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<5.3>a","Requirement","ECSS-Q-ST-80_0720270",1,"Created","The SPAP shall describe the resources to be used to perform the software product assurance function."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<5.3>b","Requirement","ECSS-Q-ST-80_0720271",1,"Created","The description in B.2.1<5.3>a shall include human resources and skills, hardware and software tools."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<5.4>a","Requirement","ECSS-Q-ST-80_0720272",1,"Created","The SPAP shall describe the reporting to be performed by software product assurance."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<5.5>a","Requirement","ECSS-Q-ST-80_0720273",1,"Created","The SPAP shall describe the quality models applicable to the project and how they are used to specify the quality requirements."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<5.6>a","Requirement","ECSS-Q-ST-80_0720274",1,"Created","The SPAP shall describe the contribution of the software product assurance function to the project risk management."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<5.7>a","Requirement","ECSS-Q-ST-80_0720275",1,"Created","The SPAP shall describe the contribution of the software product assurance function to the next level suppliers selection and control."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<5.8>a","Requirement","ECSS-Q-ST-80_0720276",1,"Created","The SPAP shall describe the methods and tools used for all the activities of the development cycle, and their level of maturity."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<5.9>a","Requirement","ECSS-Q-ST-80_0720277",1,"Created","1.The SPAP shall state the scope and objectives of process assessment."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<5.9>b","Requirement","ECSS-Q-ST-80_0720278",1,"Created","2.The SPAP shall describe the methods and tools to be used for process assessment and improvement."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<5.10>a","Requirement","ECSS-Q-ST-80_0720279",1,"Created","The SPAP shall specify the quality measures related to the operations and maintenance processes (alternatively, a separate SPAP is produced)."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<6.1>a","Requirement","ECSS-Q-ST-80_0720280",1,"Created","The SPAP shall refer to the software development cycle description in the software development plan. "]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<6.1>b","Requirement","ECSS-Q-ST-80_0720281",1,"Created","If not covered in the software development plan, the life cycle shall be described."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<6.1>c","Requirement","ECSS-Q-ST-80_0720282",1,"Created","The life cycle shall include a milestone immediately before the starting of the software validation."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<6.2>a","Requirement","ECSS-Q-ST-80_0720283",1,"Created","The SPAP shall describe all plans to be produced and used in the project."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<6.2>b","Requirement","ECSS-Q-ST-80_0720284",1,"Created","The relationship between the project plans and a timely planning for their preparation and update shall be described."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<6.3>a","Requirement","ECSS-Q-ST-80_0720285",1,"Created","The SPAP shall contain a description and justification of the measures to be applied for the handling of critical software, including the analyses to be performed and the standards applicable for critical software."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<6.4>a","Requirement","ECSS-Q-ST-80_0720286",1,"Created","The SPAP shall describe the contribution of the software product assurance function to the proper implementation of documentation and configuration management."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<6.4>b","Requirement","ECSS-Q-ST-80_0720287",1,"Created","The nonconformance control system shall be described or referenced. The point in the software life cycle from which the nonconformance procedures apply shall be specified."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<6.4>c","Requirement","ECSS-Q-ST-80_0720288",1,"Created","The SPAP shall identify method and tool to protect the supplied software, a checksum-type key calculation for the delivered operational software, and a labelling method for the delivered media."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<6.5>a","Requirement","ECSS-Q-ST-80_0720289",1,"Created","The SPAP shall describe the process metrics derived from the defined quality models, the means to collect, store and analyze them, and the way they are used to manage the development processes."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<6.6>a","Requirement","ECSS-Q-ST-80_0720290",1,"Created","The SPAP shall describe the approach for the reuse of existing software, including delta qualification. "]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<6.7>a","Requirement","ECSS-Q-ST-80_0720291",1,"Created","The following processes and activities shall be covered, taking into account the project scope and life cycle:\n    1. software requirements analysis;\n    2. software architectural design and design of software items;\n    3. coding;\n    4. testing and validation (including regression testing);\n    5. verification;\n    6. software delivery and acceptance;\n    7. operations and maintenance."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<6.8>a","Requirement","ECSS-Q-ST-80_0720292",1,"Created","The SPAP shall describe or list by reference all procedures and standards applicable to the development of the software in the project."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<6.8>b","Requirement","ECSS-Q-ST-80_0720293",1,"Created","The software product assurance measures to ensure adherence to the project procedures and standards shall be described. "]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<6.8>c","Requirement","ECSS-Q-ST-80_0720294",1,"Created","The standards and procedures to be described or listed in accordance with B.2.1<6.8>a shall be as a minimum those covering the following aspects:\n    1. project management;\n    2. risk management;\n    3. configuration and documentation management;\n    4. verification and validation;\n    5. requirements engineering;\n    6. design;\n    7. coding;\n    8. metrication;\n    9. nonconformance control;\n    10. audits;\n    11. alerts;\n    12. procurement;\n    13. reuse of existing software;\n    14. use of methods and tools;\n    15. numerical accuracy;\n    16. delivery, installation and acceptance;\n    17. operations;\n    18. maintenance;\n    19. device programming and marking."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<7>a","Requirement","ECSS-Q-ST-80_0720295",1,"Created","The SPAP shall describe the approach taken to ensure the quality of the software product. "]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<7>b","Requirement","ECSS-Q-ST-80_0720296",1,"Created","The description of the approach specified in B.2.1<7>a shall include the:\n    1. specification of the product metrics, their target values and the means to collect them;\n    2. definition of a timely metrication programme;\n    3. analyses to be performed on the collected metrics;\n    4. way the results are fed back to the development team;\n    5. documentation quality requirements;\n    6. assurance activities meant to ensure that the product meets the quality requirements."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<8>a","Requirement","ECSS-Q-ST-80_0720297",1,"Created","The SPAP shall include the compliance matrix to the applicable software product assurance requirements (e.g. ECSS-Q-ST-80 clauses, as tailored by a product assurance requirements document), or provide a reference to it."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","B.2.1<8>b","Requirement","ECSS-Q-ST-80_0720298",1,"Created","For each software product assurance requirement, the following information shall be provided:\n    1. requirement identifier;\n    2. compliance (C = compliant, NC = non–compliant, NA = not applicable);\n    3. reference to the project documentation covering the requirement (e.g. section of the software product assurance plan);\n    4. remarks."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","C.2.1<1>a","Requirement","ECSS-Q-ST-80_0720299",1,"Created","The SPAMR shall contain a description of the purpose, objective, content and the reason prompting its preparation."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","C.2.1<2>a","Requirement","ECSS-Q-ST-80_0720300",1,"Created","The SPAMR shall list the applicable and reference documents to support the generation of the document."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","C.2.1<3>a","Requirement","ECSS-Q-ST-80_0720301",1,"Created","The SPAMR shall include any additional terms, definition or abbreviated terms used."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","C.2.1<4>a","Requirement","ECSS-Q-ST-80_0720302",1,"Created","The SPAMR shall contain reporting on verification activities performed by the product assurance function, including:\n    1. reviews;\n    2. inspections;\n    3. walk-throughs;\n    4. review of traceability matrices;\n    5. documents reviewed."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","C.2.1<4>b","Requirement","ECSS-Q-ST-80_0720303",1,"Created","The SPAMR shall contain reporting on the verification of the measures applied for the handling of critical software."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","C.2.1<5>a","Requirement","ECSS-Q-ST-80_0720304",1,"Created","The SPAMR shall include or reference a justification of the suitability of the methods and tools applied in all the activities of the development cycle, including requirements analysis, software specification, design, coding, validation, testing, configuration management, verification and product assurance."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","C.2.1<5>b","Requirement","ECSS-Q-ST-80_0720305",1,"Created","The SPAMR shall include reporting on the correct use of methods and tools."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","C.2.1<6>a","Requirement","ECSS-Q-ST-80_0720306",1,"Created","The SPAMR shall include reporting on the adherence of software products to the applicable modelling, design and coding standards, including:\n    1. reporting on the application of measures meant to ensure that the design complexity and modularity meet the quality requirements;\n    2. reporting on design documentation w.r.t. suitability for maintenance."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","C.2.1<7>a","Requirement","ECSS-Q-ST-80_0720307",1,"Created","The SPAMR shall include reporting on the collected product and process metrics, the relevant analyses performed, the corrective actions undertaken and the status of these actions."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","C.2.1<7>b","Requirement","ECSS-Q-ST-80_0720308",1,"Created","The results of the software maturity analysis shall also be reported."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","C.2.1<8>a","Requirement","ECSS-Q-ST-80_0720309",1,"Created","The SPAMR shall include reporting on adequacy of the testing and validation documentation (including feasibility, traceability repeatability), and on the achieved test coverage w.r.t. stated goals."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","C.2.1<9>a","Requirement","ECSS-Q-ST-80_0720310",1,"Created","The SPAMR shall include reporting on the status of software problem reports and nonconformances relevant to software."]
["ECSS-Q-ST-80C","ECSS - Superseded v1.0","C.2.1<10>a","Requirement","ECSS-Q-ST-80_0720311",1,"Created","Whenever relevant and up-to-date information has been already delivered as part of the regular PA progress reporting, a representative summary shall be provided, together with a detailed reference to the progress report(s) containing that information."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.1a","Requirement","ECSS-Q-ST-10-09_0350001",1,"Created","The supplier’s project PA representative shall perform an immediate preliminary assessment of the nonconformance to establish its extent and cause when it is detected."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.1b","Requirement","ECSS-Q-ST-10-09_0350002",1,"Created","Based on the preliminary assessment the supplier’s project PA representative shall take the following actions without delay:\n    1. Provisions for the safety of the personnel and of the equipment.\n    2. Prevention of unauthorized use of the nonconforming items, by marking and, unless otherwise determined by the PA representative, segregation until their disposition.\n    3. Prevention of the recurrence of the nonconformances on similar or identical items under processing or testing at that time.\n        NOTE This can lead to the suspension of manufacturing or testing."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.1c","Requirement","ECSS-Q-ST-10-09_0350003",1,"Created","The supplier shall apply the following actions to the segregation of nonconforming articles:\n    1. Establish a clearly marked holding area for nonconforming items pending NRB disposition.\n    2. Limit the access to this area to NRB members or personnel authorized by the NRB.\n    3. Make provisions to prevent unauthorized removal of any item."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.1d","Requirement","ECSS-Q-ST-10-09_0350004",1,"Created","For items whose segregation in the holding area is not practicable the supplier shall perform the following actions:\n    1. Mark the item as “not to be used”.\n    2. Make sure that the item can not be used by unauthorized personnel."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.1e","Requirement","ECSS-Q-ST-10-09_0350005",1,"Created","The supplier shall complete the nonconformance report in conformance with Annex A, and submit it to the internal NRB. "]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.1f","Requirement","ECSS-Q-ST-10-09_0350006",1,"Created","The supplier shall describe the nonconformance clear, unambiguous and sufficiently detailed that it can be understood by personnel not involved in its detection."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.1g","Requirement","ECSS-Q-ST-10-09_0350007",1,"Created","The supplier shall ensure traceability between the NCR and the quality and manufacturing records related to the nonconforming item."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.2.1a","Requirement","ECSS-Q-ST-10-09_0350008",1,"Created","The NRB shall be the sole technical authority for the treatment of nonconformances occurring in the frame of a business agreement."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.2.1b","Requirement","ECSS-Q-ST-10-09_0350009",1,"Created","All NRB members shall make dispositions and decisions by consensus."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.2.1c","Requirement","ECSS-Q-ST-10-09_0350010",1,"Created","The NRB chairman shall involve higher management levels in case of conflict."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.2.2.1a","Requirement","ECSS-Q-ST-10-09_0350011",1,"Created","The supplier shall nominate and authorize the internal NRBs core members for the business agreement."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.2.2.1b","Requirement","ECSS-Q-ST-10-09_0350012",1,"Created","The responsibilities and authorities of each member shall be assigned."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.2.2.1c","Requirement","ECSS-Q-ST-10-09_0350013",1,"Created","The internal NRB shall include, at least, core members from the following areas:\n    1. Project PA (chairman),\n    2. Engineering.\n        NOTE Additional members, or experts, depending on the NCR subject can be nominated by the chairman."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.2.2.1d","Requirement","ECSS-Q-ST-10-09_0350014",1,"Created","Immediately after the reporting of a nonconformance, the chairman shall convene an internal NRB."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.2.2.2a","Requirement","ECSS-Q-ST-10-09_0350015",1,"Created","The internal NRB shall classify nonconformances as major or minor, based on the severity of their consequences. \n    NOTE Classification of nonconformances is not based on their consequences on cost and schedule."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.2.2.2b","Requirement","ECSS-Q-ST-10-09_0350016",1,"Created","In case of several different minor nonconformances on the same item, the internal NRB shall evaluate whether the nonconformances remain minor or reclassified as “major”."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.2.2.2c","Requirement","ECSS-Q-ST-10-09_0350017",1,"Created","In case of doubt, the internal NRB shall classify nonconformances as major."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.2.2.3a","Requirement","ECSS-Q-ST-10-09_0350018",1,"Created","The internal NRB shall investigate the cause(s) of the nonconformance.\n    NOTE If necessary, a separate group of experts can be assigned for the investigation."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.2.2.3b","Requirement","ECSS-Q-ST-10-09_0350019",1,"Created","The supplier shall carry out physical operation of an irreversible nature on the nonconforming item only with prior approval by the customer.\n    NOTE Non-destructive testing can be used, if the techniques involved have previously been approved by the customer."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.2.2.3c","Requirement","ECSS-Q-ST-10-09_0350020",1,"Created","The internal NRB shall analyse whether human error or poor workmanship are the primary or secondary cause for the nonconformance."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.2.2.3d","Requirement","ECSS-Q-ST-10-09_0350021",1,"Created","In case that human error or poor workmanship are the primary or secondary cause for the nonconformance, the supplier shall review all related documents and the competence level of personnel in order to prevent recurrence."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.2.2.3e","Requirement","ECSS-Q-ST-10-09_0350022",1,"Created","The internal NRB shall investigate the consequences of the nonconformance.\n    NOTE This can be supported, where appropriate, by dependability experts or by documentation such as FMECA, CIL, or DJF."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.2.2.3f","Requirement","ECSS-Q-ST-10-09_0350023",1,"Created","The internal NRB shall document the results of the investigation in the nonconformance report."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.2.2.4b","Requirement","ECSS-Q-ST-10-09_0350025",1,"Created","The supplier shall include minor nonconformances in the nonconformance status list.\n    NOTE Unless otherwise stated in the business agreement, minor nonconformances need not be notified to the customer."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.2.3.3a","Requirement","ECSS-Q-ST-10-09_0350034",1,"Created","Based on the results of the internal NRB’s investigations, the customer NRB shall decide on the need to perform complementary investigations of causes and consequences."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.4.1a","Requirement","ECSS-Q-ST-10-09_0350047",1,"Created","The supplier shall implement disposition by performing actions defined by the NRB and approved RFWs and RFDs."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.4.2b","Requirement","ECSS-Q-ST-10-09_0350053",1,"Created","The supplier PA representative shall close-out the NCR "]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","5.5.3c","Requirement","ECSS-Q-ST-10-09_0350065",1,"Created","The supplier shall define a frequency of the reviews which is appropriate to the volume of nonconformances, but not less than quarterly."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","6.1.2b","Requirement","ECSS-Q-ST-10-09_0350072",1,"Created","The supplier shall invite the final customer to the NRB meeting related to major nonconformances on EEE components."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","6.3.2.1b","Requirement","ECSS-Q-ST-10-09_0350081",1,"Created","All parties involved shall define clear responsibilities, authorities and procedures for the processing of operational nonconformances and anomalies."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","6.3.2.2b","Requirement","ECSS-Q-ST-10-09_0350085",1,"Created","The supplier shall classify operational anomalies in accordance with the severity of their consequences on the space system and the mission products, and the importance of the affected function for the global performance of the system."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","A.2.1<1>a","Requirement","ECSS-Q-ST-10-09_0350092",1,"Created","The NCR shall identify the supplier of the nonconforming item."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","A.2.1<11>a","Requirement","ECSS-Q-ST-10-09_0350103",1,"Created","The NCR shall provide the name of the supplier of the nonconforming item."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","A.2.1<18>a","Requirement","ECSS-Q-ST-10-09_0350111",1,"Created","The NCR shall identify minutes of meeting drafted during the NRB meeting."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","A.2.1<28>a","Requirement","ECSS-Q-ST-10-09_0350121",1,"Created","The NCR shall contain the basic fact or circumstances which causes the nonconformance as confirmed by customer NRB."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","A.2.1<37>a","Requirement","ECSS-Q-ST-10-09_0350130",1,"Created","The NCR shall have the date, signature and stamp of the supplier PA or QA responsible for final closure."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","B.2.1<6>a","Requirement","ECSS-Q-ST-10-09_0350139",1,"Created","The NCR status shall describe the disposition."]
["ECSS-Q-ST-10-09C","ECSS - Superseded v1.0","B.2.1<8>a","Requirement","ECSS-Q-ST-10-09_0350141",1,"Created","The NCR status shall refer to a RFW, if a related RFW exists."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","5.3c","Requirement","ECSS-Q-ST-70-10_0590008",1,"Created","The evaluation PCBs shall represent the highest technological capability for which the PCB manufacturer applies for qualification."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","6.2d","Requirement","ECSS-Q-ST-70-10_0590017",1,"Created","The PCB manufacturer shall agree with the qualification authority on the monitoring during the qualification programme."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","6.4f","Requirement","ECSS-Q-ST-70-10_0590027",1,"Created","If the PCBs are used for manned space programmes the customer shall assure the PCB base material is tested for the following items:\n    1. Flammability in conformance with ECSS-Q-ST-70-21.\n    2. Offgassing (toxicity) and odour according to ECSS-Q-ST-70-29."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","6.5.7a","Requirement","ECSS-Q-ST-70-10_0590040",1,"Created","The following measurements shall be performed on test pattern F:\n    1. Microsectioning to evaluate and determinate metal plating thickness.\n    2. Microsectioning after thermal cycling, thermal stress and damp heat (optional).\n        NOTE See example in Figure 6-8."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","6.5.13a","Requirement","ECSS-Q-ST-70-10_0590046",1,"Created","The CAD/CAM capability of the PCB manufacturer shall be evaluated on test pattern M by visual inspection.\n    NOTE See example Figure 6-14."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","6.6c","Requirement","ECSS-Q-ST-70-10_0590055",1,"Created","The qualification approval shall be valid for a period of two years."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.1d","Requirement","ECSS-Q-ST-70-10_0590064",1,"Created","The PCBs to be tested shall not be covered with a protective varnish."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.2.3e","Requirement","ECSS-Q-ST-70-10_0590074",1,"Created","The nonconformance criteria for non­plated­through holes \nshall be as follows:\n1.\tHoles plated unintentionally\tm/M\n2.\tIncompletely drilled holes, missing or additional holes\t          m/M\n"]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.2.3i","Requirement","ECSS-Q-ST-70-10_0590078",1,"Created","The nonconformance criteria for arbitrary defects of conductors and terminal pads shall be as follows:\n1.\ta £ 20 % of x and minimum conductor width > requirement\tm\n2.\ta > 20 % of x.................................................................................................................M\n3.\tminimum conductor width < requirement..........................................................................M\n4.\tb £ x.............................................................................................................................m\n5.\tb > x.............................................................................................................................M\n6.\tOpposite peaks: if z < 80 % of y\tM\n7.\tIsolated peaks or valleys: h > 20 % of x and z < requirement..............................................M\n8.\tConducting island: a + h > 20 % of y and the isolation spacing < requirement.......................M\n9.\tMinimum remaining spacing y - a < requirement................................................................M\n10.\ta > 20 % of y..................................................................................................................M\n11.\tb > y..............................................................................................................................M\n12.\tCover layer (flexible PCBs) covering part of solder pad (see Figure 7-3)\t.M\nNOTE \tIntermittent and irregular metallisation defects on conductors are edge roughness (peak or valley), pits, pin holes, voids, protrusions or indentations, as shown in Figure 7-1, Figure 7-2 and Figure 7-3."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.2.5d","Requirement","ECSS-Q-ST-70-10_0590085",1,"Created","The length of the PCB shall be measured."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.2.7c","Requirement","ECSS-Q-ST-70-10_0590098",1,"Created","The measurements shall be presented in tabular form.\n    NOTE An example is given in Figure 7-6."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.2.8.3a","Requirement","ECSS-Q-ST-70-10_0590106",1,"Created","The test shall be carried out in conformance with test 6c of IEC 60326-2-am 1 (1992-06)."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.2.8.4f","Requirement","ECSS-Q-ST-70-10_0590115",1,"Created","The current shall be limited to 100 μA."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.2.8.6c","Requirement","ECSS-Q-ST-70-10_0590127",1,"Created","The nonconformance criteria shall be as follows:\n    1. Discontinuity \t\t\t\t\t\t\t\t\t\t\tM\n    2. Dispersion greater than ±10 % with respect to the mean of values measured on the test pattern \tM"]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.3.2c","Requirement","ECSS-Q-ST-70-10_0590134",1,"Created","The solder shall be tin-lead 60/40 or 63/37 as specified in ECSS-Q-ST-70-08."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.3.2e","Requirement","ECSS-Q-ST-70-10_0590136",1,"Created","The specimens shall be fluxed by immersion."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.3.3.1e","Requirement","ECSS-Q-ST-70-10_0590145",1,"Created","The rate of traction shall be kept constant at 50 mm/min."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.3.3.2e","Requirement","ECSS-Q-ST-70-10_0590154",1,"Created","A tinned copper wire with a diameter of 0,3 mm less than the hole diameter and with a length of approximately 150 mm shall be soldered onto the pad."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.3.3.3e","Requirement","ECSS-Q-ST-70-10_0590164",1,"Created","The alternating movement shall be such that the loop moves at least 25 mm and that the specimen is not curved at either end."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.3.4.1b","Requirement","ECSS-Q-ST-70-10_0590173",1,"Created","The test shall be carried out on SnPb finished boards before reflow of test board."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.3.4.3.2a","Requirement","ECSS-Q-ST-70-10_0590183",1,"Created","The test shall be carried out on a microsection."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.3.4.3.2j","Requirement","ECSS-Q-ST-70-10_0590192",1,"Created","The nonconformance criteria for the distance between SnPb and Au overlap and the termination pad designated for soldering shall be as follows:\n    1. Distance < 200 μm \t\t\t\t\t\t\t\t\t\tM"]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.3.4.3.3f","Requirement","ECSS-Q-ST-70-10_0590201",1,"Created","The nonconformance criteria for voids in PCB base laminate substrate and resin recession in holes (see Figure 7-14) shall be as follows:\n    1. Voids in the PCB base laminate substrate:\n        (a) Lc > 80 mm \t\t\t\t\t\t\t\t\t\tM\n    2. At edge of metal-plating:\n        (a) Sum of resin recession hc > 20 % sum hi \t\t\t\t\t\tM\n    3. Resin recession in hole before or after test:\n        (a) Resin recession between 10 % and 20 % of height of hole \t\t\t\tm\n        (b) If resin recession > 20 % of height of hole \t\t\t\t\t\tM                                    "]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.3.5.1.2g","Requirement","ECSS-Q-ST-70-10_0590211",1,"Created","The nonconformance criteria shall be as follows:\n    1. Electrical discontinuity \t\t\t\t\t\t\t\t\tM\n    2. Blistering visible to the naked eye \t\t\t\t\t\t\t\tM\n    3. Variation in interconnection resistance increased by more than +10 % \t\t\tM"]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.3.5.2b","Requirement","ECSS-Q-ST-70-10_0590215",1,"Created","The test shall be carried out in an insulation area in conformance with Figure 7-16."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.3.6.1d","Requirement","ECSS-Q-ST-70-10_0590222",1,"Created","It shall be placed in a de-ionized water bath maintained at (23 ± 0,5) °C."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.4.1a","Requirement","ECSS-Q-ST-70-10_0590231",1,"Created","The PCB number 3 shall be used for the tests."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.4.2.2b","Requirement","ECSS-Q-ST-70-10_0590239",1,"Created","A thermal shock shall be applied to the whole board of the test board by immersion in the vapour phase of a fluorinated chemical bath."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.4.3e","Requirement","ECSS-Q-ST-70-10_0590250",1,"Created","The wires shall be inserted in the holes and soldered to the terminal areas using a conventional soldering iron, operating at a tip temperature of (270 ± 10) °C."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.5e","Requirement","ECSS-Q-ST-70-10_0590262",1,"Created","The number of cycles shall be 200."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.6.2b","Requirement","ECSS-Q-ST-70-10_0590269",1,"Created","The test conditions shall be:\n    1. Temperature: (40 ± 2) °C.\n    2. Relative humidity: 93 % (+2 %, -3 %).\n    3. Duration of test: 10 days.\n    4. No operation during test."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.6.3g","Requirement","ECSS-Q-ST-70-10_0590278",1,"Created","The specimen shall be exposed in the steam generator machine for approximately 80 min."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.6.3k","Requirement","ECSS-Q-ST-70-10_0590282",1,"Created","The nitrogen flow shall be switched off."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","7.6.3r","Requirement","ECSS-Q-ST-70-10_0590289",1,"Created","The nonconformance criteria shall be as follows:\n    1. Poor wettability of conductors, terminal pads and plated-through holes: see Figure 7-7 for terminal pads and plated-through holes M\n    2. Microsectioning (if necessary): broken metallization \t\t\t\t\tM\n    3. Evidence of corrosion \t\t\t\t\t\t\t\tM"]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","8.5b","Requirement","ECSS-Q-ST-70-10_0590300",1,"Created","The PCB manufacturer shall record any suspected or actual equipment failure as a nonconformance report according to ECSS-Q-ST-20.\n    NOTE This is to ensure that previous manufacturing results are examined to ascertain whether or not a re-inspection or re-testing is necessary."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","8.11c","Requirement","ECSS-Q-ST-70-10_0590308",1,"Created","The quality test specimen representative of the PCB and produced on the same panel shall be subjected to continuity test, solderability test and thermal stress test.\n    NOTE Other specific test can be agreed with the customer."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","9.1e","Requirement","ECSS-Q-ST-70-10_0590318",1,"Created","The limits for the electrical characteristics shall be as follows:\n1.\tInsulation resistance:\n(a)\tIntralayer (i.e. in the same layer): > 104 MW;\n(b)\tInterlayer (i.e. between opposite layers): > 105 MW;\n2.\tWithstanding voltage per mm spacing between conductors:\n(a)\tIntralayer and interlayer: 1 000 V r.m.s;\n3.\tShort time overload:\n(a)\t0,035 mm copper thickness: 7 A for 4 s;\n(b)\t0,070 mm copper thickness: 14 A for 4 s;\n4.\tLong time overload, destructive current:\n(a)\t0,035 mm copper thickness: I ³ 8 A;\n(b)\t0,070 mm copper thickness: I ³ 16 A."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","9.3d","Requirement","ECSS-Q-ST-70-10_0590327",1,"Created","The limits for the mechanical characteristics shall be as follows:\n1.\tConductor adhesion/peel strength: ³ 10 N/cm;\n2.\tPull strength:\n(a)\tFor terminal pads 4 mm Æ: ³ 60 N;\n(b)\tFor terminal pads 2 mm Æ: ³ 12 N;\n3.\tResistance to bending cycles: ³ 250 cycles;\n4.\tBending test for rigid­flex boards: ³ 25 cycles."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","9.6a","Requirement","ECSS-Q-ST-70-10_0590336",1,"Created","The base materials shall be in conformance with ECSS-Q-ST-70, IEC specifications and IPC-4101 and shall be one of the following:\n1.\tWoven­glass­reinforced epoxy resin;\n2.\tWoven­glass­reinforced polyimide resin;\n3.\tWoven­glass­reinforced bismaleimide/trazine modified epoxy (HTg) resin;\n4.\tNon­woven­aramide­reinforced polyimide resin."]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","9.6c","Requirement","ECSS-Q-ST-70-10_0590338",1,"Created","The limits for the electrolytic coatings shall be as follows:\n1.\tElectrolytic copper plating:\n(a)\tMinimum purity: 99,5 %;\n(b)\tThickness of surface pattern: ³ 25 mm;\n(c)\tThickness of plated­through holes: ³ 25 mm;\n(d)\tThickness of via holes: ³ 20 mm;\n(e)\tThickness of buried via holes: ³ 18 mm;\n(f)\tThickness of blind via holes: ³ 18 mm;\n2.\tTin lead plating after reflow:\n(a)\tTin content of alloy: (63 ± 8) %;\n(b)\tThickness on surface: ³ 8 mm in highest part;\n(c)\tThickness in plated­through holes: ³ 8 mm highest part (minimum half height of hole wall);\n(d)\tOn corner angle: ³ 2 mm;\n3.\tElectrolytic gold plating:\n(a)\tMinimum purity: 99,8 % \n(b)\tNot containing more than 0,2 % silver;\n(c)\tThickness on nickel: (4 ± 3) mm;\n(d)\tThickness on copper: (5 ± 2) mm;\n4.\tElectrolytic nickel plating:\n(a)\tThickness: 2 mm to 10 mm;\nNOTE \tIt is optional under gold.\n\n\t\t\t5.\tResin fill in buried vias: see 7.3.4.3.3h;\n\t\t\t6.\tInsulation between layers: 70 mm minimum.\n"]
["ECSS-Q-ST-70-10C","ECSS - Superseded v1.0","B.2.1<2>a","Requirement","ECSS-Q-ST-70-10_0590347",1,"Created","The report shall contain the visual inspection parameters."]
["ECSS-Q-ST-70-11C","ECSS - Superseded v1.0","5.1.1b","Requirement","ECSS-Q-ST-70-11_0600002",1,"Created","The supplier shall perform the incoming inspection and control of the delivered PCBs."]
["ECSS-Q-ST-70-11C","ECSS - Superseded v1.0","5.1.2j","Recommendation","ECSS-Q-ST-70-11_0600158",1,"Created","For surface mount technology and circuits to be wave soldered, only pads on the external layer should be used.\n    NOTE This is done because high density circuitry on external layers is not reliable."]
["ECSS-Q-ST-70-11C","ECSS - Superseded v1.0","5.2.3.1a","Requirement","ECSS-Q-ST-70-11_0600020",1,"Created","The PCB shall be manufactured with copper of purity of at least 99,5 %."]
["ECSS-Q-ST-70-11C","ECSS - Superseded v1.0","5.2.3.4a","Requirement","ECSS-Q-ST-70-11_0600031",1,"Created","The PCB manufacturer shall use gold for high frequency circuits or other assembly methods when specified by the supplier."]
["ECSS-Q-ST-70-11C","ECSS - Superseded v1.0","5.3.1a","Requirement","ECSS-Q-ST-70-11_0600040",1,"Created","The PCB manufacturer shall mark the PCBs as follows:\n    1. PCB manufacturer’s logo\n    2. PCB reference code and serial number\n        NOTE In the event that there is not sufficient space on the PCBs for the marking, the PCB manufacturer can ensure traceability by other means or request for waiver.\n    3. Number of layers."]
["ECSS-Q-ST-70-11C","ECSS - Superseded v1.0","5.3.3c","Requirement","ECSS-Q-ST-70-11_0600049",1,"Created","The PCB manufacturer shall deliver the data package to the supplier."]
["ECSS-Q-ST-70-11C","ECSS - Superseded v1.0","5.4.2f","Requirement","ECSS-Q-ST-70-11_0600059",1,"Created","Desiccant or dry nitrogen filling shall be used in the packaging."]
["ECSS-Q-ST-70-11C","ECSS - Superseded v1.0","5.5.1b","Requirement","ECSS-Q-ST-70-11_0600067",1,"Created","The supplier shall visually inspect each of the delivered PCBs in conformance with the procedure shown in clause 6."]
["ECSS-Q-ST-70-11C","ECSS - Superseded v1.0","5.5.2a","Requirement","ECSS-Q-ST-70-11_0600070",1,"Created","The supplier and the PCB manufacturer shall agree on the electrical test to be performed by the PCB manufacturer."]
["ECSS-Q-ST-70-11C","ECSS - Superseded v1.0","6.2.2g","Requirement","ECSS-Q-ST-70-11_0600081",1,"Created","The nonconformance criteria for the surface metallization shall be as follows:\n1.\tConductors or pads not conforming to supplier’s specification\tM\n2.\tTerminal pads or conductors partially or completely missing...............................................M\n3.\tTerminal pads or conductors that are cut\tM\n4.\tTerminal pads or conductors forming a short circuit...........................................................M\n5.\tLifting/delamination of conductive pattern from substrate....................................................M\n6.\tScratches in the SnPb metallisation exposing the underlaying copper plating\tM\n7.\tCopper or nickel visible on top surface plated areas\tM\nNOTE \tExposed copper can be accepted on the side of tracks or on the side of soldering pads.\n8.\tLarge number of superficial scratches not attributed to a manufacturing process evidencing bad workmanship\tM\n9.\tDewetting of fused tin lead finish on solder pads\tM\n10.\tGranular surface structure of fused tin lead finish on solder pads\tm/M\n11.\tCorrosion of exposed copper...........................................................................................M\n12.\tMigration of underlaying copper through gold coating.........................................................M"]
["ECSS-Q-ST-70-11C","ECSS - Superseded v1.0","6.2.4c","Requirement","ECSS-Q-ST-70-11_0600089",1,"Created","The maximum bow between the plane horizontal surface and the PCB shall be measured as defined in Figure 6-4."]
["ECSS-Q-ST-70-11C","ECSS - Superseded v1.0","6.2.5f","Requirement","ECSS-Q-ST-70-11_0600099",1,"Created","The nonconformance criteria shall be as follows:\n1.\tTwist > requirement\tM"]
["ECSS-Q-ST-70-11C","ECSS - Superseded v1.0","6.3.2j","Requirement","ECSS-Q-ST-70-11_0600112",1,"Created","The nonconformance criteria for the distance between SnPb and Au overlap and the termination pad designated for soldering shall be as follows:\n1.\tDistance < 200 mm\tM"]
["ECSS-Q-ST-70-11C","ECSS - Superseded v1.0","6.3.3d","Requirement","ECSS-Q-ST-70-11_0600119",1,"Created","The nonconformance criteria for the layer misregistration on the internal layers (see Figure 6-6) shall be as follows:\n1.\tdi < requirement\tM\n2.\tMinimum insulation between layers < requirement\tM"]
["ECSS-Q-ST-70-11C","ECSS - Superseded v1.0","6.3.3f","Requirement","ECSS-Q-ST-70-11_0600121",1,"Created","The nonconformance criteria for voids in PCB base laminate substrate and resin recession in holes (see Figure 6-12) shall be as follows:\n1.\tVoids in the PCB base laminate substrate:\n(a)\tLc > 80 mm..............................................................................................................M\n2.\tAt edge of metal­plating:\n(a)\tSum of resin recession hc > 20 % sum hi\tM\n3.\tResin recession in hole before or after test:\n(a)\tResin recession between 10 % and 20 % of height of hole\tm\n(b)\tIf resin recession > 20 % of height of hole\tM"]
["ECSS-Q-ST-70-11C","ECSS - Superseded v1.0","7.2b","Requirement","ECSS-Q-ST-70-11_0600130",1,"Created","The limits for the dimensional characteristics shall be as follows:\n1.\tExternal dimension tolerance: ±0,2 mm;\n2.\tThickness tolerance: ±10 %;\n3.\tActive board size, maximum: supplier’s specification;\n4.\tBoard thickness (minimum/maximum): customer’s and supplier’s specification according to electrical performance;\n5.\tPositioning tolerance between registration mark and edge of circuit: ±0,2 mm;\n6.\tConductor width/spacing: customer’s and supplier’s specification according to electrical performance;\n7.\tTolerance on conductor (minimum/maximum): supplier’s specification;\n8.\tTolerance on diameter of terminal pads: customer’s and supplier’s specification according to electrical performance;\n9.\tMinimum hole diameter:\n(a)\tComponent hole: in conformance with ECSS-Q-ST-70-08;\n(b)\tVia hole: 0,25 mm minimum \t\nand maximum aspect ratio t/d = 6;\n10.\tTolerance on diameter of plated­through holes:\n(a)\tNominal Æ ³ 0,7: D maximum 0,15 mm for component hole;\n(b)\tNominal Æ < 0,7: D maximum 0,20 mm;\n11.\tTolerance on diameter of non­plated­through holes: \nD maximum 0,20 mm;\n12.\tPositioning tolerance of holes with respect to reference mark: ±0,1 mm;\n13.\tRelative misregistration pad/hole: £ 0,15 mm;\n14.\tMisalignment determined by measuring minimum annular ring:\n(a)\tSolder side: 0,2 mm;\n(b)\tComponent side (reduced pads): 0,1 mm;\n(c)\tNon­soldering hole: 0,1 mm."]
["ECSS-Q-ST-70-11C","ECSS - Superseded v1.0","7.4a","Requirement","ECSS-Q-ST-70-11_0600139",1,"Created","The requirements for rigid-flex PCBs shall be in conformance with clause 7.3 for the flexible part and clause 7.5 for the rigid part."]
["ECSS-Q-ST-70-11C","ECSS - Superseded v1.0","7.6d","Requirement","ECSS-Q-ST-70-11_0600149",1,"Created","The limits for the mechanical characteristics shall be as follows:\n1.\tWarp and twist: \n£ 1,1 % for board thickness ³ 1,6 mm, \n£ 1,5 % for board thickness < 1,6 mm;\n2.\tConductor adhesion/peel strength:\n(a)\tOn epoxy with Tg < 160 °C: ³ 16 N/cm;\n(b)\tOn epoxy with Tg > 180 °C: ³ 12 N/cm;\n(c)\tOn polyimide: ³ 12 N/cm;\n(d)\tOn bismaleimide/trazine modified epoxy HTg: ³ 12 N/cm;\n(e)\tAramide/polyimide: ³ 6 N/cm;\n3.\tBond strength/pull strength:\n(a)\tFor terminal pads 4 mm Æ on epoxy Tg < 160 °C: ³ 140 N;\n(b)\tFor terminal pads 4 mm Æ on epoxy Tg > 180 °C: ³ 80 N;\n(c)\tFor terminal pads 4 mm Æ on polyimide: ³ 80 N;\n(d)\tFor terminal pads 4 mm Æ on bismaleimide/trazine modified epoxy HTg: ³ 60 N;\n(e)\tFor terminal pads 4 mm Æ on aramide/polyimide: ³ 60 N;\n(f)\tFor terminal pads 2 mm Æ on epoxy Tg < 160 °C: ³ 35 N;\n(g)\tFor terminal pads 2 mm Æ on epoxy Tg > 180 °C: ³ 20 N;\n(h)\tFor terminal pads 2 mm Æ on polyimide: ³ 20 N;\n(i)\tFor terminal pads 2 mm Æ on bismaleimide/trazine modified epoxy HTg: ³ 12 N;\n(j)\tFor terminal pads 2 mm Æ aramide/polyimide: ³ 12 N.\n"]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","5.2a","Requirement","ECSS-Q-ST-70-38_0210006",1,"Created","The PID shall contain a production flow chart which identifies all individual processes, inspections and a summary table that compiles all verified surface mount components and materials \n    NOTE See Annex B for examples."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","6.1a","Requirement","ECSS-Q-ST-70-38_0210017",1,"Created","Records of tool calibration and verification shall be maintained."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","6.6.5a","Requirement","ECSS-Q-ST-70-38_0210026",1,"Created","ECSS-Q-ST-70-08 shall apply for \"Insulation strippers\"."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","6.7.1d","Requirement","ECSS-Q-ST-70-38_0210035",1,"Created","Temperature and time profiles for assembly shall be identified by the supplier and approved by the approval authority."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","6.8.2c","Requirement","ECSS-Q-ST-70-38_0210045",1,"Created","Equipment used to apply solder preforms shall ensure alignment of the preform with the land or device lead and termination."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","6.8.7c","Requirement","ECSS-Q-ST-70-38_0210053",1,"Created","The resolution of the X-ray equipment shall be able to detect solder balls having a diameter of 0,03 mm. "]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","7.1a","Requirement","ECSS-Q-ST-70-38_0210056",1,"Created","Material selection shall be performed in accordance with ECSS-Q-ST-70-71."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","7.2.4d","Requirement","ECSS-Q-ST-70-38_0210065",1,"Created","Neither paste purchased premixed nor paste mixed in-house shall be used if the use-by date or shelf life recommended by the manufacturer of the paste or paste constituents has expired."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","7.5a","Requirement","ECSS-Q-ST-70-38_0210073",1,"Created","ECSS-Q-ST-70-08 shall apply for \"Flexible insulation materials\"."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","7.9.1a","Requirement","ECSS-Q-ST-70-38_0210084",1,"Created","Components and their finishes shall be selected from those approved in conformance with ECSS-Q-ST-60, for “manufacturer and component evaluation” and “Procurement control”."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","7.9.1h","Requirement","ECSS-Q-ST-70-38_0210091",1,"Created","Where wave soldering is used for surface-mount soldering, devices shall be capable of withstanding a minimum of 10 seconds immersion in molten solder at 260 °C."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","7.10a","Requirement","ECSS-Q-ST-70-38_0210103",1,"Created","Adhesives shall be dispensable, non-stringing, and shall have a reproducible dot profile after application. "]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","8.1.2a","Requirement","ECSS-Q-ST-70-38_0210112",1,"Created","ECSS-Q-ST-70-08, clause “Surfaces to be soldered” shall apply."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","8.5c","Requirement","ECSS-Q-ST-70-38_0210120",1,"Created","Baking times and temperatures shall be documented.\n    NOTE 1 Typical baking conditions are from 6 h to 24 h at 125 C depending on the JEDEC classification, except for components delivered in reels for which a lower temperature and longer time are used. \n    NOTE 2 It is good practice to store components under nitrogen, dry air (20 % RH maximum) or partial vacuum."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","9.3a","Requirement","ECSS-Q-ST-70-38_0210123",1,"Created","ECSS-Q-ST-70-08 shall apply for \"Mounting of terminals to PCBs\"."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","9.7.4b","Requirement","ECSS-Q-ST-70-38_0210134",1,"Created","Forming shall not degrade the solderability or cause loss of plating adhesion to the leads."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","9.7.6d","Requirement","ECSS-Q-ST-70-38_0210142",1,"Created","Devices that are bonded to the PCB prior to wave- or reflow-soldering shall be placed so that the requirements after soldering given in clause 11 are met."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","9.7.9f","Requirement","ECSS-Q-ST-70-38_0210152",1,"Created","All devices except area arrays weighing more than 5 g shall be staked. \n    NOTE 1 This is to minimize shock and vibration loading on the leads\n    NOTE 2 The staking compound can be applied either before or after soldering in conformance with the supplier’s process identification document."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","11.5.1d","Requirement","ECSS-Q-ST-70-38_0210161",1,"Created","Mispositioning of devices shall not reduce the specified minimum electrical clearance to adjacent tracks or other metallized elements."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","11.5.6a","Requirement","ECSS-Q-ST-70-38_0210170",1,"Created","Solder joints formed to round, flattened, ribbon, “L” and gull-wing shaped leads shall meet the dimensional and solder fillet requirements of Table 11-5 and Figure 11-5."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","11.5.8a","Requirement","ECSS-Q-ST-70-38_0210172",1,"Created","The outer row of solder joints to area array devices shall be visually inspected by looking from the side in accordance with the requirements in 11.5.1 and Table 11-7 and with the rejection criteria specified in 13.3 and 13.4."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","13.1a","Requirement","ECSS-Q-ST-70-38_0210181",1,"Created","Each soldered connection shall be visually inspected in accordance with the criteria specified in the clauses below."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","13.6a","Requirement","ECSS-Q-ST-70-38_0210190",1,"Created","The result of the final inspection shall be recorded on the shop traveller."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","14.1j","Requirement","ECSS-Q-ST-70-38_0210200",1,"Created","Verification by similarity shall not be used for moisture sensitive components."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","14.2f","Requirement","ECSS-Q-ST-70-38_0210208",1,"Created","The metallization of the termination and the barrier layers on leadless devices shall be identical."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","14.6b","Requirement","ECSS-Q-ST-70-38_0210219",1,"Created","The total number of temperature cycles shall be 500, except for area array devices with conformal coating when clause 14.9.2 is applicable."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","14.8b","Requirement","ECSS-Q-ST-70-38_0210228",1,"Created","The dye penetrant test results and samples shall be stored for a period of at least 10 years.\n    NOTE 1 Stored samples can assist the analysis of in-service failures.\n    NOTE 2 Conformal coatings and underfills can lead to non-inspectability and difficulties for rework or repair."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","14.10d","Requirement","ECSS-Q-ST-70-38_0210237",1,"Created","Surface and internal cracks that penetrate less than 25 % of the solder fillet critical zone (as defined in Figure 14-2), ball or column, shall be considered acceptable."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","15.2a","Requirement","ECSS-Q-ST-70-38_0210247",1,"Created","ECSS-Q-ST-70-08 shall apply for \"Data\"."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","15.7c","Requirement","ECSS-Q-ST-70-38_0210255",1,"Created","The inspection shall also include the substrate, components and component position in accordance with clauses 11.5.1 to 11.5.8."]
["ECSS-Q-ST-70-38C","ECSS - Superseded v1.0","15.8c","Requirement","ECSS-Q-ST-70-38_0210258",1,"Created","Operators performing hand soldering of SMDs, and inspectors of SMD and mixed-technology assemblies shall be trained and certified at a school authorised by the final customer."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.2.4c","Requirement","ECSS-Q-ST-20_0380012",2,"Normative Change","The use of acceptance authority media shall be restricted to authorized personnel as identified in the acceptance authority media control system."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.2.4g","Permission","ECSS-Q-ST-20_0380231",1,"Created","<<deleted>>"]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.2.6d","Requirement","ECSS-Q-ST-20_0380025",1,"Unchanged","The supplier shall record the basis for the calculation of the cumulative errors as specified in requirement 5.2.6c."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.2.6k","Requirement","ECSS-Q-ST-20_0380032",1,"Unchanged","The supplier shall assess and document the validity of previous inspection and test results when inspection, measuring or test equipment is found to be out of calibration."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.2.7.2e","Requirement","ECSS-Q-ST-20_0380044",1,"Unchanged","The supplier shall maintain records to ensure that all stored items are within the usable life limits, controlled and retested, and to provide traceability within the storage or segregated area."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.2.8.2a","Requirement","ECSS-Q-ST-20_0380049",1,"Unchanged","When sampling plans are used the supplier shall define and justify the following:\n1.\tsample size, sample selection methods and criteria for inspection severity, \n2.\tacceptance / rejection criteria, and \n3.\tscreening of rejected lots."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.3.1.4a","Requirement","ECSS-Q-ST-20_0380054",2,"Informative Change","The supplier shall ensure that the product is designed such that it can be operated in accordance with programme constraints and requirements, throughout its whole life cycle including handling, storage, transportation, integration and operations."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.3.2.4.1a","Requirement","ECSS-Q-ST-20_0380063",1,"Informative Change","The supplier shall ensure that all configuration items and their constituent items, either off-the-shelf or specifically designed, are properly qualified with margins commensurate with the application and use environment.\nNOTE \tFor equipment with heritage, an Equipment Qualification Status Review can be organised to assess qualification status."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.3.2.4.4a","Requirement","ECSS-Q-ST-20_0380072",1,"Unchanged","The supplier shall report the qualification status in conformance with the “Qualification status list” DRD as defined in ECSS-Q-ST-10."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.4.2b","Requirement","ECSS-Q-ST-20_0380081",1,"Unchanged","The supplier shall ensure that requirements to those contained in lower tier procurement documents are traceable."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.4.4.1c","Requirement","ECSS-Q-ST-20_0380091",1,"Unchanged","Receiving inspectors shall have available the procurement documents, specifications, drawings and any other document relevant to incoming supplies as required in the procurement documents."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.5.1f","Requirement","ECSS-Q-ST-20_0380100",1,"Unchanged","Only “first off” shop travellers shall be reviewed unless subsequent travellers incorporate a significant change of inspection requirements or order of events."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.5.3.3a","Recommendation","ECSS-Q-ST-20_0380233",1,"Created","Statistical methods for process control should be used for early detection of significant variations in manufacturing processes, in order to determine, analyse and eliminate the causes of undesirable variations."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.5.6.1d","Requirement","ECSS-Q-ST-20_0380119",2,"Normative Change","The approval shall be marked in conformance with 5.2.4, and recorded."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.5.7.1a","Requirement","ECSS-Q-ST-20_0380127",1,"Unchanged","The supplier shall establish controls for cleanliness of spacecraft hardware and facilities, and the limitation of sources of contamination.\nNOTE \tCleanliness and contamination control methods and processes are detailed in ECSS-Q-ST-70-01."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.5.7.3a","Requirement","ECSS-Q-ST-20_0380130",1,"Unchanged","The supplier shall develop detailed methods for attaining the cleanliness levels specified for the hardware."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.5.8e","Requirement","ECSS-Q-ST-20_0380139",2,"Normative Change","MIPs shall be agreed with the customer on the basis of a list prepared by the supplier.\nNOTE \tThis list may be part of another deliverable document."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.5.9.1c","Requirement","ECSS-Q-ST-20_0380146",1,"Unchanged","The supplier shall establish and maintain records of temporary installations and removals."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.6.2a","Requirement","ECSS-Q-ST-20_0380155",1,"Unchanged","The supplier shall ensure that computer-aided testing techniques and data are validated prior to use and controlled during their use in testing."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.6.4a","Requirement","ECSS-Q-ST-20_0380162",2,"Normative Change","On the basis of an analysis of the test plan, the QA organization shall define within the test plan the way to monitor the performance of test activities, to ensure the adherence to the test procedures, and that any deviations are properly documented and treated."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.7.2b","Requirement","ECSS-Q-ST-20_0380174",1,"Unchanged","The EIDP shall constitute the basis for formal acceptance reviews."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.7.4.1a","Requirement","ECSS-Q-ST-20_0380183",1,"Unchanged","The supplier shall ensure that packaging materials, methods, procedures and instructions provide for protection of items while at the supplier’s plant, during transportation, and after their arrival at destination."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.8.1.1.1a","Requirement","ECSS-Q-ST-20_0380234",1,"Created","<< deleted, requirement moved to 5.8.1a >>"]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.8.2a","Requirement","ECSS-Q-ST-20_0380191",1,"Unchanged","The supplier shall ensure that GSE is configuration controlled."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.8.6b","Requirement","ECSS-Q-ST-20_0380243",1,"Created","<< deleted, requirement moved to 5.8.4.3b>>"]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","5.8.9b","Requirement","ECSS-Q-ST-20_0380204",1,"Unchanged","The supplier shall ensure that maintenance demonstration is performed in order to prove that maintainability requirements are satisfied in the real operational environment."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","A.2.1<5>a","Requirement","ECSS-Q-ST-20_0380209",1,"Unchanged","The Quality Assurance Plan shall describe the activities to be applied to fulfil the applicable Quality assurance requirements for procurement defined in ECSS-Q-ST-20 clause 5.4."]
["ECSS-Q-ST-20C Rev.1","ECSS - Superseded v1.0","C.2.1h","Requirement","ECSS-Q-ST-20_0380222",1,"Unchanged","The logbook shall contain, in chronological order, the events related to the integration and test activities performed on the relevant item (i.e. system, subsystem, and equipment), including the following:\n1.\tAction requested form, reporting all the operations performed with the references to the applicable documents or procedures, start date, completion date and quality inspection stamps.\n2.\tStep-by-step procedures and results, in which copies of the as-run procedures are included in a suitable format.\n3.\tProcedures variation form, in which copies of modified procedures (red marked) identified with a procedure variation number and duly approved by responsible authorities, are included. "]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","4.1.3e","Requirement","ECSS-Q-ST-70_0490196",1,"Created","To obtain the validation status for materials and qualification status for parts and verification status for processes, the MMPP manager shall present to the customer activities which were performed in conformance with requirement 4.1.3d together with the results obtained."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","4.2.2b","Requirement","ECSS-Q-ST-70_0490006",2,"Normative Change","The lists specified in 4.2.2a shall reflect the current design at the time of issue."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","4.2.2g","Requirement","ECSS-Q-ST-70_0490011",2,"Normative Change","For items classified as critical in conformance with 4.2.2f.1 a request for approval shall be submitted in conformance with Annex D."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","4.2.3h","Requirement","ECSS-Q-ST-70_0490019",1,"Unchanged","Any change after CDR or QR shall be reflected in the list and shall be in accordance with Figure 4-1 (Part 2).\nNOTE \t1\tThe MMPP manager is responsible within the programme to ensure that all the information needed is given and that the approval status is consistent with technical and scheduling objectives and data is exchangeable.\nNOTE \t2\tWhere no project requirements exist for a separate DMPL, the mechanical parts can be entered into a separate section of the DML.\nNOTE \t3\tThe materials of, for example, screws and nuts that are made up of a few materials can be listed in the DMPL. The materials (metals and plastics) of complex parts can be listed in the DML with, for example, outgassing, toxicity, flammability, corrosion and stress corrosion values and reference to the DMPL item."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","4.3c","Requirement","ECSS-Q-ST-70_0490027",2,"Deleted","<< deleted >>"]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","5.1.1a","Requirement","ECSS-Q-ST-70_0490204",1,"Created","Material design data shall be generated for the intended service conditions using test and analysis procedures approved by the customer."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","5.1.4d","Recommendation","ECSS-Q-ST-70_0490271",1,"Created","The need for retest outgassing characteristics of materials used for an extended period of time at a temperature higher than 50 °C should be mutually agreed with the customer.\nNOTE \tWhen dynamic outgassing tests are required see ECSS-Q-TM-70-52."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","5.1.7d","Requirement","ECSS-Q-ST-70_0490213",1,"Created","In case synergistic testing is not possible it shall be proven that synergistic effects caused by radiation and temperature are not degrading the materials properties."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","5.1.11c","Requirement","ECSS-Q-ST-70_0490216",1,"Created","The compatibility of materials which are or can come into contact with LOX or GOX shall be evaluated except the case specified in the requirement 5.1.11d.\nNOTE \tSee NASA-STD-6001 Tests No. 13 and No. 14."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","5.1.14c","Requirement","ECSS-Q-ST-70_0490220",1,"Created","Micrometeoroids and debris analysis and test procedures shall be subject to the approval by the customer."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","5.1.18d","Requirement","ECSS-Q-ST-70_0490225",1,"Created","The level of bacterial growth and fungus contamination shall be determined on the assembled hardware."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","5.1.19b","Requirement","ECSS-Q-ST-70_0490228",1,"Created","The material evaluation specified in 5.1.19a shall be performed including the assessment of a protection and control."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","5.2.2c","Requirement","ECSS-Q-ST-70_0490239",1,"Created","Cadmium and Zinc shall not be used as raw material or surface treatment for flight hardware."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","5.2.2g","Requirement","ECSS-Q-ST-70_0490243",1,"Created","Beryllium shall not be used for structures."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","5.5.1c","Requirement","ECSS-Q-ST-70_0490070",1,"Unchanged","Guarantied characteristics of materials and material supplier inspection methods, together with associated documents, shall be available for review at the supplier’s premises before the start of evaluation or qualification phases."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","5.5.4b","Requirement","ECSS-Q-ST-70_0490076",2,"Normative Change","If approval is not granted, the supplier in charge of the item shall either:\n1.\tselect another material, or\n2.\tpropose a modified evaluation programme and resubmit for approval, or\n3.\tif actions specified in the requirements 5.5.4b.1 and 5.5.4b.2 fail to achieve positive results, initiate a deviation procedure."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","5.7.2a","Requirement","ECSS-Q-ST-70_0490088",2,"Normative Change","The supplier shall apply the traceability rules specified in the requirements from clause 5.2.5 of ECSS-Q-ST-20 to all materials."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","5.7.5a","Requirement","ECSS-Q-ST-70_0490094",2,"Normative Change","Materials with limited­life after implementation shall be identified and controlled in conformance with requirements from the clause 5 of ECSS-Q-ST-10-04.\nNOTE \t1\tPropellant is an example of material with limited-life after implementation\nNOTE \t2\tStorage and mission life are criteria for the assessment and control of those materials."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","6.2b","Requirement","ECSS-Q-ST-70_0490099",1,"Unchanged","Type reduction actions shall be implemented at all levels of the programme."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","6.5.2c","Requirement","ECSS-Q-ST-70_0490110",1,"Unchanged","The behaviour of the parameters to be monitored which were also recorded during the evaluation programme tests, shall serve as a reference for the analysis of qualification test results.\nNOTE \tExample of such behaviour is variation and change over time."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","6.5.5a","Requirement","ECSS-Q-ST-70_0490115",2,"Normative Change","For mechanical parts not conforming to project requirements, whether at the end of criticality analysis or of evaluation and qualification tests, the supplier shall submit a request for deviation in conformance with requirements from the clause 5.2.3.5 of ECSS-Q-ST-10-09."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","6.6.4a","Requirement","ECSS-Q-ST-70_0490124",2,"Normative Change","Each part or batch of mechanical parts shall be submitted to an incoming inspection."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","6.7.2b","Requirement","ECSS-Q-ST-70_0490251",1,"Created","Parts shall be identified by a unique reference number or code and a lot number to provide traceability - where there is an incident or nonconformance, or for the purposes of technical investigations following failure or damage - to reconstruct the mechanical parts history, either individually (individual traceability) or by the manufacturing lot it was part of (lot traceability)."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","7.3f","Requirement","ECSS-Q-ST-70_0490255",1,"Created","Operators shall be trained for all processes."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","7.4a","Requirement","ECSS-Q-ST-70_0490140",1,"Unchanged","The supplier shall establish and maintain a declared processes list in conformance with Annex C."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","7.6.2a","Requirement","ECSS-Q-ST-70_0490150",2,"Normative Change","The evaluation specified in 7.6.1a shall include the following as a minimum for each critical process:\n1.\tthe limits of use,\n2.\tthe values, determined by test samples or technology samples, of relevant parameters and their tolerances, and\n3.\tacceptance criteria."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","7.6.4b","Requirement","ECSS-Q-ST-70_0490265",1,"Created","In case approval specified in the requirement 7.6.4a is not granted, the supplier in charge of the item shall either:\n1.\tselect other processes, or\n2.\tpropose a modified evaluation programme and resubmit for approval, or\n3.\tif actions specified in 7.6.4b.1 and 7.6.4b.2 fail to achieve positive results, initiate a deviation procedure."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","7.7.1b","Requirement","ECSS-Q-ST-70_0490159",2,"Normative Change","Any modification, change of condition or configuration of application shall lead to a re-evaluation in conformance with the process.\nNOTE \tSee Figure 4-1."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","A.2.1<1>b","Requirement","ECSS-Q-ST-70_0490168",1,"Unchanged","If new groups are created, for a given project, these shall have numbers over 21."]
["ECSS-Q-ST-70C Rev.1","ECSS - Superseded v1.0","B.2.1<2>a","Requirement","ECSS-Q-ST-70_0490175",2,"Normative Change","The DMPL shall include the information in Figure B-1, where the header information identifies the list as the declared mechanical parts  list and includes the issue number and date of issue, as follows:\n1.\tItem number (applicable at equipment supplier level only)\n(a)\tThis consists of the mechanical part identifier and the user code. It takes the form of:\n<group number>.<identifier within the group>.<running number>.<user code>\nNOTE \tFor example: 7.2.1.ACSA.\n(b)\tCharacteristics of the item number are:\n-\tIdentify the subcontractor by an agreed user code for the project.\n-\tOne only per mechanical part type. \n-\tDoes not change during the life of the mechanical parts list.\n2.\tCommercial identification\n(a)\tEnter the correct and standard designation, such as trade name plus number. \n(b)\tIf no trade name exists then enter the manufacturers’ name and number.\n3.\tType of part\nDescribe the material and surface treatment (if applicable).\n4.\tProcurement information\n(a)\tManufacturer or distributor: name of the manufacturer and name of the distributor if different.\n(b)\tProcurement specification: provide reference to one of the following:\n-\tthe procurement specification with issue, revision and date\n-\ta national or international specification or standard, if this exists, and identifies the source of procurement (if relevant), with issue, revision and date.\n5.\tElementary function, main characteristics\n(a)\tEnter the function of the mechanical part.\n(b)\tEnter the main characteristics of the mechanical part.\nNOTE \tFor example, number of revolutions per minute for a ball bearing.\n6.\tUse and location\nUse codes able to define the location of the mechanical part with respect to the:\n(a)\tsubsystem;\n(b)\tparticular piece of equipment (box or item);\n(c)\tuse of the equipment.\n7.\tEnvironmental code\nThe environmental code is defined using Table B-2.\n8.\tCriticality\nEnter “C” for critical or “N” for non­critical. If a mechanical part is considered critical, describe the reason for the criticality and methods of control.\n9.\tSupplier reference, prime comments and prime approval status \n(a)\tUse the supplier reference, prime comments and approval columns to enter all additional information that are necessary in order to obtain customer approval.\n(b)\tThis information comprises reference and issue of the RFA or approval, mechanical parts justification file, evaluation reports and deviation requests.\n(c)\tMake reference to the relevant test data that demonstrates acceptability of the mechanical part under the environment conditions and the application relevant to the particular project concerned.\n(d)\tUse standard abbreviations, defined by the customer, to summarize the acceptance status of a mechanical part for a particular property.\n(e)\tIn order to justify the use of a material for flammability resistance, list here the material thickness and height of oxygen share.\n(f)\tSelect the prime approval status code from Table B-3.\n10.\tThe customer approval status code and comments\n(a)\tSelect this code from Table B-3. \n(b)      Include additional comments where appropriate."]
["ECSS-Q-ST-70-05C","ECSS - Superseded v1.0","5.1.1a","Requirement","ECSS-Q-ST-70-05_0540001",1,"Created","Unavoidable hazards to personnel equipment and materials shall be controlled by risk management procedures and kept to a minimum."]
["ECSS-Q-ST-70-05C","ECSS - Superseded v1.0","5.1.2.1a","Requirement","ECSS-Q-ST-70-05_0540008",1,"Created","The work area shall be clean and free of dust."]
["ECSS-Q-ST-70-05C","ECSS - Superseded v1.0","5.1.6a","Requirement","ECSS-Q-ST-70-05_0540020",1,"Created","The following items shall be used for acquiring and preparing the samples:\n    1. Pre-cleaned standard filter paper of 70 mm diameter.\n        NOTE For orientation on the cleaning process see F.2.3.\n    2. Piece of pre-cleaned foam rubber, approximately (50 x 30) mm.\n        NOTE See F.2.3.\n    3. A PTFE film can be used to protect the foam rubber.\n    4. Clean, powder-free and lint-free gloves.\n    5. Spectral grade solvents.\n    6. Petri dishes ranging in diameter from (50 - 70) mm.\n    7. Glass rod or micro-syringe.\n    8. Glass syringe.\n    9. Tweezers.\n    10. Infrared lamp."]
["ECSS-Q-ST-70-05C","ECSS - Superseded v1.0","5.2.3.3c","Requirement","ECSS-Q-ST-70-05_0540029",1,"Created","The cleaned tissue shall be stored/kept in a clean container."]
["ECSS-Q-ST-70-05C","ECSS - Superseded v1.0","5.3b","Requirement","ECSS-Q-ST-70-05_0540037",1,"Created","The surface area for the direct methods shall be based on the diameter of the IR beam diameter at the position of the sample window."]
["ECSS-Q-ST-70-05C","ECSS - Superseded v1.0","5.4.1a","Requirement","ECSS-Q-ST-70-05_0540040",1,"Created","Quality assurance records and log sheets shall be retained for ten years after they have been established."]
["ECSS-Q-ST-70-05C","ECSS - Superseded v1.0","5.4.3.1m","Requirement","ECSS-Q-ST-70-05_0540055",1,"Created","The standards materials shall be conserved in a cool and dark area and the evaporation of chloroform limited by sealing the measuring flask."]
["ECSS-Q-ST-70-05C","ECSS - Superseded v1.0","5.4.3.2d","Requirement","ECSS-Q-ST-70-05_0540059",1,"Created","Each point shall be measured at least three times, possibly with different windows in order to eliminate systematic errors."]
["ECSS-Q-ST-70-05C","ECSS - Superseded v1.0","5.4.3.3e","Requirement","ECSS-Q-ST-70-05_0540064",1,"Created","The detection limit of the analysis shall be specified and reported in Mass/specific area."]
["ECSS-Q-ST-70-05C","ECSS - Superseded v1.0","5.4.5.2c","Requirement","ECSS-Q-ST-70-05_0540078",1,"Created","Trained personnel performing calibration and analysis shall be certified."]
["ECSS-Q-ST-70-05C","ECSS - Superseded v1.0","5.5.2b","Requirement","ECSS-Q-ST-70-05_0540087",1,"Created","The initial audit shall consist of: \n    1. inspecting the apparatus and associated equipment,\n    2. assessing the performance of a test on a defined set of materials,\n    3. reporting the non-conformances, and \n    4. reporting the audit findings."]
["ECSS-Q-ST-70-05C","ECSS - Superseded v1.0","5.5.4b","Requirement","ECSS-Q-ST-70-05_0540093",1,"Created","The customer shall audit the modifications, if deemed necessary, before utilization of the modified system for the customer’s project."]
["ECSS-Q-ST-70-31C","ECSS - Superseded v1.0","4.1.1b","Requirement","ECSS-Q-ST-70-31_0660002",1,"Created","Depending on the specific project requirements, the paint applied shall fulfil part or all the acceptance criteria given in 4.4 of this Standard."]
["ECSS-Q-ST-70-31C","ECSS - Superseded v1.0","4.2.2.1d","Requirement","ECSS-Q-ST-70-31_0660015",1,"Created","Coated surfaces shall be shielded from contact by using appropriate bags or sheets.\n    ","NOTE The suitable bags are for example plastic bags with desiccators, sheet of tissue-paper, sheet of polyethylene foam."]
["ECSS-Q-ST-70-31C","ECSS - Superseded v1.0","4.2.2.3b","Requirement","ECSS-Q-ST-70-31_0660021",1,"Created","These samples shall be of the same material and be surface treated in the same manner as the workpiece."]
["ECSS-Q-ST-70-31C","ECSS - Superseded v1.0","4.2.4.2b","Permission","ECSS-Q-ST-70-31_0660109",1,"Created","The ambient conditions specified in 4.2.4.2a may be different, providing that are qualified for the specific process."]
["ECSS-Q-ST-70-31C","ECSS - Superseded v1.0","4.2.5f","Requirement","ECSS-Q-ST-70-31_0660040",1,"Created","Brushes shall be new or cleaned after use with a proper solvent."]
["ECSS-Q-ST-70-31C","ECSS - Superseded v1.0","4.3.1.2e","Requirement","ECSS-Q-ST-70-31_0660049",1,"Created","When cleaning with tissues, the single wipe approach shall be used."]
["ECSS-Q-ST-70-31C","ECSS - Superseded v1.0","4.3.1.3d","Requirement","ECSS-Q-ST-70-31_0660053",1,"Created","The hardware shall be protected from random temperature extremes, high humidity and physical damage."]
["ECSS-Q-ST-70-31C","ECSS - Superseded v1.0","4.3.4.1c","Requirement","ECSS-Q-ST-70-31_0660068",1,"Created","The amount of thinner/solvent shall be established by making test pieces which bear a strongly adhering, homogeneous layer.\n    ","NOTE The amount of thinner/solvent needed depends on the type of spray gun that is used."]
["ECSS-Q-ST-70-31C","ECSS - Superseded v1.0","4.3.4.2a","Requirement","ECSS-Q-ST-70-31_0660076",1,"Created","Unmasking shall be performed after the paint is sufficiently dried or cured to avoid damage."]
["ECSS-Q-ST-70-31C","ECSS - Superseded v1.0","4.3.4.2d","Requirement","ECSS-Q-ST-70-31_0660079",1,"Created","If masking tape adhesive remains on the surface, no attempt shall be made to clean it off until after the final cure."]
["ECSS-Q-ST-70-31C","ECSS - Superseded v1.0","4.3.6.3b","Requirement","ECSS-Q-ST-70-31_0660094",1,"Created","For spray gun, painting shall consist in:\n    1. applying the paint using the spray gun as soon as the thinner has evaporated;\n    2. applying the primer as described in technical data sheet, if the primer needs to be repaired;\n    3. applying the paint after complete drying."]
["ECSS-Q-ST-70-31C","ECSS - Superseded v1.0","4.4d","Requirement","ECSS-Q-ST-70-31_0660098",1,"Created","Adhesion properties shall be measured according to ECSS-Q-ST-70-13, ISO 2409:2007 or equivalent national standards."]
["ECSS-Q-ST-70-31C","ECSS - Superseded v1.0","4.5.5a","Requirement","ECSS-Q-ST-70-31_0660107",1,"Created","Traceability shall be maintained throughout the process from incoming inspection to final test, including details of test equipment and personnel employed in performing the task."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.2.2e","Requirement","ECSS-Q-ST-70-71_1260007",1,"Created","Long-term manned structures, shall not use aluminium alloys 5083-H32, 5083-H38, 5086-H34, 5086-H38, 5456-H32 and 5456-H38 in applications where the temperature exceeds 66 °C."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.2.6b","Requirement","ECSS-Q-ST-70-71_1260019",1,"Created","Tempers of precipitation hardening steels that are susceptible to stress corrosion and hydrogen embrittlement shall not be used."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.2.8b","Requirement","ECSS-Q-ST-70-71_1260025",1,"Created","The fusion zone and the unmelted heat affected zone of a weld shall be accessible for inspection."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.2.8g","Requirement","ECSS-Q-ST-70-71_1260030",1,"Created","Design shall include the effect of the brazing process on the strength of the parent metal.\n","NOTE\tBase metal is the example of the parent metal."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.2.9j","Requirement","ECSS-Q-ST-70-71_1260043",1,"Created","Foreign material which contains sulphur shall be removed from superalloys prior to heat treatment or high-temperature service.\n","NOTE\tExamples of materials that can contain sulphur are: oils, grease and cutting lubricants."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.2.11a","Requirement","ECSS-Q-ST-70-71_1260049",1,"Created","The surfaces on which the adhesives, coatings or varnishes are applied shall be clean and dry prior to their application."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.2.11j","Requirement","ECSS-Q-ST-70-71_1260058",1,"Created","Any compound that contains or releases corrosive media that can attack adjacent parts of the assembly shall be assessed for its potential risk.\n","NOTE\tExamples of corrosive media are: acetic acid, ammonia, amines, hydrochloric and other acids."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.2.12a","Requirement","ECSS-Q-ST-70-71_1260063",1,"Created","Tapes containing polyvinylchloride shall not be used in space segment elements or ground segment equipment undergoing vacuum."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.2.13b","Requirement","ECSS-Q-ST-70-71_1260076",1,"Created","Contamination of painted surfaces shall be prevented.\n","NOTE\tFor non-moisture curing paints, environmental control applies."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.2.14b","Requirement","ECSS-Q-ST-70-71_1260080",1,"Created","Lubricants shall only be applied to clean surfaces."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.2.15j","Requirement","ECSS-Q-ST-70-71_1260095",1,"Created","All potting, coating and sealing materials used successively shall be evaluated for compatibility.\n","NOTE\tSome chemical or atmospheric constituents can affect those of another material."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.2.16b","Requirement","ECSS-Q-ST-70-71_1260098",1,"Created","Composite materials made with polyester containing styrene shall not be used."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.2.17d","Requirement","ECSS-Q-ST-70-71_1260106",1,"Created","Silicone materials shall not be used in pressurized systems requiring low gas permeability."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.2.17m","Requirement","ECSS-Q-ST-70-71_1260114",1,"Created","For rubbers and elastomers, environmental exposure shall be assessed.\n","NOTE\tExamples of environmental exposure are: flammability requirements, electrical requirements, normal use temperature, abnormal use temperature excursions, chemical exposure and humidity levels. "]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.2.18l","Requirement","ECSS-Q-ST-70-71_1260126",1,"Created","Materials that absorb and release water shall be assessed with respect to the effect on the performance of the material and for contamination risk."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.2.19a","Requirement","ECSS-Q-ST-70-71_1260133",1,"Created","Structural design of components using thermosetting resins shall conform to the requirements of clause 4 of ECSS-E-ST-32-08.\n","NOTE\tExamples of thermoset plastics are fibre reinforced composites."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.2.20c","Requirement","ECSS-Q-ST-70-71_1260140",1,"Created","Coaxial, radiofrequency, flexible cables shall be procured in conformance with the requirements ESCC Generic specification 3902."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.3.1f","Requirement","ECSS-Q-ST-70-71_1260152",1,"Created","During the bonding process, the adhesive cure cycle shall be controlled in accordance with an established procedure approved by the customer.\n","NOTE\tFor guidelines on structural adhesive bonding see ECSS-E-HB-32-21."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.3.4c","Requirement","ECSS-Q-ST-70-71_1260161",1,"Created","Pre-treatment processes for the surfaces to be painted shall be selected and controlled to ensure adhesion of the paint to the substrate.\n","NOTE\tPre-treatment processes include for example cleaning, abrasion and priming."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.3.5c","Requirement","ECSS-Q-ST-70-71_1260164",1,"Created","Cleaning processes shall not degrade the base material, any applied surface coating or finishes, or adjacent parts.\n","NOTE \t1\tSurface coatings include for example paint and varnish.\nNOTE \t2\tLabels can also be damaged by cleaning.\nNOTE \t3\tCleaning processes including for example submerging in solvent baths and use of ultrasonic cleaning can induce damage."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.3.6g","Requirement","ECSS-Q-ST-70-71_1260172",1,"Created","Each operator shall be trained and certified in accordance with the requirements from clause 6 and 7 from ECSS-Q-ST-70-39, along with the applicable welding equipment and related procedure for specific welding tasks."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.3.8d","Requirement","ECSS-Q-ST-70-71_1260187",1,"Created","The supplier shall demonstrate that when subsequent fusion welding or brazing is applied, it is not affecting any soldered joints in the vicinity."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.3.9.1d","Requirement","ECSS-Q-ST-70-71_1260191",1,"Created","An assessment shall be performed to demonstrate that the CTE mismatches between coating and substrates, if exist, do not prevent to meet the specified requirements.\n","NOTE \t1\tSurfaces of materials are often treated for the following reasons:\n·\tTo improve properties, e.g. nitriding, carburising and shot-peening.\n·\tTo increase resistance to an environment, e.g. corrosion, moisture- and diffusion barriers, high-temperature and ATOX.\n·\tTo provide particular characteristics, e.g. thermo-optical properties.\nNOTE \t2\tSome surface treatments are also included in other processes, for example preparation prior to painting and adhesive bonding to improve adhesion. These can include a proprietary “chemical” process such as anodizing or alodining or the application of a primer."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.3.9.2e","Requirement","ECSS-Q-ST-70-71_1260196",1,"Created","Process conditions shall be implemented and controlled.\n","NOTE \t1\tProcess conditions include for example bath constituents, temperature and time.\nNOTE \t2\tAnodizing is an electrolytic process for thickening and stabilizing the inherent oxide films on metal substrates. Anodizing is widely used on aluminium alloys and can be applied to magnesium and titanium. The anodized layer is electrically non-conductive. \nNOTE \t3\tNot all grades of an alloy can be anodized successfully.\nNOTE \t4\tDepending on the precise process, anodizing can produce:\n·\thard anodized wear resistant and durable surfaces;\n·\tcoloured surfaces (either functional or decorative), e.g. black for optical properties;\n·\tpre-treatment process prior to adhesive bonding or painting.\nNOTE \t5\tSpecifications for aerospace anodizing processes are available (often of American origin), but bath constituents and process conditions tend to vary between organizations."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.3.12.2a","Requirement","ECSS-Q-ST-70-71_1260210",1,"Created","Forging techniques shall be used that produce an internal grain-flow pattern such that the direction of flow is parallel to principal stresses."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.3.13b","Requirement","ECSS-Q-ST-70-71_1260219",1,"Created","Heat treatment procedures that are not included in any national or international specifications shall be approved by the customer prior to their use."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.3.14e","Requirement","ECSS-Q-ST-70-71_1260225",1,"Created","Stamping resulting in stress-raisers shall not be performed."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.3.15.4a","Requirement","ECSS-Q-ST-70-71_1260230",1,"Created","Fabrication processes and controls used in staking and conformal coating of printed circuit boards and electronic assemblies shall conform to the requirements of from clause 5 to clause 15 of ECSS-Q-ST-70-08, from clause 5 of ECSS-Q-ST-70-07 and from clause 5 to clause 16 of ECSS-Q-ST-70-38."]
["ECSS-Q-ST-70-71C","ECSS - Superseded v1.0","4.3.16d","Requirement","ECSS-Q-ST-70-71_1260243",1,"Created","Inspection equipment shall be maintained and calibrated in conformance with the clause 5.2.6 from ECSS-Q-ST-20."]
["ECSS-Q-ST-60-14C","ECSS - Superseded v1.0","4.1.4d","Requirement","ECSS-Q-ST-60-14_0470007",1,"Created","Storage areas shall conform to a cleanliness level as defined in ECSS-Q-ST-70-01 clause 5.3.1.4. \n    ","NOTE This cleanliness level is often called and known as “grey zone”."]
["ECSS-Q-ST-60-14C","ECSS - Superseded v1.0","6.1.1b","Requirement","ECSS-Q-ST-60-14_0470019",1,"Created","Component families not covered in Table 6-1 shall be subject to special procedures to be defined by the program.\n    ","NOTE The relifing procedure can be applied on a sub-lot containing only the quantity of components immediately needed for production. In this case, the relifing date-code is applicable only to parts actually tested. The time limits specified in Table 5-1 remain applicable for the residual sub-lot."]
["ECSS-Q-ST-60-14C","ECSS - Superseded v1.0","6.1.2e","Requirement","ECSS-Q-ST-60-14_0470026",1,"Created","For film capacitors using the polycarbonate technology, a DPA test shall be performed on three pieces ,including:\n    1. external visual inspection \n    2. sealing test after insulate sleeve removal \n    3. microsection on two pieces \n    4. decaping on third part. \n        ","NOTE See (5) in Table 6-1."]
["ECSS-Q-ST-60-14C","ECSS - Superseded v1.0","6.1.4c","Requirement","ECSS-Q-ST-60-14_0470035",1,"Created","The part tested for solderability shall be considered destroyed."]
["ECSS-Q-ST-60-14C","ECSS - Superseded v1.0","6.2b","Requirement","ECSS-Q-ST-60-14_0470039",1,"Created","Any components not satisfying at least one of the requirements included in this standard shall be considered as not conform."]
["ECSS-Q-ST-60-14C","ECSS - Superseded v1.0","A.2.1d","Requirement","ECSS-Q-ST-60-14_0470054",1,"Created","The relifing report shall indicate the new datecode (after relifing)."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","4.1.2.1b","Requirement","ECSS-Q-ST-60_0480003",1,"Unchanged","The supplier’s organization shall comply with all the requirements of ECSS-M-ST-10."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","4.1.4a","Requirement","ECSS-Q-ST-60_0480011",2,"Normative Change","For each equipment, its supplier shall issue a DCL in an editable and sortable electronic format, as a minimum compatible with CSV, identifying all component types needed.","NOTE CSV is a common file format that can be used to transfer data between database or spreadsheet tables (a spreadsheet program is for example Excel®)."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","4.2.2.1d","Requirement","ECSS-Q-ST-60_0480025",1,"Unchanged","Starting with the design phase of the project the supplier shall ensure maximum use of preferred (see 4.2.2.3) and qualified components to achieve an effective component reduction and standardization. "]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","4.2.2.2b","Requirement","ECSS-Q-ST-60_0480029",1,"Unchanged","The supplier shall evaluate the robustness of selected EEE components against the stresses induced by the assembly techniques to be employed."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","4.2.2.3c","Requirement","ECSS-Q-ST-60_0480038",1,"Unchanged","Parts subject to export restrictions or regulations shall not be preferred. "]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","4.2.2.5b","Requirement","ECSS-Q-ST-60_0480049",1,"Unchanged","For wire link fuses, the current derating factor shall be 50 % with an additional derating of 0,2 %/°C for an increase in the temperature of fuse body above 25 °C."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","4.2.3.1h","Requirement","ECSS-Q-ST-60_0480057",1,"Unchanged","For programmable devices, the representativeness shall include the programming hardware tools and the compatibility of the software."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","4.2.3.3b","Requirement","ECSS-Q-ST-60_0480063",1,"Unchanged","The Constructional Analysis shall comprise destructive and non-destructive inspections, analyses, and testing, to identify:\n    1. Design and construction technology,\n    2. Materials used,\n    3. Inherent reliability aspects,\n    4. Quality of workmanship,\n    5. Potential hazards."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","4.2.4b","Requirement","ECSS-Q-ST-60_0480068",1,"Unchanged","The approval of components shall be based on consideration of all pertinent data including both the electrical and environmental performance as well as the established quality and the dependability assurance requirements."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","4.3.2b","Requirement","ECSS-Q-ST-60_0480080",1,"Unchanged","International specifications systems, recognized as suitable for space applications (e.g. ESCC, MIL), shall be used by the supplier. "]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","4.3.3a","Requirement","ECSS-Q-ST-60_0480086",1,"Unchanged","All components to be incorporated into flight standard hardware shall be subjected to screening. "]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","4.3.4b","Requirement","ECSS-Q-ST-60_0480092",1,"Unchanged","The procurement entity shall carry out, at the manufacturer’s premises, a customer precap inspection on critical space qualified parts , including as a minimum relays, crystals, oscillators and hybrids."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","4.3.6b","Requirement","ECSS-Q-ST-60_0480097",1,"Unchanged","The buy-off shall include:\n    1. External visual inspection,\n    2. Witnessing electrical measurements,\n    3. Verifying mechanical dimensions,\n    4. Review and verification of the data-package."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","4.3.9a","Requirement","ECSS-Q-ST-60_0480110",2,"Normative Change","The DPA shall be performed on 3 samples per lot/date code for non-space qualified parts belonging to the following categories:\n    1. Capacitors (glass, ceramic, tantalum and variable)\n    2. Crystals\n    3. Oscillators\n    4. Discrete semiconductors (including diodes and transistors)\n    5. Filters\n    6. Monolithic microcircuits (including MMICs)\n    7. Hybrid circuits\n    8. Relays\n    9. Switches (including mechanical and thermal)\n    10. Optoelectronic devices (e.g. opto-couplers, LED’s, CCD’s and sensors)\n    11. Passive microwave devices (e.g. mixers, couplers, isolators and switches)"]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","4.3.9e","Requirement","ECSS-Q-ST-60_0480114",1,"Unchanged","The DPA process shall be documented by a procedure to be sent, on request, to the customer for review."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","4.5.1a","Requirement","ECSS-Q-ST-60_0480129",1,"Unchanged","The supplier shall establish and implement the requirements of this document including methods, organizations and documents used to control the selection and procurement of components in accordance with the requirements of ECSS-Q-ST-20."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","4.5.2c","Requirement","ECSS-Q-ST-60_0480132",1,"Unchanged","The nonconformance control system shall handle all nonconformances occurring on EEE components during:\n    1. Manufacture (if available), screening and acceptance tests, \n    2. Incoming inspection,\n    3. Integration and test of equipment,\n    4. Storage and handling."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","4.5.4d","Requirement","ECSS-Q-ST-60_0480140",2,"Normative Change","The traceability of EEE parts during installation in equipment, shall be ensured by the supplier through maintaining the traceability to the manufacturer’s lot/date code number of the EEE parts actually mounted. "]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","4.6.4a","Requirement","ECSS-Q-ST-60_0480147",2,"Normative Change","For FPGA, ECSS-Q-ST-60-02 shall apply. "]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","5.1.2.2a","Requirement","ECSS-Q-ST-60_0480159",1,"Unchanged","The supplier shall prepare a compliance matrix to the clauses of this standard. "]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","5.1.4b","Requirement","ECSS-Q-ST-60_0480166",2,"Normative Change","The list specified in 5.1.4a shall be kept under configuration control (issue and identification of changes). "]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","5.2.2.1a","Requirement","ECSS-Q-ST-60_0480176",1,"Unchanged","The supplier shall establish and maintain in his own facility, and ensure that his suppliers also establish and maintain, procedures for selecting and controlling all components intended for use in deliverable products. "]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","5.2.2.2e","Requirement","ECSS-Q-ST-60_0480184",1,"Unchanged","For limited life duration, known instability, safety hazards or reliability risk reasons, EEE components listed below shall not be used for new designs:\n    1. RNC90 > 100 kW,\n    2. TO3 and DO4/DO5 packages."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","5.2.2.3f","Requirement","ECSS-Q-ST-60_0480193",1,"Unchanged","The supplier shall identify components which are not compliant with the radiation requirements as critical radiation sensitive components. "]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","5.2.2.3i","Requirement","ECSS-Q-ST-60_0480196",1,"Unchanged","The Equipment Radiation Analysis document shall be submitted to the customer for approval.\n    ","NOTE  More detailed information about the above requirements is given in ECSS-E-ST-10-12 and ECSS-Q-ST-60-15."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","5.2.3.1f","Requirement","ECSS-Q-ST-60_0480204",1,"Unchanged","Omission of any of these elements, or the introduction of alternative activities, shall be justified."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","5.2.3.4b","Requirement","ECSS-Q-ST-60_0480214",1,"Unchanged","The supplier shall review the already existing data in order to adapt and minimize the content of the evaluation testing while ensuring that there are inputs and pertinent results covering the following topics:\n    1. Endurance test (operating at elevated temperature and electrical stress),\n    2. Mechanical stress (shock, vibration, constant acceleration),\n    3. Environmental stress (thermal shock, temperature cycling, high and low temperature storage, humidity),\n    4. Assembly capability testing,\n    5. Radiation testing, for total dose and single event effects sensitivity.\n        ","NOTE For guidance refer to ESCC basic specification no. 22600 and the ancillary specifications for dedicated component families. "]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","5.3.1d","Requirement","ECSS-Q-ST-60_0480223",1,"Unchanged","For non qualified parts, the supplier shall put in place a configuration control system to ensure that any change of the product (e.g. mask, manufacturing and assembly process) affecting evaluation, performance, quality, reliability and interchangeability is communicated to him by the manufacturer (e.g. PCN)."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","5.3.2a","Requirement","ECSS-Q-ST-60_0480227",1,"Unchanged","The supplier shall procure EEE components according to controlled specifications."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","5.3.3h","Requirement","ECSS-Q-ST-60_0480458",1,"Created","In case of X-rays inspection, the total dose deposited shall be less than 1/10 of the product acceptable dose."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","5.3.7a","Requirement","ECSS-Q-ST-60_0480247",1,"Unchanged","The procurement entity shall perform incoming inspection at his premises on all components to verify conformance with the purchase order requirements."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","5.3.9a","Requirement","ECSS-Q-ST-60_0480257",2,"Normative Change","The DPA shall be performed on 3 samples per lot/date code for the following non-space qualified parts types: as a minimum relays, oscillators and commercial parts."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","5.3.9b","Permission","ECSS-Q-ST-60_0480508",1,"Created","DPA may be carried out on representative samples of the components families when the following three conditions are met:\n    1. procured from the same manufacturer and same package without major change in the process, \n    2. with a limited datecode range of 13 weeks,\n    3. approved by the customer through the PAD (or Justification document) process.","NOTE In complement of above conditions, for series of integrated circuits, series of thermal switches, series of active discrete and series of passive components (e.g. 54xxxx, 1N63xx, …), representative samples can be from the same family considering technology limit and their complexity."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","5.4a","Requirement","ECSS-Q-ST-60_0480271",1,"Unchanged","The supplier shall establish and implement procedures for handling and storage of components in order to prevent possible degradation. "]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","5.5.2b","Requirement","ECSS-Q-ST-60_0480277",1,"Unchanged","Any observed deviation of EEE components from requirements as laid down in applicable specifications, procedures and drawings shall be controlled by the nonconformance control system.\n    ","NOTE This includes failures, malfunctions, deficiencies and defects."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","5.6.2a","Requirement","ECSS-Q-ST-60_0480289",2,"Normative Change","ECSS-Q-ST-60-02 shall apply. "]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","5.6.4d","Requirement","ECSS-Q-ST-60_0480294",1,"Unchanged","One time programmable components shall be submitted to a post-programming sequence. "]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","6.1.2.2a","Requirement","ECSS-Q-ST-60_0480303",1,"Unchanged","The supplier shall prepare a compliance matrix to the clauses of this standard. "]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","6.1.4b","Requirement","ECSS-Q-ST-60_0480307",2,"Normative Change","The list specified in 6.1.4a shall be kept under configuration control (issue and identification of changes)."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","6.2.2.2b","Requirement","ECSS-Q-ST-60_0480321",1,"Unchanged","The supplier shall evaluate the robustness of selected EEE components against the stresses induced by the assembly techniques to be employed."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","6.2.2.2e","Requirement","ECSS-Q-ST-60_0480324",1,"Unchanged","For limited life duration, known instability, safety hazard or reliability risk reasons, the use of EEE components listed below shall not be used for new designs:\n    1. RNC90 > 100 kW,\n    2. TO3 and DO4/DO5 packages."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","6.2.2.4d","Requirement","ECSS-Q-ST-60_0480332",1,"Unchanged","Due consideration shall be given to the mission orbit and trajectory, the duration, the associated spatial and temporal variations of the radiation environment as well as all protective factors such as shielding. "]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","6.2.3.1c","Requirement","ECSS-Q-ST-60_0480342",1,"Unchanged","The scope and planning of the component evaluation actions shall be derived from the results of an assessment of the design and intended application of the needed component. "]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","6.2.3.2a","Requirement","ECSS-Q-ST-60_0480351",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","6.2.4d","Requirement","ECSS-Q-ST-60_0480360",2,"Normative Change","Prior to procurement of components (or before equipment CDR, at the latest), the approval process by the customer shall be organized as follows:\n    1. All parts are approved by the review of the DCL,\n    2. A PAD in conformance with Annex D (or information included in the DCL) is required for parts when:\n        (a) additional controls are required (e.g. precap, buy-off, LAT or LVT, RVT, DPA),\n        (b) used outside the specified limits,\n        (c) specific tests are required during procurement as per Table 7 3.\n        (d) pure tin is used inside or outside the part\n    3. A Justification Document, is required for any commercial part, instead of PAD in conformance with the requirements from the ECSS-Q-ST-60-13."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","6.3.2e","Requirement","ECSS-Q-ST-60_0480370",1,"Unchanged","The use of any new specification or datasheet shall be submitted to the customer for review through the approval process (see clause 6.2.4)."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","6.3.3f","Requirement","ECSS-Q-ST-60_0480466",1,"Created","When a component is available in a qualified version according to quality level specified in Table 7-3 it shall be selected."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","6.3.7d","Permission","ECSS-Q-ST-60_0480514",1,"Created","If the parts have passed successfully a final CSI (or buy-off), the incoming inspection may be reduced to the following minimum:\n    1. Verification of the manufacturer’s CoC,\n    2. Packing checking,\n    3. Quantity verification."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","6.3.7e","Permission","ECSS-Q-ST-60_0480515",1,"Created","In case the incoming inspection has been performed by a procurement agent, the incoming inspection performed by the end-user, may be reduced to the following minimum:\n    1. Packing checking,\n    2. Quantity verification."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","6.3.9h","Requirement","ECSS-Q-ST-60_0480469",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","6.3.11b","Requirement","ECSS-Q-ST-60_0480405",2,"Normative Change","Any other data (i.e. LAT or LVT, QCI or TCI), defined in the applicable procurement documents, shall be available at the manufacturer’s facilities or delivered to the parts’ procurer in line with the purchase order, as a minimum compatible with CSV.","NOTE CSV is a common file format that can be used to transfer data between database or spreadsheet tables (a spreadsheet program is for example Excel®)."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","6.5.2c","Requirement","ECSS-Q-ST-60_0480414",1,"Unchanged","The nonconformance control system shall handle all nonconformances occurring on EEE components during: \n    1. Manufacture (if available), screening and acceptance tests, \n    2. Incoming inspection,\n    3. Integration and test of equipment,\n    4. Storage and handling."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","6.5.5a","Requirement","ECSS-Q-ST-60_0480423",2,"Normative Change","For radiation tests, the set of test samples shall be in accordance with ECSS-Q-ST-60-15."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","6.6.4e","Requirement","ECSS-Q-ST-60_0480431",2,"Normative Change","For FPGA types without a clear and defined heritage, a post-programming burn-in shall be applied, in conformance with ESCC9000 subclause 8.21, for a minimum duration of 160 h.","NOTE FPGA types with defined heritage are documented in the report: ESCC REP 010 SCSB Decisions Regarding OTP FPGA PPBI, available on https://escies.org."]
["ECSS-Q-ST-60C Rev. 2","ECSS - Superseded v1.0","6.6.5a","Requirement","ECSS-Q-ST-60_0480435",2,"Normative Change","Design, selection, procurement and use of the microwave monolithic integrated circuits shall be performed in conformance with the requirements from ECSS-Q-ST-60-12."]
["ECSS-Q-ST-70-07C","ECSS - Superseded v1.0","5.2.2b","Requirement","ECSS-Q-ST-70-07_0560009",1,"Created","The supplier shall perform a cleaning without conformal coating of the samples specified in 5.2.2a."]
["ECSS-Q-ST-70-07C","ECSS - Superseded v1.0","5.2.2e","Requirement","ECSS-Q-ST-70-07_0560012",1,"Created","Except for the actual machine soldering procedure, the full component assembly requirements of ECSS-Q-ST-70-08 shall apply. "]
["ECSS-Q-ST-70-07C","ECSS - Superseded v1.0","5.3d","Requirement","ECSS-Q-ST-70-07_0560020",1,"Created","The approval authority shall submit to the supplier a copy of the audit report.\n    NOTE The line audit report is a customer document provided to the supplier and is used as input for the customer to decide if the verification programme can be further implemented (see 5.4.1a). No DRD is specified for this activity."]
["ECSS-Q-ST-70-07C","ECSS - Superseded v1.0","5.4.2e","Requirement","ECSS-Q-ST-70-07_0560029",1,"Created","There shall be at least three components of each type per board.\n    NOTE It is important to pay particular attention to heat sensitive components."]
["ECSS-Q-ST-70-07C","ECSS - Superseded v1.0","5.5.3a","Requirement","ECSS-Q-ST-70-07_0560041",1,"Created","The approval of any wave-soldering line shall be withdrawn by the approval authority in any of the following cases:\n    1. the supplier experiences rework activities of more than 5 %,\n    2. any of the materials, permitted component types or manufacturing processes have been changed without prior authorization (i.e. changes to the PID),\n    3. modifications related to B.2.1b as given in the Annex C – DRD. have taken place, without an approval before implementation,\n    4. the customer or his intermediate suppliers have experienced delays in delivery or manufacturing defects directly attributable to the wave-soldering process.\n        NOTE 1 Renewed approval can be granted following a review of the discrepancy(ies).\n        NOTE 2 A repeat, or partial repeat of the verification programme can be considered necessary."]
["ECSS-Q-ST-70-07C","ECSS - Superseded v1.0","5.6f","Requirement","ECSS-Q-ST-70-07_0560048",1,"Created","The soldering area and machines shall be kept clean and orderly."]
["ECSS-Q-ST-70-07C","ECSS - Superseded v1.0","5.6q","Requirement","ECSS-Q-ST-70-07_0560059",1,"Created","Evidences shall be provided that: \n    1. the assembled board does not become contaminated before being loaded on the carrier.\n    2. the conveyer speed does not vary by more than ±5 %."]
["ECSS-Q-ST-70-07C","ECSS - Superseded v1.0","B.2.1a","Requirement","ECSS-Q-ST-70-07_0560067",1,"Created","The request for verification of the automatic wave soldering process shall contain a brief description of the facility, details of past experience and the name of the spacecraft project concerned."]
["ECSS-Q-ST-70-07C","ECSS - Superseded v1.0","C.2.1b","Requirement","ECSS-Q-ST-70-07_0560076",1,"Created","The verification report shall contain for the 5 assembled PCBs specified in 5.4.2 (including the one used for reference), the initial test specifications, procedures and test results as defined in the verification programme, including: \n    1. Visual inspection report established in conformance with the requirements of ECSS-Q-ST-70-08;\n    2. Summary of cleanliness test results in conformance with clause 11.3 of ECSS-Q-ST-70-08 or equivalent method;\n    3. Tests results concerning the warp (bow) and twist of circuit board in conformance with the requirements of ECSS-Q-ST-70-10;\n    4. Electrical continuity test specification, procedure and reports (for multilayer boards). "]
["ECSS-Q-ST-70-07C","ECSS - Superseded v1.0","C.2.1e","Requirement","ECSS-Q-ST-70-07_0560079",1,"Created","The automatic wave soldering process verification report shall contain a list of findings and recommendations in order to optimize the automatic wave soldering process specifications and control parameters for a given assembled PCB. "]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","5.2a","Requirement","ECSS-Q-ST-70-08_0570003",1,"Created","Personnel facilities shall be separated from the soldering areas.\n    NOTE Example: Washrooms, eating areas, smoking facilities."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","5.3d","Requirement","ECSS-Q-ST-70-08_0570013",1,"Created","The relative humidity at room temperature of the facility shall be maintained at 55 % ± 15 %."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","5.5.2a","Requirement","ECSS-Q-ST-70-08_0570022",1,"Created","The working bench shall have a static dissipative top with surface resistance (Rs) in the range 1 ´ 104 Ω to 1 ´ 1010 Ω."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","5.5.2j","Requirement","ECSS-Q-ST-70-08_0570031",1,"Created","Paperwork shall not come into contact with ESD sensitive components."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","5.6.2a","Requirement","ECSS-Q-ST-70-08_0570041",1,"Created","Medium-stiff natural- or synthetic bristle, ESD-safe, brushes shall be used for cleaning provided that they do not damage any surface to be cleaned or adjacent materials."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","5.6.4b","Requirement","ECSS-Q-ST-70-08_0570050",1,"Created","Components shall not be damaged by the bending process (see also clause 8.2).\n    NOTE It is good practice to use bending tools with polished finish. The preferred surface finish for shaping tools is hard chromium plating."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","5.6.7a","Requirement","ECSS-Q-ST-70-08_0570060",1,"Created","The size and shape of the soldering iron and bit shall not damage adjacent areas or connections during soldering operations."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","5.6.7b","Requirement","ECSS-Q-ST-70-08_0570061",1,"Created","Temperature-controlled soldering irons shall be used.\n    NOTE It is good practice to verify periodically the solder tip temperature."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","5.6.7j","Permission","ECSS-Q-ST-70-08_0570548",1,"Created","A soldering-bit temperature up to 380 °C may be used for polyimide PCBs with heat sinks, wide tracks or ground planes."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","6.1b","Requirement","ECSS-Q-ST-70-08_0570080",1,"Created","Components, subassemblies, assemblies and hardware for space flight applications shall not have tin finishes containing more than 97 % tin."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","6.3.1d","Permission","ECSS-Q-ST-70-08_0570552",1,"Created","When pretinning with fully activated rosin-based flux does not give acceptable wetting, INH1 corrosive, water-soluble, acid flux may be used in accordance with clause 6.3.2.\n    NOTE Difficulties in pretinning can arise from poor solderability."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","6.3.3b","Requirement","ECSS-Q-ST-70-08_0570099",1,"Created","When flux-cored solder is used, it shall be positioned such that the flux flows and covers the components to be joined as the solder melts."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","6.4g","Requirement","ECSS-Q-ST-70-08_0570108",1,"Created","Solvents shall not be used such that dissolved flux residue contaminates electrical contact surfaces.\n    NOTE Examples of electrical contact surfaces are those in switches, potentiometers or connectors."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","6.4k","Requirement","ECSS-Q-ST-70-08_0570112",1,"Created","Solvents shall be selected such that they dry completely."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","6.7e","Requirement","ECSS-Q-ST-70-08_0570127",1,"Created","Chemical stripping materials shall be completely neutralised and be cleaned such that there are no residues from the stripping, neutralizing, or cleaning steps."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","6.8.1b","Requirement","ECSS-Q-ST-70-08_0570130",1,"Created","For non-plated-through holes, interfacial connections shall be made according to clause 8.2.2."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","6.10e","Requirement","ECSS-Q-ST-70-08_0570138",1,"Created","No materials that emit acetic acid, ammonia, amines, hydrochloric acid and other acids shall be used.\n    NOTE Such compounds can cause stress-corrosion cracking of part leads."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","7.2.1.2a","Requirement","ECSS-Q-ST-70-08_0570148",1,"Created","The remaining conductor insulation shall not be damaged by the insulation removal process."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","7.2.1.4.2b","Requirement","ECSS-Q-ST-70-08_0570157",1,"Created","The minimum insulation clearance shall not result in insulation imbedded in the solder joint."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","7.2.3.1a","Requirement","ECSS-Q-ST-70-08_0570166",1,"Created","Tin-lead alloy solders shall not be used to solder to gold."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","7.2.3.2.2f","Requirement","ECSS-Q-ST-70-08_0570177",1,"Created","The component leads shall be allowed to cool before cleaning."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","7.2.4d","Requirement","ECSS-Q-ST-70-08_0570185",1,"Created","Liquid solder shall not come into contact with the component body or its glass meniscus."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","7.2.5.3d","Requirement","ECSS-Q-ST-70-08_0570195",1,"Created","Pretinning shall not degrade the characteristics of the wire. \n    NOTE Flow of solder (wicking) beyond the insulation can reduce the flexibility of the wire."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","7.2.5.3e","Requirement","ECSS-Q-ST-70-08_0570196",1,"Created","The insulation shall not be damaged by the pretinning."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","7.3.1a","Requirement","ECSS-Q-ST-70-08_0570204",1,"Created","The bit shall be fitted in accordance with the equipment manufacturer’s specification."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","7.5c","Requirement","ECSS-Q-ST-70-08_0570215",1,"Created","During assembly, component leads, terminals, wire ends and PCB termination areas shall not be touched with bare hands."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","7.6.3c","Requirement","ECSS-Q-ST-70-08_0570224",1,"Created","Corrosive acid fluxes shall be stored in accordance with clause 6.3.2c.\n    NOTE Example: INH1 flux."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","8.1.1a","Requirement","ECSS-Q-ST-70-08_0570233",1,"Created","Components shall be mounted parallel to the mounting surface."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","8.1.4a","Requirement","ECSS-Q-ST-70-08_0570243",1,"Created","Glass-encased parts shall be enclosed with sleeving when epoxy material is used for staking, conformal coating or encapsulating.\n    NOTE Epoxy material cannot be applied directly to the glass."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","8.1.5g","Requirement","ECSS-Q-ST-70-08_0570251",1,"Created","CKR-06 and similar packages shall be adhesively staked in accordance with Figure 8-1.\n    NOTE The use a filler (silica powder) can prevent excessive flow of adhesive."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","8.2.1a","Requirement","ECSS-Q-ST-70-08_0570262",1,"Created","During bending, component leads shall be supported to avoid axial stress and damage to seals or internal bonds."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","8.2.1d","Requirement","ECSS-Q-ST-70-08_0570265",1,"Created","The minimum distance from the bend to the end seal shall be two lead diameters for round leads and 0,50 mm for ribbon leads."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","8.3d","Requirement","ECSS-Q-ST-70-08_0570273",1,"Created","After swaging, the terminal shall be inspected for circumferential splits or cracks."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","8.4.2e","Requirement","ECSS-Q-ST-70-08_0570282",1,"Created","The soldered length shall comply with clauses 8.4.4 and 8.4.5."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","8.5a","Requirement","ECSS-Q-ST-70-08_0570294",1,"Created","Components shall be mounted in accordance with clause 8.1."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","8.6d","Requirement","ECSS-Q-ST-70-08_0570301",1,"Created","Before soldering, the operator shall ensure that there is no contact between the solder fillet to be formed and the gold plating."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","9.2.4b","Requirement","ECSS-Q-ST-70-08_0570312",1,"Created","Wicking shall be controlled.\n    NOTE Anti-wicking tools can be used for pre-tinning the stranded wires."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","9.3.2a","Requirement","ECSS-Q-ST-70-08_0570320",1,"Created","The conductor shall enter the terminal from the bottom, pass through the side slot at the top, and be wrapped as for the side route, see Figure 9-1 (b)."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","9.4.3e","Permission","ECSS-Q-ST-70-08_0570570",1,"Created","Conductors may project beyond the diameter of the base, see Figure 9-3 (c), provided that clearances, environmental and electrical characteristics are not compromised."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","9.4.4b","Requirement","ECSS-Q-ST-70-08_0570332",1,"Created","Top route connections shall be as shown in Figure 9-4."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","9.5b","Requirement","ECSS-Q-ST-70-08_0570340",1,"Created","The bend to attach conductors to hook terminals shall be:\n    1. a minimum of 1/2 turn,\n    2. a maximum of 3/4 turn."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","9.7e","Requirement","ECSS-Q-ST-70-08_0570350",1,"Created","Flux shall not be trapped within the solder cup."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","9.9.1d","Requirement","ECSS-Q-ST-70-08_0570359",1,"Created","After soldering, conductors shall be covered with heat-shrinkable sleeving."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","9.9.3e","Requirement","ECSS-Q-ST-70-08_0570368",1,"Created","The shield material shall be of good solderability."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","9.9.4.2e","Requirement","ECSS-Q-ST-70-08_0570378",1,"Created","Wires shall be spliced using lap joints."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","9.9.6a","Requirement","ECSS-Q-ST-70-08_0570387",1,"Created","The removal of flux and residues shall be in accordance with clause 11."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","9.10c","Requirement","ECSS-Q-ST-70-08_0570397",1,"Created","Stress relief shall be provided."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","9.10d","Requirement","ECSS-Q-ST-70-08_0570398",1,"Created","For PTFE-insulated wire, the minimum distance between the insulation and the solder fillet shall be 1 mm."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","10.2.2c","Requirement","ECSS-Q-ST-70-08_0570406",1,"Created","Terminals with more than one wire shall have each wire in contact with, and soldered to, the terminal."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","10.3.2c","Requirement","ECSS-Q-ST-70-08_0570417",1,"Created","On lap terminations where one side of a conductor is flush with the edge of the termination pad, a fillet of solder shall be present along at least three of the four sides of the lead."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","10.3.4c","Requirement","ECSS-Q-ST-70-08_0570424",1,"Created","The heated soldering iron bit shall be applied to the joint."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","11.1c","Requirement","ECSS-Q-ST-70-08_0570436",1,"Created","Flux and residue shall be removed within a maximum period of 8 hours after soldering operations.\n    NOTE It is good practice to remove flux as soon as possible because even rosin fluxes are difficult to remove after longer ageing."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","11.3.4a","Requirement","ECSS-Q-ST-70-08_0570445",1,"Created","Sodium chloride (NaCl) equivalent ionic contamination shall be measured as follows:\n    1. Use a solution of 75 % isopropyl alcohol and 25 % deionized water for the sodium chloride (NaCl) equivalent ionic contamination test.\n    2. Calibrate the equipment using a sodium chloride solution of known quantity and composition."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","12.2a","Requirement","ECSS-Q-ST-70-08_0570453",1,"Created","Acceptable solder connections shall be characterised by:\n    1. a clean, smooth satin to bright undisturbed surface,\n    2. solder fillets between conductor and termination areas as described and illustrated in clause 15,\n    3. for solder fillets of plated-through hole connections, the criteria in clause 10.3.3 apply,\n    4. visible contour of wires and leads such that their presence, direction of bend and termination end can be determined,\n    5. complete wetting as evidenced by a low contact angle between the solder and the joined surfaces,\n    6. acceptable amount and distribution of solder in accordance with clause 15,\n    7. absence of any of the defects mentioned in clauses 12.3,\n    8. high-voltage connections in accordance with clause 10.1.3,\n    9. stress relief."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","13.2c","Requirement","ECSS-Q-ST-70-08_0570464",1,"Created","The test levels and durations shall be derived from the system requirements.\n    NOTE 1 The vibration test levels for launcher hardware are more severe than those for other flight hardware.\n    NOTE 2 Vibration testing methodology - From the input levels required by the projects in progress, the maximum deformation of the printed circuit board at the part level is established for each configuration (part type, location on the printed circuit board). The test specimen is representative of these configurations and covers at least the maximum deformations previously established, with a margin either minimum for a specific project or higher for generic applications. Nevertheless, in order to take into account test specimen imperfections, notching can be used to reduce non-representative mechanical overstresses. The part assembly (mounting condition) is defined in order to withstand the vibration levels estimated at the part level. The success of verification of the test specimen and the successful completion of QM qualification validate the assembly configuration and the implemented methodology."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","13.3b","Requirement","ECSS-Q-ST-70-08_0570471",1,"Created","Before the start of the temperature cycling, the test specimen shall be baked-out to remove the internal humidity. "]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","13.3f","Requirement","ECSS-Q-ST-70-08_0570475",1,"Created","The soak time at each temperature extreme shall be a minimum of 15 minutes."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","14.3a","Requirement","ECSS-Q-ST-70-08_0570485",1,"Created","Nonconformance in the soldering process shall be dispositioned in accordance with ECSS-Q-ST-10-09."]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","14.7a","Requirement","ECSS-Q-ST-70-08_0570494",1,"Created","During all stages of the process, the inspection points shall be implemented. "]
["ECSS-Q-ST-70-08C","ECSS - Superseded v1.0","A.2.1<1>a","Requirement","ECSS-Q-ST-70-08_0570503",1,"Created","The report shall contain the name, organization and address of the originator."]
["ECSS-Q-ST-30-11C Rev.1","ECSS - Superseded v1.0","4a","Requirement","ECSS-Q-ST-30-11_0140001",1,"Created","The user of this Standard shall verify that the ordered assurance level of procured components is compatible with the intended application."]
["ECSS-Q-ST-30-11C Rev.1","ECSS - Superseded v1.0","5.3.2h","Requirement","ECSS-Q-ST-30-11_0140009",1,"Created","Where components are required to operate in protection mode or in fail-safe mode in order to prevent failure propagation (e.g. short-circuit protection), the components concerned shall meet the derating requirements and application rules when performing the protection or fail-safe function under the worst failure case (i.e. highest stress applied to the components that can last throughout the mission)."]
["ECSS-Q-ST-30-11C Rev.1","ECSS - Superseded v1.0","6.2.1b","Permission","ECSS-Q-ST-30-11_0140163",1,"Created","Multilayer capacitors with a DC voltage rating less than 100 V may be used in low voltage (less than 10 V) continuous applications provided they have been submitted to a low voltage (1,5 V) 85 % humidity at 85 °C test or other approved method. "]
["ECSS-Q-ST-30-11C Rev.1","ECSS - Superseded v1.0","6.2.1c","Recommendation","ECSS-Q-ST-30-11_0140164",1,"Created","<<deleted>>"]
["ECSS-Q-ST-30-11C Rev.1","ECSS - Superseded v1.0","6.3.1f","Recommendation","ECSS-Q-ST-30-11_0140166",1,"Created","Internal heating due to ESR can increase ageing and should be taken into account by applying a margin in temperature. Where ESR is not known at the frequency of a ripple current, an extrapolation of the ESR value and resonance (from manufacturer’s or test data) should be made where possible."]
["ECSS-Q-ST-30-11C Rev.1","ECSS - Superseded v1.0","6.5.3a","Requirement","ECSS-Q-ST-30-11_0140038",1,"Created","Self healing requirements (if applicable): clearing recommendations from manufacturers shall be followed."]
["ECSS-Q-ST-30-11C Rev.1","ECSS - Superseded v1.0","6.9.2a","Requirement","ECSS-Q-ST-30-11_0140046",1,"Created","Parameters of capacitors from family-group code 01-11 shall be derated as per Table 6-8."]
["ECSS-Q-ST-30-11C Rev.1","ECSS - Superseded v1.0","6.12.2a","Requirement","ECSS-Q-ST-30-11_0140057",1,"Created","Parameters of connectors RF from family-group code 02-05 shall be derated as per Table 6-11."]
["ECSS-Q-ST-30-11C Rev.1","ECSS - Superseded v1.0","6.15.2a","Requirement","ECSS-Q-ST-30-11_0140070",1,"Created","Parameters of Diodes from family-group code 04-05, 04-11 to 04-13, 04-15, 04-16 and 04-17 shall be derated as per Table 6-15."]
["ECSS-Q-ST-30-11C Rev.1","ECSS - Superseded v1.0","6.18.2a","Requirement","ECSS-Q-ST-30-11_0140081",1,"Created","Parameters of Inductors and transformers from family-group code: 07-01 to 07-03 and 14-01 shall be derated as per Table 6-18."]
["ECSS-Q-ST-30-11C Rev.1","ECSS - Superseded v1.0","6.22.3a","Requirement","ECSS-Q-ST-30-11_0140097",1,"Created","Some linear circuits can be radiation sensitive: the issue shall be recorded in the design file and the components selection shall be reviewed and approved as described in ECSS-Q-ST-60."]
["ECSS-Q-ST-30-11C Rev.1","ECSS - Superseded v1.0","6.25.1b","Requirement","ECSS-Q-ST-30-11_0140104",1,"Created","The minimum coil pulse duration for latching relays shall be 3 times the latch time (tL) or 40 ms, whichever is greater."]
["ECSS-Q-ST-30-11C Rev.1","ECSS - Superseded v1.0","6.25.3c","Requirement","ECSS-Q-ST-30-11_0140110",1,"Created","Paralleled relays shall not be used to increase current switching capabilities of contacts. When relays are paralleled for redundancy, in order to increase the system’s reliability, the sum of the paralleled currents shall not exceed the contact current rating. \n"]
["ECSS-Q-ST-30-11C Rev.1","ECSS - Superseded v1.0","6.26.2.8a","Requirement","ECSS-Q-ST-30-11_0140126",1,"Created","Actual rated power shall be specified in the applicable heater design drawing. It shall be determined from the specified heating area (s) in cm2 taking into account the thermal properties of the mounted heater in the\napplication."]
["ECSS-Q-ST-30-11C Rev.1","ECSS - Superseded v1.0","6.29.2a","Requirement","ECSS-Q-ST-30-11_0140134",1,"Created","Parameters of Transistors from family-group code 12-05 and 12-06 shall be derated as per Table 6-34."]
["ECSS-Q-ST-30-11C Rev.1","ECSS - Superseded v1.0","6.33.3b","Requirement","ECSS-Q-ST-30-11_0140151",1,"Created","Opto-couplers can be radiation sensitive, in particular, operation at low diode currents increases radiation sensitivity: this issue shall be recorded in the design file and the components selection shall be reviewed and approved as described in ECSS-Q-ST-60."]
["ECSS-Q-ST-30-11C Rev.1","ECSS - Superseded v1.0","6.34.3c","Requirement","ECSS-Q-ST-30-11_0140159",1,"Created","Maximum mating and de-mating cycles shall be limited to 50 cycles."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","4.1.4a","Requirement","ECSS-Q-ST-60-13_0460011",1,"Created","For each equipment, its supplier shall issue a DCL in an editable and sortable electronic format, as a minimum compatible with CSV, identifying all component types needed.","NOTE CSV is a common file format that can be used to transfer data between database or spreadsheet tables (a spreadsheet program is for example Excel®)."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","4.1.5b","Requirement","ECSS-Q-ST-60-13_0460020",1,"Created","Flight hardware connector interfaces to GSE shall interface to a flight compatible connector, as per 4.1.5a.","NOTE This connector can be installed on the test harness or can be a saver."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","4.2.2.1e","Requirement","ECSS-Q-ST-60-13_0460026",1,"Created","When selecting items, the supplier shall check the current data, applicability of the basis of qualification, problem notifications and alerts, and adequacy of specifications. "]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","4.2.2.2a","Requirement","ECSS-Q-ST-60-13_0460028",1,"Created","The supplier shall ensure that non-hermetically sealed materials of components meet the requirements of ECSS-Q-ST-70 regarding off-gassing, out-gassing, flammability, toxicity and any other criteria specified for the intended use. "]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","4.2.2.4b","Requirement","ECSS-Q-ST-60-13_0460040",1,"Created","The supplier who is responsible for the design of the piece of hardware shall demonstrate the compliance of its components selection with the radiation constraints of the project."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","4.2.2.5b","Requirement","ECSS-Q-ST-60-13_0460049",1,"Created","For wire link fuses, the current derating factor shall be 50 % with an additional derating of 0,2 %/°C for an increase in the temperature of fuse body above 25 °C."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","4.2.3.1f","Requirement","ECSS-Q-ST-60-13_0460055",1,"Created","Omission of any of these elements, or the introduction of alternative activities, shall be justified."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","4.2.3.3b","Requirement","ECSS-Q-ST-60-13_0460063",1,"Created","The Construction analysis shall be documented by a procedure to be sent to the customer for approval.","NOTE Annex H provides guidelines for such procedure."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","4.2.4c","Requirement","ECSS-Q-ST-60-13_0460069",1,"Created","The supplier shall maintain a system of traceability of the acceptance and approval of each component used in flight products."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","4.3.1j","Requirement","ECSS-Q-ST-60-13_0460488",1,"Created","Each trace code shall be maintained as is through the entire supply chain including distributor.","NOTE As far as possible, commercial parts should be ordered in the manufacturer’s standard packing quantities or multiples thereof to avoid distributor re-packing and handling and to preserve the traceability information usually included on the original manufacturer packaging."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","4.3.1k","Requirement","ECSS-Q-ST-60-13_0460489",1,"Created","The supplier shall ensure that the elements of the JD in accordance with Annex F, including any action plan, are applicable to flight parts."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","4.3.3c","Requirement","ECSS-Q-ST-60-13_0460088",1,"Created","All screening tests shall be performed at the component manufacturer’s premises or at a facility approved either by the qualification approval authority, where applicable (e.g. ESCC), or otherwise by the supplier."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","4.3.7c","Requirement","ECSS-Q-ST-60-13_0460102",1,"Created","The incoming inspection shall be documented by a procedure to be presented, on request, to the customer for review."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","4.3.9a","Requirement","ECSS-Q-ST-60-13_0460110",1,"Created","The DPA shall be performed on 3 samples per lot of commercial parts during evaluation after lifetest as specified in the clause 4.2.3.4 and after relifing as specified in the clause 4.3.10.","NOTE Annex H provides guidelines for the construction analysis and descrtictive physical analysis."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","4.3.11b","Requirement","ECSS-Q-ST-60-13_0460123",1,"Created","Any other data, defined in the procurement documents, shall be delivered to the parts’ procurer in line with the purchase order."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","4.5.2b","Requirement","ECSS-Q-ST-60-13_0460131",1,"Created","Any observed deviation of EEE components from requirements as laid down in applicable specifications, procedures and drawings shall be controlled by the nonconformance control system.\n    ","NOTE This includes failures, malfunctions, deficiencies and defects."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","4.5.4c","Requirement","ECSS-Q-ST-60-13_0460139",1,"Created","In any case, the traceability requirements imposed by the supplier on the EEE parts manufacturer or distributor shall allow managing the adequacy of the tests performed by the supplier (i.e. evaluation, lot validation, any additional test or inspection). "]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","4.6.4g","Requirement","ECSS-Q-ST-60-13_0460153",1,"Created","The lot acceptance procedure, as defined in clause 4.3.5, shall be performed on devices coming from the flight lot/date code and programmed on the same kind of hardware tools and compatible software."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","5.1.3a","Requirement","ECSS-Q-ST-60-13_0460161",1,"Created","The approval of the selection and usage of EEE parts shall be implemented through Parts Control Boards (PCBs) held between the customer and the supplier (or lower tier subcontractor)."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","5.1.4a","Requirement","ECSS-Q-ST-60-13_0460165",1,"Created","For each equipment, its supplier shall issue a DCL in an editable and sortable electronic format, as a minimum compatible with CSV, identifying all component types needed.","NOTE CSV is a common file format that can be used to transfer data between database or spreadsheet tables (a spreadsheet program is for example Excel®)."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","5.2.2.1c","Requirement","ECSS-Q-ST-60-13_0460178",1,"Created","Preference shall be given to components which necessitate the least evaluation or qualification effort. "]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","5.2.2.2b","Requirement","ECSS-Q-ST-60-13_0460181",1,"Created","The supplier shall evaluate the robustness of selected EEE components against the stresses induced by the assembly techniques to be employed."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","5.2.2.3c","Requirement","ECSS-Q-ST-60-13_0460190",1,"Created","For this demonstration, the supplier shall consider all types of radiation including cosmic (Heavy Ions), electromagnetic, trapped (charged particles - electrons, protons - in radiation belts) and solar (flares). "]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","5.2.2.3i","Requirement","ECSS-Q-ST-60-13_0460196",1,"Created","The Equipment Radiation Analysis document shall be submitted to the customer for approval.\n    ","NOTE  More detailed information about the above requirements is given in ECSS-E-ST-10-12 and ECSS-Q-ST-60-15."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","5.2.3.1h","Requirement","ECSS-Q-ST-60-13_0460206",1,"Created","For programmable devices, the representativeness shall include the programming hardware tools and the compatibility of the software."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","5.2.3.4a","Requirement","ECSS-Q-ST-60-13_0460213",1,"Created","The evaluation shall determine which inspections or tests are required to provide the confidence that the component type under evaluation, when assembled and tested in accordance with the procurement specification, successfully meets the project requirements."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","5.2.3.4b","Requirement","ECSS-Q-ST-60-13_0460214",1,"Created","The supplier shall review the already existing data in order to adapt and minimize the content of the evaluation testing while ensuring that there are inputs and pertinent results covering the following topics:\n    1. Endurance test (operating at elevated temperature and electrical stress),\n    2. Mechanical stress (shock, vibration, constant acceleration),\n    3. Environmental stress (thermal shock, temperature cycling, high and low temperature storage, humidity),\n    4. Assembly capability testing,\n    5. Radiation testing, for total dose and single event effects sensitivity.\n        ","NOTE For guidance refer to ESCC basic specification no. 22600 and the ancillary specifications for dedicated component families. "]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","5.2.4e","Requirement","ECSS-Q-ST-60-13_0460219",1,"Created","In case the evaluation results are changing the testing conditions documented in the JD, a new revision of JD shall be submitted to the customer for approval."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","5.3.2e","Requirement","ECSS-Q-ST-60-13_0460231",1,"Created","The use of any new specification or datasheet shall be submitted to the customer for approval through the PAD process (see clause 5.2.4)."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","5.3.3f","Requirement","ECSS-Q-ST-60-13_0460456",1,"Created","When a component is available in a qualified version according to quality level specified in Table 7 2 it shall be selected."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","5.3.6c","Requirement","ECSS-Q-ST-60-13_0460526",1,"Created","For commercial parts, the buy off shall be replaced by an incoming inspection at the procurement entity’s facility reported in the JD in accordance with clause 5.3.7."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","5.3.9a","Requirement","ECSS-Q-ST-60-13_0460257",1,"Created","The DPA shall be performed on 3 samples per lot of commercial parts (during evaluation after lifetest as specified in clause 5.2.3.4 and after relifing as specified by clause 5.3.10).","NOTE Annex H provides guidelines for the construction analysis and destructive physical analysis."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","5.3.10b","Requirement","ECSS-Q-ST-60-13_0460267",1,"Created","For components meeting the criteria specified in requirement 5.3.10a, and which have a lot / date code exceeding 7 years, the relifing procedure ECSS-Q-ST-60-14 shall apply to the lot."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","5.5.1a","Requirement","ECSS-Q-ST-60-13_0460275",1,"Created","The supplier shall establish and implement the requirements of this document including methods, organizations and documents used to control the selection and procurement of components in accordance with the requirements of ECSS-Q-ST-20."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","5.5.4a","Requirement","ECSS-Q-ST-60-13_0460282",1,"Created","The traceability of individual components during manufacturing and testing shall be maintained as required by the procurement specifications."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","5.5.4e","Requirement","ECSS-Q-ST-60-13_0460286",1,"Created","If the as built DCL has not yet been delivered, the supplier shall be able to provide this information (part type actually installed with its relevant trace code number) within one week."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","5.6.4g","Requirement","ECSS-Q-ST-60-13_0460297",1,"Created","The lot acceptance procedure, as defined in clause 5.3.5, shall be performed on devices coming from the flight lot/date code and programmed on the same kind of hardware tools and compatible software."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","6.1.4a","Requirement","ECSS-Q-ST-60-13_0460306",1,"Created","For each equipment, its supplier shall issue a DCL in an editable and sortable electronic format, as a minimum compatible with CSV, identifying all component types needed.","NOTE CSV is a common file format that can be used to transfer data between database or spreadsheet tables (a spreadsheet program is for example Excel®)."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","6.2.2.1b","Requirement","ECSS-Q-ST-60-13_0460317",1,"Created","Components shall be selected on the basis of proven qualification, characterization, and previous space experience and data, relevant with regard to the requirements for the programme, from manufacturers or sources (preferably European) employing effective Product Assurance Programmes in manufacturing and test. "]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","6.2.2.2b","Requirement","ECSS-Q-ST-60-13_0460321",1,"Created","The supplier shall evaluate the robustness of selected EEE components against the stresses induced by the assembly techniques to be employed."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","6.2.2.4g","Requirement","ECSS-Q-ST-60-13_0460335",1,"Created","The supplier shall implement a Radiation Hardness Assurance Programme, in conformance with the requirements of the ECSS-Q-ST-60-15, documented by a plan to be approved by the customer, for radiation sensitive components, covering the collection of all relevant information and specifying the necessary actions in terms of evaluation and procurement testing, planning and control."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","6.2.3.1b","Requirement","ECSS-Q-ST-60-13_0460341",1,"Created","The supplier shall plan and carry out the evaluation."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","6.2.3.1j","Requirement","ECSS-Q-ST-60-13_0460349",1,"Created","The supplier shall summarize the evaluation results in the evaluation report and send it to the customer for approval."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","6.2.3.4c","Requirement","ECSS-Q-ST-60-13_0460538",1,"Created","Evaluation tests shall be performed as specified in Table 6-1."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","6.3.2a","Requirement","ECSS-Q-ST-60-13_0460366",1,"Created","The supplier shall procure EEE components according to controlled specifications.","NOTE It can be procurer’s in-house specification, a manufacturer’s drawing or a datasheet as a minimum."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","6.3.3a","Requirement","ECSS-Q-ST-60-13_0460373",1,"Created","All components to be incorporated into flight standard hardware shall be subjected to screening."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","6.3.5c","Requirement","ECSS-Q-ST-60-13_0460547",1,"Created","Lot acceptance of retinned components shall be performed as specified in Figure 8-6 from the requirement 8.1a."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","6.3.9a","Requirement","ECSS-Q-ST-60-13_0460392",1,"Created","The DPA process shall be documented by a procedure to be sent, on request, to the customer for review.","NOTE Annex H provides guidelines for the construction analysis and destructive physical analysis."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","6.3.10c","Requirement","ECSS-Q-ST-60-13_0460552",1,"Created","Humidity test and lifetest shall be performed in accordance with the clause 6.3.5 in case if these tests have not been performed on the lot during the evaluation or the procurement phase.","NOTE Humidity test includes HAST or THB."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","6.4a","Requirement","ECSS-Q-ST-60-13_0460407",1,"Created","The supplier shall establish and implement procedures for handling and storage of components in order to prevent possible degradation."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","6.5.2a","Requirement","ECSS-Q-ST-60-13_0460412",1,"Created","The supplier shall establish and maintain a nonconformance control system in accordance with the general requirements in ECSS-Q-ST-10-09."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","6.5.4c","Requirement","ECSS-Q-ST-60-13_0460420",1,"Created","In any case, the traceability requirements imposed by the supplier on the EEE parts manufacturer or distributor shall allow managing the adequacy of the tests performed by the supplier (i.e. evaluation, lot validation, any additional test or inspection). "]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","6.6.4g","Requirement","ECSS-Q-ST-60-13_0460433",1,"Created","The lot acceptance procedure, as defined in clause 6.3.5, shall be performed on devices coming from the flight lot/date code and programmed using on the same kind of hardware tools and compatible software."]
["ECSS-Q-ST-60-13C","ECSS - Superseded v1.0","B.2.1a","Requirement","ECSS-Q-ST-60-13_0460439",1,"Created","The DCL shall include or refer to the following information:\n    1. A description of the purpose, content and the reason prompting its preparation, \n    2. A list of the applicable and reference documents,\n    3. Any additional terms, definitions or abbreviations,\n    4. Component number (commercial equivalent designation),\n    5. Family (ESCC group code),\n    6. Package,\n    7. Value or range of values with tolerance for non qualified parts,\n    8. Component manufacturer (name, country),\n    9. Generic procurement specification, \n    10. Detail procurement specification (with issue and revision for non qualified parts),\n    11. Specification amendment (including issue and revision),\n    12. Name of the procurement agents (CPPA, supplier, distributor),\n    13. Quality level and lot test (ESCC LAT or LVT, MIL TCI or QCI or CI),\n    14. Space qualified status (yes or no),\n    15. RVT (yes or no),\n    16. Reference of the PAD or Justification Document, where required,\n    17. Approval status of the part,\n    18. Change identification between each DCL issue,\n    19. Date-code (only for “as built” DCL)."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","5.1.2d","Permission","ECSS-Q-ST-70-38_0210495",1,"Created","For supplier, already approved on the basis of reliable tests results which supported the approval of any deviation finally recorded in the PID, then the PID may supersede the corresponding requirements from this standard."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","5.2d","Requirement","ECSS-Q-ST-70-38_0210009",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","6.1b","Requirement","ECSS-Q-ST-70-38_0210284",1,"Created","Requirements from clause 5.1 from ECSS-Q-ST-70-08 shall apply for “Calibration”."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","6.6.7a","Requirement","ECSS-Q-ST-70-38_0210028",2,"Normative Change","Requirements from clause 5.6.7 from ECSS-Q-ST-70-08 shall apply for “Soldering irons and resistance soldering equipment”."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","6.7.1d","Requirement","ECSS-Q-ST-70-38_0210035",1,"Unchanged","Temperature and time profiles for assembly shall be identified by the supplier and approved by the Approval Authority."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","6.7.3a","Requirement","ECSS-Q-ST-70-38_0210037",2,"Normative Change","Condensation reflow machines shall conform to the following requirements:\n1.\tNot transmit a movement or vibration into the assemblies being soldered that result in misalignment of devices or disturbed solder joints.\n2.\tBe capable of preheating an assembly with solder paste to the temperature recommended by the solder paste manufacturer prior to soldering.\n3.\tUse a reflow fluid whose boiling point is a minimum of 12 °C above the melting point of the solder being used.\n4.\tMaintain the preselected temperature to within ±5 °C in the reflow zone during soldering.\n5.\tInclude an extraction system that conforms to requirements 6.2a and 6.3a."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","6.8.5a","Requirement","ECSS-Q-ST-70-38_0210049",2,"Normative Change","Requirements from clause 11.3.1 from ECSS-Q-ST-70-08 shall apply for “Cleanliness testing”."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","6.8.7d","Requirement","ECSS-Q-ST-70-38_0210054",1,"Informative Change","The sensitivity shall be demonstrated by means of actual 0,03 mm diameter solder balls, stuck to adhesive tape, attached to the multilayer board assembly being inspected.","NOTE\t<<deleted>>\n"]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","7.2.4b","Requirement","ECSS-Q-ST-70-38_0210063",1,"Unchanged","Manufacturers’ instructions shall be applied for the handling and storage of containers of solder paste purchased premixed."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","7.3.1a","Requirement","ECSS-Q-ST-70-38_0210069",2,"Normative Change","Requirements from clause 6.3.1 from ECSS-Q-ST-70-08 shall apply for \"Rosin based flux\"."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","7.8.2a","Requirement","ECSS-Q-ST-70-38_0210079",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","7.9.1a","Requirement","ECSS-Q-ST-70-38_0210084",2,"Normative Change","Devices and their finishes shall be selected from those approved in conformance with requirements from clauses 4, 5 and 6 of ECSS-Q-ST-60, for “manufacturer and component evaluation” and “Procurement control”."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","7.9.1g","Requirement","ECSS-Q-ST-70-38_0210090",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","7.9.3a","Requirement","ECSS-Q-ST-70-38_0210096",2,"Normative Change","Moisture sensitive devices shall be stored and handled in conformance with the device manufacturer’s recommendations. .","NOTE\tMany types of plastic encapsulated devices, particularly some plastic BGAs, are moisture sensitive.\n"]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","7.10a","Requirement","ECSS-Q-ST-70-38_0210103",2,"Normative Change","Adhesives shall be dispensable, non-stringing, and have a reproducible dot profile after application. "]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","7.10j","Requirement","ECSS-Q-ST-70-38_0210298",1,"Created","Bonding shall not be performed on fused tin lead unless the tin lead surface is limited to < 25 % by area of the bonding surface and demonstrated by verification as specified in clause 14."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","8.4a","Requirement","ECSS-Q-ST-70-38_0210117",2,"Normative Change","Requirements from clause 7.6 from ECSS-Q-ST-70-08 shall apply for \"Storage\"."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","8.5f","Requirement","ECSS-Q-ST-70-38_0210306",1,"Created","Baking of populated PCB shall be made at a temperature which does not degrade the devices or assembly.","NOTE\tTo limit the bake out operation, which can induce later failure, the PCB can be stored in dry environment after the baking.\n"]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","9.7.1c","Requirement","ECSS-Q-ST-70-38_0210129",1,"Unchanged","Devices incapable of withstanding machine soldering temperatures shall be hand soldered in a subsequent operation."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","9.7.4e","Requirement","ECSS-Q-ST-70-38_0210310",1,"Created","Formed leads shall not be re-bent."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","9.7.6d","Requirement","ECSS-Q-ST-70-38_0210142",1,"Unchanged","Devices that are bonded to the PCB prior to wave- or reflow-soldering shall be placed so that the requirements after soldering given in clause 11 are met."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","9.7.7a","Requirement","ECSS-Q-ST-70-38_0210145",2,"Normative Change","Surface mounting of leaded (round or rectangular cross section) devices shall be parallel to the board surface."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","9.7.9h","Requirement","ECSS-Q-ST-70-38_0210313",1,"Created","Stacking and bonding shall be performed on clean surfaces."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","11.5.1b","Requirement","ECSS-Q-ST-70-38_0210159",2,"Normative Change","Soldering to gold with tin-lead alloys shall not be performed.","NOTE\t1\tSee also requirement 11.5.1h. \nNOTE\t2\tSee also clause 8.1.3 \"Degolding and pretinning of conductors\".\n"]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","11.5.1n","Requirement","ECSS-Q-ST-70-38_0210321",1,"Created","The footprint design shall be done in such way as to avoid, during soldering, contact between the device and the soldering tip."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","11.5.3b","Requirement","ECSS-Q-ST-70-38_0210323",1,"Created","Solder fillet shall show acceptable wetting on all visible sides."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","11.5.10b","Requirement","ECSS-Q-ST-70-38_0210334",1,"Created","Solder fillet shall be visible on the side of the terminal on the connection."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","11.5.13b","Requirement","ECSS-Q-ST-70-38_0210349",1,"Created","Solder fillet shall be visible in the heel fillet."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","13.1a","Requirement","ECSS-Q-ST-70-38_0210181",2,"Normative Change","Each soldered connection shall be visually inspected in accordance with the criteria specified in the requirements 13.1d, 13.1e, and 13.1f"]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","13.1e","Requirement","ECSS-Q-ST-70-38_0210185",2,"Normative Change","The substrate, solder joint, devices and device position, shall be inspected in accordance with the requirements in clause 11.5.","NOTE\tAnnex I includes examples of acceptable and unacceptable workmanship.\n"]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.1c","Requirement","ECSS-Q-ST-70-38_0210193",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.1h","Requirement","ECSS-Q-ST-70-38_0210198",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.1u","Requirement","ECSS-Q-ST-70-38_0210364",1,"Created","Sensitive devices shall be submitted to re-verification every four years to monitor the stability of the assembly."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.2c","Requirement","ECSS-Q-ST-70-38_0210205",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.2.1a","Requirement","ECSS-Q-ST-70-38_0210368",1,"Created","A package shall be identified as the same family in case the following conditions are met:\n1.\tthe lead pitch, nominal thickness, nominal width and materials composition are identical,\n2.\tthe coated lead finishes on the termination are identical,\n3.\tthe bending dimensions and shape are identical,\n4.\tthe packages are constructed from the same materials.","NOTE\t1\tGlass to metal sealed, glass sealed side-brazed, top-brazed, and bottom-brazed packages are different families.\nNOTE\t2\tDual side pin arrangements are different to quad side pin families.\n"]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.2.2d","Requirement","ECSS-Q-ST-70-38_0210372",1,"Created","Verification by similarity for leaded devices, cylindrical or square end-capped devices with cylindrical body and device with inward formed L-shaped leads shall be valid in case the following conditions are met:\n1.\tthe devices are from the same family in conformance with the requirements from the clause 14.2.1,\n2.\tdevices are smaller than the verified Lmax and Wmax, \n3.\tdemonstration that small package is not damaged during the placement on PCB.","NOTE\tThe dimension L is the distance between the outermost leads of the device and W is the device width.\n"]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.3d","Permission","ECSS-Q-ST-70-38_0210503",1,"Created","When mechanical bonding is underneath the device, microsectioning of one device may be performed after vibration and 50 thermal cycles to justify the integrity of the bonding.","NOTE\tThe device can be one of the three assembled devices.\n"]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.3p","Requirement","ECSS-Q-ST-70-38_0210387",1,"Created","The supplier shall organise with the Approval Authority a final verification review in conformance with requirements from clause 14.15.5.","NOTE\tThe Assembly processes can be reviewed during the meeting in order to have the PID issued. Verification of closure of the actions identified during the audit of the manufacturing line.\n"]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.4.1c","Requirement","ECSS-Q-ST-70-38_0210392",1,"Created","Capacitors and “SMD - xx” devices shall be excluded from electrical monitoring.","NOTE\tCapacitor and “SMD-xx” devices such SMD05, SMD1, SMD2 and SMD5C are excluded as the failure mechanism is crack in ceramic.\n"]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.4.1j","Permission","ECSS-Q-ST-70-38_0210505",1,"Created","Capability samples may be excluded from the programme if it can be demonstrated through previous verification heritage."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.5j","Requirement","ECSS-Q-ST-70-38_0210408",1,"Created","The accelerometers shall be placed on the PCB as well as on the base plate in order to determine the acceleration of the PCB."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.7e","Requirement","ECSS-Q-ST-70-38_0210226",2,"Deleted","<<deleted, modified and moved to 14.7.2>>"]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.7.1c","Requirement","ECSS-Q-ST-70-38_0210411",1,"Created","When in-house or other non-listed microsection facilities are used, the company shall demonstrate the following: \n1.\tthe laboratory capability on a representative sample without conformal coating is provided,\n2.\ta report with associated microsections is sent to the Approval Authority for review and assessment of quality of microsectioning, \n3.\trepresentative samples include chip devices, LCCs and FPs."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.8a","Requirement","ECSS-Q-ST-70-38_0210227",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.9.3a","Requirement","ECSS-Q-ST-70-38_0210425",1,"Created","The assembly verification of hermetic ceramic AADs shall be divided in the following two parts, as shown in Figure 14-3.\n1.\telectrical monitoring, and\n2.\tdemonstration of capability. ","NOTE\t1\tThe purpose of the capability samples is to show that the PCB integrity and the device are intact after the assembly and repair of AAD and environmental testing (vibration, mechanical shock and 500 temperature cycles). A crack in the columns or balls is not considered as reason for rejection.\nNOTE\t2\tOnce the capability samples show a satisfactory result the verification of AAD can commence.\nNOTE\t3\tCapability samples can be excluded from the programme if the supplier can demonstrate through previous verification heritage.\n"]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.9.4b","Requirement","ECSS-Q-ST-70-38_0210429",1,"Created","The PCB material, PCB build-up, foot print and devices used as capability samples shall be representative for the FM of the hardware."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.9.5g","Requirement","ECSS-Q-ST-70-38_0210443",1,"Created","The five devices shall be submitted to 1500 thermal cycles with temperature conditions in conformance with requirements from the clause 13.2 of ECSS-Q-ST-70-08."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.9.5l","Requirement","ECSS-Q-ST-70-38_0210447",1,"Created","The maximum increase of each individual daisy chain resistance, across the entire temperature cycling range during 1500 thermal cycles, shall not be more than 10 % of initial resistance recorded during the first five cycles."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.10h","Requirement","ECSS-Q-ST-70-38_0210449",1,"Created","The devices shall be in conformance with the assembly requirements of clause 11.5."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.10n","Requirement","ECSS-Q-ST-70-38_0210455",1,"Created","Acceptance and rejection criterion for PCBs shall be in compliance with clause 7.2 of ECSS-Q-ST-70-10."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.13g","Requirement","ECSS-Q-ST-70-38_0210462",1,"Created","Number of sensitive parts to be assembled and microsectioned shall be five."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.15.1a","Requirement","ECSS-Q-ST-70-38_0210466",1,"Created","Verification approval procedure shall list the single point contact for all SMT matters."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","14.15.3b","Requirement","ECSS-Q-ST-70-38_0210471",1,"Created","The Approval Authority shall inform the supplier on acceptance regarding the start of the next stages of the approval process."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","15.4a","Requirement","ECSS-Q-ST-70-38_0210249",2,"Normative Change","Requirements from clause 14.4 from ECSS-Q-ST-70-08 shall apply for \"Calibration\"."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","15.8a","Requirement","ECSS-Q-ST-70-38_0210256",2,"Normative Change","Requirements from clause 18.8 from ECSS-Q-ST-70-08 shall apply for \"Operator and inspector training and certification\"."]
["ECSS-Q-ST-70-38C Rev.1 Corr.1","ECSS - Superseded v1.0","F.2.1<2>a","Requirement","ECSS-Q-ST-70-38_0210483",1,"Created","The PID shall contain the Manufacturing control flow chart of the verified SMT.","NOTE 1\tThis illustrates the various stages of procurement, manufacturing and inspection operations specific to this technology in a flow chart format.\nNOTE 2\tIt can be used to identify, among others:\n·\tthe operation,\n·\tthe body responsible for its implementation,\n·\trelated documents: (only their reference),\n·\tprocurement specifications (for materials),\n·\tacceptance inspection procedures (for materials and devices),\n·\tmanufacturing procedures,\n·\tmanufacturing and quality control procedures during and at the end of production.\n"]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","4.1.2.1a","Requirement","ECSS-Q-ST-60_0480002",1,"Unchanged","The supplier shall identify the organization responsible for the management of the component programme, and describe the organization’s approaches (including the procurement system and its rationale) and capability to efficiently implement, manage, and control the component requirements."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","4.1.3b","Requirement","ECSS-Q-ST-60_0480008",2,"Unchanged","At supplier's level, the Parts Control Board (PCB) shall be composed as follows:\n1.\tchaired by a member of the supplier’s PA team with designated responsibility for components management,\n2.\tinclude, as a minimum, in addition the suppliers’ parts engineer, the customer’s representative and the lower tier subcontractor parts engineers."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","4.1.4a","Requirement","ECSS-Q-ST-60_0480011",2,"Unchanged","For each equipment, its supplier shall issue a DCL in an editable and sortable electronic format, as a minimum compatible with CSV, identifying all component types needed.","NOTE \tCSV is a common file format that can be used to transfer data between database or spreadsheet tables (a spreadsheet program is for example Excel®).\n"]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","4.2.2.1b","Requirement","ECSS-Q-ST-60_0480023",1,"Unchanged","Components shall be selected on the basis of proven qualification, characterization,  and previous space experience and data, relevant with regard to the requirements for the programme, from manufacturers or sources (preferably European) employing effective Product Assurance Programmes in manufacturing and test."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","4.2.2.2f","Permission","ECSS-Q-ST-60_0480494",1,"Unchanged","The use of pure tin in internal cavities may be authorized, on a case-by-case basis, based on the demonstration that there is no alternative product and there is no risk (supported by a technical justification)."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","4.2.2.2j","Requirement","ECSS-Q-ST-60_0480526",1,"Created","The following actions shall be performed by the supplier to control the pure-tin risk:\n1.\tCollect and synthesize all information participating to the risk analysis in conformance with Clause 9.\n2.\tBased on the risk analysis, elaborate a mitigation plan.\n3.\tInclude in the JD the risk analysis and mitigation plan for customer approval.\n4.\tBefore retinning of flight parts, document the hot solder dip process by a procedure to be submitted to customer for approval.\n5.\tPerform evaluation tests, lot acceptance tests and screening tests of retinned components after the retinning process.","NOTE\t1\tThe mitigation plan can include one or a combination of the following solutions:\n·\tTin whisker sensitivity evaluation\n·\tRetinning of terminations with complementary evaluation,\n·\tConformal coating,\n·\tDesign modification.\nNOTE\t2\tSolder dip for tin whisker mitigation differs from solder dip for solderability in that for tin whisker mitigation, the termination is coated over its entire length, right up to the package surface (no stand off). As this process is critical it is good practice to evaluate it and control it well.\n"]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","4.2.2.3g","Requirement","ECSS-Q-ST-60_0480027",1,"Unchanged","The supplier shall implement a type reduction activity."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","4.2.2.5b","Requirement","ECSS-Q-ST-60_0480049",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","4.2.3.1c","Requirement","ECSS-Q-ST-60_0480052",1,"Unchanged","The scope and planning of the component evaluation shall be derived from the results of an assessment of the design and intended application of the component. "]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","4.2.3.1i","Requirement","ECSS-Q-ST-60_0480058",2,"Normative Change","The supplier shall review the evaluation results to determine their impact on the content of the procurement specification and amend it as necessary."]
["ECSS-Q-ST-60-13C Rev.1","ECSS - Superseded v1.0","4.2.3.4c","Requirement","ECSS-Q-ST-60-13_0460482",1,"Created"]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","4.3.1b","Requirement","ECSS-Q-ST-60_0480073",1,"Unchanged","Class 1 components shall meet the quality levels ands supplementary conditions specified in Table 7-1."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","4.3.1d","Requirement","ECSS-Q-ST-60_0480075",1,"Unchanged","For non qualified parts, the supplier shall put in place a configuration control system to ensure that any change of the product (e.g. mask, manufacturing and assembly process) affecting evaluation, performance, quality, reliability and interchangeability is communicated to him by the manufacturer (e.g. PCN)."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","4.3.2b","Requirement","ECSS-Q-ST-60_0480080",1,"Unchanged","International specifications systems, recognized as suitable for space applications (e.g. ESCC, MIL), shall be used by the supplier. "]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","4.3.3h","Requirement","ECSS-Q-ST-60_0480450",2,"Normative Change","In case of X-rays or CT scan inspection, the total dose deposited and exposure time shall not deteriorate part performance or reliability."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","4.3.5b","Requirement","ECSS-Q-ST-60_0480095",2,"Unchanged","The sample size for lot acceptance which may be reduced in some cases, shall be submitted to the customer for approval through the PAD process (see clause 4.2.4)."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","4.3.8c","Requirement","ECSS-Q-ST-60_0480107",1,"Unchanged","In such a case, a PAD in conformance with Annex D shall be issued and processed as per clause 4.2.4."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","4.3.9c","Permission","ECSS-Q-ST-60_0480498",1,"Unchanged","DPA may be carried out on representative samples of the components families when the following three conditions are met:\n1.\tprocured from the same manufacturer and same package without major change in the process,\n2.\twith a limited datecode range of 13 weeks,\n3.\tapproved by the customer through the PAD process.","NOTE \tIn complement of above conditions, for series of integrated circuits, series of thermal switches, series of active discrete and series of passive components (e.g. 54xxxx, 1N63xx, …), representative samples can be from the same family considering technology limit and their complexity.\n"]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","4.3.10b","Requirement","ECSS-Q-ST-60_0480121",2,"Normative Change","For components meeting the criteria specified in requirement 4.3.10a, and which have a lot / date code exceeding the period defined in ECSS-Q-ST-60-14 clause 5, the relifing procedure ECSS-Q-ST-60-14 shall apply to the lot."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","4.4b","Requirement","ECSS-Q-ST-60_0480126",1,"Unchanged","The procedures shall be applicable at any facility dealing with components for flight application."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","4.5.2b","Requirement","ECSS-Q-ST-60_0480131",1,"Unchanged","Any observed deviation of EEE components from requirements as laid down in applicable specifications, procedures and drawings shall be controlled by the nonconformance control system.","NOTE \tThis includes failures, malfunctions, deficiencies and defects.\n"]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","4.5.5b","Requirement","ECSS-Q-ST-60_0480143",2,"Unchanged","For radiation tests, the set of test samples shall be in accordance with ECSS-Q-ST-60-15. "]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","4.6.4b","Requirement","ECSS-Q-ST-60_0480148",1,"Unchanged","The PAD shall allow traceability to the information related to the procurement of blank parts, the programming process and the acceptance of the programmed parts.","NOTE \tThe programming process and the acceptance of the programmed parts are under the authority of the PCB if not otherwise determined in the PAD.\n"]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","5.1.2.1a","Requirement","ECSS-Q-ST-60_0480158",1,"Unchanged","The supplier shall identify the organization responsible for the management of the component programme, and describe the organization’s approaches (including the procurement system and its rationale) and capability to efficiently implement, manage, and control the component requirements."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","5.1.4b","Requirement","ECSS-Q-ST-60_0480166",2,"Unchanged","The list specified in 5.1.4a shall be kept under configuration control (issue and identification of changes). "]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","5.1.5b","Requirement","ECSS-Q-ST-60_0480174",2,"Unchanged","Flight hardware connector interfaces to GSE shall interface to a flight compatible connector, as per 5.1.5a.2.","NOTE \tThis connector can be installed on the test harness or can be a saver.\n"]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","5.2.1a","Requirement","ECSS-Q-ST-60_0480175",1,"Unchanged","The supplier shall ensure that the following requirements are met during his selection process:\n1.\tProject requirements (e.g. quality levels, component policy, manufacturing and delivery schedules and budgets, and quantities), \n2.\tDesign requirements (e.g. component type, case, dimensions, and materials), \n3.\tProduction requirements (e.g. packaging, thermal and storage constraints, component mounting and process), \n4.\tOperational requirements (e.g. electrical, mechanical, radiation, reliability, assembly, and lifetime).","NOTE \tThe supplier of each product is responsible for the selection of components, which enable the performance, lifetime, environmental, material, safety, quality and reliability requirements of the product of which they form a part, to be satisfied in all respects.\n"]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","5.2.2.2l","Requirement","ECSS-Q-ST-60_0480537",1,"Created","If one of the three conditions specified in requirement 5.2.2.2k is not met, a mitigation plan shall be submitted to the customer for approval, through the JD approval process.","NOTE \tThis mitigation plan can include, as an example, one of the following solutions:\n·\tConformal coating,\n·\tDesign analysis and risk assessment versus a possible short circuit.\n"]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","5.2.2.3b","Requirement","ECSS-Q-ST-60_0480189",1,"Unchanged","The supplier who is responsible for the design of the piece of hardware shall demonstrate the compliance of its components selection with the radiation constraints of the project. "]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","5.2.2.4b","Requirement","ECSS-Q-ST-60_0480198",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","5.2.3.1g","Requirement","ECSS-Q-ST-60_0480205",1,"Unchanged","All tests and inspections shall be carried out on representative samples of the component type from the current production of the manufacturer selected for the component procurement for the flight hardware."]
["ECSS-Q-ST-60-13C Rev.1","ECSS - Superseded v1.0","5.2.3.1l","Requirement","ECSS-Q-ST-60-13_0460507",1,"Unchanged"]
["ECSS-Q-ST-60-13C Rev.1","ECSS - Superseded v1.0","5.2.3.4c","Requirement","ECSS-Q-ST-60-13_0460510",2,"Normative Change"]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","5.3.1c","Requirement","ECSS-Q-ST-60_0480222",1,"Unchanged","The supplier shall be responsible for manufacturer surveillance and control throughout the procurement programme."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","5.3.2a","Requirement","ECSS-Q-ST-60_0480227",1,"Unchanged","The supplier shall procure EEE components according to controlled specifications.","NOTE\tIt can be procurer’s in-house specification, a manufacturer’s drawing or a datasheet as a minimum."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","5.3.2f","Requirement","ECSS-Q-ST-60_0480232",1,"Unchanged","Upon request, any new procurement specification prepared in the frame of the project, shall be delivered to the customer."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","5.3.3d","Requirement","ECSS-Q-ST-60_0480237",2,"Unchanged","The quality levels defined in Table 7-2 shall apply. "]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","5.3.6c","Permission","ECSS-Q-ST-60_0480505",1,"Unchanged","The buy-off may be replaced by an incoming inspection at the procurement entity's facilities; "]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","5.3.8a","Requirement","ECSS-Q-ST-60_0480252",1,"Unchanged","Radiation sensitive components, as defined in clause, 5.2.2.3 and for which applicable existing test data is insufficient shall be subjected to RVT."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","5.3.9d","Requirement","ECSS-Q-ST-60_0480260",2,"Normative Change","The DPA process shall be documented by a procedure to be submitted, on request, to the customer for information.","NOTE\tFor guidance refer to the basic specificaton ESSC 20600 and for active parts ECSS-Q-ST-60-13 Annex H."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","5.4c","Requirement","ECSS-Q-ST-60_0480273",1,"Unchanged","On request, handling and storage procedures shall be sent to the customer for review."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","5.5.2c","Requirement","ECSS-Q-ST-60_0480278",1,"Unchanged","The nonconformance control system shall handle all nonconformances occurring on EEE components during: \n1.\tManufacture (if available), screening and acceptance tests, \n2.\tIncoming inspection,\n3.\tIntegration and test of equipment,\n4.\tStorage and handling."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","5.5.3b","Requirement","ECSS-Q-ST-60_0480281",1,"Unchanged","If alerts become available at a later stage, the supplier shall analyse the alerts, analyse the project risk and propose an action plan for customer approval. "]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","5.6.4e","Requirement","ECSS-Q-ST-60_0480295",3,"Normative Change","For one time programmable FPGA and PROM  without a clear and defined heritage, a post-programming burn-in shall be applied, in conformance with ESCC9000 subclause 8.16, for a minimum duration of 160 h.","NOTE \tFPGA and PROM  with defined heritage are documented in these reports: ESCC REP 010 and ESCC REP011, available on https://escies.org.\n"]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","5.6.4g","Requirement","ECSS-Q-ST-60_0480297",2,"Unchanged","The lot acceptance procedure, as defined in clause 5.3.5, shall be performed on devices coming from the flight lot/date code and programmed on the same kind of hardware tools and compatible software."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","6.1.3a","Requirement","ECSS-Q-ST-60_0480305",2,"Unchanged","<<deleted>>"]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","6.1.5a","Requirement","ECSS-Q-ST-60_0480313",2,"Unchanged","EEE components used in GSE, which are physically and directly interfacing to flight hardware, shall be:\n1.\tFit Form and Function compatible, \n2.\tmanufactured from materials identical to the flight opposite part,\n3.\tensured to be visibly clean before each connection to flight hardware. "]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","6.2.2.2c","Requirement","ECSS-Q-ST-60_0480322",3,"Normative Change","With respect to health and safety, beryllium oxide and lithium (except for the one which is identified in the procurement specification), cadmium, magnesium, mercury, zinc, radioactive material and all material which can cause safety hazard shall not be used."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","6.2.2.2k","Requirement","ECSS-Q-ST-60_0480545",1,"Created","All the following conditions shall be fulfilled to use Parts with matte pure tin finish, >97% tin:\n1.\tThey pass the JESD-201A class 2 requirements or meet the GEIA-STD-0005-2/Level 2B requirements,\n2.\tThey are not used in power function, where both Voltage >15 V and Current >2 A conditions are applied at the same time,\n3.\tThey are not mechanically torqued on board or equipment."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","6.2.2.4f","Requirement","ECSS-Q-ST-60_0480334",1,"Unchanged","The supplier shall identify components which are not compliant with the radiation requirements as critical radiation sensitive components. "]
["ECSS-Q-ST-60-13C Rev.1","ECSS - Superseded v1.0","6.2.2.6d","Requirement","ECSS-Q-ST-60-13_0460673",1,"Created"]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","6.2.3.1h","Requirement","ECSS-Q-ST-60_0480347",1,"Unchanged","For programmable devices, the representativeness shall include the programming hardware tools and the compatibility of the software."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","6.2.3.1j","Requirement","ECSS-Q-ST-60_0480349",2,"Unchanged","The supplier shall summarize the evaluation results in the evaluation report and send it to the customer for approval.","NOTE \tFor guidance for the assessment of the space environmental aspects refer to ECSS-E-ST-10-04 and ECSS E-ST-10-12.\n"]
["ECSS-Q-ST-60-13C Rev.1","ECSS - Superseded v1.0","6.2.3.4d","Requirement","ECSS-Q-ST-60-13_0460539",2,"Normative Change"]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","6.3.1c","Requirement","ECSS-Q-ST-60_0480364",1,"Unchanged","The supplier shall be responsible for manufacturer surveillance and control throughout the procurement programme."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","6.3.2e","Requirement","ECSS-Q-ST-60_0480370",1,"Unchanged","The use of any new specification or datasheet shall be submitted to the customer for review through the approval process (see clause 6.2.4)."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","6.3.5a","Requirement","ECSS-Q-ST-60_0480379",3,"Normative Change","The supplier shall ensure that any lot/date code of EEE parts is submitted to a lot acceptance procedure, in line with applied normative systems, according to the following rules:\n1.\tSpace qualified parts: \n(a)\tESCC: user’s lot acceptance on the procured lot/date code is not required due to periodic lot validation testing performed by the manufacturer.\n(b)\tMIL: QCI or TCI performed by the manufacturer is in accordance with the quality level of the MIL specification.\n2.\tOther HiRel qualified parts: \n(a)\tThe content of the lot acceptance is defined according to the available data. \n(b)\tThe proposed lot acceptance is approved through the approval process (see clause 6.2.4).\n3.\tCommercial parts:\n(a)\tThe content of the lot acceptance is defined according to information provided by the justification document according to ECSS-Q-ST-60-13.\n(b)\tThe proposed lot acceptance is approved through the approval process in accordance with clause 6.2.4."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","6.3.7c","Requirement","ECSS-Q-ST-60_0480384",1,"Unchanged","The incoming inspection shall be documented by a procedure to be presented, on request, to the customer for review."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","6.3.9a","Requirement","ECSS-Q-ST-60_0480392",2,"Unchanged","The DPA shall be performed on 3 samples per lot/date code for the following non-space qualified part types, as a minimum relays and commercial parts."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","6.3.9f","Permission","ECSS-Q-ST-60_0480517",2,"Deleted","<<deleted>>"]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","6.3.11a","Requirement","ECSS-Q-ST-60_0480404",1,"Unchanged","The manufacturer’s CoC shall be delivered to the parts procurer. "]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","6.5.2d","Requirement","ECSS-Q-ST-60_0480415",1,"Unchanged","For ESCC qualified components the supplier shall apply the ESCC basic specification no 22800."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","6.5.4e","Requirement","ECSS-Q-ST-60_0480422",2,"Unchanged","The supplier shall be able to provide these information (part type actually installed with its relevant lot/date code number) within one working day (when the flight system is on launch pad) or within one week (in the other cases)."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","6.6.4e","Requirement","ECSS-Q-ST-60_0480431",3,"Normative Change","For one time programmable FPGA and PROM  without a clear and defined heritage, a post-programming burn-in shall be applied, in conformance with ESCC9000 subclause 8.16, for a minimum duration of 160 h.","NOTE \tFPGA and PROM  with defined heritage are documented in these reports: ESCC REP 010 and ESCC REP011, available on https://escies.org.\n"]
["ECSS-Q-ST-60-13C Rev.1","ECSS - Superseded v1.0","8.2b","Permission","ECSS-Q-ST-60-13_0460699",1,"Created",null,"NOTE\tThis permission is referenced in the Procurement Test Tables as “Note (a)”.\n"]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","A.2.2a","Permission","ECSS-Q-ST-60_0480521",1,"Unchanged","The CCP may be part of the overall project PA plan (see clause 4.1.2.2b)."]
["ECSS-Q-ST-60C Rev. 3","ECSS - Superseded v1.0","D.2a","Requirement","ECSS-Q-ST-60_0480441",1,"Unchanged","The information given in Table D-1 shall be provided. "]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","5.2.1.3a","Requirement","ECSS-Q-ST-80_0720016",1,"Unchanged","The software product assurance plan shall be revisited and updated as needed at each milestone to ensure that the activities to be undertaken in the following phase are fully defined.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","5.2.1.5a","Requirement","ECSS-Q-ST-80_0720018",1,"Unchanged","The supplier shall provide with the software product assurance plan a compliance matrix documenting conformance with the individual software product assurance requirements applicable for the project or business agreement.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","5.2.5.3a","Requirement","ECSS-Q-ST-80_0720027",1,"Unchanged","The procedures for software problems shall define the interface with the nonconformance system (i.e. the circumstances under which a problem qualifies as a nonconformance).\n","EXPECTED OUTPUT: Software problem reporting procedures [PAF, -; PDR]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","5.3.2.1a","Requirement","ECSS-Q-ST-80_0720035",1,"Unchanged","For critical item control, ECSS-Q-ST-10-04 shall apply."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","5.4.4a","Requirement","ECSS-Q-ST-80_0720045",1,"Unchanged","The supplier shall provide the lower level suppliers with the relevant results of the safety and dependability analyses performed at higher and his level (ref. clauses 6.2.2.1 and 6.2.2.2), including:\n    1. the criticality classification of the software products to be developed;\n    2. information about the failures that can be caused at higher level by the software products to be developed.\n","EXPECTED OUTPUT: Safety and dependability analyses results for lower level suppliers [RB, -; SRR]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","5.6.1.3a","Requirement","ECSS-Q-ST-80_0720054",1,"Unchanged","The correct use of methods and tools shall be verified and reported. \n","EXPECTED OUTPUT: Software product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","5.7.3.1b","Requirement","ECSS-Q-ST-80_0720064",1,"Unchanged","The suppliers shall ensure that the results of previous assessments are used in its project activity \n","EXPECTED OUTPUT: Software process assessment records: improvement plan [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","6.2.1.1a","Requirement","ECSS-Q-ST-80_0720073",1,"Unchanged","The following activities shall be covered either in software-specific plans or in project general plans:\n    1. development;\n    2. specification, design and customer documents to be produced;\n    3. configuration and documentation management;\n    4. verification, testing and validation activities;\n    5. maintenance.\n","EXPECTED OUTPUT: Software project plans [MGT, MF, DJF]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","6.2.2.1a","Requirement","ECSS-Q-ST-80_0720082",2,"Normative Change","For the system-level analyses leading to the criticality classification of software products based on the severity of failures consequences, ECSS-Q-ST-40 clause 6.5.6.3, and ECSS-Q-ST-30 clause 5.4, shall apply.\n","EXPECTED OUTPUT: Criticality classification of software products [PAF, -; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","6.2.2.3a","Requirement","ECSS-Q-ST-80_0720084",1,"Unchanged","The supplier shall identify the methods and techniques for the software dependability and safety analysis to be performed at technical specification and design level."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","6.2.3.3a","Requirement","ECSS-Q-ST-80_0720095",1,"Unchanged","The application of the chosen measures to handle the critical software shall be verified.\n","EXPECTED OUTPUT: Software product assurance milestone report [PAF, SPAMR; PDR, CDR, QR, AR]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","6.2.4.2a","Requirement","ECSS-Q-ST-80_0720102",1,"Unchanged","The software configuration management system shall allow any reference version to be re-generated from backups.\n","EXPECTED OUTPUT: Software configuration management plan [MGT, SCMP; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","6.2.4.10a","Requirement","ECSS-Q-ST-80_0720111",1,"Unchanged","The checksum value shall be provided in the software configuration file with each software delivery.\n","EXPECTED OUTPUT: Software configuration file [DDF, SCF; -]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","6.2.6.6a","Requirement","ECSS-Q-ST-80_0720124",1,"Unchanged","Software containing configurable code shall be verified specifically to ensure that any unintended configuration cannot be activated at run time or included during code generation.\n","EXPECTED OUTPUT: Software verification report [DJF, SVR; CDR, QR, AR]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","6.2.6.12a","Requirement","ECSS-Q-ST-80_0720130",1,"Unchanged","Traceability matrices (as defined in ECSS-E-ST-40 clause 5.8) shall be verified at each milestone.\n","EXPECTED OUTPUT: Software product assurance milestone report [PAF, SPAMR; SRR, PDR, CDR, QR, AR, ORR]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","6.2.7.2a","Requirement","ECSS-Q-ST-80_0720133",1,"Unchanged","Analyses of the advantages to be obtained with the selection of existing software (ref. 3.2.11) instead of new development shall be carried out.\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Software reuse approach, including approach to delta qualification [PAF, SPAP; SRR, PDR];\n          b.Software reuse file [DJF, SRF; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","6.2.8.6a","Requirement","ECSS-Q-ST-80_0720149",1,"Unchanged","Clause 6.3.4 shall apply to automatically generated code, unless the supplier demonstrates that the automatically generated code does not need to be manually modified."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","6.3.1.1a","Requirement","ECSS-Q-ST-80_0720151",1,"Unchanged","For the definition of the software related system requirements to be specified in the requirements baseline, ECSS-E-ST-40 clause 5.2 shall apply."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","6.3.3.2a","Requirement","ECSS-Q-ST-80_0720160",1,"Unchanged","Mandatory and advisory design standards shall be defined and applied.\n","EXPECTED OUTPUT: Design standards [PAF, -; SRR, PDR]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","6.3.4.3a","Requirement","ECSS-Q-ST-80_0720169",1,"Unchanged","The tools to be used in implementing and checking conformance with coding standards shall be identified in the product assurance plan before coding activities start.\n","EXPECTED OUTPUT: Software product assurance plan [PAF, SPAP; PDR]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","6.3.5.5a","Requirement","ECSS-Q-ST-80_0720180",1,"Unchanged","Test coverage shall be checked with respect to the stated goals.\n","EXPECTED OUTPUT: Software product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","6.3.5.12a","Requirement","ECSS-Q-ST-80_0720188",1,"Unchanged","The supplier shall ensure that tests are repeatable by verifying the storage and recording of tested software, support software, test environment, supporting documents and problems found.\n","EXPECTED OUTPUT: Software product assurance reports [PAF, -; -]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","6.3.5.22a","Requirement","ECSS-Q-ST-80_0720198",1,"Unchanged","Tests shall be organized as activities in their own right in terms of planning, resources and team composition. \n","EXPECTED OUTPUT: Test and validation documentation [DJF, SValP; PDR], [DJF, SUITP; PDR, CDR]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","6.3.5.31a","Requirement","ECSS-Q-ST-80_0720207",1,"Unchanged","Software containing configurable code shall be validated specifically to ensure that unintended configuration cannot be activated at run time or included during code generation.\n","EXPECTED OUTPUT: Testing and validation reports [DJF, -; CDR, QR, AR]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","6.3.6.8a","Requirement","ECSS-Q-ST-80_0720216",1,"Unchanged","On completion of the acceptance tests, a report shall be drawn up and be signed by the supplier’s representatives, the customer’s representatives, the software quality engineers of both parties and the representative of the organization charged with the maintenance of the software product.\n","EXPECTED OUTPUT: Acceptance test report [DJF, -; AR]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","6.3.7.1a","Requirement","ECSS-Q-ST-80_0720218",1,"Unchanged","During operations, the quality of the mission products related to software shall be agreed with the customer and users.","NOTE Quality of mission products can include parameters such as: error-free data, availability of data and permissible outages; permissible information degradation.\nEXPECTED OUTPUT: Software operation support plan [OP, -; ORR]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","6.3.8.7a","Requirement","ECSS-Q-ST-80_0720227",1,"Unchanged","Maintenance records shall be established for each software product, including, as a minimum, the following information,:\n    1. list of requests for assistance or problem reports that have been received and the current status of each;\n    2. organization responsible for responding to requests for assistance or implementing the appropriate corrective actions;\n    3. priorities assigned to the corrective actions;\n    4. results of the corrective actions;\n    5. statistical data on failure occurrences and maintenance activities.","NOTE The record of the maintenance activities can be utilized for evaluation and enhancement of the software product and for improvement of the quality system itself.\nEXPECTED OUTPUT: Maintenance records [MF, -; -]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","7.2.1.1a","Requirement","ECSS-Q-ST-80_0720236",1,"Unchanged","The software quality requirements shall be documented in the requirements baseline and technical specification.","EXPECTED OUTPUT: The following outputs are expected:\n          a.Requirement baseline [RB, SSS; SRR];\n          b.Technical specification [TS, SRS; PDR]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","7.2.3.5a","Requirement","ECSS-Q-ST-80_0720246",1,"Unchanged","The hardware and software configuration shall be identified and documented as part of the test documentation."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","7.3.7a","Requirement","ECSS-Q-ST-80_0720254",1,"Unchanged","The supplier shall provide a certificate of conformance that the tests have been successfully completed on all the relevant platforms.","NOTE In case not all platforms are available, the certificate of conformance states the limitations of the validation performed.\nEXPECTED OUTPUT: Verification and validation documentation for reusable components [DJF, -; CDR]."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","B.2.1<3>a","Requirement","ECSS-Q-ST-80_0720265",1,"Unchanged","The SPAP shall include any additional terms, definition or abbreviated terms used."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","B.2.1<5.6>a","Requirement","ECSS-Q-ST-80_0720274",1,"Unchanged","The SPAP shall describe the contribution of the software product assurance function to the project risk management."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","B.2.1<6.2>a","Requirement","ECSS-Q-ST-80_0720283",1,"Unchanged","The SPAP shall describe all plans to be produced and used in the project."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","B.2.1<6.3>a","Requirement","ECSS-Q-ST-80_0720285",1,"Unchanged","The SPAP shall contain a description and justification of the measures to be applied for the handling of critical software, including the analyses to be performed and the standards applicable for critical software."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","C.2.1<3>a","Requirement","ECSS-Q-ST-80_0720301",1,"Unchanged","The SPAMR shall include any additional terms, definition or abbreviated terms used."]
["ECSS-Q-ST-80C Rev.1","ECSS - Superseded v1.0","C.2.1<5>a","Requirement","ECSS-Q-ST-80_0720304",1,"Unchanged","The SPAMR shall include or reference a justification of the suitability of the methods and tools applied in all the activities of the development cycle, including requirements analysis, software specification, design, coding, validation, testing, configuration management, verification and product assurance."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","5.3.2a","Recommendation","ECSS-Q-ST-70-60_1390724",1,"Created","For flexible PCBs, a company specific qualification with auditing and review of QA should be performed.","NOTE \tThis is good practice to verify batch-to-batch reproducibility.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","5.3.2i","Requirement","ECSS-Q-ST-70-60_1390011",1,"Created","Assembly to flexible PCB using PTH or SMT shall be verified in conformance with ECSS-Q-ST-70-08 and ECSS-Q-ST-70-38."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","5.5g","Requirement","ECSS-Q-ST-70-60_1390020",1,"Created","The PCB manufacturer shall demonstrate that it meets the requirements for quality assurance in conformance with clause 5.6."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","5.6c","Requirement","ECSS-Q-ST-70-60_1390023",1,"Created","The PCB manufacturer shall hold certification for its quality management system in conformance with ISO 9001:2015 and EN 9100:2016 or demonstrate that he has a quality management system in line with the above standards."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","5.9b","Requirement","ECSS-Q-ST-70-60_1390037",1,"Created","The audit shall occur when PCB production is in progress."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","5.9d","Requirement","ECSS-Q-ST-70-60_1390039",1,"Created","The qualification authority shall submit to the PCB manufacturer an audit checklist that verifies the requirements from ECSS-Q-ST-70-60 and its normative references one month prior to the date of the audit."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","5.9m","Requirement","ECSS-Q-ST-70-60_1390048",1,"Created","The final conclusion of the audit process shall be provided in the final audit report or minutes of meeting."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","5.12b","Requirement","ECSS-Q-ST-70-60_1390056",1,"Created","The qualification authority shall publish the qualification status."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","5.13f","Requirement","ECSS-Q-ST-70-60_1390064",1,"Created","For major and minor process changes, the PCB manufacturer shall issue a process change notice in conformance with the DRD in Annex E to the qualification authority."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","5.15e","Requirement","ECSS-Q-ST-70-60_1390071",1,"Created","Upon successful qualification renewal, the qualification authority shall approve the qualification in conformance with the clause 5.12 and issue a new qualification letter in conformance with requirement 5.12a."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","6.2.3d","Requirement","ECSS-Q-ST-70-60_1390076",1,"Created","The procurement authority shall record double insulation in the PCB definition dossier.","NOTE \tDouble insulation is specified for critical nets in conformance with requirement 13.9.2a from ECSS-Q-ST-70-12.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","6.2.6d","Requirement","ECSS-Q-ST-70-60_1390084",1,"Created","In case more than three prepreg sheets are used between layers, it shall be a review item in the MRR.","NOTE \tMore than three prepreg sheets can be used in case a large volume to be filled with resin while maintaining a specific dielectric thickness, such as for thick copper layers or blind vias.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","6.3i","Requirement","ECSS-Q-ST-70-60_1390093",1,"Created","The PCB manufacturer shall specify in its PID the range of etchback."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","6.4a","Requirement","ECSS-Q-ST-70-60_1390095",1,"Created","The PCB manufacturer shall retain the quality records for at least ten years and in accordance with business agreement requirements."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","6.5l","Requirement","ECSS-Q-ST-70-60_1390108",1,"Created","The verification and re-life procedure of prepreg shall be performed by the raw material supplier and documented in a new CoC for the prepreg.","NOTE\t1\tThe new prepreg CoC include a new shelf-life. Shelf-life and storage conditions are important for the flow factor of prepreg, particularly for no-flow prepreg.\nNOTE\t2\tIt is good practice to allow for the lead time for relife tests when anticipating supply of material for PCB manufacture.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","6.6c","Requirement","ECSS-Q-ST-70-60_1390111",1,"Created","Electrolytic soft gold plating shall have a purity of ≥ 99,8 % gold, except for the case of electrolytic hard gold plating."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","6.6l","Requirement","ECSS-Q-ST-70-60_1390119",1,"Created","ENIG, ENEPIG and ENIPIG adhesion shall be verified once per panel by peel test on a coupon specified by the PCB manufacturer."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","6.7.2f","Recommendation","ECSS-Q-ST-70-60_1390744",1,"Created","Prior to lay-up, cleaning of prepreg sheets and etched inner layers should be performed by using vacuum hovering or by use of tacky rollers or wipes."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","6.8g","Requirement","ECSS-Q-ST-70-60_1390132",1,"Created","Marking on coverlay for flexible PCB and sculptured flex PCB shall not lift after tape test in conformance with clause 9.4.5."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","6.9a","Requirement","ECSS-Q-ST-70-60_1390139",1,"Created","All operators and inspectors shall be trained for their task and for the understanding of the applicable quality assurance requirements."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","6.10.2l","Permission","ECSS-Q-ST-70-60_1390752",1,"Created","In case a PCB exceeds warp or twist requirements from clauses 9.3.3.2 or 9.3.3.3, it may be flattened using pressure and elevated temperature in case the initial warp and twist does not exceed 1,6 %.","NOTE \tApproval for this process is specified in requirement 6.10.2b because the PCB can increase its non-flatness after storage, bake-out or assembly processes. These processes are not under control of the PCB manufacturer. The main cause for non-flatness is asymmetric build-up or shape, which is driven by the design from the procurement authority.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","6.10.2n","Requirement","ECSS-Q-ST-70-60_1390147",1,"Created","Other repairs that are not specified in this clause shall not be performed.","NOTE \tExamples of such repairs are:\n·\trepair of burrs;\n·\tbrushing of overhang of Ni/Au or Au;\n·\trepair of PTH with too small diameter due to excessive SnPb thickness.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","6.11i","Requirement","ECSS-Q-ST-70-60_1390156",1,"Created","If desiccant is used, precautions shall be taken to prevent damage due to contact between desiccant and PCB.","NOTE \tDamage can include mechanical damage due to pressure or friction. Damage can include chemical damage to the surface finish.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","6.12d","Permission","ECSS-Q-ST-70-60_1390756",1,"Created","Spare coupons may be stored in an uncontrolled environment.","NOTE \tThis is acceptable because it is considered worse-case.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","6.14e","Requirement","ECSS-Q-ST-70-60_1390171",1,"Created","The procurement authority shall list each PCB technology, in conformance with the requirement 5.11b, in the DML as a separate item."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","6.14m","Requirement","ECSS-Q-ST-70-60_1390177",1,"Created","The procurement authority shall provide the PCB approval sheet part 1 and part 2 to its customer for review and approval during MPCBs."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","7.2c","Requirement","ECSS-Q-ST-70-60_1390187",1,"Created","For qualification renewal of a technology the following test shall be performed on PCB and coupon:\n1.\tGroup 2: peel strength and solderability;\n2.\tGroup 3: all."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","7.4b","Requirement","ECSS-Q-ST-70-60_1390196",1,"Created","The PCB manufacturer of the new technology shall already hold a qualification in conformance with clause 5."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","7.6f","Requirement","ECSS-Q-ST-70-60_1390204",1,"Created","In case delta qualification is initiated in the context of a space project, the procurement authority shall handle it through an RFA, in conformance with clause 7.7."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","7.7.2b","Requirement","ECSS-Q-ST-70-60_1390206",1,"Created","Project qualification shall provide approval of a PCB technology for the batch used on that project only. "]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","7.7.2k","Requirement","ECSS-Q-ST-70-60_1390212",1,"Created","DR shall be performed in conformance with 6.2.5a with support of the PCB manufacturer to review the manufacturability and reliability of the design and to review previous heritage and test campaigns performed."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","8.1d","Requirement","ECSS-Q-ST-70-60_1390218",1,"Created","The PCB manufacturer shall perform referee testing on a spare PCB in case this is specified in Table 10-26 and 10.6.3c.","NOTE \tReferee testing is specified in Ref. b and c from Table 10-26.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","8.2.2i","Requirement","ECSS-Q-ST-70-60_1390231",1,"Created","The term “coupon Bn” shall indicate all coupons B1, B2 … Bn for all plating sequences."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","8.2.3e","Recommendation","ECSS-Q-ST-70-60_1390769",1,"Created","In case more than one PCB is placed in the panel, a coupon for evaluation of plating should be placed in the middle of the panel.","NOTE \tA coupon for plating can be an IST coupon, A/B coupon or a spare PCB. An example of coupon placement in the centre of the panel is shown in Figure 8-3.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","8.2.4e","Requirement","ECSS-Q-ST-70-60_1390248",1,"Created","Microsectioning on coupon A/B shall be performed on at least 4 holes per drilling sequence and on coupon Bn on at least 3 holes per drilling sequence.","NOTE \tSee Figure 8-2 for an example of drilling sequence of holes.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","8.2.5b","Permission","ECSS-Q-ST-70-60_1390773",1,"Created","The IST coupon may be send later than the other coupons, due to its logistics of test and shipment."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","8.4d","Requirement","ECSS-Q-ST-70-60_1390262",1,"Created","In case of nonconformances during incoming inspection an NCR shall be issued by the procurement authority to the PCB manufacturer."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","8.4f","Requirement","ECSS-Q-ST-70-60_1390263",1,"Created","The procurement authority shall complete the incoming inspection within 3 months after availability of the PCBs."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.2.3c","Requirement","ECSS-Q-ST-70-60_1390275",1,"Created","Plated copper elongation shall be ≥ 18 %."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.2.4c","Requirement","ECSS-Q-ST-70-60_1390278",1,"Created","After closing the generator, it shall be purged with nitrogen at a flow rate between 250 ml/minute and 750 ml/minute."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.3.1a","Requirement","ECSS-Q-ST-70-60_1390284",1,"Created","Visual inspection shall be performed using 10x to 40x magnification.","NOTE \tExamples of equipment used for visual inspection are: binoculars, loups, single scope.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.3.3.1i","Requirement","ECSS-Q-ST-70-60_1390296",1,"Created","In case overhang or undercut causes the top of the conductor to protrude from the foot, conductor width and spacing shall be measured at the widest point of the conductor."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.3.3.2h","Requirement","ECSS-Q-ST-70-60_1390304",1,"Created","The maximum warp shall be £ 1,5 %."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.3.3.3f","Requirement","ECSS-Q-ST-70-60_1390311",1,"Created","The twist shall be expressed in percentage terms."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.3.7.2b","Requirement","ECSS-Q-ST-70-60_1390322",1,"Created","The test voltage shall be ≥ 250 V."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.3.7.2d","Requirement","ECSS-Q-ST-70-60_1390324",1,"Created","The sustain time shall be ≥ 5 ms.","NOTE \tIt is common that the sustain time is more than 5 ms to allow the voltage ramp up, especially in case large ground layers are present.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.3.7.2m","Requirement","ECSS-Q-ST-70-60_1390331",1,"Created","In case the test fails below 0,1 GΩ, re-test shall not be performed.","NOTE \tFailure above 0,1 GΩ can occur due to insufficient surface cleaning or insufficient dehumidification. High temperature during baking can affect the quality of the surface finish which is verified by the PCB manufacturer.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.3.8.2g","Requirement","ECSS-Q-ST-70-60_1390339",1,"Created","Test point assignment shall be set as follows: \n1.\tOn the top and bottom layer of a drilled pad that is not connected with any track.\n2.\tOn the top layer of a drilled pad that is not connected with any track on the top layer and connected with only one track on the bottom layer.\n3.\tOn the bottom layer of a drilled pad that is not connected with any track on the bottom layer and connected with only one track on the opposite layer.\n4.\tOn the top and bottom layer of a drilled pad that is not connected with any track on the top layer or the opposite layer, but is connected to one inner layer.\n5.\tOn the bottom layer of a drilled pad that is not connected with any track on the bottom layer and connected with more than one track on the opposite layer.\n6.\tOn the top layer of a drilled pad that is not connected with any track on the top layer and connected with more than one track on the opposite layer.\n7.\tOn the top and bottom layer of a drilled pad that is not connected with any track on the top layer or the opposite layer, but is connected to two or more inner layers.","NOTE \tThese 7 conditions for test point assignment are illustrated in Figure 9-6.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.4.2g","Requirement","ECSS-Q-ST-70-60_1390348",1,"Created","Machine inertia shall have no effect on the measurement."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.4.3d","Requirement","ECSS-Q-ST-70-60_1390355",1,"Created","Flexural fatigue test shall be performed for a rigid-flex PCB on the individual flexible laminate.","NOTE \tFlexural fatigue test assesses the bare laminate properties. The individual flexible laminate can be non-representative of a rigid-flex PCB in case multiple flexible layers are used or laminated together. In this case, the bending test assesses the representative construction.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.4.4c","Requirement","ECSS-Q-ST-70-60_1390365",1,"Created","The test shall be carried out in conformance with requirements 9.4.3f and 9.4.3g, 9.4.3h, except for the following:\n1.\tNumber of cycles is 25;\n2.\tThe radius of the mandrel over which the flexible section is bend equals 12x the total thickness of the flexible section.","NOTE \tThe build-up of flex laminate with lowest thickness includes 25 μm flex laminate, with 35 μm copper cladding on both sides, with 25 μm coverlay on both sides, with approximately 10 μm to 20 μm adhesive between coverlay and flex laminate. This results in approximately 165 μm thickness. The minimum bend radius of 12x is in conformance with clause 8.6.2a of ECSS-Q-ST-70-12. The minimum mandrel radius therefore equals 1,98 mm, corresponding to a diameter of 3,96 mm.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.4.5f","Requirement","ECSS-Q-ST-70-60_1390374",1,"Created","The surface finish shall not peel from the test surface or stick to the tape.","NOTE \tCoating adhesion test can be performed on coupon P from IPC-2221B.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.4.8a","Recommendation","ECSS-Q-ST-70-60_1390794",1,"Created","Thermal analysis should be performed on a sample without copper."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.4.8c","Requirement","ECSS-Q-ST-70-60_1390381",1,"Created","Time to delamination at 288˚C, T288, shall be measured in conformance with test method 2.4.24.1 of IPC-TM-650 using TMA."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.4.11.3e","Requirement","ECSS-Q-ST-70-60_1390392",1,"Created","The solder bath temperature shall be set at 235°C."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.4.11.4c","Requirement","ECSS-Q-ST-70-60_1390394",1,"Created","Flux shall be applied to the test area and drained on absorbent, clean material prior to solderability test."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.5.2.1a","Recommendation","ECSS-Q-ST-70-60_1390802",1,"Created","The methods for microsectioning from test method 2.1.1f from IPC-TM-650 should be used."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.5.2.3g","Requirement","ECSS-Q-ST-70-60_1390408",1,"Created","In case fluorescent dye is not used for potting of rigid-to-flex interface, the following shall be demonstrated:\n1.\tthe efficiency to detect possible delamination without the contrast from the fluorescent dye;\n2.\tany possible delamination is not caused by the microsectioning."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.5.3c","Requirement","ECSS-Q-ST-70-60_1390417",1,"Created","The solder bath float shall be performed to one side of the sample by floating it for 10 s in a solder bath maintained at 288 °C."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.5.4.1b","Requirement","ECSS-Q-ST-70-60_1390424",1,"Created","The coupon shall include representative PTH in accordance with ECSS-Q-ST-70-12 requirements 15.2d.5(a) and 15.2d.8.","NOTE \tThese clauses specify to include PTH with hole sizes of maximum or most frequently used dimensions.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.5.4.3h","Recommendation","ECSS-Q-ST-70-60_1390810",1,"Created","Sample with high thermal mass should be submitted to pre-heating during the rework simulation test.","NOTE \tThis is done to limit the soldering time to maximum 5 seconds.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.5.5.2.1a","Requirement","ECSS-Q-ST-70-60_1390438",1,"Created","The PCB manufacturer shall have a work instruction for in-process IST control."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.5.5.2.2b","Requirement","ECSS-Q-ST-70-60_1390443",1,"Created","At least one coupon shall be included per panel and submitted to IST testing."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.5.5.4.1a","Recommendation","ECSS-Q-ST-70-60_1390815",1,"Created","Electrical pre-screening and possible down selection should be performed in conformance with instruction PWB-150316 in case multiple IST coupons are available.","NOTE \tThe referenced work instruction is available on the website of the test equipment supplier.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.5.5.4.1g","Permission","ECSS-Q-ST-70-60_1390818",1,"Created","In case re-absorption of humidity is mitigated in conformance with point 9.5.5.4.1d, IST coupons need not to be submitted to IST testing within 12 hours after baking."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.5.5.4.2m","Requirement","ECSS-Q-ST-70-60_1390462",1,"Created","For testing microvias, the power cable shall be connected directly to the microvias sense circuit. ","NOTE \tThe sense cable is connected to a power or sense circuit that has previously demonstrated to be robust, e.g. the superheat circuit. The measured sense data is not considered important and any failure or variation measured is disregarded.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.5.5.5.2c","Recommendation","ECSS-Q-ST-70-60_1390824",1,"Created","Specific IST coupons for interconnect verification should include all drill sizes for holes that interconnect on RF laminate.","NOTE \tThis does not include non-functional pads.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.6.2d","Requirement","ECSS-Q-ST-70-60_1390471",1,"Created","Microsectioning and evaluation in conformance with 9.6.2c.10 and 9.6.2c.11 shall be performed on the following:\n1.\tAt least 4 PTH from the PCB that have been subjected to rework simulation;\n2.\tAll technology features under qualification.","NOTE \tTechnology features under qualification can include all via types, the build-up and materials.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.6.3f","Permission","ECSS-Q-ST-70-60_1390833",1,"Created","In case a stable reading is obtained earlier, the insulation resistance (R) may be measured before 1 minute. "]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.6.3l","Requirement","ECSS-Q-ST-70-60_1390482",1,"Created","The interlayer insulation resistance after thermal stress shall be ≥ 10 GΩ.","NOTE \tTo measure such high resistance it is good practice to use an equipment with a measurement range up to 1000 GΩ.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.7.2.1a","Requirement","ECSS-Q-ST-70-60_1390487",1,"Created","A justification shall be provided in case any part of this test method is tailored.","NOTE \tThe specified method can be superseded by future test campaigns to implement lessons learned or to represent applications.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.7.2.2i","Requirement","ECSS-Q-ST-70-60_1390496",1,"Created","In total four samples shall be tested from at least two different panels."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.7.3.2a","Requirement","ECSS-Q-ST-70-60_1390506",1,"Created","The lay-out of the test vehicle for CAF test shall meet all the following conditions:\n1.\tIt includes the pattern configuration A as specified in Table 9-2 for aligned vias using ≥20x20 vias configured in X and Y-direction;\n2.\tIt includes the pattern configuration B as specified in Table 9-3 for staggered vias using ≥10x20 vias;\n3.\tIt includes the pattern configuration C as specified in Table 9-4 for vias in plane using ≥20x20 vias with all non-functional pads removed;\n4.\tElectrical registration coupons in X and Y-direction for verification of registration.","NOTE\t1\tFor requirement 9.7.3.2a.1 such comb pattern of aligned vias result in 20 vias x 19 spacing = 380 CAF opportunities within a layer. \nNOTE\t2\tFor requirement 9.7.3.2a.2 such comb pattern of staggered vias result in 10 vias x 19 spacings x 2 manhattan paths = 380 CAF opportunities within a layer.\nNOTE\t3\tFor requirement 9.7.3.2a.3 the C pattern of vias-in-plane is used to represent via-to-track. The non-functional pad is removed on all layers, otherwise the failure mechanism can be as for the configuration conductor-to-conductor.\nNOTE\t4\tFor requirement 9.7.3.2a.3 C pattern is designed with bias voltage connected to the vias. Therefore the vias are positive, i.e. the anode. CAF grows from the anode, hence CAF can grow from the via, which is the purpose of this test pattern design.\nNOTE\t5\tFor requirement 9.7.3.2a.1 test pattern A is deemed to be most susceptible to CAF. \nNOTE\t6\tIt is good practice to implement an incremental spacing to rows of vias to avoid that the via pattern always aligns with the glass weave of the laminate.\nNOTE\t7\tLaser drilled microvias give less propensity for CAF compared to mechanical vias, because:\n·\tsmaller diameter and smaller contact area to glass\n·\tless desmear\n·\tless vibrations during hole wall formation\n\tBased on this, testing a mechanical via is considered representative or slightly worse-case of a microvia. For microvia, the critical spacing is to a conductor, not to an adjacent microvia. This is therefore covered by test pattern C. By design, microvias can be spaced further apart than mechanical vias because of small feature size and possibility to stagger.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.7.3.3b","Requirement","ECSS-Q-ST-70-60_1390516",1,"Created","The CAF test method shall be as follows:\n1.\tAmbient phase using the parameters: 24h, 25°C, 50% RH, 0V;\n2.\tPreconditioning phase using the parameters: 96h, 85°C, 75% RH, 0V;\n3.\tCAF phase using the parameters: 500h, 85°C, 75% RH, 50V;\n4.\tAmbient phase using the parameters: 24h, 25°C, 50% RH, 0V.","NOTE\t1\tCAF is relevant for HDI which can use voltages up to 30 V in conformance with ECSS-Q-ST-70-12. The guidelines in IPC-9691B recommend a margin of x2. For practical considerations of the test equipment this is limited to 50 V.\nNOTE\t2\tIt is good practice to control the environmental chamber such that no condensation or rain occurs. This can be achieved during the transition from the ambient phase to the pre-conditioning phase by increasing temperature at a controlled rate, implementing a dwell time, after which the humidity can be increased at a controlled rate. This can be achieved during the transition from the CAF phase to the ambient phase by decreasing the humidity at a controlled rate, implementing a dwell time, after which the temperature can be decreased at a controlled rate.\nNOTE\t3\tIt is good practice to clean the environmental chamber and the electrical test rack and to perform a dry run at a temperature and humidity level higher than the set points during the CAF test.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.8.2d","Requirement","ECSS-Q-ST-70-60_1390524",1,"Created","Microsectioning and evaluation in conformance with 9.8.2c.5 and 9.8.2c.6 shall be performed on the following:\n1.\tAt least 4 PTH of the PCB that have been subjected to rework simulation;\n2.\tAll technology features under qualification."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.8.3e","Requirement","ECSS-Q-ST-70-60_1390529",1,"Created","The sample shall be cooled at ambient temperature for at least 10 minutes."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.8.4h","Requirement","ECSS-Q-ST-70-60_1390537",1,"Created","The maximum temperature shall be between +130 °C and +145 °C.","NOTE \tThe Tg of laminates is typically higher than this temperature.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","9.8.4j","Requirement","ECSS-Q-ST-70-60_1390539",1,"Created","The number of cycles shall be 200."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","10.2p","Requirement","ECSS-Q-ST-70-60_1390555",1,"Created","For the technological feature dimensional verification of the rigid-flex interface the acceptance criteria, the inspection samples and the measurement method shall be in conformance with Table 10-16."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","10.3c","Requirement","ECSS-Q-ST-70-60_1390574",1,"Created","For the technological feature blind via planarity, the acceptance criteria, the inspection samples and the measurement method shall be in conformance with Table 10-19."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","10.3i","Requirement","ECSS-Q-ST-70-60_1390580",1,"Created","For the technological feature pad lift, the acceptance criteria, the inspection samples and the measurement method shall be in conformance with Table 10-25."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","10.4a","Requirement","ECSS-Q-ST-70-60_1390614",1,"Created","For the technological feature conductor width, the acceptance criteria, the inspection samples and the measurement method shall be in conformance with Table 10-38."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","10.4j","Requirement","ECSS-Q-ST-70-60_1390623",1,"Created","For the technological feature marking the acceptance criteria, the inspection samples and the measurement method shall be in conformance with Table 10-47."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","10.5c","Requirement","ECSS-Q-ST-70-60_1390644",1,"Created","For the technological feature tin-lead infiltration for sculptured flex PCB, the acceptance criteria, the inspection samples and the measurement method shall be in conformance with Table 10-54."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","10.5o","Requirement","ECSS-Q-ST-70-60_1390656",1,"Created","For the technological feature microsection for sculptured flex PCB, the acceptance criteria, the inspection samples and the measurement method shall be in conformance with Table 10-66."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","10.6.2b","Requirement","ECSS-Q-ST-70-60_1390676",1,"Created","Cracks in the laminate underneath SMT pads without via-in-pad shall be evaluated as dielectric cracks, in conformance with the Table 10-26.","NOTE \tSMT pads without via-in-pad are not included on coupons.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","10.6.2g","Requirement","ECSS-Q-ST-70-60_1390680",1,"Created","In case cracks associated with pad lift are observed on the coupon for procurement, conformance to Table 10-25 shall be evaluated after group 6 test for representative technology and recorded in the PID.","NOTE \tThis provides an evaluation that the cracks associated with pad lift do not propagate until the hole wall after group 6, as done for qualification. Propagation of cracks until the hole wall increases the risk of further propagation along the hole wall and potential rupture of innerlayer connections.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","10.6.3i","Permission","ECSS-Q-ST-70-60_1390847",1,"Created","The customer may specify a requirement for maximum copper thickness in the PCB definition dossier.","NOTE \tECSS-Q-ST-70-60 and ECSS-Q-ST-70-12 do not specify a maximum copper thickness for plated layers. This could be important for HDI layers, thermal performance of PCBs or for RF applications. Copper thickness on plated layers (internal/external) can be influenced by pattern design and value above maximum are acceptable in case all other requirements like dielectric thickness, undercut, conductor width/space are achieved.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","B.2.1.2a","Requirement","ECSS-Q-ST-70-60_1390696",1,"Created","The declaration of conformance shall include the following:\n1.\tDeclaration of conformance to ECSS-Q-ST-70-60;\n2.\tDeclaration of conformance to the PCB definition dossier;\n3.\tTraceability reference to the PCB definition dossier from procurement authority including revision and issue number;\n4.\tMRR reference;\n5.\tIn case of partial or noncompliance to B.2.1.2a1 or B.2.1.2a2 reference to waiver request;\n6.\tPurchase order number from procurement authority;\n7.\tTraceability reference from PCB manufacturer;\n8.\tDate code, as per the following format: YYWW;\n9.\tQuantity of delivered PCBs in the batch;\n10.\tSerial numbers of delivered PCBs in the batch;\n11.\tSignature from PCB manufacturer.","NOTE 1\tNote to item 3: This traceability reference can be named ‘part number’.\nNOTE 2:\tNote to item 7: This traceability reference can be named ‘batch code’.\nNOTE 3\tNote to item 8: YYWW indicates a two digit reference to year followed by a two digit reference to week number.\n"]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","B.2.1.5d","Requirement","ECSS-Q-ST-70-60_1390705",1,"Created","The lab report for microsection for qualitative aspects shall include the following representative pictures of microsections covering the batch, except in case this is specifically waived by the customer in the PCB definition dossier:\n1.\tOverview of PTH after SB in dark field showing laminate integrity, build-up;\n2.\t500x magnification after SB in bright field showing interconnect and absence of ICD;\n3.\t500x magnification as received in bright field showing SnPb on corner;\n4.\tOverview of rigid-to-flex interface after SB in dark field showing laminate integrity and absence of delamination."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","C.2.1a","Requirement","ECSS-Q-ST-70-60_1390710",1,"Created","The qualification test report shall include:\n1.\tDescription and history of the samples.\n2.\tReference to the approved qualification test plan.\n3.\tAll results from the qualification tests in conformance with requirements from clause 7.2.\n4.\tPhotographic documentation of results obtained from microsectioning."]
["ECSS-Q-ST-70-60C Corr.1","ECSS - Superseded v1.0","G.2.1c","Requirement","ECSS-Q-ST-70-60_1390722",1,"Created","The PCB approval sheet part 2 shall provide confirmation for each aspect in conformance with requirements from G.2.1b that it is within the qualified domain from the PID of the PCB manufacturer."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","5.2h","Requirement","ECSS-Q-ST-70-12_1200005",1,"Created","The PCB manufacturer shall provide the PCB manufacturing dossier in conformance with DRD in the Annex B."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","5.2j","Requirement","ECSS-Q-ST-70-12_1200007",1,"Created","During the MRR, supplier and PCB manufacturer shall approve the PCB manufacturing dossier, the PCB definition dossier and all Review Items.\nNOTE \tThe approvals are recorded in the MRR checklist."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","7.1.2a","Recommendation","ECSS-Q-ST-70-12_1200378",1,"Created","The thickness of the copper cladding on both sides of the laminate should be equal except on outer layers of the PCB or half-stack.\nNOTE \tEqual copper thickness is needed when laminate is etched in same process steps, as is the case for internal layers. The exception on outer layers is made because each side is etched in different process steps and because thin copper on external layers decreases the total thickness after plating."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","7.1.2d","Recommendation","ECSS-Q-ST-70-12_1200379",1,"Created","Copper distribution within a layer should be homogeneous.\nNOTE \tThis is done to ensure even pressure distribution during lamination, which can cause filling voids, cracks or glass compression."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","7.1.3c","Requirement","ECSS-Q-ST-70-12_1200028",1,"Created","In case a single sheet of glass is used in a glass-reinforced laminate it shall be recorded as Review Item in the PCB definition dossier.\nNOTE \tTwo sheets of glass reinforcement are specified to mitigate the risk of reduced insulation caused by contamination. This is also specified for laminates for class 3/A in accordance with IPC-6012 Appendix A. In case a single reinforcement in laminate is used, it is recommended to implement other means to mitigate the risk of contamination in laminate. IPC-4121 provides various properties, such as resin-to-glass ratio, for core laminate constructions."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","7.1.3k","Requirement","ECSS-Q-ST-70-12_1200034",1,"Created","In case other laminate classes are used, the PCB manufacturer shall calculate minimum projected peak-to-peak insulation distance in conformance with requirement 7.1.3i.\nNOTE \tAn example of this is shown in Table 7-2 for class C laminate and commonly used copper profiles. "]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","7.3.5a","Requirement","ECSS-Q-ST-70-12_1200041",1,"Created","Except the case specified in the requirement 11.5.6a, the aspect ratio of vias on a rigid and rigid-flex PCB shall be ≤ 7.\nNOTE \t1\tThere is no additional requirement for the minimum diameter of plated via in case the diameter conforms to the aspect ratio of ≤ 7.\nNOTE \t2\tRequirement 11.5.6a specifies aspect ratio for AAD with 1 mm pitch on HDI PCBs."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","7.4.3c","Requirement","ECSS-Q-ST-70-12_1200047",1,"Created","In case the as-designed track width and spacing for external layers of rigid PCB is less than the values specified in the requirement 7.4.3b, the following conditions shall be met:\n1.\tthe manufacturing tolerances as specified in the PID are smaller than as specified in Table 7-3,\n2.\tthe as-manufactured dimensions specified in Table 7-4 and Table 13-7 are met, and\n3.\tit is recorded as a Review Item in the PCB definition dossier."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","7.4.5c","Requirement","ECSS-Q-ST-70-12_1200057",1,"Created","Fine pitch shall be limited to the functionality of impedance control or signal routing to AAD."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","7.4.6b","Requirement","ECSS-Q-ST-70-12_1200063",1,"Created","Tracks shall exit from AAD footprint before changing direction to keep the insulation distance to the pad in compliance with normal pitch as specified in Table 7-5.\nNOTE \tSee example of nonconformance indicated by green arrow in Figure 7-1."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","7.5.1b","Permission","ECSS-Q-ST-70-12_1200399",1,"Created","Non-functional pads may be removed:\n1.\twhen the presence of the pads degrade the electrical performance, they can be removed by the supplier, or \n2.\tto prevent high pressure area during lamination that cause resin starvation in the prepreg, the pads can be removed by the PCB manufacturer.\nNOTE \tRemoval of non-functional pads is approved by supplier and PCB manufacturer during MRR in conformance with the requirement 7.5.1c.6"]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","7.5.2g","Permission","ECSS-Q-ST-70-12_1200404",1,"Created","For via holes and component holes on component side the diameter of external pads may be the diameter of as-manufactured hole plus ≥ 0,5 mm in case:\n1.\tthe as-manufactured annular ring as specified in the requirement 7.5.2b, and.\n2.\tit is recorded as a Review Item in the PCB definition dossier."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","7.6b","Recommendation","ECSS-Q-ST-70-12_1200409",1,"Created","The grid should be offset between layers.\nNOTE \tThese additional openings act as venting holes for desorption of humidity out of the PCB. For example, a grid can be 0,4 mm lines at a pitch of 0,6 mm and at 45° angle. The thermal and electrical resistance across such hatch plane is a factor of 2,5 larger than across a solid plane, assuming pattern as specified above. This can affect both power distribution and signal integrity, in particular for RF or digital PCB."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","8.3.1a","Requirement","ECSS-Q-ST-70-12_1200079",1,"Created","The maximum number of copper layers on a flex PCB shall be 2."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","8.3.2d","Requirement","ECSS-Q-ST-70-12_1200084",1,"Created","The thickness of the polyimide cover layer shall be 25 µm or 50 µm."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","8.4e","Recommendation","ECSS-Q-ST-70-12_1200418",1,"Created","Tracks should be evenly distributed over the entire width of the PCB."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","8.4n","Requirement","ECSS-Q-ST-70-12_1200097",1,"Created","Track width and spacing shall be in conformance with the values specified in the Table 13-4."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","8.5.2a","Requirement","ECSS-Q-ST-70-12_1200104",1,"Created","PTH shall be located only in termination zones, not in the bending zone, as specified in Figure 8-2."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","8.5.3c","Recommendation","ECSS-Q-ST-70-12_1200425",1,"Created","The track width should be at least half the diameter of the pad except the case specified in the requirement 8.5.3d. \nNOTE \tIn the Figure 8-3 IC is track width and D1, D2 are diameters of the pad."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","8.7.4a","Permission","ECSS-Q-ST-70-12_1200427",1,"Created","The connection fingers may be bend in a staggered pattern to fit the footprint of the connecting PCB\nNOTE \tAn example of staggered bend connection fingers is shown in Figure 8-7."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","8.7.5f","Requirement","ECSS-Q-ST-70-12_1200124",1,"Created","There shall be no adhesive inside the hole.\nNOTE \tAdhesive can be squeezed from underneath the cover layer and misregistration of the cover layer on component side can risk to have adhesive inside the hole. "]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","9.2c","Requirement","ECSS-Q-ST-70-12_1200131",1,"Created","No termination zone shall be defined for the flex section of a rigid-flex PCB."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","9.4c","Requirement","ECSS-Q-ST-70-12_1200141",1,"Created","The cover layer shall extend into the rigid section of the PCB by ≥ 1,5 mm."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","9.6c","Requirement","ECSS-Q-ST-70-12_1200148",1,"Created","Non-functional pads on flex laminate shall be in conformance with  requirement 7.5.1c.2."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","10.3.2b","Requirement","ECSS-Q-ST-70-12_1200152",1,"Created","The copper or aluminium core shall have a protective layer to prevent corrosion.\nNOTE \tThe type of protective layer is specified in the PCB definition dossier. Examples of protective layers to prevent corrosion are anodization, alodine, nickel plating, gold plating. These corrosion protections can have specific drawbacks for further PCB processing."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","10.3.3b","Requirement","ECSS-Q-ST-70-12_1200158",1,"Created","Distance between 2 clearances shall be ≥ 1,5 mm along straight edges.\nNOTE \tDistance along straight edges is indicated as “Iz1” in Figure 10-1."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","10.4.3c","Requirement","ECSS-Q-ST-70-12_1200172",1,"Created","The number of heat sink layers with CIC shall be ≤ 2."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","10.4.3f","Requirement","ECSS-Q-ST-70-12_1200174",1,"Created","The thickness of molybdenum inserts shall be 0,5 mm."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","10.4.4d","Requirement","ECSS-Q-ST-70-12_1200180",1,"Created","The distance between a plated hole and the heat sink shall be in conformance with the requirement 13.8.2k and values specified in the Table 13-3."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","11.4.1f","Recommendation","ECSS-Q-ST-70-12_1200443",1,"Created","Microvia layers should be designed with copper foil and prepreg."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","11.4.2e","Requirement","ECSS-Q-ST-70-12_1200198",1,"Created","The plated copper thickness on the corner of the microvia shall be ≥25 µm."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","11.4.4a","Requirement","ECSS-Q-ST-70-12_1200202",1,"Created","The annular ring as-manufactured for microvias for internal pads shall be ≥ 10 µm."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","11.5.4a","Permission","ECSS-Q-ST-70-12_1200450",1,"Created","The spacing and width of pads and tracks for impedance control and routing to AAD on internal layers may be reduced to requirements for fine pitch in conformance with the values from Table 7-5."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","12.2c","Permission","ECSS-Q-ST-70-12_1200453",1,"Created","Copper type “electrodeposited - ED” or “rolled and annealed - RA” may be used for copper cladding and copper foils."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","12.3c","Requirement","ECSS-Q-ST-70-12_1200218",1,"Created","Embedded film resistors shall be of type NiP or NiCr.\nNOTE \tType NiP is available from OhmegaPly. Type NiCr is available from Ticer."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","12.4b","Permission","ECSS-Q-ST-70-12_1200459",1,"Created","The thickness of RF PCB as-designed may be > 3 mm in case the following conditions are met:\n1.\tthe thickness as-designed is ≤ 5,5 mm,\n2.\tthe materials used are not based on PTFE, and\n3.\tit is recorded as a Review Item in the PCB definition dossier.\nNOTE \tHigh PCB thickness involve a more difficult drilling process, lamination and handling in automated equipment. It is important that the PCB manufacturer confirms the good processability of the materials."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","12.6.1a","Requirement","ECSS-Q-ST-70-12_1200228",1,"Created","Dimensions of the via hole pads shall be in conformance with the requirements from clause 7.5.2."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","13.4b","Requirement","ECSS-Q-ST-70-12_1200236",1,"Created","DWV between tracks shall be 1000 Vrms/mm for intralayer and interlayer."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","13.5a","Requirement","ECSS-Q-ST-70-12_1200239",1,"Created","All conductive parts and patterns shall not be left isolated, in conformance with clauses 6.3.1, 9.2.1 and 9.2.2 of ECSS-E-ST-20-06.\nNOTE \tECSS-E-ST-20-06 defines: \n·\tthe area of a floating surface is ≤ 1 cm2 \n·\tthe capacitance of the floating surface is ≤10pF. "]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","13.6.4.2b","Requirement","ECSS-Q-ST-70-12_1200250",1,"Created","For PCBs with a thickness between 1,5 mm and 1,8 mm, the temperature rise of tracks shall be increased by 20%.\nNOTE \tThe mathematical fitting of Figure 5-14 of chapter 5.2.2. of IPC-2152 presented as a guideline in Annex D is valid for PCBs of 1,8 mm. The justification for 20% margin for thinner PCBs is given in chapter A.4.2 of IPC-2152."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","13.7.2a","Requirement","ECSS-Q-ST-70-12_1200251",1,"Created","Criticality of tracks shall be as specified in requirement 13.9.2a."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","13.8.2d","Requirement","ECSS-Q-ST-70-12_1200257",1,"Created","The insulation distance as function of voltage of the as-manufactured PCB shall be in compliance with values specified in Table 13-3 and Table 13-4.\nNOTE \t1\tThe insulation distances also depends on manufacturing capability and tolerances as specified in clause 13.8.1 and specified in Table 7-4 and Table 7-5.\nNOTE \t2\tThe Table 13-3 and Table 13-4 cover any elevation. Withstanding voltage between two tracks in air at 87% relative humidity is 1600 V/mm. It is considered that breakdown or arcing cannot occur below this field strength as indicated in the paper by D. P Cullen and G O’Brien (see bibliography)."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","13.8.4e","Requirement","ECSS-Q-ST-70-12_1200272",1,"Created","For the footprint of components and connectors that cannot be conformally coated, the insulation distance shall be in compliance with the requirements specified in Table 13-3 for X,Y external without conformal coating."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","13.9.2a","Requirement","ECSS-Q-ST-70-12_1200275",1,"Created","Nets shall be identified as “critical” when they include the following functionalities:\n1.\tnon-protected sections of a main bus power distribution system up to and including the first protection device,\n2.\tnets that are a single point failure SPF for the system,\n3.\tnets on which a loss of insulation can result in electrical failure propagation to a critical net,\n4.\tcross-strapped functions and associated common links from source to load.\nNOTE \t1\tDetails for requirement 13.9.2a.1 are specified in requirement 5.8.1.c. of the ECSS-E-ST-20.\nNOTE \t2\tExample for the requirement 13.9.2a.3 is primary and redundant nets on a single PCB.\nNOTE \t3\tExamples of cross-strapped functions from the requirement 13.9.2a.4 are hot redundant power links, majority voters \"reliable\" links, specific telecommand or telemetry matrices."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","13.9.3.2c","Requirement","ECSS-Q-ST-70-12_1200285",1,"Created","The insulation distance from a conductor to the PCB edge in conformance with the requirement 13.8.2h shall be doubled in case the PCB edge faces an external conductive element within a distance of less than 1 mm."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","13.11.2d","Recommendation","ECSS-Q-ST-70-12_1200483",1,"Created","The controlled impedance tracks should be designed with end-to-end configuration."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","13.11.4a","Requirement","ECSS-Q-ST-70-12_1200297",1,"Created","Series termination shall be used for end-to-end configuration."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","13.12.2a","Recommendation","ECSS-Q-ST-70-12_1200488",1,"Created","The layout of a PCB should be partitioned by using zone management where different logical blocks are physically separated from each other.\nNOTE \tDifferent blocks to be separated in a board layout can be low speed (or static) links, analog links, power lines, high speed serial digital links, RF signals. "]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","13.12.3.2a","Requirement","ECSS-Q-ST-70-12_1200305",1,"Created","Signals that require a monotonic waveform through the voltage threshold of the receivers shall be identified as “critical”.\nNOTE \tExamples of critical signals are: clocks signals, write signals."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","13.13.2.1a","Requirement","ECSS-Q-ST-70-12_1200309",1,"Created","Signals that have low speed, low bandwidth or low resolution shall be identified as “non-critical”. \nNOTE \tThe signal-to-noise ratio, pickup and crosstalk noise (or any combination) are non-critical for such signals. These signals do not affect the performance or the functionality of the equipment. "]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","13.13.3a","Requirement","ECSS-Q-ST-70-12_1200313",1,"Created","Ground planes shall be used for critical and highly critical analog circuitries specified in the requirements 13.13.2.2a and13.13.2.3a."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","13.14d","Requirement","ECSS-Q-ST-70-12_1200315",1,"Created","In case planes of analog and digital circuitries are combined, power supply decoupling shall be implemented."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","14.3.1a","Requirement","ECSS-Q-ST-70-12_1200320",1,"Created","The distance of the surface pattern to the adjacent surroundings shall be in conformance with values specified in Table 14-1.\nNOTE \tAn illustration is given in Figure 14-1."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","14.3.3i","Requirement","ECSS-Q-ST-70-12_1200330",1,"Created","The extended pad shall be included in the assembly qualification as the extra size affects the volume of solder in the joint."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","14.3.4d","Permission","ECSS-Q-ST-70-12_1200514",1,"Created","The SMT pad of an AAD may be asymmetric.\nNOTE \tExamples of asymmetric SMT pad are key hole, solder verification snip. The purpose of this is to verify quality of the solder joint. "]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","14.5.6a","Requirement","ECSS-Q-ST-70-12_1200350",1,"Created","The pad design for components of type LCC shall be in conformance with the as-manufactured values specified in the Table 14-9, except for the case specified in 14.5.2c.\nNOTE \t1\tAn illustration is given in Figure 14-11.\nNOTE \t2\tLCC means leadless chip carrier."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","15.2c","Recommendation","ECSS-Q-ST-70-12_1200523",1,"Created","Test coupon location in the manufacturing panel should be representative of the worst case.\nNOTE \tWorst-case location for registration is typically on the corners of the panel. However, worst-case for plating is typically in the centre of the panel. In this case, it is important the PCB manufacturer compares the plating thickness in the coupon with the rest of the panel. This is typically verified during qualification."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","15.2i","Requirement","ECSS-Q-ST-70-12_1200360",1,"Created","Each coupon shall have a serial number that ensures traceability to the panel."]
["ECSS-Q-ST-70-12C","ECSS - Superseded v1.0","A.2.1<5>a","Requirement","ECSS-Q-ST-70-12_1200365",1,"Created","The PCB definition dossier shall include the drawings containing at least the following:\n1.\tDrilling drawing,\n2.\tDrilling tables, including:\n(a)\tSymbol, \n(b)\tDiameter of as-manufactured holes,\n(c)\tTolerance,\n(d)\tPlated or not plated,\n(e)\tQuantity. \n3.\tBuild-up data, including:\n(a)\tNumbered conductive layers from top to bottom,\n(b)\tTotal copper thickness, basic + plated, for each layers with tolerances,\n(c)\tPresence of planes: ground and supply, mesh plane or full copper,\n(d)\tPresence of layers with controlled impedance,\n(e)\tThickness tolerance of laminate and prepreg, including minimum as-manufactured insulation distances,\n(f)\tTotal PCB thickness and tolerance,\n(g)\tSpecification if thickness is measured over bare laminate or over conductive pattern,\n(h)\tSpecific requirements for build-up.\nNOTE 1\tExamples of specific requirements for build-up are:\n·\tstyle of prepreg and laminate,\n·\tuse of separate copper foil or copper cladding on laminate for external layers,\n·\tuse of single or double sided laminate,\n·\tuse of two individually cured insulators to achieve double insulation.\nNOTE 2\tExamples of Drilling drawing, Drilling table and Build-up data are given in Figure A-2, Figure A-3, Figure A-4."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.1.2.1a","Requirement","ECSS-Q-ST-70-01_0500003",1,"Created","The supplier shall define and document cleanliness requirements in a cleanliness requirement specification (CRS), in conformance with the DRD in Annex A."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.1.3b","Requirement","ECSS-Q-ST-70-01_0500009",1,"Created","The specified contamination levels shall be derived from the acceptable performance losses simulated through dedicated modelling."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.2.1.1c","Requirement","ECSS-Q-ST-70-01_0500021",1,"Created","When the design baseline is incompatible with cleanliness requirements, the design changes shall be identified and corrective actions shall be taken in close cooperation with all levels involved."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.2.1.2g","Requirement","ECSS-Q-ST-70-01_0500028",1,"Created","When contamination sensitive items are involved or for materials in the vicinity of cryogenic surfaces, more stringent requirements shall apply.\n    NOTE Those more stringent requirements are specified in clauses 5.2.1.2h to 5.2.1.2j."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.2.2.1e","Requirement","ECSS-Q-ST-70-01_0500037",1,"Created","For elements that cannot be cleaned after manufacturing, then manufacturing and assembling areas shall meet the cleanliness level requirements specification."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.2.2.2a","Requirement","ECSS-Q-ST-70-01_0500041",1,"Created","Involved personnel shall be trained with respect to the cleanliness policy."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.2.2.2h","Requirement","ECSS-Q-ST-70-01_0500048",1,"Created","An audit of the integration facilities shall be performed according to ECSS-Q-ST-10 clause 5.2.3 criteria."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.2.3.2a","Requirement","ECSS-Q-ST-70-01_0500059",1,"Created","Launcher parts, shall be clean in order to avoid contamination of the clean items of the space system.\n    NOTE Launcher parts can be fairings and mechanical systems for double or multiple launches."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.3.1.1c","Requirement","ECSS-Q-ST-70-01_0500067",1,"Created","The floor shall be resistant to withstand wear by personnel and operations within the room."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.3.1.2c","Requirement","ECSS-Q-ST-70-01_0500073",1,"Created","In laminar flow cleanrooms, the air flow velocity through the cross section of the room shall be maintained at 27 m/min with a uniformity within ± 20 % throughout the undisturbed room."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.3.1.5f","Requirement","ECSS-Q-ST-70-01_0500086",1,"Created","Monitoring techniques and routines shall be established to meet the requirements of a specific category of cleanroom or clean work station."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.3.1.6a","Requirement","ECSS-Q-ST-70-01_0500095",1,"Created","For a preliminary budget only, i.e. for SRR, the correlation between the airborne and PFO shall be established on the basis of the Table 5-5."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.3.1.9a","Requirement","ECSS-Q-ST-70-01_0500106",1,"Created","A positive pressure differential shall be maintained between the cleanroom and the outside. "]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.3.1.12c","Requirement","ECSS-Q-ST-70-01_0500114",1,"Created","Maintenance shall comprise regular inspections of the cleanroom, its control facilities and its operating equipment, including calibration of all inspection and monitoring devices as specified in ECSS-Q-ST-20."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.3.1.12i","Requirement","ECSS-Q-ST-70-01_0500120",1,"Created","The cleanliness after the cleaning operations shall be verified by inspection by means of UV or high intensity white light."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.3.1.13b","Requirement","ECSS-Q-ST-70-01_0500125",1,"Created","The access to the areas shall be controlled by a permanently operating access control or door lock system."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.3.1.13o","Requirement","ECSS-Q-ST-70-01_0500138",1,"Created","Personnel movements to and from the cleanroom shall be kept to a minimum."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.3.1.13u","Requirement","ECSS-Q-ST-70-01_0500144",1,"Created","Fingernail polish shall not be permitted in the area."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.3.3a","Requirement","ECSS-Q-ST-70-01_0500153",1,"Created","The CRS and the C&CCP shall address the cleanliness and contamination control policy for any other facilities such as anechoic chamber, EMC chamber."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.4.1.2.1a","Requirement","ECSS-Q-ST-70-01_0500158",1,"Created","Cleaning aids shall not increase the contaminant levels of the items to be cleaned."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.4.2.3a","Requirement","ECSS-Q-ST-70-01_0500172",1,"Created","Molecular contamination shall be monitored through visual inspection and quantitative methods directly on the surface (including witnesses) or indirectly after transfer of contaminants.\n    NOTE 1 Surfaces can be examined by the same visual inspection methods as for particulate contamination. Experience with Micro-VCM tests has shown that, generally, levels of organic contamination above 1 ´ 10-6 g/cm2 can already be visible to the naked eye. By wet wiping of a portion of the surface or after evaporation of a droplet of a substrate compatible solvent, a contamination can be revealed by contrast. \n    NOTE 2 A surface of a known area is wiped with a clean tissue, the tissue is subjected to extraction with chloroform of spectral grade, and the residue of the chloroform is analysed by infrared techniques in accordance with ECSS-Q-ST-70-05. This method, applied to a wiped area of 100 cm2, permits detection of organic contamination levels down to 3 10-9 g/cm2. The results of this method depend very much on the surface roughness, on the type of tissue and on the solvent used. Particular attention is paid to the compatibility between solvent and surface.\n    NOTE 3 A surface of a known area is rinsed with a solvent and the residue is weighed after evaporation according to ASTM-E1235M-95.. The accuracy and detection limit of this method depend greatly upon the sensitivity of the balance, the substrate water absorption, the washing efficiency and the solvent background. The NVR measurement is expressed in mass per unit area and the residue can be used for further analyses). Direct measurements can be made in situ using quartz crystal microbalances (QCM).\n    NOTE 4 Further analyses can be performed to characterize molecular contamination (e.g. gas chromatography, mass spectrometry, ultra-violet degradation, SEM)."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.4.2.6a","Recommendation","ECSS-Q-ST-70-01_0500262",1,"Created","Contamination of external surfaces should be monitored.\n    NOTE 1 particulate contamination can be measured by light scattering (e.g. using the Sun or a laser as the a light source) or using QCMs with a crystal having a surface to which particles stick.\n    NOTE 2 Molecular contamination can be measured using QCM located near a sensitive item and maintained at the same temperature as the item or using a mass spectrometer.\n    NOTE 3 Measurements of contamination in space are not often made because the policy of cleanliness control is based upon the basic principle of achieving the lowest possible contamination levels with existing knowledge and within the allocated financial budgets. However, it is advisable to implement an “in space contamination monitoring” as part of the spacecraft housekeeping. When appropriate sensor elements are applied it is possible to predict design life-times at system, subsystem, component or equipment levels."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.4.3.1f","Requirement","ECSS-Q-ST-70-01_0500183",1,"Created","A cleanliness declaration of conformity shall be delivered for space hardware."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.4.3.2j","Requirement","ECSS-Q-ST-70-01_0500194",1,"Created","Baking time shall start when the material/item under baking has reached the predefined bakeout temperature."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.4.4d","Requirement","ECSS-Q-ST-70-01_0500202",1,"Created","Storage areas shall provide adequate protection to the package and the product for the intended storage period."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","5.4.4m","Requirement","ECSS-Q-ST-70-01_0500211",1,"Created","Bags for contamination-sensitive items shall be flushed with dry nitrogen or dry clean air and then sealed."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","A.2.1<3>a","Requirement","ECSS-Q-ST-70-01_0500223",1,"Created","The CRS shall describe all possible contamination sources to be analysed and the maximum acceptable emissions.\n    NOTE For example: Materials outgassing, lubricants escaping from bearings, wear particles from moving parts, terrestrial contaminants such as dust, plume contaminants from thrusters and engines, leaks from fuel systems and from hermetically sealed components, dumps and EVA, co-passengers, fairing and equipment bay items of the launcher."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","B.2.1<2>a","Requirement","ECSS-Q-ST-70-01_0500230",1,"Created","The C&CCP shall list the applicable and reference documents to support the generation of the document."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","B.2.1<6>c","Requirement","ECSS-Q-ST-70-01_0500241",1,"Created","The C&CCP shall contain a list (or brief description) of internal procedures for personnel training and rules to operate under contamination control conditions."]
["ECSS-Q-ST-70-01C","ECSS - Superseded v1.0","B.2.1<7.5>b","Requirement","ECSS-Q-ST-70-01_0500249",1,"Created","A cleanliness control flow chart shall be established, showing the stages at which specific cleanliness controls are undertaken, reported in an annex to the C&CCP."]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","4.1.2a","Requirement","ECSS-Q-ST-60-02_0450002",1,"Created","The supplier shall establish and maintain an organization for the management of the ASIC and FPGA programme. "]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","4.3.1a","Requirement","ECSS-Q-ST-60-02_0450007",1,"Created","The supplier shall prepare a detailed ASIC and FPGA development plan (ADP) in conformance with the DRD in Annex B. "]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","5.2c","Requirement","ECSS-Q-ST-60-02_0450016",1,"Created","Each development step using design inputs shall reflect the revision numbers of the inputs in a log file to prove consistency;"]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","5.3.5b","Requirement","ECSS-Q-ST-60-02_0450026",1,"Created","The documentation generated within this phase shall be reviewed."]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","5.4.1e","Requirement","ECSS-Q-ST-60-02_0450035",1,"Created","The architecture definition and the baseline choices made during the definition phase shall be settled, frozen and documented with a level of detail that allows proceeding with the subsequent detailed design."]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","5.4.4a","Requirement","ECSS-Q-ST-60-02_0450040",1,"Created","As a minimum, the following activities shall be performed and documented in an architecture verification and optimization report:\n    1. Verify that the defined architecture meets the requirements by appropriate simulation and analysis techniques;\n    2. Verify that the models referred to in clause 5.4.2a.9 above are compliant to the verification plan;\n    3. Perform an independent verification in order to avoid masking of design errors;\n    4. When allocation and connectivity of hard-macro cells can be an issue, a preliminary floorplan, assure that the expected cells are effectively place- and routable within the given constraints; \n        NOTE This is not applicable for FPGA designs.\n    5. Re-assess the feasibility and risks;\n    6. Find an application related trade-off for conflicting requirements;\n        NOTE For example: power consumption vs. speed and performance, pin count vs. package size and complexity vs. die area. \n    7. Establish the implementation choices."]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","5.5.3b","Requirement","ECSS-Q-ST-60-02_0450054",1,"Created","Use the agreed design tools as specified in the ADP (see clause 5.3.4). Check their maintenance status. Consider known bugs, existing patches, preventive and workaround measures."]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","5.5.4c","Requirement","ECSS-Q-ST-60-02_0450063",1,"Created","If an iteration back to the architectural design is required by means of changes in the model released during the PDR, that model shall be verified again."]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","5.5.7c","Requirement","ECSS-Q-ST-60-02_0450069",1,"Created","The reviewers shall verify that the detailed design documentation (see clause 7.3.5) together with the documentation of previous development phases completely documents all results obtained and decisions made along with the corresponding justifications in a level of detail that allow to proceed with the layout. "]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","5.6.1a","Requirement","ECSS-Q-ST-60-02_0450074",1,"Created","The layout shall generate the placement and routing information to meet the design rules, timing and other constraints. "]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","5.6.7g","Requirement","ECSS-Q-ST-60-02_0450087",1,"Created","In the case where no DDR was held after the detailed design phase, the reviewers shall check that the CDR encompasses also all review items of the DDR."]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","5.7.2e","Requirement","ECSS-Q-ST-60-02_0450093",1,"Created","The production test shall be performed on 100 % of the delivered prototypes, using the test vectors generated during the previous phases."]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","5.8.3b","Requirement","ECSS-Q-ST-60-02_0450105",1,"Created","License agreements for the intellectual property (the design itself and third party IP cores) contained in the device shall be established to cover the whole lifetime."]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","5.8.4a","Requirement","ECSS-Q-ST-60-02_0450198",1,"Created","The executive summary report shall be completed in conformance with the DRD in Annex I."]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","5.8.6e","Requirement","ECSS-Q-ST-60-02_0450121",1,"Created","The reviewer shall check that the planned measures, tools, methods and procedures were applied."]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","6.1c","Requirement","ECSS-Q-ST-60-02_0450125",1,"Created","ECSS-Q-ST-60 clauses 4.5, 5.5 and 6.5 (components quality assurance) shall apply. "]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","6.2b","Requirement","ECSS-Q-ST-60-02_0450132",1,"Created","Design reviews shall be defined along with the criteria for their successful completion in the ASIC and FPGA development plan (see clause 5.3.4). "]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","6.3c","Requirement","ECSS-Q-ST-60-02_0450143",1,"Created","Extraordinary risks shall be covered by a contingency plan identifying alternative or back-up solutions."]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","7.1g","Requirement","ECSS-Q-ST-60-02_0450151",1,"Created","If a document is delivered before being complete, each page with incomplete information shall be clearly marked. \n    NOTE Some of the information listed is better delivered separately or in appendices, such as layout plots, gate-level schematics and lists of undetected faults."]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","7.3.4a","Requirement","ECSS-Q-ST-60-02_0450161",1,"Created","The detailed design documentation shall consist of the following contributions to the architectural design documentation:\n    1. The design entry report providing all inputs available for the detailed design phase as detailed in clause 5.5.3.\n    2. The netlist generation report describing the work performed and the decisions taken to generate a netlist as detailed in clause 5.5.4.\n    3. The netlist verification report listing all steps of simulation and verification performed (see clause 5.5.5) together with the corresponding results."]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","8.1a","Requirement","ECSS-Q-ST-60-02_0450170",1,"Created","Upon request, the customer shall receive free of charge from the supplier the information coming from the manufacturer or foundry, for the duration of the development, a complete design kit for the selected process, including all libraries and design kit tools and their complete documentation, in order to allow the customer to independently verify the design.\n    NOTE This only applies if such a design kit actually exists for the design tools available at the customer."]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","A.2.1b","Requirement","ECSS-Q-ST-60-02_0450179",1,"Created","Compliance matrix to the clauses of this standard taking into account applicable tailoring."]
["ECSS-Q-ST-60-02C","ECSS - Superseded v1.0","G.2.1e","Requirement","ECSS-Q-ST-60-02_0450190",1,"Created","All signal interfaces shall be described in detail including for instance a description of all signals, test and power pins, specifying e.g. the usage of the signals and the signal polarity. "]
["ECSS-Q-ST-60-15C","ECSS - Superseded v1.0","5.1b","Requirement","ECSS-Q-ST-60-15_1150002",1,"Created","A draft mission environment specification shall be available at SRR."]
["ECSS-Q-ST-60-15C","ECSS - Superseded v1.0","5.1c","Requirement","ECSS-Q-ST-60-15_1150003",1,"Created","A final version of mission environment specification shall be available latest at system PDR."]
["ECSS-Q-ST-60-15C","ECSS - Superseded v1.0","5.1m","Requirement","ECSS-Q-ST-60-15_1150014",1,"Created","For any component that is estimated to have on-orbit performance degradation due to TID, a WCA of the function shall be performed in accordance with requirements of ECSS-Q-ST-30 to demonstrate that the function performs within specification despite radiation induced drifts in its constituent part parameters at EOL."]
["ECSS-Q-ST-60-15C","ECSS - Superseded v1.0","5.2b","Requirement","ECSS-Q-ST-60-15_1150027",1,"Created","A draft mission environment specification shall be available at SRR."]
["ECSS-Q-ST-60-15C","ECSS - Superseded v1.0","5.2h","Requirement","ECSS-Q-ST-60-15_1150034",1,"Created","TNID irradiation test plans shall be submitted to customer for approval.\n    ","NOTE This is because no standard method exists for TNID testing."]
["ECSS-Q-ST-60-15C","ECSS - Superseded v1.0","5.2q","Requirement","ECSS-Q-ST-60-15_1150042",1,"Created","If combined TNID and TID tests are used to get the combined TID/TNID sensitivity, such test plans shall be submitted to customer for approval.\n    ","NOTE Generally, TNID sensitive parts are also sensitive to TID."]
["ECSS-Q-ST-60-15C","ECSS - Superseded v1.0","5.2v","Requirement","ECSS-Q-ST-60-15_1150047",1,"Created","A final version of radiation analysis report shall be issued for equipment CDR.\n    ","NOTE At that stage all RHA activities except RVTs are completed."]
["ECSS-Q-ST-60-15C","ECSS - Superseded v1.0","5.3h","Permission","ECSS-Q-ST-60-15_1150115",1,"Created","For the SET criticality analysis of SET in analog ICs, worst case SET templates in Table 5-4 may be used in the absence of acceptable test data."]
["ECSS-Q-ST-60-15C","ECSS - Superseded v1.0","5.3l","Requirement","ECSS-Q-ST-60-15_1150068",1,"Created","Below a LETth of 15 MeVcm2/mg proton induced sensitivity analysis shall be analyzed."]
["ECSS-Q-ST-60-15C","ECSS - Superseded v1.0","5.3s","Requirement","ECSS-Q-ST-60-15_1150075",1,"Created","For any component that is not immune to destructive SEE analysis, it shall be demonstrated that the probability of occurrence in the mission environment is more than 10 times lower than component intrinsic failure rate.\n    ","NOTE Examples of destructive SEE are: SEL, SEB, SEGR and SEDR."]
["ECSS-Q-ST-60-15C","ECSS - Superseded v1.0","5.3dd","Requirement","ECSS-Q-ST-60-15_1150086",1,"Created","All data and analysis shall be documented in Radiation Analysis report in conformance with the DRD in Annex B."]
["ECSS-Q-ST-60-15C","ECSS - Superseded v1.0","A.2.1<3>a","Requirement","ECSS-Q-ST-60-15_1150094",1,"Created","GCR fluxes versus LET spectrum calculated for a given Aluminium shield thickness (e.g. 1 g/cm2) shall be presented with figure and table."]
["ECSS-Q-ST-60-15C","ECSS - Superseded v1.0","B.2.1<3>a","Requirement","ECSS-Q-ST-60-15_1150103",1,"Created","The radiation analysis report shall provide TNID tolerance of each sensitive component with reference of test report and date code of tested parts."]
["ECSS-Q-ST-70-05C Rev.1","ECSS - Superseded v1.0","5.1.1f","Requirement","ECSS-Q-ST-70-05_0540006",1,"Informative Change","Before starting any operation, safety hazards shall be identified, and the necessary precautions taken to minimize risks.","NOTE \tFor example, use of protection devices when chloroform is used.\n"]
["ECSS-Q-ST-70-05C Rev.1","ECSS - Superseded v1.0","5.1.3b","Requirement","ECSS-Q-ST-70-05_0540012",1,"Unchanged","Limited-life materials shall be labelled with their shelf lives and dates of manufacture."]
["ECSS-Q-ST-70-05C Rev.1","ECSS - Superseded v1.0","5.2.3.2a","Requirement","ECSS-Q-ST-70-05_0540023",1,"Informative Change","For the washing process the following steps shall be applied:\n1.\tPlace the contaminated solvent in a Petri dish, and evaporate it in a slightly tilted position with an infrared lamp until only a few droplets remain.\n2.\tTransfer the droplets to the IR-transparent window.\n3.\tPosition the droplets on the window in an area corresponding to the beam shape of the IR spectrophotometer.\n4.\tDistribute the contaminant over the area of the IR transparent disk covered by the IR beam.","NOTE \t1\tto item 2: To avoid contamination and facilitate the work, a glass rod or a micro syringe is normally used for the transfer.\nNOTE \t2\tto item 4: This step is also appropriate for contaminants or substances of low surface tension, which tend to concentrate in small spots (e.g. silicones). Concentration into small spots can lead to a local saturation of the IR signal and thus to a subsequent underestimation of the overall concentration.\n"]
["ECSS-Q-ST-70-05C Rev.1","ECSS - Superseded v1.0","5.2.3.3e","Requirement","ECSS-Q-ST-70-05_0540031",1,"Unchanged","Depending on the chosen type of wiping process (wet or dry), the following steps shall be performed:\n1.\tFor a wet wipe process \n(a)\tFold with tweezers the pre-cleaned tissue in order to use it as a little \"sponge\";\n(b)\tWet with spectral grade IPA or chloroform;\n(c)\tHold the folded tissue with curved point tweezers;\n(d)\tStore the tissue after wiping, when the solvent is evaporated in the transport container.\n2.\tFor a dry wipe process, cover the foam or rubber tube with a standard filter paper and a pre-cleaned tissue."]
["ECSS-Q-ST-70-05C Rev.1","ECSS - Superseded v1.0","5.2.3.3f","Requirement","ECSS-Q-ST-70-05_0540032",1,"Unchanged","The tissue to be analysed shall be immersed for 10 minutes to 15 minutes in a known quantity of spectral grade solvent contained in a Petri dish of 70 mm diameter."]
["ECSS-Q-ST-70-05C Rev.1","ECSS - Superseded v1.0","5.4.2a","Requirement","ECSS-Q-ST-70-05_0540042",1,"Unchanged","Any nonconformance that is observed during the measurement procedure shall be dispositioned in conformance to ECSS-Q-ST-10-09."]
["ECSS-Q-ST-70-05C Rev.1","ECSS - Superseded v1.0","5.4.3.1i","Requirement","ECSS-Q-ST-70-05_0540051",1,"Unchanged","The standards materials used for the calibration lines shall be of high purity."]
["ECSS-Q-ST-70-05C Rev.1","ECSS - Superseded v1.0","5.4.3.3b","Requirement","ECSS-Q-ST-70-05_0540061",1,"Informative Change","The calibration curve shall have a correlation coefficient higher than 0,98 for six sample points.","NOTE \tA typical calibration curve is shown in C.3.3.\n"]
["ECSS-Q-ST-70-05C Rev.1","ECSS - Superseded v1.0","5.4.3.5b","Requirement","ECSS-Q-ST-70-05_0540070",1,"Unchanged","The noise level shall be at least three times less than the signal in order to recognize a signal."]
["ECSS-Q-ST-70-05C Rev.1","ECSS - Superseded v1.0","5.4.5.2d","Requirement","ECSS-Q-ST-70-05_0540079",1,"Unchanged","The certification of personnel shall be based upon objective evidence of reproducibility and accuracy."]
["ECSS-Q-ST-70-05C Rev.1","ECSS - Superseded v1.0","5.5.3a","Requirement","ECSS-Q-ST-70-05_0540089",1,"Unchanged","The supplier shall perform an annual regular review which consists of:\n1.\tinspecting apparatus and associated equipment,\n2.\tevaluating the mutual comparability (testing),\n3.\treporting the nonconformances, and\n4.\treporting the audit findings."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","4.2.2.2a","Requirement","ECSS-E-ST-20-07_0080001",1,"Created","Overload capability of the spacecraft RF receivers during the pre-launch and launch phases with or without fairing, shall be demonstrated by the spacecraft supplier.\n    NOTE 1 It is expected the electromagnetic environment generated by companion payloads is assessed by the launching company and addressed in the User’s Manual.\n    NOTE 2 A conductive fairing is likely to cause resonances and cavity effects."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","4.2.2.2b","Requirement","ECSS-E-ST-20-07_0080002",1,"Created","Spacecraft equipment shall not exhibit any malfunction, degradation of performance or deviation beyond the tolerance indicated in its individual specification after being exposed, even not operating, to the electromagnetic environment from the launcher and launch site.\n    NOTE Most of spacecraft equipment is not operating during launch. During the launching sequence spacecraft transmitters and receivers (platform and payload) can be either in OFF- or ON-state depending on the launch vehicle."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","4.2.6a","Requirement","ECSS-E-ST-20-07_0080012",1,"Created","Spurious emissions requirements at antenna ports shall be specified for RF compatibility purpose by the spacecraft supplier."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","4.2.10.2c","Requirement","ECSS-E-ST-20-07_0080020",1,"Created","An upper value of common mode voltage shall be specified considering:\n    1. power quality requirements defined in ECSS-E-ST-20 for “Spacecraft bus”,\n    2. type of detectors and sensitivity,\n    3. characteristics of analogue signal monitor receiver circuit, in accordance with ECSS-E-ST-50-14, Table 5-2 d,\n    4. characteristics of bi-level signal monitor receiver circuit, in accordance with ECSS-E-ST-50-14, clause Table 6-2 e,\n    5. hazards due to fault currents internal to the space vehicle or between the space vehicle and its EGSE."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","4.2.11.2i","Requirement","ECSS-E-ST-20-07_0080031",1,"Created","If the structure is used as the return current path, bonding provisions shall be such that DC and AC voltage drops along power paths comply with clause 4.2.10.2c."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","4.2.13.2f","Recommendation","ECSS-E-ST-20-07_0080261",1,"Created","Overshields should be bonded to chassis ground at intermediary points with a separation distance less than 1m between two grounding points."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","5.2.2.3b","Requirement","ECSS-E-ST-20-07_0080050",1,"Created","During testing, at least one of the following conditions shall be met:\n    1. the ambient is at least 6 dB below the individual test limits, \n    2. the EUT complies with the individual test limits,\n    3. it is shown that recorded data exceeding the limits cannot be generated by the EUT (emission tests) or cannot sensitize the EUT (susceptibility tests)."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","5.2.3.2c","Requirement","ECSS-E-ST-20-07_0080059",1,"Created","The metallic ground planes shall be electrically bonded to the floor or wall of the basic shielded room structure at least once every 1 m."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","5.2.3.3b","Requirement","ECSS-E-ST-20-07_0080063",1,"Created","Composite ground planes shall be electrically bonded to the enclosure with means suitable to the material."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","5.2.4g","Requirement","ECSS-E-ST-20-07_0080070",1,"Created","If the return line is grounded at the power source in the actual installation (star distribution), the return line of the LISN shall be grounded on the power source side."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","5.2.6.3c","Requirement","ECSS-E-ST-20-07_0080081",1,"Created","When mounting bases do not have bonding straps, bonding straps shall not be used in the test setup."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","5.2.6.6.2c","Requirement","ECSS-E-ST-20-07_0080089",1,"Created","If a cable is longer than 10 m in the actual installation, the cable length in the set up shall be between 10 m and the actual length."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","5.2.6.6.3f","Requirement","ECSS-E-ST-20-07_0080099",1,"Created","If the power leads are twisted in the actual installation, they shall be twisted up to the LISN's"]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","5.2.7.1c","Requirement","ECSS-E-ST-20-07_0080108",1,"Created","When the EUT has several available modes (including software controlled operational modes), the number of modes to be tested for emission and susceptibility shall be such that all circuitry is evaluated. \n    NOTE It is expected that the customer defines or agrees operating modes."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","5.2.9.1b","Requirement","ECSS-E-ST-20-07_0080117",1,"Created","Video filtering shall not be used to bandwidth limit the receiver response. "]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","5.2.9.4d","Requirement","ECSS-E-ST-20-07_0080128",1,"Created","Data output of the EUT test result shall be in the form of amplitude over time (for the time domain plots) and amplitude over frequency (for frequency domain plots), superimposed with the EMI test limit."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","5.2.10.1c","Requirement","ECSS-E-ST-20-07_0080136",1,"Created","Step sizes shall be decreased such to permit observation of a response.\n    NOTE For receivers, it can make use of the frequency plan to adjust the number of points."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","5.2.10.2a","Requirement","ECSS-E-ST-20-07_0080137",1,"Created","Susceptibility test signals shall be pulse modulated (on/off ratio of 40 dB minimum) at a 1 kHz rate with a 50 % duty cycle for susceptibility signals at a frequency larger than 100 kHz."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","5.2.11.1a","Requirement","ECSS-E-ST-20-07_0080147",1,"Created","Measurement antennas, current probes, field sensors, and other devices used in the measurement loop shall be calibrated at least every two years or when damaged."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","5.3.3c","Requirement","ECSS-E-ST-20-07_0080155",1,"Created","In case of a transmitting spacecraft under fairing, the EMISM applied to EED's shall be verified."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","5.3.10b","Requirement","ECSS-E-ST-20-07_0080166",1,"Created","Except for bonding used only for charging control, the probes shall be reversed and re-measured to detect possible non linearities across the bonded junction.\n    NOTE See clause 5.3.5b. "]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","5.4.4.3a","Requirement","ECSS-E-ST-20-07_0080175",1,"Created","The test setup shall be as follows:\n    1. Maintain a basic test setup for the EUT as specified in 5.2.6 and Figure 5-3.\n    2. Configure the test setup for the measurement system check as shown in Figure 5-10.                              \n    3. Configure the test setup for compliance testing of the EUT as shown in Figure 5-11.                             "]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","5.4.5.3a","Requirement","ECSS-E-ST-20-07_0080184",1,"Created","The test sequence shall be as follows:\n    1. EUT not operating, initial measurements on the six semi-axes at the reference distances.\n    2. Deperm:\n        (a) EUT not operating, application of a deperming field in accordance with Figure 5-12 frequency 3 Hz, maximum amplitude between 4 000 µT and 5 000 µT, successively on each XYZ axis of the EUT.\n            NOTE 1 This is usually done using Helmholtz coils.\n            NOTE 2 A sequence of symmetrical sine periods of increasing and decreasing amplitude gives better results than a sine wave modulated by exponentials or ramp functions.                                          \n        (b) Measurement after deperm on the six semi-axes at the reference distances.       \n    3. Perm:\n        (a) EUT not operating, application of a perm field of 300 µT on each XYZ axis.\n        (b) Measurement after perm on the six semi-axes at the reference distances.\n    4. Stray field: EUT operating, measurement on the six semi-axes at the reference distances.\n    5. Final deperm: repeat 5.4.5.3a.2."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","5.4.6.4c","Requirement","ECSS-E-ST-20-07_0080194",1,"Created","The measurement system shall be checked as follows: \n    1. Using the system check path of Figure 5-13, perform the following evaluation of the overall measurement system from each antenna to the data output device at the highest measurement frequency of the antenna: \n        (a) Apply a calibrated signal level that is at least 6 dB below the limit (limit minus antenna factor) to the coaxial cable at the antenna connection point.\n        (b) Scan the measurement receiver in the same manner as a normal data scan, and verify that the data-recording device indicates a level within ±3 dB of the injected signal level.\n        (c) If readings are obtained which deviate by more than ±3 dB, locate the source of the error and correct the deficiency prior to proceeding with the testing.\n    2. Using the measurement path of Figure 5-13, perform the following evaluation for each antenna to demonstrate that there is electrical continuity through the antenna:\n        (a) Radiate a signal using an antenna or stub radiator at the highest measurement frequency of each antenna.\n        (b) Tune the measurement receiver to the frequency of the applied signal and verify that a received signal of appropriate amplitude is present.\n            NOTE This evaluation is intended to provide a coarse indication that the antenna is functioning properly. There is no requirement to measure accurately the signal level."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","5.4.8.2a","Requirement","ECSS-E-ST-20-07_0080202",1,"Created","The test equipment shall be as follows:\n    1. Signal generator with amplitude or pulse modulation capability,\n    2. pulse generator, 1 kHz - 100 kHz, adjustable duty cycle,\n    3. power amplifier, 50 kHz - 100 MHz,\n    4. current injection probe, 50 kHz - 100 MHz,\n    5. current measurement probe, 50 kHz - 100 MHz,\n    6. one or two calibration fixture(s) (jigs) defined in 5.2.8.3,\n    7. one two-channels oscilloscope, 50 W input impedance,\n    8. waveform recording device,\n    9. 50 W coaxial load,\n    10. LISN defined in 5.2.4,\n    11. spectrum analyzer (optional)."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","5.4.8.4b","Requirement","ECSS-E-ST-20-07_0080205",1,"Created","The measurement system shall be calibrated by performing the following procedures using the calibration setup:\n    1. Set the frequency of the generator to 50 kHz and apply the pulse modulation, Figure 5-19.                                            \n    2. Increase the applied signal until the oscilloscope indicates the voltage specified by application of clause 4.2.8.\n    3. Verify that both inputs of the oscilloscope, voltage monitored on 50 W and current monitored by the current probe, are consistent within 3 dB. This is applicable only if a current probe is used during calibration\n    4. Record the generator settings.\n    5. Repeat 5.4.8.4b.2 through 5.4.8.4b.4 for each measurement frequency."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","5.4.10.5a","Requirement","ECSS-E-ST-20-07_0080216",1,"Created","In addition to 5.2.10.4, data presentation shall provide:\n    1. Tabular data showing verification of the radiating loop in.5.4.10.4b.\n    2. Tabular data, diagrams, or photographs showing the locations and test frequencies determined in.5.4.10.4c.2(e) and 5.4.10.4c.2(f)."]
["ECSS-E-ST-20-07C","ECSS - Superseded v1.0","5.4.11.4a","Requirement","ECSS-E-ST-20-07_0080224",1,"Created","The measurement equipment and EUT shall be turned on and waited until they are stabilized.\n    NOTE It is important at this point to assess the test area for potential RF hazards and take precautionary steps to assure safety of test personnel and fire avoidance."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","4.2b","Requirement","ECSS-E-ST-20-08_0090002",1,"Created","The data specified in requirement 4.2a shall be determined during the development phase of a new component and need not be repeated during the qualification program."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","4.4a","Requirement","ECSS-E-ST-20-08_0090014",1,"Created","The critical interface information shall be part of the PMP list.\n    NOTE For PMP, see ECSS-Q-ST-70 Annex B."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.2d","Requirement","ECSS-E-ST-20-08_0090021",1,"Created","Deviations from this Standard applicable to the SCD-PVA shall:\n    1. be agreed between the customer and the supplier;\n    2. include alternative requirements equivalent to those of this Standard;\n    3. not affect the reliability and performances of the photovoltaic assemblies;\n    4. be only those specified in requirement 5.2c."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.3.2.6a","Requirement","ECSS-E-ST-20-08_0090032",1,"Created","PVA materials shall be capable of tolerating a defined erosion level resulting from spacecraft operation without degradation in the nominal performance of the PVA, in conformance with the PVA specification.\n    NOTE Example: thruster plumes."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.3.3.2c","Requirement","ECSS-E-ST-20-08_0090040",1,"Created","Potential parallel connections shall not prevent performance measurement specified in requirement 5.3.3.2b."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.3.3.2d","Requirement","ECSS-E-ST-20-08_0090041",1,"Created","If the dimensions of the coupon enables the accommodation, the full flight string length shall be represented on the qualification coupon."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.3.3.9d","Requirement","ECSS-E-ST-20-08_0090051",1,"Created","No failure shall be propagated from one solar array wiring group to another."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.3.3.13a","Requirement","ECSS-E-ST-20-08_0090060",1,"Created","The solar array design shall be such that it can survive the charging environment and operating conditions defined by the mission. "]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.4.3.4a","Requirement","ECSS-E-ST-20-08_0090070",1,"Created","The adherence of the SCAs to the substrate, shall be performed in parallel to panel laydown."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.4.5b","Requirement","ECSS-E-ST-20-08_0090079",1,"Created","The processes variables specified in requirement 5.4.5a shall be recorded during manufacturing."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.5.1.2i","Requirement","ECSS-E-ST-20-08_0090088",1,"Created","Each qualification coupon shall be flight representative as far as allowed by the dimensions of the qualification coupon "]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.5.1.3.3f","Permission","ECSS-E-ST-20-08_0091067",1,"Created","If space is available, additional components may be included to be tested as separate items."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.5.1.3.4d","Requirement","ECSS-E-ST-20-08_0090107",1,"Created","For a LEO mission, the following cycling profiles shall be used:\n    1. A temperature profile which envelopes the variation of temperature extremes during the mission. \n    2. The total profile, divided into a number of equally shaped sub-profiles, where the number of sub-profiles are:\n        (a) equal to the number of years of the mission, and \n        (b) with extreme cycle temperatures derived from the slicing of the temperature profile of the whole mission."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.5.1.3.4e","Requirement","ECSS-E-ST-20-08_0090108",1,"Created","The number of cycles and temperature limits of requirements 5.5.1.3.4a and 5.5.1.3.4b shall be stated in the SCD-PVA."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.5.1.4.4c","Requirement","ECSS-E-ST-20-08_0090118",1,"Created","Relative humidity shall be higher than 90 %. "]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.5.1.5.2b","Requirement","ECSS-E-ST-20-08_0090126",1,"Created","Testing shall demonstrate that the observed primary arcs do not produce any type of damage to the solar array or to the cells."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.5.3.2.2b","Requirement","ECSS-E-ST-20-08_0090137",1,"Created","Training records of the personnel performing the visual inspection shall be made available to the customer under request."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.5.3.2.5c","Requirement","ECSS-E-ST-20-08_0090144",1,"Created","The integrity of the substrate shall not deviate from the coupon assembly drawing."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.5.3.2.9a","Requirement","ECSS-E-ST-20-08_0090156",1,"Created","Cracks in the body of the diode, causing separation of the material, shall not be present."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.5.3.2.12a","Requirement","ECSS-E-ST-20-08_0090165",1,"Created","None of the wiring shall exhibit any of the following defects at the end of acceptance testing:\n    1. Sharp bends, sharp twists, sharp buckles or creases in the wire.\n    2. Delamination or looseness of the wire attachment.\n    3. Chafing or abrasion of the wire insulation.\n    4. Cracks, breaks or nicks in the wire insulation or conductor.\n    5. Exposed shields on shielded wires."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.5.3.2.18a","Requirement","ECSS-E-ST-20-08_0090173",1,"Created","All identification markings specified by the customer shall be firmly adhered to the locations identified on the assembly drawing."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.5.3.2.19b","Requirement","ECSS-E-ST-20-08_0090176",1,"Created","Stand-off of all components shall conform to the qualification coupon assembly drawing."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.5.3.3.4b","Requirement","ECSS-E-ST-20-08_0090187",1,"Created","The grounding resistance shall be the value stated in the SCD-PVA."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.5.3.3.7b","Requirement","ECSS-E-ST-20-08_0090195",1,"Created","When all the cells are protected by shunt diodes, the supplier shall provide the test method and precautions to be taken."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.5.3.4.2e","Requirement","ECSS-E-ST-20-08_0090205",1,"Created","Calibration shall be done with an agreed primary standard reference and secondary working standard (SWS) in conformance with clause 10."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.5.3.7.2a","Recommendation","ECSS-E-ST-20-08_0091072",1,"Created","Thermal vacuum cycling should be used."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.5.3.7.3g","Requirement","ECSS-E-ST-20-08_0090223",1,"Created","Acceptance criteria shall be: \n    1. A maximum increment of IOP, and a minimum isolation, as stated in the SCD-PVA.\n    2. The existence of electrical continuity (no open circuit).\n    3. At the end of the test, less than a 2 % increase in cracked cells or one cracked cell, whichever is higher, not cumulative with the results of the bake-out test and which can have an impact on the electrical performance of the string."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.5.3.11.2a","Requirement","ECSS-E-ST-20-08_0090234",1,"Created","The components to be checked for electrical continuity shall be identified in the SCD-PVA."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.5.3.11.3b","Requirement","ECSS-E-ST-20-08_0090242",1,"Created","No open circuit conditions shall be recorded during continuity testing."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","5.5.3.11.3c","Requirement","ECSS-E-ST-20-08_0090243",1,"Created","There shall be less than a 2 % increase in cracked cells or one cracked cell, whichever is higher, not cumulative with the results of the fatigue thermal cycling test, and which can have an impact on the electrical performance of the string."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","6.1.2b","Requirement","ECSS-E-ST-20-08_0090253",1,"Created","The SCD-SCA shall be prepared by the supplier in conformance with Annex B, and provided to the customer for reviewing and agreement."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","6.3.1a","Requirement","ECSS-E-ST-20-08_0090261",1,"Created","Acceptance tests shall be performed on the following:\n    1. components for delivery;\n    2. components used for qualification."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","6.4.1b","Requirement","ECSS-E-ST-20-08_0090272",1,"Created","Qualification shall be granted by the customer. "]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","6.4.2.2b","Requirement","ECSS-E-ST-20-08_0090281",1,"Created","The supplier shall provide access to the customer to monitor the manufacture of the test samples in conformance with a procedure agreed with the customer. "]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","6.4.3.1.4a","Requirement","ECSS-E-ST-20-08_0090290",1,"Created","The location and maximum dimensions of edge chips, corner chips and surface nicks shall be in conformance with Figure 6-1 and Table 6-2."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","6.4.3.1.5f","Requirement","ECSS-E-ST-20-08_0090300",1,"Created","Coverglasses shall be rejected if they contain cracks with any one of the following characteristics:\n    1. there is a visible separation between cracks;\n    2. there are more than three per cover;\n    3. meeting cracks are separated by more than 2 mm at the non-meeting end."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","6.4.3.1.8b","Requirement","ECSS-E-ST-20-08_0090308",1,"Created","In the interconnector weld area, clause 7.5.1.5.2 shall apply."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","6.4.3.2b","Requirement","ECSS-E-ST-20-08_0090311",1,"Created","The lateral dimensions of the coverglasses shall be such as to ensure 100 % coverage of the bare surface of the cells."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","6.4.3.4f","Requirement","ECSS-E-ST-20-08_0090326",1,"Created","The coefficient of determination for the indicated electrical parameters obtained from the curve fit shall be included."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","6.4.3.5.2d","Requirement","ECSS-E-ST-20-08_0090330",1,"Created","The irradiation intensity at all wavelengths shall be such as to ensure that the measurement is made in the region where the cell response short-circuit current versus irradiance is linear. "]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","6.4.3.8.2c","Requirement","ECSS-E-ST-20-08_0090339",1,"Created","Relative humidity shall be higher than 90 %. "]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","6.4.3.9.2b","Requirement","ECSS-E-ST-20-08_0090346",1,"Created","Test conditions shall be established according to a standard which is mutually agreed with the customer.\n    NOTE Example of standards that can be used for the test conditions of the coating adherence test are ISO 9211-4 and ECSS-Q-ST-70-13."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","6.4.3.11.2g","Requirement","ECSS-E-ST-20-08_0090358",1,"Created","After combined electron and photon irradiation, the SCAs shall conform to the requirements stated in the SCD-SCA."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","6.4.3.15.2a","Requirement","ECSS-E-ST-20-08_0090369",1,"Created","The integrated intensity of the photons shall be measured with a Sun-blind photo-diode."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","6.4.3.15.3a","Requirement","ECSS-E-ST-20-08_0090377",1,"Created","The electrical performance of the SCAs shall not degrade more than 70 % of the UV loss factor used for the EOL power analysis. "]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","6.4.3.15.3b","Requirement","ECSS-E-ST-20-08_0090378",1,"Created","The UV loss factor shall be specified in the SCD-SCA."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","6.5.2a","Requirement","ECSS-E-ST-20-08_0090388",1,"Created","An SCA shall be considered as failed if it exhibits one or more of the failure modes detailed in clause 6.5.1."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","7.1.1.2a","Requirement","ECSS-E-ST-20-08_0090397",1,"Created","The conditions and methods of testing shall conform to the bare solar cell source control drawing (SCD-BSC).\n    NOTE The bare solar cell specification consists of two parts, the generic specification (this Standard) and the SCD-BSC. The SCD-BSC contains the technical specification for a cell type relevant to acceptance testing, as well as for the qualification testing. For the preparation of the SCD-BSC for bare solar cells, refer to Annex C."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","7.1.2b","Requirement","ECSS-E-ST-20-08_0090407",1,"Created","Delivered solar cells shall have completed all tests and inspections specified herein in conformance with the SCD-BSC."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","7.3.1f","Requirement","ECSS-E-ST-20-08_0090416",1,"Created","For cells with integral diode the acceptance tests described in Table 9-1 shall be performed."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","7.3.2.2.4a","Requirement","ECSS-E-ST-20-08_0090425",1,"Created","The BSCs tested in conformance with clause 7.3.2.2.2 and accepted shall be graded for Itest. performance "]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","7.4.2.1b","Requirement","ECSS-E-ST-20-08_0090435",1,"Created","A production flow chart, process schedules and inspection procedures shall be provided."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","7.4.2.3d","Requirement","ECSS-E-ST-20-08_0090444",1,"Created","More than one failure in any subgroup, or more than two failures in total, shall constitute a failure in the qualification.\n    NOTE For a definition of failure see clause 7.6."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","7.5.1.2a","Requirement","ECSS-E-ST-20-08_0090445",1,"Created","Solar cells shall be inspected with an equipment with a resolution which is 5 times higher than the minimum allowed defect size to verify the requirements for defects on solar cell and contacts."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","7.5.1.5.2a","Requirement","ECSS-E-ST-20-08_0090455",1,"Created","The maximum dimension of voids or bubbles shall be 0,25 mm in diameter."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","7.5.1.5.4b","Requirement","ECSS-E-ST-20-08_0090463",1,"Created","The cumulative area of voids, bubbles and drops shall not exceed 2 % of the total area."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","7.5.3.2f","Requirement","ECSS-E-ST-20-08_0090474",1,"Created","There shall be a maximum of 3 % deviation in the current at the test voltage Vt, from the measurements before test, after the humidity and thermal cycling test in subgroup O. "]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","7.5.5.2b","Requirement","ECSS-E-ST-20-08_0090481",1,"Created","The monochromatic irradiation shall be generated by one of the following methods: \n    1. The irradiation shall be generated with the aid of narrow-band interference filters, having the following characteristic:\n        (a) for silicon solar cells, at least, at 14 discrete wavelength intervals between 0,3 mm and 1,1 mm; \n        (b) for single-junction GaAs solar cells at least, at 14 discrete wavelength intervals between 0,3 mm and 1,1 mm and at least 3 narrow band interference filters in the range 0,75 mm to 1,1 mm.\n        (c) for multi-junction GaAs solar cells, the number of narrow band interference filters and their wavelength are stated in the SCD-BSC.\n    2. By means of a high intensity monochromator for continuous recording between 0,3 mm and at least 1,8 mm."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","7.5.7.1.2b","Requirement","ECSS-E-ST-20-08_0090493",1,"Created","The chamber temperature shall then be increased to 60 °C minimum."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","7.5.7.2.2c","Requirement","ECSS-E-ST-20-08_0090502",1,"Created","Relative humidity shall be higher than 90 %."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","7.5.8.2d","Requirement","ECSS-E-ST-20-08_0090510",1,"Created","Any visible delamination of parts of the contacts or the anti-reflection coating shall not exceed the limits specified in clauses 7.5.1.4 and 7.5.1.5."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","7.5.10.2a","Requirement","ECSS-E-ST-20-08_0090513",1,"Created","The thickness of the solar cell metal contact in the interconnector weld area or on dedicated in-process test samples shall be checked with a step-height profiler, as stated in the SCD-BSC.\n    NOTE For example, with a betascope or a similar instrument."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","7.5.13.2h","Requirement","ECSS-E-ST-20-08_0090528",1,"Created","Electron irradiation at a dose corresponding to the dose at transfer orbit (as stated in the SCD-BSC) shall be added."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","7.5.14.2d","Requirement","ECSS-E-ST-20-08_0090532",1,"Created","The flux of the proton irradiation, in p+ cm-2 s-1, shall be as stated in the SCD-BSC."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","7.6.2b","Requirement","ECSS-E-ST-20-08_0090546",1,"Created","Failed components shall be identified as such and included in the delivery. "]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","7.9.2a","Requirement","ECSS-E-ST-20-08_0090551",1,"Created","If a bare cell is sensitive to ESD according to clause 5.2 of ESCC 23800 Issue 1 then it shall be handled and stored according to ESCC 24900 Issue 2, clause 10."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","8.3.1.3b","Requirement","ECSS-E-ST-20-08_0090560",1,"Created","These tests and inspections shall be performed at the plant of the manufacturer or at a facility approved by the customer.\n    NOTE For test house requirements, see ECSS-Q-ST-20-07."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","8.4b","Requirement","ECSS-E-ST-20-08_0090566",1,"Created","The supplier shall do the following:\n    1. maintain configuration control of all documents;\n    2. keep the issues of the documents effective at the date of acceptance by the customer; \n    3. provide the PID to the customer for review;\n    4. submit to the customer for review and approval any modifications or changes to documents in the PID with any quality and reliability implications."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","8.6.2.1a","Requirement","ECSS-E-ST-20-08_0090579",1,"Created","Before starting production of the qualification lot, the manufacturer shall compile a production test schedule, showing by date and duration, production and test activities, including all major processing operations and key stages in the production and testing. "]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","8.6.2.1b","Requirement","ECSS-E-ST-20-08_0090580",1,"Created","Process schedules and inspection procedures shall be provided."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","8.7.1.3.3a","Requirement","ECSS-E-ST-20-08_0090590",1,"Created","The projected area of any bubble or inclusions in the coverglass shall not be larger than 0,02 mm^2.\n    NOTE See MIL-PRF-13830."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","8.7.2a","Requirement","ECSS-E-ST-20-08_0090598",1,"Created","The transmission into air of the coverglass shall be measured (for l and T in conformance with requirement 8.7.2b) using a calibrated spectro-photometer as follows:\n    1. at an incidence angle of less than 10°,\n    2. with a wavelength tolerance of (l ± 2) nm, and \n    3. an absolute transmission tolerance of (T ± 1) %."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","8.7.4.5a","Requirement","ECSS-E-ST-20-08_0090609",1,"Created","The perpendicularity of the sides of the coverglass shall be measured using an optical instrument with a reference normal. "]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","8.7.7a","Requirement","ECSS-E-ST-20-08_0090618",1,"Created","When a conductive coating is incorporated in the coverglass, the surface resistivity shall be measured, using the equipment stated in the SCD-CVG, as follows:\n    1. Measure the resistance between two indium-tin soldered buzzbars applied to the coverglass, as shown in Figure 8-5.\n    2. Calculate the surface resistivity from the resistance and the length a, and b, defined in Figure 8-5 using the following equation:\n \nwhere\nR \tis the measured resistance;\nRS\tis the surface resistivity.\n                              "]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","8.7.11.1.2b","Requirement","ECSS-E-ST-20-08_0090627",1,"Created","The chamber temperature shall then be increased from ambient temperature to 50 °C at a minimum."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","8.7.11.2.2e","Requirement","ECSS-E-ST-20-08_0090637",1,"Created","High-purity water in conformance with ASTM D1193-99, Type I, shall be used."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","8.7.13.2a","Requirement","ECSS-E-ST-20-08_0090645",1,"Created","The coverglasses shall be subjected to 1 MeV electron irradiation."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","8.7.13.2d","Requirement","ECSS-E-ST-20-08_0090648",1,"Created","The nominal rate shall be lower than the value stated in the SCD-CVG."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","8.7.18b","Requirement","ECSS-E-ST-20-08_0090663",1,"Created","The coating shall show no evidence of delamination.\n    NOTE For further guidance, see also MIL-M-13508."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","8.8.2c","Requirement","ECSS-E-ST-20-08_0090667",1,"Created","Failure analysis of these components shall be performed by the supplier and the results provided to the customer as part of an NRB documentation.\n    NOTE For NRB, see ECSS-Q-ST-10-09."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","9.2.1.2.2c","Requirement","ECSS-E-ST-20-08_0090676",1,"Created","Any deviation from the required in-process, acceptance and qualification test s shall be justified.."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","9.2.2.2b","Requirement","ECSS-E-ST-20-08_0090683",1,"Created","Delivered external protection diodes shall have completed all tests and inspections specified in the SCD-EPD."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","9.4.4d","Requirement","ECSS-E-ST-20-08_0090695",1,"Created","The data documentation of acceptance tests shall be delivered together with the delivered cells/diodes and the qualification test lot."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","9.4.6a","Requirement","ECSS-E-ST-20-08_0090701",1,"Created","Documentation on acceptance tests shall conform to clause 9.8."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","9.5.3c","Requirement","ECSS-E-ST-20-08_0090714",1,"Created","For a procurement lot of a previously qualified external protection diodes, the qualification tests need not be repeated if the following conditions are satisfied:\n    1. No changes are made to the design, function or electrical or mechanical parameters of the external protection diode.\n    2. The same source control drawing is applicable.\n    3. No changes are made to the PID.\n    4. Delta qualification tests are performed to cover the requirements imposed by the new application. "]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","9.5.4.2b","Requirement","ECSS-E-ST-20-08_0090719",1,"Created","The test samples shall be chosen statistically and at random from a minimum number of diodes, stated in the SCD-BSC or SCD-EPD, and from the first n batches, where n is also stated in the SCD-BSC or SCD-EPD.\n    NOTE For sampling see ISO 2859."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","9.6.1b","Requirement","ECSS-E-ST-20-08_0090725",1,"Created","The test system shall be checked on compliance with 9.6.1a by using an oscilloscope and dummy cell before performing the following electrical test on diodes, 9.6.5, 9.6.14, 9.6.15, 9.6.16, 9.6.17 and 9.6.18.\n    NOTE The test methods, conditions and measurement requirements for the tests in Table 9-3 and Table 9-4 are detailed in clauses 9.6.2 to 9.6.18. For failure criteria, see clause 9.7."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","9.6.3a","Requirement","ECSS-E-ST-20-08_0090734",1,"Created","The overall lateral dimensions of the protection diode (including thickness of the EPD), contact dimensions and interconnector position shall conform to the requirements stated in the SCD-BSC or SCD-EPD."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","9.6.6.2f","Requirement","ECSS-E-ST-20-08_0090748",1,"Created","Water condensation on the surface of the protection diodes shall be prevented."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","9.6.8.3a","Requirement","ECSS-E-ST-20-08_0090753",1,"Created","The thickness of the metal layers of the diode contacts shall conform to the requirements of the interconnection process (as stated in the SCD-EPD), and the certified procurement specification of the supplier."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","9.6.11.2b","Requirement","ECSS-E-ST-20-08_0090762",1,"Created","The ultimate pull strength of each tab shall be as stated in the SCD-BSC or SCD-EPD."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","9.6.13.2b","Requirement","ECSS-E-ST-20-08_0090772",1,"Created","After the test, the samples shall be kept at temperatures below 50 °C until the diode characterization test is performed."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","9.6.16.2a","Requirement","ECSS-E-ST-20-08_0090781",1,"Created","The protection diodes shall be equipped with interconnects."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","9.6.16.2f","Requirement","ECSS-E-ST-20-08_0090786",1,"Created","Diode characterization shall be performed at the end of the sequence of pulses, after disconnection of the diode from the cell. "]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","9.6.17.2d","Requirement","ECSS-E-ST-20-08_0090792",1,"Created","The applied signal for the switching cycles shall be in conformance with the Figure 9-2."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","9.6.18.2e","Requirement","ECSS-E-ST-20-08_0090800",1,"Created","The test duration and parameter settings for each individual diode shall be as in Table 9-5 and mission requirements."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","10.1.1.2a","Requirement","ECSS-E-ST-20-08_0090811",1,"Created","Total Irradiance (solar constant AM0-equivalent) of the Sun simulator on the test plane shall be determined by the use of AM0 calibrated reference cells as indicated in clause 10.2."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","10.1.2b","Requirement","ECSS-E-ST-20-08_0090818",1,"Created","For multi-source simulators used for characterizing multijunction solar cells, the relevant class of solar simulator in Table 10-3 shall be determined for each junction. "]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","10.2.2.1a","Requirement","ECSS-E-ST-20-08_0090830",1,"Created","For single junctions, 10 solar cells representing a spectral response range similar when compared in conformance with requirement 10.2.2.1d to that of the cells to be tested, shall be calibrated for their AM0 equivalent short-circuit current using a Sun simulator, conforming to clause 10.1, using the accepted primary standards "]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","10.2.2.3.2b","Requirement","ECSS-E-ST-20-08_0090839",1,"Created","If the average short-circuit current of the photon-irradiated cells deviates by more than 1 % from the original values, a new set of SWS shall be selected from a different production process established to yield stable cells."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","10.2.4a","Requirement","ECSS-E-ST-20-08_0090847",1,"Created","All standard solar cells (primary and SWS) shall be kept at temperatures below 50 °C during operation and storage. "]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","10.2.5b","Requirement","ECSS-E-ST-20-08_0090850",1,"Created","Those cells that do not meet the stability requirements (> 1 % change per year in short circuit current) shall be discarded as reference cells."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","11.1.4.2.1a","Recommendation","ECSS-E-ST-20-08_0091090",1,"Created","The small signal electrical model parameters (Figure 11-4) should be calculated for each bias voltage Vcell,i and bias current Icell,i with respect to the frequency, as follows:\n  \n \n\n\n\n    1. Minimize the relative error of the theoretical impedance Ztheo(Ls,Rs,Cp,Rp,¦) with the measured values (regression by least square method).\n        NOTE \tAs the Nf impedance measurements\n \nare associated to the frequencies\n \nthe function to minimize is\n \nwhich is a function of Ls, Rs, Cp and Rp.\n\n    2. Calculate each parameter Rp, Cp, Ls and Rs by successive iterative optimization, one after the other, using the following initial parameters:\nRp0 = Z(fMIN),\nCp0 = 1/ (2 ´ p ´ fMIN Z(fMIN)),\nLs0 = Z(fMAX) /(2 ´ p ´ fMAX),\nRs0 = minimum value of Z(f).\n"]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","11.2.2.1a","Recommendation","ECSS-E-ST-20-08_0091093",1,"Created","The time domain capacitance measurement test set-up, should comprise the following test equipment:\n    1. A continuous or pulsed solar simulator according to the requirements specified in clause 10.\n    2. A solar array capacity tester which supplies a synchronizable fast switch to perform a controlled short-circuit release at the open circuit condition of the qualification coupon or SCA under test.\n    3. A digital-analogue oscilloscope to capture the voltage-current transient during the short-circuit release at the open circuit condition.\n    4. A twisted harness of short length to reduce the parasitic inductance of the harness from the test specimen to the capacity tester."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","A.2.1<6.1>a","Requirement","ECSS-E-ST-20-08_0090883",1,"Created","The SCD-PVA shall state the maximum value of the mass of the coupon, in g, obtained from the mass measurement specified in clause 5.4.3.2."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","A.2.1<7.1>a","Requirement","ECSS-E-ST-20-08_0090888",1,"Created","In conformance with clause 5.5.1.3, the SCD-PVA shall state the following:\n    1. The following test conditions:\n        (a) the number of cycles to perform;\n        (b) the temperature limits, in °C.\n    2. For the acceptance criteria:\n        (a) the maximum variation of IOP, in %,;\n        (b) the minimum insulation, in MW."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","A.2.1<8.3>d","Requirement","ECSS-E-ST-20-08_0090897",1,"Created","For bleed resistor test, in conformance with clause 5.5.3.3.5, the SCD-PVA shall state the range of values, in kW, of the bleed resistor."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","A.2.1<8.5>a","Requirement","ECSS-E-ST-20-08_0090903",1,"Created","In conformance with clause 5.5.3.5, the SCD-PVA shall state a procedure to measure the capacitance, including the test temperature (average operational temperature). "]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","B.2.1<6.1>a","Requirement","ECSS-E-ST-20-08_0090916",1,"Created","In conformance with clause 6.4.3.2, the SCD-SCA shall include:\n    1. A figure, showing the physical dimensions of the solar cell assembly, including both, the nominal values and tolerances.\n    2. The average weight (per lot) of solar cell assemblies including the interconnector, in grams."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","B.2.1<6.6>a","Requirement","ECSS-E-ST-20-08_0090921",1,"Created","In conformance with clause 6.4.3.7, the SCD-SCA shall include the number of cycles to be performed and their extreme temperatures, to simulate the number of eclipses occurring during one year in orbit for LEO missions, and 1000 thermal cycles for GEO missions, or the complete lifetime cycling for interplanetary or other mission types."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","B.2.1<6.12>a","Requirement","ECSS-E-ST-20-08_0090927",1,"Created","In conformance with clause 6.4.3.14 (it is applicable only for SCAs without protection diode or with a protection diode electrically isolated form the cell).the SCD-SCA shall include:\n    1. The reverse I/V characteristics measured under illumination of 1 S.C.;\n    2. The following measurement parameters shall be clearly stated in the SCD-SCA\n        (a) power supply limitation\n        (b) temperature\n        (c) hold time\n        (d) maximum reverse bias voltage\n    3. The pass-fail criteria\n        (a) the maximum change in the value of reverse current DI, in mA from the initial value of the same parameter when measured as delivered. Pass fail criteria shall be specified in the SCD-SCA.\n        (b) the maximum absolute value of the reverse current, in mA."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","C.2.1<5>a","Requirement","ECSS-E-ST-20-08_0090935",1,"Created","The SCD-BSC shall include:\n    1. Reference to the procurement specification of the supplier.\n    2. For silicon solar cells, the following characteristics of the cells:\n        (a) growth technique;\n        (b) doping element;\n        (c) orientation;\n        (d) main breakage direction;\n        (e) base resistivity;\n        (f) thickness;\n        (g) for ARC: materials; \n        (h) for metal contact materials and thickness.\n    3. For single and multi-junction III-V solar cells, the following characteristics of the cells: \n        (a) substrate material, orientation and thickness;\n        (b) doping element of the substrate;\n        (c) substrate resistivity;\n        (d) for each sub-cell: materials, \n        (e) for ARC: materials; \n        (f) for metal contact materials and thickness."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","C.2.1<6.9>a","Requirement","ECSS-E-ST-20-08_0090946",1,"Created","In conformance with clause 9.4.5.2, the SCD-BSC shall include for cells with protection diode electrically isolated from the cell:\n    1. For the test specified in requirement 9.4.5.2.2:\n        (a) the temperature, \n        (b) the forward current, \n        (c) the reverse voltage.\n    2. The pass-fail criteria for the test specified in clause 9.4.5.2.3:\n        (a) the maximum absolute value of the forward voltage in V;\n        (b) the reverse current in mA."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","C.2.1<7.7>a","Requirement","ECSS-E-ST-20-08_0090955",1,"Created","In conformance with clause 7.5.9, the SCD-BSC shall include\n    1. the equipment to measure the contact thickness;\n    2. the requirements of the interconnection process to uniformity of the contact. \n        NOTE Example: maximum and minimum values of the contact thickness in mm."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","C.2.1<7.11>a","Requirement","ECSS-E-ST-20-08_0090959",1,"Created","In conformance with clause 7.5.14.2, the SCD-BSC shall include:\n    1. The two energies to which cells of subgroup P are irradiated (X1 and X2 in MeV);\n    2. For each of the two energies defined in C.2.1<7.11> a.1, the flux in p+ cm-2 s-2."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","D.2.1<7.4>a","Requirement","ECSS-E-ST-20-08_0090974",1,"Created","The SCD-CVG shall include the same provisions as for the visual inspection for qualification tests (in conformance with clause D.2.1<8.1>)."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","D.2.1<8.5>a","Requirement","ECSS-E-ST-20-08_0090982",1,"Created","In conformance with clause 8.7.4, the SCD-CVG shall include a figure showing the nominal values and tolerances of the following mechanical properties:\n    1. dimensions (A: length, B: width);\n    2. weight (average per shipping lot);\n    3. density\n    4. thickness;\n    5. edge parallelism;\n    6. perpendicularity of sides.\n        NOTE This figure can be the same as in clause D.2.1<8.4>."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","D.2.1<8.8>a","Requirement","ECSS-E-ST-20-08_0090985",1,"Created","In conformance with clause 8.7.7, the SCD-CVG shall include the minimum value of the surface resistivity, in W/cm2, and the equipment used to measure the resistivity."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","E.2.1<6>c","Requirement","ECSS-E-ST-20-08_0091000",1,"Created","For contact thickness, in conformance with clause 9.6.8, the SCD-EPD shall include the maximum and minimum values of the contact thickness in mm."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","E.2.1<6>g","Requirement","ECSS-E-ST-20-08_0091004",1,"Created","For diode performance, in conformance with clause 9.4.5.2 the SCD-EPD shall include:\n    1. For the test conditions specified in clause 9.4.5.2.2:\n        (a) the temperature, \n        (b) the forward current level , \n        (c) the reverse voltage level.\n    2. The pass-fail criteria for the test specified in clause 9.4.5.2.3:\n        (a) the maximum absolute value of the forward voltage in V;\n        (b) the reverse current in mA;"]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","E.2.1<7.9>a","Requirement","ECSS-E-ST-20-08_0091013",1,"Created","In conformance with clause 9.6.11, the SCD-EPD shall include:\n    1. the interconnection technique parameter;\n    2. the material and dimension of the interconnectors;\n    3. the value of the pull speed in mm/min and direction (0°, 45° or 90°);\n    4. the value of the ultimate pull strength in N."]
["ECSS-E-ST-20-08C","ECSS - Superseded v1.0","G.2.1a","Requirement","ECSS-E-ST-20-08_0091020",1,"Created","The PVA-DDP of coupons for the delivery review board (DRB) shall include, as a minimum, the following items:\n    1. table of contents;\n    2. certificate of conformance;\n    3. shipping documents;\n    4. configuration item data list (CIDL);\n    5. product manufacturing and control file (PMCF);\n    6. parts, materials and processes (PMP) list;\n    7. list of requests for deviations;\n    8. list of requests for waivers;\n    9. list of nonconformances, including copies of nonconformance reports (NCRs) NRB documentation including failure analysis and failed coupon list;\n    10. history record;\n    11. connector mate and de-mate record;\n    12. serialized components list;\n    13. in-process inspection test results, including positioning in the manufacturing flow chart;\n    14. open work or open test;\n    15. replacement or temporary installation record;\n    16. acceptance and qualification test procedures and test reports;\n    17. assembly drawings and circuit diagram;\n    18. notes and comments;\n    19. operation and maintenance manuals and user restrictions;\n    20. minutes of delivery review board (DRB) meetings;\n    21. lower level data documentation packages (DDPs)."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","4.1.2.4a","Requirement","ECSS-E-ST-50-05_0900003",1,"Created","Frequency bands shall be used in conformance with the direction indicated in Table 4-1. "]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","4.2.1.1.1c","Requirement","ECSS-E-ST-50-05_0900010",1,"Created","Earth station transmitters shall provide the functionality for adjustable RF output power in steps of 3 dB or less. "]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","4.3.1d","Requirement","ECSS-E-ST-50-05_0900023",1,"Created","The information that is supplied in 4.3.1c shall be identified if it is in a preliminary state and is to be confirmed (and finalized) at a later date."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","4.3.2c","Requirement","ECSS-E-ST-50-05_0900028",1,"Created","At this stage, the data supplied as per 4.3.1 shall be the final data."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","5.2.2a","Requirement","ECSS-E-ST-50-05_0900034",1,"Created","The frequency stability of spacecraft receivers shall be within the limits specified in Table 5-4.\n    NOTE For phase lock loop receivers the frequency referred to is the best lock frequency."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","5.5.1.3a","Recommendation","ECSS-E-ST-50-05_0900273",1,"Created","Unwanted emissions falling into the frequency bands of Space Research (deep space) should be kept to power flux spectral density values less than those given in Table 5-9 at the deep space antenna sites.\n    NOTE From Recommendation ITU-R SA.1157-1 and SFCG Recommendation 14-1R1. "]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","5.5.5.3b","Requirement","ECSS-E-ST-50-05_0900057",1,"Created","Since host administrations for Earth stations may specify tighter minimum elevation limits, the minimum elevation angle for transmission shall be agreed with the frequency coordinator."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","6.1.2a","Permission","ECSS-E-ST-50-05_0900274",1,"Created","The following modulating waveforms may be used:\n    1. Telemetry, a subcarrier modulated by PCM data.\n    2. Telemetry, PCM data, SP-L encoded.\n    3. Telecommand, a subcarrier modulated by PCM data.\n    4. Telecommand, PCM data, SP-L encoded.\n    5. Ranging, the appropriate ranging baseband signal.\n        NOTE 1 In the case of simultaneous telecommand, ranging and telemetry, when selecting telecommand and telemetry modulation schemes it is important to take into account their mutual interference. \n        NOTE 2 See also ECSS-E-ST-50-02."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","6.1.3d","Requirement","ECSS-E-ST-50-05_0900066",1,"Created","NRZ waveforms shall only be used when modulated onto a subcarrier."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","6.1.4.2.2c","Requirement","ECSS-E-ST-50-05_0900081",1,"Created","The short-term frequency stability shall be a minimum of ±1 × 10-6, over any time period less than or equal to 100 times the subcarrier’s waveform period."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","6.1.5b","Requirement","ECSS-E-ST-50-05_0900090",1,"Created","To ensure recovery of the symbol clock by the ground demodulators, the maximum string of either ones or zeros shall be limited to 64 symbols."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","6.1.6d","Requirement","ECSS-E-ST-50-05_0900095",1,"Created","Worst case tolerances shall be used to meet clause 6.1.6."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","6.1.10b","Requirement","ECSS-E-ST-50-05_0900101",1,"Created","Phase noise of the unmodulated carrier, integrated between 10 Hz and 100 kHz, shall be less than the following values:\n    1. 2° r.m.s. at UHF (2 025 MHz - 2 110 MHz and 2 200 MHz - 2 290 MHz).\n    2. 4° r.m.s. at SHF (7 190 MHz - 7 235 MHz, and 8 450 MHz - 8 500 MHz)."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","6.2.1c","Requirement","ECSS-E-ST-50-05_0900113",1,"Created","Data signals shall be PCM. "]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","6.2.2e","Recommendation","ECSS-E-ST-50-05_0900278",1,"Created","From a spectrum efficiency point of view, OQPSK should be used instead of QPSK."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","6.2.3.2e","Requirement","ECSS-E-ST-50-05_0900127",1,"Created","The symbol clocks shall be synchronized to within ±2 % of the symbol period or 1 ns, whichever is larger."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","6.2.3.4e","Requirement","ECSS-E-ST-50-05_0900139",1,"Created","The symbol clocks shall be synchronized to within ±2 % of the symbol period or 1 ns, whichever is larger."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","6.2.3.5b","Requirement","ECSS-E-ST-50-05_0900148",1,"Created","For category A applications and for the 8 025 MHz - 8 400 MHz band, a BTS = 0,25 shall be used together with pre-coding where:\nB = one-sided 3-dB bandwidth of the filter;\nTS = symbol duration in accordance with Figure 6-1 and Figure 6-2."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","6.2.3.6a","Requirement","ECSS-E-ST-50-05_0900151",1,"Created","The modulation format shall be as described in 9.2.\n    NOTE The NRZ-L input symbols are encoded differentially and convolutionally by the 4-dimensional 8PSK-TCM modulator."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","6.2.5c","Requirement","ECSS-E-ST-50-05_0900159",1,"Created","The telemetry symbol rate short-term variation shall be less than ±1 × 10-6, over any time period less than or equal to 100 times the symbol duration."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","7.1.3b","Requirement","ECSS-E-ST-50-05_0900178",1,"Created","When the status of the transponder changes between coherent and non-coherent, and the resulting frequency step in the space-Earth link causes a loss of telemetry, a new acquisition of the space-Earth link shall be performed."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","7.2.1d","Requirement","ECSS-E-ST-50-05_0900182",1,"Created","If Doppler compensation is used, then Doppler shift predictions with an error of 5 kHz maximum shall be available at the station.\n    NOTE The centre frequency can be offset from the assigned value to compensate for Doppler shift and, if this information is available, for drift of the transponder local oscillator. "]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","7.2.2e","Requirement","ECSS-E-ST-50-05_0900196",1,"Created","The Earth station shall have capability to support a continuous frequency sweep with the following specifications:\n    1. Sweep rate: 1 Hz/s to 10 kHz/s.\n    2. Sweep range: ±100 Hz to ±300 kHz."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","8.2.2b","Requirement","ECSS-E-ST-50-05_0900201",1,"Created","The document referred in 8.2.2a shall contain all the relevant parameters for any new ground systems to be developed for the project and for the computation of the link budget."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","8.3.2b","Recommendation","ECSS-E-ST-50-05_0900287",1,"Created","For a given set of parameters the link budget should be evaluated for the planned maximum distance of the spacecraft from the Earth for which these parameters are used."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","8.3.2h","Permission","ECSS-E-ST-50-05_0900291",1,"Created","Each project may have its own criteria for acceptability of link performance, using the various margins calculated in the link budget tables."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","9.2.2e","Requirement","ECSS-E-ST-50-05_0900229",1,"Created","The constellation mapper shall deliver 4 parallel symbols coded with three bits to perform 8PSK modulation based on natural mapping (i.e., 0, 1, 2 …, 7 anticlockwise)."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","9.2.5a","Requirement","ECSS-E-ST-50-05_0900234",1,"Created","The constellation mapper for SEF = 2 shall conform to Figure 9-4."]
["ECSS-E-ST-50-05C Rev. 1","ECSS - Superseded v1.0","9.2.6.2a","Recommendation","ECSS-E-ST-50-05_0900299",1,"Created","This type of channel filtering should be used for linear amplifier conditions, or with amplifier linearization, when the symbol rate to central frequency ratio is low. "]
["ECSS-E-ST-32-08C","ECSS - Superseded v1.0","4.2.4b","Requirement","ECSS-E-ST-32-08_0220005",1,"Created","Metallic materials intended for use in corrosive surface environments shall be tested for fracture.\n    NOTE The fracture toughness is a measure of the damage tolerance of a material containing initial flaws or cracks. The fracture toughness in metallic materials is described by the plain strain value of the critical stress intensity factor. The fracture toughness depends on the environment. For fracture control, see ECSS-E-ST-32-01."]
["ECSS-E-ST-32-08C","ECSS - Superseded v1.0","4.2.7c","Requirement","ECSS-E-ST-32-08_0220012",1,"Created","The CTE of composite materials used in high stability structural applications shall be determined by means of dry test coupons under dry test conditions after release of all potential moisture."]
["ECSS-E-ST-32-08C","ECSS - Superseded v1.0","4.3.3a","Requirement","ECSS-E-ST-32-08_0220021",1,"Created","For chemical conversion, ECSS-Q-ST-70-71 clause “Chemical conversion” shall apply."]
["ECSS-E-ST-32-08C","ECSS - Superseded v1.0","4.3.6a","Requirement","ECSS-E-ST-32-08_0220025",1,"Created","The thermal barrier coating shall not spall.\n    NOTE Thermal barrier coatings are used to retard component heating due to high heat fluxes. Thermal barrier coatings are ceramic overlay coatings, where the thickness is approximately 0,4 mm."]
["ECSS-E-ST-32-08C","ECSS - Superseded v1.0","4.5.2a","Requirement","ECSS-E-ST-32-08_0220040",1,"Created","The determination of the allowables for composite materials shall include the following factors:\n    1. The level of control of the manufacturing process.\n        NOTE Composite materials are created at the same time as the finished component, and therefore the control of the manufacturing process has a very strong influence on the final material properties.\n    2. Deviation of lamina properties from the nominal values.\n        NOTE Lamina properties exhibit large differences in directional properties, as well as small strain to failure with limited yielding or plastic behaviour.\n    3. Failure modes in either the fibre, the matrix or the fibre to matrix interface.\n    4. The size of residual strains due to the curing process.\n    5. Effects of combined loading.\n    6. Scatter in compression strength properties.\n    7. Susceptibility to environmental effects.\n        NOTE E.g. humidity, temperature, radiation and cycling loading.\n    8. Dependence of the non-linearity on the specimen, load conditions and test environment."]
["ECSS-E-ST-32-08C","ECSS - Superseded v1.0","4.5.2d","Requirement","ECSS-E-ST-32-08_0220043",1,"Created","The composite material shall be specified, including both qualification and lot control and indicates the test methods and the accept or reject criteria including the minimum acceptable mechanical and physical properties."]
["ECSS-E-ST-32-08C","ECSS - Superseded v1.0","4.6.2a","Requirement","ECSS-E-ST-32-08_0220051",1,"Created","The overall performance characteristics of the laminate shall be predicted using laminated plate theory. "]
["ECSS-E-ST-32-08C","ECSS - Superseded v1.0","4.6.4i","Requirement","ECSS-E-ST-32-08_0220066",1,"Created","The following tests shall be performed as a minimum:\n    1. volume fibre, porosity and ply thickness measurements;\n    2. in the case of thermoset resin matrix: degree of cure and glass transition temperature measurements;\n    3. non-destructive inspection (NDI).\n        NOTE The test methods used are determined in relation to the kind of material to be tested and the property to be measured and can be taken from the standards listed below:\n            · ECSS Standards where available;\n            · EN (European Standards), ASTM, other space agencies or national standards of the member states;\n            · supplier’s procedures or other national standard."]
["ECSS-E-ST-32-08C","ECSS - Superseded v1.0","4.6.5d","Requirement","ECSS-E-ST-32-08_0220070",1,"Created","The customer and supplier shall agree in advance the design of the reference standard and to the procedure for using it.\n    NOTE Most non-destructive inspections rely on a reference standard to define acceptance limits or to estimate flaw sizes."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","5.2.1c","Requirement","ECSS-E-ST-10_0790006",1,"Created","The system engineering organisation shall ensure consistency of the requirements at system level, at lower levels, as well as amongst levels."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","5.2.3.2b","Requirement","ECSS-E-ST-10_0790017",1,"Created","The system engineering organisation shall reflect the consolidated requirements in updates of the specifications."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","5.2.3.7a","Requirement","ECSS-E-ST-10_0790025",1,"Created","In phase 0 the system engineering organisation shall validate the requirements against the expressed needs together with the customer.\n    NOTE For definition of “needs” see ECSS-E-ST-10-06."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","5.3.1c","Requirement","ECSS-E-ST-10_0790031",1,"Created","The system engineering organisation shall document the functional architecture in the design definition file (DDF) in conformance with Annex G."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","5.3.3a","Requirement","ECSS-E-ST-10_0790044",1,"Created","The system engineering organisation shall conduct or consolidate trade-off analyses to:\n    1. assist in selecting system concepts, designs and solutions (including people, parts and materials availability);\n    2. support material selection and process decisions;\n    3. support make-or-buy and supplier selection;\n    4. examine alternative technologies to satisfy functional and design requirements; \n    5. evaluate environmental and cost impacts of materials and processes;\n    6. evaluate alternative physical architectures to select preferred products and processes;\n    7. establish the system and its configuration items;\n    8. analyze planning critical paths and propose alternatives;\n    9. select standard components, techniques, services and facilities that reduce system life-cycle cost;\n    10. establish model and product verification philosophy for achieving qualification and acceptance objectives while considering testability;\n    11. assess design capacity to evolve."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","5.3.4c","Requirement","ECSS-E-ST-10_0790049",1,"Created","The system engineering organisation shall ensure that analysis tools are maintained."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","5.4.1.1a","Requirement","ECSS-E-ST-10_0790055",1,"Created","The system engineering organisation shall establish a design of the system from its functional architecture, requirement allocation, and technology selection.\n    NOTE This includes definition of the interfaces and corresponding ICDs."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","5.4.1.3a","Requirement","ECSS-E-ST-10_0790064",1,"Created","The system engineering organisation shall define the design methods, tools and related models to be used during the product life cycle and document them in the SEP."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","5.4.2.3b","Requirement","ECSS-E-ST-10_0790078",1,"Created","The system engineering organisation shall document the hierarchy and assembly sequence of the system elements with the physical architecture."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","5.5.2d","Requirement","ECSS-E-ST-10_0790083",1,"Created","The system engineering organisation shall confirm that all product verification objectives are achieved by analysing the results of the verification activities. \n    NOTE This includes analysis of Verification Control Document and its closeout documents, as defined in ECSS-E-ST-10-02 Annex B."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","5.6.1b","Requirement","ECSS-E-ST-10_0790087",1,"Created","The system engineering organization shall set up the system engineering organization and interfaces in accordance with the system engineering plan.\n    NOTE For example: to customer, to lower levels, management, product assurance, production, operations and logistics."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","5.6.6b","Requirement","ECSS-E-ST-10_0790102",1,"Created","The system engineering organization shall define the margin policy as applicable to the maturity level of the product.\n    NOTE Details are provided in the system engineering plan in D<4.2>b.5."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","5.6.9c","Requirement","ECSS-E-ST-10_0790111",1,"Created","The system engineering organization shall implement and control agreed actions.\n    NOTE 1 Change is related to a request for deviation.\n    NOTE 2 Nonconformance is related to a request for waiver.\n    NOTE 3 The change procedure/control is defined as part of the configuration management as defined in ECSS-M-ST-40."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","6.2e","Requirement","ECSS-E-ST-10_0790116",1,"Created","The system engineering organisation shall ensure that for critical elements which are not at the next lower level, the technical requirements specification, the design definition file and the design justification file are available early in the project to control the project risk.\n    NOTE Information regarding the expected delivery of system engineering documents for each project review is provided in Annex A.\nThe documents to be approved by the customer as well as the time of their approval are listed in the business agreement."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","6.4c","Requirement","ECSS-E-ST-10_0790122",1,"Created","The system engineering organization shall support the PRR and ensure implementation of PRR actions."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","6.8c","Requirement","ECSS-E-ST-10_0790134",1,"Created","The system engineering organization shall support the FRR, ORR, LRR, CRR, ELR, and recurring products AR, and ensure implementation of the actions of those reviews."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","B.2.1<4>a","Requirement","ECSS-E-ST-10_0790141",1,"Created","The MDD shall provide:\n    1. Overview of the concept\n    2. Mission analysis\n    3. System description, element by element\n        NOTE For example: For a spacecraft, its ground control segment, and a user segment, e.g.\n        Space Segment \n            · Payload \n            · Platform \n            · Launch Vehicle \n            · Orbit related aspects\n            · On-Board Data Handling \n            · Reference Operation Scenarios / Observation characteristics\n            · Operability / Autonomy Requirements \n        Ground Segment \n            · Functional Requirements and Major Elements \n            · Monitoring and Control Segment \n            · Data Processing Segment \n        User segment\n            · Functional Requirements and Major Elements \n            · Monitoring requirements "]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","D.2.1<3.1>a","Requirement","ECSS-E-ST-10_0790152",1,"Created","The SEP shall contain the following description of:\n    1. The project objective and the main elements that characterize the user’s need.\n    2. The objective of the system or product as established by the TS (as defined in the ECSS-E-ST-10-06 Annex A).\n    3. The main elements of the system architecture (i.e. first level elements of the architecture adopted for the system and identification of their reuse constraints).\n    4. The principal characteristics of the project lifecycle and the incremental development of the system (e.g. successive versions, progressive implementation of system functions).\n    5. The main elements supporting the project lifecycle (e.g. ground support equipments, and facilities).\n    6. The organizational constraints impacting system engineering activities (e.g. the external and internal industrial organization (e.g. contractors, partners, suppliers, own company) constraints).\n    7. The list of the critical issues identified at the beginning of the project phase(s).\n    8. The list of national and international regulations.\n    9. The capacity for verification and validation of the product, taking into account the means available, e.g. for tests, analysis, or simulation."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","D.2.1<4.1>c","Requirement","ECSS-E-ST-10_0790160",1,"Created","The SEP shall list the internal means and facilities (e.g. equipment, software, and premises) made available by the organization in charge of the development of the system or product."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","D.2.1<5.1.1>a","Requirement","ECSS-E-ST-10_0790169",1,"Created","The SEP shall describe the system engineering process tailored to the specifics of the considered project, and identify all the system engineering tasks to be implemented from the starting conditions (e.g. kick-off) to the closing event (e.g. review), their relationship, and their interfaces with other actors of the project, and identify and describe any existing iteration within the process.\n    NOTE Details are provided in ECSS-E-HB-10 “System engineering guidelines”."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","D.2.1<5.1.2>b","Requirement","ECSS-E-ST-10_0790172",1,"Created","The SEP shall define the process and control to be put in place to meet requirements for the thermal, structures, mechanisms, environmental control and life support, propulsion, pyrotechnics, mechanical parts, and materials functions and interfaces.\n    NOTE These requirements refer to Mechanical engineering as defined in ECSS-E-ST-3x series of standards."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","D.2.1<5.1.2>j","Requirement","ECSS-E-ST-10_0790180",1,"Created","The SEP shall define the process and control to be put in place to meet requirements for ground and in-orbit logistics and maintenance, addressing, amongst others, technical activities, related engineering standards, methods and analyses to be performed to ensure that the development of space systems (i.e. manned and unmanned) properly takes into account and integrates the supportability and support aspects for the whole life cycle."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","D.2.1<6>a","Requirement","ECSS-E-ST-10_0790190",1,"Created","The SEP shall introduce the system engineering activities, to be conducted during subsequent phase(s) of the project, and as a minimum, list any identified critical issue and risk to be mitigated during the subsequent phase(s)."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","E.2.1<4.3>d","Requirement","ECSS-E-ST-10_0790199",1,"Created","The TP shall identify technical milestones, showing their interactions and relationships with the SEP milestones."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","G.2.1<2>a","Requirement","ECSS-E-ST-10_0790213",1,"Created","The DDF shall contain the list of applicable and reference documents, used in support to the generation of the document. "]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","G.2.1<3>c","Requirement","ECSS-E-ST-10_0790218",1,"Created","The DDF of a system shall contain at least the technical requirements specifications of the elements in which the system is broken down "]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","G.2.1<5.4>b","Requirement","ECSS-E-ST-10_0790227",1,"Created","The DDF shall reference any documentation containing detailed technical descriptions and associated matrices to ensure overall consistency and completeness."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","G.2.1<7.3>a","Requirement","ECSS-E-ST-10_0790233",1,"Created","The DDF shall present the constraints induced by the system or product design definition on the transportation activities and during the periods of storage of the product e.g. allowable envelopes, restrictions on transportation and storage, exclusion zones, packaging, shock levels, temperature environments, humidity, cleanliness, regulations, and dangerous materials."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","I.2.1<4>a","Requirement","ECSS-E-ST-10_0790246",1,"Created","For each key engineering parameter, the technical budget shall:\n    1. provide the specified value of the parameter,\n    2. provide the supplier’s margin resulting of the allocation of the parameter to the lower level products,\n    3. provide the specified values with the reference to the relevant technical requirement of the lower level products, \n    4. propose a specific program to conform to the specified value in case of nonconformance,\n    5. contain a chart of parameter history that presents the evolution of the parameter’s value at the different design maturity steps for which the evaluation of the parameter is performed,\n    6. list the documentation sources (e.g. analysis report and verification report)."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","J.2.1<4>a","Requirement","ECSS-E-ST-10_0790251",1,"Created","The specification tree document shall provide the complete list of specifications defining the system or product, and contain a graphical representation where the system or product specification (i.e. at the top level of the tree) is decomposed into lower level product specifications."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","K.2.1<2>c","Requirement","ECSS-E-ST-10_0790257",1,"Created","The reference document list shall contain the reference to:\n    1. Trade-Off-Reports, as defined Annex L.\n    2. Analysis Reports (e.g. requirements allocation analysis, functional analysis).\n    3. Requirements Traceability Matrix, as defined in Annex N (with link to analysis).\n    4. Verification Control Document \n    5. All verification documentation, such as:\n        (a) Analysis Reports (e.g. reports w.r.t. qualification aspects)\n        (b) Test Reports\n        (c) ROD Reports\n        (d) Inspection Reports\n        (e) Verification Reports"]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","K.2.1<7>c","Requirement","ECSS-E-ST-10_0790269",1,"Created","The DJF shall include the status of DJF of lower level products.\n    NOTE Activities related to verification are dealt with in section K.2.1<8>."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","K.2.1<8.2.3>a","Requirement","ECSS-E-ST-10_0790276",1,"Created","The DJF shall contain all evidence (e.g. analyses, test results, and model descriptions and correlations) regarding the suitability and validation of all models used for the analysis of the system."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","K.2.1<10.4>a","Requirement","ECSS-E-ST-10_0790285",1,"Created","The DJF shall present the justification of constraints induced by the system or product design definition on the maintenance activities and procedures e.g. operational allowable envelopes, accessibility, tooling, support materials, parts availability, and deliveries. "]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","L.2.1<2>a","Requirement","ECSS-E-ST-10_0790289",1,"Created","The trade-off report shall list the applicable and reference documents in support to the generation of the document and include the reference to the following applicable documents:\n    1. Mission description document, if relevant\n    2. Technical requirements specification\n    3. System engineering plan\n    4. Project phasing and planning requirement document."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","L.2.1<10>b","Requirement","ECSS-E-ST-10_0790304",1,"Created","The trade-off report shall present the identified technical and programmatic risks induced by the choice of the recommended solution, and any additional activity necessary to be performed for risk mitigation."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","M.2.1<2>b","Requirement","ECSS-E-ST-10_0790307",1,"Created","The IRD shall include the following references:\n    1. Product tree (as defined in ECSS-M-ST-10 Annex B)\n    2. Specification tree (as defined in ECSS-E-ST-10 Annex J)."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","N.2.1<3>a","Requirement","ECSS-E-ST-10_0790315",1,"Created","The RTM shall list all the technical requirement of the product TS."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","O.2.1<4>a","Requirement","ECSS-E-ST-10_0790325",1,"Created","The RJF shall present and justify the life profile situations for the concept presented in the technical requirements specification.\n    NOTE For justification, reference can be made to the system concept report of the considered project where relevant."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","P.2.1<3.1>a","Requirement","ECSS-E-ST-10_0790334",1,"Created","The PUM shall provide a general description of the expected functions of the product during its lifetime in expected operational context and environment."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","P.2.1<4.6>a","Requirement","ECSS-E-ST-10_0790343",1,"Created","The PUM shall describe the conditions and procedures for the handling of the product, be it integrated or stand-alone."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","P.2.1<4.9.3>c","Requirement","ECSS-E-ST-10_0790354",1,"Created","Appropriate cross-reference shall be made to product constituent modes and procedures."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","P.2.1<5.2>a","Requirement","ECSS-E-ST-10_0790362",1,"Created","The PUM shall describe the product constituent including:\n    1. the overall functions of the product constituent and the definition of its operational modes during the different mission phases;\n    2. description of any product constituent management functions, fault management concept and redundancy provisions;\n    3. a summary description of the component units/equipment and software including the functions which each supports;\n    4. product constituent functional block diagrams and a diagram showing the source of telemetry outputs and the sink of telecommand inputs;\n    5. interfaces;\n    6. budgets."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","P.2.1<5.6>c","Requirement","ECSS-E-ST-10_0790372",1,"Created","Each telecommand shall have a functional description with utilization conditions (e.g. pre-transmission validity, criticality level), command parameters (syntax and semantics) and execution verification in telemetry."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","P.2.1<5.9>a","Requirement","ECSS-E-ST-10_0790381",1,"Created","For each operational mode of the product constituent, sensor output data, conditions under which they are generated, their contents, and data rate shall be described."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","Q.2.1<2>a","Requirement","ECSS-E-ST-10_0790386",1,"Created","The analysis report shall list the applicable and reference documents in support to the generation of the document, and make a clear reference to the configuration baseline of the product considered for the analysis."]
["ECSS-E-ST-10C","ECSS - Superseded v1.0","Q.2.1<8>a","Requirement","ECSS-E-ST-10_0790392",1,"Created","The analysis report shall:\n    1. summarize the analysis results,\n    2. summarize the conditions of validity of this analysis, \n    3. clearly state and describe any open issue."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","5.1.2f","Requirement","ECSS-E-ST-31-02_1190010",1,"Created","The technical requirements shall not be in conflict with other requirements contained in business agreement documents."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","5.1.3f","Requirement","ECSS-E-ST-31-02_1190019",1,"Created","A technical requirement shall be verifiable using one or more approved verification methods."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","5.3.1a","Requirement","ECSS-E-ST-31-02_1190027",1,"Created","The qualification stage shall be completed before launch."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","5.3.2d","Requirement","ECSS-E-ST-31-02_1190031",1,"Created","Calibration of laboratory equipment shall be verified prior to their use."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","5.5.3.2b","Requirement","ECSS-E-ST-31-02_1190048",1,"Created","All safety critical functions shall be verified by test."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","5.5.3.3.2b","Requirement","ECSS-E-ST-31-02_1190057",1,"Created","Qualification by similarity shall not be performed on a product that has been previously qualified by similarity."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","5.5.4.1a","Requirement","ECSS-E-ST-31-02_1190062",1,"Created","Equipment for which a full qualification programme is required as per Table 5-1 shall be qualified by test according to clause 5.5.3.2 and 5.6 and by analysis according to clause 5.5.3.3."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","5.5.5.2b","Requirement","ECSS-E-ST-31-02_1190068",1,"Created","For VCHP, the following specific performance characteristics shall be determined and verified against specified data:\n    1. The characteristics specified in 5.5.5.2a,\n    2. Maximum transport capability in fully-on conditions,\n    3. Heat leak from condenser to evaporator in off-mode,\n    4. Thermal resistance between condenser and reservoir,\n    5. Ability to regulate the evaporator temperature with passive and active methods.\n        ","NOTE Passive methods include devices with non-heated gas reservoirs, active methods include devices with heated/cooled gas reservoirs."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","5.6.3.2.2a","Requirement","ECSS-E-ST-31-02_1190083",1,"Created","The accuracy of test instrumentation shall be verified in accordance with approved calibration procedures."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","5.6.5a","Requirement","ECSS-E-ST-31-02_1190090",1,"Created","Proof pressure test shall be performed applying 1,5 times MDP as specified in ECSS-E-ST-32-02 for duration of 15 minutes.\n    ","NOTE During manufacturing processes (e.g. curing of panels with embedded heat pipes) the pressure can be higher than MDP, as long as the unit material stays in the elastic domain."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","5.6.7g","Requirement","ECSS-E-ST-31-02_1190101",1,"Created","If burst pressure tests are performed at sub-unit level, the burst pressure test processes shall include all parts of the product including all joints, welds, end fittings.\n    ","NOTE For example, if it is performed at the level of the evaporator or reservoir of a TPL."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","5.6.9.1d","Requirement","ECSS-E-ST-31-02_1190109",1,"Created","When establishing the maximum heat transport capability, the vapour temperature shall be varied in increments within the specified operational temperature range such that a performance over temperature curve is generated."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","5.6.9.2.2b","Requirement","ECSS-E-ST-31-02_1190118",1,"Created","Measurement shall be performed at sufficient tilt intervals as to create a smooth curve of performance over tilt height."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","5.6.9.2.4a","Requirement","ECSS-E-ST-31-02_1190121",1,"Created","After a full depriming (emptying the capillary structure), a start-up procedure shall be determined."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","5.6.10.1b","Requirement","ECSS-E-ST-31-02_1190129",1,"Created","Sinusoidal, random vibration and shock tests shall be performed on component level in order to verify critical details of the device.\n    ","NOTE A deflection test to replace sinusoidal and random testing can be agreed with the customer. For example: TPHTE with capillary structures, which have an inherent characteristic to be damaged by mechanical loads."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","5.6.12c","Requirement","ECSS-E-ST-31-02_1190142",1,"Created","Aging tests shall be performed in the functional test sequence as given in Figure 5-2 with a duration of 300 hours."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","5.6.14.2a","Requirement","ECSS-E-ST-31-02_1190151",1,"Created","CCHP shall be tested according to requirements 5.6.9.2.1a.1, 5.6.9.2.1a.2, 5.6.9.2.1a.3 and 5.6.9.2.1a.4 for one selected configuration."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","5.8a","Requirement","ECSS-E-ST-31-02_1190159",1,"Created","When TPHTE hardware is put into storage they shall be protected against:\n    1. exposure to adverse environments that can cause corrosion or degrade the material;\n    2. mechanical damages."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","A.2.1<3>b","Requirement","ECSS-E-ST-31-02_1190170",1,"Created","The TS shall put the product into perspective with other related products. "]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","B.2.1<1>b","Requirement","ECSS-E-ST-31-02_1190178",1,"Created","Open issues, assumptions and constraints relevant to this document shall be stated and described."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","B.2.1<9>a","Requirement","ECSS-E-ST-31-02_1190187",1,"Created","The VP shall describe high level definitions of the verification tools to be used, such as S/W facilities, special tools, simulators, analytical tools."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","C.2.1<2>a","Requirement","ECSS-E-ST-31-02_1190195",1,"Created","The RRPT shall list the applicable and reference documents in support to the generation of the document."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","D.2.1<4>a","Requirement","ECSS-E-ST-31-02_1190204",1,"Created","The IRPT shall describe the product configuration data of the inspected item."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","D.2.1<5>b","Requirement","ECSS-E-ST-31-02_1190206",1,"Created","Open issues shall be clearly stated and described."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","E.2.1<9>b","Requirement","ECSS-E-ST-31-02_1190218",1,"Created","In the TSPE, the error budgets and the confidence levels to be applied, including tolerance, shall be specified."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","F.2.1<4>a","Requirement","ECSS-E-ST-31-02_1190225",1,"Created","The TPRO shall provide a mapping matrix to the TSPE giving traceability towards the test requirement."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","F.2.1<12>a","Requirement","ECSS-E-ST-31-02_1190234",1,"Created","The TPRO shall list the allocation of responsibilities and resources."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","F.2.1<14>a","Requirement","ECSS-E-ST-31-02_1190238",1,"Created","The TPRO shall provide detailed instructions, including expected results, with tolerances, pass/fail criteria, and identification of specific steps to be witnessed by QA personnel."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","H.2.1<1>b","Requirement","ECSS-E-ST-31-02_1190252",1,"Created","Open issues, assumptions and constraints relevant to this document shall be stated and described."]
["ECSS-E-ST-31-02C","ECSS - Superseded v1.0","H.2.1<4>a","Requirement","ECSS-E-ST-31-02_1190255",1,"Created","The VRPT shall describe the verification approach, the associated problems and results with reference to the relevant test, analysis, review-of-design and inspection reports."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.2.4.1.2a","Requirement","ECSS-E-ST-33-01_0820004",1,"Created","Marking shall be applied on non-functional surfaces."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.2.5.1b","Requirement","ECSS-E-ST-33-01_0820014",1,"Created","For non-critical mechanisms, conformance to the reliability figure shall be demonstrated by simplified methods (e.g. parts count or other methods accepted by the customer).\n    NOTE The methods to achieve by design, derive by analysis, and demonstrate by test the specified reliability figures are presented in ECSS-Q-ST-30."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.2.5.2f","Requirement","ECSS-E-ST-33-01_0820023",1,"Created","Unless redundancy is achieved by the provision of a complete redundant mechanism, active elements of mechanisms, such as sensors, motor windings, brushes, actuators, switches and electronics, shall be redundant."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.4.2d","Requirement","ECSS-E-ST-33-01_0820032",1,"Created","The movement of each part shall ensure that there is no mechanical interference with any other part of the mechanism, the spacecraft, the payload or the launcher."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.5.2.6c","Requirement","ECSS-E-ST-33-01_0820043",1,"Created","In manned space systems, flammable, toxic and unstable materials shall not be used."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.5.3b","Requirement","ECSS-E-ST-33-01_0820051",1,"Created","If operational constraints are imposed by the mechanism, they shall be identified, justified and approved by the customer."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.7.3.1d","Requirement","ECSS-E-ST-33-01_0820061",1,"Created","The use of sliding surfaces shall be avoided. "]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.7.3.2c","Requirement","ECSS-E-ST-33-01_0820070",1,"Created","The dry lubricant application process shall be verified with respect to lubricant performance and repeatability."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.7.3.4.1a","Requirement","ECSS-E-ST-33-01_0820079",1,"Created","The life of tribological components shall be verified under worst case ground and flight conditions."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.7.3.4.2b","Requirement","ECSS-E-ST-33-01_0820081",1,"Created","The calculation specified in requirement 4.7.3.4.2a shall be made available to the customer."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.7.4.1a","Requirement","ECSS-E-ST-33-01_0820090",1,"Created","The mechanism engineering shall conform to the thermal engineering requirements specified by the customer.\n    NOTE For thermal control, see ECSS-E-ST-31."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.7.5.1a","Requirement","ECSS-E-ST-33-01_0820099",1,"Created","Mechanisms shall be designed to meet the mechanical performance requirements and to withstand the specified environment during handling, transportation, testing, storage, launch and operation in orbit for the specified lifetime."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.7.5.2.5d","Requirement","ECSS-E-ST-33-01_0820109",1,"Created","The margin of safety (MOS) shall be derived from stresses or load."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.7.5.2.6e","Requirement","ECSS-E-ST-33-01_0820117",1,"Created","The following specific factors of safety shall apply:\n    1. For cables, stress factor of safety against rupture   3\n    2. For stops, shaft shoulders and recesses, against yield  2"]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.7.5.3.2e","Requirement","ECSS-E-ST-33-01_0820128",1,"Created","When the actuation torque (or force) is supplied by a spring actuator, the actuation torque (or force) supplied by the spring, shall be derived considering worst-case conditions, and be multiplied by the maximum uncertainty factor of 0,8."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.7.5.4.3a","Requirement","ECSS-E-ST-33-01_0820137",1,"Created","Latching mechanisms used to assure positive locking shall be designed to avoid inadvertent opening by vibration or shock occurring during the mission."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.7.5.4.4a","Requirement","ECSS-E-ST-33-01_0820146",1,"Created","Mechanisms with restricted travel or rotation shall be provided with regular or emergency mechanical end stops to limit their motion and travel extremes to the maximum position specified in the SMS."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.7.5.4.4c","Requirement","ECSS-E-ST-33-01_0820148",1,"Created","The mechanical end stops and arresting mechanisms shall be designed to withstand without damage the maximum shock loads with the structural margins defined in clause 4.7.5.4.5. "]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.7.5.4.5g","Requirement","ECSS-E-ST-33-01_0820160",1,"Created","Except for gears and ball or journal bearings, and unless one surface is a self-lubricating material, when metallic material mating or separating surfaces subject to relative motion are used, they shall\n    1. have a minimum hardness of 500 HV, and \n    2. either:\n        (a) be composed of dissimilar material, or \n        (b) at least one of the two surfaces have a dissimilar coating. \n            NOTE 1 Example of self-lubrificating material is bronze.\n            NOTE 2 Examples of dissimilar coatings are nitride, carbide or oxide. \n            NOTE 3 The use of bonded or sputtered MoS2 or polymeric materials is not excluded."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.7.5.4.8c","Requirement","ECSS-E-ST-33-01_0820167",1,"Created","Clearances shall be verified by inspection. "]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.7.5.4.12c","Requirement","ECSS-E-ST-33-01_0820178",1,"Created","The conformity of the design, material and manufacture of elements to be cut used in release and locking devices to the reliability requirements specified in the SMS shall be verified by test.\n    NOTE Example of such elements are bolts, rods and cables."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.7.7.1.1c","Requirement","ECSS-E-ST-33-01_0820186",1,"Created","Electrical power consumption, generation and thermal dissipation shall be quantified by design."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.7.7.3a","Requirement","ECSS-E-ST-33-01_0820195",1,"Created","Electrical wires shall be designed to withstand a high voltage of 500 V AC (50 Hz) applied between each other or between wires and the structure without causing disruptive discharges."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.7.7.4b","Requirement","ECSS-E-ST-33-01_0820198",1,"Created","If electronic or electrical components are mounted internally to or externally on the mechanism a ground bonding strap shall be used between the mechanism housing and the mounting ground plane."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.7.7.5d","Requirement","ECSS-E-ST-33-01_0820206",1,"Created","Electrical connectors shall be redundant."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.7.8.1b","Requirement","ECSS-E-ST-33-01_0820216",1,"Created","Non-linear control systems stability margin value and assessment method shall be agreed by the customer."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.7.8.7a","Requirement","ECSS-E-ST-33-01_0820225",1,"Created","The control system shall be compatible with the specified maximum angular and linear rates and accelerations of the spacecraft."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.8.2.1a","Requirement","ECSS-E-ST-33-01_0820234",1,"Created","The mechanisms parts, components and assembly analytical verification shall include the analysis specified in 4.8.2.2 to 4.8.2.19."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.8.2.6.2b","Requirement","ECSS-E-ST-33-01_0820244",1,"Created","The model specified in requirement 4.8.2.6.2a shall be such that the following can be performed:\n    1. a parametric study of all the mechanical variables, and\n    2. an update of input parameters during the design and test phase. "]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.8.2.8a","Requirement","ECSS-E-ST-33-01_0820253",1,"Created","Conformance of mechanisms to specified requirements on functional dimensioning shall be verified by analysis.\n    NOTE Example of such requirements are torque, force, and kinematics."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.8.2.13d","Requirement","ECSS-E-ST-33-01_0820263",1,"Created","Non-linearities such as backlash, dead zones, friction, saturation of drive electronics shall be characterized and taken into account in the control system analysis. "]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.8.2.16a","Requirement","ECSS-E-ST-33-01_0820272",1,"Created","The design compatibility with the hygroscopic environment during the complete lifetime shall be verified by analysis.\n    NOTE The hygroscopic environment is mainly relevant on-ground."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.8.3.1f","Requirement","ECSS-E-ST-33-01_0820281",1,"Created","The mechanism shall be subjected to a thermal verification."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.8.3.1h","Requirement","ECSS-E-ST-33-01_0820283",1,"Created","Non-linearities shall be measured in order to characterize the dynamic behaviour of the mechanism.\n    NOTE Examples of non-linearities are hysteresis and backlash."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.8.3.3.3a","Requirement","ECSS-E-ST-33-01_0820290",1,"Created","A thermal qualification of the mechanism shall be performed."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.8.3.3.8b","Requirement","ECSS-E-ST-33-01_0820302",1,"Created","ESD testing shall be performed on a complete mechanism including all electrical components and thermal hardware.\n    NOTE For EMC and ESD see ECSS-E-ST-20."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.8.3.3.11b","Requirement","ECSS-E-ST-33-01_0820311",1,"Created","Exposure of lifetime model to vibrations prior to life test shall include:\n    1. exposure to accumulated durations of acceptance tests at acceptance load level and accumulated durations corresponding to the number of vibrations tests expected by the flight hardware, and \n    2. one time exposure to qualification load level and duration of vibration."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.8.3.3.14d","Requirement","ECSS-E-ST-33-01_0820319",1,"Created","In order to determine the lifetime to be demonstrated by test, an accumulation of cycles multiplied by their individual factors shall be used.\n    NOTE  Table 4-4 presents two case examples to calculate the number of cycles to be used in the test."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.8.3.4.4a","Requirement","ECSS-E-ST-33-01_0820330",1,"Created","Acceptance testing shall be considered successful when all the following criteria are met:\n    1. The peak torque or force, resulting from the summation of the following, comply with the functional dimensioning requirements specified in clause 4.7.5.3: \n        (a) the worst-case variation or degradation of the peak torque or force measured on the qualification model overall throughout life testing, and\n        (b) the worst case force or torque measured on the flight unit.\n    2. Deterioration torque or force performance throughout acceptance tests is less than the values measured on the qualification model.\n    3. All measured performances conform to the specific mechanism specification (SMS)."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","4.9.3a","Requirement","ECSS-E-ST-33-01_0820333",1,"Created","The assembly of mechanisms shall be performed in a clean environment specified by the customer."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","A.2.1<3>a","Requirement","ECSS-E-ST-33-01_0820341",1,"Created","The SMS shall specify or refer to the qualification procedure for parts and components.\n    NOTE See 4.2.4.2a."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","A.2.1<6>a","Requirement","ECSS-E-ST-33-01_0820351",1,"Created","The SMS shall list the handling, storage and operational requirements for all lubricated components."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","A.2.1<7>b","Requirement","ECSS-E-ST-33-01_0820360",1,"Created","The SMS shall list the limited-life components lifetime requirements.\n    NOTE See 4.8.2.15b."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","B.2.1<5>a","Requirement","ECSS-E-ST-33-01_0820369",1,"Created","The MDD shall describe the mechanism detailed design, including the following:\n    1. product tree (sub assembly break down);\n    2. physical design of the mechanism in all configurations;\n    3. how each function is achieved;\n    4. protection and redundancy implementation;\n    5. general assembly drawings with cross sections or equivalent;\n    6. interface descriptions (mechanical, thermal and electrical);\n    7. static and dynamic envelopes."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","D.2.1<1>c","Requirement","ECSS-E-ST-33-01_0820380",1,"Created","The user manual shall include any additional definitions, abbreviations or symbols used."]
["ECSS-E-ST-33-01C","ECSS - Superseded v1.0","D.2.1<7>a","Requirement","ECSS-E-ST-33-01_0820388",1,"Created","The user manual shall provide the following information with regards to interfaces definition:\n    1. description of mechanical and thermal interfaces (including the list of applicable mechanical and thermal ICD);\n    2. description of electrical interfaces (including the list of applicable electrical ICD);\n    3. description of optical interfaces (including the list of applicable optical ICD).\n        NOTE In case the ICDs are provided in a specific chapter of the EIDP, the list of applicable ICDs can be limited to the EIDP chapter reference. "]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","5.2.1d","Requirement","ECSS-E-ST-10-02_0740005",1,"Created","The verification approach shall be defined by the supplier in the Verification Plan (VP) for approval by the customer prior to implementation."]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","5.2.2.2c","Requirement","ECSS-E-ST-10-02_0740014",1,"Created","When the test objectives include the demonstration of qualitative operational performance, the execution shall be observed and results recorded."]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","5.2.2.3e","Requirement","ECSS-E-ST-10-02_0740023",1,"Created","An analysis programme shall be defined in the Verification Plan (VP)."]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","5.2.2.4a","Requirement","ECSS-E-ST-10-02_0740025",1,"Created","Verification by Review-of design (ROD) shall consist of using approved records or evidence that unambiguously show that the requirement is met.\n    NOTE Examples of such approved records are design documents and reports, technical descriptions, and engineering drawings."]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","5.2.4.1b","Requirement","ECSS-E-ST-10-02_0740034",1,"Created","Qualification, acceptance and pre-launch stages shall be completed before launch."]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","5.2.4.3.2b","Requirement","ECSS-E-ST-10-02_0740043",1,"Created","The acceptance article shall perform as the qualified product."]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","5.2.5a","Requirement","ECSS-E-ST-10-02_0740053",1,"Created","The model philosophy shall be defined as part of the overall verification planning."]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","5.2.6.2d","Requirement","ECSS-E-ST-10-02_0740061",1,"Created","Ground support equipment (GSE) that is modified or used in a new application shall be re-verified or re-validated."]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","5.2.7e","Requirement","ECSS-E-ST-10-02_0740072",1,"Created","Verification execution and reporting shall be incrementally carried out through the project life cycle starting from phase C."]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","5.3.1a","Requirement","ECSS-E-ST-10-02_0740081",1,"Created","The supplier shall assign clear responsibility for the implementation of the verification programme."]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","5.3.2.2b","Requirement","ECSS-E-ST-10-02_0740090",1,"Created","The Analysis report (ARPT) shall be in conformance with the DRD in Annex Q of ECSS-E-ST-10."]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","5.3.2.2d","Requirement","ECSS-E-ST-10-02_0740092",1,"Created","An Analysis report (APRT) shall be provided for each Analysis verification task identified in the VP."]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","5.3.2.4c","Requirement","ECSS-E-ST-10-02_0740099",1,"Created","The supplier shall provide an Inspection report (IRPT) for the reviews as agreed with the customer\n    NOTE Guidelines are provided in Annex G."]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","5.4.1b","Requirement","ECSS-E-ST-10-02_0740111",1,"Created","The verification process control shall be supported by a computer based verification database."]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","5.4.2d","Requirement","ECSS-E-ST-10-02_0740117",1,"Created","The Verification Control Board (VCB) shall assess the verification status with a periodicity agreed with the customer, along the project life cycle.\n    NOTE The results of the VCB are at least presented on the occasions of project reviews as defined in ECSS-M-ST-10."]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","A.2.1<3>a","Requirement","ECSS-E-ST-10-02_0740130",1,"Created","The VP shall list the applicable dictionary or glossary and the meaning of specific terms or abbreviations utilized in the document."]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","A.2.1<10>a","Requirement","ECSS-E-ST-10-02_0740139",1,"Created","The VP shall describe the proposed methodology to be utilized for verification monitoring and control including the use of a verification data base."]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","B.2.1<1>b","Requirement","ECSS-E-ST-10-02_0740146",1,"Created","Open issues, assumptions and constraints relevant to this document shall be stated and described."]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","B.2.1<4>a","Requirement","ECSS-E-ST-10-02_0740150",1,"Created","The VCD shall describe the verification control approach applied to the product, the involved documentation and the computerized tool used to support the process."]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","C.2.1<4>b","Requirement","ECSS-E-ST-10-02_0740160",1,"Created","The TRPT shall contain the analysis of test data and the relevant assessment."]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","D.2.1<3>a","Requirement","ECSS-E-ST-10-02_0740169",1,"Created","The RRPT shall list the applicable dictionary or glossary and the meaning of specific terms or abbreviations utilized in the document with the relevant meaning."]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","E.2.1<5>a","Requirement","ECSS-E-ST-10-02_0740178",1,"Created","The IRPT shall summarize the: \n    1. inspection results, including:\n        (a) the list of the requirements to be verified (in correlation with the VCD), \n        (b) traceability to used documentation, \n        (c) inspection event location and date, \n        (d) expected finding, \n        (e) conformance or deviation including proper references and signature and date, \n    2. comparison with the requirements, and \n    3. verification close-out judgement. "]
["ECSS-E-ST-10-02C","ECSS - Superseded v1.0","F.2.1<5>c","Requirement","ECSS-E-ST-10-02_0740188",1,"Created","Open issues shall be clearly stated and described."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.2.2a","Requirement","ECSS-E-ST-33-11_0280009",1,"Created","The explosive system shall achieve the specified properties within defined levels of reliability and confidence agreed with the customer. \n    NOTE 1 All components are contributors. \n    NOTE 2 This standard specifies the properties of particular concern."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.2.3d","Requirement","ECSS-E-ST-33-11_0280019",1,"Created","The basis of the time shall be specified and justified."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.2.5.3a","Requirement","ECSS-E-ST-33-11_0280028",1,"Created","For phases A and B of the component, the methodology for dimensioning explosive devices shall be justified."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.3b","Requirement","ECSS-E-ST-33-11_0280037",1,"Created","The environmental conditions, life cycle and the functions being activated shall be specified.\n    NOTE E.g. ground storage, transport, launcher ignition, staging and safety functions, payload separation, motor ignition, solar array, antenna, boom or cover release, propulsion system branch opening or closing, de-orbiting."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.4a","Requirement","ECSS-E-ST-33-11_0280039",1,"Created","The timing of each function of the explosive system shall be specified."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.4h","Requirement","ECSS-E-ST-33-11_0280046",1,"Created","Explosive systems shall be two fault tolerant, if premature initiation causes a catastrophic failure."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.5.2.1f","Requirement","ECSS-E-ST-33-11_0280058",1,"Created","Stray circuits or coupling which can result in unintentional firing shall be avoided."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.5.2.3e","Requirement","ECSS-E-ST-33-11_0280067",1,"Created","It shall revert to its initial state after the fire command within an interval agreed with the customer."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.5.2.5d","Requirement","ECSS-E-ST-33-11_0280075",1,"Created","The fire function shall revert to its initial state after the firing command within an interval agreed with the customer."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.7.3a","Requirement","ECSS-E-ST-33-11_0280086",1,"Created","Each element in the explosive system shall be compatible with its neighbour."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.8.1.3b","Requirement","ECSS-E-ST-33-11_0280093",1,"Created","The capability shall be provided to test the components separately."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.8.1.5a","Requirement","ECSS-E-ST-33-11_0280097",1,"Created","Access shall be provided throughout the space vehicle integration\n    1. to the initiators, safe, test, and arm plugs for connection,\n    2. for measurements of properties,\n    3. to all elements for inspection."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.8.2.4c","Requirement","ECSS-E-ST-33-11_0280111",1,"Created","Control circuits shall limit the power level at any barrier to at least 20 dB below the minimum activation power."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.8.2.5e","Requirement","ECSS-E-ST-33-11_0280116",1,"Created","Measures to satisfy requirement 4.8.2.5d shall not violate single-point grounding requirements."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.8.2.8c","Requirement","ECSS-E-ST-33-11_0280125",1,"Created","Provision shall be made to isolate power lines and return lines of the explosive system from electrical ground.\n    NOTE This is to prevent continued drain on the power system after firing when e.g. short circuit to ground can occur."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.8.2.11b","Requirement","ECSS-E-ST-33-11_0280131",1,"Created","When exposed to RF conditions, the explosive system shall not be degraded."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.8.4.1b","Requirement","ECSS-E-ST-33-11_0280144",1,"Created","The functionality shall be provided to verify the status of the barriers protecting the initiator before inserting the arming plug. "]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.9a","Requirement","ECSS-E-ST-33-11_0280154",1,"Created","All materials, including explosive substances, shall be compatible with those materials with which they can come into contact.\n    NOTE 1 Outgassing can occur during e.g. polymerization, degradation of polymers.\n    NOTE 2 Selection of materials and processes are done in conformance with ECSS-E-ST-32-08, ECSS-ST-Q-70, and ECSS-ST-Q-70-71.\n    NOTE 3 Explosive systems use materials (e.g. explosives, propellants, powder, binders, cleaning agents, cements) that can be toxic, corrosive, highly reactive, flammable, and dangerous with direct contact."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.9j","Requirement","ECSS-E-ST-33-11_0280163",1,"Created","Degradation of the explosives shall not exceed agreed limits."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.10.1h","Requirement","ECSS-E-ST-33-11_0280172",1,"Created","Electrical connectors shall provide continuous shielding in all directions."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.10.1j","Requirement","ECSS-E-ST-33-11_0280174",1,"Created","Connector-savers shall be used.\n    NOTE This is to prevent the receptacle and contacts from wear and damage."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.10.4a","Requirement","ECSS-E-ST-33-11_0280183",1,"Created","Faraday caps shall be used."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.10.7b","Requirement","ECSS-E-ST-33-11_0280192",1,"Created","Provision shall be made for access to the interface."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.10.10a","Requirement","ECSS-E-ST-33-11_0280202",1,"Created","The test plug shall:\n    1. provide electrical access to the firing circuits with electrical properties in any line agreed with the end-user, \n        NOTE Electrical properties include resistance, isolation, bonding, and faraday protection. \n    2. be compatible with the safe and arm connector,\n    3. not carry any potential or current at the time of insertion or removal, \n    4. be suitable for the number of connection cycles necessary to cover integration, test and use,\n    5. be suitable for use with flight hardware,\n    6. be scoop-proof,\n    7. be lockable.\n        NOTE E.g. sub-D connector, bayonet or triple-start thread type."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.10.11.1h","Requirement","ECSS-E-ST-33-11_0280210",1,"Created","All additional blocks shall be flagged “Remove before flight”.\n    NOTE Safe and arm devices can use initiator-simulator resistors."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.10.11.5c","Requirement","ECSS-E-ST-33-11_0280221",1,"Created","During transition from “safe” to “arm” each electrical switch shall disconnect before connecting to the next circuit.\n    NOTE Clause 4.1.2. applies."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.11.1.1b","Requirement","ECSS-E-ST-33-11_0280230",1,"Created","For other elements of the system, which can be fully tested before flight, the equipment environmental test conditions of the end-user shall apply.\n    NOTE The requirements for explosive components are given below as measurements to be made after specific preconditioning and under survival and operational conditions identified in 4.6."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.11.2.1a","Requirement","ECSS-E-ST-33-11_0280239",1,"Created","The properties of initiators given in Table 4-3 shall be quantified and conform to the figures where shown."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.11.2.2a","Requirement","ECSS-E-ST-33-11_0280241",1,"Created","The minimum no-fire rating shall be 1A (current) or 1W (power) for five minutes."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.11.2.4a","Requirement","ECSS-E-ST-33-11_0280248",1,"Created","The properties of the laser initiator given in Table 4-6 shall be quantified and conform to the figures where shown."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.11.3.3a","Requirement","ECSS-E-ST-33-11_0280260",1,"Created","The initiator shall incorporate an interface to match the interfaces on the fibre optic connector and the adapter which is used to join the two items."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.11.4.1b","Requirement","ECSS-E-ST-33-11_0280266",1,"Created","Under the conditions in column E of Table 4-9, the properties in column A, expressed in the units specified in column B, shall be between the values in column C (maximum) and column D (minimum)."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.11.5a","Requirement","ECSS-E-ST-33-11_0280279",1,"Created","Clause 4.10.11 shall apply."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.12.2b","Requirement","ECSS-E-ST-33-11_0280288",1,"Created","Re-settable separation nuts shall include a means of verifying that the nut is properly reset before and after its mating bolt or stud installation and torquing."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.12.3d","Requirement","ECSS-E-ST-33-11_0280295",1,"Created","Under the conditions in column E of Table 4-19, the properties in column A, expressed in the units specified in column B, shall be between the values in column C (maximum) and column D (minimum)."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.12.5a","Requirement","ECSS-E-ST-33-11_0280299",1,"Created","The properties of the cutter given in Table 4-21 shall be quantified and conform to the figures where shown."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.13.2b","Requirement","ECSS-E-ST-33-11_0280313",1,"Created","Uncontrolled modifications to equipment or procedures shall be prohibited."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.13.3e","Requirement","ECSS-E-ST-33-11_0280318",1,"Created","Periods of sensitivity to external environment shall be notified to the authorities.\n    NOTE Example of external environment is EMI."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.14.3.1c","Requirement","ECSS-E-ST-33-11_0280327",1,"Created","Qualification and lot acceptance tests shall be in conformance with clause 4.14.4."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.14.3.7a","Requirement","ECSS-E-ST-33-11_0280337",1,"Created","Safety tests shall be performed on unpacked articles in conformance with Table 4-23. "]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.14.4.1e","Requirement","ECSS-E-ST-33-11_0280346",1,"Created","Dynamic leak measurement shall be made under vacuum."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.15.1a","Requirement","ECSS-E-ST-33-11_0280351",1,"Created","Specified transport, handling, and facilities for explosive subsystems and devices shall be provided."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.15.3f","Requirement","ECSS-E-ST-33-11_0280365",1,"Created","The location of every live or fired explosive component or subsystem shall be known and identifiable at any time."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.16.1a","Requirement","ECSS-E-ST-33-11_0280374",1,"Created","Checks shall be made to assure the consistency of information between different equipment at different stages in the launch preparation."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.16.1c","Requirement","ECSS-E-ST-33-11_0280376",1,"Created","Information shall be provided of hardware and software provisions for the monitoring and command of explosive functions, and show changes from one stage to the next."]
["ECSS-E-ST-33-11C","ECSS - Superseded v1.0","4.16.3a","Requirement","ECSS-E-ST-33-11_0280383",1,"Created","Confirmation of operation shall be made available immediately."]
["ECSS-E-ST-20-06C","ECSS - Superseded v1.0","6.2.2a","Requirement","ECSS-E-ST-20-06_0070005",1,"Created","In order to limit differential voltage, a maximum current density of J = 10 nA/cm2 through the dielectric shall be used to calculate the maximum resistivity of dielectric materials.\n    NOTE This current is a recommended upper bound of the current through dielectric material to other parts on Earth orbiting spacecraft. It is not the electron irradiation current used for testing.. For example, a small sunlit area of aluminium coupled to a larger area of material in eclipse can lead to a current flow through a dielectric beneath the aluminium as large as the photocurrents (~ 4nA/cm2 for aluminium) plus any difference in secondary emission current."]
["ECSS-E-ST-20-06C","ECSS - Superseded v1.0","6.3.2a","Permission","ECSS-E-ST-20-06_0070166",1,"Created","Except in the case specified in 6.3.2c, floating conductive parts may be used if they have an area less than 1 cm2 and have a total capacitance less than 10 pF with respect to the structure. \n    NOTE This is to limit the energy available to discharge. "]
["ECSS-E-ST-20-06C","ECSS - Superseded v1.0","6.3.3.3b","Requirement","ECSS-E-ST-20-06_0070022",1,"Created","Any point on a blanket shall be within 1 m of a bonding strap. "]
["ECSS-E-ST-20-06C","ECSS - Superseded v1.0","6.5a","Requirement","ECSS-E-ST-20-06_0070033",1,"Created","The perturbation of surface electrostatic potential arising from potentials that are deliberately maintained on a surface shall be analysed.\n    NOTE This can for example be the case where a scientific experiment has a deliberately exposed surface held at a potential. Recessing and shielding of the potential surface are strategies for reducing such perturbations."]
["ECSS-E-ST-20-06C","ECSS - Superseded v1.0","6.6.1g","Requirement","ECSS-E-ST-20-06_0070040",1,"Created","A mono-energetic spectrum with energy from 20 keV to 40 keV shall be used to deliver the surface charging current. "]
["ECSS-E-ST-20-06C","ECSS - Superseded v1.0","6.6.1k","Requirement","ECSS-E-ST-20-06_0070044",1,"Created","Qualification tests for materials shall:\n    - be performed with multi-energetic electron beams, and \n    - reproduce the dose-rate and charging current of the environment.\n        NOTE This is because of the radiation and electric field induced conductivity. These effects influence the surface voltage and consequently the risk of discharge."]
["ECSS-E-ST-20-06C","ECSS - Superseded v1.0","6.7d","Requirement","ECSS-E-ST-20-06_0070058",1,"Created","The effect of elevated voltage systems and of the spacecraft motion through the ambient magnetic field shall be analysed.\n    NOTE An example is for solar array."]
["ECSS-E-ST-20-06C","ECSS - Superseded v1.0","6.8.2a","Requirement","ECSS-E-ST-20-06_0070063",1,"Created","Material parameters shall be ascertained through testing, either by the manufacturer or as part of the selection procedure. \n    NOTE Examples are bulk conductivity and surface conductivity."]
["ECSS-E-ST-20-06C","ECSS - Superseded v1.0","7.2.2a","Requirement","ECSS-E-ST-20-06_0070072",1,"Created","If the design does not fulfil clause 6.3, then an analysis shall be made and an EMC test approved by the customer shall be defined to cover the expected discharge level. \n    NOTE EMC test specifications can originate in ISO 14302 or ECSS-E-ST-20-07."]
["ECSS-E-ST-20-06C","ECSS - Superseded v1.0","7.2.3.1e","Requirement","ECSS-E-ST-20-06_0070078",1,"Created","The test duration shall be such as to allow at least 10 discharges in each area."]
["ECSS-E-ST-20-06C","ECSS - Superseded v1.0","7.2.3.2m","Requirement","ECSS-E-ST-20-06_0070091",1,"Created","The capacitance of the missing cover glasses shall be included in the test. "]
["ECSS-E-ST-20-06C","ECSS - Superseded v1.0","7.3b","Requirement","ECSS-E-ST-20-06_0070096",1,"Created","Testing requirements for solar arrays in 7.2.3 shall apply all exposed parts of a power system.\n    NOTE The objective is to demonstrate that secondary arcing due to any kind of primary phenomenon cannot lead to damage."]
["ECSS-E-ST-20-06C","ECSS - Superseded v1.0","9.2.3e","Requirement","ECSS-E-ST-20-06_0070110",1,"Created","For analysis and testing, a customer-agreed worst-case environment shall be used, in the form of either:\n    1. a worst-case model of radiation belt electron fluxes in conjunction with an orbit generator, or\n    2. a worst-case spectrum for the orbit in question\n        NOTE 1 A worst case spectrum for internal charging is a time-average where the time period reflects the time-scale of internal charging (usually 1 day).\n        NOTE 2 The FLUMIC electron environment model (see Annex D.3) has been created specifically for internal charging assessments for all terrestrial orbits.\n        NOTE 3 Electron environment models which are averages of periods much longer than a day are used in assessments of other processes, e.g. dose analysis, but are inappropriate for internal charging analysis. "]
["ECSS-E-ST-20-06C","ECSS - Superseded v1.0","9.3g","Permission","ECSS-E-ST-20-06_0070172",1,"Created","Detailed assessment of the surface voltages on internal surfaces need not be performed if the following has been established.\n    1. The thickness of the dielectric is less than 0,1 mm.\n        NOTE In this case meeting the electric field requirements also meets the internal surface voltage requirement.\n    2. The product of charging current density and thickness is very low, i.e. less than the product of Vmax and σmin (as described in 9.3f). \n        NOTE For Vmax=1 kV and σmin=2 × 10-17W-1m-1, this product is 2 × 10 14 A m."]
["ECSS-E-ST-20-06C","ECSS - Superseded v1.0","9.3i","Requirement","ECSS-E-ST-20-06_0070121",1,"Created","For systems sensitive to absolute levels of internal electric fields and comprising insulators or isolated conductors, an analysis of the susceptibility to internal charging shall be made. \n    NOTE For devices like triaxial accelerometers, this is most likely to be achieved using particle transport codes. For MEMS devices, where the trapping of charge in dielectric layers is not easily calculated, this is most likely to be achieved by laboratory simulation. In all cases, it cannot be done without identification of suitable environment models. This can include energetic proton and ion models where these are significant sources of deposited charge."]
["ECSS-E-ST-20-06C","ECSS - Superseded v1.0","10.2.7a","Requirement","ECSS-E-ST-20-06_0070130",1,"Created","Mechanical hazards to the spacecraft and the debris hazards to other spacecraft associated with a tether that breaks due to electrical burn-out or other cause shall be analysed. "]
["ECSS-E-ST-20-06C","ECSS - Superseded v1.0","11.2.1h","Requirement","ECSS-E-ST-20-06_0070143",1,"Created","The current capacity of the neutralizers whose role is to control natural charging levels shall be higher than the largest natural charging current. "]
["ECSS-E-ST-20-06C","ECSS - Superseded v1.0","11.2.2c","Requirement","ECSS-E-ST-20-06_0070149",1,"Created","The electrostatic perturbation resulting from the assessment specified in 11.2.2b shall be within a level agreed with the customer. "]
["ECSS-E-ST-20-06C","ECSS - Superseded v1.0","11.3.2c","Requirement","ECSS-E-ST-20-06_0070157",1,"Created","Computer models shall be validated with data coming from ground tests or with flight tests. "]
["ECSS-E-ST-60-20C Rev. 1","ECSS - Superseded v1.0","4.1.3.1a","Requirement","ECSS-E-ST-60-20_0920005",1,"Created","The minimum set of inputs to be supplied in order to initialize the Star Tracking shall be:\n    1. the initial star position;\n    2. the angular rate;\n    3. validity date."]
["ECSS-E-ST-60-20C Rev. 1","ECSS - Superseded v1.0","4.1.5.2a","Requirement","ECSS-E-ST-60-20_0920014",1,"Created","A sensor with autonomous attitude determination shall have the minimum outputs:\n    1. the relative orientation of the defined sensor reference frame with respect to the defined inertial reference frame;\n        NOTE The relative orientation is usually expressed in the form of a normalized attitude quaternion\n    2. the Measurement date;\n    3. a validity index or flag estimating the validity of the determined attitude."]
["ECSS-E-ST-60-20C Rev. 1","ECSS - Superseded v1.0","4.1.6.1d","Requirement","ECSS-E-ST-60-20_0920018",1,"Created","The supplier shall document whether the star sensor initialization uses either:\n    • Internal initialization, or\n    NOTE The information to initialize the sensor is provided by the attitude determination function of the star sensor.\n    • Direct initialization.\n    NOTE The information to initialize the sensor is supplied by an external source e.g. AOCS."]
["ECSS-E-ST-60-20C Rev. 1","ECSS - Superseded v1.0","4.1.8.2b","Requirement","ECSS-E-ST-60-20_0920025",1,"Created","The image output time shall be verified by test using the hardware agreed between the customer and supplier.\n    NOTE 1 The hardware used to perform the test is the hardware used to download the image from the star sensor.\n    NOTE 2 For example:\n        • “The Star Sensor shall be capable of performing a full Image Download of the entire Field of View at 12-bit resolution. The image output time shall be less than 10 seconds.”\n        • “The Star Sensor shall be capable of performing a partial Image Download at 12-bit resolution of a n×n section of the Field of View. The image output time shall be less than 10 seconds.”"]
["ECSS-E-ST-60-20C Rev. 1","ECSS - Superseded v1.0","4.3.2a","Requirement","ECSS-E-ST-60-20_0920032",1,"Created","Any use of an IRF shall be accompanied by the definition of the IRF frame."]
["ECSS-E-ST-60-20C Rev. 1","ECSS - Superseded v1.0","5.1.2c","Requirement","ECSS-E-ST-60-20_0920044",1,"Created","The performances shall be assessed by using the sensor EOL conditions agreed with the customer.\n    NOTE The EOL conditions include e.g. aging effects, radiation dose."]
["ECSS-E-ST-60-20C Rev. 1","ECSS - Superseded v1.0","5.4c","Requirement","ECSS-E-ST-60-20_0920050",1,"Created","The supplier shall identify the worst case projection in BRF of the value defined in 5.4d. \n    NOTE Different angular rates can be specified with associated required performance."]
["ECSS-E-ST-60-20C Rev. 1","ECSS - Superseded v1.0","5.5.2.1c","Requirement","ECSS-E-ST-60-20_0920063",1,"Created","The bias performance shall be specified for a defined ambient temperature.\n    NOTE The initial alignment is an instantaneous measurement error at the time of calibration. For the purposes of error budgeting it can be considered to be an invariant error."]
["ECSS-E-ST-60-20C Rev. 1","ECSS - Superseded v1.0","5.5.4.1b","Requirement","ECSS-E-ST-60-20_0920072",1,"Created","The ‘Ensemble’ interpretation shall be used (see NOTE in 5.5.2.1b)."]
["ECSS-E-ST-60-20C Rev. 1","ECSS - Superseded v1.0","5.5.5.1c","Requirement","ECSS-E-ST-60-20_0920079",1,"Created","The performance shall be specified under the related performance general conditions."]
["ECSS-E-ST-60-20C Rev. 1","ECSS - Superseded v1.0","5.5.5.3b","Requirement","ECSS-E-ST-60-20_0920083",1,"Created","Pixel spatial errors shall be verified by analysis and simulations using verified budgets of contributing error sources methods.\n    NOTE E.g. “The Star Sensor shall have a pixel spatial error of less than 5 arcseconds (resp. 30) around X and Y axes (resp. Z axis) for spatial period of 400 arcsecond, and less than 2 arcseconds (resp 10) around X and Y axes (resp. Z axis) for spatial period of 100 arcsecond.”"]
["ECSS-E-ST-60-20C Rev. 1","ECSS - Superseded v1.0","5.5.9b","Permission","ECSS-E-ST-60-20_0920152",1,"Created","On-ground tests may be performed.\n    NOTE E.g. “The Star Sensor shall have a Measured Output Bandwidth of greater than 10 Hz.” "]
["ECSS-E-ST-60-20C Rev. 1","ECSS - Superseded v1.0","5.8.1b","Requirement","ECSS-E-ST-60-20_0920102",1,"Created","The following additional performance metrics shall be established: track maintenance probability, as specified in 5.7.2."]
["ECSS-E-ST-60-20C Rev. 1","ECSS - Superseded v1.0","5.9.4c","Requirement","ECSS-E-ST-60-20_0920115",1,"Created","Probability of Invalid Attitude Solution:\n    1. The probability of invalid attitude solution shall be estimated considering all possible initial pointing directions within a defined region within the celestial sphere.\n    2. The probability of invalid attitude determination shall be estimated under the conditions given in given in 5.4 and 5.9.2.\n    3. The probability of invalid attitude determination shall be verified using the method specified in 5.9.3.\n        NOTE E.g. “The probability of invalid attitude solution shall be less than 0,1 % for random initial pointing within the entire celestial sphere, for rates around any axis of up to 100 arcsec/s at EOL and for accelerations up to 10 arcsec/s².”"]
["ECSS-E-ST-60-20C Rev. 1","ECSS - Superseded v1.0","5.10.1f","Requirement","ECSS-E-ST-60-20_0920121",1,"Created","For the effect of single event upsets (SET’s) the following condition shall be met:\nQuote the maintenance level of tracking with the maximum number of SET’s per second for which the specification is applicable."]
["ECSS-E-ST-60-20C Rev. 1","ECSS - Superseded v1.0","5.11.2a","Requirement","ECSS-E-ST-60-20_0920130",1,"Created","Performance at finite rates and accelerations, and for all scenarios under the specified conditions, shall be verified by simulation.\n    NOTE E.g. The Star Sensor shall have an angular rate measurement around any BRF axis of less than 100 arcsec/s, at rates around any axis of up to 10 deg/s at EOL and for accelerations up to 1 deg/s²."]
["ECSS-E-ST-60-20C Rev. 1","ECSS - Superseded v1.0","5.12e","Requirement","ECSS-E-ST-60-20_0920135",1,"Created","The functional mathematical model shall be validated against the actual temporal performances of the sensor."]
["ECSS-E-ST-60-20C Rev. 1","ECSS - Superseded v1.0","A.2.1<5>b","Requirement","ECSS-E-ST-60-20_0920149",1,"Created","For sensors with the autonomous attitude tracking capability, the FMM description shall include the autonomous attitude tracking capability."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.2.3a","Requirement","ECSS-E-ST-33-01_0820002",1,"Unchanged","SI-units and associated symbols system shall be used."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.2.4.3a","Requirement","ECSS-E-ST-33-01_0820009",1,"Unchanged","All items having the same identification number shall be functionally and dimensionally interchangeable."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.2.5.1d","Requirement","ECSS-E-ST-33-01_0820016",1,"Unchanged","For structural reliability aspects ECSS-E-ST-32 shall apply."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.4.1a","Requirement","ECSS-E-ST-33-01_0820028",1,"Unchanged","The mechanism functional performance shall conform to the system performance requirements."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.5.2.4a","Requirement","ECSS-E-ST-33-01_0820037",1,"Unchanged","Materials shall be selected as specified in ECSS-Q-ST-70-36."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.5.2.10a","Requirement","ECSS-E-ST-33-01_0820049",1,"Unchanged","For fluid compatibility, ECSS-Q-ST-70-71 clause “Fluid compatibility” shall apply."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.6.2a","Requirement","ECSS-E-ST-33-01_0820056",1,"Unchanged","Thermo­mechanical interfaces shall be designed to take into account the stresses induced by the structure between the mechanism and its I/F attachment points."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.7.3.1f","Recommendation","ECSS-E-ST-33-01_0820457",1,"Created","Metal to metal tribological contacts should be composed of dissimilar materials, in conformance with 4.5.2.3."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.7.3.1j","Requirement","ECSS-E-ST-33-01_0820067",1,"Unchanged","The lubricant shall conform to the molecular and particulate contamination requirements specified for the entire mission.","NOTE \tFor molecular and particulate contamination, see ECSS-Q-ST-70-01.\n"]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.7.3.4.2b","Requirement","ECSS-E-ST-33-01_0820081",1,"Unchanged","The calculation specified in requirement 4.7.3.4.2a shall be made available to the customer."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.7.3.4.2g","Recommendation","ECSS-E-ST-33-01_0820459",1,"Created","Bearing preload should be measured after final mechanism assembly."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.7.4.2e","Requirement","ECSS-E-ST-33-01_0820095",1,"Unchanged","The mechanism design shall take into account the worst-case combinations (including uncertainties) of:\n1.\textremes of operational and survival steady­state, \n2.\ttransient temperatures, \n3.\tmechanism heat dissipation, and\n4.\tthe temperature gradients across the mechanism.","NOTE \tFailure to consider the effects of differential expansion can lead to a catastrophic failure.\n"]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.7.5.2.2a","Requirement","ECSS-E-ST-33-01_0820101",1,"Unchanged","The load general requirements of ECSS-E-ST-32, shall apply in­orbit loads."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.7.5.2.6a","Requirement","ECSS-E-ST-33-01_0820113",1,"Unchanged","For the structural factors of safety, requirements of ECSS-E-ST-32-10 shall apply."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.7.5.2.6f","Requirement","ECSS-E-ST-33-01_0820398",1,"Created","In the mechanism requirement specification the Design Limit Loads (DLL) shall be specified.","NOTE \t 1\tIt is good practice to clarify with the customer that the Project factor (KP) and the Model factor (KM) are already included, to avoid duplication of factors.\nNOTE \t2\tDLL are intended to be environmental loads.\n"]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.7.5.3.2e","Requirement","ECSS-E-ST-33-01_0820128",2,"Normative Change","When the actuation torque or force is supplied by a spring actuator, the actuation torque or force supplied by the spring, shall be:\n1.\tderived considering worst-case conditions,\n2.\tmultiplied by the maximum uncertainty factor of 0,8 when ageing measurement are not available, and\n3.\tagreed with the customer when ageing measurement are performed."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.7.5.3.2i","Requirement","ECSS-E-ST-33-01_0820402",1,"Created","When the actuation torque or force is supplied by an electric motor the worst case torque or force generated by the motor shall be based on:\n1.\tmeasurement at operating conditions, or\n2.\tagreement with the customer if a measurement is not available.","NOTE \tOperating conditions include speed and duty cycle.\n"]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.7.5.4.2b","Requirement","ECSS-E-ST-33-01_0820136",1,"Unchanged","Mission critical mechanisms shall be designed in such way that monitoring information of its critical functions is accessible to the spacecraft telemetry.","NOTE \tFor telemetry requirements, see ECSS-E-ST-70-11, clause 5.9.5\n"]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.7.5.4.3g","Requirement","ECSS-E-ST-33-01_0820143",1,"Unchanged","Latches shall be resettable for ground testing."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.7.5.4.5c","Requirement","ECSS-E-ST-33-01_0820156",1,"Unchanged","Except for gears and ball or journal bearings, the repeatability of the contact between the mating surfaces shall be verified and agreed by the customer.","NOTE \tRepeatability includes contact loads, contact area, contact stress, and alignment.\n"]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.7.5.4.5i","Requirement","ECSS-E-ST-33-01_0820408",1,"Created","In case recommendation 4.7.5.4.5h is not met, justification shall be provided and approved by the customer."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.7.5.4.10b","Requirement","ECSS-E-ST-33-01_0820171",1,"Unchanged","Threaded fasteners shall be made from materials, which are not susceptible to stress corrosion cracking.","NOTE \t1\tFor materials preferred list, see ECSS-Q-ST-70-36. For other materials validation, see ECSS-Q-ST-70-37.\nNOTE \t2\tFor manufacturing of threaded fasteners see ECSS-Q-ST-70-46. \n"]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.7.5.4.12b","Requirement","ECSS-E-ST-33-01_0820177",1,"Unchanged","Where no actuator redundancy is provided, redundancy shall be provided by duplicating up to and including the level of the initiators, heating element or equivalent for non­pyrotechnic devices, and its power supply."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.7.7.1.1c","Requirement","ECSS-E-ST-33-01_0820186",1,"Unchanged","Electrical power consumption, generation and thermal dissipation shall be quantified by design."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.7.7.1.1g","Requirement","ECSS-E-ST-33-01_0820190",1,"Unchanged","If brush motors are used, it shall be verified under representative environment and over specified lifetime that debris generation does not result in electrical failure.","NOTE \tFor example, short circuit of commutators.\n"]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.7.7.3a","Requirement","ECSS-E-ST-33-01_0820195",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.7.7.5d","Requirement","ECSS-E-ST-33-01_0820206",1,"Unchanged","Electrical connectors shall be redundant."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.7.7.8a","Requirement","ECSS-E-ST-33-01_0820214",1,"Unchanged","Mechanisms shall conform to the spacecraft system requirements on magnetic cleanliness in conformance with ECSS-E-ST-20-07, and conductivity of surfaces for electrostatic discharge (ESD) protection in conformance with ECSS-E-ST-20-06. "]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.7.8.5a","Requirement","ECSS-E-ST-33-01_0820220",1,"Unchanged","The control system shall not excite mechanism eigenmodes."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.8.1b","Requirement","ECSS-E-ST-33-01_0820233",1,"Unchanged","A verification matrix shall be established by the supplier and provided to the customer for agreement."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.8.2.6.1a","Requirement","ECSS-E-ST-33-01_0820242",2,"Normative Change","Functional performance analysis shall be performed for worst case environmental and operational conditions.","NOTE \tOperational conditions are based on worst-case identification.\n"]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.8.2.6.3e","Requirement","ECSS-E-ST-33-01_0820249",1,"Unchanged","If test results do not match predictions, the reason of the disagreement shall be found, and the analysis shall be updated accordingly. "]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.8.2.8a","Requirement","ECSS-E-ST-33-01_0820253",1,"Informative Change","Conformance of mechanisms to specified requirements on functional dimensioning shall be verified by analysis.","NOTE \tExamples of such requirements are torque, force, and kinematics.\n"]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.8.2.14a","Requirement","ECSS-E-ST-33-01_0820267",1,"Unchanged","An analysis of the choice of lubrication system and its dimensioning for the proposed application and lifetime shall be provided."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.8.2.16a","Requirement","ECSS-E-ST-33-01_0820272",1,"Unchanged","The design compatibility with the hygroscopic environment during the complete lifetime shall be verified by analysis.","NOTE \tThe hygroscopic environment is mainly relevant on-ground.\n"]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.8.3.2.2a","Requirement","ECSS-E-ST-33-01_0820285",2,"Normative Change","Except in the case specified in requirement 4.8.3.2.2b, the following verification tests on development model mechanisms shall be performed during phases A or B of the project:\n1.\tfunctional performance tests in ground ambient environment.\n2.\tvibration and thermal tests.\n3.\ttribological lifetime test on life critical items."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.8.3.3.3b","Requirement","ECSS-E-ST-33-01_0820291",1,"Unchanged","Operation of the mechanism in a representative environment under worst-case temperature gradients shall be verified by test at a level agreed by the customer."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.8.3.3.7b","Requirement","ECSS-E-ST-33-01_0820299",1,"Unchanged","Lubricant quantity shall be verified by tests."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.8.3.3.9b","Requirement","ECSS-E-ST-33-01_0820304",2,"Deleted","<<deleted>> "]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.8.3.3.14b","Requirement","ECSS-E-ST-33-01_0820317",1,"Unchanged","For the test verification, the number of expected cycles shall be multiplied by the factors in Table 4-4."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.8.3.3.14f","Requirement","ECSS-E-ST-33-01_0820420",1,"Created","For crewed space missions, safety critical mechanisms using “design for minimum risk” to control hazards, the following minimum factors shall be applied for both ground and in-orbit cycles when the result of calculation using the Table 4-4 is lower than:\n1.\tan overall factor of 2 for critical hazard potential, and \n2.\tan overall factor of 4 for catastrophic hazard potential.","NOTE \tTable 4-6 and Table 4-7 present two case examples to calculate the number of cycles to be used in the test for safety critical mechanisms.\n"]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.8.3.4.2c","Requirement","ECSS-E-ST-33-01_0820327",1,"Unchanged","The acceptance level testing shall be carried out at levels, which are higher than expected in flight but less than the qualification levels."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","4.10b","Requirement","ECSS-E-ST-33-01_0820335",1,"Unchanged","The supplier shall provide the mechanisms analytical verification (MAV) in conformance with the DRD in Annex C."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","A.2.1<3>b","Requirement","ECSS-E-ST-33-01_0820342",1,"Unchanged","If the mechanism is not maintenance free during storage and ground life, the SMS shall list the maintenance requirements, including for each of them:\n1.\tnumber of operations,\n2.\tfrequency of operations,\n3.\tspecial tooling and test equipment,\n4.\tcalibration and adjustments, \n5.\tfault identification and repair, and\n6.\tenvironment for maintainability operation.","NOTE \tSee 4.2.4.4b.\n"]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","A.2.1<6>a","Requirement","ECSS-E-ST-33-01_0820351",2,"Normative Change","The SMS shall list the handling, storage and operational requirements for all lubricated parts."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","B.2.1<1>c","Requirement","ECSS-E-ST-33-01_0820363",1,"Unchanged","The MDD shall include any additional definition, abbreviation or symbol used."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","B.2.1<6>a","Requirement","ECSS-E-ST-33-01_0820370",1,"Unchanged","The MDD shall provide informative data with regard to performance, mass and power budgets.","NOTE \tThis is provided for information only. The contractual values are provided in the verification files.\n"]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","C.2.1<1>b","Requirement","ECSS-E-ST-33-01_0820372",1,"Informative Change","The MAV shall list:\n1.\tall the applicable documents regarding requirements related to design and performance; \n2.\tthe design definition file reference of the mechanism being analysed;\n3.\tthe list of documents providing inputs to analyses presented in this document; \n4.\tany other applicable and reference documents to support the generation of the document.","NOTE 1 \tto item 3: For example, thermal analysis, structural analysis, and test reports.\nNOTE 2\tto item 3: Subsystems and parts data to be included."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","D.2.1<2>a","Requirement","ECSS-E-ST-33-01_0820381",1,"Unchanged","The user manual shall describe the mission and the role of the mechanism in achieving the mission. "]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","F.2.1<1>b","Requirement","ECSS-E-ST-33-01_0820426",1,"Created","The MSVP shall list:\n1.\tthe development phase of the mechanism being described;\n2.\tthe list of documents providing additional subsystem design description; \n3.\tany other applicable and reference documents to support the generation of the document. "]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","F.2.1<3>b","Requirement","ECSS-E-ST-33-01_0820431",1,"Created","The MSVP shall identify safety critical mechanisms and determine the severity level of the hazard."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","G.2.1<1>b","Requirement","ECSS-E-ST-33-01_0820440",1,"Created","The MSVR shall list: \n1.\tthe development phase of the mechanism being described;\n2.\tthe list of documents providing additional verification description;\n3.\tany other applicable and reference documents to support the generation of the document."]
["ECSS-E-ST-33-01C Rev.1","ECSS - Superseded v1.0","G.2.1<5>c","Requirement","ECSS-E-ST-33-01_0820450",1,"Created","The MSVR shall cross-reference any separate test analyses."]
["ECSS-E-ST-32-10C Rev. 1","ECSS - Superseded v1.0","4.1.4.4a","Requirement","ECSS-E-ST-32-10_0110009",1,"Created","The qualification factor KQ shall be applied for satellites.\n    ","NOTE For satellites, the qualification loads are part of the specified loads and are accounted for in the dimensioning process. This is different for launch vehicles for which QL are consequences of the dimensioning process."]
["ECSS-E-ST-32-10C Rev. 1","ECSS - Superseded v1.0","4.2.1a","Requirement","ECSS-E-ST-32-10_0110014",1,"Created","QL, AL, DLL, DYL, and DUL, for the test and the design of satellite, expendable launch vehicles, pressurized hardware and man-rated system shall be calculated from the LL as specified in Figure 4-1 and Table 4-1.\n    ","NOTE 1 As a result of the launch vehicle-satellite coupled dynamic load analysis (LCDA) performed during the project design and verification phases, the knowledge of the LL can be modified during the course of the project, leading to a final estimation of the loads LLfinal. Then for final verification, it is used as a minimum:\nQL = KQ × LLfinal \t\tfor qualification, and\nAL = KA × LLfinal\t\tfor acceptance\nNOTE 2 The yield design factor of safety (FOSY) ensures a low probability of yielding during loading at DLL level.\nNOTE 3 The ultimate design factor of safety (FOSU) ensures a low probability of failure during loading at DLL level."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","5.2.1b","Requirement","ECSS-E-ST-50-12_0910004",1,"Created","The SpaceWire cable shall comprise four twisted pair wires with a separate shield around each twisted pair and an overall shield as illustrated in Figure 5-1."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","5.2.2.2b","Requirement","ECSS-E-ST-50-12_0910008",1,"Created","The tensile strength of each strand shall be at least 350 N/mm2."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","5.2.3.4a","Requirement","ECSS-E-ST-50-12_0910015",1,"Created","The filler material shall be extruded or wrapped from tapes to a diameter of 1,0 mm."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","5.2.3.10a","Requirement","ECSS-E-ST-50-12_0910024",1,"Created","The jacket colour of the differential signal pairs shall be white."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","5.2.4.10a","Requirement","ECSS-E-ST-50-12_0910037",1,"Created","All strands used in the manufacture of the braided shield shall be silver-coated, soft or annealed oxygen-free high conductivity copper."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","5.2.4.14a","Requirement","ECSS-E-ST-50-12_0910043",1,"Created","The colour of the jacket shall be white."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","5.3.2b","Requirement","ECSS-E-ST-50-12_0910055",1,"Created","Receptacles shall be equipped with female contacts. "]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","5.3.3d","Requirement","ECSS-E-ST-50-12_0910062",1,"Created","Crimping shall conform to ECSS-Q-ST-70-26."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","5.3.7c","Requirement","ECSS-E-ST-50-12_0910071",1,"Created","If a PCB mounting right-angled connector is used, signals connected to the top row shall be given correspondingly shorter PCB track lengths than tracks going to the bottom row. \n    ","NOTE The reason is that the topmost row of pins on the right-angled connect have longer leads than the bottom row."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","5.4.3a","Requirement","ECSS-E-ST-50-12_0910075",1,"Created","The connector contacts shall be terminated as shown in Figure 5-3 and Table 5-3.\n    ","NOTE The cable signal wires cross over to achieve a transmit to receive interconnection, e.g. Dout+ is connected to Din+ ."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","5.5.2.3a","Requirement","ECSS-E-ST-50-12_0910082",1,"Created","The skew introduced between the Data and Strobe (D and S) signals shall be minimized as specified here. For PCB tracks, skew is controlled by making the tracks all close to the same length. "]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","6.3.2b","Requirement","ECSS-E-ST-50-12_0910093",1,"Created","When the SpaceWire transmitter is reset it shall be a controlled reset avoiding simultaneous transitions of Data and Strobe signals.\n    ","NOTE 1 For example, after stopping transmission the Strobe signal can be reset first, followed by the Data signal.\nNOTE 2 Simultaneous transitions on the Data and Strobe lines are not part of the normal operation of SpaceWire. They can occur, however, either when a SpaceWire cable is plugged in while the transmitter is trying to make a connection, or when the LVDS driver or receiver circuits are enabled while the transmitter is trying to make a connection. "]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","6.6.5a","Requirement","ECSS-E-ST-50-12_0910101",1,"Created","After a reset or disconnect (see clause 8.9.2.1) the SpaceWire link transmitter shall initially commence operating at a data signalling rate of (10±1) Mb/s. "]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","7.3e","Requirement","ECSS-E-ST-50-12_0910111",1,"Created","An escape character (ESC) followed by ESC, EOP or EEP is an invalid sequence and shall be noted as an escape error (see clause 8.9.2.3)."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","7.7a","Requirement","ECSS-E-ST-50-12_0910120",1,"Created","The time interface to the host system shall comprise two signals, TICK_IN and TICK_OUT, a six-bit time output port, a six-bit time input port, a two-bit control flag input port and a two-bit control flag output port."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","8.2.2b","Requirement","ECSS-E-ST-50-12_0910129",1,"Created","A received character shall not be acted upon until its parity has been checked."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","8.3b","Requirement","ECSS-E-ST-50-12_0910131",1,"Created","A FCT sent out by a link interface shall be used to indicate that there is space for eight more N-Chars in the host receive buffer. "]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","8.3k","Requirement","ECSS-E-ST-50-12_0910140",1,"Created","On reset (or after a link disconnect) the initial number of FCTs to transmit shall be set according to the size of the receive buffer (one FCT for every eight N-Chars that can be held in the receive buffer) up to a maximum of seven.\n    ","NOTE If the receive buffer has a capacity of more than 56 (seven FCTs worth) then the number of FCTs to transmit initially shall be set to seven. A maximum of seven FCTs can be outstanding at any time."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","8.5.2.2a","Requirement","ECSS-E-ST-50-12_0910149",1,"Created","The ErrorReset state shall be entered after a system reset, after link operation is terminated for any reason or if there is an error during link initialization."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","8.5.2.4b","Requirement","ECSS-E-ST-50-12_0910159",1,"Created","In the Ready state the link interface is ready to initialize as soon as it is allowed to do so. The receiver shall be enabled and the transmitter shall be reset."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","8.5.2.6b","Requirement","ECSS-E-ST-50-12_0910172",1,"Created","On entering the Connecting state a 12,8 ms timeout timer shall be started. "]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","8.5.2.7b","Requirement","ECSS-E-ST-50-12_0910178",1,"Created","If the link interface is disabled, or if a disconnect error, parity error, escape error or credit error is detected (see clause 8.5.3), while in the Run state, then the state machine shall move to the ErrorReset state. \n    ","NOTE The Run state is the state for normal operation where link connection has been made and L-Chars and N-Chars can flow freely in both directions across the link. The link remains in the Run state until an error occurs or until the link is disabled."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","8.5.3.5a","Requirement","ECSS-E-ST-50-12_0910187",1,"Created","A time-code received when the exchange-level state machine is not in the Run state shall be interpreted as an error.\n    ","NOTE gotTime-Code means that a time-code has been received."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","8.5.3.7.4a","Requirement","ECSS-E-ST-50-12_0910192",1,"Created","The Escape error shall be detected by the receiver in the link interface.\n    ","NOTE The escape error event occurs if an ESC character is followed by any control character other than an FCT (ESC followed by FCT is a NULL, see clause 7.3). ESC followed by a data character is a Time-Code (clause 7.3)."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","8.9.2.1.2b","Requirement","ECSS-E-ST-50-12_0910206",1,"Created","The disconnect-detection time shall be 850 ns nominal. \n    ","NOTE See clause 8.11.2 for the disconnect timing specification. A disconnection cannot be detected unless the receiver has previously received at least one bit."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","8.9.2.1.2f","Requirement","ECSS-E-ST-50-12_0910210",1,"Created","If the disconnect error occurs in the Run state then the disconnect error shall be flagged up to the network level as a link error (see clause 8.9.5)."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","8.9.2.4a","Requirement","ECSS-E-ST-50-12_0910217",1,"Created","A credit error shall be identified when in the Run state, a normal character is received when the host system is not expecting any N-Chars.\n    ","NOTE A credit error can be caused if an error occurs undetected by the parity bit (e.g. two bits in error) which results in one or more spurious FCTs. "]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","8.9.5c","Requirement","ECSS-E-ST-50-12_0910228",1,"Created","A link error shall be reported to the network level whenever any of the following errors occur while a link interface is in the Run state: disconnect error, parity error, escape sequence error, or credit error. \n    ","NOTE The exclusion of character sequence error from this list is because a character sequence error can only occur during initialization."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","8.12.2d","Requirement","ECSS-E-ST-50-12_0910236",1,"Created","When the time master link interface receives a tick (TICK_IN asserted) it shall increment its time-counter and then send out a Time-Code with the six-bit time field of the data character set to the new value of the time-counter and the other two bits set to the value of the control flags.\n    ","NOTE The frequency at which the TICK_IN signal is driven is called the tick rate."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","8.12.2m","Requirement","ECSS-E-ST-50-12_0910245",1,"Created","After reset or disconnect-reconnect (state machine in ErrorReset state) the time-counter shall be set to zero and any control-flag outputs shall be set to zero."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","9.2.4b","Requirement","ECSS-E-ST-50-12_0910257",1,"Created","EOP (end_of_packet) shall be used as the normal end of packet marker indicating the end of a packet."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","10.2.3b","Requirement","ECSS-E-ST-50-12_0910264",1,"Created","A SpaceWire routing switch shall either implement only path addressing, or a combination of path addressing, logical addressing and regional addressing."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","10.2.3d","Requirement","ECSS-E-ST-50-12_0910266",1,"Created","The routing switch addresses shall be assigned as shown in Table 10-1.\n    ","NOTE 1 A leading data character with a value of 0 results in the packet being routed to the routing switch configuration logic.\nNOTE 2 A leading data character with a value of 6 results in the packet being routed to output port 6.\nNOTE 3 A leading data character with a value of 49 results in the packet being routed to the output port that is referred to in location 49 of the routing table within the routing switch."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","10.2.3m","Requirement","ECSS-E-ST-50-12_0910275",1,"Created","One and only one data character (destination identifier) shall be deleted by each routing switch with header deletion enabled, that is traversed by the packet.\n    ","NOTE For very large switches the two leading destination identifiers can be used by a single routing switch to determine the destination address This enables switches with up to 961 (31 ´ 31) physical links and with over 50,000 (224 ´ 224) logical addresses."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","10.2.4g","Requirement","ECSS-E-ST-50-12_0910284",1,"Created","If the assigned output port is busy then the newly arrived packet shall wait at the input port until the assigned output port is free to transmit the new packet. "]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","10.3a","Requirement","ECSS-E-ST-50-12_0910294",1,"Created","A SpaceWire node shall comprise one or more SpaceWire link interfaces (encoder-decoders) and an interface to the host system.\n    ","NOTE A SpaceWire node represents an interface between a SpaceWire network and an application system using the network services. "]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","10.5.2d","Requirement","ECSS-E-ST-50-12_0910303",1,"Created","The current packet being received shall stop being received and the part of the packet that has been received already shall be terminated by an EEP."]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","12.2.1a","Requirement","ECSS-E-ST-50-12_0910313",1,"Created","An implementation of SpaceWire cable shall conform to all of the requirements given in all clauses listed in Table 12-1. \n    ","NOTE A cable meeting this specification may use the following conformance statement:\n“This cable conforms to the SpaceWire cable specification ECSS-E-ST-50-12-.”"]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","12.2.6a","Requirement","ECSS-E-ST-50-12_0910322",1,"Created","An implementation of a SpaceWire encoder-decoder which include the LVDS drivers and receivers shall conform to all of the requirements given in all clauses listed in Table 12-6. \n    ","NOTE A product fitted with an interface meeting this specification may use the following conformance statement:\n“This product conforms to the SpaceWire LVDS encoder- decoder specification ECSS-E-ST-50-12.”"]
["ECSS-E-ST-50-12C","ECSS - Superseded v1.0","12.2.9a","Requirement","ECSS-E-ST-50-12_0910331",1,"Created","An implementation of a SpaceWire routing switch unit shall conform to all of the requirements given in all clauses listed in Table 12-9. \n    ","NOTE A routing switch unit meeting this specification may use the following conformance statement:\n“This product conforms to the SpaceWire routing switch unit specification ECSS-E-ST-50-12.”"]
["ECSS-E-ST-32-10C Rev.2","ECSS - Superseded v1.0","4.1.4.3a","Requirement","ECSS-E-ST-32-10_0110007",1,"Unchanged","A specific “project factor” KP shall be applied to account for the maturity of the program (e.g. stability of the mass budget, well identified design) and the confidence in the specification given to the project (this factor integrates a programmatic margin e.g. for growth potential for further developments).","NOTE \tThe value of this factor is generally defined at system level and can be reduced during the development.\n"]
["ECSS-E-ST-32-10C Rev.2","ECSS - Superseded v1.0","4.1.5.2b","Requirement","ECSS-E-ST-32-10_0110011",1,"Unchanged","KLD values shall be justified.","NOTE \t1\tJustification can be performed based on relevant historical practice, analytical or experimental means.\nNOTE \t2\tFor satellites, a typical value of 1,2 is used in the following cases:\n·\tComposite structures discontinuities;\n·\tSandwich structures discontinuities (face wrinkling, intracell buckling, honeycomb s\nhear);\n·\tJoints and inserts.\nNOTE \t3\tThe use of a local design factor does not preclude appropriate engineering analysis (e.g. KLD does not cover the stress concentration factors) and assessment of all uncertainties.\n"]
["ECSS-E-ST-32-10C Rev.2","ECSS - Superseded v1.0","4.2.2a","Requirement","ECSS-E-ST-32-10_0110018",1,"Unchanged","The QL shall be defined with a corrected KQ.","NOTE \t1\tThe correction takes into account manufacturing variability and difficulties of having test conditions fully representative of flight conditions.\nNOTE \t2\tThe commonly used method for defining the corrected KQ is presented in Annex A for information.\n"]
["ECSS-E-ST-32-10C Rev.2","ECSS - Superseded v1.0","4.3.2.3a","Requirement","ECSS-E-ST-32-10_0110025",1,"Unchanged","The factor of safety for global and local buckling shall be selected from Table 4-5.","NOTE \tThe factor of safety does not cover the knock down factors commonly used in buckling analyses - see Buckling handbook (ECSS-E-HB-32-24).\n"]
["ECSS-E-ST-10-04C","ECSS - Superseded v1.0","5.3a","Permission","ECSS-E-ST-10-04_0760128",1,"Created","a.\tWhile the IGRF 10 model should normally be used for internal fields, a low­fidelity dipole model (using aligned, eccentric or tilted dipoles as appropriate) may suffice for some engineering applications. "]
["ECSS-E-ST-10-04C","ECSS - Superseded v1.0","6.2.2b","Requirement","ECSS-E-ST-10-04_0760018",1,"Created","For fixed index values, the numbers given in Table 6-3 for low, moderate and high solar and geomagnetic activities shall be used: \n1.\tThe long­term values are averaged values for periods longer than 27 days.\n2.\tThe long-term values apply as well for periods of 1 week or longer.\n3.\tThe short-term values are daily values. "]
["ECSS-E-ST-10-04C","ECSS - Superseded v1.0","7.2.1.2c","Requirement","ECSS-E-ST-10-04_0760030",1,"Created","For analysis periods longer than 1 week the long term activities given in Table 6-3 shall be used as input for both, the daily and the 81-day averaged values."]
["ECSS-E-ST-10-04C","ECSS - Superseded v1.0","8.2.1b","Requirement","ECSS-E-ST-10-04_0760037",1,"Created","Applicable environments for each region shall be characterised according to the models specified in 8.2.2 to 8.2.6."]
["ECSS-E-ST-10-04C","ECSS - Superseded v1.0","8.2.5a","Requirement","ECSS-E-ST-10-04_0760046",1,"Created","For assessment of surface charging, the worst­case environment listed in Table 8-1 shall be used as input to a spacecraft charging simulation or calculation, applicable to the outer magnetosphere environment. \nNOTE \tThis is a dynamic region in terms of plasma density and temperature and for most engineering purposes, worst­case environments are the most important consideration. See Annex H.3.4 for typical plasma parameters in this region. "]
["ECSS-E-ST-10-04C","ECSS - Superseded v1.0","8.2.6d","Requirement","ECSS-E-ST-10-04_0760050",1,"Created","A r-0,64 variation shall be used to map the mean and range of the electron temperature to other locations in the heliosphere in the ecliptic plane."]
["ECSS-E-ST-10-04C","ECSS - Superseded v1.0","9.2.1.2.1a","Requirement","ECSS-E-ST-10-04_0760057",1,"Created","For electron fluxes in geostationary orbits (± 500 km altitude) the standard model for Earth radiation belt energetic electrons shall be the IGE 2006 average model (previously called POLE [RN.12] and Annex B.2)."]
["ECSS-E-ST-10-04C","ECSS - Superseded v1.0","9.2.2.1a","Requirement","ECSS-E-ST-10-04_0760068",1,"Created","Fluxes and fluences of solar energetic particles shall be assumed to be isotropic.\nNOTE \tAnisotropic distributions do exist in near-Earth space due to geomagnetic shielding (see clause 9.2.4) and in the early stages of a SPE, where particles arrive along interplanetary field lines. The direction of the interplanetary magnetic field can be variable and not along the Earth-Sun direction. An isotropic distribution is assumed due to a lack of knowledge for specific events."]
["ECSS-E-ST-10-04C","ECSS - Superseded v1.0","9.2.4a","Requirement","ECSS-E-ST-10-04_0760076",1,"Created","The minimum energies, i.e. cut-off energies, necessary for ions to penetrate to a geographic location shall be calculated with one of the following methods:\n¾\tStørmer’s theory [RN.20]\n¾\tMAGNETOCOSMICS [RN.21]\n¾\tThe method given by Smart and Shea in [RN.22]\n¾\tStassinopoulos & King: no geomagnetic shielding for McIlwain L-shells greater than 5 RE [RN.23]\n¾\tNo geomagnetic shielding for a conservative estimate."]
["ECSS-E-ST-10-04C","ECSS - Superseded v1.0","10.2.1c","Requirement","ECSS-E-ST-10-04_0760086",1,"Created","The directional and velocity distributions of the space debris and meteoroid fluxes shall be included in the impact risk assessment."]
["ECSS-E-ST-10-04C","ECSS - Superseded v1.0","10.2.3a","Requirement","ECSS-E-ST-10-04_0760095",1,"Created","The MASTER-2005 flux model [RN.26] shall be used together with the following input parameters: \n1.\tMASTER-2005’s latest reference epoch of May 2005 for mission periods after May 2005.\n2.\tThe size interval given in terms of diameter.\n3.\tAll sources included. \nNOTE \tAccess points for the ESA Master model and its patches are defined in Annex J. Model characteristics, uncertainties, some general aspects and other space debris flux models are discussed in Annex J as well. "]
["ECSS-E-ST-10-04C","ECSS - Superseded v1.0","10.2.5a","Requirement","ECSS-E-ST-10-04_0760105",1,"Created","For the translation of flux into number of impacts N, a linear increase of N with exposed area and with exposure time shall be used, as follows:\n \nWhere:\nF \tis the number of impacts per unit area;\nA \tis the total exposed area;\nT \tis the exposure time."]
["ECSS-E-ST-10-04C","ECSS - Superseded v1.0","10.2.5c","Requirement","ECSS-E-ST-10-04_0760108",1,"Created","The probability of exactly n impacts occurring in the corresponding time interval shall be determined according to the expression: \n"]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","4.1.2d","Requirement","ECSS-E-ST-20_0020004",1,"Created","The application of the nominal signals or a faulty signal (as defined in the general design and interface requirements document) to an un-powered interface shall not cause damage to that interface.\n    NOTE In case verification by analysis is not conclusive a complementary verification by test is necessary."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","4.1.3g","Requirement","ECSS-E-ST-20_0020013",1,"Created","In case of critical commands of category 1 and 2, at least two physically independent electrical barriers, including associated control circuits, are mandatory for arming and executing the command. \n    NOTE 1 For criticality categories, see ECSS-Q-ST-30 or ECSS-Q-ST-40.\n    NOTE 2 Mechanical barriers can be considered.\n    NOTE 3 Physically independent electrical barriers and associated control circuits are the ones not sharing any hardware function and without risk of reciprocal failure propagation."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","4.2.1c","Recommendation","ECSS-E-ST-20_0020387",1,"Created","Provision 4.2.1b should be met via redundant harness and physically separated connectors."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","4.2.1k","Requirement","ECSS-E-ST-20_0020031",1,"Created","In case of signal cross-strapping, no single failure of either interface circuit shall propagate to the other one."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","4.2.1v","Requirement","ECSS-E-ST-20_0020042",1,"Created","SEE shall not activate protection circuits of essential functions. \n    NOTE Mitigation techniques can be implemented to avoid such phenomena: filtering, majority voting, etc"]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","4.2.3c","Recommendation","ECSS-E-ST-20_0020392",1,"Created","The test connector covers should be metallic or metallized and grounded to structure."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","4.2.3l","Requirement","ECSS-E-ST-20_0020060",1,"Created","Provision shall be taken to avoid arcing or short circuits in connectors.\n    NOTE For example: unused pins, placed between positive and return lines; specific connector design."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","4.2.4g","Requirement","ECSS-E-ST-20_0020070",1,"Created","The redundancy of parts and functions, which failure can lead to the loss of the mission or human injury, shall be verified by test simulating the failure event."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","4.2.4k","Requirement","ECSS-E-ST-20_0020074",1,"Created","Hot redundant functions and protection functions shall be tested up to the highest possible level of integration of the unit."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","4.2.6b","Requirement","ECSS-E-ST-20_0020081",1,"Created","The uniformity of the performance characteristics and dimensions of the units shall enable equipment interchange without unforeseen adjustments and recalibration."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","5.2.2.2c","Requirement","ECSS-E-ST-20_0020092",1,"Created","A power budget shall be established based on the peak power values and an energy budget based on the average power values for all mission phases."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","5.4a","Requirement","ECSS-E-ST-20_0020100",1,"Created","The electrical power interface between the solar array(s) and the power control units and between batteries and power control units shall\n    1. be defined, and \n    2. result in the specification of the input impedance seen by the power conditioning units."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","5.5.2e","Requirement","ECSS-E-ST-20_0020109",1,"Created","The solar array design shall be such that charging phenomena do not degrade the performance of the solar array below the requirements specified in 5.5.2a and 5.5.2c.\n    NOTE Good practices in accordance with the present state of the art, are to:\n        · limit the differential voltage in between cells to 30 V in all conditions if the minimum accepted gap between adjacent non-directly connected cells is 0,5 mm;\n        · implement string blocking diodes;\n        · have a coverglass extending beyond the solar cell limits."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","5.5.2q","Requirement","ECSS-E-ST-20_0020121",1,"Created","Solar cells shall be protected against any deleterious reverse-bias conditions."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","5.5.3g","Requirement","ECSS-E-ST-20_0020128",1,"Created","For recently developed solar cells and produced in large scale, the string current calculation shall include as a random parameter the increase of solar cell performance."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","5.5.3i","Requirement","ECSS-E-ST-20_0020130",1,"Created","Shadowing and hot spot phenomena shall be analysed."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","5.6.2d","Requirement","ECSS-E-ST-20_0020139",1,"Created","In case verification by analysis of 5.6.2c is not conclusive a complementary verification by test shall be performed."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","5.6.2m","Requirement","ECSS-E-ST-20_0020148",1,"Created","Battery thermal design shall ensure that:\n    1. maximum and minimum qualification temperature of cell operation under intended cycling conditions are not exceeded;\n    2. maximum qualification temperature gradients between different parts of the same cell and between two cells in a battery are not exceeded."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","5.6.4b","Requirement","ECSS-E-ST-20_0020158",1,"Created","For the procurement of cells and batteries the manufacturer shall supply a user manual in conformance with Annex D."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","5.6.5.2d","Recommendation","ECSS-E-ST-20_0020398",1,"Created","The failure of one or more cells within a battery due to imbalance in the state of charge, temperature or other parameter between cells should be prevented by the battery control electronics."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","5.7.2h","Requirement","ECSS-E-ST-20_0020177",1,"Created","A fully regulated bus shall keep its nominal value in steady state within ± 0,5 % of the bus voltage at the main regulation point. "]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","5.7.2q","Requirement","ECSS-E-ST-20_0020186",1,"Created","During integration phase the power system shall be able to start up from any of its power sources irrespective of the connection of the other power source."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","5.7.3g","Requirement","ECSS-E-ST-20_0020195",1,"Created","The battery charge current and end of charge control shall be autonomous and one fault tolerant (two failure tolerant for manned mission). "]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","5.7.5b","Requirement","ECSS-E-ST-20_0020205",1,"Created","The phase margin of converters and regulators not belonging to the spacecraft power system shall be at least 50° and the gain margin 10 dB for worst case end-of-life conditions with representative loading. \n    NOTE Rationale for this requirement:\nThe condition expressed in requirements 5.7.5a and 5.7.5b assumes that the converter has a monotonic decreasing transfer function for which the sufficient condition of the Nyquist criterion can be applied. It indirectly encourages the designer to make designs for which the verification of the stability is simple. A higher quality is used for converters driving the bus quality, and in particular 60° is selected to minimize the “overshoot” in the response."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","5.7.6b","Requirement","ECSS-E-ST-20_0020213",1,"Created","No load shall generate a spurious response that can damage itself or any other equipment during bus voltage variation, up or down, at any ramp rate, and over the full range from zero to maximum bus voltage."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","5.8.1a","Requirement","ECSS-E-ST-20_0020216",1,"Created","The primary power source shall be grounded to the spacecraft structure at the star reference point with a connection capable of sustaining the worst case fault current."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","5.8.1j","Requirement","ECSS-E-ST-20_0020225",1,"Created","Equipment connected to independent, redundant power buses shall ensure that:\n    1. for unmanned missions, no single failure causes the loss of more than one power bus;\n    2. for manned missions two failures do not cause the loss of more than one power bus ."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","5.8.2b","Requirement","ECSS-E-ST-20_0020233",1,"Created","With the exception of the solar array, routing of power lines shall be near ground."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","5.10b","Requirement","ECSS-E-ST-20_0020244",1,"Created","Non pressurised and non potted high voltage equipment shall be designed and manufactured to avoid discharge phenomena according to Pashen curves valid for its specified pressure range."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","5.11.2c","Requirement","ECSS-E-ST-20_0020251",1,"Created","FMECA shall be performed and based on the failure modes previously defined at component level."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","6.3.2.2a","Requirement","ECSS-E-ST-20_0020263",1,"Created","The electromagnetic environment seen by the spacecraft and the EMC requirements during the pre-launch and launch phases shall be according to those described in the applicable launchers user's manuals.\n    NOTE Specific EMC requirements during the pre-launch and launch phase are described in an Interface Control document established on a contractual basis between the launching company and the customer."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","6.3.4.3c","Requirement","ECSS-E-ST-20_0020273",1,"Created","Provision shall be made such that an unintended action does not result."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","6.3.7.3a","Requirement","ECSS-E-ST-20_0020281",1,"Created","On the basis of the attitude control requirements, the supplier shall derive magnetic requirements for the spacecraft so as to limit transient, diurnal and secular torques. "]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","6.3.8.2a","Requirement","ECSS-E-ST-20_0020284",1,"Created","A controlled ground reference concept, including the definition of circuit and unit categories shall be specified and agreed with the customer for the spacecraft prior to initial release of the EMC control plan."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","7.2.1.3a","Requirement","ECSS-E-ST-20_0020295",1,"Created","Antennas are in general single point failure elements; therefore their failure rates shall be agreed with the customer, specified and demonstrated.\n    NOTE To improve the failure rate, special precautions in the redundancy architecture are commonly taken to cover the failures of active elements."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","7.2.2.2.3b","Requirement","ECSS-E-ST-20_0020303",1,"Created","The effects of antenna support structures on the main RF wave propagation path shall be quantified and the impact on performance assessed. "]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","7.2.2.3.2a","Requirement","ECSS-E-ST-20_0020313",1,"Created","Reflective properties (losses, depolarisation, and diffusivity) of the materials and composites used shall be quantified and their impact on antenna performances assessed."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","7.2.2.3.4c","Requirement","ECSS-E-ST-20_0020322",1,"Created","In all RF BFN structures having a central conductor (ideally insulated), the thermal power generated by Joule effect on the conductor itself shall be quantified and its impact on antenna performances assessed. "]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","7.2.2.4.1a","Requirement","ECSS-E-ST-20_0020331",1,"Created","The level of passive inter-modulation products generated by the antenna shall be quantified and their impact on antenna performances assessed. \n    NOTE 1 See clause 7.4 for further details.\n    NOTE 2 Ferro-magnetic materials and metal-to-metal junctions are the most common non-linear elements in antennas."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","7.2.2.4.1c","Requirement","ECSS-E-ST-20_0020333",1,"Created","Thermally induced changes of dimension and shape in all metallic antenna parts shall be quantified and their impact on antenna performances assessed."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","7.2.3.1b","Requirement","ECSS-E-ST-20_0020342",1,"Created","It shall be demonstrated that the generation of passive inter-modulation products that can occur at the antenna ports is below the specified limits agreed with the customer."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","7.3.3.1b","Requirement","ECSS-E-ST-20_0020351",1,"Created","For those components and equipments which design does not allow operating them over the full pressure range the following action shall be taken:\n    1. specify the applicable pressure range and gas properties, \n    2. ensure that the design and manufacturing is such to avoid discharge phenomena according to Pashen curves valid for its specified pressure range and gas properties."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","7.4.4c","Requirement","ECSS-E-ST-20_0020361",1,"Created","The test frequencies, number of carriers and power levels of these carriers shall be those as identified in 7.4.3b."]
["ECSS-E-ST-20C","ECSS - Superseded v1.0","B.2.1a","Requirement","ECSS-E-ST-20_0020369",1,"Created","The EMEVP shall contain a description of the purpose, objective, content and the reason of prompting its preparation."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","4.1a","Requirement","ECSS-E-ST-35-06_0200001",1,"Created","This standard shall only apply to propulsion systems using Hydrazines, MON, Propane, Butane, Nitrogen, Helium, Xenon as propellants."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","4.1j","Requirement","ECSS-E-ST-35-06_0200010",1,"Created","All components, subsystems, systems or related equipment for use in ground support equipment and spacecraft requiring cleaning shall be\n    1. cleaned to the specified cleanliness level, in conformance with the CRA produced in conformance with Annex A, \n    2. inspected in conformance with Annex B."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","4.2.2.2b","Recommendation","ECSS-E-ST-35-06_0200382",1,"Created","Tubings and manifolds should avoid blind holes and dead ends,"]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","4.2.2.3i","Recommendation","ECSS-E-ST-35-06_0200386",1,"Created","A valve or regulator assembly should allow for the integration of protective filters after the final cleaning of the unit has been performed and verified in conformance with the CTS produced in conformance with Annex B."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","4.2.2.7a","Requirement","ECSS-E-ST-35-06_0200037",1,"Created","The deposition of NVR on catalyst beds shall be analysed and reported.\n    ","NOTE See Annex A."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","4.2.3c","Requirement","ECSS-E-ST-35-06_0200040",1,"Created","Filtration rate and capacity requirements shall include the flight operation and the contamination introduced by integration and testing at higher build level. \n    ","NOTE See Annex A."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","4.3.4b","Requirement","ECSS-E-ST-35-06_0200055",1,"Created","Tubing, manifolds and transition joints shall have passed all contaminating handling steps before final cleaning, e.g. bending, flaring, cutting to length and contaminating inspections."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","4.3.4f","Requirement","ECSS-E-ST-35-06_0200059",1,"Created","Component interiors shall be protected by internally plugging the tubing stud in case of acid pickling.\n    ","NOTE For example, valves."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","4.3.4o","Requirement","ECSS-E-ST-35-06_0200068",1,"Created","The joining process shall not introduce contamination into the critical surface area or bring contaminants into contact with propellants, pressurants or simulation fluids."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","4.3.5f","Requirement","ECSS-E-ST-35-06_0200075",1,"Created","It shall be determined which environmental classes apply to 4.3.5c and 4.3.5e.\n    ","NOTE See Annex A."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","4.3.6e","Requirement","ECSS-E-ST-35-06_0200087",1,"Created","It shall be determined which environmental class applies to requirement 4.3.6d.\n    ","NOTE See Annex A."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","4.3.7a","Requirement","ECSS-E-ST-35-06_0200089",1,"Created","The final rinsing solution shall meet or exceed the cleanliness requirements for which they are intended. "]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","4.4.1g","Requirement","ECSS-E-ST-35-06_0200098",1,"Created","In cases where the flow systems, or sections thereof (propellant or pressurant), consist of more than one line size, the smallest flow system size shall specify the selection."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","4.4.3c","Requirement","ECSS-E-ST-35-06_0200107",1,"Created","Dryness from other liquids (e.g. IPA, HFE) shall correspond to a vapour concentration in the purge gas \n    1. For chemical propulsion systems the effluent gas liquid vapour content to be less than 10 ml/l for individual components and systems,\n    2. For electrical propulsion systems using Xenon the effluent gas moisture content to be less than 10 ml/l for individual components and systems."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","4.4.4j","Requirement","ECSS-E-ST-35-06_0200117",1,"Created","It shall be verified that the cleaning fluids meet their specifications. "]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","4.6c","Requirement","ECSS-E-ST-35-06_0200126",1,"Created","The cleanliness code and the established particulate class, sub-class and level shall be used to specify to the cleaning facility the desired level of cleanliness. "]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","5.1h","Requirement","ECSS-E-ST-35-06_0200136",1,"Created","The cleaning fluids shall be compatible with the components being cleaned.\n    ","NOTE 1 See ECSS-E-ST-35-10.\nNOTE 2 Solvents identified in Annex D as having low threshold limit values are not suitable for cleaning processes conducted in enclosed environments, such as clean rooms, due to their toxicity unless the facility is especially designed for their use."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","5.2.2e","Requirement","ECSS-E-ST-35-06_0200145",1,"Created","Components obstructing precision cleaning due to blocking portions of a system causing the following, shall be removed and replaced:\n    1. entrapment of liquids,\n    2. incompatibility with the required cleaning process."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","5.3.2.1b","Requirement","ECSS-E-ST-35-06_0200154",1,"Created","Mechanical pre-cleaning shall be performed before or during chemical cleaning."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","5.3.3.1c","Requirement","ECSS-E-ST-35-06_0200164",1,"Created","To avoid corrosion and etching, passivation and neutralising solutions shall be used as a supplementary process to mechanical, acid and alkaline cleaning."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","5.4.1d","Requirement","ECSS-E-ST-35-06_0200172",1,"Created","For precision cleaning, clause 4.6 shall apply."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","5.4.1g","Requirement","ECSS-E-ST-35-06_0200175",1,"Created","Assembled items that do not lend themselves to this type of treatment shall have been treated prior to assembly. "]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","5.5.1e","Requirement","ECSS-E-ST-35-06_0200184",1,"Created","The selected temperature for drying from liquids shall be within the operational temperature range of the liquid."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","5.5.3.2a","Requirement","ECSS-E-ST-35-06_0200192",1,"Created","The quantitative analysis reliability sample shall consist of a minimum of 5 % of the items dried but not less than one sample from each group of items dried. "]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","5.5.3.4e","Requirement","ECSS-E-ST-35-06_0200203",1,"Created","An increase in the halogen, alcohol or hydrocarbon concentration of 5 ml/l or more in the drying gas shall necessitate additional drying prior to packaging or of the application of protective coatings. \n    ","NOTE 1 Due to the time for evaporation of liquids in a closed volume, the measurements of dryness need be timed properly.\nNOTE 2 The reliability of the drying procedure for items subjected to liquids during cleaning or drying procedures can be established."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","5.5.5.3b","Requirement","ECSS-E-ST-35-06_0200210",1,"Created","The drying time, vacuum level and temperature for the hardware shall be specified."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","6.1.1b","Requirement","ECSS-E-ST-35-06_0200222",1,"Created","An external light source or boroscope shall be used to examine internal surfaces."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","6.1.2c","Requirement","ECSS-E-ST-35-06_0200231",1,"Created","When tested, the pH shall range from 5,0 to 8,0 and reported in conformance with Annex C."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","6.2.2g","Permission","ECSS-E-ST-35-06_0200397",1,"Created","Alternatively to 6.2.2f, the polymer components may be vacuum dried as described in 6.2.6 and 6.2.7."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","6.2.3c","Requirement","ECSS-E-ST-35-06_0200242",1,"Created","In cases where all critical surfaces are less than 0,1 m2 a minimum of a 100 ml sample of test liquid shall be used."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","6.2.6.3c","Requirement","ECSS-E-ST-35-06_0200257",1,"Created","All items shall meet the dryness requirements of clause 4.4.3."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","6.3.2a","Requirement","ECSS-E-ST-35-06_0200261",1,"Created","All temporary hardware necessary to perform or validate the cleaning process shall be compatible with the processing materials and the subsystem, system or other related field equipment that is to be cleaned."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","6.4.1a","Requirement","ECSS-E-ST-35-06_0200271",1,"Created","The results of the dryness verification shall be reported in conformance with Annex C."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","6.4.4a","Requirement","ECSS-E-ST-35-06_0200280",1,"Created","For batches of hardware processed together (e.g. manifolds or component parts) a representative sample of a minimum of 5% shall be tested."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","7.2b","Requirement","ECSS-E-ST-35-06_0200289",1,"Created","All the plastic film of one type, e.g. one size and one configuration, tubing, flat roll stock, sheet and fabricated bags, offered by one manufacturer at one time, shall be considered to be one lot."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","7.5.3a","Requirement","ECSS-E-ST-35-06_0200295",1,"Created","Fabricated bags shall be sealed across the open end. "]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","7.5.4b","Requirement","ECSS-E-ST-35-06_0200300",1,"Created","The following rinsing procedure shall be used:\n    1. introduce the test liquid into the sealed bag through the previously cut opening;\n    2. close the bag by folding over the cut corner;\n    3. agitate the test liquid within the bag for a minimum of 15 s, wetting all surfaces;\n    4. pour the used test liquid into a precision-cleaned beaker, taking care to exclude airborne contamination;\n    5. analyse the test fluid for particulate population in conformance with Table 4-1 sub-class I."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","8.1i","Requirement","ECSS-E-ST-35-06_0200309",1,"Created","If desiccants or humidity indicators are required for additional corrosion protection, they shall be placed in the outer bag. "]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","10.1c","Requirement","ECSS-E-ST-35-06_0200319",1,"Created","Tubing, piping and hoses are flushed in accordance with either Method I or Method II (see 11.1.2 Method I “Liquid Flush Test” and 11.1.3 Method II “Liquid Flow Test”). "]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","11.1.2a","Requirement","ECSS-E-ST-35-06_0200327",1,"Created","The liquid flush test shall be performed for particle population and NVR remaining on critical surfaces of items cleaned in a controlled environment."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","11.1.4a","Requirement","ECSS-E-ST-35-06_0200338",1,"Created","Systems or components which are not allowed to be flushed with liquids shall be cleaned by purging with gas as follows:\n    1. in conformance with clause 5.5.2.\n    2. filtered through a 2µm filter.\n    3. for components with a critical area £ 0,1 m2, an amount of gas equivalent to 100 l at 0,1 MPa and 293 K (standard conditions) with a minimum flow rate of 10 l/min (standard conditions).\n    4. for large subsystems or systems a minimum of 1000 l gas (standard conditions) with a minimum flow rate of 100 l/min (standard conditions).\n    5. for components and small subsystems with a critical area > 0,1 m2, 1000 l/m2 of critical surface area using gas with a flow rate of 100 l/min (standard conditions) to 1000 l/min (standard conditions).\n    6. the flow rate is less than the maximum allowable flow rate specified for the hardware.\n    7. the static pressures does not exceed the operating limits of the hardware.\n    8. the gas sample is counted for particles using:\n        (a) ECSS-E-ST-35-06 clause 12.1 with a gridded membrane filter of £ 2 mm, or\n        (b) a calibrated automatic gas particle counter.\n    9. repeated sampling is performed until two successive readings comply with the required level in conformance with clause 4.4.1, Table 4-1. "]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","A.2.1<3>b","Requirement","ECSS-E-ST-35-06_0200347",1,"Created","The CRA shall include any additional term, definitions, abbreviated terms and symbol used."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","A.2.1<5>f","Requirement","ECSS-E-ST-35-06_0200356",1,"Created","In addition to particulate and NVR specifications the definition of the required dryness level and packaging requirements (protections) shall be presented."]
["ECSS-E-ST-35-06C Rev.1","ECSS - Superseded v1.0","B.2.1<5>a","Requirement","ECSS-E-ST-35-06_0200366",1,"Created","The processes and related procedures for cleaning and cleanliness verification shall be described. "]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","5.1a","Requirement","ECSS-E-ST-32-01_0810001",1,"Created","A fracture control programme shall be implemented by the supplier for space systems and their related GSE in conformance with this Standard, when required by ECSS-Q-ST-40 or the NASA document NSTS 1700.7, incl. ISS Addendum (clause 208.1)."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","5.1d","Requirement","ECSS-E-ST-32-01_0810004",1,"Created","Items for which implementation of fracture control programme is required shall be selected in conformance with Figure 5-1. "]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","6.2.1a","Requirement","ECSS-E-ST-32-01_0810019",1,"Created","Each PFCI shall be damage tolerant."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","6.3.1b","Requirement","ECSS-E-ST-32-01_0810023",1,"Created","The methodology applied for evaluation by test shall be subject to customer approval.\n    NOTE Customer approval is specified, because evaluation by test is not specified to the same level of detail than evaluation by analysis. Evaluation by test is similar to evaluation by analysis, where appropriate and not specified otherwise."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","6.3.3a","Requirement","ECSS-E-ST-32-01_0810032",1,"Created","The evaluation procedure for a PFCI considered as fail-safe item shall be as specified in Figure 6-4."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","6.3.3h","Requirement","ECSS-E-ST-32-01_0810039",1,"Created","For limited life items, a reduced service life shall be verified, which allows replacement of the items when:\n    1. Less than 2 flight lives remain, for manned Shuttle-mission.\n        NOTE This is to allow for a potential aborted mission and subsequent re-launch.\n    2. Less than one flight life remains, for any other case."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","6.3.5.2b","Requirement","ECSS-E-ST-32-01_0810049",1,"Created","The maximum tensile stress based on net cross-sectional area in the part at limit load shall be no greater than 30 percent of the ultimate tensile strength for the metal used."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","6.4.3a","Requirement","ECSS-E-ST-32-01_0810055",1,"Created","The analysis of all PFCIs, FCIs, contained and restrained items shall be documented in a fracture control analysis report in conformance with ECSS-E-ST-32 ‘Fracture control analysis (FCA) - DRD’."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","7.1b","Requirement","ECSS-E-ST-32-01_0810060",1,"Created","The following data shall be made available in order to enable crack growth prediction and critical crack-size calculation:\n    1. Stress distribution\n    2. Load spectra\n    3. Material properties\n    4. Initial crack size\n    5. Stress intensity factor solutions."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","7.2.2c","Requirement","ECSS-E-ST-32-01_0810069",1,"Created","In cases where the most critical location or orientation of the initial crack is not obvious, the analysis shall consider a sufficient number of locations and orientations."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","7.2.5e","Requirement","ECSS-E-ST-32-01_0810079",1,"Created","Lower boundary values shall be derived as follows:\n    1. values with a 90% probability and 95% confidence level of being exceeded (B-value as defined in DOT/FAA/AR-MMPDS), or\n    2. in cases where insufficient test data are available: 70 % of the mean values."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","7.2.6e","Requirement","ECSS-E-ST-32-01_0810088",1,"Created","For automatic hole preparation indicated in 7.2.6d, an initial crack size shall be assumed based on the worst of the following:\n    1. The initial crack size determined by the NDI performed before hole preparation, or\n    2. The potential damage from hole preparation operations, as defined below:\n        (a) For drilled holes with driven rivets, the assumed defect due to potential damage is a 0,13 mm length crack through the thickness at one side of the hole.\n        (b) For fastener holes other than those for driven rivets, where the material thickness is equal to or less than 1,3 mm, the assumed fabrication defect due to potential damage is a 1,3mm length crack through the thickness at one side of the hole.\n        (c) For fastener holes other than those for driven rivets, where the thickness is greater than 1,3 mm, the initial crack size due to potential damage is a 1,3 mm radius corner crack at one side of the hole."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","7.2.8c","Requirement","ECSS-E-ST-32-01_0810093",1,"Created","The complete loading spectrum shall be analytically imposed at least four (4) times in sequence, one after another."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","8.2.2.2b","Requirement","ECSS-E-ST-32-01_0810107",1,"Created","Fracture mechanics verification of metallic pressure vessels and metallic liners of COPV shall, when required in conformance with ECSS-E-ST-32-02, be performed in conformance with Figure 8-1 and clauses 6.3.2 and 7."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","8.2.3.2b","Requirement","ECSS-E-ST-32-01_0810116",1,"Created","The design shall be safe life to leakage."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","8.3.2b","Requirement","ECSS-E-ST-32-01_0810128",1,"Created","When the material properties specified in 8.3.2a are not available, they shall be derived by means of a test programme covering:\n    1. Ultimate and yield strength for all welding conditions used, including mechanical properties (as in 8.3.2a) in the presence of different misalignments, angles between joints or typical defects, and their consequences.\n    2. Fracture toughness KC, stress-corrosion cracking threshold KISCC, and crack propagation parameters for each type of thickness.\n    3. Young’s modulus for weld material:\n        (a) Evaluated by test only in those cases, where a significant amount of a second phase with a different modulus compared to the base material appears. \n        (b) If the microstructure with respect to the different phases does not change, the base material Young’s modulus applies also for weld material."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","8.4.1c","Requirement","ECSS-E-ST-32-01_0810136",1,"Created","Composite overwraps of COPV and other composite overwrapped pressurized hardware shall be in conformance with clause 8.2 and ECSS-E-ST-32-02, as minimum.\n    NOTE 1 This means that these composite PFCI do not need to be fully compliant with the detailed requirements of this clause 8.4\n    NOTE 2 For the attachments of pressurized hardware, which are not part of the pressurized shell, no special requirements are specified in 8.2 and ECSS-E-ST-32-02. Composite, bonded and sandwich attachment hardware follows the rules of this clause 8.4 to prevent catastrophic or critical hazards."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","8.4.2.1c","Requirement","ECSS-E-ST-32-01_0810139",1,"Created","The effects of the potential manufacturing defects on the structural integrity shall be established, documented and verified.\n    NOTE Examples of such effects are strength, stability, and fatigue."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","8.4.3.2d","Requirement","ECSS-E-ST-32-01_0810148",1,"Created","For the type and maximum magnitude of the threat during each event that can cause mechanical damage, as identified in 8.4.3.2a, 8.4.3.2b and 8.4.3.2c, the resulting mechanical damage shall be identified with its type and size or level.\n    NOTE 1 Types of damage are for example: impact damage (including delamination, broken fibres and perforation), scratch, and abrasion.\n    NOTE 2 Damage size or level can be characterised, for example, by energy level for impact, or depth and length for a scratch."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","8.4.4.2a","Requirement","ECSS-E-ST-32-01_0810156",1,"Created","A safe life item shall meet all the requirements for the safe life approach described in clauses 6.2, 6.3, and 10.7.\n    NOTE See also Figure 6-3."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","8.4.4.3e","Requirement","ECSS-E-ST-32-01_0810167",1,"Created","For a low-risk fracture item the strain at the limit load shall be below the damage tolerance threshold strain. "]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","8.5f","Requirement","ECSS-E-ST-32-01_0810174",1,"Created","Test loads on the non-metallic item shall not exceed 80% percent of ultimate strength."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","8.8a","Requirement","ECSS-E-ST-32-01_0810186",1,"Created","Fasteners smaller than diameter 5 mm (or 3/16”) shall not be used in safe life applications."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","9b","Requirement","ECSS-E-ST-32-01_0810195",1,"Created","Where validated properties for analysis are not available, or available properties are not validated by standard or other test procedures agreed with the customer, the statistical basis for average and minimum values shall be established by tests."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","10.3.1e","Requirement","ECSS-E-ST-32-01_0810203",1,"Created","Rolled threads shall not be etched.\n    NOTE This refers to both the inspection for cracks of safe life fasteners (where eddy current inspection is preferred in conformance with 8.8f), and penetrant inspection of other fasteners which is sometimes performed as part of process control."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","10.3.1h","Requirement","ECSS-E-ST-32-01_0810206",1,"Created","Inspection of all welds shall include a search for surface flaws as well as embedded flaws."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","10.3.3d","Requirement","ECSS-E-ST-32-01_0810221",1,"Created","Where etching or inspection cannot be performed on the finished part, that etching and penetrant-inspection shall be performed at the latest practical stage of finishing.\n    NOTE For example, before final machining of parts with precision tolerances, or at the assembly level before holes are drilled."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","10.3.3h","Requirement","ECSS-E-ST-32-01_0810225",1,"Created","For transparent optical elements, a standard initial crack size of 2,54 mm length shall be used when visual inspection with 10 times or higher magnification is performed with lighting applied at right angles to the actual flaw orientation.\n    NOTE 1 Example of such transparent optical elements are windows and lenses.\n    NOTE 2 This visual inspection method detects both surface and embedded flaws."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","10.4.2.1b","Requirement","ECSS-E-ST-32-01_0810230",1,"Created","For the standard NDI level of inspection one or more of the following standard industrial NDI techniques applied to metallic materials shall be used: \n    NOTE 1 Fluorescent penetrant\n    NOTE 2 X-ray\n    NOTE 3 Ultrasonic\n    NOTE 4 Eddy current, or\n    NOTE 5 magnetic particle."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","10.4.2.3d","Requirement","ECSS-E-ST-32-01_0810244",1,"Created","Where proof testing of a flight item is performed as a screening or inspection technique for cracks, which are larger than the initial cracks used in the analytical life prediction, proof test procedures shall be submitted to the customer for approval prior to the start of testing.\n    NOTE 1 Proof testing can result in the application of loads substantially in excess of those usually imposed on flight hardware in order to screen for cracks of sufficiently small size. This can result in significant risk to damage and reject otherwise acceptable hardware.\n    NOTE 2 Requirements for crack growth and critical crack size analysis are specified in clause 7. A significant amount of test data can be necessary to validate or complement the analysis results in order to limit the risk of damage to flight hardware. Advanced non-linear fracture analysis methodology is normally applied to accurately predict the behaviour of cracks under proof loading, except for e.g. thick-walled items with part-through cracks where the minimum remaining ligament (material thickness ahead of crack tip) is greater than 2,5 (K1c/ sy)2. A crack screening proof test of thin-walled items is generally not recommended because of the increased risk of damage due to stable crack growth during the proof test. "]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","10.4.3.3a","Requirement","ECSS-E-ST-32-01_0810253",1,"Created","Ultrasonic inspection shall be in conformance with SAE AMS-STD-2154 Class A as a minimum. "]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","10.4.3.4b","Requirement","ECSS-E-ST-32-01_0810259",1,"Created","A minimum signal-to-noise ratio of 3:1 shall be achieved for standard NDI."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","10.4.3.5c","Requirement","ECSS-E-ST-32-01_0810264",1,"Created","Interface surface finish shall be Ra = 3,2 mm or lower."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","10.5.2.2.2a","Requirement","ECSS-E-ST-32-01_0810277",1,"Created","In the cases other than those addressed by 10.5.1a, the procedure shall be written by an expert for the NDI method.\n    NOTE For example, the procedure can be written by an operator practicing this method."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","10.6.2b","Requirement","ECSS-E-ST-32-01_0810283",1,"Created","Each fracture-critical item shall be traceable by its own unique serial number."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","10.7.2.1.1b","Requirement","ECSS-E-ST-32-01_0810291",1,"Created","The analysis or test shall be performed as follows:\n    1. Define the dimensions and location of the detected defect conservatively (e.g. for a surface crack the length and depth).\n    2. In the case of irregular defect shapes or grouped defects, make a recharacterisation for the analytical prediction (in the case of metallic part) or for test with induced defect (for metallic or composite part).\n        NOTE For metallic parts, flaw characterization as proposed by BS 7910 or ASME boiler and pressure vessel code Section XI, article IGA-3000 can be applied.\n    3. Demonstrate by analysis that the stresses used are conservative.\n        NOTE Improved analysis methods, which are subjected to customer approval, can be needed to achieve this."]
["ECSS-E-ST-32-01C Rev. 1","ECSS - Superseded v1.0","10.7.3a","Requirement","ECSS-E-ST-32-01_0810302",1,"Created","If the origin of a detected defect is not uniquely determined and eliminated, and regular occurrence of significant crack-like defects is not excluded by means of improvement of the manufacturing process, an improved NDI method approved by the customer shall be used, such that it provides a probability higher than 90% of detection of unacceptable defects. "]
["ECSS-E-ST-50-01C","ECSS - Superseded v1.0","5.2c","Recommendation","ECSS-E-ST-50-01_0240059",1,"Created","If differential encoding (i.e. conversion from NRZ-L to NRZ-M) is used at the sending end, the conversions should be as follows:\n     - the conversion is performed at the input to the convolutional encoder;\n     - the corresponding conversion at the receiving end from NRZ-M to NRZ-L is performed at the output of the convolutional decoder.\n        ","NOTE 1 This prevents avoidable link performance loss.\nNOTE 2 When suppressed-carrier modulation systems are used, NRZ-M or NRZ-L can be used as a modulating waveform. In NRZ-M a data \"1\" is represented by a change in level and a data \"0\" is represented by no change in level. In NRZ-L a data \"1\" is represented by one of two levels, and a data \"0\" is represented by the other level.\nNOTE 3 When a fixed pattern (the fixed part of the convolutionally encoded attached sync marker) in the symbol stream is used to provide node synchronization for the Viterbi decoder, the modulating waveform conversion can cause a modification of the pattern."]
["ECSS-E-ST-50-01C","ECSS - Superseded v1.0","6.2a","Requirement","ECSS-E-ST-50-01_0240007",1,"Created","For Reed-Solomon coding, the frame synchronization defined in clause 8 shall be used.\n    ","NOTE The reliability of the Reed-Solomon code depends on proper codeblock synchronization"]
["ECSS-E-ST-50-01C","ECSS - Superseded v1.0","6.4.2b","Requirement","ECSS-E-ST-50-01_0240022",1,"Created","The Reed-Solomon code with E=8 shall not be concatenated with one of the convolutional codes defined in clause 5."]
["ECSS-E-ST-50-01C","ECSS - Superseded v1.0","8.2.2a","Requirement","ECSS-E-ST-50-01_0240030",1,"Created","If the telemetry channel is uncoded, Reed-Solomon coded, or turbo coded, the code symbols comprising the ASM shall be attached directly to the encoder output without being encoded by the Reed-Solomon or turbo code. "]
["ECSS-E-ST-50-01C","ECSS - Superseded v1.0","8.2.3b","Requirement","ECSS-E-ST-50-01_0240033",1,"Created","For a turbo coding system, the ASM shall be acquired in the channel symbol domain (i.e. the code symbol domain of the turbo code)."]
["ECSS-E-ST-50-01C","ECSS - Superseded v1.0","9.3.2d","Requirement","ECSS-E-ST-50-01_0240048",1,"Created","The pseudo-random sequence shall not be exclusive-ORed with the ASM."]
["ECSS-E-ST-50-03C","ECSS - Superseded v1.0","5.1b","Requirement","ECSS-E-ST-50-03_0880002",1,"Created","The maximum length for a TM Transfer Frame shall be 2048 octets."]
["ECSS-E-ST-50-03C","ECSS - Superseded v1.0","5.1k","Requirement","ECSS-E-ST-50-03_0880011",1,"Created","On a physical channel that carries TM Transfer Frames, all the frames shall have the same Transfer Frame Version Number.\n    ","NOTE The TM Transfer Frames specified in this Standard do not share a physical channel with other types of frame."]
["ECSS-E-ST-50-03C","ECSS - Superseded v1.0","5.2.2.2b","Requirement","ECSS-E-ST-50-03_0880018",1,"Created","The Transfer Frame Version Number shall be contained within bits 0-1 of the Transfer Frame Primary Header."]
["ECSS-E-ST-50-03C","ECSS - Superseded v1.0","5.2.4d","Requirement","ECSS-E-ST-50-03_0880030",1,"Created","The Operational Control Field Flag shall be static in the associated master channel or virtual channel throughout a mission phase.\n    ","NOTE See clause 5.5.1."]
["ECSS-E-ST-50-03C","ECSS - Superseded v1.0","5.2.6b","Requirement","ECSS-E-ST-50-03_0880036",1,"Created","The Virtual Channel Frame Count shall be contained within bits 24-31 of the Transfer Frame Primary Header."]
["ECSS-E-ST-50-03C","ECSS - Superseded v1.0","5.2.7.1c","Requirement","ECSS-E-ST-50-03_0880041",1,"Created","The Transfer Frame Data Field Status shall consist of five fields, positioned contiguously, in the following sequence:\n    1. Transfer Frame Secondary Header Flag\t1 bit\n    2. Synchronization Flag\t\t\t1 bit\n    3. Packet Order Flag\t\t\t\t1 bit\n    4. Segment Length Identifier\t\t\t2 bits\n    5. First Header Pointer\t\t\t11 bits\n        ","NOTE 1 All these five fields are always present in a Transfer Frame Data Field Status.\nNOTE 2 This field indicates whether a secondary header is present and provides information relating to the data contained in the Transfer Frame Data Field."]
["ECSS-E-ST-50-03C","ECSS - Superseded v1.0","5.2.7.5a","Requirement","ECSS-E-ST-50-03_0880054",1,"Created","The Segment Length Identifier shall always be present in a Transfer Frame Data Field Status."]
["ECSS-E-ST-50-03C","ECSS - Superseded v1.0","5.2.7.6d","Requirement","ECSS-E-ST-50-03_0880060",1,"Created","If at least one packet starts in the Transfer Frame Data Field, the First Header Pointer shall contain the location of the first octet of the first packet that starts in the Transfer Frame Data Field. \n    ","NOTE If the last packet in the Transfer Frame Data Field of frame X spills over into frame Y of the same virtual channel (X<Y), the First Header Pointer in frame Y ignores the residue of the split packet and indicates the start of the first packet that starts in frame Y."]
["ECSS-E-ST-50-03C","ECSS - Superseded v1.0","5.3.1f","Requirement","ECSS-E-ST-50-03_0880069",1,"Created","The Transfer Frame Secondary Header shall consist of two fields, positioned contiguously, in the following sequence:\n    1. Transfer Frame Secondary Header Identification\t\t8 bits\n    2. Transfer Frame Secondary Header Data Field \t\t8, 16, ... or 504 bits\n        ","NOTE 1 Both fields are always present in a Transfer Frame Secondary Header.\nNOTE 2 The format of the Transfer Frame Secondary Header is shown in Figure 5-1"]
["ECSS-E-ST-50-03C","ECSS - Superseded v1.0","5.3.2.1c","Requirement","ECSS-E-ST-50-03_0880074",1,"Created","The Transfer Frame Secondary Header Identification shall comprise two fields, positioned contiguously, in the following sequence:\n    1. Transfer Frame Secondary Header Version Number\t2 bits\n    2. Transfer Frame Secondary Header Length\t\t6 bits\n        ","NOTE Both fields are always present in a Transfer Frame Secondary Header Identification."]
["ECSS-E-ST-50-03C","ECSS - Superseded v1.0","5.3.4.2d","Requirement","ECSS-E-ST-50-03_0880088",1,"Created","The use of the extended virtual channel frame count shall be associated with either a master channel or a virtual channel.\n    ","NOTE 1 If the extended virtual channel frame count is associated with a master channel, then the Transfer Frame Secondary Header of every frame on the master channel contains the extended count. However, the value of the extended count in a given frame is the value for the virtual channel to which the frame belongs.\nNOTE 2 If the extended virtual channel frame count is associated with a virtual channel, then the Transfer Frame Secondary Headers of other virtual channels can be absent or used for other purposes."]
["ECSS-E-ST-50-03C","ECSS - Superseded v1.0","5.4.2c","Requirement","ECSS-E-ST-50-03_0880092",1,"Created","If a Transfer Frame Secondary Header is present, the Transfer Frame Secondary."]
["ECSS-E-ST-50-03C","ECSS - Superseded v1.0","5.4.3.5d","Requirement","ECSS-E-ST-50-03_0880107",1,"Created","Any idle packets extracted from Transfer Frame Data Fields shall be discarded."]
["ECSS-E-ST-50-03C","ECSS - Superseded v1.0","5.4.4.2h","Requirement","ECSS-E-ST-50-03_0880115",1,"Created","Any Communications Link Control Word (see clause 5.5.3) extracted from the Operational Control Field of a recorded TM Transfer Frame shall not be processed by the real-time telecommand system."]
["ECSS-E-ST-50-03C","ECSS - Superseded v1.0","5.5.1c","Requirement","ECSS-E-ST-50-03_0880118",1,"Created","The Operational Control Field shall be associated with a master channel or a virtual channel.\n    ","NOTE Support at the receiving end for retrieving the Operational Control Field can be limited. In some cases, the receiving end can only support retrieval of the Operational Control Field associated with a master channel."]
["ECSS-E-ST-50-03C","ECSS - Superseded v1.0","5.5.4a","Requirement","ECSS-E-ST-50-03_0880127",1,"Created","If the Type Flag is ‘1’, the Operational Control Field shall contain a Type-2-Report."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","5.2.1d","Requirement","ECSS-E-ST-50-04_0890004",1,"Created","If the next lower sublayer below the segmentation sublayer is the transfer sublayer, and the segmentation sublayer at the sending end is generating TC Segments for a particular virtual channel, then all data units delivered by the transfer sublayer at the receiving end for that virtual channel shall be TC Segments.\n    ","NOTE TC Segments do not share a virtual channel with other data structures."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","5.2.2.2c","Requirement","ECSS-E-ST-50-04_0890011",1,"Created","The Sequence Flags shall be set as follows:\n    1. ‘01’ for the first segment of a user data unit;\n    2. ‘00’ for a continuing segment of a user data unit;\n    3. ‘10’ for the last segment of a user data unit;\n    4. ‘11’ no segmentation.\n        ","NOTE The Sequence Flags provide information about the sequential position of the segment to enable the receiving end to reassemble the user data units from a stream of segments. However, the flags do not provide a sequence count, so the reassembly process depends on the stream of segments being delivered in sequence and without omissions. The sequence-controlled service of the transfer sublayer can provide delivery in sequence and without omissions."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","5.2.3c","Requirement","ECSS-E-ST-50-04_0890018",1,"Created","The maximum length of the Segment Data Field is one octet less than the maximum length of a TC Segment.\n    ","NOTE The length of the Segment Data Field is variable."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","5.4.3a","Requirement","ECSS-E-ST-50-04_0890030",1,"Created","The blocking and deblocking functions shall be conducted independently for each virtual channel."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","5.4.6a","Requirement","ECSS-E-ST-50-04_0890039",1,"Created","The deblocking function shall extract the packets from the data units it receives."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","5.5.4.2b","Requirement","ECSS-E-ST-50-04_0890047",1,"Created","A pair of MAP connections shall consist of one MAP for data and one MAP for control."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","5.5.4.2e","Requirement","ECSS-E-ST-50-04_0890050",1,"Created","A TC Segment carrying user data shall have the MAP Identifier of the data MAP."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","6.2.1a","Requirement","ECSS-E-ST-50-04_0890065",1,"Created","The TC Transfer Frame shall consist of the major fields, positioned contiguously, in the following sequence:\n    1. Transfer Frame Primary Header\t5 octets\n    2. Transfer Frame Data Field\t\tvariable length\n    3. Frame Error Control Field\t\t2 octets\n        ","NOTE 1 All three fields are always present in a TC Transfer Frame.\nNOTE 2 Figure 6-1 illustrates the detailed format of the TC Transfer Frame."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","6.2.2.2a","Requirement","ECSS-E-ST-50-04_0890069",1,"Created","The Transfer Frame Version Number shall always be present in a Transfer Frame Primary Header."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","6.2.2.3c","Requirement","ECSS-E-ST-50-04_0890074",1,"Created","The Bypass Flag shall be set as follows:\n    1. ‘0’ for a type-A Transfer Frame;\n    2. ‘1’ for a type-B Transfer Frame."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","6.2.2.8a","Requirement","ECSS-E-ST-50-04_0890088",1,"Created","The Frame Length shall always be present in a Transfer Frame Primary Header."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","6.2.3b","Requirement","ECSS-E-ST-50-04_0890097",1,"Created","The Transfer Frame Data Field shall follow, without gap, the Transfer Frame Primary Header."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","6.2.4.1c","Requirement","ECSS-E-ST-50-04_0890103",1,"Created","The Frame Error Control Field shall have a length of two octets."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","6.3.1a","Requirement","ECSS-E-ST-50-04_0890108",1,"Created","The length of a CLCW shall be 4 octets."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","6.3.8b","Requirement","ECSS-E-ST-50-04_0890121",1,"Created","The No RF Available Flag shall always carry a true report of the status of the physical channel, even when other fields in the CLCW report the status of an inactive virtual channel.\n    ","NOTE The flag reports the status of the physical channel and therefore applies to all virtual channels."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","6.3.13a","Requirement","ECSS-E-ST-50-04_0890127",1,"Created","The FARM-B Counter field of the CLCW shall contain the two least significant bits of the internal counter used by FARM-1 to count the accepted type-B Transfer Frames.\n    ","NOTE 1 The FARM-1 maintains a counter which increments each time a type-B Transfer Frame is accepted.\nNOTE 2 This field can be used to verify that type-B Transfer Frames have been accepted. The verification process is not specified in this Standard. The field is not used by FOP-1.\nNOTE 3 The number of bits in the FARM-1 internal counter of accepted type-B Transfer Frames is implementation dependent. This field in the CLCW only carries the two least significant bits of the counter. This does not preclude the transmission in telemetry data of the full counter value."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","7.2.3.8.2b","Requirement","ECSS-E-ST-50-04_0890139",1,"Created","The values of PW and NW shall be set according to the following rule:\nPW = NW = W/2"]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","7.4.2.2d","Requirement","ECSS-E-ST-50-04_0890146",1,"Created","The directive qualifier shall take the value appropriate to the directive type as shown in Table 7-3.\n    ","NOTE A directive with an invalid directive type or directive qualifier is handled as an invalid directive."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","7.4.2.6.2a","Requirement","ECSS-E-ST-50-04_0890155",1,"Created","When FOP-1 suspends the AD service, it shall send an asynchronous notification signal with the notification type set to indicate a Suspend notification.\n    ","NOTE 1 The notification qualifier parameter of the signal is not used for a Suspend notification.\nNOTE 2 The Suspend_State variable, SS, takes a value corresponding to the state FOP-1 was in at the time it was suspended."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","7.4.3.2c","Requirement","ECSS-E-ST-50-04_0890159",1,"Created","The system of request identifiers shall be able to handle multiple requests awaiting confirm responses at the same time."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","7.5.4.2a","Requirement","ECSS-E-ST-50-04_0890174",1,"Created","If the back-end buffer is available, then FARM-1 shall:\n    1. Copy the FDU from the frame into the back-end buffer.\n    2. Signal an FDU Arrived Indication, with the FDU aborted indication not set."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","7.5.5b","Requirement","ECSS-E-ST-50-04_0890177",1,"Created","An FDU Arrived Indication shall carry the following parameters:\n    1. FDU\n    2. Virtual channel identification\n    3. FDU aborted indication\n        ","NOTE 1 The setting of the FDU aborted indication is specified in clauses 7.5.3.2 and 7.5.4.2.\nNOTE 2 In addition, the parameters can include a type identifier to indicate which service (AD or BD) was used to transfer the FDU."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","7.6.4b","Requirement","ECSS-E-ST-50-04_0890185",1,"Created","Following receipt of a Transmit Request for Frame signal from FOP-1, the lower procedures shall asynchronously send a Response signal with the response type set to one of the following values:\n    1. AD_Accept\n    2. AD_Reject\n    3. BC_Accept\n    4. BC_Reject\n    5. BD_Accept\n    6. BD_Reject.\n        ","NOTE 1 The response indicates acceptance or rejection of a request by the lower procedures. For example, AD_Accept means acceptance of a transmit request for a frame with type identifier AD.\nNOTE 2 The lower procedures delay sending an accept response until they are ready to receive the next transmit request for that frame type on that virtual channel.\nNOTE 3 The responses cause events E41 to E46 in the FOP-1 state table."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","7.9.2.5a","Requirement","ECSS-E-ST-50-04_0890200",1,"Created","If the Wait_Queue is empty, no processing shall be performed for purging the Wait_Queue."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","7.9.2.8a","Requirement","ECSS-E-ST-50-04_0890204",1,"Created","Transmit Unlock type-BC frame shall include the following:\n    1. Creating a new frame with an Unlock control command in the Transfer Frame Data Field.\n    2. Performing the Transmit type-BC frame action defined in clause 7.9.2.7 for the frame."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","7.9.2.17a","Requirement","ECSS-E-ST-50-04_0890213",1,"Created","Initialise shall include the following:\n    1. Purging the Sent_Queue.\n    2. Purging the Wait_Queue.\n    3. Setting the Transmission_Count to 1.\n    4. Setting Suspend_State (SS) to 0."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","8.2.3.1b","Requirement","ECSS-E-ST-50-04_0890224",1,"Created","The Error Control field shall be contained in bits 56 to 63 of the BCH codeblock."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","8.3.1a","Requirement","ECSS-E-ST-50-04_0890232",1,"Created","A CLTU shall consist of three major fields, positioned contiguously, in the following sequence:\n    1. Start Sequence\t16 bits\n    2. Encoded Data\tvariable length\n    3. Tail Sequence\t64 bits\n        ","NOTE All three fields are always present. Figure 8-2 shows the format of a CLTU."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","8.3.3b","Requirement","ECSS-E-ST-50-04_0890238",1,"Created","The Encoded Data field shall start at bit 16 of the CLTU."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","8.3.4b","Requirement","ECSS-E-ST-50-04_0890243",1,"Created","The Tail Sequence field shall \n    1. Have a length of 8 octets.\n    2. Be contained in the last 64 bits of the CLTU."]
["ECSS-E-ST-50-04C","ECSS - Superseded v1.0","9.2.1b","Requirement","ECSS-E-ST-50-04_0890256",1,"Created","The pattern of the acquisition sequence shall be alternating \"ones\" and \"zeroes\", starting with either a \"one\" or a \"zero\".\n    ","NOTE 1 The acquisition sequence is a data structure forming a preamble which provides for initial symbol synchronization within the incoming stream of detected symbols.\nNOTE 2 The length of the acquisition sequence is selected according to the mission telecommand link performance specifications.\nNOTE 3 The length of the acquisition sequence can be effectively increased by transmitting the idle sequence defined in clause 9.2.3\n\t\t\t\t\t\t\t\t\t\t\t"]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","5.2.1.3a","Requirement","ECSS-E-ST-50_0970002",1,"Created","As an output from the requirements engineering activity, the customer shall produce the space communication system requirements specification (CSRD) in conformance with the DRD of Annex A."]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","5.2.3.3c","Requirement","ECSS-E-ST-50_0970011",1,"Created","The supplier shall provide the simulations and demonstrations used to verify the design, to resolve design conflicts, and to select options (CSVP), in conformance with the DRD in Annex D, and"]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","5.2.4.3c","Requirement","ECSS-E-ST-50_0970016",1,"Created","The supplier shall provide all test and check-out procedures used to verify the system (CSVP), in conformance with the DRD in Annex D;"]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","5.4.1a","Requirement","ECSS-E-ST-50_0970030",1,"Created","The design of the space communication system shall ensure that the spacecraft can be commanded at all spacecraft attitudes, and at all anticipated attitude rates."]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","5.4.4b","Requirement","ECSS-E-ST-50_0970034",1,"Created","The list of essential commands, including their encoding and effects, shall be agreed at PDR."]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","5.5.5a","Requirement","ECSS-E-ST-50_0970049",1,"Created","All telemetry packets generated onboard the spacecraft shall be time stamped such that the temporal ordering of the acquired telemetry can be determined on the ground, regardless of the location of the onboard application that generated the telemetry packet.\n    ","NOTE The implication of this requirement is that the time stamp is related to a common onboard reference time."]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","5.6.2a","Requirement","ECSS-E-ST-50_0970052",1,"Created","Each space link shall be treated as a simplex communication channel."]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","5.6.8a","Requirement","ECSS-E-ST-50_0970060",1,"Created","To support contingency situations, the design shall enable the transfer of meaningful commands and status reports within very short acquisition periods.\n    ","NOTE Link setup times are kept to a minimum in order to cope with short contact periods with the spacecraft."]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","5.6.11.5a","Requirement","ECSS-E-ST-50_0970069",1,"Created","Uplink budget calculations shall be based on a BER of 10-5 at the input to the telecommand decoder."]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","5.6.12.4b","Requirement","ECSS-E-ST-50_0970081",1,"Created","The PFD limits specified in requirement 5.6.12.4a shall apply during all phases of the mission. \n    ","NOTE This can involve means of reducing the transmit power onboard the spacecraft."]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","5.6.13.5a","Requirement","ECSS-E-ST-50_0970088",1,"Created","ARQ settings shall be verified in end-to-end simulations under all expected conditions to ensure that there is neither unnecessary loss of data nor excessive re-transmission."]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","5.7.1.2a","Requirement","ECSS-E-ST-50_0970099",1,"Created","The space network performance shall be deterministic under all loads."]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","5.7.2.2a","Requirement","ECSS-E-ST-50_0970107",1,"Created","The space network shall provide a reliable packet transfer service that guarantees the delivery of data packets to the destination or, if the packet cannot be delivered, notifies the sender that the packet is not deliverable."]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","5.8.3a","Requirement","ECSS-E-ST-50_0970116",1,"Created","The ground network shall provide security mechanisms to prevent unauthorized access to the ground facilities to command or acquire data from the spacecraft."]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","5.8.6a","Requirement","ECSS-E-ST-50_0970119",1,"Created","The ground network shall be available for all scheduled operations on the spacecraft. "]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","A.2.1<6>a","Requirement","ECSS-E-ST-50_0970127",1,"Created","The CSRD shall include the following launch information\n    1. The launch vehicle, the launch site location and the ascent trajectory.\n    2. For orbital vehicles, the orbit injection characteristics."]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","A.2.1<7.2>c","Requirement","ECSS-E-ST-50_0970137",1,"Created","The CSRD shall list the communication system requirements for the space network, which comprises all of the nodes of the flight segment of the mission."]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","B.2.1<4>b","Requirement","ECSS-E-ST-50_0970146",1,"Created","The CSBD shall describe all of the assumptions made in establishing the communication system baseline definition."]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","B.2.1<6>b","Recommendation","ECSS-E-ST-50_0970229",1,"Created","The CSBD should: \n    1. list all communication system issues to be resolved by modelling or simulation, and\n    2. describe the modelling or simulation technique to be applied."]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","B.2.1<14>a","Requirement","ECSS-E-ST-50_0970165",1,"Created","The CSBD shall list all of the items for which a clear resolution has not yet been found."]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","C.2.1<4>d","Recommendation","ECSS-E-ST-50_0970230",1,"Created","The CSAD should contain a list of the communication system issues to be resolved by analysis."]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","D.2.1<2>a","Requirement","ECSS-E-ST-50_0970180",1,"Created","The CSVP shall list the applicable and reference documents in support to the generation of the document."]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","D.2.1<4>c","Requirement","ECSS-E-ST-50_0970185",1,"Created","The CSVP shall list any special tools or facilities to be used."]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","E.2.1<5>a","Requirement","ECSS-E-ST-50_0970198",1,"Created","This CSADD shall provide a requirement applicability matrix, including the following information: \n    1. requirements - containing a list of all requirements in the CSRD plus any derived requirements contained in the CSBD;\n    2. applicability - indicating the applicability of each requirement to each major communication system component. Usually, this column can be subdivided into a series of columns, one for each major system component, and completed check-box style;\n    3. notes - providing any special information associated with a given requirement in respect of its allocation to a communication system component."]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","F.2.1<4>a","Requirement","ECSS-E-ST-50_0970204",1,"Created","The CSDDD shall contain the detailed design of the communication system, with all critical detailed design decision justifications, including:\n    1. the requirements applicable to each of the major components of the communication system identified in the CSADD,\n    2. the detailed design of each major component of the communication system,\n    3. a justification of all design decisions relating to the detailed design of each component, and\n    4. a complete description of all of the interfaces to each component."]
["ECSS-E-ST-50C","ECSS - Superseded v1.0","H.2.1<4>b","Requirement","ECSS-E-ST-50_0970216",1,"Created","The CSOM shall describe the communication system test procedures used to verify the correct operation of the communication system during the mission;"]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","4.1b","Requirement","ECSS-E-ST-10-03_0750002",1,"Created","The customer and the supplier shall agree the need to treat a space segment element as a space segment equipment.\n    ","NOTE This is typically the case for small instrument."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","4.3.2.1a","Requirement","ECSS-E-ST-10-03_0750011",1,"Created","The test programme shall be decomposed in blocks.\n    ","NOTE The general test programme is reviewed at the CDR as per ECSS-M-ST-10."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","4.3.2.2b","Requirement","ECSS-E-ST-10-03_0750015",1,"Created","The TRR shall address the following topics:\n    1. test documentation availability and suitability, including: \n        (a) approved AITP,\n        (b) approved test specification,\n        (c) test predictions (when relevant),\n        (d) approved test procedures (including contingency and emergency procedures),\n        (e) approved measurement point plan,\n        (f) approved test facility readiness report,\n        (g) approved test schedule, and\n        (h) acceptance data package of lower level items.\n    2. item under test configuration;\n    3. test configuration/set-up;\n    4. inspection status report of KIP, MIP, or both;\n    5. test facility, environmental conditions, test instrumentations, calibration, maintenance status; \n    6. cleanliness condition, hazard and safety;\n    7. ground support equipment (GSE) and infrastructures;\n    8. status of nonconformances that affect the item under test, its associated GSE, or the test facility;\n    9. waivers status, and deviations;\n    10. personnel qualification and availability;\n    11. results from test rehearsal using the test facility with or without the item under test, when relevant;\n    12. test pass/fail criteria completeness;\n    13. assignment of responsibilities;\n    14.test schedule.","NOTE 1 For 4.3.2.2b.1(f), the content of the facility readiness report is defined in ECSS-Q-ST-20-07.\nNOTE 2 The level of details according to which each topic is addressed, is different for the general test programme TRR than for each block test TRR. "]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","4.3.3.3c","Requirement","ECSS-E-ST-10-03_0750030",1,"Created","The way the requirement 4.3.3.3b is achieved shall be agreed between the customer and the supplier."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","4.3.3.4c","Requirement","ECSS-E-ST-10-03_0750033",1,"Created","The way the requirement 4.3.3.4b is achieved shall be agreed between the customer and the supplier."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","4.3.5c","Requirement","ECSS-E-ST-10-03_0750041",1,"Created","Trend analysis shall be performed using test data acquired across test sequences."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","4.4.2b","Requirement","ECSS-E-ST-10-03_0750051",1,"Created","For the purpose of 4.4.2a test tolerances shall be justified by reference to the uncertainty budget and confidence level of the measurement instrument(s) used.\n    ","NOTE 1 EA-4/16 and EA-4/02 (section 2) guidelines can be used to build up the uncertainty budget.\nNOTE 2 The tolerances specified in Table 4-1 are the allowable ranges within which the test parameters can vary, they include instrumentation accuracy."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","4.5.1a","Requirement","ECSS-E-ST-10-03_0750060",1,"Created","The test programme shall be defined taking into account the agreed model philosophy.\n    ","NOTE The model philosophy, including model definition, is detailed in ECSS-E-HB-10-02."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","4.5.3b","Requirement","ECSS-E-ST-10-03_0750069",1,"Created","Acceptance testing shall be performed on each flight product, except the one used as Protoflight, to assure freedom from workmanship defects and flawed materials in conformance with ECSS-E-ST-10-02."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","4.6.3e","Requirement","ECSS-E-ST-10-03_0750080",1,"Created","Any additional test to the one listed in 4.6.3d shall be identified for customer approval."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","5.1a","Requirement","ECSS-E-ST-10-03_0750088",1,"Created","The test baseline and sequencing shall be tailored to the specific space segment equipment type for each project.","NOTE The types of space segment equipment are uniformly listed at the end of Table 5-1, Table 5-3, and Table 5-5."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","5.2a","Requirement","ECSS-E-ST-10-03_0750098",1,"Created","The space segment equipment qualification test baseline shall consist of the tests specified in Table 5-1 in line with requirement 5.1b, according to the type of the space segment equipment."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","5.3a","Requirement","ECSS-E-ST-10-03_0750099",1,"Created","The space segment equipment acceptance test baseline shall consist of the tests specified in Table 5-3 in line with requirement 5.1b, according to the type of the space segment equipment."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","5.5.1.1k","Requirement","ECSS-E-ST-10-03_0750112",1,"Created","When protection function have the capability to be overwritten, the overwrite function shall be tested."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","5.5.1.3a","Requirement","ECSS-E-ST-10-03_0750118",1,"Created","The life test for space segment equipment qualification shall be designed to demonstrate the ability of the space segment equipment to withstand the maximum operating time and the maximum number of predicted operational cycles during the “product lifetime” by providing the required performance at the end of life.\n    ","NOTE This test is performed on life-limited space segment equipment or part of it."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","5.5.2.1b","Requirement","ECSS-E-ST-10-03_0750127",1,"Created","The space segment equipment shall be in launch configuration, unless this configuration cannot be reproduced on ground."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","5.5.2.3c","Requirement","ECSS-E-ST-10-03_0750132",1,"Created","In order to evaluate the space segment equipment integrity a resonance search shall be performed before and after the random vibration test."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","5.5.2.6a","Requirement","ECSS-E-ST-10-03_0750146",1,"Created","Shock tests shall be conducted in the item under test configuration relevant to the event where the shock is produced.","NOTE The shock tests demonstrate the ability of the space segment equipment to withstand the shocks encountered during the lifetime, e.g.: fairing separation, space segment equipment separation, booster burn out, apogee boost motor ignition, solar arrays and antennas deployment, shocks from landing of reusable elements."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","5.5.2.6e","Permission","ECSS-E-ST-10-03_0750455",1,"Created","To reduce the number of shock activations, axes and directions may be combined, provided the required environment is created."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","5.5.3.1g","Requirement","ECSS-E-ST-10-03_0750165",1,"Created","When temperature potentially affects the sealing materials or surfaces, an evaluation of the hardware design and operational characteristics shall be performed and, if technically warranted, the leak test conducted at the minimum and maximum qualification or acceptance temperature limits for respectively qualification or acceptance test."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","5.5.3.2b","Requirement","ECSS-E-ST-10-03_0750168",1,"Created","The proof pressure acceptance test shall be performed to demonstrate absence of workmanship problem leading to leak above the specification."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","5.5.4.1b","Requirement","ECSS-E-ST-10-03_0750176",1,"Created","Thermal balance phase(s), if required, shall be included in the thermal vacuum or thermal ambient test at a pressure value corresponding to the type of mission.\n    ","NOTE E.g. for very dissipative equipment, equipment with important thermal gradients at vacuum conditions, Earth atmospheric pressure, space station pressure or Mars pressure."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","5.5.4.1k","Requirement","ECSS-E-ST-10-03_0750185",1,"Created","Functional tests shall be performed as a minimum at hot and cold operating temperatures.\n    ","NOTE Test during transition are subjected to case by case decision."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","5.5.4.2e","Requirement","ECSS-E-ST-10-03_0750197",1,"Created","For solar array, continuity and insulation resistance shall be monitored during the test as per ECSS-E-ST-20-08 requirements 5.5.3.11.2 f and g."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","5.5.5.1c","Requirement","ECSS-E-ST-10-03_0750204",1,"Created","For RF space segment equipment sniff or spray test shall be performed at one or several frequencies used by the space segment equipment under test or in mission critical receive bands."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","5.5.6.1.2b","Requirement","ECSS-E-ST-10-03_0750215",1,"Created","The sound power level shall be converted into cabin pressure level."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","6.1f","Requirement","ECSS-E-ST-10-03_0750223",1,"Created","Any unusual or unexpected behaviour shall be evaluated to determine the existence of any trend potentially leading to anomaly or failure situation."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","6.5.1.2.1c","Requirement","ECSS-E-ST-10-03_0750232",1,"Created","Functional tests shall be performed, under ambient conditions, at the beginning and at the end of the test programme providing the criteria for judging the integrity of the space segment element thought the overall test programme.","NOTE The results of both tests should be identical within the test tolerances."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","6.5.1.2.1f","Recommendation","ECSS-E-ST-10-03_0750460",1,"Created","The FFT activities should follow the expected mission sequence, properly involving the interested functions, with the element correct configuration for the particular mission phase."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","6.5.1.2.3c","Requirement","ECSS-E-ST-10-03_0750243",1,"Created","During the electrical functional tests, all components shall be operated, including redundant space segment equipment and paths, taking into account the type of redundancy (e.g. hot or cold).\n    ","NOTE Pyrotechnic devices are replaced by simulators that can be energized and monitored."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","6.5.1.3a","Requirement","ECSS-E-ST-10-03_0750253",1,"Created","Performance tests shall verify that the space segment element provide the specified performances for the required function.\n    ","NOTE Performance tests are mainly defined for payload. At satellite level performances are mostly checked at payload or subsystem level."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","6.5.1.5b","Requirement","ECSS-E-ST-10-03_0750262",1,"Created","Polarity tests shall be performed, with the validated final software installed, in all specific modes, on all chains from sensor to actuator, with the spacecraft in its final flight configuration."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","6.5.2.1d","Permission","ECSS-E-ST-10-03_0750462",1,"Created","For a large space segment element, the physical properties may be calculated using data from equipment individual measurements providing the final results meet the specified accuracy."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","6.5.2.5b","Requirement","ECSS-E-ST-10-03_0750281",1,"Created","Propellant storage tanks shall be at least mass and stiffness representative during transient testing.","NOTE Simulated propellant can be used."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","6.5.2.6d","Requirement","ECSS-E-ST-10-03_0750290",1,"Created","The internal pressure decay shall be verified for pressurized space segment equipment being part of the space segment element under test."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","6.5.2.7f","Requirement","ECSS-E-ST-10-03_0750300",1,"Created","Notching criteria and implementation shall be approved by the customer and, if relevant, by the launcher authority."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","6.5.2.7g","Requirement","ECSS-E-ST-10-03_0750301",1,"Created","The induced cross axis accelerations at the attachment points shall be limited to the maximum test levels specified for the cross axis. "]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","6.5.2.9a","Requirement","ECSS-E-ST-10-03_0750314",1,"Created","During shock tests the space segment element shall be in an operating mode representative of launch, ascent phases or configuration relevant during the shock actuation."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","6.5.2.9g","Requirement","ECSS-E-ST-10-03_0750320",1,"Created","Activation of both primary and redundant devices inducing shock shall be carried out in the same sequence as they are intended to be operated."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","6.5.3.4b","Requirement","ECSS-E-ST-10-03_0750332",1,"Created","When the fully assembled configuration precludes accessibility to perform requirement 6.5.3.4a, leak tests shall be conducted on a configuration to be agreed with the customer."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","6.5.4.1f","Requirement","ECSS-E-ST-10-03_0750339",1,"Created","The equipment power ON/OFF status, throughout the test (including transitions), shall be defined in the test specification."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","6.5.4.1o","Requirement","ECSS-E-ST-10-03_0750348",1,"Created","The rate of temperature change during cooling, and heating shall be the same as those projected for the mission, but not exceed them."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","6.5.4.2b","Requirement","ECSS-E-ST-10-03_0750352",1,"Created","The pressure during the test shall be maintained £ 10-5 hPa."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","6.5.7.1b","Requirement","ECSS-E-ST-10-03_0750367",1,"Created","Space segment equipment internal, in case of payload elements, self-induced vibration responses and transfer functions shall be measured."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","6.5.7.3a","Requirement","ECSS-E-ST-10-03_0750370",1,"Created","A toxic gas test shall be performed in thermal chamber to verify that the flight hardware does not produce toxic vapours that can build up to harmful levels for the crew in the closed loop life support system."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","7a","Requirement","ECSS-E-ST-10-03_0750378",1,"Created","Pre-launch tests shall confirm that all elements needed for the launch, including their interfaces are verified, and that their parameters are within the specified limits.\n    ","NOTE 1 Elements needed for the launch are: Launch segment element, space segment element and associated GSE.\nNOTE 2 For space segment element, the set of parameters checked as part of pre-launch testing is a sub set of those used during AIT. The definition of this sub set is subject to agreement with the customer."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","A.2.1<1>a","Requirement","ECSS-E-ST-10-03_0750388",1,"Created","The AITP shall contain a description of the purpose, objective, content and the reason prompting its preparation."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","A.2.1<5>e","Recommendation","ECSS-E-ST-10-03_0750466",1,"Created","The sequencing of activities should be presented as flow charts."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","B.2.1<1>b","Requirement","ECSS-E-ST-10-03_0750406",1,"Created","Any open issue, assumption and constraint relevant to this document shall be stated and described."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","B.2.1<10>a","Requirement","ECSS-E-ST-10-03_0750417",1,"Created","The TSPE shall list the requirements for the involved documentation, including test procedure, test report and PA and QA records."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","C.2.1<5>b","Requirement","ECSS-E-ST-10-03_0750425",1,"Created","The software version of the item under test shall be identified."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","C.2.1<13>c","Requirement","ECSS-E-ST-10-03_0750435",1,"Created","The TPRO shall contain a placeholder for identifying:\n    a. procedure variations, together with justification, and\n    b. anomalies."]
["ECSS-E-ST-10-03C","ECSS - Superseded v1.0","C.2.1<14>a","Requirement","ECSS-E-ST-10-03_0750436",1,"Created","The TPRO shall provide detailed instructions, including expected results, with tolerances, pass/fail criteria, and identification of specific steps to be witnessed by QA personnel."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","4.2.4.2a","Requirement","ECSS-E-ST-20-07_0080006",1,"Unchanged","Analysis or tests at system level shall be performed for assessing the threat at subsystem or equipment level.\n    NOTE Analysis or tests can be defined in the time or frequency domain. They are expected to evaluate the coupling level from the ESD source to critical points."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","4.2.9b","Requirement","ECSS-E-ST-20-07_0080017",1,"Unchanged","The EGSE shall be immune to signals used for spacecraft susceptibility tests."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","4.2.11.2d","Requirement","ECSS-E-ST-20-07_0080026",1,"Unchanged","The DC resistance between the equipment bonding stud and the nearby spacecraft structure shall be less than 2,5 mW."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","4.2.13.1b","Requirement","ECSS-E-ST-20-07_0080035",1,"Unchanged","Wires falling into one category shall be assembled into a same bundle. "]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.2.2.2a","Requirement","ECSS-E-ST-20-07_0080045",1,"Unchanged","The enclosures shall be large such that the EUT arrangement requirements of 5.2.6 and antenna positioning requirements described in the individual test procedures are satisfied."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.2.2.3a","Requirement","ECSS-E-ST-20-07_0080049",1,"Unchanged","The ambient electromagnetic level shall be measured with the EUT not operating and all auxiliary equipment turned on."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.2.4a","Requirement","ECSS-E-ST-20-07_0080064",1,"Unchanged","The impedance of power sources providing input power to the EUT shall be controlled by Line Impedance Stabilization Networks (LISNs) for all measurement."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.2.4d","Requirement","ECSS-E-ST-20-07_0080067",1,"Unchanged","The LISN circuit shown in Figure 5-2 shall be used.\n    NOTE 1 The LISN can be split in several cases, one per power lead.\n    NOTE 2 The series inductances represent the inductances of the wiring; the series resistances represent the resistances of the wiring and of the central protections.\n    NOTE 3 The 50W resistors result in 100W at high frequency, similar to the characteristic impedance of the line.\n    NOTE 4 The feed-through capacitors provide a short-circuit at high frequency and make the LISN symmetrical\n    NOTE 5 Connecting the regulation wires of the laboratory supply at the LISN input in order to provide sufficiently low impedance at low frequency is an appropriate method. The source impedance is then dominated by the series resistances in the LISN. Alternatively, a large capacitor (between 1 mF and 10 mF) will be used."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.2.5.3a","Requirement","ECSS-E-ST-20-07_0080075",1,"Unchanged","Checks shall be performed to assure that an overload condition does not exist.\n    NOTE Measurement receivers and transducers are subject to overload, especially receivers without preselectors and active transducers."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.2.6.5b","Requirement","ECSS-E-ST-20-07_0080084",1,"Unchanged","Bench mounted EUTs comprising interconnecting cables shall be located (10 ± 2) cm from the front edge of the ground plane."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.2.6.6.3c","Requirement","ECSS-E-ST-20-07_0080096",1,"Unchanged","Power leads that are bundled, as part of an interconnecting cable in the actual installation, shall be configured in the same fashion for the 2 m exposed length and then shall be separated from the bundle and routed to the LISNs."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.2.6.7d","Requirement","ECSS-E-ST-20-07_0080103",1,"Unchanged","When variable electrical or mechanical loading is present in the actual installation, testing shall be performed under expected worst-case conditions. "]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.2.8.2b","Requirement","ECSS-E-ST-20-07_0080114",1,"Unchanged","When measurement devices other than peak detector are used for susceptibility testing, correction factors shall be determined and applied for test signals to adjust the reading to equivalent r.m.s. values under the peak of the modulation envelope.\n    NOTE Example of such measurement devices are oscilloscopes, non-selective voltmeters, and field strength sensors."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.2.9.3b","Requirement","ECSS-E-ST-20-07_0080122",1,"Unchanged","Minimum measurement time for analogue measurement receivers during emission testing shall be as specified in Table 5-2."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.2.9.4g","Requirement","ECSS-E-ST-20-07_0080131",1,"Unchanged","For frequency domain plots, emission data shall be reported in graphic form with frequency resolution of 1 %, or twice the measurement receiver bandwidth, whichever is less stringent."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.2.10.1a","Requirement","ECSS-E-ST-20-07_0080134",1,"Unchanged","For susceptibility measurements, the entire frequency range for each applicable test shall be scanned.\n    NOTE Stepped scans refer to signal sources that are sequentially tuned to discrete frequencies."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.2.10.4c","Requirement","ECSS-E-ST-20-07_0080142",1,"Unchanged","Indications of compliance with the requirements shall be provided.\n    NOTE Such indications can be provision of oscilloscope plots of injected waveforms with test data."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.3.2b","Requirement","ECSS-E-ST-20-07_0080152",1,"Unchanged","Safety margin demonstration for something that is susceptible to a time domain circuit (including EEDs) shall use time domain methods."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.3.6a","Requirement","ECSS-E-ST-20-07_0080159",1,"Unchanged","Spacecraft DC magnetic field emission requirements shall be verified by a combination of analysis and tests."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.4.2.2a","Requirement","ECSS-E-ST-20-07_0080168",1,"Unchanged","The test equipment shall be as follows:\n    1. Measurement receiver,\n    2. Current probe,\n    3. Signal generator with amplifier,\n    4. DC-current supply,\n    5. Data recording device,\n    6. Oscilloscope,\n    7. Coaxial “T” connector and coaxial to bifilar transition,\n    8. 1 W and 10 W power metal film resistors with inductance lower than 100 nH,\n    9. LISN defined in 5.2.4."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.4.4.5b","Requirement","ECSS-E-ST-20-07_0080178",1,"Unchanged","Two separate displays shall be provided showing respectively the initial rise time and the full inrush response.\n    NOTE Typical time bases are 10 µs full scale for the initial rise time and 1 ms full scale for the full inrush response."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.4.6.3a","Requirement","ECSS-E-ST-20-07_0080187",2,"Normative Change","A basic test setup for the EUT as shown and described in Figure 5-3 and 5.2.6 shall be maintained to ensure that the EUT is oriented such that the surface that produces the maximum radiated emissions is toward the front edge of the test setup boundary.\n    NOTE The LISN should be used."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.4.7.2a","Requirement","ECSS-E-ST-20-07_0080197",1,"Unchanged","The test equipment shall be as follows:\n    1. Signal generator,\n    2. Power amplifier,\n    3. 1,5 W to 2,7 W power metal film resistor with inductance lower 1 000 nH and peak power capability,\n    4. Oscilloscopes,\n    5. Current probe,\n    6. Differential high voltage-probe,\n    7. injection transformer,\n    8. LISN defined in 5.2.4 optional."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.4.7.3a","Requirement","ECSS-E-ST-20-07_0080198",2,"Normative Change","The test setup shall be as follows:\n    1. Maintain a basic test setup for the EUT as specified in 5.2.6 and Figure 5-3.\n    2. Check measurement system by configuring the test equipment in accordance with Figure 5-16, and setting up the oscilloscope to monitor the voltage across the resistor.                                    \n    3. Test the EUT by configuring the test equipment as shown in Figure 5-17.                                      "]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.4.8.4c","Requirement","ECSS-E-ST-20-07_0080206",1,"Unchanged","The EUT shall be tested by performing the following procedures and using the EUT test setup:\n    1. Turn on the EUT and wait until it is stabilized.\n    2. Select a bundle for testing and clamp the current probes into position.\n        (a) Set the modulated sine generator to a test frequency, at low output level.\n        (b) Adjust the modulation in duty cycle and frequency.\n        (c) Increase the generator output to the level determined during calibration, without exceeding the current limit specified by application of clause 4.2.8 and record the peak current obtained.\n        (d) Monitor the EUT for degradation of performance.\n        (e) If susceptibility is noted, determine the threshold level as measured by the current monitor probe in accordance with 5.2.10.3.\n        (f) Repeat 5.4.8.4c.2(a) through 5.4.8.4c.2(e) for each test frequency.\n    3. Repeat 5.4.8.4c.2. applying the test signals to each bundle interfacing with each connector or all bundles taken together."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.4.11.2a","Requirement","ECSS-E-ST-20-07_0080217",1,"Unchanged","The test equipment shall be as follows:\n    1. Signal generators,\n    2. Power amplifiers,\n    3. Receive antennas,\n        (a) under 1 GHz, not applicable.\n        (b) 1 GHz to 18 GHz, double ridge horn, 24.2 by 13.6 cm opening.\n            NOTE Above 1 GHz receive antennas may be not used, see 5.4.11.3b.2.\n    4. Linearly polarized transmit antennas\n        NOTE The following antennas are commonly used:\n            · 30 MHz to 200 MHz, biconical, 137 cm tip to tip,\n            · 200 MHz to 1 GHz, double ridge horn, 69,0 cm by 94,5 cm opening, or log-periodic,\n            · 1 GHz to 18 GHz, double ridge horn, 24,2 cm by 13,6 cm opening.\n    5. Electric field sensors (physically small - electrically short),\n    6. Measurement receiver,\n    7. Power meter,\n    8. Directional coupler,\n    9. Attenuator,\n    10. Data recording device,\n    11. LISN defined in 5.2.4, optional."]
["ECSS-E-ST-20-07C Rev. 1","ECSS - Superseded v1.0","5.4.11.4a","Requirement","ECSS-E-ST-20-07_0080224",1,"Unchanged","The measurement equipment and EUT shall be turned on and waited until they are stabilized.\n    NOTE It is important at this point to assess the test area for potential RF hazards and take precautionary steps to assure safety of test personnel and fire avoidance."]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","4.1.2e","Requirement","ECSS-E-ST-20_0020005",1,"Informative Change","An undetermined status at the interfaces of a powered unit shall not cause damage to an un-powered interface. ","NOTE \tUndetermined status includes: non-nominal operating modes, permanent and non-permanent failure modes, powered and un-powered interfaces.\n"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","4.1.3h","Requirement","ECSS-E-ST-20_0020014",1,"Informative Change","Processor and simple logic circuits shall not be able to issue category 1 and 2 critical commands without a ground commanded arm/safe or enable/ disable command.","NOTE \tTo avoid inadvertent activation of processes enabled/disabled by category 1 or 2 critical commands during ground operations and in low earth orbit phases, it is necessary to foresee safety barriers (arm/safe commands) to inhibit the execution of such critical commands. Such safety barriers might be spacecraft skin connections (to be established or broken just before flight) or connections/disconnection plugs to be activated by launcher stages release (in flight). The activation/deactivation of such barriers has to be independent from on board processor.\n"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","4.2.1b","Recommendation","ECSS-E-ST-20_0020022",2,"Normative Change","Redundant signal or power lines should be segregated via physically separated connectors and harnesses."]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","4.2.1m","Requirement","ECSS-E-ST-20_0020033",2,"Normative Change","Disabling critical on-board autonomous functions shall be allowed only if an interlock mechanism is implemented, which prevents the disabling of both main and redundant functions at the same time.","NOTE \tCritical functions refers to functions which prevent the satellite from being recovered when both main and redundant are switched off, e.g. RF receiver or command decoder.\n"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","4.2.1p","Requirement","ECSS-E-ST-20_0020036",2,"Normative Change","Essential functions shall not be lost upon a single failure of other functions which are centrally powered or controlled.","NOTE\t1\tE.g. on synchronization and auxiliary supply.\nNOTE\t2\tThat can imply the capability of an equipment performing an essential function of operating independently of any external synchronization and auxiliary power supply if these are not SPF free.\n"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","4.2.1x","Requirement","ECSS-E-ST-20_0020407",1,"Created","Occurrence of a non-destructive SEE after a failure shall not lead to the loss of the mission.","NOTE \tAccordingly, a non-destructive SEE cannot derail a reconfiguration process after first hardware failure.\n"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","4.2.3e","Requirement","ECSS-E-ST-20_0020053",1,"Informative Change","It shall be ensured that erroneous mating is avoided by connector keying or marking.","NOTE \tThe requirement is met either by harness routing, or by using keyed connectors, or adequate positioning of connectors, or connectors of different type or size, or connector marking.\n"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","4.2.3n","Requirement","ECSS-E-ST-20_0020062",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","4.2.4h","Requirement","ECSS-E-ST-20_0020071",2,"Normative Change","Circuits meant for on-ground testing or unused circuits shall not create or be sensitive to the noise expected during operation.","NOTE \tFor example spacecraft stimuli, unit test points, unused operational amplifiers or comparators.\n"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","4.2.6c","Requirement","ECSS-E-ST-20_0020082",1,"Informative Change","When components operating in a single event are used, 4 times the quantity to be used for flight units shall be procured as one lot: 25 % for the lot acceptance test, 25 % for flight use, 25 % for spares and 25 % for a confirmation test near to the launch date. ","NOTE \tExample of such components are fuses.\n"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","5.2.1a","Requirement","ECSS-E-ST-20_0020088",1,"Unchanged","Budgets and margins shall be established during Project phase B, and reviewed in all subsequent phases of the project."]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","5.3c","Requirement","ECSS-E-ST-20_0020098",2,"Normative Change","In flight operation, if primary power bus shutdown happens, the system, including the power subsystem, shall be able to restart.","NOTE\t1\tStartup is possible as soon as sufficient power is available for a sufficient time from any source of the primary power bus, without considering failure for unmanned mission, or after single failure for manned mission.\nNOTE\t2\tThis requirement can imply that the battery is sufficiently recharged before its energy starts to be provided, for example to recover spacecraft attitude.\n"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","5.3d","Requirement","ECSS-E-ST-20_0020099",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","5.5.2c","Requirement","ECSS-E-ST-20_0020107",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","5.5.2n","Requirement","ECSS-E-ST-20_0020118",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","5.5.3f","Requirement","ECSS-E-ST-20_0020127",1,"Unchanged","The BOL worst and best case power calculations shall include the parameters indicated in Table 5-1."]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","5.6.2a","Requirement","ECSS-E-ST-20_0020136",2,"Normative Change","The battery shall be specified to ensure the energy balance in each mission phase during operational life, including contingency modes resulting from a single failure for unmanned missions and two failures for manned missions."]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","5.6.2k","Requirement","ECSS-E-ST-20_0020146",2,"Normative Change","Provisions for interfacing the battery with the ground support equipment during pre-launch operations shall be made.","Such provisions can include:\n· signal lines for monitoring battery voltage,\n· signal lines for monitoring battery temperature,\n· capability to charge the battery,\n· capability to discharge the battery."]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","5.6.3d","Requirement","ECSS-E-ST-20_0020153",1,"Unchanged","For any intended cell operation under acceleration greater than 1 g, the supplier shall ensure that no effect upon both short term (e.g. capacity) performance and lifetime can prevent battery nominal operation. "]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","5.6.5.2a","Requirement","ECSS-E-ST-20_0020164",2,"Normative Change","The battery safety shall be managed in conformance with ECSS-Q-ST-40."]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","5.7.2b","Requirement","ECSS-E-ST-20_0020171",2,"Normative Change","For manned missions, no double failure shall result in the loss of the power subsystem capability to the extent that the minimum mission requirements, in any of its phases, cannot be fulfilled."]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","5.7.2f","Requirement","ECSS-E-ST-20_0020175",2,"Normative Change","The design shall ensure that under all conditions during the required lifetime, including operation in eclipse with one battery cell failure and one solar array string failed, the primary bus voltage remains within specified performances."]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","5.7.2o","Requirement","ECSS-E-ST-20_0020184",1,"Informative Change","At the point of regulation, the impedance mask of a fully regulated bus, operating with one source shall be below the impedance mask shown in Figure 5-1.","NOTE\t1\tE.g. battery, solar array.\nNOTE\t2\tRationale for the impedance mask:\n\tIt translates requirement 5.7.2i.1 of 1 % voltage change for 50 % load change in a domain of regulation up to 10 kHz bandwidth. In DC the integrator in the control loop is designed to ensure no static error, in higher frequency, between 10 kHz and 100 kHz it is likely that the inductance effect of the components and connections are seen and the impedance rise not always making feasible to respect the ideal impedance mask.\n"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","5.7.3b","Requirement","ECSS-E-ST-20_0020190",2,"Deleted","<<deleted>>"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","5.7.4e","Requirement","ECSS-E-ST-20_0020202",2,"Normative Change","The spacecraft design shall be such that in the event of an under-voltage condition on the bus, no failure is induced in the power subsystem or the loads during and when recovering from this under-voltage. "]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","5.7.6b","Requirement","ECSS-E-ST-20_0020213",1,"Unchanged","No load shall generate a spurious response that can damage itself or any other equipment during bus voltage variation, up or down, at any ramp rate, and over the full range from zero to maximum bus voltage."]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","5.8.1f","Requirement","ECSS-E-ST-20_0020221",2,"Normative Change","If fuses are used to protect main bus distribution lines, provision shall be made allowing easy replacement of blown or defective fuse.","NOTE \tProvision can consist in easy accessibility to fuses or in replacement of concerned unit by available spare one.\n"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","5.8.1o","Recommendation","ECSS-E-ST-20_0020230",2,"Normative Change","When protection elements are in cascade, the closest one upstream from the anomaly should be the first to act."]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","5.8.1v","Requirement","ECSS-E-ST-20_0020420",1,"Created","In alternative to, and under the same assumptions of requirement 5.8.1u, the magnitude of the load impedance shall be smaller than the magnitude of the source impedance by at least a factor 10.","NOTE\t1\tThe requirements 5.8.1r to 5.8.1v can be used as alternative by the user for verification purposes (only one is used among 5.8.1r to 5.8.1t, or between 5.8.1u and 5.8.1v).\nNOTE\t2\tThe diagrams for the verification of requirements 5.8.1r to 5.8.1v are provided in Figure 5-2.\nNOTE\t3\tThe requirements 5.8.1r to 5.8.1v can be used for evaluating the small signal stability for systems that are linear or can be linearised around an operating point.\nNOTE\t4\tn is a positive integer including 0.\n"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","5.8.2b","Requirement","ECSS-E-ST-20_0020233",1,"Unchanged","With the exception of the solar array, routing of power lines shall be near ground."]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","5.10a","Requirement","ECSS-E-ST-20_0020243",1,"Unchanged","For non pressurised and non potted high voltage equipment, the applicable pressure range when this equipment is on shall be specified."]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","6.2.1a","Requirement","ECSS-E-ST-20_0020252",1,"Informative Change","The supplier shall establish an overall EMC programme.","NOTE\t1\tThe EMC programme is an activity the purpose of which is to provide for spacecraft-level compatibility with the minimum impact to programme cost, schedule and operational capabilities. The role of the customer in the EMC programme is that of top-level oversight.\nNOTE\t2\tThe EMC programme is based on requirements of this standard, the statement of work, spacecraft specification, and other applicable contractual documents.\n"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","6.3.1.2a","Requirement","ECSS-E-ST-20_0020260",1,"Unchanged","The list of points where the margin is demonstrated (critical points) shall be submitted to the customer for approval."]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","6.3.4.2c","Requirement","ECSS-E-ST-20_0020270",1,"Informative Change","The spacecraft charging protection programme shall include:\n1.\tsurface electrostatic charging, \n2.\tthreat from internal electrostatic charging of dielectric materials and isolated conducting items, due to the penetration of energetic electrons as defined in the environmental specification. ","NOTE \tECSS-E-ST-20-06 is intended to provide clear and consistent requirements to the application of measures to assess and mitigate hazardous effects arising from spacecraft charging and other environmental effects on a spacecraft’s electrical behaviour.\n"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","6.3.6c","Requirement","ECSS-E-ST-20_0020279",1,"Unchanged","The RF compatibility analysis, if used instead of test, shall include the effects of inter-modulation products."]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","6.4.1c","Requirement","ECSS-E-ST-20_0020289",1,"Unchanged","An electromagnetic effects verification report (EMEVR) in conformance with the DRD in Annex C shall be prepared by the supplier."]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","6.4.2a","Requirement","ECSS-E-ST-20_0020290",1,"Unchanged","Safety margins for critical or EED circuit shall be demonstrated at system-level."]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","7.2.2.2.1b","Requirement","ECSS-E-ST-20_0020298",1,"Unchanged","If a number of TT&C antennas operate simultaneously, the combined radiation pattern shall be used in the performance evaluation. "]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","7.2.2.3.1d","Requirement","ECSS-E-ST-20_0020309",1,"Unchanged","It shall be demonstrated that the scattering of the radiation pattern of individual radiating elements does not affect the accuracy of all radiated performance measurement."]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","7.2.2.3.3a","Requirement","ECSS-E-ST-20_0020316",2,"Normative Change","Reflective and transmissive properties of the materials and composites used for the lenses shall be quantified and their impact on antenna performances assessed.","NOTE \tExamples of reflective and transmissive properties are losses, depolarization and diffusivity.\n"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","7.2.2.3.5d","Requirement","ECSS-E-ST-20_0020328",1,"Informative Change","For antenna RF chain the design and manufacturing shall be performed to avoid discharge phenomena according to Paschen curves valid for its specified pressure range and gas properties.","NOTE \tSee clause 7.3 for further details. \n"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","7.2.2.4.3a","Requirement","ECSS-E-ST-20_0020337",1,"Informative Change","The dielectric losses of plastic component in the RF power path shall be quantified and their impact on antenna performances assessed.","NOTE \tComponents made from homogeneous plastic are usually limited to small parts (e.g. spacers or washers).\n"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","7.2.3.2a","Requirement","ECSS-E-ST-20_0020345",1,"Informative Change","Electromagnetic interactions among the antenna and the surrounding spacecraft structure and appendages shall be quantified starting from Phase B, as a minimum, and their impact on antenna performances assessed.","NOTE \tThe field radiated or received by the antenna interacts with the surrounding environment. Interactions with the spacecraft structure and appendages usually have a direct impact on the antenna performances.\n"]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","7.4.3a","Requirement","ECSS-E-ST-20_0020356",1,"Unchanged","All operating conditions shall be identified in which two or more transmit RF signals simultaneously illuminate or passed through a passive RF component, equipment or both."]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","7.4.4e","Requirement","ECSS-E-ST-20_0020363",1,"Unchanged","Acceptance testing shall be carried out on flight components, equipments or systems over an acceptance temperature range to be agreed with the customer, range which can be limited to ambient temperature."]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","A.2.1b","Requirement","ECSS-E-ST-20_0020366",1,"Unchanged","The EMC control plan shall list the applicable and reference documents to support the generation of the document."]
["ECSS-E-ST-20C Rev.1","ECSS - Superseded v1.0","C.2.1b","Requirement","ECSS-E-ST-20_0020376",1,"Unchanged","The EMEVR shall list the applicable and reference documents to support the generation of the document."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","4.3.2a","Requirement","ECSS-E-ST-20-08_0090006",1,"Unchanged","The accuracy of the instruments and test equipment used to control or measure test parameters shall be one order of magnitude higher than the tolerance on the variable to be measured.","NOTE \tExamples of where this cannot be achieved include measurements of electrical performance and temperatures. \n"]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","4.4b","Requirement","ECSS-E-ST-20-08_0090015",1,"Unchanged","Silver cladding shall be annealed and contain a minimum of 99,9 % pure silver."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.2d","Requirement","ECSS-E-ST-20-08_0090021",1,"Unchanged","Deviations from this Standard applicable to the SCD-PVA shall:\n1.\tbe agreed between the customer and the supplier;\n2.\tinclude alternative requirements equivalent to those of this Standard;\n3.\tnot affect the reliability and performances of the photovoltaic assemblies;\n4.\tbe only those specified in requirement 5.2c."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.3.2.7b","Requirement","ECSS-E-ST-20-08_0090034",1,"Unchanged","The ATOX resistivity shall be determined by the individual resistivities of the used materials and components in their configuration."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.3.3.4a","Requirement","ECSS-E-ST-20-08_0090044",1,"Unchanged","Sections shall not be included at the coupon level. "]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.3.3.4b","Permission","ECSS-E-ST-20-08_0091066",1,"Unchanged","To test the technique of interconnecting strings, the negative ends of individual strings may be connected in a way that is representative for flight panels. "]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.3.3.10b","Requirement","ECSS-E-ST-20-08_0090053",1,"Unchanged","The design of the PVA shall include the result of the verification specified in requirement 5.3.3.10a. "]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.4.1a","Requirement","ECSS-E-ST-20-08_0090064",1,"Unchanged","The manufacturing and integration processes shall be validated for all the project specific design configurations and to meet the engineering design requirements."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.4.3.5b","Requirement","ECSS-E-ST-20-08_0090073",1,"Unchanged","The visual inspection procedure and criteria shall be agreed with the customer and be described in the SCD-PVA."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.5.1.2c","Requirement","ECSS-E-ST-20-08_0090082",1,"Unchanged","Qualification margins shall not exceed component and material specifications unless agreed between supplier and customer."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.5.1.3.2c","Requirement","ECSS-E-ST-20-08_0090092",1,"Unchanged","The temperature extremes of the thermal cycling shall be extended or a dedicated structural test shall be performed in cases where analysis demonstrates that the structural loading results in a greater stress than the thermal cycling.","NOTE \tFor example, acoustic and noise can produce greater stress than thermal cycling in certain missions.\n"]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.5.1.3.3h","Requirement","ECSS-E-ST-20-08_0090100",1,"Unchanged","The production of the qualification coupons shall be representative of the full processing of the flight hardware. "]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.5.1.3.4h","Requirement","ECSS-E-ST-20-08_0090111",1,"Unchanged","Insulation and continuity shall not be measured simultaneously."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.5.1.4.4c","Requirement","ECSS-E-ST-20-08_0090118",1,"Unchanged","Relative humidity shall be higher than 90 %. "]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.5.1.4.4g","Requirement","ECSS-E-ST-20-08_0090122",1,"Unchanged","Water condensation on the surface of the test sample shall be prevented."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.5.2.4b","Requirement","ECSS-E-ST-20-08_0090131",1,"Unchanged","All results of the acceptance test shall be reported in the data documentation package (DDP).","NOTE \tFor the DDP, see clause 5.7 and Annex G.\n"]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.5.3.2.3a","Requirement","ECSS-E-ST-20-08_0090138",1,"Unchanged","The PVA supplier shall define the inspection criteria for the PVA components, to be agreed by the customer, and included in the SCD-PVA."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.5.3.2.7a","Requirement","ECSS-E-ST-20-08_0090150",1,"Unchanged","After coverglass or solar cell repair, there shall be no delamination or discoloration in the adhesive, except in the area opposite rear welds, where discoloration may be present."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.5.3.2.9a","Requirement","ECSS-E-ST-20-08_0090156",1,"Unchanged","Cracks in the body of the diode, causing separation of the material, shall not be present."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.5.3.2.15a","Requirement","ECSS-E-ST-20-08_0090169",1,"Unchanged","Crimping of wires shall be in conformance with a standard agreed with the customer.","NOTE \tFor crimping, see for instance ECSS-Q-ST-70-26.\n"]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.5.3.2.19d","Requirement","ECSS-E-ST-20-08_0090178",1,"Unchanged","For the connectors, the status of the following items shall be verified: \n1.\tfixing on the substrate;\n2.\tabsence of cracks;\n3.\tconnections;\n4.\tshrinkage tube."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.5.3.3.3b","Requirement","ECSS-E-ST-20-08_0090185",1,"Unchanged","The insulation shall be in conformance with that stated in the SCD-PVA."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.5.3.3.5b","Requirement","ECSS-E-ST-20-08_0090189",1,"Unchanged","The resistance shall be the value stated in the SCD-PVA."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.5.3.4.2c","Requirement","ECSS-E-ST-20-08_0090203",1,"Unchanged","The results shall be in conformance with those stated in the SCD-PVA."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.5.3.5.2b","Requirement","ECSS-E-ST-20-08_0090208",1,"Unchanged","The method for measuring the capacitance shall be stated in the SCD‑PVA."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.5.3.7.3a","Requirement","ECSS-E-ST-20-08_0090217",1,"Unchanged","The panels shall be exposed to the number of thermal cycles for acceptance as stated in the SCD-PVA."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.5.3.9a","Requirement","ECSS-E-ST-20-08_0090227",1,"Unchanged","X-ray photographs shall be taken of all busbars, wire collection strips and diode boards on the qualification coupons. "]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.5.3.11.2c","Requirement","ECSS-E-ST-20-08_0090236",1,"Unchanged","The qualification coupon shall be exposed to 10 vacuum thermal cycles "]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.5.3.11.3a","Requirement","ECSS-E-ST-20-08_0090241",1,"Unchanged","The qualification coupon electrical performance and insulation resistance shall not degrade more than as stated in the SCD-PVA."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","5.7a","Requirement","ECSS-E-ST-20-08_0090247",1,"Unchanged","The supplier shall provide a data documentation package (DDP) in conformance with Annex G for the qualification approval records for each coupon."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","6.1.2d","Requirement","ECSS-E-ST-20-08_0090255",1,"Unchanged","Deviations from this Standard applicable to the SCD-SCA shall:\n1.\tbe agreed between the customer and the supplier;\n2.\tnot affect the reliability and performances of the SCAs;\n3.\tonly be those specified in requirement 6.1.2c."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","6.3.3.2b","Requirement","ECSS-E-ST-20-08_0090266",1,"Unchanged","The predicted operational voltage (Vop) shall be defined in the SCD‑SCA."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","6.4.1c","Requirement","ECSS-E-ST-20-08_0090273",1,"Unchanged","The qualification plan shall consist of the tests specified in Table 6‑1."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","6.4.2.3b","Requirement","ECSS-E-ST-20-08_0090285",1,"Unchanged","The total quantity of test samples shall be a minimum of 80 or 90 SCAs depending on previous testing, in conformance with requirement 6.4.3.11.2e."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","6.4.3.1.4e","Requirement","ECSS-E-ST-20-08_0090294",1,"Unchanged","The total area of anti-reflection coating voids shall not exceed 3 % of the total active area of the cell."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","6.4.3.1.6b","Requirement","ECSS-E-ST-20-08_0090302",1,"Unchanged","Adhesive voids along the cover edge shall not exceed 0,6 mm in depth."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","6.4.3.3.2a","Requirement","ECSS-E-ST-20-08_0090313",1,"Unchanged","The electrical current of SCA under 1 S.C. (AM0) shall be measured and recorded digitally at least at 50 points, at a solar cell temperature of 25  °C +/- 0,5 °C or operating temperature. "]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","6.4.3.3.3c","Requirement","ECSS-E-ST-20-08_0090320",1,"Unchanged","After qualification tests, the maximum degradation of electrical performance shall be in conformance with requirements 6.4.3.3.3a and 6.4.3.3.3b."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","6.4.3.4d","Requirement","ECSS-E-ST-20-08_0090324",1,"Unchanged","Data for all electrical performance parameters at the different solar cell temperatures shall be provided."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","6.4.3.8.2b","Requirement","ECSS-E-ST-20-08_0090338",1,"Unchanged","The chamber temperature shall then be increased to 60 °C minimum. "]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","6.4.3.8.2g","Requirement","ECSS-E-ST-20-08_0090343",1,"Unchanged","Water condensation on the surface of the SCAs shall be prevented."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","6.4.3.11.2a","Requirement","ECSS-E-ST-20-08_0090352",1,"Unchanged","The SCAs shall be subjected to 1 MeV electron irradiation.","NOTE \tISO 23038 outlines a methodology to perform this test.\n"]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","6.4.3.11.2g","Requirement","ECSS-E-ST-20-08_0090358",1,"Unchanged","After combined electron and photon irradiation, the SCAs shall conform to the requirements stated in the SCD-SCA."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","6.4.3.15.2c","Requirement","ECSS-E-ST-20-08_0090371",1,"Unchanged","Spectral Irradiance for UV light sources shall be performed in conformance with ECSS-Q-ST-70-06."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","6.4.3.15.2h","Requirement","ECSS-E-ST-20-08_0090376",1,"Unchanged","Control samples shall be included in the UV chamber in order to identify potential contaminations occurring during the test."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","6.4.3.16.2c","Requirement","ECSS-E-ST-20-08_0090382",1,"Unchanged","The capacitance shall be measured at SCA level in conformance with the method referred in requirement 6.4.3.16.2b at the temperature range stated in the SCD-SCA."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","6.5.2c","Requirement","ECSS-E-ST-20-08_0090390",1,"Unchanged","Failure analysis of these SCAs shall be performed by the supplier and the results provided to the customer, as part of an NRB documentation.","NOTE \tFor NRB, see ECSS-Q-ST-10-09.\n"]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","7.1.1.3a","Requirement","ECSS-E-ST-20-08_0090401",1,"Unchanged","The supplier shall ensure that the tests and inspections are performed."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","7.2b","Requirement","ECSS-E-ST-20-08_0090410",1,"Unchanged","The supplier shall do the following:\n1.\tmaintain configuration control of all documents;\n2.\tkeep the issues of the documents effective at the date of acceptance by the customer;\n3.\tprovide the PID to the customer for review;\n4.\tsubmit to the customer for review and approval any modifications or changes to documents in the PID with any quality and reliability implications."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","7.3.2.2.2f","Requirement","ECSS-E-ST-20-08_0090423",1,"Unchanged","Continuous or pulsed light source calibrated in conformance with clause 10 shall be used to verify the requirements given in 7.3.2.2.3 for electrical characterization."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","7.4.1b","Requirement","ECSS-E-ST-20-08_0090429",1,"Unchanged","The qualification plan shall consist of the tests specified in Table 7‑2."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","7.4.2.2b","Requirement","ECSS-E-ST-20-08_0090437",1,"Unchanged","The test samples shall be chosen statistically and at random from the qualification lot","NOTE \tFor sampling see ISO 2859.\n"]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","7.5.1.4.1b","Requirement","ECSS-E-ST-20-08_0090448",1,"Unchanged","The cumulative area of all edge chips, corner chips and surface nicks shall not exceed 5 % of the total cell area."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","7.5.1.5.2a","Requirement","ECSS-E-ST-20-08_0090455",1,"Unchanged","The maximum dimension of voids or bubbles shall be 0,25 mm in diameter."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","7.5.1.5.2e","Requirement","ECSS-E-ST-20-08_0090459",1,"Unchanged","The cumulative area of voids, bubbles, drops and spatter shall not exceed 2 % of the total welding area."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","7.5.2b","Requirement","ECSS-E-ST-20-08_0090468",1,"Unchanged","The weight of the solar cell shall be verified by determination of the average weight per qualification lot or weight per contacts vacuum evaporation batch (sample base)."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","7.5.4a","Requirement","ECSS-E-ST-20-08_0090475",1,"Unchanged","Temperature coefficients of all samples in subgroup B and on a minimum of 12 samples from each of subgroups C1, C2 and P shall be measured."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","7.5.6.3b","Requirement","ECSS-E-ST-20-08_0090487",1,"Unchanged","For multi-junction solar cells, the agent to be used to simulate the optical properties of the adhesive shall be stated in the SCD-BSC."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","7.5.7.1.2b","Requirement","ECSS-E-ST-20-08_0090493",1,"Unchanged","The chamber temperature shall then be increased to 60 °C minimum."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","7.5.7.2.2g","Requirement","ECSS-E-ST-20-08_0090506",1,"Unchanged","If there are requirements on specific environmental conditions, such as chemical vapours, they shall be stated in the SCD-BSC."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","7.5.11.2a","Requirement","ECSS-E-ST-20-08_0090515",1,"Unchanged","The surface finish in the interconnector weld area shall be checked with a micro surface-roughness tester."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","7.5.13.2b","Requirement","ECSS-E-ST-20-08_0090522",1,"Unchanged","The flux density and energy shall be uniform over the cell area within ±10 %. "]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","7.5.13.2f","Requirement","ECSS-E-ST-20-08_0090526",1,"Unchanged","For mission specific qualification (Subgroup C2) the irradiation shall be performed as follows:\n1.\tState the expected dose for the envisaged application, Fp, in the SCD-BSC.\n2.\tDivide subgroup C2 (in conformance with Table 7‑2) in two batches of 12 samples as a minimum, constituted as follows (in conformance with requirement 7.4.2.2c):\n(a)\ta minimum of 8 mid-grade cells;\n(b)\ta minimum of 2 high-grade cells;\n(c)\ta minimum of 2 low-grade cells.\n3.\tIrradiate the batches specified in requirement 7.5.13.2f.2 as follows:\n(a)\tthe first batch, twice at Fp;\n(b)\tthe second batch, twice at Fp/2.","NOTE \tThis results in data for 12 samples at Fp/2, at Fp x 2, and data for 24 samples at Fp.\n"]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","7.5.18.2a","Requirement","ECSS-E-ST-20-08_0090540",1,"Unchanged","Test in clause 7.5.3 shall be repeated using a non infrared-rich simulator having a maximum deviation of the total energy in the spectral region of 0,8 mm to 1,1 mm (as described in clause 10.1.1) of a percentage value stated in the SCD-BSC."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","7.6.2a","Requirement","ECSS-E-ST-20-08_0090545",1,"Unchanged","A component shall be considered to have failed if it exhibits one or more of the failure modes specified in clause 7.6.1. "]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","8.3.1.2d","Requirement","ECSS-E-ST-20-08_0090558",1,"Unchanged","Deviations from this Standard applicable to the SCD-CVG shall:\n1.\tbe agreed between the customer and the supplier;\n2.\tinclude alternative requirements equivalent to those of this Standard;\n3.\tnot affect the reliability and performances of the coverglasses;\n4.\tonly be those specified in requirement 8.3.1.2c."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","8.3.3b","Requirement","ECSS-E-ST-20-08_0090564",1,"Unchanged","The orientation method along with associated dimensional tolerances shall be stated in the SCD-CVG."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","8.5.4a","Requirement","ECSS-E-ST-20-08_0090573",1,"Unchanged","Documentation on acceptance tests shall conform to clause 8.9."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","8.6.1e","Requirement","ECSS-E-ST-20-08_0090578",1,"Unchanged","The supplier shall provide details of the outcome of the qualification programme to the customer. "]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","8.6.2.3b","Requirement","ECSS-E-ST-20-08_0090584",1,"Unchanged","A failure in any subgroup shall constitute a failure in the qualification."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","8.7.1.3.6a","Requirement","ECSS-E-ST-20-08_0090596",1,"Unchanged","Surface, edge or corner cracks shall not be present on a coverglass.","NOTE \tFor further information, see MIL-PRF-13830.\n"]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","8.7.4.1b","Requirement","ECSS-E-ST-20-08_0090603",1,"Unchanged","The values and tolerances of the weight of the coverglass, verified by determining the average weight per shipping lot, shall be as stated in the SCD-CVG."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","8.7.4.5b","Requirement","ECSS-E-ST-20-08_0090610",1,"Unchanged","The perpendicularity shall be as stated in the SCD-CVG."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","8.7.9a","Requirement","ECSS-E-ST-20-08_0090622",1,"Unchanged","The transmission into the adhesive shall be measured as in clause 8.7.2, using a fused silica or uncoated coverglass backing piece laminated onto the coverglass component and a matching fluid with a refractive index of 1,41. "]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","8.7.11.1.2f","Requirement","ECSS-E-ST-20-08_0090631",1,"Unchanged","Water condensation on the surface of the coverglasses shall be prevented."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","8.7.11.2.2b","Requirement","ECSS-E-ST-20-08_0090634",1,"Unchanged","The chamber temperature shall then be increased from ambient temperature to 50 °C at a minimum."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","8.7.13.2f","Requirement","ECSS-E-ST-20-08_0090650",1,"Unchanged","The irradiation shall be performed at doses representative of LEO and GEO mission environments and at least 2 × Fp, as stated in the SCD-CVG."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","8.7.16a","Requirement","ECSS-E-ST-20-08_0090657",1,"Unchanged","The coverglasses shall be exposed to the number of cycles over the range of temperature (both as stated in the SCD-CVG) with a total cycle duration not greater than 10 minutes."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","8.7.17b","Requirement","ECSS-E-ST-20-08_0090661",1,"Unchanged","The coverglass shall show no evidence of physical degradation."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","9.2.1.2.2b","Requirement","ECSS-E-ST-20-08_0090675",1,"Unchanged","The SCD-EPD shall be prepared by the supplier in conformance with Annex E and provided to the customer for reviewing and agreement."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","9.2.2.1a","Requirement","ECSS-E-ST-20-08_0090680",1,"Unchanged","Delivered integral protection diodes shall be processed and inspected in conformance with the requirements of the process identification document (PID) defined in clause 7.2, and "]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","9.4.2a","Requirement","ECSS-E-ST-20-08_0090689",1,"Unchanged","Acceptance tests for integral protection diodes shall consist of the tests specified in Table 9‑1. "]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","9.4.4d","Requirement","ECSS-E-ST-20-08_0090695",1,"Unchanged","The data documentation of acceptance tests shall be delivered together with the delivered cells/diodes and the qualification test lot."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","9.5.2e","Requirement","ECSS-E-ST-20-08_0090708",1,"Unchanged","The integral protection diodes shall be equipped with front interconnectors as step 7 in Table 7‑2."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","9.5.3b","Requirement","ECSS-E-ST-20-08_0090713",1,"Unchanged","During the qualification, all external protection diodes shall be equipped with n- and p-interconnectors, except for the diodes of subgroup O. "]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","9.5.4.2b","Requirement","ECSS-E-ST-20-08_0090719",1,"Unchanged","The test samples shall be chosen statistically and at random from a minimum number of diodes, stated in the SCD-BSC or SCD-EPD, and from the first n batches, where n is also stated in the SCD-BSC or SCD‑EPD.","NOTE \tFor sampling see ISO 2859.\n"]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","9.6.2.5.1b","Requirement","ECSS-E-ST-20-08_0090730",1,"Unchanged","Peeling, blistering and delamination of contacts shall not be present."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","9.6.4.2a","Requirement","ECSS-E-ST-20-08_0090737",1,"Unchanged","All external protection diode qualification samples shall be submitted to thermal cycling consisting of TBSc cycles from -TBS1 °C to + TBS2°C under nitrogen gas environment, where the values TBSc, TBS1 and TBS2 are values to be specified in the SCD-EPD."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","9.6.6.2d","Requirement","ECSS-E-ST-20-08_0090746",1,"Unchanged","The duration of the test shall be 30 days."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","9.6.10.2d","Requirement","ECSS-E-ST-20-08_0090759",1,"Unchanged","It shall be assured that the adhesion of the used tape is within a tolerance of + 10 %."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","9.6.12.2b","Requirement","ECSS-E-ST-20-08_0090765",1,"Unchanged","The flux density and energy shall be uniform over the cell area within ±10 %. "]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","9.6.12.2e","Requirement","ECSS-E-ST-20-08_0090768",1,"Unchanged","The irradiation facility, dosimetry included, shall be approved by the customer. "]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","9.6.16.2d","Requirement","ECSS-E-ST-20-08_0090784",1,"Unchanged","The voltage level shall be 12 kV for single and multi-pulse testing."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","9.6.17.2c","Requirement","ECSS-E-ST-20-08_0090791",1,"Unchanged","One switching cycle shall be defined as a vice-versa cycle between the reverse bias and forward bias points as defined in the Figure 9‑1. "]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","9.6.17.3a","Requirement","ECSS-E-ST-20-08_0090795",1,"Unchanged","The diode characteristics test shall satisfy the pass-fail criteria stated in the SCD-BSC or SCD-EPD."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","9.7.2b","Requirement","ECSS-E-ST-20-08_0090804",1,"Unchanged","Failed components shall be identified as such and included in the delivery. "]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","10.1.1.3d","Requirement","ECSS-E-ST-20-08_0090815",1,"Unchanged","For a test lot of single solar cells, the spectral distribution of the Sun simulator in the test plane shall be matched to the AM0 spectrum for errors due to the spectral response spread of the relevant lot of cells to be 1 % or less, as follows:\n1.\tMeasure the short-circuit current of 10 solar cells accepted by the customer as representing a worst-case simulation of the spectral response spread of the cells to be tested, at the constant nominal intensity of the Sun simulator.\n2.\tFrom the measured spectral response of the cells (ìn conformance with clause 7.5.5) and the AM0 spectrum given in Table 10‑1:\n(a)\tCalculate the short-circuit current and multiply it by a common factor which adjusts the average calculated short-circuit current to the average current resulting from the simulator measurements.\n(b)\tEnsure that the difference between the calculated and measured current of each individual cell does not exceed 1 % of the measured current."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","10.1.2g","Requirement","ECSS-E-ST-20-08_0090823",1,"Unchanged","The irradiance uniformity of the Sun simulator in the test area shall not introduce errors due to the dimension of the reference cell used to adjust Sun simulator irradiance to AM0 equivalent conditions higher than 1 % or other value proposed by the supplier and accepted by the customer.","NOTE \tSee clause 10.2 for requirements of reference solar cells.\n"]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","10.2.1b","Requirement","ECSS-E-ST-20-08_0090829",1,"Unchanged","The number and type of primary standard cells shall be mutually agreed upon between the supplier and the customer."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","10.2.2.3.3a","Requirement","ECSS-E-ST-20-08_0090842",1,"Unchanged","For linearity measurements methods, annex I of ISO 15387:2005 shall be applied.  "]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","10.2.6.1a","Requirement","ECSS-E-ST-20-08_0090851",1,"Unchanged","The irradiance in the test plane shall be adjusted to the AM0 equivalent intensity by means of an SWS for single junction solar cells with a deviation from the calibrated short-circuit current of the SWS not be higher than 1 %."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","11.1.3.1b","Recommendation","ECSS-E-ST-20-08_0091083",1,"Unchanged","The parameters of the network analyser should be adjusted using the network analyser in the B/A mode (B/A= (Vcell+Vshunt)/Vshunt), ensuring that the channels are not inverted, as follows:\n1.\tfrequency range: 10 Hz to 10 MHz;\n2.\tnumber of frequencies Nf : at least 26;\n3.\tstep type: logarithmic;\n4.\tbandwidth: automatic or otherwise limited to few Hz in order to limit the noise at low frequency;\n5.\tinjection level: default value of the network analyser;\n6.\tprogram the network analyser to record the B/A values in the complex form X+j ´Y; or in the amplitude |B/A| and phase j (B/A)."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","11.1.3.2d","Requirement","ECSS-E-ST-20-08_0090862",1,"Informative Change","Adjust the injection level of the network analyser as follows:\n1.\tConnect the cell in place of the short-circuit and keep the voltage supply at 0 V.\n2.\tBegin at 0 dB and lower the signal with 3 dB steps until there is no change at low frequency (variation lower than 0,1 dB).\n3.\tMonitor the selected injection level.","NOTE \tThe injection level is selected low enough so as not to generate a variation of the impedance curves when the level changes."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","11.2.2.4a","Recommendation","ECSS-E-ST-20-08_0091100",1,"Unchanged","Since the voltage of the test specimen at the moment of the short-circuit release is difficult to measure (due to the high frequency oscillations created by the parasitic harness inductance), one of the following two methods should be used to determine the voltage:\n¾\tmathematical analysis to find a curve without oscillation that fits the voltage curve measured;\n¾\tcalculation of the intersection of two voltage curves. ","NOTE \tExample of two voltage curves that can be used for this purpose are the first voltage curve at the test specimen terminals and the second voltage curve at the capacity tester terminal (+) and test specimen terminal (-).\n"]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","A.2.1<4>a","Requirement","ECSS-E-ST-20-08_0090881",1,"Unchanged","In conformance with clause 5.2, the SCD-PVA shall include the description and justification for any deviation in the in-process, acceptance and qualification tests."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","A.2.1<8.3>a","Requirement","ECSS-E-ST-20-08_0090894",1,"Unchanged","For electrical continuity check, in conformance with clause 5.5.3.3.2, the SCD-PVA shall state the following conditions for checking the continuity of the strings: \n1.\tcurrent to be applied, in A, or voltage to be measured, in V.\n2.\tspecified illumination to performed the measurement."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","A.2.1<8.3>g","Requirement","ECSS-E-ST-20-08_0090900",1,"Unchanged","For thermal sensor test, in conformance with clause 5.5.3.3.8, the SCD-PVA shall state:\n1.\tThe resistance of the thermal sensor as a function of the temperature.\n2.\tThe range of resistance to be obtained from the test, in W.","NOTE \tA reference to a calibration table, included in the SCD, can be used.\n"]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","A.2.1<8.11>a","Requirement","ECSS-E-ST-20-08_0090909",1,"Unchanged","In conformance with clause 5.5.3.10, the SCD-PVA shall state:\n1.\tThe test method, either airscan, or C-scan, or destructive test, for the integrity of the skin to honeycomb.\n2.\tThe acceptance criteria."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","B.2.1<4>a","Requirement","ECSS-E-ST-20-08_0090914",1,"Unchanged","In conformance with clause 6.1.2, the SCD-SCA shall include the justification for any deviation in the in-process, acceptance and qualification tests."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","B.2.1<6.5>a","Requirement","ECSS-E-ST-20-08_0090920",1,"Unchanged","In conformance with clause 6.4.3.6, the SCD-SCA shall include the following:\n1.\tThe maximum value of the solar absorptance as a percentage of SCAs with tolerances.\n2.\tThe maximum value of normal emittance as a percentage (%) of SCAs with tolerances."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","C.2.1<2>a","Requirement","ECSS-E-ST-20-08_0090932",1,"Unchanged","The SCD-BSC shall list the applicable and reference documents to support the generation of the document."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","C.2.1<6.4>a","Requirement","ECSS-E-ST-20-08_0090939",1,"Unchanged","In conformance with clause 7.5.11, the SCD-BSC shall include the maximum value of the surface finish (Rz) in mm."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","C.2.1<7.3>a","Requirement","ECSS-E-ST-20-08_0090950",1,"Unchanged","In conformance with clause 7.5.3.2, the SCD-BSC shall include the pass-fail values shown in Table C-1, for\n1.\tthe individual solar cells, and\n2.\tthe minimum average."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","C.2.1<7.10>a","Requirement","ECSS-E-ST-20-08_0090958",1,"Unchanged","In conformance with clause 7.5.13.2, the SCD-BSC shall include:\n1.\tFor general characterization of solar cells, the dosages at 1 MeV, in e- cm-2.\n2.\tFor mission specific qualification, the expected dose for the envisaged application, Fp, at 1MeV, in e- cm-2.\n3.\tThe electron irradiation at transfer orbit dose at 1MeV, in e- cm-2, when specified by the mission requirements."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","D.2.1<3>a","Requirement","ECSS-E-ST-20-08_0090967",1,"Unchanged","The SCD-CVG shall include any additional definition, abbreviation or symbol used."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","D.2.1<6>a","Requirement","ECSS-E-ST-20-08_0090970",1,"Unchanged","In conformance with clause 8.3.3, the SCD-CVG shall include a figure defining the coating orientation method for coverglass front surface coating identification.","NOTE \tThis figure can be the same as the one mentioned in clause D.2.1<8.4>.\n"]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","D.2.1<8.9>a","Requirement","ECSS-E-ST-20-08_0090986",1,"Unchanged","In conformance with clause 8.7.8, the SCD-CVG shall include:\n1.\tThe minimum value of the flatness or bow, as a maximum deviation, in mm.\n2.\tThe maximum value of coverglass displacement, from an optically flat surface over a specified distance in mm, for localized flatness deformations, in mm."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","D.2.1<8.11>a","Requirement","ECSS-E-ST-20-08_0090988",1,"Unchanged","In conformance with clause 8.7.11.1, the SCD-CVG shall state the chemical contents (type and percentage (%) in the mist) of the humid environment when there are specific requirements on the contents of the environment."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","E.2.1<5>a","Requirement","ECSS-E-ST-20-08_0090997",1,"Unchanged","The SCD-EPD shall include:\n1.\tReference to the procurement specification of the supplier.\n2.\tThe following characteristics of the external protection diodes:\n(a)\tgrowth technique;\n(b)\tdoping element;\n(c)\torientation;\n(d)\tmain breakage direction;\n(e)\tbase resistivity;\n(f)\tthickness."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","E.2.1<7.7>a","Requirement","ECSS-E-ST-20-08_0091011",1,"Unchanged","In conformance with clause 9.6.7.3, the SCD-EPD shall include the maximum and minimum values of the contact thickness in mm."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","E.2.1<7.12>a","Requirement","ECSS-E-ST-20-08_0091016",2,"Normative Change","In conformance with requirement 9.6.18.2e, the SCD-EPD shall include the total number of test steps in reverse and forward bias mode, VREV, IFW and the maximum allowables IREV and VFW."]
["ECSS-E-ST-20-08C Rev.1","ECSS - Superseded v1.0","G.3.1d","Requirement","ECSS-E-ST-20-08_0091024",1,"Unchanged","The DDP for SCA, BSC, CVG and protection diode shall consist of failed SCAs, BSCs, CVGs and EPDs list and the corresponding non conformance reports , including:\n1.\tThe reference number and description of the test or measurement as stated in this Standard or in the corresponding SCD.\n2.\tThe identification of failed component (for SCDs, BSCs, coverglasses and protection diodes).\n3.\tThe failed parameter and the failure mode of the component (for SCDs, BSCs, coverglasses and protection diodes).\n4.\tA detailed failure analysis report. "]
["ECSS-E-ST-10-24C","ECSS - Superseded v1.0","5.1a","Requirement","ECSS-E-ST-10-24_1290001",1,"Created","An interface management plan shall be established by the interface responsible to describe the Interface Management approach."]
["ECSS-E-ST-10-24C","ECSS - Superseded v1.0","5.3e","Requirement","ECSS-E-ST-10-24_1290013",1,"Created","Nonconformance to interface requirements shall be treated as major NCR in accordance with the NCR process as defined in ECSS-Q-ST-10-09."]
["ECSS-E-ST-10-24C","ECSS - Superseded v1.0","5.4e","Requirement","ECSS-E-ST-10-24_1290018",1,"Created","The ICD shall be put under configuration control prior to interface end suppliers PDR."]
["ECSS-E-ST-10-24C","ECSS - Superseded v1.0","5.5e","Requirement","ECSS-E-ST-10-24_1290024",1,"Created","The interface definition agreed change shall be listed, until relevant CR content is incorporated in a new version of a baseline ICD.","NOTE \tInterface definition agreed change is as documented in the agreed CR."]
["ECSS-E-ST-10-24C","ECSS - Superseded v1.0","A.2.1<2>c","Requirement","ECSS-E-ST-10-24_1290036",1,"Created","The IRD shall include the following references:\n1.\tProduct tree (as defined in ECSS-M-ST-10 Annex B),\n2.\tSpecification tree (as defined in ECSS-E-ST-10),\n3.\tReferences to requirements specified in other Technical requirement specifications or Standards which are applicable for a particular Interface.","NOTE \tFor example, an IRD can refer to individual requirements coming from Technical Requirement Specification such as GDIR (General Design and Interface Requirements) or SSS (System Support Specification) or Standards such as MIL-STD-1553 Bus."]
["ECSS-E-ST-10-24C","ECSS - Superseded v1.0","A.2.1<4>e","Requirement","ECSS-E-ST-10-24_1290043",1,"Created","The IRD shall specify the requirements of an interface, for all identified interface ends."]
["ECSS-E-ST-10-24C","ECSS - Superseded v1.0","B.2.1<2>a","Requirement","ECSS-E-ST-10-24_1290051",1,"Created","The responsibilities of the interfacing organizations for development of the ICD shall be stated. "]
["ECSS-E-ST-10-24C","ECSS - Superseded v1.0",null,"Requirement","ECSS-E-ST-10-24_1290064",1,"Created","In case the ICD addresses more than one interface, the interface definition shall be grouped either per physical/logical interface, or per nature of interface.","NOTE 1\tAn example of physical/logical grouping is arranging the interface data by a pair of interface ends (see Figure B-1).\nNOTE 2\tAn example of grouping by nature is arranging the interface data by discipline such as mechanical, electrical, thermal and software/data (see Figure B-1).\nNOTE 3\tIt is a good practice to group the interface requirements by the interface natures defined in Annex E."]
["ECSS-E-ST-10-24C","ECSS - Superseded v1.0","C.2.1<4>a","Requirement","ECSS-E-ST-10-24_1290070",1,"Created","The applicable dictionary or glossary and the meaning of specific terms or abbreviation utilized in IDD shall be defined."]
["ECSS-E-ST-10-24C","ECSS - Superseded v1.0","C.2.2<1>a","Permission","ECSS-E-ST-10-24_1290075",1,"Created","The IDD may take different forms depending on the kind of interface end it documents.","NOTE \tExamples of different forms are: a mechanical drawing, interface 3D CAD model, electrical circuit schematic, software API, software architectural or detailed design document."]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","5.2.4.3a","Requirement","ECSS-E-ST-50_0970014",1,"Unchanged","During the space communication system implementation activity the supplier shall deliver the complete communication system to the customer. \n"]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","5.2.4.3c","Requirement","ECSS-E-ST-50_0970016",1,"Unchanged","The supplier shall provide all test and check­out procedures used to verify the system (CSVP), in conformance with the DRD in Annex D;\n"]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","5.2.6.3a","Requirement","ECSS-E-ST-50_0970024",1,"Unchanged","During the space communication system operation activities, the space communication system shall be operated to meet the mission’s system requirements.\n"]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","5.4.4a","Requirement","ECSS-E-ST-50_0970033",1,"Unchanged","The design of the space communication system shall enable essential telecommands to be decoded and control signals distributed even when all other systems, including the CDMU, are non­operational.\n"]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","5.5.1a","Requirement","ECSS-E-ST-50_0970042",2,"Normative Change","The design of the space communication system shall ensure that essential telemetry can be transmitted at all spacecraft attitudes, and at all anticipated attitude rates.\n","NOTE\t1\tIn some missions this provision can be unachievable. Its intent is that ground controllers can always obtain telemetry from the spacecraft for contingency operations and failure recovery.\nNOTE\t2\tIn some deep space missions (additional) essential telemetry can be implemented by the transmission of basic health status information via dedicated sub-carriers only or tones modulation (semaphores approach).\n"]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","5.5.6a","Requirement","ECSS-E-ST-50_0970050",1,"Unchanged","The telemetry downlink shall support a range of simultaneous source data rates with a given priority and respect for maximum latency times for each data source.\n"]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","5.6.7a","Requirement","ECSS-E-ST-50_0970059",1,"Unchanged","All mission phases shall be supported including AIT, pre­launch, launch, operations execution, and end of life.\n"]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","5.6.11.4a","Requirement","ECSS-E-ST-50_0970068",1,"Unchanged","The space link shall be adaptable to a range of failure modes including:\n1.\tloss of link,\n2.\treduction in link margin, and\n3.\tsporadic carrier acquisition.\n"]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","5.6.12.1b","Recommendation","ECSS-E-ST-50_0970226",1,"Unchanged","The total number of frequencies used by a project should be minimized.\n"]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","5.6.12.3a","Requirement","ECSS-E-ST-50_0970079",1,"Informative Change","Unwanted RF emissions shall be kept at a level such that they do not interfere with users of other bands.\n","NOTE \tRequirements on spurious emissions are described in ECSS-E-ST-50-05 and address both:\n·\ta global limitation on the level of the spurious signals over the whole frequency spectrum, and\n·\tspecial protection applicable to the band of the particularly interference­sensitive services: radio astronomy and deep space.\n"]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","5.6.13.5a","Requirement","ECSS-E-ST-50_0970088",1,"Unchanged","ARQ settings shall be verified in end­to­end simulations under all expected conditions to ensure that there is neither unnecessary loss of data nor excessive re­transmission.\n"]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","5.7.1.5a","Requirement","ECSS-E-ST-50_0970102",2,"Normative Change","The on-board network shall provide medium access mechanisms to enable all connected nodes to access the on-board sub­network in order to transfer data.\n"]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","5.7.2.2a","Requirement","ECSS-E-ST-50_0970107",2,"Deleted","<<deleted>>\n"]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","5.7.4.3a","Requirement","ECSS-E-ST-50_0970244",1,"Created","The inter-spacecraft network shall provide a network management service supporting configuration, operations, monitoring, and provisioning of the network in order to provide high reliability and availability of the inter-spacecraft network.\n"]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","5.8.5a","Requirement","ECSS-E-ST-50_0970118",1,"Unchanged","The ground network shall enable the hot redundant operation of nodes used for the control and operation of critical mission functions.\n"]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","A.2.1<6>a","Requirement","ECSS-E-ST-50_0970127",1,"Unchanged","The CSRD shall include the following launch information\n1.\tThe launch vehicle, the launch site location and the ascent trajectory.\n2.\tFor orbital vehicles, the orbit injection characteristics."]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","A.2.1<7.1>a","Requirement","ECSS-E-ST-50_0970132",1,"Unchanged","The CSRD shall list the high level requirements on the space communication system, at a level appropriate to enable all significant aspects of the communication system technical baseline to be elaborated.\n    ","NOTE \this in turn enables: \n·\tinformed decision making concerning the development and procurement of the communication system components, and \n·\tthe communication system design drivers to be established."]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","A.2.1<7.2>d","Requirement","ECSS-E-ST-50_0970138",1,"Unchanged","For missions that involve multiple space segment elements, such as cluster missions, orbiter­lander combinations, lander­rover combinations, and missions with deployable probes, the CSRD shall list the requirements on the communications between those elements."]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","B.2.1<6>a","Requirement","ECSS-E-ST-50_0970150",1,"Unchanged","The CSBD shall describe: \n1.\tall of the communication system analysis and system studies to design a communication system that meets the objectives of the space mission, and\n2.\tthe justification of the analysis and studies referred to in B.2.1<6>a1. "]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","B.2.1<9>c","Requirement","ECSS-E-ST-50_0970157",1,"Informative Change","The CSBD shall describe special operational procedures to be used for contingency operation of the communication system, i.e. in case of degradation of its normal performance.\n","NOTE \tThese operational procedures can include unidirectional operation of the communication system, e.g. command­in­the­blind and telemetry­in­the­blind, and operation at reduced space link data rates.\n"]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","C.2.1<2>a","Requirement","ECSS-E-ST-50_0970168",1,"Unchanged","The CSAD shall list the applicable and reference documents in support to the generation of the document."]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","C.2.1<5>b","Requirement","ECSS-E-ST-50_0970176",1,"Unchanged","For each technique referred to in C.2.1<5>a, the CSAD shall include at least the following:\n1.\tthe objective of the analysis,\n2.\ta detailed description of the analysis technique,\n3.\ta description of any tools used to carry out the analysis,\n4.\ta list of any assumptions made concerning the communication system or its environment during the analysis,\n5.\ta list of starting conditions for the analysis,\n6.\tcopies of all inputs to the analysis,\n7.\tthe results of the analysis,\n8.\tan appraisal of the analysis drawing conclusions and inferences with respect to the communication system, and\n9.\trecommendations for the communication system based on the analysis.","NOTE \tThe objective is that the analysis results can be reviewed offline, and the analyses can be repeated. \n"]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","D.2.1<4>c","Requirement","ECSS-E-ST-50_0970185",1,"Unchanged","The CSVP shall list any special tools or facilities to be used."]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","D.2.1<6>a","Requirement","ECSS-E-ST-50_0970188",1,"Unchanged","The CSVP shall describe the tools, equipment, and facilities associated with the communication system that can be made available to support other verification activities, such as the ground system or flight system verification."]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","F.2.1<4>a","Requirement","ECSS-E-ST-50_0970204",1,"Unchanged","The CSDDD shall contain the detailed design of the communication system, with all critical detailed design decision justifications, including:\n1.\tthe requirements applicable to each of the major components of the communication system identified in the CSADD,\n2.\tthe detailed design of each major component of the communication system,\n3.\ta justification of all design decisions relating to the detailed design of each component, and\n4.\ta complete description of all of the interfaces to each component."]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","F.2.2a","Permission","ECSS-E-ST-50_0970233",1,"Unchanged","This DRD imposes no constraints on the tools used to elaborate the detailed design, and some elements of the detailed design, that can only be viewed with the aid of the tools used in the elaboration of the design, may be accepted."]
["ECSS-E-ST-50C Rev. 1","ECSS - Superseded v1.0","H.2.1<4>a","Requirement","ECSS-E-ST-50_0970215",1,"Unchanged","The CSOM shall describe the procedures used to commission the communication system during the early phases of the mission;"]
["ECSS-E-AS-50-23C","ECSS - Superseded v1.0","4a","Requirement","ECSS-E-AS-50-23_1540001",1,"Created","CCSDS 732.0-B-3, AOS Space Data Link Protocol, Issue 3, September 2015 shall apply with the following modifications listed in Table 4‑1."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.2.4.1b","Requirement","ECSS-E-ST-40_0860008",1,"Created","The customer shall specify the content and media of the delivery.\n","EXPECTED OUTPUT: Delivery content and media [RB, SSS; SRR]."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.2.5a","Requirement","ECSS-E-ST-40_0860017",1,"Created","The customer shall conduct a system requirements review (SRR) in accordance with 5.3.4.1a."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.3.2.4d","Requirement","ECSS-E-ST-40_0860027",1,"Created","The supplier shall define in the SDP the verification and validation strategy for automatic code generation as a result of the trade off between the qualification of the code generation toolchain and the end to end validation strategy of the software item, or any combination thereof, in relation with ECSS-Q-ST-80 clause 6.2.8.\n","EXPECTED OUTPUT: Automatic code generation verification and validation strategy [MGT, SDP; SRR, PDR]."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.3.4.1a","Requirement","ECSS-E-ST-40_0860036",1,"Created","After completion of the software requirements baseline specification, a system requirements review (SRR) shall take place.\nAIM: Reach the approval of the software requirements baseline by all stakeholders.\n","EXPECTED OUTPUT: Approved requirements baseline [RB; SRR]."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.3.4.4a","Requirement","ECSS-E-ST-40_0860041",1,"Created","After completion of the software validation against the requirements baseline, and the verification activities, a qualification review (QR) shall take place. \n","EXPECTED OUTPUT: Qualified software product [RB, TS, DDF, DJF, MGT, MF; QR]."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.3.6.2a","Requirement","ECSS-E-ST-40_0860047",1,"Created","For ground segment software, the software life cycle shall be chosen assessing the following constraints for the ground reviews phasing: \n    1. the baseline of the software requirements (e.g. SWRR) is performed before the ground segment PDR ,\n    2. the software PDR is performed before the ground segment CDR\n    3. all the other software reviews are performed before the ground segment QR.\n","EXPECTED OUTPUT: Ground software review phasing [MGT, SDP;SRR, PDR]"]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.4.3.1a","Requirement","ECSS-E-ST-40_0860059",1,"Created","The supplier shall transform the requirements for the software item into an architecture that:\n    1. describes its top-level structure;\n    2. identifies the software components, ensuring that all the requirements for the software item are allocated to its software components and later refined to facilitate detailed design;\n    3. covers as a minimum hierarchy, dependency, interfaces and operational usage for the software components;\n    4. documents the process, data and control aspects of the product;\n    5. describes the architecture static decomposition into software elements such as packages, classes or units;\n    6. describes the dynamic architecture, which involves the identification of active objects such as threads, tasks and processes;\n    7. describes the software behaviour.\n","EXPECTED OUTPUT: Software architectural design [DDF, SDD; PDR]."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.4.3.6c","Requirement","ECSS-E-ST-40_0860066",1,"Created","The supplier shall design the software such that mission and configuration dependant data are separated e.g. in a database.\n","EXPECTED OUTPUT: Software architectural design with configuration data - [DDF, SDD; PDR, CDR]."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.5.2.4a","Requirement","ECSS-E-ST-40_0860075",1,"Created","The supplier shall use a design method (e.g. object oriented or functional method) to produce the detailed design including:\n    1. software units, their interfaces, and;\n    2. software units relationships.\n","EXPECTED OUTPUT: Software design method [DDF, SDD; CDR]"]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.5.3.2b","Requirement","ECSS-E-ST-40_0860088",1,"Created","The supplier shall test each software unit ensuring that it satisfies its requirements and document the test results.\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Software component design document and code (update) [DDF, SDD, source code; CDR];\n          b.Software unit test reports [DJF, - ; CDR]."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.6.2.1c","Requirement","ECSS-E-ST-40_0860094",1,"Created","The validation effort and the degree of organizational independence of that effort shall be determined, coherent with ECSS-Q-ST-80 clause 6.3.5.19.\n","EXPECTED OUTPUT: Software validation plan - effort and independence [DJF, SValP; PDR]."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.6.3.1a","Requirement","ECSS-E-ST-40_0860097",1,"Created","The supplier shall develop and document, for each requirement of the software item in TS (including ICD), a set of tests, test cases (inputs, outputs, test criteria) and test procedures including: \n    1. testing with stress, boundary, and singular inputs;\n    2. testing the software product for its ability to isolate and reduce the effect of errors; \n        NOTE For example: This reduction is done by graceful degradation upon failure, request for operator assistance upon stress, boundary and singular conditions.\n    3. testing that the software product can perform successfully in a representative operational environment;\n    4. external interface testing including boundaries, protocols and timing test; \n    5. testing HMI applications as per ECSS-E-ST-10-11.\n","EXPECTED OUTPUT: Software validation specification with respect to the technical specification [DJF, SVS; CDR]."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.7.2.4a","Requirement","ECSS-E-ST-40_0860113",1,"Created","The resources and information to install the software product shall be determined and be available. \n","EXPECTED OUTPUT: Installation report [DJF, - ; AR]."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.7.2.4c","Requirement","ECSS-E-ST-40_0860115",1,"Created","It shall be ensured that the software code and databases initialize, execute and terminate as specified in the installation plan. \n","EXPECTED OUTPUT: Installation report [DJF, - ; AR]."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.8.2.1a","Requirement","ECSS-E-ST-40_0860124",1,"Created","The verification process shall be established by the supplier to verify the software products.\n","EXPECTED OUTPUT: Software verification plan - verification process identification [DJF, SVerP; PDR]."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.8.3.4a","Requirement","ECSS-E-ST-40_0860133",1,"Created","The supplier shall verify the software detailed design ensuring that:\n    1. detailed design is externally consistent with the architecture;\n    2. there is internal consistency between software components and software units;\n    3. the traceability between the architecture and the detailed design is complete;\n    4. the software units that are not traced to the components are justified;\n    5. testing is feasible, by assessing that:\n        (a) commandability and observability features are identified and included in the detailed design in order to prepare the effective testing of the performance requirements;\n        (b) computational invariant properties and temporal properties are added within the design;\n        (c) fault injection is possible.\n    6. operation and maintenance are feasible;\n    7. the design is correct with respect to requirements and interfaces, including safety, security, and other critical requirements;\n    8. the design implements proper sequence of events, inputs, outputs, interfaces, logic flow, allocation of timing and sizing budgets, and error handling;\n    9. the design model has been checked;\n    10. 1the hierarchical breakdown from high level components to terminal ones is provided;\n    11. 1the dynamic features (tasks definition and priorities, synchronization mechanisms, shared resources management) are provided and the real-time choices are justified;\n    12. 1the synchronisation between external interface and internal timing is achieved;\n","EXPECTED OUTPUT: The following outputs are expected:\n          a.Detailed design traceability matrices [DJF, SVR or SDD; CDR];\n          b.Detailed design verification report [DJF, SVR; CDR]."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.8.3.9a","Requirement","ECSS-E-ST-40_0860146",1,"Created","The supplier shall identify the requirements of the technical specification and the requirements baseline that cannot be tested in its own environment, and shall forward to the customer a request to validate them at system level.\n    NOTE For example: Some of the requirements cannot be verified because the test environment used for the validation does not allow it. These requirements can only be tested when the software is integrated within the system (e.g. satellite and launcher).\n","EXPECTED OUTPUT: Complement of validation at system level [DJF, SValP; PDR]."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.8.3.13a","Requirement","ECSS-E-ST-40_0860154",1,"Created","As support to the verification of the software requirements, the supplier shall verify the software behaviour using the behavioural view of the logical model produced in 5.4.2.3c.\n","EXPECTED OUTPUT: Software behaviour verification [DJF, SVR; PDR]."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.9.4.2a","Requirement","ECSS-E-ST-40_0860164",1,"Created","Encountered problems shall be recorded and handled in accordance with the applicable procedures.\n","EXPECTED OUTPUT: Problem and nonconformance report [OP, - ; - ]."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.10.2.1b","Requirement","ECSS-E-ST-40_0860173",1,"Created","Software maintenance shall be performed using the same procedures, methods, tools and standards as used for the development.\n","EXPECTED OUTPUT: Maintenance plan - applicability of development process procedures, methods, tools and standards [MF, - ; QR, AR, ORR]."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.10.3.1e","Requirement","ECSS-E-ST-40_0860182",1,"Created","The maintainer shall obtain approval for the selected modification option in accordance with procedures agreed with the customer.\n","EXPECTED OUTPUT: Modification approval [MF; -]"]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.10.4.2a","Requirement","ECSS-E-ST-40_0860184",1,"Created","All changes to the software product shall be documented in accordance with the procedures for document control and configuration management.\n","EXPECTED OUTPUT: Modification documentation [MF, - ;-]."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.10.6.2a","Requirement","ECSS-E-ST-40_0860193",1,"Created","A migration plan shall be developed, documented, and executed, including the following items:\n    1. requirements analysis and definition of migration;\n    2. development of migration tools;\n    3. conversion of software product and data;\n    4. migration execution;\n    5. migration verification;\n    6. support for the old environment in the future;\n    7. operator involvement in the activities.\n","EXPECTED OUTPUT: Migration plan [MF, - ; - ]."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","5.10.7.2a","Requirement","ECSS-E-ST-40_0860202",1,"Created","The maintainer shall notify the retirement plan and related activities, including the following items:\n    1. description of the replacement or upgrade with its date of availability;\n    2. statement of why the software product is no longer to be supported;\n    3. description of other support options available, once support is removed.\n","EXPECTED OUTPUT: Retirement notification [MF, - ; - ]."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","B.2.1<4.4>a","Requirement","ECSS-E-ST-40_0860212",1,"Created","The SSS shall describe the software operational environment."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","B.2.1<5.1>b","Requirement","ECSS-E-ST-40_0860220",1,"Created","When requirements are expressed as models, the supplier shall establish a way to assign identifiers within the model for sake of traceability."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","B.2.1<5.5.2>a","Requirement","ECSS-E-ST-40_0860231",1,"Created","The SSS shall list the requirements on the computer resource utilization (e.g. processor capacity and memory capacity) available for the software item (e.g. sizing and timing). "]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","B.2.1<5.12>a","Requirement","ECSS-E-ST-40_0860240",1,"Created","The SSS shall include the system requirements for the maintenance of the software (including the system requirements for in flight modifications capabilities) .\n    NOTE 1 The supplier’s response is agreed with the customer in the system requirements review (SRR), intended to release the maintenance plan for execution as established in clause 5.10. \n    NOTE 2 Due to the long lifetimes often encountered with flight software, special requirements also exist to ensure that the supporting tools (e.g. compilers, engineering tools and inflight modification tools) can support the in–orbit reprogramming during the specified lifetime."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","C.2.1<1>a","Requirement","ECSS-E-ST-40_0860249",1,"Created","The IRD shall contain a description of the purpose, objective, content and the reason prompting its preparation."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","C.2.1<3>a","Requirement","ECSS-E-ST-40_0860251",1,"Created","The IRD shall include any additional terms, definition or abbreviated terms used."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","C.2.1<6>a","Requirement","ECSS-E-ST-40_0860263",1,"Created","The IRD shall describe if necessary the validation requirements specified to support the demonstration that software requirements are met."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","D.2.1<4.2>a","Requirement","ECSS-E-ST-40_0860270",1,"Created","The SRS shall summarize: \n    1. the physical environment of the target system;\n    2. the hardware environment in the target system;\n    3. the operating environment in the target system;"]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","D.2.1<5.2>b","Requirement","ECSS-E-ST-40_0860281",1,"Created","The SRS shall provide where applicable the link between the requirements and the system states and modes."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","D.2.1<5.4>d","Requirement","ECSS-E-ST-40_0860289",1,"Created","The definition of each interface shall include at least the provided service, the description (name, type, dimension), the range and the initial value."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","D.2.1<5.10>a","Requirement","ECSS-E-ST-40_0860298",1,"Created","The SRS shall list any quality requirement applicable to the software item."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","D.2.1<5.13>a","Requirement","ECSS-E-ST-40_0860301",1,"Created","The SRS shall list any safety requirement applicable to the software item."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","E.2.1<2>a","Requirement","ECSS-E-ST-40_0860316",1,"Created","The ICD shall list the applicable and reference documents to support the generation of the document."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","E.2.1<4>a","Permission","ECSS-E-ST-40_0860684",1,"Created","The ICD may reference the software overview done in the SRS. "]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","E.2.1<5.3>d","Requirement","ECSS-E-ST-40_0860327",1,"Created","The definition of each interface shall include at least the provided service, the description (name, type, dimension), the range and the initial value."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","F.2.1<4.1>b","Requirement","ECSS-E-ST-40_0860337",1,"Created","The SDD shall also describe any system state or mode in which the software operates."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","F.2.1<5.1>b","Requirement","ECSS-E-ST-40_0860347",1,"Created","The architecture structure of the software item shall be described, identifying the software components, their hierarchical relationships, any dependency and interfaces between them. "]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","F.2.1<5.2>g","Requirement","ECSS-E-ST-40_0860356",1,"Created","The SDD shall describe the error handling and fault tolerance principles (e.g. error detection, reporting, logging, and fault containment regions.)"]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","F.2.1<5.4.3>c","Recommendation","ECSS-E-ST-40_0860696",1,"Created","The physical characteristics should be described by stating the type of component, using the implementation terminology (e.g. task, subroutine, subprogram, package and file).\n    NOTE The contents of some components description clauses depend on the component type. For the purpose of this guide, the following categories are used: executable (i.e. contains computer instructions) or non–executable (i.e. contains only data)."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","F.2.1<5.4.8>d","Permission","ECSS-E-ST-40_0860703",1,"Created","If the information in <5.4.8>c. is implicit in the definition of the type of component, a description need not be done. "]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","F.2.1<5.5>a","Requirement","ECSS-E-ST-40_0860384",1,"Created","The SDD shall describe the internal interfaces among the identified software components."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","F.2.1<5.5>c","Requirement","ECSS-E-ST-40_0860386",1,"Created","For each identified internal interface, all the defined data elements shall be included. \n    NOTE The amount of detail to be provided depends strongly on the type of component. "]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","H.2.1<3>a","Requirement","ECSS-E-ST-40_0860402",1,"Created","The SUM shall include any additional terms, definition or abbreviated terms used."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","H.2.1<6>a","Requirement","ECSS-E-ST-40_0860405",1,"Created","The SUM shall identify the software files, including databases and data files, which are necessary for the software to operate, including security and privacy considerations for each file and identification of the software necessary to continue or resume operation in case of an emergency."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","H.2.1<9.4>a","Requirement","ECSS-E-ST-40_0860414",1,"Created","The SUM shall give an overview of the access and security features of the software that are visible to the user, and in particular:\n    - How and from whom to obtain a password\n    - How to add, delete, or change passwords under user control\n    - Security and privacy considerations pertaining to the storage and marking of output reports and other media that the user can generate"]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","H.2.1<10.4>a","Requirement","ECSS-E-ST-40_0860422",1,"Created","The SUM shall include a guide to the command language used, operations and functions."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","I.2.1<4.2>b","Requirement","ECSS-E-ST-40_0860433",1,"Created","The following topics that shall be included:\n    1. roles;\n    2. reporting channels;\n    3. levels of authority for resolving problems;\n    4. organization relationships;\n    5. level of required and implemented independence."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","I.2.1<4.4>a","Requirement","ECSS-E-ST-40_0860436",1,"Created","The SVerP shall summarize the resources to be used to perform the verification activities such as staff, hardware and software tools."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","J.2.1<4.1>b","Requirement","ECSS-E-ST-40_0860452",1,"Created","The SValP shall also address, if it is applicable to the software validation campaign against the requirements baseline, to the software validation campaign against the technical specification, or, for both. "]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","J.2.1<4.1>d","Requirement","ECSS-E-ST-40_0860454",1,"Created","The SValP shall include the validation of the quality requirements."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","J.2.1<4.6>a","Requirement","ECSS-E-ST-40_0860463",1,"Created","The SValP shall describe the software tools, techniques and methods used for validation activities as well as the needed hardware facilities and, testing data, support software (simulators)."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","J.2.1<5>e","Requirement","ECSS-E-ST-40_0860472",1,"Created","The detailed information and the data for the testing procedures shall be provided in the software validation testing specifications."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","K.2.1<3>a","Requirement","ECSS-E-ST-40_0860483",1,"Created","The SUITP shall include any additional terms, definition or abbreviated terms used."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","K.2.1<5.4>b","Recommendation","ECSS-E-ST-40_0860713",1,"Created","The responsibilities specified in <5.4>a. should be described by identifying the groups responsible for managing, designing, preparing, executing the tests. \n    NOTE Groups can include developers, technical support staff, and product assurance staff. "]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","K.2.1<7.5>a","Requirement","ECSS-E-ST-40_0860501",1,"Created","The SUITP shall describe the general criteria to be used to determine whether or not test are passed."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","K.2.1<8.2.3>b","Requirement","ECSS-E-ST-40_0860510",1,"Created","The description specified in a. shall provide the rationale for the test case selection and grouping into test procedures."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","K.2.1<9.2.2>b","Requirement","ECSS-E-ST-40_0860519",1,"Created","Reference to appropriate documentation shall be performed and traceability information shall be provided."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","K.2.1<9.2.4>a","Requirement","ECSS-E-ST-40_0860521",1,"Created","This SUITP shall describe the expected outputs. "]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","K.2.1<10.2.2>a","Requirement","ECSS-E-ST-40_0860530",1,"Created","The SUITP shall describe the purpose of this procedure. "]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","L.2.1<5.2>a","Requirement","ECSS-E-ST-40_0860539",1,"Created","The SVS w.r.t. TS or RB shall describe all the features to be tested, making references to the applicable documentation."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","L.2.1<6.2.2>a","Requirement","ECSS-E-ST-40_0860549",1,"Created","The SVS w.r.t. TS or RB shall describe the test items and the features to be tested. "]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","L.2.1<7.2.1>a","Requirement","ECSS-E-ST-40_0860557",1,"Created","The SVS w.r.t. TS or RB shall describe the test case uniquely. "]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","L.2.1<8.2.1>a","Requirement","ECSS-E-ST-40_0860568",1,"Created","The SVS w.r.t. TS or RB shall identify each test procedure uniquely. "]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","M.2.1<2>a","Requirement","ECSS-E-ST-40_0860577",1,"Created","The SVR shall list the applicable and reference documents to support the generation of the document."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","M.2.1<4.6>a","Requirement","ECSS-E-ST-40_0860586",1,"Created","The SVR shall present in gathering all the specific verification reports that have been planned to be provided w.r.t. the SVerP, including e.g.: \n    1. Traceability (when not already included in related software validation specification), presenting the following traceability matrices: \n        · software validation specifications to TS\n        · software validation specifications to RB\n    2. Feasibility, presenting in gathering all the specific verification reports that have been planned to be provided w.r.t. the SVerP, including e.g.: \n        · Verification of software validation w.r.t. TS as per 5.8.3.8a.\n        · Verification of software validation w.r.t. RB as per 5.8.3.8b.\n        · Verification of software documentation as per 5.8.3.10\n        · Verification of testing as per ECSS-Q-ST-80 clause 7.2.3.6"]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","M.2.1<5.1>a","Requirement","ECSS-E-ST-40_0860588",1,"Created","The SVR shall include the way to compute the technical budgets and margins."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","N.2.1<6>b","Requirement","ECSS-E-ST-40_0860604",1,"Created","For each software item, the SRF shall provide the following information:\n    1. decision to reuse or not reuse, based on the information provided in previous chapters;\n    2. estimated level of reuse;\n    3. assumptions and methods applied when estimating the level of reuse."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","N.2.1<8>b","Requirement","ECSS-E-ST-40_0860607",1,"Created","The SRF shall document the detailed results of the implementation of the identified corrective actions."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","O.2.1<4.7>a","Requirement","ECSS-E-ST-40_0860618",1,"Created","The SDP shall describe the roles and skills of staff involved in the project, the organisational structure, boundaries and interface, the external interface responsibles, and the resources."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","O.2.1<5.2.3>a","Requirement","ECSS-E-ST-40_0860626",1,"Created","The SDP shall describe scope and purpose of each identified review, relevant deliverable and expected outputs. "]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","O.2.1<5.3>g","Requirement","ECSS-E-ST-40_0860635",1,"Created","Any adaptation of the design method (e.g. deviations, extensions, and avoidance of utilization of some methodology features) shall be described or referenced."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","O.2.1<5.5.2>a","Requirement","ECSS-E-ST-40_0860642",1,"Created","The SDP, for each document to be produced (both internal documents and deliverable), shall include the documentation plan stating: \n    1. the documentation file;\n    2. the document name;\n    3. the delivery requirements;\n    4. the review requirements;\n    5. the approval requirements."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","P.2.1<5>b","Requirement","ECSS-E-ST-40_0860654",1,"Created","Review data package documentation shall be according to the deliveries for every review in the Software life cycle chosen (see ECSS-E-ST-40C DRL per review)."]
["ECSS-E-ST-40C","ECSS - Superseded v1.0","P.2.1<7>a","Requirement","ECSS-E-ST-40_0860656",1,"Created","The SRevP shall include:\n    1. The review entry criteria:\n        (a) Review data package is ready.\n        (b) Review team, organization and plan are agreed and ready. \n    2. Review success criteria:\n        (a) Review objectives are met\n        (b) Actions agreed to be closed before this review have been closed\n        (c) RIDs agreed to be closed before this review have been closed\n        (d) RIDs from this review are dispositioned and actions assigned\n    3. The review conclusion, based on the review success criteria.\n        NOTE Possible review conclusions are:\n            · Successful: review success criteria have been met. Authorization to proceed with next life cycle phase is granted.\n            · Successful with rework to be done: review success criteria have been partially met. There are pending corrections for documents and/or Software. Corrections are done according to open SPRs and actions agreed on RIDs. Authorization to proceed with next life cycle phase is granted. Dates for closure of open SPRs and implementation of actions from RIDs are agreed in the review.\n            · Not successful: review success criteria have not been met. Documents to be baselined at the review cannot be baselined, and Software released for the review cannot be used for follow on activities in their current status. Authorization to proceed with next life cycle phase is not granted.\n    4. The review report, including review minutes of meeting content, presentations, RID status metric, dispositioned RIDs, discussions, actions, review conclusion and any other material used during the review."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.1.1a","Requirement","ECSS-E-ST-40-07_1440002",1,"Created","All SMP fields, parameters, constants and properties shall be of either a Primitive Type as per PrimitiveTypes.h in [SMP_FILES], or a User Defined Type published to the Type Library.","NOTE\tThis specification is compliant with the types specified in Table 5-1.\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.1.2c","Requirement","ECSS-E-ST-40-07_1440012",1,"Created","Zulu time shall be time dependent on the system clock of the host machine or an external clock source expressed using the DateTime type.","NOTE\tHigh Real Time systems sometimes uses an external clock source instead of the local system clock of host machine.\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.1.4a","Requirement","ECSS-E-ST-40-07_1440022",1,"Created","All SMP types shall have a unique UUID as per Uuid.h in [SMP_FILES].","NOTE\t1\tThe UUID follows the specification from Open Group (http://pubs.opengroup.org/onlinepubs/9629399/apdxa.htm) \nNOTE\t2\tThe UUID is a 128 bit long unique identifier.\nNOTE\t3\tThe UUID allows for example to:\n·\tUniquely identify types defined in catalogues so that can be bound with implementations defined within packages. \n·\tUniquely identify linked elements within a Catalogue.\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.2.3.1b","Requirement","ECSS-E-ST-40-07_1440031",1,"Created","The IComponent GetState method shall return the current state of the component as per ComponentStateKind.h in [SMP_FILES], specified in Table 5-2."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.2.3.3b","Requirement","ECSS-E-ST-40-07_1440042",1,"Created","All SMP components which implement the IService interface shall ensure their state is fully persisted in a simulation breakpoint and restored on Restore."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.2.4.2d","Requirement","ECSS-E-ST-40-07_1440051",1,"Created","The IReference AddComponent method shall add a component to the collection of referenced components, with the following argument and behaviour:\n1.\tArgument:\n(a)\t“component” giving a reference to the component to be added. \n2.\tBehaviour:\n(a)\tIf the maximum supported number of referenced components is reached, it throws a ReferenceFull exception as per ReferenceFull.h in [SMP_FILES];\n(b)\tIf the reference interface implementation is expecting the given component to inherit from another type it throws an InvalidObjectType exception as per InvalidObjectType.h in [ZIPFLE].","NOTE\tA (typed) reference can attempt to type-cast a component to a specific type, to ensure that all components within the reference inherit from this common base type.\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.2.5.2b","Requirement","ECSS-E-ST-40-07_1440060",1,"Created","The IContainer GetComponent method shall return the component matching the given name, with the following argument and behaviour:\n1.\tArgument:\n(a)\t“name” giving the name of the component to be returned.\n2.\tBehaviour:\n(a)\tIf no component matching the given name is found, it returns nullptr.","NOTE\tAs the container does not support component name duplication, it is not possible to get naming conflict when performing query.\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.2.5.2d","Requirement","ECSS-E-ST-40-07_1440062",1,"Created","The IContainer AddComponent method shall add a component to the collection of contained components, with the following argument and behaviour:\n1.\tArgument:\n(a)\t“component” giving the component to be added.\n2.\tBehaviour:\n(a)\tIf the maximum supported number of components is reached, it throws a ContainerFull exception as per ContainerFull.h in [SMP_FILES];\n(b)\tIf a component with the same name and parent already exists, it throws a DuplicateName exception as per DuplicateName.h in [SMP_FILES]; \n(c)\tIf the container interface implementation is expecting the given component to inherit from another type, it throws an InvalidObjectType exception as per InvalidObjectType.h in [SMP_FILES].","NOTE\tA (typed) container can attempt to type-cast a component to a specific type, to ensure that all components within the container inherit from this common base type.\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.2.6.4b","Requirement","ECSS-E-ST-40-07_1440078",1,"Created","The IEventProvider GetEventSources method shall return a collection of all the contained event sources, with the following behaviour:\n1.\tIf no event source is contained, it returns an empty collection."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.2.7.1b","Requirement","ECSS-E-ST-40-07_1440081",1,"Created","The IEntryPoint Execute method shall be called when the triggering event is emitted."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.2.8.1f","Requirement","ECSS-E-ST-40-07_1440090",1,"Created","All requests created with IDynamicInvocation CreateRequest shall be deleted with a call to IDynamicInvocation DeleteRequest."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.2.8.2f","Requirement","ECSS-E-ST-40-07_1440098",1,"Created","The IRequest GetParameterValue method shall return the value stored at the given index in the parameters collection, with the following argument and behaviour:\n1.\tArgument:\n(a)\t“index” of the parameter for which the value is returned.\n2.\tBehaviour:\n(a)\tIf the given index is less than zero, it throws an InvalidParameterIndex exception as per InvalidParameterIndex.h in [SMP_FILES];\n(b)\tIf the index is greater than or equal to the number of parameters of the request object, it throws an InvalidParameterIndex exception as per InvalidParameterIndex.h in [SMP_FILES];\n(c)\tIf the index is valid, it returns the current value of the parameter.","NOTE\t1\tThe current value is either the initial value from creation of the request object, or the value provided to the last successful call of the SetParameterValue method for the same index.\nNOTE\t2\tThis operation only considers parameters of direction in, out or in/out, but not of type return.\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.2.10.2a","Requirement","ECSS-E-ST-40-07_1440109",1,"Created","All Simulation models which can be failed through a list of possible failures shall implement the IFallibleModel interface as per IFallibleModel.h in [SMP_FILES].","NOTE\t1\tThis is an optional interface. \nNOTE\t2\tThe simulation environment does not automatically persist the state of each failure, as it is the responsibility of the models to store the failure state in persisted data.\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.2.11.1d","Requirement","ECSS-E-ST-40-07_1440116",1,"Created","The ISimpleField GetPrimitiveTypeKind method shall return the primitive type kind of the field."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.2.11.4f","Requirement","ECSS-E-ST-40-07_1440128",1,"Created","The ISimpleArrayField SetValues method shall allow setting all values of an array with the following arguments and behaviour:\n1.\tArguments:\n(a)\t“length” giving the length of the array with values to be set;\n(b)\t“values” giving an array of values to be set in the array.\n2.\tBehaviour:\n(a)\tIf the given length does not match the ArrayField length, it throws a InvalidArraySize as per InvalidArraySize.h in [SMP_FILES];\n(b)\tIf any of the given values simple type kind does not match the array item simple type kind, then it throws an InvalidFieldValue as per InvalidFieldValue.h in [SMP_FILES].\n(c)\tIf any of the given values simple type kind does match the array item simple type kind, then it stores the given values into the corresponding array item values."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.2.11.5b","Requirement","ECSS-E-ST-40-07_1440130",1,"Created","The IField GetView method shall return the View Kind for the field. ","NOTE\tSee Table 4-2 for specification of View Kind.\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.2.11.6e","Requirement","ECSS-E-ST-40-07_1440139",1,"Created","The IForcibleField IsForced shall return true if field is forced or freezed, otherwise it returns false."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.2.12.2d","Requirement","ECSS-E-ST-40-07_1440149",1,"Created","The IPublication PublishOperation method shall allow publishing an operation as per following procedure:\n1.\tCall the IPublication PublishOperation method giving the following arguments:\n(a)\tName of Operation\n(b)\tDescription of Operation\n(c)\tIts view state\n2.\tThe IPublication PublishOperation method returns a pointer to a IPublicationOperation interface\n3.\tUse the returned IPublicationOperation interface to publish each of the parameters and the return value of the operation.","NOTE\tSee clause 5.3.9.2 for specification of the IPublicationOperation interface\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.3.1e","Requirement","ECSS-E-ST-40-07_1440156",1,"Created","The list of log message kinds mapping shall be restored upon breakpoint restoring. ","NOTE\tThis implies that the list of log message kinds and associated names are part of the breakpoints and that models can store log message kinds they need and not continuously ask which LogMessageKind corresponds to a given LogMessageKind name. This leads to more efficient implementations.\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.3.3a","Requirement","ECSS-E-ST-40-07_1440169",1,"Created","The simulation environment shall provide a Scheduler implementing the IScheduler in Services/IScheduler.h in [SMP_FILES]."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.3.3k","Requirement","ECSS-E-ST-40-07_1440179",1,"Created","The IScheduler RemoveEvent method shall remove an already scheduled Event from the Scheduler, with the following argument and behaviour: \n1.\tArgument:\n(a)\t“eventId” giving the unique identifier of the Event.\n2.\tBehaviour:\n(a)\tIf the given EventId does not identify an even currently in the Scheduler, it throws an InvalidEventId exception as per InvalidEventId.h in [SMP_FILES];\n(b)\tIf the EventId is identical to the current executing Event in the schedule, then the call is functionally equivalent to setting the repeat count to 0 via the SetEventCount.","NOTE\tSetting the repeat count to 0 implies that the Event is removed from the scheduler immediately after it is executed.\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.3.3t","Requirement","ECSS-E-ST-40-07_1440188",1,"Created","The complete state of the Scheduler, with the exception of Events scheduled using ZuluTime, shall be part of persisted data and saved/restored to/from breakpoints. "]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.3.4f","Requirement","ECSS-E-ST-40-07_1440197",1,"Created","The IEventManager Unsubscribe method shall remove a pair from the list, with the following arguments and behaviour: \n1.\tArguments:\n(a)\t“event” giving the ID of the event to be unsubscribed;\n(b)\t“entryPoint” giving a pointer to the entry point to be unsubscribed. \n2.\tBehaviour:\n(a)\tIf called with a pair of event identifier and entry point that is currently in the internal list, it removes this pair to the internal list;\n(b)\tIf called with a pair of event identifier and entry point that is not in the internal list, it throws an EntryPointNotSubscribed exception as per Services/EntryPointNotSubscribed.h in [SMP_FILES];\n(c)\tIf called with an invalid event id, it throws an InvalidEventId exception as per Services/InvalidEventId.h in [SMP_FILES]. "]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.3.5c","Requirement","ECSS-E-ST-40-07_1440204",1,"Created","The Resolver ResolveRelative method shall return a reference to an object in the simulation with the following arguments and behaviour:\n1.\tArguments:\n(a)\t“relativePath” giving a path string representing the relative path to the object;\n(b)\t“sender” giving the reference to the Component issuing the request.\n2.\tBehaviour:\n(a)\tIf “relativePath” does not resolve to any object, it returns nullptr;\n(b)\tIf “relativePath” resolves to an object, it returns an IObject reference to the object. ","NOTE\tThe specification of path string is given in clause 5.1.3.\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.3.6e","Requirement","ECSS-E-ST-40-07_1440209",1,"Created","The ILinkRegistry GetLinkSources method shall return the collection of source components for which a link to the given target component has been added to the registry."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.3.7g","Requirement","ECSS-E-ST-40-07_1440218",1,"Created","The ISimulator Initialise method shall call all initialization entry points within the simulation as per the following procedure:\n1.\tIf the simulation is not in Standby state, then it returns and no action is taken;\n2.\tIf Initialise method is called during the execution of the global event SMP_LeavingStandby, then it returns and no action is taken;\n3.\tIf the simulation is in Standby state, it issues the global event “SMP_LeavingStandby” via the Event Manager;\n4.\tAfter returning from the SMP_LeavingStandby global event, the simulator state changes to Initialising state;\n5.\tAfter entering Initializing state, it issues the global event “SMP_EnterInitialising” via the Event Manager;\n6.\tAfter returning from the SMP_EnterInitialising global event, it executes all entry points added via the ISimulator AddInitEntryPoint() method in the order they have been added by the AddInitEntryPoint() call;\n7.\tAfter executing the entry points, it removes the entry points from the list so that in case Initialise is called again, the same Initialise entry point is not called twice;\n8.\tAfter all entry points has been executed, it issues the global event “SMP_LeavingInitialising” via the Event Manager;\n9.\tAfter returning from the “SMP_LeavingInitialising” global event, it changes the simulation state to Standby state;\n10.\tFinally, it issues the global event “SMP_EnteringStandby” via the Event Manager."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.3.7q","Requirement","ECSS-E-ST-40-07_1440228",1,"Created","The ISimulator AddModel method shall add a model to the models collection of the simulator, with the following argument and behaviour:\n1.\tArgument:\n(a)\t“model” giving the model to be added.\n2.\tBehaviour:\n(a)\tIf the Simulation is not in Standby, Building, Connecting or Initializing state, it throws an InvalidSimulatorState exception as per InvalidSimulatorState.h in [SMP_FILES];\n(b)\tIf the name of the new model conflicts with the name of an existing model already added via AddModel, it throws a DuplicateName exception as per DuplicateName.h in [SMP_FILES];\n(c)\tIf the name of the new model conflicts with the name of an existing service already added via AddService, it throws a DuplicateName exception as per DuplicateName.h in [SMP_FILES].","NOTE\t1\tThe container for the models has no upper limit and thus the ContainerFull exception will never be thrown.\nNOTE\t2\tThe method will never throw the InvalidObjectType exception, as it gets a component implementing the IModel interface.\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.3.7y","Requirement","ECSS-E-ST-40-07_1440236",1,"Created","The ISimulator GetLinkRegistry method shall return the interface to the mandatory link registry service.","NOTE\tThis is a type-safe convenience method, to avoid having to use the generic GetService() method. For the standardised services, it is recommended to use the convenience methods, which are guaranteed to return a valid reference.\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.3.8.1a","Requirement","ECSS-E-ST-40-07_1440247",1,"Created","The simulation environment shall provide a component implementing the IStorageReader interface as per IStorageReader.h in [SMP_FILES].","NOTE\t1\tThe IStoragerReader interface provides functionality to read data from storage.\nNOTE\t2\tThe IStoragerReader interface allows objects implementing the IPersist interface to restore their state.\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.3.9.1b","Requirement","ECSS-E-ST-40-07_1440256",1,"Created","The IPublication GetTypeRegistry method shall return a reference to the Type Registry.","NOTE\tSee clause 5.3.10 for details on the Type Registry.\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.3.9.1k","Requirement","ECSS-E-ST-40-07_1440265",1,"Created","The IPublication GetField method shall return an interface to a field, with the following argument and behaviour:\n1.\tArgument:\n(a)\t“fullName“ giving the path relative to the component.\n2.\tBehaviour:\n(a)\tIf no field exists with the given fully qualified name, it throws an InvalidFieldName exception as per InvalidFieldName.hin [SMP_FILES];\n(b)\tIf the field matching the given fully qualified name has a simple type, it returns an ISimpleField instance;\n(c)\tIf the field matching the given fully qualified name is an Array Field, it returns an IArrayField instance;\n(d)\tIf the field matching the given fully qualified name is a Structure Field, it returns an IStructureField instance.","NOTE\tThe path relative to the component is constructed as per clause 5.1.3. Examples:\n·\tMyStructuredField.InnerField\n·\tMyArrayField[2]\n·\tMyStructuredField.ArrayInnerField[2]\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.3.9.1m","Requirement","ECSS-E-ST-40-07_1440267",1,"Created","The IPublication GetProperties method shall return a collection of published properties as per PropertyCollection in Property.h in [SMP_FILES]."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.3.10.1j","Requirement","ECSS-E-ST-40-07_1440283",1,"Created","The ITypeRegistry AddStructureType method shall return the interface to a new Structure type that allows adding fields, with the following arguments and behaviour:\n1.\tArguments:\n(a)\t“name” giving name of the registered type;\n(b)\t“description” giving description of the registered type;\n(c)\t“uuid” giving the universally unique identifier of the registered type.\n2.\tBehaviour:\n(a)\tIf another type with the same uuid already is registered, it throws a TypeAlreadyRegistered exception as per TypeAlreadyRegistered.h in [SMP_FILES]."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.3.10.2b","Requirement","ECSS-E-ST-40-07_1440286",1,"Created","The IType GetPrimitiveTypeKind method shall return the primitive type kind as per PrimitiveTypes.h in [SMP_FILES] for types in the type registry as follows:\n1.\tIf the type cannot be mapped to a primitive type kind, it returns PTK_None;\n2.\tIf the type is registered as a derived type of one of the primitive types, it returns the Primitive type kind;\n3.\tIf the type is one of the primitive types themselves, it returns the corresponding primitive type kind. ","NOTE\t1\tThe primitive types are specified in Table 5-1.\nNOTE\t2\tTypes that cannot be mapped to a primitive type include:\n·\tArrays registered via ITypeRegistry AddArrayType;\n·\tStructures registered via ITypeRegistry AddStructureType.\nNOTE\t3\tDerived types include:\n·\tEnumerations registered via ITypeRegistry AddEnumerationType;\n·\tStrings registered via ITypeRegistry AddStringType;\n·\tInteger types registered via the ITypeRegistry AddIntegerType;\n·\tFloat types registered via the ITypeRegistry AddFloatType.\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.3.10.5a","Requirement","ECSS-E-ST-40-07_1440292",1,"Created","The simulation environment shall provide a class implementing the IArrayType interface as per Publication/IArrayType.h in [SMP_FILES]."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.4.1.2.1c","Requirement","ECSS-E-ST-40-07_1440305",1,"Created","Types that are used in another Type shall be visible for that Type."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.4.1.2.2f","Requirement","ECSS-E-ST-40-07_1440314",1,"Created","The length of a String Value shall not exceed the size of the corresponding String type."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.4.1.2.3a","Requirement","ECSS-E-ST-40-07_1440321",1,"Created","A Named Element Name shall be unique in its context."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.4.1.2.4g","Requirement","ECSS-E-ST-40-07_1440333",1,"Created","For a Reference, the Lower limit shall be less or equal to the Upper limit."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.4.1.2.7a","Requirement","ECSS-E-ST-40-07_1440339",1,"Created","Property Attached Field shall have the type of Property’s Type, or a type derived thereof."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.4.1.2.7f","Requirement","ECSS-E-ST-40-07_1440344",1,"Created","A Property of an Interface shall not be static."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.4.1.2.10a","Requirement","ECSS-E-ST-40-07_1440353",1,"Created","An operation of an Interface shall be public."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.4.1.2.12c","Requirement","ECSS-E-ST-40-07_1440363",1,"Created","The Type link of an EventSource shall point to an EventType."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.4.1.3g","Requirement","ECSS-E-ST-40-07_1440372",1,"Created","Each Field of a model or service that is of a type defined in a catalogue shall be defined in a catalogue."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","5.4.1.3l","Requirement","ECSS-E-ST-40-07_1440377",1,"Created","Each Event Sink of a model or service shall be defined in a catalogue."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","6.1.4.1a","Requirement","ECSS-E-ST-40-07_1440394",1,"Created","Simple value elements shall be mapped to ISO/ANSI C++ variable’s values as follows:\n1.\tSyntax as per “Simple” template in Table 6-2;\n2.\tIf the element value is of EnumerationValue type, mapping is done using the Literal attribute instead of the Value one."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","6.1.4.3d","Requirement","ECSS-E-ST-40-07_1440403",1,"Created","The Static attribute as per ecss.smp.smpcat in [SMP_FILES] shall have the following effect for the Field C++ mapping:\n1.\tIf set to “true”, then the C++ field includes the ‘static’ specifier as per “Field” template in Table 6-1;\n2.\tIf not set, then it has no effect;\n3.\tIf set to “false”, then it has no effect."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","6.1.4.4a","Requirement","ECSS-E-ST-40-07_1440405",1,"Created","Association elements shall be mapped to ISO/ANSI C++ member variables as per “Association” template in Table 6-1;"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","6.1.4.6g","Requirement","ECSS-E-ST-40-07_1440424",1,"Created","The Virtual attribute as per ecss.smp.smpcat in [SMP_FILES] shall have the following effect for the Property C++ mapping:\n1.\tIf set to “true”, then the C++ mapping includes the ‘virtual’ specifier as per “Property Getter” and “Property Setter” template in Table 6-1;\n2.\tIf not set, then the C++ mapping includes the ‘virtual’ specifier as per “Property Getter” and “Property Setter” template in Table 6-1 if the property belongs to an Interface, Model or Service;\n3.\tIf set to “false”, then it has no effect."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","6.1.4.6j","Requirement","ECSS-E-ST-40-07_1440427",1,"Created","The Const attribute as per ecss.smp.smpcat in [SMP_FILES] shall have the following effect for the Property C++ mapping:\n1.\tIf set to “true”, then the C++ mapping includes the ‘const’ specifier at the beginning, as per “Property Getter” and \"Property Setter\" templates in Table 6-1;\n2.\t2. If not set, then it has no effect;\n3.\t3. If set to “false”, then it has no effect."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","6.1.4.7i","Requirement","ECSS-E-ST-40-07_1440436",1,"Created","The Operator attribute as per ecss.smp.smpcat in [SMP_FILES] shall have the following effect for the Operation C++ mapping:\n1.\tIf set, then the C++ mapping of the Operator kind referenced in the Operator attribute as per Table 6-7 is used.\n2.\tIf not set, it has no effect."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","6.1.4.10a","Requirement","ECSS-E-ST-40-07_1440445",1,"Created","EventSource elements shall be mapped to ISO/ANSI C++ member pointer variables as per “EventSource” template in Table 6-1."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","6.1.4.12d","Requirement","ECSS-E-ST-40-07_1440456",1,"Created","If the Type element of the Reference points to a reference type, then the implementation of the AddComponent method of the Smp::IReference interface shall expect the component parameter to be derived from this Type.","NOTE\tSee clause 5.2.4.2 for the details of the AddComponent method of the Smp::IReference interface.\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","6.1.5.2c","Requirement","ECSS-E-ST-40-07_1440463",1,"Created","Literal elements shall be declared within the exact same Enumeration type as in the Catalogue."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","6.1.6.3b","Requirement","ECSS-E-ST-40-07_1440475",1,"Created","Class types shall have a default constructor whose access specifier is defined by the mapping of the Visibility attribute.","NOTE\tSee clause 6.1.3 for details on the mapping of Visibility attributes.\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","6.1.6.3h","Requirement","ECSS-E-ST-40-07_1440481",1,"Created","The BaseClass attribute as per ecss.smp.smpcat in [SMP_FILES] shall have the following effect for the Class C++ mapping:\n1.\tIf set, then the class includes an inheritance link to the base class that the attribute points to;\n2.\tIf not set, then it has no effect."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","6.1.6.4e","Requirement","ECSS-E-ST-40-07_1440486",1,"Created","Association, Property and Operation elements belonging to the Exception type shall be mapped within the exact same C++ class the type is mapped to.","NOTE\tSee clause 6.1.4.4 for details on the mapping of Association elements, clause 6.1.4.6 for details on the mapping of Property elements and clause 6.1.4.7 for details on the mapping of Operation elements.\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","6.1.7.3a","Requirement","ECSS-E-ST-40-07_1440495",1,"Created","Model types shall be mapped to ISO/ANSI C++ classes as follows:\n1.\tSyntax as per “Model” template in Table 6-1;\n2.\tIf Base element is defined, the class inherits from the Base class;\n3.\tIf Interface elements are defined, the class inherits from the Interface classes;\n4.\tIf at least one EntryPoint is defined, the class inherits from the Smp::IEntryPointPublisher class;\n5.\tIf at least one EventSink element is defined, the class inherits from the Smp::IEventConsumer class;\n6.\tIf at least one EventSource element is defined, the class inherits from the Smp::IEventProvider class;\n7.\tIf at least one Container element is defined, the class inherits from the Smp::IComposite class;\n8.\tIf at least one Reference element is defined, the class inherits from the Smp::IAggregate class."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","6.1.7.3g","Requirement","ECSS-E-ST-40-07_1440501",1,"Created","The BaseClass attribute as per ecss.smp.smpcat in [SMP_FILES] shall have the following effect for the Model C++ mapping:\n1.\tIf set, then the class includes an inheritance link to a base class that the attribute points to;\n2.\tIf not set, then it has no effect. "]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","6.2.2g","Requirement","ECSS-E-ST-40-07_1440515",1,"Created","The Initialise function shall register an instance of all Services in the library using the ISimulator AddService method.","NOTE\tThe ownership of the service is handed over to the object implementing ISimulator.\n"]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","6.2.3e","Requirement","ECSS-E-ST-40-07_1440520",1,"Created","The Dynamic Shared Object shall contain a Finalise method as per the “Dynamic Finalise” template in Table 6-8."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","6.2.5d","Requirement","ECSS-E-ST-40-07_1440534",1,"Created","A SMP bundle shall be composed by all the SMP catalogues related to the SMDL packages."]
["ECSS-E-ST-40-07C","ECSS - Superseded v1.0","D.2.1b","Requirement","ECSS-E-ST-40-07_1440543",1,"Created","The SMP Manifest file shall be an ASCII file which contains key-value pairs in the following format: “Key: Value”"]
["ECSS-S-ST-00C","ECSS - Superseded v1.0","9.2a","Requirement","ECSS-S-ST-00_1000001",1,"Created","The customer shall select which ECSS Standards to make applicable and to use to establish the project/product requirements, including use of ECSS-S-ST-00-01 for terms and definitions."]
["ECSS-S-ST-00C","ECSS - Superseded v1.0","9.3b","Requirement","ECSS-S-ST-00_1000006",1,"Created","The documentation identifying the compliance to ECSS requirements applicable to the project (e.g. the ECM) shall include following data:\n    1. The complete list of ECSS requirements applicable to the project (e.g. in the EARM).\n    2. For each requirement, the actual indication of compliance. When deviation is identified the justification is provided."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.2.3.1g","Requirement","ECSS-E-ST-32-02_0260011",1,"Created","Initial tests shall then be conducted at pressure levels not to exceed 50 % of the nominal operating pressure until operating characteristics can be established."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.2.3.2e","Requirement","ECSS-E-ST-32-02_0260017",1,"Created","The minimum internal pressure to guaranty structural stabilization shall be identified and included in the acceptance data package."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.2.3.6b","Requirement","ECSS-E-ST-32-02_0260025",1,"Created","As a minimum, the records specified in 4.2.3.6a shall contain the following information:\n    1. temperature, pressurization history, and pressurizing fluid for both tests and operations;\n    2. number of pressurization cycles experienced as well as the maximum number in safe-life analysis or test;\n    3. results of any inspection conducted, including: inspector, inspection dates, inspection techniques employed, location and character of flaws, flaw origin and cause;\n    4. storage condition;\n    5. maintenance and corrective action performed from manufacturing to operational use, including refurbishment;\n    6. sketches and photographs to show areas of structural damage and the extent of repair;\n    7. acceptance and re-acceptance test performed, including test condition and results;\n    8. analyses supporting the repair or modification which can influence future use capability."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.3.1b","Requirement","ECSS-E-ST-32-02_0260036",1,"Created","For loads different from internal pressure, minimum values of factors of safety for ‘pressurized hardware’ shall be applied in conformance with ECSS-E-ST-32-10.\n    ","NOTE Exceptions to the values provided in Table 4-1 are sometimes specified by the customer or granted with customer approval.\nWhen this is the case for a burst factor, the following relations can be used for determination of the proof factor:\njproof = (1 + jburst) / 2 \twhen jburst < 2,0\njproof = 1,5 \t\twhen jburst > 2,0"]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.3.2.1i","Requirement","ECSS-E-ST-32-02_0260045",1,"Created","For material selection, material design allowables and their characterisation, requirements shall be applied in conformance with ECSS-E-ST-32."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.3.2.2b","Permission","ECSS-E-ST-32-02_0260440",1,"Created","The first qualification test article specified in 4.3.2.2a may be deleted with customer approval."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.3.2.3a","Requirement","ECSS-E-ST-32-02_0260056",1,"Created","All hardware shall be submitted to the following chronology of operations:\n    1. initial NDI, in order to establish the initial condition of the hardware;\n    2. proof pressure test;\n    3. leak test;\n    4. final NDI.\n        ","NOTE For example:\n            · The NDI prior to proof test can be substituted for that of the manufacturing process.\n            · Proof test monitoring by acoustic emission is acceptable for composite items instead of post testing NDI, with customer approval."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.3.3.2a","Requirement","ECSS-E-ST-32-02_0260072",1,"Created","A first qualification test article shall be submitted to the following chronology of operations:\n    1. non-destructive inspection (NDI);\n    2. proof pressure test;\n    3. leak test;\n    4. design burst pressure test;\n    5. burst test."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.3.3.2d","Permission","ECSS-E-ST-32-02_0260444",1,"Created","The leak test after proof pressure test specified in 4.3.3.2c, and the final burst test specified in4.3.3.2c may be deleted with customer approval."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.3.3.3a","Requirement","ECSS-E-ST-32-02_0260081",1,"Created","All hardware shall be submitted to the following chronology of operations:\n    1. initial NDI, in order to establish the initial condition of the hardware;\n    2. proof pressure test;\n    3. leak test;\n    4. final NDI.\n        ","NOTE For example:\n            · The NDI prior to proof test can be substituted for that of the manufacturing process.\n            · Proof test monitoring by acoustic emission is acceptable for composite items instead of post testing NDI, with customer approval."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.3.4.1j","Requirement","ECSS-E-ST-32-02_0260094",1,"Created","For corrosion effects (control and prevention), the requirements in ECSS-E-ST-32 shall apply."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.3.4.2e","Permission","ECSS-E-ST-32-02_0260449",1,"Created","When the vibration loads are enveloped by the other qualification tests, the vibration tests specified in 4.3.4.2c may be deleted with customer approval."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.3.4.3b","Requirement","ECSS-E-ST-32-02_0260110",1,"Created","For COPV, initial NDI operations shall be applied to the over-wrap, in addition to NDI on the liner."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.4.2.1c","Requirement","ECSS-E-ST-32-02_0260122",1,"Created","Except in the case specified in 4.4.2.1d, ‘safe life item’ demonstration shall be performed by analysis or test or both in conformance with ECSS-E-ST-32-01."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.4.2.1i","Requirement","ECSS-E-ST-32-02_0260128",1,"Created","For material selection, material design allowables and their characterisation, requirements shall be applied in conformance with ECSS-E-ST-32."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.4.2.2c","Requirement","ECSS-E-ST-32-02_0260133",1,"Created","Clause 5.4 shall be applied to the qualification tests."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.4.3.1h","Requirement","ECSS-E-ST-32-02_0260146",1,"Created","Qualification tests shall be conducted in conformance with clause 4.4.3.2 to demonstrate the structural adequacy of the design."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.4.3.2a","Requirement","ECSS-E-ST-32-02_0260152",1,"Created","The qualification test article shall be submitted to the following chronology of operations:\n    1. NDI;\n    2. proof pressure test;\n    3. leak test;\n    4. pressure cycling test;\n    5. design burst pressure test."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.4.3.3d","Requirement","ECSS-E-ST-32-02_0260161",1,"Created","Final NDI shall be performed on the over-wrap of the COPS as a minimum."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.4.4.1e","Requirement","ECSS-E-ST-32-02_0260166",1,"Created","The liner of the COPS shall exhibit a LBB failure mode."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.4.4.2e","Requirement","ECSS-E-ST-32-02_0260180",1,"Created","The need to apply external loads in combination with internal pressure during testing shall be considered taking into account their relative magnitude, fatigue and destabilizing effects of external loads."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.4.4.3c","Requirement","ECSS-E-ST-32-02_0260184",1,"Created","For CPS, NDI operations shall be applied to the composite wall as a minimum."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.5.1.2c","Requirement","ECSS-E-ST-32-02_0260191",1,"Created","A ‘safe life item’ demonstration shall be performed by analysis or test or both in conformance with ECSS-E-ST-32-01 for pressure components not submitted to a proof pressure test or for which the proof factor used in the proof pressure test is less than 1,5."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.5.2.2a","Requirement","ECSS-E-ST-32-02_0260207",1,"Created","Clause 5.2 on structural engineering shall be applied."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.5.2.2d","Requirement","ECSS-E-ST-32-02_0260210",1,"Created","The failure mode shall be demonstrated by analysis or test or both according to clause 5.3."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.5.2.2m","Requirement","ECSS-E-ST-32-02_0260219",1,"Created","Inspections shall be applied according to clause 5.7.","NOTE The development approach is illustrated in Figure 4-4. "]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.5.2.4c","Requirement","ECSS-E-ST-32-02_0260231",1,"Created","Clause 5.5 shall be applied to the acceptance tests."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.5.3.2d","Requirement","ECSS-E-ST-32-02_0260238",1,"Created","The failure mode shall be demonstrated by test on full-scale article according to the requirements developed per clauses 5.3.1, 5.3.4 and 5.3.5."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.5.3.2k","Requirement","ECSS-E-ST-32-02_0260245",1,"Created","For material selection, material design allowables and their characterisation, requirements shall be applied in conformance with clause 5.6 and ECSS-E-ST-32."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.5.3.4a","Requirement","ECSS-E-ST-32-02_0260257",1,"Created","All hardware shall be submitted to the following chronology of operations:\n    1. initial NDI, in order to establish the initial condition of the hardware;\n    2. proof pressure test;\n    3. leak test;\n    4. final NDI.","NOTE For example:\n            · The NDI prior to proof test can be substituted for that of the manufacturing process.\n            · Proof test monitoring by acoustic emission is acceptable for composite items instead of post testing NDI, with customer approval."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.1.2a","Requirement","ECSS-E-ST-32-02_0260263",1,"Created","Clause 5.2 on structural engineering shall be applied.\n    ","NOTE Thermal, stress and strain analyses and stiffness, strength and stability demonstrations are sometimes substituted with certification from qualified aerospace suppliers, with customer approval."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.1.2e","Requirement","ECSS-E-ST-32-02_0260267",1,"Created","Qualification tests shall be conducted according to 4.6.1.3 to demonstrate the structural adequacy of the design."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.1.2f","Requirement","ECSS-E-ST-32-02_0260268",1,"Created","A ‘safe life item’ demonstration shall be performed by analysis or test or both in conformance with ECSS-E-ST-32-01 for heat pipes and hazardous fluids containers not submitted to a proof pressure test or for which the proof factor used in the proof pressure test is less than 1,5."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.1.2g","Requirement","ECSS-E-ST-32-02_0260269",1,"Created","Fatigue-life demonstration shall be performed by analysis or test or both in conformance with ECSS-E-ST-32."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.1.2h","Requirement","ECSS-E-ST-32-02_0260270",1,"Created","For corrosion effects (control and prevention), the requirements in ECSS-E-ST-32 shall apply."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.1.2i","Requirement","ECSS-E-ST-32-02_0260271",1,"Created","For hydrogen embrittlement phenomena, requirements shall be applied in conformance with ECSS-E-ST-32-08."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.1.2j","Requirement","ECSS-E-ST-32-02_0260272",1,"Created","For material selection, material design allowables and their characterisation, requirements shall be applied in conformance with ECSS-E-ST-32."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.1.2k","Requirement","ECSS-E-ST-32-02_0260273",1,"Created","For ‘process control’, requirements shall be in conformance with ECSS-Q-ST-70."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.1.2l","Requirement","ECSS-E-ST-32-02_0260274",1,"Created","Inspections shall be applied according to clause 5.7.\n    ","NOTE 1 The development approach for sealed containers is illustrated in Figure 4-10\nNOTE 2 The development approach for cryostats (or Dewars) is illustrated in Figure 4-11\nNOTE 3 The development approach for heat pipes is illustrated in Figure 4-12\nNOTE 4 The development approach for hazardous fluids containers is illustrated in Figure 4-13\nNOTE 5 Failure mode demonstration as per clause 5.3 is sometimes specified for heat pipes by the customer."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.1.3a","Requirement","ECSS-E-ST-32-02_0260275",1,"Created","All cryostats shall be submitted to the following chronology of operations:\n    1. proof pressure test;\n    2. vibration tests;\n    3. design burst pressure test."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.1.3b","Requirement","ECSS-E-ST-32-02_0260276",1,"Created","All heat pipes and hazardous fluids containers shall be submitted to a design burst pressure test."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.1.3c","Requirement","ECSS-E-ST-32-02_0260277",1,"Created","All batteries meeting the pressure vessel definition shall be submitted to the qualification tests as per clause 4.3.2.2."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.1.3d","Requirement","ECSS-E-ST-32-02_0260278",1,"Created","For batteries meeting the pressure vessel definition, the qualification tests to be performed for functional performance shall be defined with customer approval.","NOTE Qualification leak test is sometimes replaced by thermal vacuum test."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.1.3e","Requirement","ECSS-E-ST-32-02_0260279",1,"Created","Clauses 5.4.1, 5.4.2, 5.4.4 and 5.4.6, shall be applied to the qualification tests."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.1.4a","Requirement","ECSS-E-ST-32-02_0260280",1,"Created","The following SPE shall be submitted to a proof pressure test:\n    1. sealed containers with MDP greater than or equal to 0,2 MPa and exhibiting a LBB failure mode;\n    2. cryostats;\n    3. heat pipes;\n    4. hazardous fluids containers. "]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.1.4b","Requirement","ECSS-E-ST-32-02_0260281",1,"Created","Cryostats shall be NDI inspected prior to the proof pressure test."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.1.4c","Requirement","ECSS-E-ST-32-02_0260282",1,"Created","Fusion joints shall be 100 % inspected by means of a NDI method, defined with customer approval, prior and after the proof pressure test."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.1.4d","Requirement","ECSS-E-ST-32-02_0260283",1,"Created","All batteries meeting the pressure vessel definition shall be submitted to the acceptance tests as per clause 4.3.2.3."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.1.4e","Requirement","ECSS-E-ST-32-02_0260284",1,"Created","For batteries meeting the pressure vessel definition, additional acceptance tests shall be defined for functional performance with customer approval."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.1.4f","Requirement","ECSS-E-ST-32-02_0260285",1,"Created","Clauses 5.5.1, 5.5.2, and 5.5.3 shall be applied to the acceptance tests.\n    ","NOTE Proof and leak tests can be performed at the assembled pressurized system level."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.1a","Requirement","ECSS-E-ST-32-02_0260286",1,"Created","The values in Table 4-9 shall be applied as minimum values of factors of safety for internal pressure."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.1b","Requirement","ECSS-E-ST-32-02_0260287",1,"Created","The values specified in ECSS-E-ST-32-10 shall apply as minimum values of factors of safety for loads different from internal pressure.\n    ","NOTE Exceptions to the values provided in Table 4-9 are sometimes specified by the customer or granted with customer approval.\nWhen this is the case for a burst factor, the following relations can be used for determination of the proof factor:\njproof = (1 + jburst) / 2 \twhen jburst < 2,0\njproof = 1,5 \t\twhen jburst > 2,0"]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.2a","Requirement","ECSS-E-ST-32-02_0260288",1,"Created","Clause 5.2 on structural engineering shall be applied."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.2b","Requirement","ECSS-E-ST-32-02_0260289",1,"Created","A stiffness demonstration shall be performed by analysis and test."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.2c","Requirement","ECSS-E-ST-32-02_0260290",1,"Created","A strength and stability demonstration shall be performed by analysis and test."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.2d","Requirement","ECSS-E-ST-32-02_0260291",1,"Created","The failure mode shall be demonstrated by analysis or test or both according to clause 5.3."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.2e","Requirement","ECSS-E-ST-32-02_0260292",1,"Created","The metallic liner of the COSPE shall exhibit a LBB failure mode."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.2f","Requirement","ECSS-E-ST-32-02_0260293",1,"Created","‘Safe life item’ demonstration shall be performed for the metallic liner by analysis or test or both in conformance with ECSS-E-ST-32-01."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.2g","Requirement","ECSS-E-ST-32-02_0260294",1,"Created","Fatigue-life demonstration shall be performed for the composite over-wrap by analysis or test or both in conformance with ECSS-E-ST-32."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.2h","Requirement","ECSS-E-ST-32-02_0260295",1,"Created","Qualification tests shall be conducted in conformance with clause 4.6.2.3 to demonstrate the structural adequacy of the design."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.2i","Requirement","ECSS-E-ST-32-02_0260296",1,"Created","For corrosion effects (control and prevention), the requirements in ECSS-E-ST-32 shall apply."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.2j","Requirement","ECSS-E-ST-32-02_0260297",1,"Created","For hydrogen embrittlement phenomena, requirements shall be applied in conformance with ECSS-E-ST-32-08."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.2k","Requirement","ECSS-E-ST-32-02_0260298",1,"Created","For material selection, material design allowables and their characterisation, requirements shall be applied in conformance with clause 5.6 and ECSS-E-ST-32."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.2l","Requirement","ECSS-E-ST-32-02_0260299",1,"Created","For ‘process control’, requirements shall be in conformance with ECSS-Q-ST-70."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.2m","Requirement","ECSS-E-ST-32-02_0260300",1,"Created","Inspections shall be applied according to clause 5.7.","NOTE The development approach is illustrated in Figure 4-4. "]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.3a","Requirement","ECSS-E-ST-32-02_0260301",1,"Created","A first qualification test article shall be submitted to the following chronology of operations:\n    1. non-destructive inspection (NDI);\n    2. proof pressure test;\n    3. leak test;\n    4. design burst pressure test;\n    5. burst test."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.3b","Permission","ECSS-E-ST-32-02_0260461",1,"Created","The first qualification test article specified in 4.6.2.3a may be deleted with customer approval."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.3c","Requirement","ECSS-E-ST-32-02_0260303",1,"Created","A second qualification test article shall be submitted to the following chronology of operations:\n    1. NDI;\n    2. proof pressure test;\n    3. leak test;\n    4. vibration tests;\n    5. pressure cycling test;\n    6. leak test;\n    7. design burst pressure test;\n    8. burst test."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.3d","Permission","ECSS-E-ST-32-02_0260462",1,"Created","The leak test after proof pressure test specified in 4.6.2.3c, and the final burst test, specified in 4.6.2.3c may be deleted with customer approval."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.3e","Permission","ECSS-E-ST-32-02_0260463",1,"Created","When the vibration loads are enveloped by the other qualification tests, the vibration tests specified in 4.6.2.3c may be deleted with customer approval."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.3f","Requirement","ECSS-E-ST-32-02_0260306",1,"Created","NDI operations shall be applied to the over-wrap, in addition to NDI on the liner."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.3g","Requirement","ECSS-E-ST-32-02_0260307",1,"Created","Clause 5.4 shall be applied to the qualification tests."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.3h","Requirement","ECSS-E-ST-32-02_0260308",1,"Created","The need to apply external loads in combination with internal pressure during testing shall be considered taking into account their relative magnitude, the fatigue and destabilizing effects of external loads."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.3i","Requirement","ECSS-E-ST-32-02_0260309",1,"Created","If external cycling loads are applied, the load shall be cycled to limit for four times the predicted number of operating cycles of the most severe design condition.","NOTE Destabilizing load with constant minimum internal pressure or maximum additive load with a constant MDP."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.4a","Requirement","ECSS-E-ST-32-02_0260310",1,"Created","All hardware shall be submitted to the following chronology of operations:\n    1. initial NDI, in order to establish the initial condition of the hardware;\n    2. proof pressure test;\n    3. leak test;\n    4. final NDI.","NOTE For example:\n            · The NDI prior to proof test can be substituted for that of the manufacturing process.\n            · Proof test monitoring by acoustic emission is acceptable for composite items instead of post testing NDI, with customer approval."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.4b","Requirement","ECSS-E-ST-32-02_0260311",1,"Created","Initial NDI operations shall be applied to the over-wrap, in addition to NDI on the liner."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.4c","Requirement","ECSS-E-ST-32-02_0260312",1,"Created","Clause 5.5 shall be applied to the acceptance tests."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.2.4d","Requirement","ECSS-E-ST-32-02_0260313",1,"Created","Final NDI shall be performed on the over-wrap of the COSPE as a minimum."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.1a","Requirement","ECSS-E-ST-32-02_0260314",1,"Created","The values in Table 4-10 shall be applied as minimum values of factors of safety for internal pressure."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.1b","Requirement","ECSS-E-ST-32-02_0260315",1,"Created","The values specified in ECSS-E-ST-32-10 shall be applied as minimum values of factors of safety for loads different from internal pressure.\n    ","NOTE Exceptions to the values provided in Table 4-10 are sometimes specified by the customer or granted with customer approval.\nWhen this is the case for a burst factor, the following relations can be used for determination of the proof factor:\njproof = (1 + jburst) / 2 \twhen jburst < 2,0\njproof = 1,5 \t\twhen jburst > 2,0"]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.2a","Requirement","ECSS-E-ST-32-02_0260316",1,"Created","Clause 5.2 on structural engineering shall be applied."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.2b","Requirement","ECSS-E-ST-32-02_0260317",1,"Created","A stiffness demonstration shall be performed by analysis and test."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.2c","Requirement","ECSS-E-ST-32-02_0260318",1,"Created","A strength and stability demonstration shall be performed by analysis and test."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.2d","Requirement","ECSS-E-ST-32-02_0260319",1,"Created","The failure mode shall be demonstrated by test on full-scale article according to the requirements developed per clauses 5.3.1, 5.3.4 and 5.3.5."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.2e","Requirement","ECSS-E-ST-32-02_0260320",1,"Created","The liner of the COSPE shall exhibit a LBB failure mode."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.2f","Permission","ECSS-E-ST-32-02_0260464",1,"Created","When the non-metallic liner of the COSPE remains in compression up to MDP and flaws do not propagate during the LBB test, the flaws pre-fabricated in the liner of the LBB full-scale specimen may be through cracks."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.2g","Requirement","ECSS-E-ST-32-02_0260322",1,"Created","‘Safe life item’ demonstration shall be performed in accordance with ECSS-E-ST-32-01:\n    1. by test for non-metallic items;\n    2. by analysis or test or both for metallic items (e.g. metallic bosses)."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.2h","Requirement","ECSS-E-ST-32-02_0260323",1,"Created","Qualification tests shall be conducted according to clause 4.6.3.3 to demonstrate the structural adequacy of the design."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.2i","Requirement","ECSS-E-ST-32-02_0260324",1,"Created","For corrosion effects (control and prevention), the requirements in ECSS-E-ST-32 shall apply."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.2j","Requirement","ECSS-E-ST-32-02_0260325",1,"Created","Embrittlement control shall be applied in accordance with ECSS-E-ST-32-08."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.2k","Requirement","ECSS-E-ST-32-02_0260326",1,"Created","For materials selection, material design allowables and their characterisation, requirements shall be applied in conformance with clause 5.6 and ECSS-E-ST-32."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.2l","Requirement","ECSS-E-ST-32-02_0260327",1,"Created","For ‘process control’, requirements shall be in conformance with ECSS-Q-ST-70."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.2m","Requirement","ECSS-E-ST-32-02_0260328",1,"Created","Inspections shall be applied according to clause 5.7.","NOTE The development approach is illustrated in Figure 4-5."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.3a","Requirement","ECSS-E-ST-32-02_0260329",1,"Created","A first qualification test article shall be submitted to the following chronology of operations:\n    1. non-destructive inspection (NDI);\n    2. proof pressure test;\n    3. leak test;\n    4. design burst pressure test;\n    5. burst test."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.3b","Permission","ECSS-E-ST-32-02_0260465",1,"Created","The first qualification test article specified in 4.6.3.3a may be deleted with customer approval."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.3c","Requirement","ECSS-E-ST-32-02_0260331",1,"Created","A second qualification test article shall be submitted to the following chronology of operations:\n    1. NDI;\n    2. proof pressure test;\n    3. leak test;\n    4. vibration tests;\n    5. pressure cycling test;\n    6. leak test;\n    7. design burst pressure test;\n    8. burst test."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.3d","Permission","ECSS-E-ST-32-02_0260466",1,"Created","The leak test after proof pressure test specified in 4.6.3.3c, and the final burst test specified in 4.6.3.3c may be deleted with customer approval."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.3e","Permission","ECSS-E-ST-32-02_0260467",1,"Created","When the vibration loads are enveloped by the other qualification tests, the vibration tests specified in 4.6.3.3c may be deleted with customer approval."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.3f","Requirement","ECSS-E-ST-32-02_0260334",1,"Created","NDI operations shall be applied to the over-wrap, in addition to NDI on the liner."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.3g","Requirement","ECSS-E-ST-32-02_0260335",1,"Created","Clause 5.4 shall be applied to the qualification tests."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.3h","Requirement","ECSS-E-ST-32-02_0260336",1,"Created","The need to apply external loads in combination with internal pressure during testing shall be considered taking into account their relative magnitude, the fatigue and destabilizing effects of external loads."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.3i","Requirement","ECSS-E-ST-32-02_0260337",1,"Created","If external cycling loads are applied, the load shall be cycled to limit for four times the predicted number of operating cycles of the most severe design condition.","NOTE Destabilizing load with constant minimum internal pressure or maximum additive load with a constant MDP."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.4a","Requirement","ECSS-E-ST-32-02_0260338",1,"Created","All hardware shall be submitted to the following chronology of operations:\n    1. initial NDI, in order to establish the initial condition of the hardware;\n    2. proof pressure test;\n    3. leak test;\n    4. final NDI.","NOTE For example:\n            · The NDI prior to proof test can be substituted for that of the manufacturing process.\n            · Proof test monitoring by acoustic emission is acceptable for composite items instead of post testing NDI, with customer approval."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.4b","Requirement","ECSS-E-ST-32-02_0260339",1,"Created","Initial NDI operations shall be applied to the over-wrap, in addition to NDI on the liner."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.4c","Requirement","ECSS-E-ST-32-02_0260340",1,"Created","Clause 5.5 shall be applied to the acceptance tests."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","4.6.3.4d","Requirement","ECSS-E-ST-32-02_0260341",1,"Created","Final NDl shall be performed on the over-wrap of the COSPE as a minimum."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.2a","Requirement","ECSS-E-ST-32-02_0260342",1,"Created","The structural design of pressurized hardware shall be in conformance with ECSS-E-ST-32."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.2b","Requirement","ECSS-E-ST-32-02_0260343",1,"Created","The effect of each operating parameter of the system (e.g. pressure regulator lock-up characteristics, valve actuation and water hammer) and any external loads and environments shall be considered for MDP determination."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.2c","Requirement","ECSS-E-ST-32-02_0260344",1,"Created","Proof pressure and design burst pressure shall be derived from the MDP using the factor of safety given in clause 4."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.2d","Requirement","ECSS-E-ST-32-02_0260345",1,"Created","The range of internal pressure shall be taken into account in the stiffness analysis (e.g. foreign frequency analysis)."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.2e","Requirement","ECSS-E-ST-32-02_0260346",1,"Created","As a minimum, any item of pressurized hardware shall possess, throughout the respective service life of the hardware in the expected operating environments, a strength such to withstand:\n    1. proof pressure without detrimental deformation;\n    2. design burst pressure without experiencing rupture or fibre failure;\n    3. DYL and simultaneous internal pressure multiplied by FOSY for internal pressure without detrimental deformation;\n    4. MDP multiplied by FOSY for internal pressure and simultaneous loads multiplied by FOSY for mechanical and thermal loads, without detrimental deformation;\n    5. DUL and simultaneous internal pressure multiplied by FOSU for internal pressure without experiencing rupture or fibre failure;\n    6. MDP multiplied by FOSU for internal pressure and simultaneous loads multiplied by FOSU for mechanical and thermal loads, without experiencing rupture or fibre failure;\n    7. DUL and simultaneous external pressure multiplied by FOSU for mechanical and thermal loads, without experiencing rupture or fibre failure when pressurized to the minimum anticipated operating pressure."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.2f","Requirement","ECSS-E-ST-32-02_0260347",1,"Created","The minimum internal pressure to guaranty structural stabilization shall be identified and included in the acceptance data package."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.2g","Requirement","ECSS-E-ST-32-02_0260348",1,"Created","The pressurized hardware shall possess, throughout its service life in the expected operating environments, a stability such to withstand:\n    1. DUL and simultaneous external pressure multiplied by FOSU for pressure loads, without experiencing collapse when pressurized to the minimum anticipated operating pressure;\n    2. DUL and simultaneous internal pressure without experiencing collapse."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.2h","Requirement","ECSS-E-ST-32-02_0260349",1,"Created","A scatter factor of five (5) shall be used in fatigue analysis."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.1a","Requirement","ECSS-E-ST-32-02_0260350",1,"Created","The failure mode demonstration (i.e. demonstration of LBB or no LBB) can be ensured by analysis or test or both."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.1b","Requirement","ECSS-E-ST-32-02_0260351",1,"Created","The choice of the demonstration methodology (i.e. analysis or test or both) shall conform to the requirements on failure mode demonstration specified in clauses 4.2 to 4.5 according to the type of pressurized hardware.\n    ","NOTE For example:\n        · Failure mode may be demonstrated by similarity with an existing analysis or test with customer approval.\n        · For new designs, without heritage, the demonstration by test is sometimes specified by the customer."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.1c","Requirement","ECSS-E-ST-32-02_0260352",1,"Created","When failure mode is demonstrated by test, coupons or full-scale articles with prefabricated flaws shall be used as test specimens."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.1d","Requirement","ECSS-E-ST-32-02_0260353",1,"Created","The failure mode shall be demonstrated for the structural items of the pressurized hardware, which serve as a fluid permeation barrier and which are primarily designed by pressure loads.\n    ","NOTE For example:\n        · For composite over-wrapped pressurized hardware, the liner is the fluid permeation barrier.\n        · For composite over-wrapped pressurized hardware, the boss area can be primarily designed by shear and not by pressure loads.\n        · For CPV and CPS, the composite wall itself is considered as the fluid permeation barrier."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.1e","Requirement","ECSS-E-ST-32-02_0260354",1,"Created","When the failure mode demonstration is performed for metallic items, fracture mechanics principles shall be employed."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.1f","Requirement","ECSS-E-ST-32-02_0260355",1,"Created","Areas where the LBB failure mode is not demonstrated shall be designed according to safe-life requirements as per clause 5.3."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.1g","Requirement","ECSS-E-ST-32-02_0260356",1,"Created","For composite and composite over-wrapped pressurized hardware, potential degradation of the composite strength by the leaking fluid shall be accounted for in the failure mode demonstration."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.2a","Requirement","ECSS-E-ST-32-02_0260357",1,"Created","It shall be shown that, at MDP, an initial surface crack with a flaw shape (a/c), ranging from 0,2 to 1,0, meets the following conditions:\n    1. it does not fail as a surface crack; and\n    2. it grows through the wall of the hardware to become a through crack with a length greater than or equal to 10 times the wall thickness of the metallic hardware item and remains stable.\n        ","NOTE For example:\n            · For a part-through surface crack, the crack aspect ratio is the ratio (a/c) of crack depth (a) to half crack length (c). For a part-through corner crack, the crack aspect ratio is the ratio (a/c) of crack depth (a) to crack length (c)/\n            · If no assumption is made about the initial surface crack size, the specified range a/c between 0,2 and 1,0 leads to a maximum through crack length of 2 c = 10 t (for a = t, where t is the wall thickness)."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.2b","Requirement","ECSS-E-ST-32-02_0260358",1,"Created","When LBB demonstration is based on a through crack with a length less than 10 times the wall thickness in accordance with 5.3.2a.2, the considered initial crack size shall be justified.\n    ","NOTE Justification of initial surface crack size can be based on NDI capability or on a crack whose depth is as close as possible to the wall thickness, within the range of a/c specified in clause 5.3.2a."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.3a","Requirement","ECSS-E-ST-32-02_0260359",1,"Created","Coupons shall duplicate the materials (parent metals, weld joints, and heat affected zones) and the thickness of the metallic hardware items."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.3b","Requirement","ECSS-E-ST-32-02_0260360",1,"Created","The coupon tests shall duplicate the loading conditions of the metallic hardware items.\n    ","NOTE Loading conditions include stress state aspects of bi-axial, compressive stresses parallel to crack plane."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.3c","Requirement","ECSS-E-ST-32-02_0260361",1,"Created","The flaws shall be surface cracks and the flaw shape of the pre-fabricated surface cracks shall range from a/c = 0,2 to 1,0.\n    ","NOTE For the definition of a part-through surface crack, and a part-through corner crack see NOTE 1 in 5.3.2a."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.3d","Requirement","ECSS-E-ST-32-02_0260362",1,"Created","The initial surface crack size shall be justified.\n    ","NOTE Justification of initial surface crack size can be based on NDI capability or on a crack whose depth is as close as possible to the wall thickness, within the range of a/c specified in 5.3.3c."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.3e","Requirement","ECSS-E-ST-32-02_0260363",1,"Created","Stress (or strain) cycles shall be applied to the specimens with the maximum stress (or strain) corresponding to the MDP level and minimum stress (or strain) kept to zero, or actual minimum stress (or strain), until the surface crack grows through the specimen's thickness to become a through crack."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.3f","Requirement","ECSS-E-ST-32-02_0260364",1,"Created","It shall be shown that the length of the through crack becomes equal to or greater than 10 times the specimen's thickness and remains stable at MDP."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.4a","Requirement","ECSS-E-ST-32-02_0260365",1,"Created","The full-scale article shall be representative of the flight hardware."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.4b","Requirement","ECSS-E-ST-32-02_0260366",1,"Created","The type and initial size of pre-fabricated flaws shall be justified.\n    ","NOTE Justification of initial flaw size can be based on NDI capability or on a crack whose depth is as close as possible to the wall thickness, within the range of a/c specified in sub clause 5.3.4c."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.4c","Requirement","ECSS-E-ST-32-02_0260367",1,"Created","For pre-flawed metallic items, the flaws shall be surface cracks and the aspect ratio of the pre-fabricated surface cracks shall range from a/c = 0,2 to 1,0.\n    ","NOTE For the definition of a part-through surface crack, and a part-through corner crack see NOTE 1 in 5.3.2a."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.4d","Permission","ECSS-E-ST-32-02_0260468",1,"Created","For pre-flawed composite items (liner or walls), the flaws may be through cracks with a length greater than or equal to 10 times the wall thickness of the item."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.4e","Requirement","ECSS-E-ST-32-02_0260369",1,"Created","Location and orientation of pre-fabricated flaws shall be the most critical with regard to LBB response."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.4f","Requirement","ECSS-E-ST-32-02_0260370",1,"Created","Pressure cycles shall be applied to the pressurized hardware, with the upper pressure equal to MDP and the lower pressure greater than or equal to zero."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.4g","Requirement","ECSS-E-ST-32-02_0260371",1,"Created","After a flaw has grown through the thickness to become a through flaw and leakage has been detected, internal pressure shall be increased up to MDP."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.4h","Requirement","ECSS-E-ST-32-02_0260372",1,"Created","At least one of the following conditions shall be satisfied after 5.3.4g has been met:\n    - no burst occurs at MDP and leak rate is equal to or greater than a value defined with customer approval. This criteria is applicable to composite over-wrapped pressurized hardware, or\n    - the length of the through crack in the metallic item becomes equal to or greater than 10 times the wall thickness of the item and remains stable at MDP. This criteria is only applicable to metallic and fully composite pressurized hardware."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.4i","Requirement","ECSS-E-ST-32-02_0260373",1,"Created","Test fluid shall be compatible with the materials used in the hardware and not pose a hazard to test personnel."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.4j","Requirement","ECSS-E-ST-32-02_0260374",1,"Created","The full-scale test shall duplicate the loading conditions and pressurization medium (gas or liquid) of the flight hardware.\n    ","NOTE E.g. loading conditions include stress state aspects of bi-axial, compressive stresses parallel to crack plane."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.5a","Requirement","ECSS-E-ST-32-02_0260375",1,"Created","When LBB is demonstrated by analysis:\n    1. an analysis report in conformance with ECSS-E-ST-10-02 shall be prepared;\n    2. in the report specified in 5.3.5a.1, loading spectra, assumed initial flaw sizes, crack growth models, and fatigue crack growth rates shall be delineated."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.3.5b","Requirement","ECSS-E-ST-32-02_0260376",1,"Created","When LBB is demonstrated by test, a test report shall be prepared in conformance with ECSS-E-ST-10-02."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.4.1a","Requirement","ECSS-E-ST-32-02_0260377",1,"Created","‘General requirements’ and ‘Qualification testing’ requirements shall apply in conformance with ECSS-E-ST-10-03."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.4.1b","Requirement","ECSS-E-ST-32-02_0260378",1,"Created","When the hardware mounting induces axial or radial restrictions on the pressure driven expansion of the hardware, the burst test fixture shall simulate the structural response or reaction loads of the flight mounting."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.4.1c","Requirement","ECSS-E-ST-32-02_0260379",1,"Created","When a qualification test is conducted at temperature other than temperature expected for the design loads, the change of material properties at this temperature shall be verified:\n    - by adjustment of the pressure and load level, or\n    - by analysis, supported by tests on samples or sub-scale articles and providing material strength design allowable versus temperature."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.4.1d","Requirement","ECSS-E-ST-32-02_0260380",1,"Created","When NDI is performed in the qualification tests, it shall meet clause 5.7."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.4.1e","Requirement","ECSS-E-ST-32-02_0260381",1,"Created","The test fluids shall not deteriorate the test article."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.4.1f","Requirement","ECSS-E-ST-32-02_0260382",1,"Created","The test fluids shall not pose a hazard to the test personnel."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.4.1g","Requirement","ECSS-E-ST-32-02_0260383",1,"Created","When the strength design allowable of the materials depends on the fluid to be stored in the flight hardware (e.g. when the stored fluid is liquid hydrogen), the change of material properties shall be verified:\n    - by using this specific fluid to pressurize the test specimens, or\n    - by analysis, supported by tests on samples or sub-scale articles and providing material strength design allowable versus fluid characteristics."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.4.1h","Requirement","ECSS-E-ST-32-02_0260384",1,"Created","In case of changing the manufacturing process, the qualification tests shall be repeated unless it is demonstrated that the new manufacturing process maintains or improves material and geometrical characteristics."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.4.2a","Requirement","ECSS-E-ST-32-02_0260385",1,"Created","During the proof pressure test, the load level (i.e. pressure level, external load level) shall be maintained for 5 minutes as a minimum."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.4.2b","Requirement","ECSS-E-ST-32-02_0260386",1,"Created","The interest for application of external loads in combination with internal pressures during testing shall be evaluated based on the relative magnitude, the destabilizing effect, or both, of stresses due to the external load."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.4.3a","Requirement","ECSS-E-ST-32-02_0260387",1,"Created","During the leak test, the pressure level shall be maintained at MDP or greater for 30 minutes as a minimum."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.4.3b","Requirement","ECSS-E-ST-32-02_0260388",1,"Created","For qualification ‘leakage test’, requirements shall be in conformance with ECSS-E-ST-10-03.\n    ","NOTE Exceptions to the values provided in 5.4.3a and 5.4.3b are sometimes specified by the customer or granted with customer approval."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.4.4a","Requirement","ECSS-E-ST-32-02_0260389",1,"Created","Vibration testing shall be conducted at the pressure condition corresponding to the maximum predicted vibration environment."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.4.4b","Requirement","ECSS-E-ST-32-02_0260390",1,"Created","Operational conditions (e.g. fluid density, and filling ratio) shall be taken into account in the test configuration."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.4.5a","Requirement","ECSS-E-ST-32-02_0260426",1,"Created","Pressure cycles shall range from zero differential pressure to MDP and back to zero differential pressure for at least 50 cycles or four times the number of planned pressure cycles expected in one service life, whichever is greater."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.4.5b","Requirement","ECSS-E-ST-32-02_0260427",1,"Created","Only cycles having a peak operating pressure that creates a liner tensile stress (exceeds the compressive metal liner pre-stress as imposed by the over-wrap, as a result of vessel autofrettage) shall be considered in the life cycle test of composite over-wrapped pressurized hardware."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.4.6a","Requirement","ECSS-E-ST-32-02_0260391",1,"Created","During the design burst pressure test, the design burst pressure level shall be maintained for 30 seconds as a minimum."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.4.6b","Requirement","ECSS-E-ST-32-02_0260392",1,"Created","No burst or collapse shall occur prior to the end of the design burst pressure application."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.4.7a","Requirement","ECSS-E-ST-32-02_0260393",1,"Created","The pressure shall be increased until burst occurs."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.4.7b","Requirement","ECSS-E-ST-32-02_0260394",1,"Created","The burst pressure shall be recorded."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.5.1a","Requirement","ECSS-E-ST-32-02_0260395",1,"Created","‘General requirements’ and ‘Accepting testing’ requirements shall apply in conformance with ECSS-E-ST-10-03."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.5.1b","Requirement","ECSS-E-ST-32-02_0260396",1,"Created","When an acceptance test is conducted at temperature other than temperature expected for the design loads, the change of material properties at this temperature shall be verified:\n    - by adjustment of the pressure and load level, or\n    - by analysis, supported by tests on samples or sub-scale articles and providing material strength design allowable versus temperature."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.5.1c","Requirement","ECSS-E-ST-32-02_0260397",1,"Created","When NDI is performed in the acceptance tests, it shall meet clause 5.7."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.5.1d","Requirement","ECSS-E-ST-32-02_0260398",1,"Created","When the strength design allowable of the materials depends on the fluid to be stored in the flight hardware (e.g. when the stored fluid is liquid hydrogen), the change of material properties shall be verified:\n    - by using this fluid to pressurize the test specimens, or\n    - by analysis, supported by tests on samples or sub-scale articles and providing material strength design allowable versus fluid characteristics."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.5.2a","Requirement","ECSS-E-ST-32-02_0260399",1,"Created","During the proof pressure test, the load level (i.e. pressure level, external load level) shall be maintained for 5 minutes as minimum."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.5.2b","Requirement","ECSS-E-ST-32-02_0260400",1,"Created","The interest for application of external loads in combination with internal pressures during testing shall be evaluated based on the relative magnitude, the destabilizing effect, or both, of stresses due to the external load."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.5.3a","Requirement","ECSS-E-ST-32-02_0260401",1,"Created","During the leak test, the pressure level shall be maintained at MDP or greater for 30 minutes as minimum."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.5.3b","Requirement","ECSS-E-ST-32-02_0260402",1,"Created","For acceptance ‘leakage test’, requirements shall be in conformance with ECSS-E-ST-10-03.\n    ","NOTE Exceptions to the values provided in 5.5.3a and 5.5.3b are sometimes specified by the customer or granted with customer approval."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.6a","Requirement","ECSS-E-ST-32-02_0260403",1,"Created","Strength design allowable shall be generated from at least one of the following tests:\n    1. elementary testing on samples or coupons, which are representative of the characteristics of the hardware;\n    2. bursting of full or sub-scale specimens of different configurations, provided that applicability to the full scale article is demonstrated by analysis;\n    3. bursting of sub-scale specimens, provided that scaling factor is accounted for;\n    4. bursting of full-scale specimens. "]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.6b","Requirement","ECSS-E-ST-32-02_0260404",1,"Created","Test results from at least two lots of yarns shall be used in the design allowable calculations unless all of the items are fabricated from the same lot of material."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.6c","Requirement","ECSS-E-ST-32-02_0260405",1,"Created","When the composite wall of the pressurized hardware serves partially or totally as a permeation barrier (e.g. for CPV or CPS), any degradation of the wall due to the contact with the stored fluid shall be accounted for in the design allowable of material strength.\n    ","NOTE When in contact with liquid hydrogen, the composite wall can experience superficial micro-cracking and degradation of its transverse shear and tensile strength."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.7.1a","Requirement","ECSS-E-ST-32-02_0260406",1,"Created","An inspection plan shall be established prior to the start of fabrication."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.7.1b","Requirement","ECSS-E-ST-32-02_0260407",1,"Created","For ‘Inspection’ plan, requirements shall be in conformance with ECSS-Q-ST-20."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.7.1c","Requirement","ECSS-E-ST-32-02_0260408",1,"Created","For ‘Inspection of PFCI’, requirements shall be in conformance with ECSS-E-ST-32-01. "]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.7.1d","Requirement","ECSS-E-ST-32-02_0260409",1,"Created","The inspection plan shall specify inspection points throughout the program, beginning with material procurement, continuing through fabrication, assembly, acceptance proof test and operation, and using the following techniques:\n    1. procurement of raw materials, in conformance with ECSS-Q-ST-70;\n    2. procurement of mechanical parts in conformance with ECSS-Q-ST-70;\n    3. NDI for detecting mechanical damage or flaw, in conformance with clauses 5.7.2 and ECSS-E-ST-32-08."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.7.1e","Requirement","ECSS-E-ST-32-02_0260410",1,"Created","Acceptance and rejection criteria shall be established within the inspection plan for each phase of inspection and for each type of inspection."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.7.1f","Requirement","ECSS-E-ST-32-02_0260411",1,"Created","For ‘Detected defects’ outside of the acceptance criteria defined in 5.7.1e, requirements shall be in conformance ECSS-E-ST-32-01."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.7.2a","Requirement","ECSS-E-ST-32-02_0260412",1,"Created","After application of composite manufacturing process, any composite over-wrapped or composite item of pressurized hardware shall be subjected to the following inspections:\n    1. visual inspection for detecting impact damage,\n    2. state-of-the-art NDI techniques for inspecting mechanical damage or flaw induced on the composite."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.7.2b","Requirement","ECSS-E-ST-32-02_0260413",1,"Created","Visual inspection shall be performed by inspectors, who have been trained to detect visible damage on composite or composite over-wrapped pressurized hardware involving the use of actual damaged hardware."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.7.2c","Requirement","ECSS-E-ST-32-02_0260414",1,"Created","The NDI procedures are based on using multiple NDI methods to perform survey inspections or diagnostic inspections as follows: \n    1. survey NDI inspections shall be conducted when the location of the potential damage or flaw zone is unknown;\n    2. diagnostic NDI inspections shall be performed within a localized suspect zone to characterize the type and extent of the damage or flaw."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.7.2d","Requirement","ECSS-E-ST-32-02_0260415",1,"Created","All NDI techniques, whether used as a single inspection technique or as a combination of methods, shall have the capability to detect impact or flaw that can cause the composite over-wrapped or composite pressurized hardware to fail."]
["ECSS-E-ST-32-02C Rev. 1","ECSS - Superseded v1.0","5.7.2e","Requirement","ECSS-E-ST-32-02_0260416",1,"Created","For ‘NDI for composite and bonded parts’, requirements shall be in conformance with ECSS-E-ST-32-01."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.2a","Requirement","ECSS-E-ST-70-11_0290001",1,"Created","The space segment shall provide visibility of its internal status, configuration and performance to the ground segment in conformance with the level of detail and the time delays specified for all routine and specified contingency operations, including subsequent diagnostic activities.\n    ","NOTE 1 For detailed operability requirements reflecting these objectives, refer to clause 5.2                                         \nNOTE 2 Specified contingency operations are derived during the failure analysis performed in the mission development process (e.g. the failure modes, effects and criticality analysis (FMECA)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.3a","Requirement","ECSS-E-ST-70-11_0290002",1,"Created","The control functions (telecommands) provided at each level of the system hierarchy shall be capable of achieving the mission objectives under all specified circumstances.\n    ","NOTE 1 This can include the use of redundant equipment to meet the overall system reliability requirements.\nNOTE 2 Detailed operability requirements reflecting these objectives appear in clause 5.5                                         "]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.4a","Requirement","ECSS-E-ST-70-11_0290003",1,"Created","The space segment shall conform to all on-board design standards specified for the mission in order to ensure compatibility with the specified ground systems."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.4b","Requirement","ECSS-E-ST-70-11_0290004",1,"Created","The space segment design shall be such that its operation is not constrained by, nor adversely constrains, the availability or capacity of the space-Earth communications links."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.5a","Requirement","ECSS-E-ST-70-11_0290005",1,"Created","No single command function executed at the wrong time or in the wrong configuration shall lead to the loss of the mission.\n    ","NOTE For a mission-critical command function, this can be ensured by the provision of two independent commands, both to be executed (e.g. ARM and FIRE)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.5b","Requirement","ECSS-E-ST-70-11_0290006",1,"Created","Except for explicitly agreed single point failures, the capability shall be provided to recover all on-board functions after a single failure within a specific function.\n    ","NOTE The impact of several non-correlated failures occurring at the same time has to be assessed at mission-level."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.5c","Requirement","ECSS-E-ST-70-11_0290007",1,"Created","No single unintentional ground command or failure in one space segment element shall cause a failure in another space segment element."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.5d","Requirement","ECSS-E-ST-70-11_0290008",1,"Created","The design of the space segment failure detection, isolation and recovery (FDIR) function shall be such that all anticipated on-board failures can be overcome either by autonomous on-board action or by clear, unambiguous and timely notification of the problem to the ground segment."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.5e","Requirement","ECSS-E-ST-70-11_0290009",1,"Created","The FDIR design shall ensure that the space segment is safe without ground segment intervention for the specified duration in the presence of a single failure."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.5f","Requirement","ECSS-E-ST-70-11_0290010",1,"Created","No reconfiguration of the spacecraft shall lead to a configuration where new single point failures are introduced.\n    ","NOTE With the exception of reconfigurations that are triggered on-board as the result of genuine failures."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.6a","Requirement","ECSS-E-ST-70-11_0290011",1,"Created","All authorized combinations of prime and redundant equipment shall exhibit the same operational characteristics.\n    ","NOTE 1 This requirement does not prevent a change of calibration data, but it precludes different operational procedures.\nNOTE 2 This does not include any reduced redundancy that exists following a failure."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.6b","Requirement","ECSS-E-ST-70-11_0290012",1,"Created","The capability shall be provided for the ground segment to allocate which of the redundant units are included in the nominal chain and which in the redundant chain.\n    ","NOTE 1 This enables redundancy to be restored without reconfiguring the on-board hardware and also enables a failed unit to be removed from both the nominal and redundant chains while maintaining the rest of the redundancy of the chain.\nNOTE 2 Software-selectable units, rather than hardware, are more suitable for use where the extent of cross-strapping provided is determined from the reliability analysis."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.6c","Requirement","ECSS-E-ST-70-11_0290013",1,"Created","Any selection of prime or redundant equipment shall be reversible.\n    ","NOTE This implies that the space segment design supports switching between prime and redundant equipment in both directions."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.6d","Requirement","ECSS-E-ST-70-11_0290014",1,"Created","For each on-board function, there shall be at least one alternative configuration that can achieve the same function using different on-board units."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.6e","Requirement","ECSS-E-ST-70-11_0290015",1,"Created","On-board functions shall have well-defined inputs and outputs that are accessible from the ground for workaround solutions in case of contingency operations.\n    ","NOTE Whilst inputs to on-board functions can be modified from the ground (e.g. threshold settings), this does not include the manipulation of on-board measurements."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.6f","Recommendation","ECSS-E-ST-70-11_0290348",1,"Created","On-board storage and buffer areas should be resizable to cater for non-nominal mission events.\n    ","NOTE There can be operational restrictions on how this is achieved."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.6g","Requirement","ECSS-E-ST-70-11_0290017",1,"Created","The allocation of budgets for on-board resources shall provide the specified spare capacity for each subsystem and each payload.\n    ","NOTE 1 For example, mass memory, power, fuel.\nNOTE 2 This spare capacity is provided in order to ensure flexibility during the mission."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.6h","Requirement","ECSS-E-ST-70-11_0290018",1,"Created","The capability shall be provided to determine, at any point in the mission and with the specified accuracy, the remaining on-board resources that impact on mission lifetime.\n    ","NOTE 1 For example, power, cooling fluid, fuel.\nNOTE 2 The accuracy is specified to be compatible with the mission requirements."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.7a","Requirement","ECSS-E-ST-70-11_0290019",1,"Created","Each application process shall provide the capability to perform a set of end-to-end test functions which can be exercised under ground control.\n    ","NOTE For example, an “are you alive” function which generates a response for testing the end-to-end connection between the ground and an application process."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.7b","Recommendation","ECSS-E-ST-70-11_0290349",1,"Created","For test purposes, the capability should be provided to operate redundant on-board equipment in an “off-line” manner (i.e. in parallel with, but without any disturbance to, the prime equipment).\n    ","NOTE This capability can be unfeasible if the redundant unit has an unacceptable disturbing influence such as in the case of a momentum wheel."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.7c","Recommendation","ECSS-E-ST-70-11_0290350",1,"Created","The capability should be provided to confirm the health of a currently unused unit prior to operational utilization.\n    ","NOTE This applies in particular to units that are vital for the health and control of the space segment. The selection of units is to be made on a case-by-case basis, taking into account the impact on the space segment design (e.g. the telemetry definition)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.7d","Requirement","ECSS-E-ST-70-11_0290022",1,"Created","The capability shall be provided to load and check redundant memory prior to operational utilization."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.8a","Requirement","ECSS-E-ST-70-11_0290023",1,"Created","On-board resources shall be provided for configuring the spacecraft into a safe state at the end of its life.\n    ","NOTE 1 This can include de-orbiting (essential for LEO spacecraft) or bringing the spacecraft to a graveyard orbit (GEO spacecraft).\nNOTE 2 Safe state means safe for the space environment."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","4.8b","Requirement","ECSS-E-ST-70-11_0290024",1,"Created","The capability shall be provided to completely deactivate the spacecraft at the end of its life.\n    ","NOTE This can include the removal of all internal energy sources, e.g. power and fuel."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.2.1a","Requirement","ECSS-E-ST-70-11_0290025",1,"Created","The space segment shall be designed such that the following can be ensured:\n    1. the integrity of each data stream produced;\n    2. the confidentiality of each data stream produced;\n    3. the authentication of each telecommand received;\n    4. the authorization of each telecommand received."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.2.1b","Requirement","ECSS-E-ST-70-11_0290026",1,"Created","The space segment shall be designed such that continued access to both the telemetry and telecommand transmission functions in the presence of specified external influences outside the control of the mission control team can be ensured.\n    ","NOTE The external influences to be accommodated are identified during the spacecraft design phase, i.e. at mission analysis level. They generally include RFI and adverse weather conditions. However, other influences, such as meteorite impacts or malicious dazzling of the uplink, clearly cannot be accommodated."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.2.1c","Requirement","ECSS-E-ST-70-11_0290027",1,"Created","The space segment shall be designed such that the recovery of access to both the telemetry and telecommand transmission functions can be ensured after all specified space and ground segment configuration changes."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.2.2a","Requirement","ECSS-E-ST-70-11_0290028",1,"Created","The design of the overall mission operations system (i.e. constituting both the ground and space segments) shall ensure that control functions that have response times shorter than <GRND_RESP_TIME> are implemented on-board."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.2.2b","Requirement","ECSS-E-ST-70-11_0290029",1,"Created","Under all circumstances, the elapsed time for an application process to build and release telemetry source packets shall be such that the overall delay between the generation of a packet and its reception at the mission control centre is consistent with the response times <GRND_RESP_TIME> (there can be several such parameters for a given mission) that have been identified for ground control functions."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.2.2c","Requirement","ECSS-E-ST-70-11_0290030",1,"Created","The frequency of generation of telemetry source packets shall be consistent with <GRND_RESP_TIME>."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.2.2d","Requirement","ECSS-E-ST-70-11_0290031",1,"Created","The time differences between the release of packets containing data and packets containing ancillary information used for its ground processing shall be such that the effective operational information (i.e. after ground processing) is available within delays consistent with <GRND_RESP_TIME>."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.2.3a","Requirement","ECSS-E-ST-70-11_0290032",1,"Created","Different downlink bandwidths shall be allocated to different classes of data using physical channels and virtual channels."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.2.3b","Requirement","ECSS-E-ST-70-11_0290033",1,"Created","The assignment of virtual channels to different data classes shall not be changed during the mission.\n    ","NOTE Data classes means distinct data streams, such as real-time housekeeping telemetry, science data or playback data rather than different packet types within the same stream."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.2.3c","Requirement","ECSS-E-ST-70-11_0290034",1,"Created","The allocation of bandwidth to different virtual channels shall be modifiable during the mission."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.2.3d","Requirement","ECSS-E-ST-70-11_0290035",1,"Created","The capability shall be provided to transmit real-time telemetry data and deferred telemetry data simultaneously."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.2.3e","Requirement","ECSS-E-ST-70-11_0290036",1,"Created","Request-driven telemetry source packets (e.g. telecommand verification packets) shall be routed to the originating source of the telecommand.\n    ","NOTE 1 The source can be either the ground or an on-board application process. In the case of telecommands released from an on-board schedule, the source is the ground.\nNOTE 2 On-board autonomous activities are reported to the ground segment using event report packets."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1a","Requirement","ECSS-E-ST-70-11_0290037",1,"Created","Telemetry data shall be provided, as defined for all mission phases, for the ground segment to determine the status of the spacecraft subsystems and payloads and to monitor the execution of nominal and anticipated contingency operations."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1b","Requirement","ECSS-E-ST-70-11_0290038",1,"Created","The data specified in requirement 5.3.1a shall include sensor readings, register readouts, equipment status (including power status), function status, reports of on-board events and actions taken by autonomous functions, and processor and memory auto-test results."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1c","Requirement","ECSS-E-ST-70-11_0290039",1,"Created","The data specified in requirement 5.3.1a shall be telemetred to the ground segment in a complete, unambiguous, and timely manner."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1d","Requirement","ECSS-E-ST-70-11_0290040",1,"Created","Event-based reporting shall be achieved by means of dedicated event report packets (progress or anomaly reports) which are generated on-board, e.g. by a failure detection and recovery function."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1e","Requirement","ECSS-E-ST-70-11_0290041",1,"Created","The design of event reporting mechanisms and of the event report packets themselves shall be such that the utilization of the downlink bandwidth does not adversely affect the availability of other operational information to the ground segment."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1f","Requirement","ECSS-E-ST-70-11_0290042",1,"Created","Essential space segment status data shall be derived from direct measurements. \n    ","NOTE This means that the essential status of the space segment is observable directly from the telemetry without the need for ground processing."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1g","Requirement","ECSS-E-ST-70-11_0290043",1,"Created","The design of telemetry shall be such that preconditions for the switching of on-board equipment and units are acquired independently, i.e. they are not dependent on the status of the equipment or unit to be switched.\n    ","NOTE 1 To comply with this requirement, power status and thermal data used prior to unit switch-on are managed at a higher level.\nNOTE 2 This provides the capability of monitoring and assessing the status of a unit even when it is switched off."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1h","Requirement","ECSS-E-ST-70-11_0290044",1,"Created","The values of telemetred parameters shall be self-contained.\n    ","NOTE This precludes, for instance, the telemetring of delta-changes or status changes."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1i","Requirement","ECSS-E-ST-70-11_0290045",1,"Created","If operationally-significant parameters monitored on-board (e.g. pyro currents) can change value at a frequency in excess of the telemetry sampling frequency, the event shall be memorized and the memorized value telemetred."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1j","Requirement","ECSS-E-ST-70-11_0290046",1,"Created","The resolution and range of analogue telemetry parameters shall be such that monitoring can be performed in all nominal and anticipated contingency situations."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1k","Requirement","ECSS-E-ST-70-11_0290047",1,"Created","Vital space segment health functions shall be monitored with redundant telemetry parameters (e.g. primary bus current and voltage, and propellant tank pressure)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1l","Requirement","ECSS-E-ST-70-11_0290048",1,"Created","Telemetry shall be provided to enable detection and diagnosis of any failure identified during the failure analysis phase (e.g. as defined in the FMECA) at least down to function or equipment level."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1m","Requirement","ECSS-E-ST-70-11_0290049",1,"Created","Where telemetry measurements are processed on-board, the capability shall be provided to downlink the raw data to the ground segment, on request.\n    ","NOTE For example, AOCS sensor data."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1n","Requirement","ECSS-E-ST-70-11_0290050",1,"Created","For elements in hot redundancy, telemetry shall be provided to enable an independent and unambiguous evaluation of the status of each chain."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1o","Requirement","ECSS-E-ST-70-11_0290051",1,"Created","For elements in redundancy, the loss or failure of one chain shall not prevent access to the telemetry of the other chain."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1p","Requirement","ECSS-E-ST-70-11_0290052",1,"Created","Where parameters are conditionally valid, the parameters determining their validity shall be telemetred with a frequency that is the same as, or higher than, the conditionally-valid parameter."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1q","Requirement","ECSS-E-ST-70-11_0290053",1,"Created","Sampling sequences and frequencies shall be specified for all related parameters that are correlated or combined for the purposes of space segment monitoring or performance evaluation to ensure that no information of operational significance is lost."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1r","Requirement","ECSS-E-ST-70-11_0290054",1,"Created","Where the interpretation of a parameter in a variable packet depends on the values of other on-board parameters, these parameters shall all be telemetred in the same packet.\n    ","NOTE When the interpretation of a parameter in a variable packet depends on the values of other onboard parameters, the first parameter is a deduced parameter, as defined in ECSS-E-ST-70-41."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1s","Requirement","ECSS-E-ST-70-11_0290055",1,"Created","A telemetry parameter shall always have the same structure and interpretation, even if it appears in different telemetry source packets."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1t","Requirement","ECSS-E-ST-70-11_0290056",1,"Created","The location of a parameter within a non-variable telemetry source packet shall be fixed and derivable from an implicit knowledge of the packet structure."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1u","Requirement","ECSS-E-ST-70-11_0290057",1,"Created","The telemetry data at a given position in a telemetry packet shall either correspond to a given physical address on-board or to a given logical address, i.e. a mixture shall not be used.\n    ","NOTE Physical means that it corresponds to a physical unit on-board, whether or not that unit is being used as prime. Logical means that the telemetry corresponds to the prime unit, which can be either one of two different physical units."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1v","Requirement","ECSS-E-ST-70-11_0290058",1,"Created","If the same telemetry parameter appears more than once in the same housekeeping telemetry source packet, then the parameter shall be sampled regularly in time."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1w","Requirement","ECSS-E-ST-70-11_0290059",1,"Created","The design of housekeeping telemetry source packets shall not use sub-commutation.\n    ","NOTE A sub-commutated parameter is one that does not appear (at a given location) in each a packet, but only in every n-th packet."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1x","Requirement","ECSS-E-ST-70-11_0290060",1,"Created","The capability shall be provided for the ground segment to define (and re-define) the packet contents for housekeeping telemetry source packets."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1y","Requirement","ECSS-E-ST-70-11_0290061",1,"Created","The capability shall be provided to request that housekeeping telemetry source packets are only sent to ground segment if there has been a change in value of specified contained parameters by more than a specified threshold."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1z","Requirement","ECSS-E-ST-70-11_0290062",1,"Created","Within a given virtual channel, telemetry packets originating from the same APID shall always be delivered to the ground segment in the same sequence as they are generated on-board.\n    ","NOTE This does not apply across separate retrievals from on-board storage, where the original chronological order is not always retained."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.1aa","Requirement","ECSS-E-ST-70-11_0290063",1,"Created","Within a given virtual channel, consecutive samples of the same telemetry parameter shall be transmitted to ground segment in chronological order, even if they appear in separate packets.\n    ","NOTE This does not apply across separate retrievals from on-board storage, where the original chronological order may not be retained."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.2a","Requirement","ECSS-E-ST-70-11_0290064",1,"Created","For anomaly investigation purposes, the capability shall be provided for the ground segment to select a set of telemetry parameters to be sampled at a high rate."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.2b","Requirement","ECSS-E-ST-70-11_0290065",1,"Created","All telemetry parameters shall be accessible in diagnostic mode."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.2c","Requirement","ECSS-E-ST-70-11_0290066",1,"Created","The capability shall be provided to sample a given telemetry parameter at a configurable sampling rate down to a minimum sampling interval of <DIAG_MIN_INTERV>."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.3.2d","Requirement","ECSS-E-ST-70-11_0290067",1,"Created","The capability shall be provided to record diagnostic mode data on-board for later retrieval by the ground segment. \n    ","NOTE For example, by using the ECSS-E-ST-70-41 on-board storage and retrieval service (see clause 5.8.9 for additional information)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.4a","Requirement","ECSS-E-ST-70-11_0290068",1,"Created","Timing information shall be provided in the telemetry such that on-board time and ground time can be correlated with an accuracy of <TIME_CORREL_ACCUR>.\n    ","NOTE For some missions, OBT/UTC time correlation is performed autonomously on-board (e.g. using GPS). Nevertheless, this requirement specifies the provision of means to check this correlation function on the ground."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.4b","Requirement","ECSS-E-ST-70-11_0290069",1,"Created","On-board time shall be common to all spacecraft modes, including standby and survival modes.\n    ","NOTE For space segment modes see clause 5.6.1."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.4c","Requirement","ECSS-E-ST-70-11_0290070",1,"Created","All timing information in the telemetry shall be synchronized with a single on-board reference clock."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.4d","Requirement","ECSS-E-ST-70-11_0290071",1,"Created","When an application process using time synchronization has just been initialized, telemetry shall be provided to notify the ground segment that time synchronization has not yet occurred."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.4e","Requirement","ECSS-E-ST-70-11_0290072",1,"Created","After initialization of an application process using time synchronization, telemetry shall be provided to notify the ground segment when time synchronization has been achieved."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.4f","Requirement","ECSS-E-ST-70-11_0290073",1,"Created","For application processes using time synchronization, telemetry information shall be provided to enable the ground segment to verify synchronization."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.4g","Requirement","ECSS-E-ST-70-11_0290074",1,"Created","No on-board clock shall wrap-around during the mission lifetime."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.4h","Recommendation","ECSS-E-ST-70-11_0290351",1,"Created","All telemetry source packets should have an on-board generation time in their packet header.\n    ","NOTE Generation time is the time when the packet is created."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.4i","Requirement","ECSS-E-ST-70-11_0290076",1,"Created","The on-board time, as telemetred to the ground segment, shall not wrap-around during the mission lifetime."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.4j","Requirement","ECSS-E-ST-70-11_0290077",1,"Created","No on-board counter telemetred to ground segment shall wrap around within the agreed ground segment non-availability period."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.4k","Requirement","ECSS-E-ST-70-11_0290078",1,"Created","The capability shall be provided to establish on the ground the time at which parameters of operational significance have actually been sampled on-board to an accuracy of <PARAM_ABS_SAMPL_TIME>."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.4l","Requirement","ECSS-E-ST-70-11_0290079",1,"Created","The capability shall be provided to determine the relative sampling time of any two parameters to an accuracy of <PARAM_REL_SAMPL_TIME>.\n    ","NOTE This also applies if the parameters appear in different packets, whether housekeeping or scientific in nature."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.4m","Requirement","ECSS-E-ST-70-11_0290080",1,"Created","The on-board sampling time of a telemetry parameter in a non-variable content telemetry packet shall be derivable from the packet generation time by adding or subtracting an implicitly known time offset."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.4n","Requirement","ECSS-E-ST-70-11_0290081",1,"Created","If the requirements for timing accuracy are expected to vary during the course of a mission, the capability shall be provided to change the rate of generation of the time packet."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.1a","Requirement","ECSS-E-ST-70-11_0290082",1,"Created","Telecommands shall be available to command all on-board equipment and functions under all nominal and envisaged contingency conditions.\n    ","NOTE This implies the provision of a high priority command to re-establish command processing in the event of processor failure."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.1b","Requirement","ECSS-E-ST-70-11_0290083",1,"Created","If a telecommand executes more than one control action, these actions shall be strictly operationally related, such that they constitute a single logical telecommand function.\n    ","NOTE To comply with this requirement, a device telecommand cannot put a battery in trickle charge and at the same time switch on a heater, unless these operations are always strictly related."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.1c","Requirement","ECSS-E-ST-70-11_0290084",1,"Created","A telecommand packet shall contain one, and only one, telecommand function.\n    ","NOTE A telecommand that loads or starts an on-board schedule only executes a single function (load or start) irrespective of the number of command functions contained in the load or schedule itself."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.1d","Requirement","ECSS-E-ST-70-11_0290085",1,"Created","Where a given function is invoked by a sequence of two or more telecommands, the capability shall be provided to “pack” such telecommands within a single telecommand packet."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.1e","Requirement","ECSS-E-ST-70-11_0290086",1,"Created","The capability shall be provided to aggregate telecommand packets within the same telecommand segment.\n    ","NOTE This does not apply to CPDU commands."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.1f","Requirement","ECSS-E-ST-70-11_0290087",1,"Created","A telecommand shall have the same action definition for the complete mission duration.\n    ","NOTE This precludes the use of flip/flop commands."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.1g","Requirement","ECSS-E-ST-70-11_0290088",1,"Created","The conditions under which a configuration-dependent telecommand can be sent (or cannot be sent) shall be determinable unambiguously from the housekeeping telemetry."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.1h","Requirement","ECSS-E-ST-70-11_0290089",1,"Created","The execution of any telecommand shall not lead to permanent loss of the telecommand function."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.1i","Requirement","ECSS-E-ST-70-11_0290090",1,"Created","Repetition of the same telecommand shall not result in any permanent degradation or loss of on-board functionality."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.1j","Requirement","ECSS-E-ST-70-11_0290091",1,"Created","The capability shall be provided to command all on-board devices individually from the ground. \n    ","NOTE 1 If a device is normally commanded using a higher-level telecommand function, this requirement specifies the capability for the ground segment to issue a device telecommand to be routed directly to that device.\nNOTE 2 This does not imply the use of high-priority commands, but can be achieved using bus-level commands."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.1k","Requirement","ECSS-E-ST-70-11_0290092",1,"Created","Command types shall correspond to the on-board function involved.\n    ","NOTE 1 The adjustment of the level or value of an on-board register or counter by the use of a register-load device command (not by a sequence of on/off commands).\nNOTE 2 The command of an on/off device by an on/off device command (not by a sub-function of a register-load device command)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.1l","Requirement","ECSS-E-ST-70-11_0290093",1,"Created","For redundant on-board units that can only be operated in cold standby (i.e. only one unit can be on at any given time), the equivalent telecommands on the prime and redundant equipment shall be: \n    1. identical, and \n    2. allocated the same APID."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.1m","Requirement","ECSS-E-ST-70-11_0290094",1,"Created","For redundant on-board units that can be operated in parallel (i.e. both units can be operated simultaneously), the equivalent telecommands on the prime and redundant equipment shall be: \n    1. identical, and\n    2. allocated different APIDs."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.1n","Requirement","ECSS-E-ST-70-11_0290095",1,"Created","The maximum execution duration of a telecommand shall be deterministic.\n    ","NOTE This implies knowledge by the ground segment that a command has been successfully executed so that the next command can be initiated. This does not exclude the possibility that subsequent automated processes with a specified goal (bounded duration) are triggered by a telecommand, so long as the process can be monitored as specified in clause 5.3.1."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.2a","Requirement","ECSS-E-ST-70-11_0290096",1,"Created","The capability shall be provided to implement critical command functions using different categories of telecommand.\n    ","NOTE For example, the use of an on-board operations procedure or the on-board schedule to execute a critical telecommand function that is normally executed from the ground using a CPDU telecommand; the use of low-level commands to replace a nominal high-level function."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.2b","Requirement","ECSS-E-ST-70-11_0290097",1,"Created","At least two separate command actions shall be used for the execution of mission-critical and safety-critical functions.\n    ","NOTE 1 This means an arm/safe or enable/disable command followed by an execute command.\nNOTE 2 See clause 3.2.2 for the definition of telecommand criticality categories.\nNOTE 3 An example where this requirement is applicable, is for commands for pyrotechnic devices."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.2c","Requirement","ECSS-E-ST-70-11_0290098",1,"Created","Register load telecommands that are mission-critical, safety-critical or vital in nature shall have a separate execute command so that the loaded data can be verified prior to execution."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.2d","Requirement","ECSS-E-ST-70-11_0290099",1,"Created","Redundant telecommands shall be provided for all mission-critical and vital telecommands by means of a maximum diversity on-board routing, i.e. using on-board routes that share no common nodes or paths.\n    ","NOTE This can be achieved by using redundant equipment."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.3a","Requirement","ECSS-E-ST-70-11_0290100",1,"Created","The capability shall be provided to “interrupt” the transmission of a telecommand packet by the transmission of another telecommand packet of higher priority."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.3b","Requirement","ECSS-E-ST-70-11_0290101",1,"Created","The on-board processing and distribution of telecommands shall ensure that no restrictions arise when the ground segment transmits telecommands of any type at the highest possible rate (i.e. making full use of the available uplink bandwidth).\n    ","NOTE This includes the case where all commands are of the same type and to the same application process, e.g. a memory load."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.3c","Requirement","ECSS-E-ST-70-11_0290102",1,"Created","Telecommand routing shall ensure that an on-board “blockage” resulting from payload commanding has no impact on platform commanding.\n    ","NOTE For example, an extensive command sequence for the configuration of a payload, which has no impact on the essential commanding of platform subsystems in parallel."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.3d","Requirement","ECSS-E-ST-70-11_0290103",1,"Created","Where the allocation of on-board routes can be modified (e.g. using a table-based mapping of APIDs to MAPs), the capability shall be provided to request a report of the on-board routing and status information."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.3e","Requirement","ECSS-E-ST-70-11_0290104",1,"Created","In order to be able to unambiguously identify the source of a telecommand (e.g. the ground or a given on-board application process), the source shall be explicitly indicated within the telecommand packet itself.\n    ","NOTE The source of telecommands released from an on-board schedule is the ground segment."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.4a","Requirement","ECSS-E-ST-70-11_0290105",1,"Created","The capability shall be provided to perform complete and unambiguous verification of well-defined stages of telecommand execution.\n    ","NOTE This applies to telecommands that are sent directly from the ground or are stored on-board for release at a later time."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.4b","Requirement","ECSS-E-ST-70-11_0290106",1,"Created","The potential stages of telecommand execution that can be verified shall include acceptance, start of execution, progress of execution and completion of execution.\n    ","NOTE These stages of telecommand execution are defined in ECSS-E-ST-70-41, clause 4.4.3."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.4c","Requirement","ECSS-E-ST-70-11_0290107",1,"Created","Except for telecommands that are executed purely by hardware (e.g. CPDU commands), verification of the acceptance stage shall be provided for all telecommands."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.4d","Permission","ECSS-E-ST-70-11_0290352",1,"Created","Verification of execution stages subsequent to acceptance:\n    1. need not be performed, and \n    2. may be different for individual telecommands."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.4e","Requirement","ECSS-E-ST-70-11_0290109",1,"Created","Failure of telecommand execution at any of the identified stages shall either be explicitly reported or unambiguously observable in the housekeeping telemetry.\n    ","NOTE ECSS-E-ST-70-41 service 1 can be used for this purpose."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.4f","Requirement","ECSS-E-ST-70-11_0290110",1,"Created","The telecommand packet shall indicate, in its packet data field header, the reports of successful execution to be generated."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.4g","Requirement","ECSS-E-ST-70-11_0290111",1,"Created","The selection possibilities for the reports of successful execution shall range from “no telecommand verification packets” to “verification at each distinct step of acceptance and execution”."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.4h","Requirement","ECSS-E-ST-70-11_0290112",1,"Created","Verification telemetry shall be provided with a delay of less than <TC_VERIF_DELAY> with respect to the time of completion of the corresponding telecommand execution stage."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.4i","Requirement","ECSS-E-ST-70-11_0290113",1,"Created","If a telecommand is invalid, it shall fail verification at the acceptance stage and shall not be distributed further.\n    ","NOTE For example, the length or CRC are wrong or the APID is invalid."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.4j","Requirement","ECSS-E-ST-70-11_0290114",1,"Created","Failure in the acceptance or the execution of commands originating on-board shall be notified to the ground segment by means of anomaly event reports."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.4k","Requirement","ECSS-E-ST-70-11_0290115",1,"Created","Verification of completion of execution of a telecommand shall use telemetry sampled at the same level as the device or function for which the telecommand is executed.\n    ","NOTE Examples are:\n        · A device telecommand verified by a hardware measurement that is directly telemetred without intermediate processing.\n        · A bi-level command verified by a status parameter."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.4l","Requirement","ECSS-E-ST-70-11_0290116",1,"Created","If a telecommand results directly in one or more changes to the space segment configuration, these changes shall be reported in the housekeeping telemetry."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.4m","Requirement","ECSS-E-ST-70-11_0290117",1,"Created","The effect of a telecommand shall be observable on the ground using telemetry data available under all circumstances under which the telecommand can be successfully executed.\n    ","NOTE To comply with this requirement, the effect of a telecommand affecting the status of on-board units involved in the generation or routing of telemetry is available in the “high priority” telemetry."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.5.4n","Requirement","ECSS-E-ST-70-11_0290118",1,"Created","Register load commands shall be confirmed by unique telemetry parameters dedicated to each commanded register, echoing exactly the currently loaded value."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.6.1a","Requirement","ECSS-E-ST-70-11_0290119",1,"Created","For configuration management purposes, the space segment shall be able to support at least the following modes:\n    1. “nominal” modes ensuring the generation of mission products;\n    2. “standby” modes ensuring safe operation of all spacecraft subsystems and payloads;\n    3. “survival” modes ensuring safety of all spacecraft subsystems and payloads."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.6.1b","Requirement","ECSS-E-ST-70-11_0290120",1,"Created","The operational modes of the space segment and its payload, subsystems and units shall be clearly identified in terms of both hardware and software configurations."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.6.1c","Requirement","ECSS-E-ST-70-11_0290121",1,"Created","The telemetry shall provide unambiguous identification of the modes and mode transitions."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.6.1d","Requirement","ECSS-E-ST-70-11_0290122",1,"Created","The capability shall be provided to perform payload mode-switching at a high-level, e.g. by sending a single mode-switching telecommand from the ground which initiates all the corresponding low-level commands to bring the payload into the desired mode."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.6.1e","Requirement","ECSS-E-ST-70-11_0290123",1,"Created","The capability shall be provided to perform all routine maintenance activities for spacecraft units by using nominal modes and mode transitions without impact on the performance of the modes and mode transitions."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.6.2a","Requirement","ECSS-E-ST-70-11_0290124",1,"Created","All on-board reconfigurations shall end with an unambiguously known and observable state of all involved elements (hardware and software)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.6.2b","Requirement","ECSS-E-ST-70-11_0290125",1,"Created","The maximum duration of an on-board reconfiguration shall be deterministic."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.6.2c","Requirement","ECSS-E-ST-70-11_0290126",1,"Created","Telemetry shall be available for the ground segment to monitor all stages of an on-board reconfiguration."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.6.2d","Requirement","ECSS-E-ST-70-11_0290127",1,"Created","The reconfiguration of on-board units or the switching between on-board functions shall not affect the status, the configuration, or the proper operation of any other unrelated unit or function."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.6.2e","Requirement","ECSS-E-ST-70-11_0290128",1,"Created","Telemetry indicating the cause of an on-board reconfiguration shall be available to the ground segment after the completion of the reconfiguration."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.6.2f","Requirement","ECSS-E-ST-70-11_0290129",1,"Created","The capability shall be provided to pre-configure selected units into consistent configurations prior to their selection as operational.\n    ","NOTE For example, the bolometer inhibition status of an infrared attitude sensor."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.6.2g","Requirement","ECSS-E-ST-70-11_0290130",1,"Created","With the exception of high-priority commands, all potentially critical configuration change telecommands initiated by the ground segment shall be buffered on-board in such a way that all parameters defining the new configuration can be inspected by the ground segment, via telemetry, before executing the change on-board."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.6.2h","Requirement","ECSS-E-ST-70-11_0290131",1,"Created","The capability shall be provided to trigger any on-board reconfiguration activities that put the space segment into a predefined safe state:\n    1. autonomously, and\n    2. by ground commanding."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.6.2i","Requirement","ECSS-E-ST-70-11_0290132",1,"Created","After separation from the launcher, the space segment shall enter a state in which it can survive for a predefined period without ground segment support. \n    ","NOTE For example, an automatic sequence triggered on detection of the separation."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.6.2j","Requirement","ECSS-E-ST-70-11_0290133",1,"Created","The capability shall be provided to configure the timing of the individual actions within on-board sequences by ground commands."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.6.2k","Requirement","ECSS-E-ST-70-11_0290134",1,"Created","The effect of each individual action within an on-board sequence shall be visible in the telemetry."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.6.2l","Requirement","ECSS-E-ST-70-11_0290135",1,"Created","The space segment shall provide mechanisms to avoid or recover from any conflict that can arise from the execution of on-board autonomous actions and ground scheduled commands.\n    ","NOTE For example, the parallel execution of routine procedures and event-driven procedures."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.6.2m","Requirement","ECSS-E-ST-70-11_0290136",1,"Created","At power up, restart and upon recovery from any power loss, the space segment electrical configuration (including all subsystems, units and instruments) shall be set into a known deterministic and reproducible state."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.2a","Requirement","ECSS-E-ST-70-11_0290137",1,"Created","The space segment shall provide on-board autonomy management functions taking into account specific mission constraints and characteristics such as:\n    1. acceptable mission outage;\n    2. expected ground station coverage;\n    3. maximum unexpected ground segment non-availability period."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.2b","Requirement","ECSS-E-ST-70-11_0290138",1,"Created","The on-board autonomy management functions shall be capable of performing all operations to continue mission operations for an autonomy duration of <AUT_DUR_EXEC>."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.2c","Requirement","ECSS-E-ST-70-11_0290139",1,"Created","The on-board autonomy management functions shall be capable of performing all operations to store mission products for an autonomy duration of <AUT_DUR_DATA>."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.2d","Requirement","ECSS-E-ST-70-11_0290140",1,"Created","The on-board autonomy management functions shall be capable of performing all operations to safeguard the space segment for an autonomy duration of <AUT_DUR_FAIL> in the presence of a single failure.\n    ","NOTE This includes the time used by the ground segment to perform failure diagnosis and full recovery."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.2e","Requirement","ECSS-E-ST-70-11_0290141",1,"Created","The fault management functions implemented on-board shall be designed such that the reaction time for the ground segment is not less than <ANOM_RESP_TIME>."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.2f","Requirement","ECSS-E-ST-70-11_0290142",1,"Created","The ground segment shall be capable of overriding any on-board autonomous function."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.2a","Requirement","ECSS-E-ST-70-11_0290143",1,"Created","The space segment shall provide FDIR functions that take into account:\n    1. the autonomy requirements addressed in clause 5.7.2a,\n    2. system, subsystem, equipment and unit safeguarding needs, and\n    3. ground segment intervention conditions.\n        ","NOTE FDIR functions are those functions that implement the failure detection, isolation and recovery actions. The FDIR functionality is established at various levels within the space segment, e.g. at hardware and software levels. The implementation of the FDIR functions is based on specific system needs, e.g. specific time constants."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.2b","Requirement","ECSS-E-ST-70-11_0290144",1,"Created","FDIR functions shall be implemented in a hierarchical manner in order to detect, isolate and recover failures at the lowest possible implementation level.\n    ","NOTE 1 For example, FDIR handling on an on-board data bus implying retries and subsequent error mechanisms in case these retries are unsuccessful.\nNOTE 2 This requirement can imply a staggered recovery scheme based on retry functions (see also clause 5.7.5.4)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.2c","Recommendation","ECSS-E-ST-70-11_0290353",1,"Created","The FDIR design should not be overly cautious, e.g. if a detected anomaly can be isolated to a specific payload or subsystem, it should not trigger a full payload switch-off or a switch to a spacecraft safe mode."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.2d","Requirement","ECSS-E-ST-70-11_0290146",1,"Created","If an FDIR function that is implemented in software is not available, a fallback mechanism shall be provided using an independent mechanism.\n    ","NOTE The independent mechanism can be a watchdog running on a separate unit or a hardware-based mechanism."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.2e","Requirement","ECSS-E-ST-70-11_0290147",1,"Created","The FDIR functions shall make use of the redundancy implemented on board."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.2f","Requirement","ECSS-E-ST-70-11_0290148",1,"Created","Any abnormal operational situation of the spacecraft, its subsystems, equipment or units shall be notified to or detectable by the next higher operational control instance (FDIR level)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.2g","Requirement","ECSS-E-ST-70-11_0290149",1,"Created","Failures that cannot be handled at a given level shall be handed over to the next higher operational instance, the highest instance being the ground segment."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.2h","Requirement","ECSS-E-ST-70-11_0290150",1,"Created","Failure detection, isolation and recovery activities performed on-board shall be reported in an unambiguous manner to the ground segment."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.2i","Requirement","ECSS-E-ST-70-11_0290151",1,"Created","The reporting of FDIR activities shall contain all information for failure analysis (e.g. time of occurrence, parameter out-of-limit, switching performed). \n    ","NOTE A time delay for this reporting can be accepted if, for example, the reporting uses an operational on-board processor."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.2j","Recommendation","ECSS-E-ST-70-11_0290354",1,"Created","The FDIR functions implemented on-board should be intrinsically failsafe."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.2k","Requirement","ECSS-E-ST-70-11_0290153",1,"Created","Except for passive hardware functions that cannot be overridden (such as fuses), the capability shall be provided to enable and to disable any on-board FDIR function by telecommand.\n    ","NOTE For example, the inhibition of a latch-up detector or the bypassing of an auto-test function."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.2l","Requirement","ECSS-E-ST-70-11_0290154",1,"Created","Where FDIR functions are based on several inputs (e.g. sensor readings, and unit status), which are independently tested to determine a failure condition, the capability shall be provided to enable and disable each such input by telecommand."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.2m","Requirement","ECSS-E-ST-70-11_0290155",1,"Created","The FDIR functions shall not be based on processing of an input that is currently disabled."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.2n","Requirement","ECSS-E-ST-70-11_0290156",1,"Created","The FDIR design shall be modular such that the ground segment can enable and disable parts of it in a graceful and consistent manner without having a detrimental effect on the overall system."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.3a","Requirement","ECSS-E-ST-70-11_0290157",1,"Created","The space segment shall provide the means to detect and report any on-board anomaly condition. \n    ","NOTE This includes both hardware and software anomalies."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.3b","Requirement","ECSS-E-ST-70-11_0290158",1,"Created","The capability shall be provided to monitor and to define out-of-limit conditions for essential on-board parameters (see clause 5.8.6)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.3c","Requirement","ECSS-E-ST-70-11_0290159",1,"Created","Failure detection algorithms shall not repeat the generation of the same exception telemetry if the same failure is detected at each successive failure detection cycle."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.3d","Recommendation","ECSS-E-ST-70-11_0290355",1,"Created","A separate telemetry indication should be generated if the exception condition disappears."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.3e","Requirement","ECSS-E-ST-70-11_0290161",1,"Created","Anomaly reports shall contain a unique identification of the anomaly, its time of occurrence, and a record of the input data to the anomaly detection function.\n    ","NOTE The record of the input data can range from a snapshot to a historical record."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.3f","Requirement","ECSS-E-ST-70-11_0290162",1,"Created","The failure detection functions shall be independent from the nominal monitoring and control functions.\n    ","NOTE For example, an AOCS FDIR function using different sensors from those used by the nominal AOCS control function."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.3g","Requirement","ECSS-E-ST-70-11_0290163",1,"Created","If a failure detection function uses multiple inputs which are combined (e.g. OR/AND), then these inputs shall be independently derived, i.e. the inputs shall not come from the same source (e.g. unit), in case that source is faulty."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.3h","Requirement","ECSS-E-ST-70-11_0290164",1,"Created","The capability shall be provided to detect failures in systems that are off line (i.e. not involved in any primary function) when this does not conflict with operational configurations or operational constraints."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.3i","Requirement","ECSS-E-ST-70-11_0290165",1,"Created","Except for hardwired failure detection mechanisms, parameters of failure detection criteria (such as thresholds and number of failure repetitions) shall be modifiable by telecommand."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.4a","Requirement","ECSS-E-ST-70-11_0290166",1,"Created","The space segment shall provide functions to isolate the failed unit or subsystem, to avoid failure propagation and deterioration of the impacted equipment."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.4b","Requirement","ECSS-E-ST-70-11_0290167",1,"Created","For failures whose resolution implies safeguarding of system functions, the offending unit, subsystem or function shall be disabled or switched off.\n    ","NOTE For example, avoidance of power drain by a failed unit to a level where the ability to provide power to the rest of the spacecraft (a vital system function) is endangered."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.4c","Requirement","ECSS-E-ST-70-11_0290168",1,"Created","For failures whose resolution does not imply the safeguarding of system functions, hierarchical isolation steps shall be applied (e.g. protocol-level retries or on-board operations procedures) before removal of the failed unit from the operational configuration.\n    ","NOTE The hierarchical isolation steps can include:\n        · command retries and telemetry readback;\n        · appropriate equipment switching, i.e. the selection of redundant equipment by telecommand or by on-board operations procedures, including functional verification;\n        · application of delay times before switching off the failed equipment."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.5a","Requirement","ECSS-E-ST-70-11_0290169",1,"Created","If an on-board failure detection function identifies an anomalous situation, it shall trigger autonomous recovery actions consistent with the specific mission needs without ground segment intervention."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.5b","Requirement","ECSS-E-ST-70-11_0290170",1,"Created","Any potential conflict between failure recovery activities and nominally ongoing on-board commanding activities shall be identified and managed.\n    ","NOTE This can imply suspending the on-board operations schedule and currently active on-board operations procedures."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.5c","Requirement","ECSS-E-ST-70-11_0290171",1,"Created","A failure in the performance of an autonomous recovery action shall be followed by an action to ensure the safety of the spacecraft, subsystem or payload.\n    ","NOTE In some cases, pre-defined retries are implemented in the system (e.g. for protocol handling)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.5d","Requirement","ECSS-E-ST-70-11_0290172",1,"Created","Where FDIR functions trigger an autonomous recovery to redundant units, the capability shall be provided to independently specify by telecommand the units to be monitored (for failure detection) and the combination of units to be selected for the recovery activities (from the available combinations)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.6a","Requirement","ECSS-E-ST-70-11_0290173",1,"Created","The safety of the space segment and its sub-functions shall be ensured for a predefined period <AUT_DUR_FAIL> in the presence of a single on-board failure and in the absence of ground segment intervention."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.6b","Requirement","ECSS-E-ST-70-11_0290174",1,"Created","After detection of an on-board failure that threatens space segment safety, the Level F1 fault management functions shall trigger reconfiguration activities leading to an on-board safe state."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.6c","Requirement","ECSS-E-ST-70-11_0290175",1,"Created","The spacecraft shall enter a safe state if any hazard exists that affects spacecraft or payload health or mission objectives."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.6d","Requirement","ECSS-E-ST-70-11_0290176",1,"Created","The spacecraft shall not enter survival mode if no hazard exists that affects spacecraft or payload health or mission objectives. \n    ","NOTE In particular, this implies a robustness of the implementation of the hierarchical FDIR to cope with minor errors (e.g. operational errors resulting from a single telecommand issued in the wrong context) without causing entry into survival mode."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.6e","Requirement","ECSS-E-ST-70-11_0290177",1,"Created","Recovery from survival mode shall be undertaken under ground control."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.7a","Requirement","ECSS-E-ST-70-11_0290178",1,"Created","The failed function shall be restored within a mission-specified interval of time."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.7.5.7b","Requirement","ECSS-E-ST-70-11_0290179",1,"Created","The on-board fault management function shall autonomously establish a fully operational configuration such that mission operations can continue, including the generation of the mission products. "]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.1a","Requirement","ECSS-E-ST-70-11_0290180",1,"Created","The capability shall be provided for the ground segment to exercise control over an application process.\n    ","NOTE As a minimum this includes “reset”."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.1b","Requirement","ECSS-E-ST-70-11_0290181",1,"Created","The application process identifier (APID) shall uniquely identify the on-board address indicating the source (telemetry source packets) or destination (telecommand packets) of packets."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.1c","Recommendation","ECSS-E-ST-70-11_0290356",1,"Created","Different platform subsystems and payloads should be assigned different sets of APIDs."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.1d","Requirement","ECSS-E-ST-70-11_0290183",1,"Created","The assignment of APIDs shall remain unchanged during the mission."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.1e","Recommendation","ECSS-E-ST-70-11_0290357",1,"Created","If the on-board design includes functions providing services and capabilities for which there is a standard service defined in ECSS-E-ST-70-41 clause 5.5, these services and capabilities should conform to ECSS-E-ST-70-41, clauses 6 to 21."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.1f","Requirement","ECSS-E-ST-70-11_0290185",1,"Created","The structure of all variable telemetry and telecommand packets shall conform to ECSS-E-ST-70-41, clauses 5.3 and 5.4."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.1g","Requirement","ECSS-E-ST-70-11_0290186",1,"Created","Each telecommand packet shall be characterized by its destination service type and by a service subtype indicating the type of function or activity requested to be executed by the service."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.1h","Requirement","ECSS-E-ST-70-11_0290187",1,"Created","All telemetry packets containing a data field header shall include type and subtype fields which appear in the same location."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.1i","Requirement","ECSS-E-ST-70-11_0290188",1,"Created","The structure of a telemetry packet containing a data field header shall be derivable from the combination of its APID, type and subtype and up to two auxiliary packet identification fields.\n    ","NOTE For example, the structure ID (SID) in ECSS-E-ST-70-41 housekeeping packets."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.1j","Requirement","ECSS-E-ST-70-11_0290189",1,"Created","All telemetry packets of the same type and subtype shall contain the auxiliary identification fields at the same location and with the same width."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.1k","Requirement","ECSS-E-ST-70-11_0290190",1,"Created","The combination of APID, packet type, subtype and auxiliary identification fields shall be uniquely assigned across the complete spacecraft (i.e. across all application processes generating telemetry)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.1l","Requirement","ECSS-E-ST-70-11_0290191",1,"Created","Variable packet structures shall only be used for event-driven or request-driven telemetry packets.\n    ","NOTE This does not apply to payload measurement data."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.1m","Requirement","ECSS-E-ST-70-11_0290192",1,"Created","The “Parameter#” used on-board to identify telemetry parameters shall be uniquely assigned across the complete spacecraft.\n    ","NOTE For the “Parameter#” used on-board to identify telemetry parameters, see ECSS-E-ST-70-41 for additional information."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.1n","Requirement","ECSS-E-ST-70-11_0290193",1,"Created","The choice structure corresponding to a given value of a choice parameter shall be unique for the complete spacecraft.\n    ","NOTE For the choice structure corresponding to a given value of a choice parameter (see ECSS-E-ST-70-41 for additional information)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.2a","Requirement","ECSS-E-ST-70-11_0290194",1,"Created","The capability shall be provided to report statistics relating to a specified set of parameters over an interval of time."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.2b","Requirement","ECSS-E-ST-70-11_0290195",1,"Created","The capability shall be provided to report maximum, minimum and mean values and the standard deviation."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.2c","Requirement","ECSS-E-ST-70-11_0290196",1,"Created","The capability shall be provided to add and delete parameters from the set being evaluated."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.2d","Requirement","ECSS-E-ST-70-11_0290197",1,"Created","The capability shall be provided to clear the set of parameters being evaluated."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.2e","Requirement","ECSS-E-ST-70-11_0290198",1,"Created","The capability shall be provided to reset the evaluation of parameter statistics."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.2f","Requirement","ECSS-E-ST-70-11_0290199",1,"Created","The capability shall be provided to request a report of the current set of parameters being evaluated."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.3a","Requirement","ECSS-E-ST-70-11_0290200",1,"Created","The capability shall be provided for the ground segment to load any changeable memory area."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.3b","Requirement","ECSS-E-ST-70-11_0290201",1,"Created","The capability shall be provided to load a contiguous memory area (e.g. by specifying the start address and the data to be loaded)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.3c","Requirement","ECSS-E-ST-70-11_0290202",1,"Created","The capability shall be provided to perform scatter loads with a single telecommand message (e.g. by specifying sets of start address and data to be loaded)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.3d","Requirement","ECSS-E-ST-70-11_0290203",1,"Created","As part of the on-board acceptance of a memory load, the destination application process shall be able to detect data corruptions."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.3e","Requirement","ECSS-E-ST-70-11_0290204",1,"Created","The on-board end-to-end verification of a memory load shall consist of confirming that the data has been correctly loaded into its destination memory (by reading it back from the memory and comparing it with the load data)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.3f","Requirement","ECSS-E-ST-70-11_0290205",1,"Created","The capability shall be provided for the ground segment to dump any memory area, on request."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.3g","Requirement","ECSS-E-ST-70-11_0290206",1,"Created","The capability shall be provided to request a memory dump from a contiguous memory area (e.g. by specifying the start address and the length of the dump)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.3h","Requirement","ECSS-E-ST-70-11_0290207",1,"Created","A single memory dump telemetry packet shall only contain data from memory areas containing contiguous on-board memory addresses.\n    ","NOTE If a dump is requested across one or more discontinuities in memory address (e.g. due to memory pages), this implies that the memory dump uses different telemetry packets that are aligned with the address discontinuities."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.3i","Requirement","ECSS-E-ST-70-11_0290208",1,"Created","The capability shall be provided to request scatter dumps (e.g. by specifying sets of start addresses and length of the dump)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.3j","Requirement","ECSS-E-ST-70-11_0290209",1,"Created","The on-board system shall not impose artificial constraints on the size of memory areas that can be loaded and dumped based on a single command."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.3k","Requirement","ECSS-E-ST-70-11_0290210",1,"Created","The on-board system shall not impose artificial constraints on the uplink speed of memory load command or memory dump command."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.3l","Requirement","ECSS-E-ST-70-11_0290211",1,"Created","The capability shall be provided for the ground segment to request a check of any on-board memory."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.3m","Requirement","ECSS-E-ST-70-11_0290212",1,"Created","The capability shall be provided to request a memory check of a contiguous memory area (e.g. by specifying the start address and the length of the area to be checked)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.3n","Requirement","ECSS-E-ST-70-11_0290213",1,"Created","The capability shall be provided to request a memory check of several areas with a single telecommand message (e.g. by specifying sets of start addresses and lengths of areas to be checked)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.3o","Requirement","ECSS-E-ST-70-11_0290214",1,"Created","In response to a request to check memory, the on-board action shall be to perform a checksumming over the requested address ranges and report the result to the ground segment."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.3p","Requirement","ECSS-E-ST-70-11_0290215",1,"Created","Integrity of the memory area during load, dump or check operations shall be ensured by the on-board application process.\n    ","NOTE Memory integrity is normally ensured by preventing other application processes from writing to this memory area during the load or check process. "]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.3q","Recommendation","ECSS-E-ST-70-11_0290358",1,"Created","Memory loads should be permanently available on-board to avoid time-consuming memory re-loads from the ground following memory switch on.\n    ","NOTE For example, using EEPROM."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.4a","Recommendation","ECSS-E-ST-70-11_0290359",1,"Created","The specialized ground-controllable tasks of an application process should be implemented using the “Function management service” specified in ECSS-E-ST-70-41."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.4b","Requirement","ECSS-E-ST-70-11_0290218",1,"Created","The capability shall be provided for the ground segment to invoke a function and to pass instantiation parameters to it, by means of a single telecommand."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.5a","Requirement","ECSS-E-ST-70-11_0290219",1,"Created","The capability shall be provided for the ground segment to load any telecommand into the on-board operations schedule.\n    ","NOTE This restricts the maximum usable packet length of a telecommand, since it is a command embedded within an “insert-into-schedule” telecommand."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.5b","Requirement","ECSS-E-ST-70-11_0290220",1,"Created","The capability shall be provided to edit the on-board operations schedule (insert, append and delete telecommands).\n    ","NOTE Although it can be assumed that most telecommands are appended (i.e. uploaded in execution time order), no constraint is imposed on the order in which telecommands are uploaded."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.5c","Requirement","ECSS-E-ST-70-11_0290221",1,"Created","The capability shall be provided to perform the editing operations without stopping the schedule."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.5d","Requirement","ECSS-E-ST-70-11_0290222",1,"Created","The capability shall be provided to start and stop the on-board operations schedule."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.5e","Requirement","ECSS-E-ST-70-11_0290223",1,"Created","The on-board operations schedule shall consist of sub-schedules that can be individually controlled (started and stopped)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.5f","Requirement","ECSS-E-ST-70-11_0290224",1,"Created","The capability shall be provided to time-shift (i.e. advance or retard) a selected set of telecommands that have already been loaded in the on-board operations schedule.\n    ","NOTE This function is used to support the re-scheduling of operations and to avoid having to delete and re-load the affected telecommands."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.5g","Requirement","ECSS-E-ST-70-11_0290225",1,"Created","The capability shall be provided for a telecommand released from the on-board operations schedule to set an interlock on (i.e. condition the release of) subsequent telecommands within the same sub-schedule."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.5h","Requirement","ECSS-E-ST-70-11_0290226",1,"Created","The capability shall be provided to request a report of the contents of the on-board operations schedule."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.5i","Requirement","ECSS-E-ST-70-11_0290227",1,"Created","The capability shall be provided to perform all editing operations on the schedule even when it is in a stopped state."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.5j","Requirement","ECSS-E-ST-70-11_0290228",1,"Created","The capacity of the on-board operations schedule shall cover at least the needs of the autonomy period."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.5k","Requirement","ECSS-E-ST-70-11_0290229",1,"Created","The elapsed time for the on-board transfer of telecommands from the on-board operations schedule to the destination application process shall be predictable to an accuracy compatible with the telecommand execution time accuracy specified for the mission."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.5l","Requirement","ECSS-E-ST-70-11_0290230",1,"Created","The protocol for the on-board transfer of telecommands to their destination application process shall ensure that any transfer error is reported to ground and to the on-board operations schedule service."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.5m","Requirement","ECSS-E-ST-70-11_0290231",1,"Created","The on-board operations schedule service shall detect any situation that prevents the on-board transfer of a telecommand to its destination application process."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.5n","Requirement","ECSS-E-ST-70-11_0290232",1,"Created","A telecommand loaded into the on-board operations schedule with an on-board release time earlier that the current on-board time (OBT) shall be rejected."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.5o","Requirement","ECSS-E-ST-70-11_0290233",1,"Created","A telecommand loaded into the on-board operations schedule with an on-board release time equal to that of a telecommand already loaded shall not be rejected but released immediately after that other telecommand."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.5p","Requirement","ECSS-E-ST-70-11_0290234",1,"Created","Any telecommands in the on-board schedule that have “elapsed” because the schedule, sub-schedule or application process to which they relate has been stopped and subsequently restarted, shall not be released."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.5q","Requirement","ECSS-E-ST-70-11_0290235",1,"Created","Management of the memory area used for the on-board operations schedule shall be performed autonomously on-board and shall not restrict schedule operation or schedule editing operations."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.5r","Requirement","ECSS-E-ST-70-11_0290236",1,"Created","The execution of each telecommand released from the on-board operations schedule shall result in the generation of either a “successful completion of execution” or an “execution failure” verification report."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.6a","Requirement","ECSS-E-ST-70-11_0290237",1,"Created","The capability shall be provided to monitor on-board a set of on-board parameters defined by ground segment.\n    ","NOTE All telemetry parameters are normally available to the on-board monitoring function."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.6b","Requirement","ECSS-E-ST-70-11_0290238",1,"Created","The on-board monitoring capabilities shall include limit-checking, expected-value-checking and delta-checking."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.6c","Requirement","ECSS-E-ST-70-11_0290239",1,"Created","The capability shall be provided to specify more than one mode-dependent monitoring check for a given parameter.\n    ","NOTE “Mode dependent” means that the check is only applied if the corresponding mode is TRUE. In the event that more than one mode is contemporaneously TRUE, all corresponding checks are applied."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.6d","Requirement","ECSS-E-ST-70-11_0290240",1,"Created","The capability shall be provided to enable and disable either the complete on-board monitoring function or selected parameters in the “monitoring list”."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.6e","Requirement","ECSS-E-ST-70-11_0290241",1,"Created","The capability shall be provided to add parameters and their monitoring information to the on-board monitoring list."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.6f","Requirement","ECSS-E-ST-70-11_0290242",1,"Created","The capability shall be provided to modify the monitoring characteristics of a parameter, including limit sets, expected value checks, delta checks and filtering characteristics."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.6g","Requirement","ECSS-E-ST-70-11_0290243",1,"Created","The capability shall be provided to modify parameter monitoring information without having to first delete the parameter and then add it again to the monitoring list."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.6h","Requirement","ECSS-E-ST-70-11_0290244",1,"Created","The capability shall be provided to clear the complete on-board monitoring list or to delete selected parameters from it."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.6i","Requirement","ECSS-E-ST-70-11_0290245",1,"Created","If the on-board monitoring list contains checks that are used by on-board FDIR functions, then the clear command shall be implemented as a mission-critical command."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.6j","Requirement","ECSS-E-ST-70-11_0290246",1,"Created","All changes of monitoring status shall be reported to the ground segment by means of a “check transition” telemetry packet.\n    ","NOTE For example, a check transition telemetry packet produced when a parameter goes out-of-limits and when it subsequently returns back into limits."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.6k","Requirement","ECSS-E-ST-70-11_0290247",1,"Created","The capability shall be provided for a change of monitoring status to give rise to an event report.\n    ","NOTE 1 This capability is used when an on-board action is defined for execution when this check transition occurs (see clause 5.8.12).\nNOTE 2 This capability is not provided as a standard on-board monitoring service capability by ECSS-E-ST-70-41."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.6l","Requirement","ECSS-E-ST-70-11_0290248",1,"Created","The capability shall be provided to request a report of the contents of the monitoring list including the parameter monitoring characteristics."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.6m","Requirement","ECSS-E-ST-70-11_0290249",1,"Created","The capability shall be provided to request a report of the full set of parameters that are currently in violation of any of their monitoring checks."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.6n","Requirement","ECSS-E-ST-70-11_0290250",1,"Created","The capability shall be provided to perform all editing operations on the on-board monitoring function even when it is in a disabled state."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.7a","Requirement","ECSS-E-ST-70-11_0290251",1,"Created","Taking into account factors such as uplink bandwidth, ground contact periods and time to recover from telecommand failure, a given mission shall be capable of defining a maximum telecommand packet length which is less than the maximum specified by ECSS-E-ST-50-04."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.7b","Requirement","ECSS-E-ST-70-11_0290252",1,"Created","Taking into account factors such as downlink bandwidth and ground contact periods, a given mission shall be capable of defining a maximum telemetry source packet length which is less than the maximum specified by ECSS-E-ST-50-03."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.7c","Requirement","ECSS-E-ST-70-11_0290253",1,"Created","When transferring a set of data that exceeds the maximum packet size specified for the mission (e.g. memory loading or dumping), the capability shall be provided to transfer this data in more than one packet (part packet)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.7d","Requirement","ECSS-E-ST-70-11_0290254",1,"Created","The capability shall be provided to send part packets with or without intermediate acknowledgement of receipt."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.7e","Requirement","ECSS-E-ST-70-11_0290255",1,"Created","In the event that the transfer of a part packet to its destination is not successful, the capability shall be provided to transfer succeeding part packets.\n    ","NOTE The procedure used for the large data transfer protocol is defined in Clause 16 of ECSS-E-ST-70-41."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.8a","Requirement","ECSS-E-ST-70-11_0290256",1,"Created","The capability shall be provided to selectively enable and disable the forwarding of telemetry source packets to the ground segment."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.8b","Requirement","ECSS-E-ST-70-11_0290257",1,"Created","The capability shall be provided to enable and disable telemetry source packet generation at the level of the originating service."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.8c","Requirement","ECSS-E-ST-70-11_0290258",1,"Created","The capability shall be provided to request a report of which telemetry source packets generated by an application process are currently disabled for forwarding to the ground segment."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.9a","Requirement","ECSS-E-ST-70-11_0290259",1,"Created","For missions with intermittent ground coverage, the on-board storage capability shall be able to store all packets generated on-board for space segment monitoring and control purposes, for a duration at least equal to the longest non-coverage period. "]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.9b","Requirement","ECSS-E-ST-70-11_0290260",1,"Created","For missions with continuous ground coverage, loss of one-shot packets (i.e. event-driven or request-driven packets) shall be remedied by the short-term on-board storage of the last <PKTS_NUM_STORED> packets.\n    ","NOTE This includes telecommand verification packets (they are effectively request-driven)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.9c","Requirement","ECSS-E-ST-70-11_0290261",1,"Created","An on-board store shall be provided containing an “anomaly log” of all event or request-driven packets reporting on-board anomalies.\n    ","NOTE For example, autonomous switch-downs and command failure reports."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.9d","Requirement","ECSS-E-ST-70-11_0290262",1,"Created","The content of the anomaly log specified in requirement 5.8.9c shall be persistent even after a reconfiguration or a cold restart of the application process managing the store."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.9e","Requirement","ECSS-E-ST-70-11_0290263",1,"Created","On-board storage shall be such that the ground segment can retrieve the stored packets within specified delays <PKT_RETR_DELAY>.\n    ","NOTE 1 For example, packets of high operational significance, such as error or anomaly packets, processed on the ground with shorter delays than routine status reporting packets.\nNOTE 2 There can be several such parameters for a given mission corresponding to data of different operational significance."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.9f","Requirement","ECSS-E-ST-70-11_0290264",1,"Created","The capability shall be provided to assign priorities to parallel retrievals from different stores.\n    ","NOTE These priorities can be assigned to maximize the utilization of the downlink bandwidth."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.9g","Requirement","ECSS-E-ST-70-11_0290265",1,"Created","For each independent on-board store, the capability shall be provided for the ground segment to enable and disable the storage function."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.9h","Requirement","ECSS-E-ST-70-11_0290266",1,"Created","For each independent on-board store, the capability shall be provided to specify the packets to be stored by adding or removing packets from a list maintained on-board."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.9i","Requirement","ECSS-E-ST-70-11_0290267",1,"Created","The capability shall be provided to select a given telemetry packet to be stored in more than one on-board store."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.9j","Requirement","ECSS-E-ST-70-11_0290268",1,"Created","On-board stores shall be either circular, where the oldest data is automatically overwritten when the store is full, or linear, where storage terminates when the on-board store is full."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.9k","Requirement","ECSS-E-ST-70-11_0290269",1,"Created","The capability shall be provided for the ground segment to clear the contents of a linear on-board store."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.9l","Requirement","ECSS-E-ST-70-11_0290270",1,"Created","The capability shall be provided to configure a linear packet store such that packets can be overwritten once they have been dumped and their reception has been acknowledged by the ground segment."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.9m","Requirement","ECSS-E-ST-70-11_0290271",1,"Created","The storage of packets shall not be interrupted if the ground segment requests a retrieval from, or reset of, the on-board storage."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.9n","Requirement","ECSS-E-ST-70-11_0290272",1,"Created","The capability shall be provided for the ground segment to request the retrieval of all packets from an on-board store or to specify a time window or a packet range for the retrieval."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.9o","Requirement","ECSS-E-ST-70-11_0290273",1,"Created","The capability shall be provided to request the retrieval of telemetry packets that have previously been retrieved (provided they have not yet been overwritten)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.9p","Requirement","ECSS-E-ST-70-11_0290274",1,"Created","The capability shall be provided to suspend and resume the retrieval of stored telemetry packets."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.9q","Requirement","ECSS-E-ST-70-11_0290275",1,"Created","When resuming a retrieval, it shall continue from the point where it was suspended."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.9r","Requirement","ECSS-E-ST-70-11_0290276",1,"Created","Housekeeping information shall be provided on the state of the on-board storage and retrieval function for each on-board store.\n    ","NOTE For example, fill level, pointer addresses."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.10a","Requirement","ECSS-E-ST-70-11_0290277",1,"Created","The on-board packet distribution system shall generate a report whenever a problem arises with the on-board traffic.\n    ","NOTE For example, a bottleneck in the distribution of telecommand packets or of telemetry source packets on the packet bus."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.10b","Requirement","ECSS-E-ST-70-11_0290278",1,"Created","Control capabilities shall be provided such that the ground segment can resolve all pre-identified on-board problems relating to telecommand packet re-assembly, telemetry data handling or on-board traffic."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.10c","Requirement","ECSS-E-ST-70-11_0290279",1,"Created","Packet bus management and resource parameters, such as average and peak bus loading and numbers of packet retransmissions, shall be routinely reported to the ground segment."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.11a","Requirement","ECSS-E-ST-70-11_0290280",1,"Created","The capability shall be provided to execute a set of operations procedures which can be loaded and controlled from the ground segment."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.11b","Requirement","ECSS-E-ST-70-11_0290281",1,"Created","The capability shall be provided to execute more than one operations procedure at the same time."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.11c","Requirement","ECSS-E-ST-70-11_0290282",1,"Created","The control operations shall include load, delete, start, stop, suspend, resume and transfer parameters."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.11d","Requirement","ECSS-E-ST-70-11_0290283",1,"Created","The ground segment shall be able to request a report of the currently active on-board operations procedures."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.11e","Requirement","ECSS-E-ST-70-11_0290284",1,"Created","The ground segment shall be able to request a report of the currently loaded on-board operations procedures."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.11f","Requirement","ECSS-E-ST-70-11_0290285",1,"Created","On-board operations procedures shall be capable to send any command available for transmission from the ground segment."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.11g","Requirement","ECSS-E-ST-70-11_0290286",1,"Created","On-board operations procedures shall have access to any telemetry parameter available to the ground segment."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.11h","Requirement","ECSS-E-ST-70-11_0290287",1,"Created","The capability shall be provided to prioritize the execution of on-board operations procedures.\n    ","NOTE 1 For example, to give priority to fault management procedures.\nNOTE 2 Priority applies in the event of conflicts."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.12a","Requirement","ECSS-E-ST-70-11_0290288",1,"Created","The capability shall be provided to trigger an on-board action as a result of the detection of an on-board event.\n    ","NOTE An action in this context is a telecommand, which can itself initiate other on-board actions (e.g. a telecommand which starts an on-board operations procedure)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.12b","Requirement","ECSS-E-ST-70-11_0290289",1,"Created","On-board actions shall include any command available for transmission from the ground segment."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.12c","Requirement","ECSS-E-ST-70-11_0290290",1,"Created","The ground segment shall be able to add and delete event-to-action definitions to and from an on-board list and to request a report of the list."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.12d","Requirement","ECSS-E-ST-70-11_0290291",1,"Created","The capability shall be provided to enable and disable individual actions without having to delete the event-to-action definition."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.8.12e","Requirement","ECSS-E-ST-70-11_0290292",1,"Created","The triggering of an on-board action shall itself give rise to an event report."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.1a","Requirement","ECSS-E-ST-70-11_0290293",1,"Created","The design (selection) of on-board processors shall ensure that the available memory and performance accommodates, with a margin of <RESOURCE_MARGIN>:\n    1. the requirements of the baseline (i.e. as launched) processes, and\n    2. a realistic allocation for processes and data to be developed and loaded after launch."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.1b","Requirement","ECSS-E-ST-70-11_0290294",1,"Created","If an on-board processor is switched from a prime to a redundant unit (or vice versa), the switchover shall be such that operations can continue safely. \n    ","NOTE This implies either that:\n        · the operational context need not be reloaded from the ground segment, or \n        · the new processor can be loaded with a safe default context before the switchover."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.1c","Recommendation","ECSS-E-ST-70-11_0290360",1,"Created","A processor switchover should not invalidate telecommands not yet released from any ground schedule.\n    ","NOTE This implies that telecommands defined for the prime unit are also valid for the redundant unit, except for any command routing data which the ground system can automatically change when addressing the redundant processor."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.1d","Requirement","ECSS-E-ST-70-11_0290296",1,"Created","The capability shall be provided to save the operational context in non-volatile memory so that it can be restored if a processor is reset or temporarily switched off."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.1e","Recommendation","ECSS-E-ST-70-11_0290361",1,"Created","Redundant processors should provide the capability to be turned on and operated outside of any control function, for the purpose of evaluating their performance prior to switching to become prime."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.1f","Requirement","ECSS-E-ST-70-11_0290298",1,"Created","The resources utilized by on-board software shall be telemetred (e.g. memory usage, central processor unit (CPU) usage and I/O usage)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.1g","Requirement","ECSS-E-ST-70-11_0290299",1,"Created","The capability shall be provided to check that on-board software has been correctly uploaded before enabling it."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.1h","Requirement","ECSS-E-ST-70-11_0290300",1,"Created","The capability shall be provided for the ground segment to patch the nominal software directly."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.1i","Requirement","ECSS-E-ST-70-11_0290301",1,"Created","The contents of a RAM of a unit or instrument that is suspended or switched off as a result of an FDIR action shall be preserved so that the ground segment can dump the content for the purposes of failure investigation."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.1j","Recommendation","ECSS-E-ST-70-11_0290362",1,"Created","Enabling of on-board software should use only a single telecommand.\n    ","NOTE This does not preclude dual-step commanding because only the final command enables the software."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.1k","Requirement","ECSS-E-ST-70-11_0290303",1,"Created","Any communication between the ground and an on-board software function or software task shall be effected by means of telecommand and telemetry source packets specifically designed for the purpose.\n    ","NOTE The objective is to ensure that memory dump and memory load packets (for example) are not used for this purpose. They are not adequate for changes of this operational significance."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.1l","Requirement","ECSS-E-ST-70-11_0290304",1,"Created","Whenever a condition that forces a processor reset is detected by software, an event report shall be generated prior to enforcement of the reset."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.1m","Requirement","ECSS-E-ST-70-11_0290305",1,"Created","Whenever a processor is running synchronously scheduled tasks, it shall check at the end of each software cycle that all tasks scheduled for that cycle have been duly completed."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.1n","Requirement","ECSS-E-ST-70-11_0290306",1,"Created","Whenever a processor overload condition is detected, an event report shall be generated."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.1o","Recommendation","ECSS-E-ST-70-11_0290363",1,"Created","A processor overload condition should not automatically lead to the processor being halted."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.1p","Requirement","ECSS-E-ST-70-11_0290308",1,"Created","Whenever an unexpected arithmetic overflow condition is detected, an event report shall be generated."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.1q","Requirement","ECSS-E-ST-70-11_0290309",1,"Created","Whenever an illegal program instruction is encountered during execution of a program code, an event report shall be generated."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.1r","Requirement","ECSS-E-ST-70-11_0290310",1,"Created","Whenever a data bus error is detected, an event report shall be generated."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.1s","Requirement","ECSS-E-ST-70-11_0290311",1,"Created","Whenever a memory corruption is detected by an error detection and correction mechanism, an event report shall be generated."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.1t","Requirement","ECSS-E-ST-70-11_0290312",1,"Created","Whenever a checksum error is detected, an event report shall be generated."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.1u","Requirement","ECSS-E-ST-70-11_0290313",1,"Created","Whenever an internal inconsistency is detected, an event report shall be generated."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.1v","Requirement","ECSS-E-ST-70-11_0290314",1,"Created","The event reports that are generated in the case of a failure shall indicate the type of failure, its location and any additional information needed for failure diagnosis."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.2a","Requirement","ECSS-E-ST-70-11_0290315",1,"Created","The power telemetry parameters assigned shall be such that the power available and power demand can be directly established from the telemetry alone. \n    ","NOTE This becomes critical in eclipse seasons, for instance, when the solar array degrades to a level approaching the sunlit demand plus recharge demand, or when the in-eclipse loads closely match the battery capabilities."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.2b","Requirement","ECSS-E-ST-70-11_0290316",1,"Created","Means and telemetry shall be provided such that the ground segment can determine the state of charge of each battery throughout all mission phases, to an accuracy of better than <BATT_CHARGE_ACC>."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.2c","Requirement","ECSS-E-ST-70-11_0290317",1,"Created","For all units that have primary power consumption greater than <POW_CONS_THRESH>, a thermistor on a hot point or a primary current sensor shall be provided and made available in telemetry."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.2d","Requirement","ECSS-E-ST-70-11_0290318",1,"Created","The power for telemetry conditioning of equipment shall be hierarchically structured to avoid the generation of invalid telemetry (which could in turn trigger unnecessary recovery actions)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.2e","Requirement","ECSS-E-ST-70-11_0290319",1,"Created","The power for telemetry conditioning of equipment shall not be supplied from other unrelated units that are not permanently powered."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.2f","Requirement","ECSS-E-ST-70-11_0290320",1,"Created","Vital power control functions shall have a switch-over function to the redundant path, but never a switch-off function."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.2g","Requirement","ECSS-E-ST-70-11_0290321",1,"Created","The capability shall be provided to redefine the list of non-essential loads to be shed in the event of a power anomaly (e.g. battery undervoltage)."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.2h","Requirement","ECSS-E-ST-70-11_0290322",1,"Created","The capability shall be provided to change the state of a critical relay without powering it on."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.3a","Requirement","ECSS-E-ST-70-11_0290323",1,"Created","Redundant receivers, cross-strapped to redundant decoders, shall be provided."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.3b","Requirement","ECSS-E-ST-70-11_0290324",1,"Created","Except following the occurrence of post-launch failures, the ground segment shall not be enabled to achieve by command a state where less than two receivers are active."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.3c","Requirement","ECSS-E-ST-70-11_0290325",1,"Created","The combined coverage of all on-board TT&C antennas shall be such that telemetry and telecommand contact can be provided under specified attitude and orbit conditions.\n    ","NOTE This does not imply ensuring full ground segment coverage during all mission phases, but rather that the spacecraft can be accessed when specified."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.3d","Requirement","ECSS-E-ST-70-11_0290326",1,"Created","Where the on-board design implies switching between antennas (e.g. for inertial-pointing spacecraft or during attitude manoeuvres), it shall be ensured that the overlap between antenna patterns is such that there is at least <ANT_SWITCH_TIME> to effect antenna-switching under all expected orbit and attitude conditions."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.4a","Requirement","ECSS-E-ST-70-11_0290327",1,"Created","Telemetry generated by sensor elements shall be assigned to dedicated telemetry channels (i.e. parameters) in order to be able to monitor all sensors (whether used or not) for diagnostic purposes."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.4b","Requirement","ECSS-E-ST-70-11_0290328",1,"Created","The operating ranges of on-board sensors shall accommodate all operational scenarios with adequate margins."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.4c","Requirement","ECSS-E-ST-70-11_0290329",1,"Created","The telemetry of stimulated detectors shall be designed to handle all flight-phase conditions either in normal mode telemetry or by mode-switching to extended range."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.4d","Requirement","ECSS-E-ST-70-11_0290330",1,"Created","Housekeeping telemetry shall be continuously available to enable verification of the operation of on-board attitude control functions and the results of any on-board attitude determination."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.4e","Requirement","ECSS-E-ST-70-11_0290331",1,"Created","Telemetry monitoring of thruster actuation shall be provided to enable thruster on-time surveillance and fuel consumption determination."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.4f","Recommendation","ECSS-E-ST-70-11_0290364",1,"Created","In normal conditions the avionics of 3-axis controlled spacecraft should maintain the knowledge of the current 3-axis attitude."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.4g","Requirement","ECSS-E-ST-70-11_0290333",1,"Created","Means shall be provided for determining from telemetry the remaining fuel in each independent propellant system."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.4h","Requirement","ECSS-E-ST-70-11_0290334",1,"Created","The accuracy for determination of the amount of remaining fuel at any given point in the mission shall be related to the amount of fuel remaining, as agreed with the customer.\n    ","NOTE 1 This accuracy depends on the particular mission planning requirements.\nNOTE 2 An accuracy of 5 % is normally acceptable at the start of the mission; however, when there is only 10% of the fuel remaining, the acceptable accuracy is normally about 10% to 20%."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.5a","Requirement","ECSS-E-ST-70-11_0290335",1,"Created","One-shot drivable mechanisms shall be provided with both hard and soft end-stops, independently telemetred."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.5b","Requirement","ECSS-E-ST-70-11_0290336",1,"Created","The status of mechanisms that are locked during launch shall be available during the pre-launch phase."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.5c","Requirement","ECSS-E-ST-70-11_0290337",1,"Created","The capability shall be provided to monitor the various stages of a deployment process.\n    ","NOTE For example, all motorized deployments monitored by potentiometers."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.5d","Requirement","ECSS-E-ST-70-11_0290338",1,"Created","The position of all mechanisms shall be known for all anticipated operations."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.5e","Requirement","ECSS-E-ST-70-11_0290339",1,"Created","The positions of all mechanisms shall be commanded and monitored absolutely, i.e. not commanded incrementally or monitored by relative or cyclic readings."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.6a","Requirement","ECSS-E-ST-70-11_0290340",1,"Created","The capability shall be provided for the ground segment to enable and disable each individual thermal control loop."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.6b","Requirement","ECSS-E-ST-70-11_0290341",1,"Created","With the exception of loops that are driven by thermostats, the capability shall be provided to adjust the temperature control thresholds of each thermal control loop by ground command."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.7a","Requirement","ECSS-E-ST-70-11_0290342",1,"Created","The design of the payload shall include taking protective action against potential damage caused by the external environment.\n    ","NOTE For example, switch-off of the high voltages if the background radiation level is detected to be too high."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.7b","Requirement","ECSS-E-ST-70-11_0290343",1,"Created","Payloads shall provide the capability to enter a safe state upon receipt of a specific command."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.7c","Requirement","ECSS-E-ST-70-11_0290344",1,"Created","There shall be no requirement for the ground segment to perform extensive payload operations for an interval <PAYLOAD_INT> after separation from the launcher.\n    ","NOTE Simple instrument switch-on, or heater activation is not excluded."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.7d","Requirement","ECSS-E-ST-70-11_0290345",1,"Created","If data compression techniques are implemented, they shall not impose special requirements on the design of the ground segment, such as redundant links or larger antennae."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.7e","Requirement","ECSS-E-ST-70-11_0290346",1,"Created","The interpretation of compressed data shall not depend on the telemetry history."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.7f","Requirement","ECSS-E-ST-70-11_0290347",1,"Created","All information to assess the health and safety of a payload instrument shall be available in the housekeeping telemetry, i.e. this information shall be available without accessing science telemetry."]
["ECSS-E-ST-70-11C","ECSS - Superseded v1.0","5.9.7g","Recommendation","ECSS-E-ST-70-11_0290365",1,"Created","Any operationally-significant information on the configuration and timing of payload operations should be downlinked in the telemetry."]