ISO 17666:2016 PDF

Space systems — Risk management

Open preview (PDF)

Title (English):

ISO 17666:2016

Space systems — Risk management

Document status:: Withdrawn
Format:: Electronic (PDF)
Number of pages:: 20
Publication date:: November 14, 2016
Edition:: ISO IS 17666 edition 2 version 1
ICS:: 49.140

Delivery type:

Full version25 €Read online 24h10 €Read online 72h15 €

Document language:

enru

Delivery time:Immediate download

Price:25 €

Description (English):

ISO 17666:2016 defines, extending the requirements of ISO 14300‑1, 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). It contains a summary of the general risk management process, which is subdivided into four (4) basic steps and nine (9) tasks. The implementation can be tailored to project-specific conditions. 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 ISO 17666:2016 are all the space project phases. A definition of project phasing is given in ISO 14300‑1. When viewed from the perspective of a specific programme or project context, the requirements defined in ISO 17666:2016 are tailored to match the genuine requirements of a particular profile and circumstances of a programme or project.

Technical details

Technical committee: ISO/TC 20/SC 14 - Space systems and operations
SKU: ISO 17666:2016

Abstract

Overview

ISO 17666:2016 - Space systems - Risk management - defines principles and requirements for integrated risk management on space projects. Extending ISO 14300‑1, it prescribes a project-level approach usable by any actor in the customer–supplier chain (customer, prime, lower‑tier suppliers). The standard outlines a structured, iterative risk management process (4 basic steps, 9 tasks), requiring information exchange across all project domains and providing risk visibility and ranking by criticality throughout all project phases.

Key topics and requirements

Four-step risk management process: Establish implementation requirements, identify and assess risks, decide and act, then monitor, communicate, and accept risks. The process is iterative and tailored to project specifics.
Nine tasks embedded in the four steps, covering policy, planning, identification, assessment, mitigation, monitoring, and documentation.
Risk visibility and ranking: Risks must be tracked, ranked by criticality (risk index), and reported to support decision-making and resource trade-offs (cost, schedule, technical).
Roles and responsibilities: Project management holds overall responsibility; implementation requires corporate commitment and clear accountability down the organisation.
Documentation: Mandates a risk management policy, a risk management plan (DRD guidance included in Annex B), and maintained risk registers / ranked risk logs (examples in Annex A).
Tailoring: Requirements are adaptable to programme or project context - select or modify requirements to match project profile and constraints.
Integration: Encourages use of existing engineering analyses (safety, dependability, critical path, cost) as part of risk management.

Applications and practical use

ISO 17666 is practical for:

Space programme and project managers who need a consistent, auditable risk framework across a multi-tier supply chain.
Systems engineers and risk managers responsible for identifying, quantifying, and mitigating technical and programmatic risks (mass, power, schedule, cost, dependability, safety).
Suppliers and subcontractors implementing contract-level risk controls aligned to prime/customer risk policies.
Project control and decision boards requiring ranked risk information to prioritise resources and actions.

Practical outputs include a tailored risk management plan, maintained risk register and ranked risk log, documented risk decisions, and periodic risk‑management cycles tied to project milestones.

Related standards

ISO 14300‑1 - referenced for project phasing and baseline requirements (ISO 17666 extends its requirements).
ECSS (European Cooperation for Space Standardization) - commonly used in tandem for space project processes and engineering best practices.

Keywords: ISO 17666, space systems risk management, risk management process, space project risk, risk register, risk management plan.

Related standards

Mentioned in the description and other ISO standards

Abstract

Overview

Key topics and requirements

Four-step risk management process: Establish implementation requirements, identify and assess risks, decide and act, then monitor, communicate, and accept risks. The process is iterative and tailored to project specifics.
Nine tasks embedded in the four steps, covering policy, planning, identification, assessment, mitigation, monitoring, and documentation.
Risk visibility and ranking: Risks must be tracked, ranked by criticality (risk index), and reported to support decision-making and resource trade-offs (cost, schedule, technical).
Roles and responsibilities: Project management holds overall responsibility; implementation requires corporate commitment and clear accountability down the organisation.
Documentation: Mandates a risk management policy, a risk management plan (DRD guidance included in Annex B), and maintained risk registers / ranked risk logs (examples in Annex A).
Tailoring: Requirements are adaptable to programme or project context - select or modify requirements to match project profile and constraints.
Integration: Encourages use of existing engineering analyses (safety, dependability, critical path, cost) as part of risk management.

Applications and practical use

ISO 17666 is practical for:

Space programme and project managers who need a consistent, auditable risk framework across a multi-tier supply chain.
Systems engineers and risk managers responsible for identifying, quantifying, and mitigating technical and programmatic risks (mass, power, schedule, cost, dependability, safety).
Suppliers and subcontractors implementing contract-level risk controls aligned to prime/customer risk policies.
Project control and decision boards requiring ranked risk information to prioritise resources and actions.

Related standards

ISO 14300‑1 - referenced for project phasing and baseline requirements (ISO 17666 extends its requirements).
ECSS (European Cooperation for Space Standardization) - commonly used in tandem for space project processes and engineering best practices.

Keywords: ISO 17666, space systems risk management, risk management process, space project risk, risk register, risk management plan.

ISO 17666:2016 PDF

Technical details

Abstract

Overview

Key topics and requirements

Applications and practical use

Related standards

Related standards

Abstract

Overview

Key topics and requirements

Applications and practical use

Related standards

Related standards

Space systems — Programme management — Part 1: Structuring of a programme

Space systems — Risk management

Systems and software engineering — Software life cycle processes

Asset management — Vocabulary, overview and principles

Asset management — Asset management system — Requirements

Information technology — Radio frequency identification device conformance test methods — Part 2: Test method…

Information technology — Multimedia framework (MPEG-21) — Part 22: User Description

Milk — Determination of the lactoperoxidase activity — Photometric method (Reference method)