航天系統(tǒng)技術(shù)成熟度等級(jí)及評(píng)價(jià)準(zhǔn)則定義_圖文_第1頁(yè)
航天系統(tǒng)技術(shù)成熟度等級(jí)及評(píng)價(jià)準(zhǔn)則定義_圖文_第2頁(yè)
航天系統(tǒng)技術(shù)成熟度等級(jí)及評(píng)價(jià)準(zhǔn)則定義_圖文_第3頁(yè)
航天系統(tǒng)技術(shù)成熟度等級(jí)及評(píng)價(jià)準(zhǔn)則定義_圖文_第4頁(yè)
航天系統(tǒng)技術(shù)成熟度等級(jí)及評(píng)價(jià)準(zhǔn)則定義_圖文_第5頁(yè)
已閱讀5頁(yè),還剩8頁(yè)未讀 繼續(xù)免費(fèi)閱讀

下載本文檔

版權(quán)說(shuō)明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請(qǐng)進(jìn)行舉報(bào)或認(rèn)領(lǐng)

文檔簡(jiǎn)介

1、ECSS-E-AS-11C1 October 2014 Space engineering Adoption Notice of ISO 16290, Space systems - Definition of the Technology Readiness Levels (TRLs and their criteria of assessmentECSS SecretariatESA-ESTECRequirements & Standards DivisionNoordwijk, The Netherlands ForewordThis Adoption Notice is one

2、 document of the series of ECSS Standards intended to be applied together for the management, engineering and product assurance in space projects and applications. ECSS is a cooperative effort of the European Space Agency, national space agencies and European industry associations for the purpose of

3、 developing and maintaining common standards. Requirements in this Standard are defined in terms of what shall be accomplished, rather than in terms of how to organize and perform the necessary work. This allows existing organizational structures and methods to be applied where they are effective, a

4、nd for the structures and methods to evolve as necessary without rewriting the standards.This Adoption Notice has been prepared by the ECSS TRL Task Force, reviewed by the ECSS Executive Secretariat and approved by the ECSS Technical Authority.DisclaimerECSS does not provide any warranty whatsoever,

5、 whether expressed, implied, or statutory, including, but not limited to, any warranty of merchantability or fitness for a particular purpose or any warranty that the contents of the item are error-free. In no respect shall ECSS incur any liability for any damages, including, but not limited to, dir

6、ect, indirect, special, or consequential damages arising out of, resulting from, or in any way connected to the use of this document, whether or not based upon warranty, business agreement, tort, or otherwise; whether or not injury was sustained by persons or property or otherwise; and whether or no

7、t loss was sustained from, or arose out of, the results of, the item, or any services that may be provided by ECSS.Published by: ESA Requirements and Standards DivisionESTEC, P.O. Box 299,2200 AG NoordwijkThe NetherlandsCopyright: 2014© by the European Space Agency for the members of ECSS Chang

8、e logFirst issueECSS-E-AS-11C1 October 2014 Table of contentsChange log (31 Scope (52 Context information (63 Terms, definitions and abbreviated terms (73.1Terms defined in other standards (73.2Terms specific to the present standard (73.3Abbreviated terms and symbols (73.4Nomenclature (84 Applicatio

9、n (9TablesTable 4-1: Applicability table for ISO 16290 (9Table 4-2: TRL summary: Milestones and work achievement (reproduced from ISO 16290:2013 (11 1Scope This document identifies the clauses and requirements modified with respect to the standard ISO 16290, Space systems - Definition of the Technol

10、ogy Readiness Levels (TRLs and their criteria of assessment, First edition 2013-11-01 for application in ECSS. 2Context information The standard ISO 16290, Space systems Definition of the Technology Readiness Levels (TRLs and their criteria of assessment, has been developed by ISO TC20/SC14. The TRL

11、 description and the achievements that are requested for enabling the TRL assessment at each level have been thoroughly discussed at international level, agreed by the ISO members and published as standard ISO 16290.Aiming at the development of world wide implementation standards dealing with TRL, E

12、CSS has proactively contributed to the preparation of ISO 16290. With this Adoption Notice ECSS is adopting and applying ISO 16290 with a minimum set of modifications, identified in the present document, to allow for reference and for a consistent integration in ECSS system of standards.The Table ta

13、ken from ISO 16290:2013, is reproduced with the permission of the International Organization for Standardization, ISO. This standard can be obtained from any ISO member and from the Web site of the ISO Central Secretariat at the following address: . Copyright remains with ISO. 3 Terms, de

14、finitions and abbreviated terms3.1 Terms defined in other standardsa.For the purpose of this document, the terms and definitions from ISO16290 (First edition 2013-11-01 apply, in particular for the following terms:1.element2.breadboard3.laboratory environment4.mature technology5.relevant environment

15、6.reproducible process7.validationb.For the purpose of this document the terms from ECSS-S-ST-00-01C,except the terms listed in 3.1a. apply, in particular for the following term:1.technology readiness levelc.For the purpose of this document the following terms from ECSS-M-ST-10apply:1.acceptance rev

16、iew2.qualification reviewmissioning result review3.2 Terms specific to the present standardNone.3.3 Abbreviated terms and symbolsThe abbreviated terms from ECSS-S-ST-00-01 and the following apply.Abbreviation MeaningAR acceptance reviewCRR commissioning result reviewQR qualification reviewTRL techno

17、logy readiness level 3.4 NomenclatureThe following nomenclature apply throughout this document:a.The word “shall” is used in this standard to express requirements. All therequirements are expressed with the word “shall”.b.The word “should” is used in this standard to express recommendations.All the

18、recommendations are expressed with the word “should”.NOTE It is expected that, during tailoring, all therecommendations in this document are eitherconverted into requirements or tailored out.c.The words “may” and “need not” are used in this standard to expresspositive and negative permissions respec

19、tively. All the positivepermissions are expressed with the word “may”. All the negativepermissions are expressed with the words “need not”.d.The word “can” is used in this standard to express capabilities orpossibilities, and therefore, if not accompanied by one of the previouswords, it implies desc

20、riptive text.NOTE In ECSS “may” and “can” have a completedifferent meaning: “may” is normative(permission and “can” is descriptive.e.The present and past tense are used in this standard to express statementof fact, and therefore they imply descriptive text. 4Application a.ISO 16290, Space systems -

21、Definition of the Technology Readiness Levels (TRLs and their criteria of assessment, first edition 2013-11-01 shall apply inECSS system apply as written (Section 1 through Section 4 with the following additions and modifications listed in Table 4-1.NOTE Table 4-2 is a reproduction of Table 1 of ISO

22、 16290:2013 ”TRL summary: Milestones and work achievement”.Table 4-1: Applicability table for ISO 16290Clause or requirement number Applicability Applicable text(the new/added text is underlinedComments Text as in the originaldocument(deleted text with strikethrough5 added Requirements Title5.1 adde

23、d General Title5.1a added To assess the readiness of an element the TRLs specified in ISO 16290:2013shall be applied.requirement5.2 added TRLs requirements Title5.2a added A TRL shall not be called TRL1 unless the conditions specified in 3.2.1 ofISO 16290:2013 and Table 4-2 first row are metrequirem

24、ent5.2b added A TRL shall not be called TRL2 unless the conditions specified in 3.3.1 ofISO 16290:2013 and Table 4-2 second row are met.requirement5.2c added A TRL shall not be called TRL3 unless the conditions specified in 3.4.1 of16290:2013 and Table 4-2 third row are met.requirement9 Clause or re

25、quirement number ApplicabilityApplicable text(the new/added text is underlinedCommentsText as in the originaldocument(deleted text with strikethrough5.2d added A TRL shall not be called TRL4 unless the conditions specified in 3.5.1 of ISO 16290:2013 and Table 4-2 fourth row are metrequirement 5.2e a

26、dded A TRL shall not be called TRL5 unless the conditions specified in 3.6.1 of ISO 16290:2013 and Table 4-2 fifth row are met.requirement 5.2f added A TRL shall not be called TRL6 unless the conditions specified in 3.7.1 of ISO 16290:2013 and Table 4-2 sixth row are met. requirement 5.2gaddedA TRL

27、shall not be called TRL7 unless:1. the conditions specified in 3.8.1 of ISO 16290:2013 and Table 4-2 seventhrow are met, 2. the element has passed through a successful QR. NOTE This successful QR can be from another programme.requirement5.2haddedA TRL shall not be called TRL8 unless:1. the condition

28、s specified in 3.9.1 of ISO 16290:2013 and Table 4-2 eighthrow are met, 2. a system, integrating the element, has passed through a successful AR. NOTE 1 This successful AR at system level can be from anotherprogrammeNOTE 2 Whatever is the hierarchy level of the element in the product tree,TRL 8 for

29、that element can only be achieved upon successful completion of the AR at system level.requirement5.2iaddedA TRL shall not be called TRL9 unless: 1. the conditions specified in 3.10.1 of ISO 16290:2013 and Table 4-2 ninthrow are met, 2. a system, integrating the element, has passed through a success

30、ful CRR.requirement10ECSS-E-AS-11C 1 October 2014 Table 4-2: TRL summary: Milestones and work achievement (reproduced from ISO 16290:2013 Technology Readiness Level TRL 1 - Basic principles observed and reported TRL 2 - Technology concept and/or application formulated TRL 3 - Analytical and experime

31、ntal critical function and/or characteristic proof-of-concept Milestone achieved for the element Potential applications are identified following basic observations but element concept not yet formulated. Formulation of potential applications and preliminary element concept. No proof of concept yet.

32、Element concept is elaborated and expected performance is demonstrated through analytical models supported by experimental data/characteristics. Work achievement (documented Expression of the basic principles intended for use. Identification of potential applications. Formulation of potential applic

33、ations. Preliminary conceptual design of the element, providing understanding of how the basic principles would be used. Preliminary performance requirements (can target several missions including definition of functional performance requirements. Conceptual design of the element. Experimental data

34、inputs, laboratory-based experiment definition and results. Element analytical models for the proof-of-concept. TRL 4 - Component and/or breadboard functional verification in laboratory environment Element functional performance is demonstrated by breadboard testing in laboratory environment. Prelim

35、inary performance requirements (can target several missions with definition of functional performance requirements. Conceptual design of the element. Functional performance test plan. Breadboard definition for the functional performance verification. Breadboard test reports. TRL 5 - Component and/or

36、 breadboard critical function verification in a relevant environment Critical functions of the element are identified and the associated relevant environment is defined. Breadboards not full-scale are built for verifying the performance through testing in the relevant environment, subject to scaling

37、 effects. Preliminary definition of performance requirements and of the relevant environment. Identification and analysis of the element critical functions. Preliminary design of the element, supported by appropriate models for the critical functions verification. Critical function test plan. Analys

38、is of scaling effects. Breadboard definition for the critical function verification. Breadboard test reports. 11 ECSS-E-AS-11C 1 October 2014 Technology Readiness Level TRL 6: Model demonstrating the critical functions of the element in a relevant environment Milestone achieved for the element Criti

39、cal functions of the element are verified, performance is demonstrated in the relevant environment and representative model(s in form, fit and function. Work achievement (documented Definition of performance requirements and of the relevant environment. Identification and analysis of the element cri

40、tical functions. Design of the element, supported by appropriate models for the critical functions verification. Critical function test plan. Model definition for the critical function verifications. Model test reports. TRL 7: Model demonstrating the element performance for the operational environment Performance is demonstrated for the operational enviro

溫馨提示

  • 1. 本站所有資源如無(wú)特殊說(shuō)明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請(qǐng)下載最新的WinRAR軟件解壓。
  • 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請(qǐng)聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
  • 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁(yè)內(nèi)容里面會(huì)有圖紙預(yù)覽,若沒(méi)有圖紙預(yù)覽就沒(méi)有圖紙。
  • 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
  • 5. 人人文庫(kù)網(wǎng)僅提供信息存儲(chǔ)空間,僅對(duì)用戶上傳內(nèi)容的表現(xiàn)方式做保護(hù)處理,對(duì)用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對(duì)任何下載內(nèi)容負(fù)責(zé)。
  • 6. 下載文件中如有侵權(quán)或不適當(dāng)內(nèi)容,請(qǐng)與我們聯(lián)系,我們立即糾正。
  • 7. 本站不保證下載資源的準(zhǔn)確性、安全性和完整性, 同時(shí)也不承擔(dān)用戶因使用這些下載資源對(duì)自己和他人造成任何形式的傷害或損失。

最新文檔

評(píng)論

0/150

提交評(píng)論