EN 16601-80:2014
(Main)Space project management - Part 80: Risk management
Space project management - Part 80: Risk management
This Standard defines the principles and requirements for integrated risk management on a space project; it explains what is needed to implement a project-integrated risk management policy by any project actor, at any level (i.e. customer, first level supplier, or lower level suppliers).
This Standard contains a summary of the general risk management process, which is subdivided into four (4) basic steps and nine (9) tasks.
The risk management process requires information exchange among all project domains, and provides visibility over risks, with a ranking according to their criticality for the project; these risks are monitored and controlled according to the rules defined for the domains to which they belong.
The fields of application of this Standard are all the activities of all the space project phases. A definition of project phasing is given in ECSS-M-ST-10.
This standard may be tailored for the specific characteristics and constraints of a space project in conformance with ECSS-S-ST-00.
Raumfahrt-Projektmanagement - Teil 80: Risikomanagement
Diese Norm legt die Grundsätze für und Anforderungen an das integrierte Risikomanagement für ein Raumfahrtprojekt fest; sie erläutert, was zur Umsetzung einer projektintegrierten Risikomanagementpolitik von jedem Projektbeteiligten auf allen Ebenen (d. h. den Kunden, Lieferanten oder Zulieferern der ersten Ebene oder den Lieferanten der unteren Ebene) verlangt wird.
Diese Norm enthält eine Zusammenfassung aller Elemente des Risikomanagementprozesses, der in vier (4) Schritte und neun (9) Aufgaben unterteilt wird.
Der Risikomanagementprozess erfordert den Informationsaustausch zwischen sämtlichen Projektbereichen und liefert eine Übersicht über die Risiken, die entsprechend ihrer Kritikalität für das Projekt eingestuft werden; diese Risiken sind nach den Regeln zu überwachen und zu steuern, die für den jeweiligen Bereich festgelegt sind.
Der Anwendungsbereich dieser Norm erstreckt sich auf sämtliche Aktivitäten in allen Phasen von Raumfahrtprojekten. Eine Definition von Projektphasen findet sich in ECSS-M-ST-10.
Diese Norm darf auf die speziellen Merkmale und Vorgaben eines Raumfahrtprojektes nach ECSS M ST 00 ausgelegt werden.
Systèmes spatiaux - Management des risques
Vodenje vesoljskih projektov - 80. del: Obvladovanje tveganja
Standard EN 16601-80 določa načela in zahteve za celostno obvladovanje tveganja pri vesoljskem projektu; pojasnjuje, kaj je pri projektu potrebno za izvajanje politike celostnega upravljanja s tveganjem s strani vseh udeleženih v projektu na kateri koli ravni (tj. stranka, dobavitelj prve ravni, dobavitelji nižjih ravni). Ta standard vsebuje povzetek splošnega postopka za obvladovanje tveganja, ki je razdeljen na štiri (4) osnovne korake in devet (9) nalog. Postopek za obvladovanje tveganja zahteva izmenjavo informacij med vsemi projektnimi področji in zagotavlja prepoznavo tveganj z razvrstitvijo glede na njihovo pomembnost za projekt; ta tveganja se spremlja in nadzira v skladu s pravili, ki so določena za področja, ki jim pripadajo. Področje veljavnosti tega standarda so vse dejavnosti vseh faz vesoljskih projektov. Opredelitev razdelitve projektnih faz je navedena v standardu ECSS-M-ST-10. Ta standard se lahko prilagodi posameznim lastnostim in omejitvam vesoljskega projekta v skladu s standardom ECSS-S-ST-00.
General Information
Relations
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Vodenje vesoljskih projektov - 80. del: Obvladovanje tveganjaRaumfahrt-Projektmanagement - Teil 80: RisikomanagementManagement des projets spatiaux - Partie 80: Management des risquesSpace project management - Part 80: Risk management49.140Vesoljski sistemi in operacijeSpace systems and operations03.100.40Raziskave in razvojResearch and developmentICS:Ta slovenski standard je istoveten z:EN 16601-80:2014SIST EN 16601-80:2014en,fr,de01-november-2014SIST EN 16601-80:2014SLOVENSKI
STANDARDSIST EN ISO 17666:20041DGRPHãþD
EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM
EN 16601-80
August 2014 ICS 49.140 Supersedes EN ISO 17666:2003
English version
Space project management - Part 80: Risk management
Systèmes spatiaux - Partie 80: Management des risques
Raumfahrtsysteme - Teil 80: Risikomanagement This European Standard was approved by CEN on 14 December 2013.
CEN and CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN and CENELEC member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by translation under the responsibility of a CEN and CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the same status as the official versions.
CEN and CENELEC members are the national standards bodies and national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom.
CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels © 2014 CEN/CENELEC All rights of exploitation in any form and by any means reserved worldwide for CEN national Members and for CENELEC Members. Ref. No. EN 16601-80:2014 E SIST EN 16601-80:2014
2 Table of contents Foreword . 4 Introduction . 5 1 Scope . 6 2 Normative references . 7 3 Terms, definitions and abbreviated terms . 8 3.1 Terms from other standards . 8 3.2 Terms specific to the present standard . 8 3.3 Abbreviated terms. 9 4 Principles of risk management . 10 4.1 Risk management concept . 10 4.2 Risk management process . 10 4.3 Risk management implementation in a project . 10 4.4 Risk management documentation . 11 5 The risk management process . 12 5.1 Overview of the risk management process . 12 5.2 Risk management steps and tasks . 14 6 Risk management implementation . 21 6.1 General considerations . 21 6.2 Responsibilities . 21 6.3 Project life cycle considerations . 22 6.4 Risk visibility and decision making . 22 6.5 Documentation of risk management . 22 7 Risk management requirements . 24 7.1 General . 24 7.2 Risk management process requirements . 24 7.3 Risk management implementation requirements . 27 Annex A (normative) Risk management policy document - DRD . 29 SIST EN 16601-80:2014
A.1 DRD identification . 29 A.2 Expected response . 29 Annex B (normative) Risk management plan - DRD . 32 B.1 DRD identification . 32 B.2 Expected response . 32 Annex C (normative) Risk assessment report - DRD . 35 C.1 DRD identification . 35 C.2 Expected response . 35 Annex D (informative) Risk register example and ranked risk log example . 37 Annex E (informative) Contribution of ECSS Standards to the risk management process . 40 E.1 General . 40 E.2 ECSS-M ST-Standards . 40 E.3 ECSS-Q Standards . 40 E.4 ECSS-E Standards . 41 Bibliography . 42
Figures Figure 5-1: The steps and cycles in the risk management process . 13 Figure 5-2: The tasks associated with the steps of the risk management process within the risk management cycle . 13 Figure 5-3: Example of a severity–of–consequence scoring scheme . 14 Figure 5-4: Example of a likelihood scoring scheme . 15 Figure 5-5: Example of risk index and magnitude scheme . 16 Figure 5-6: Example of risk magnitude designations and proposed actions for individual risks . 16 Figure 5-7: Example of a risk trend . 20
4 Foreword This document (EN 16601-80:2014) has been prepared by Technical Committee CEN/CLC/TC 5 “Space”, the secretariat of which is held by DIN. This standard (EN16601-80:2014) originates from ECSS-M-ST-80C. This European Standard shall be given the status of a national standard, either by publication of an identical text or by endorsement, at the latest by February 2015, and conflicting national standards shall be withdrawn at the latest by February 2015. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. CEN [and/or CENELEC] shall not be held responsible for identifying any or all such patent rights. This document supersedes EN ISO 17666:2003. This document has been developed to cover specifically space systems and has therefore precedence over any EN covering the same scope but with a wider domain of applicability (e.g. : aerospace). According to the CEN-CENELEC Internal Regulations, the national standards organizations of the following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. SIST EN 16601-80:2014
Introduction Risks are a threat to project success because they have negative effects on the project cost, schedule and technical performance, but appropriate practices of controlling risks can also present new opportunities with positive impact. The objective of project risk management is to identify, assess, reduce, accept, and control space project risks in a systematic, proactive, comprehensive and cost effective manner, taking into account the project’s technical and programmatic constraints. Risk is considered tradable against the conventional known project resources within the management, programmatic (e.g. cost, schedule) and technical (e.g. mass, power, dependability, safety) domains. The overall risk management in a project is an iterative process throughout the project life cycle, with iterations being determined by the project progress through the different project phases, and by changes to a given project baseline influencing project resources.
Risk management is implemented at each level of the customer-supplier network. Known project practices for dealing with project risks, such as system and engineering analyses, analyses of safety, critical items, dependability, critical path, and cost, are an integral part of project risk management. Ranking of risks according to their criticality for project success, allowing management attention to be directed to the essential issues, is a major objective of risk management. The project actors agree on the extent of the risk management to be implemented in a given project depending on the project definition and characterization. SIST EN 16601-80:2014
6 1 Scope This Standard defines the principles and requirements for integrated risk management on a space project; it explains what is needed to implement a project–integrated risk management policy by any project actor, at any level (i.e. customer, first level supplier, or lower level suppliers). This Standard contains a summary of the general risk management process, which is subdivided into four (4) basic steps and nine (9) tasks.
The risk management process requires information exchange among all project domains, and provides visibility over risks, with a ranking according to their criticality for the project; these risks are monitored and controlled according to the rules defined for the domains to which they belong. The fields of application of this Standard are all the activities of all the space project phases. A definition of project phasing is given in ECSS-M-ST-10. This standard may be tailored for the specific characteristics and constraints of a space project in conformance with ECSS-S-ST-00.
2 Normative references The following normative documents contain provisions which, through reference in this text, constitute provisions of this ECSS Standard. For dated references, subsequent amendments to, or revisions of any of these publications do not apply. However, parties to agreements based on this ECSS Standard are encouraged to investigate the possibility of applying the most recent editions of the normative documents indicated below. For undated references the latest edition of the publication referred to applies.
EN reference Reference in text Title EN 16601-00-01 ECSS-ST-00-01 ECSS system - Glossary of terms EN 16601-10 ECSS-M-ST-10 Space project management – Project planning and implementation SIST EN 16601-80:2014
8 3 Terms, definitions and abbreviated terms 3.1 Terms from other standards For the purpose of this Standard, the terms and definitions from ECSS-ST-00-01 apply, in particular for the following terms: risk residual risk risk management risk management policy 3.2 Terms specific to the present standard 3.2.1 acceptance of (risk) decision to cope with consequences, should a risk scenario materialize NOTE 1 A risk can be accepted when its magnitude is less than a given threshold, defined in the risk management policy. NOTE 2 In the context of risk management, acceptance can mean that even though a risk is not eliminated, its existence and magnitude are acknowledged and tolerated. 3.2.2 (risk) communication all information and data necessary for risk management addressed to a decision–maker and to relevant actors within the project hierarchy 3.2.3 (risk) index score used to measure the magnitude of the risk; it is a combination of the likelihood of occurrence and the severity of consequence, where scores are used to measure likelihood and severity 3.2.4 individual (risk) risk identified, assessed, and mitigated as a distinct risk items in a project SIST EN 16601-80:2014
3.2.5 (risk) management process consists of all the project activities related to the identification, assessment, reduction, acceptance, and feedback of risks 3.2.6 overall (risk) risk resulting from the assessment of the combination of individual risks and their impact on each other, in the context of the whole project NOTE
Overall risk can be expresse
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.