BS ISO 16192-2017 Space systems Experience gained in space projects (lessons learned) Principles and guidelines《航空航天系统 空间计划中的经验获取(经验学习) 原理和指南》.pdf

《BS ISO 16192-2017 Space systems Experience gained in space projects (lessons learned) Principles and guidelines《航空航天系统 空间计划中的经验获取(经验学习) 原理和指南》.pdf》由会员分享，可在线阅读，更多相关《BS ISO 16192-2017 Space systems Experience gained in space projects (lessons learned) Principles and guidelines《航空航天系统 空间计划中的经验获取(经验学习) 原理和指南》.pdf（24页珍藏版）》请在麦多课文档分享上搜索。

1、Space systems Experience gained in space projects (lessons learned) Principles and guidelinesBS ISO 16192:2017BSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06National forewordThis British Standard is the UK implementation of ISO 16192:2017. It supersedes BS ISO 16192

2、:2010, which is withdrawn.The UK participation in its preparation was entrusted to Technical Committee ACE/68, Space systems and operations.A list of organizations represented on this committee can be obtained on request to its secretary.This publication does not purport to include all the necessary

3、 provisions of a contract. Users are responsible for its correct application. The British Standards Institution 2017 Published by BSI Standards Limited 2017ISBN 978 0 580 93306 6ICS 49.020; 49.140Compliance with a British Standard cannot confer immunity from legal obligations.This British Standard w

4、as published under the authority of the Standards Policy and Strategy Committee on 30 April 2017.Amendments/corrigenda issued since publicationDate Text affectedBRITISH STANDARDBS ISO 16192:2017 ISO 2017Space systems Experience gained in space projects (lessons learned) Principles and guidelinesSyst

5、mes spatiaux valuation de la connaissance pratique Principes et lignes directricesINTERNATIONAL STANDARDISO16192Second edition2017-04-01Reference numberISO 16192:2017(E)BS ISO 16192:2017ISO 16192:2017(E)ii ISO 2017 All rights reservedCOPYRIGHT PROTECTED DOCUMENT ISO 2017, Published in SwitzerlandAll

6、 rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested fr

7、om either ISO at the address below or ISOs member body in the country of the requester.ISO copyright officeCh. de Blandonnet 8 CP 401CH-1214 Vernier, Geneva, SwitzerlandTel. +41 22 749 01 11Fax +41 22 749 09 47copyrightiso.orgwww.iso.orgBS ISO 16192:2017ISO 16192:2017(E)Foreword ivIntroduction v1 Sc

8、ope . 12 Normative references 13 Terms and definitions . 14 The role of a lessons learned activity . 24.1 Role 24.2 Information availability . 25 Lessons learned management 25.1 The main applications of the lessons learned 25.2 Information sources for the lessons learned 36 The lessons learned proce

9、ss 36.1 General . 36.2 Process steps 46.3 Description of lessons learned process steps . 66.3.1 Data and information collection . 66.3.2 Selection of the lessons learned cases . 66.3.3 Validation and acceptance of the selected lessons learned 66.3.4 Classification of the selected lessons learned . 6

10、6.3.5 Recording of the selected cases 66.3.6 Recommendation of applicable lessons learned to a new project 66.3.7 Measurement or assessment of the results of the lessons learned process . 67 Content of the lessons learned record . 77.1 General . 77.2 Detailed content . 77.2.1 General 77.2.2 Backgrou

11、nd of the root event . 77.2.3 The lessons learned . 77.2.4 Resulting recommendations and actions . 78 Lessons learned implementation . 78.1 General . 78.2 Application . 88.3 Responsibility 89 Effectiveness of the lessons learned process 8Annex A (informative) Generic lessons learned forms 9Annex B (

12、informative) Short lessons learned form 12Bibliography .13 ISO 2017 All rights reserved iiiContents PageBS ISO 16192:2017ISO 16192:2017(E)ForewordISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing

13、 International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liais

14、on with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Direc

15、tives, Part 1. In particular the different approval criteria needed for the different types of ISO documents should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).Attention is drawn to the possibility that som

16、e of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document will be in the Introduction and/or on the ISO list of patent declara

17、tions received (see www.iso.org/patents).Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement.For an explanation on the voluntary nature of standards, the meaning of ISO specific terms and expressions related to conformity asse

18、ssment, as well as information about ISOs adherence to the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT) see the following URL: www.iso.org/iso/foreword.html.This document was prepared by Technical Committee ISO/TC 20, Aircraft and space vehicles, Subcommittee SC

19、 14, Space systems and operations.This second edition cancels and replaces the first edition (ISO 16192:2010), which has been technically revised.The main changes compared to the previous edition are as follows: information previously in Clause 2 (role of lessons learned) and Clause 4 (the lessons l

20、earned process) has been reorganised and rewritten to eliminate duplication and inconsistent text; and information describing the lessons learned process which was previously in Annex A has been removed and combined with similar information in Clause 4 to further simplify the text in Clause 4.iv ISO

21、 2017 All rights reservedBS ISO 16192:2017ISO 16192:2017(E)IntroductionIn order to improve the quality of products and to work efficiently, it is important to consider past experiences and how the knowledge of those experiences is transmitted. The aim is to decrease errors (in terms of both quantity

22、 and gravity), improve working methods and decrease risks of nonconformity to specified objectives (management, technical, quality, costs and schedules).In the process of lessons learned, future space projects or programmes are intended to draw benefit from past experience, by capturing and communic

23、ating knowledge from the past through recording, classifying and making the information available.An efficient processing of lessons learned is considered essential for: ongoing efficiency and quality improvement inside any organization; successful project management. ISO 2017 All rights reserved vB

24、S ISO 16192:2017This page deliberately left blankSpace systems Experience gained in space projects (lessons learned) Principles and guidelines1 ScopeThis document outlines lessons learned principles and guidelines that are applicable in all space project activities (management, technical, quality, c

25、ost and schedule).The application of this document is intended to be included in the supplier quality management system, but can be tailored in individual contracts as agreed by the customer and supplier, depending on: the content of each project (size, technological level and novelty, particular or

26、ganization, participants, etc.); the interest and usefulness of the related information.The lessons learned information can result from any situation which might be encountered in similar contexts for future projects, i.e.: undesirable experiences that need to be avoided; strategies, rules, principl

27、es of design, validation, tests and operations that proved to be successful or necessary.This document neither endorses nor recommends the transmission of company proprietary information to external entities as part of a lessons learned process.Implementing a formal lessons learned process as outlin

28、ed in this document makes it possible to capture and benefit from this information.The lessons learned activity is an important contribution to the processing of the preventive and corrective actions specified in ISO 9001 and ISO 17666.This document also provides lessons learned processes and sugges

29、ted lessons learned forms.2 Normative referencesThere are no normative references in this document.3 Terms and definitionsNo terms and definitions are listed in this document.ISO and IEC maintain terminological databases for use in standardization at the following addresses: IEC Electropedia: availa

30、ble at http:/www.electropedia.org/ ISO Online browsing platform: available at http:/www.iso.org/obpINTERNATIONAL STANDARD ISO 16192:2017(E) ISO 2017 All rights reserved 1BS ISO 16192:2017ISO 16192:2017(E)4 The role of a lessons learned activity4.1 RoleThe role of a lessons learned activity is to ens

31、ure that projects benefit from the experiences good and bad of previous projects. The main activities involved in the process are:a) to identify and collect relevant information;b) to analyse information, classify lessons learned and issue recommendations;c) to document the process;d) to make inform

32、ation available.The outputs of the activity are: root event background; lessons learned; recommendations.The steps involved in the lessons learned process are described in detail in Clause 6.4.2 Information availabilityInformation should be made available, as necessary, by referring to a collection

33、of data and by consulting a shared database. External provision of data should be in accordance with agreements between the customer and supplier. This database should include any information considered by the participants to be useful for ongoing or future project activities.The database should be

34、searchable by domain, type of project, period and type of anomaly.Information may also be made available by means of more “active” ways of knowledge transfer, such as a debriefing or presentation of lessons learned to interested personnel (e.g. within the company) or the presentation of lessons lear

35、ned to relevant project teams (e.g. within the company).5 Lessons learned management5.1 The main applications of the lessons learnedLessons learned should be systematically applied in the following situations:a) before the start of a space project;EXAMPLE Information about costs and duration, techni

36、cal performance and quality of previous projects are made available to a new project.b) transition from one phase to another phase;EXAMPLE The lesson learned during phase B (definition phase) or phase C (development phase) is that a qualification of an advanced technology is followed by specific ins

37、pection during manufacturing.c) when the results from one project could benefit another coexisting project;EXAMPLE The lessons learned from analysis of a component in a given project is directly beneficial to another project.d) when the knowledge of one field can benefit another.2 ISO 2017 All right

38、s reservedBS ISO 16192:2017ISO 16192:2017(E)EXAMPLE The lessons learned from analysis of defects or failures during integration and test results in improvement of the specifications of a contract.5.2 Information sources for the lessons learnedThe search for useful information is an essential step to

39、 developing lessons learned.Suggested sources of useful information include the following: opinions of specialists and experts; documented conclusions of specialists and experts; technical reports, actions and recommendations resulting from reviews; non-conformance reports; failure analysis reports;

40、 assessments of success in meeting project objectives (at the end of a project); documented results of operation of models of space engineering, or results of space mission, or both; feedback from customers; alerts; accidents, mishaps, incidents and close calls; and risk assessments.6 The lessons le

41、arned process6.1 GeneralThe lessons learned process is depicted in Figure 1. It comprises three phases with related outputs:a) the background of the experience, in which the following are described in detail: the report of the fact; the analyses which comprise the identification of the causes (possi

42、ble, probable and proven) and the consequences (immediate, future and potential); the resulting actions;b) lessons learned, which are lessons drawn from the experience;c) recommendations which are applicable to new projects (impact on documentation, impact on product). ISO 2017 All rights reserved 3

43、BS ISO 16192:2017ISO 16192:2017(E)Figure 1 Lessons learned process6.2 Process stepsThe lessons learned process is optimized by implementing a common methodology of definition, classification, description and registration.The three phases in the process each comprise one or more steps. These steps ar

44、e depicted in Figure 2 and described in 6.3.1 to 6.3.7.It should be noted that, whilst the process in Figure 2 is shown as a simple sequence, only steps 3 to 5 describe a totally sequential flow. Steps 1 and 2 are performed continuously throughout the life of a project and will trigger the steps tha

45、t follow. Step 6 is event triggered, and step 7 is scheduled or periodic.4 ISO 2017 All rights reservedBS ISO 16192:2017ISO 16192:2017(E)Figure 2 Steps of lessons learned process ISO 2017 All rights reserved 5BS ISO 16192:2017ISO 16192:2017(E)6.3 Description of lessons learned process steps6.3.1 Dat

46、a and information collectionThe lessons learned are established by identifying pertinent information acquired directly from positive and negative experiences relative to the organization and management of the content of each project. Company proprietary information should be collected but should not

47、 be transmitted to external entities in a lessons learned process.6.3.2 Selection of the lessons learned casesNot all the technical experiences, occurrences, or events during a project have the same interest or importance. It is necessary to analyse the data collected and select the most significant

48、 occurrences, experiences or events, and to translate them into proposed lessons learned.6.3.3 Validation and acceptance of the selected lessons learnedThe lessons learned cases or events to be recorded in the database should be reviewed, validated and accepted (approved) by a defined method, i.e. b

49、y a “lessons learned committee” or any similar organization. An assessment should be made as to the acceptability of the proposed case or event, prior to ruling on the lessons to be drawn and describing the actions needed to decrease the risk of occurrence of the problems.The responsibility for, and frequency of, examining potential lessons learned should be defined.6.3.4 Classification of the selected lessons learnedAfter acceptance, selected lessons learned should be classified by type using key w