ISO 16192:2017 pdf download

ISO 16192:2017 pdf download.Space systems — Experience gained in space projects (lessons learned) — Principles and guidelines
1 Scope
This document outlines lessons learned principles and guidelines that are applicable in all space project activities (management, technical, quality, cost 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 organization, 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, principles 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 outlined 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 suggested lessons learned forms.
2 Normative references
There are no normative references in this document.
3 Terms and definitions .
No terms and definitions are listed in this document.
ISO and IEC maintain terminological databases for use in standardization at the following addresses: .
– IEC Electropedia: available at http://www.electropedia.org/
– ISO Online browsing platform: available at http://www.iso.org/obp
6.3 Description of lessons learned process steps
6.3.1 Data and information collection
The 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 be transmitted to external . entities in a lessons learned process.
6.3.2 Selection of the lessons learned cases
Not 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 occurrences, experiences or events, and to translate them into proposed lessons learned. .
6.3.3 Validation and acceptance of the selected lessons learned
The lessons learned cases or events to be recorded in the database should be reviewed, validated and accepted (approved]) by a defined method, i.e. by 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.