ISO 18676:2017
(Main)Space systems — Guidelines for the management of systems engineering
Space systems — Guidelines for the management of systems engineering
ISO 18676:2017 presents the guidelines for the management of systems engineering for space systems. ISO 18676:2017 addresses the systems engineering activities and provides guidelines for interfacing with specific major management subjects (e.g. configuration management, data management, interface management, risk management, requirements management, and integrated logistics support), which are themselves the subject of this document. ISO 18676:2017 establishes a common reference for all customers and suppliers in the space sector to work with management systems engineering for all space products and projects. These guidelines emphasize the following aspects of managing space systems engineering: - the positioning of space systems engineering activities related to the management of space activities; - the framework for the management of systems engineering; - the systems engineering management plan (SEMP); - the system, product and work breakdown structures; - the phasing, scheduling and recursivity of the systems engineering management; - reviews, audits and control gates; - the main activities of systems engineering and the respective management approach. ISO 18676:2017 is not the scope of this document to describe in detail the standard systems engineering process or project management process for all types of space systems.
Systèmes spatiaux — Lignes directrices pour le management de l'ingénierie système
General Information
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 18676
First edition
2017-11
Space systems — Guidelines for the
management of systems engineering
Systèmes spatiaux — Lignes directrices pour le management de
l'ingénierie système
Reference number
ISO 18676:2017(E)
©
ISO 2017
---------------------- Page: 1 ----------------------
ISO 18676:2017(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO 2017, Published in Switzerland
All 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 from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO 2017 – All rights reserved
---------------------- Page: 2 ----------------------
ISO 18676:2017(E)
Contents Page
Foreword .iv
Introduction .v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions . 1
4 Positioning of systems engineering management . 2
4.1 General . 2
4.2 Need for systems engineering management . 3
4.3 Systems engineering . 3
4.4 Systems engineering management . 4
4.5 Systems engineering management relative to the mission/programme/project . 4
5 Management of the systems engineering activities . 5
5.1 General . 5
5.2 Planning . 5
5.3 Assessment . 6
5.4 Trade-offs and decision making . 6
5.5 Control . 6
6 Systems engineering management plan (SEMP) . 7
7 Systems engineering management activities. 7
7.1 Management of stakeholder requirements analysis . 7
7.2 Management of system requirements analysis . 7
7.3 Management of architectural design . 8
7.4 Management of detailed design . 8
7.5 Management of assembly, integration and verification . 8
7.6 Management of validation . 9
8 Work breakdown structures (WBS) . 9
9 Phasing, scheduling and recursivity .10
10 Budgeting and resource planning .10
11 Status reporting and assessment .11
11.1 General .11
11.2 Cost assessments .11
11.3 Scheduling assessments .11
11.4 Performance assessments .12
11.5 Risk assessments.12
12 Reviews, audits and control gates.12
12.1 General .12
12.2 Review .13
12.3 Review list .13
12.4 Audits .14
12.5 Control gates .15
13 Interfaces management with SE .15
13.1 General .15
13.2 Acquisition and supply interface management .15
13.3 Implementation interface management .15
Bibliography .17
© ISO 2017 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO 18676:2017(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards
bodies (ISO member bodies). The work of preparing 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 liaison 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 Directives, 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 some 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 declarations 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 assessment, as well as information about ISO's 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 14, Space systems and operations.
iv © ISO 2017 – All rights reserved
---------------------- Page: 4 ----------------------
ISO 18676:2017(E)
Introduction
There is general consensus that to accomplish space programme/project requirements, it is mandatory
to manage the systems engineering activities. The main role of systems engineering management is
to ensure system performance conforms with expressed need, and to control the technical risks
involved in development. Also, cost and schedule parameters are taken into account in space systems
engineering in the search of optimal performance.
Thus, this document provides guidelines for managing the systems engineering activities related to
planning, assessment and control of space programmes/projects.
These guidelines are intended to identify a set of recommendations to help customers and space system
organizations to establish management requirements for systems engineering activities and help the
organization to construct the elements of the systems engineering management plan (SEMP).
Given the need for systems engineering management, the overall systems engineering activities can be
divided into two types:
— systems engineering management activities related to programme management which comprise
planning, assessing, controlling, trade-off studies and decision making;
— the technical activities themselves, linked to the technical processes (stakeholder requirements
analysis, system requirements analysis, system architectural design, system detailed design and
assembly, integration, and verification and validation) applied to the system.
Therefore, systems engineering management reinforces the technical viewpoint within programme
management.
In these guidelines, a set of leading indicators are suggested as measures for evaluating the
effectiveness of each space systems engineering activity. Leading indicators are important tools for
project management to make interventions and actions to avoid rework and wasted effort during the
whole system engineering life cycle.
© ISO 2017 – All rights reserved v
---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO 18676:2017(E)
Space systems — Guidelines for the management of
systems engineering
1 Scope
This document presents the guidelines for the management of systems engineering for space systems.
This document addresses the systems engineering activities and provides guidelines for interfacing
with specific major management subjects (e.g. configuration management, data management, interface
management, risk management, requirements management, and integrated logistics support), which
are themselves the subject of this document.
This document establishes a common reference for all customers and suppliers in the space sector to
work with management systems engineering for all space products and projects.
These guidelines emphasize the following aspects of managing space systems engineering:
— the positioning of space systems engineering activities related to the management of space activities;
— the framework for the management of systems engineering;
— the systems engineering management plan (SEMP);
— the system, product and work breakdown structures;
— the phasing, scheduling and recursivity of the systems engineering management;
— reviews, audits and control gates;
— the main activities of systems engineering and the respective management approach.
It is not the scope of this document to describe in detail the standard systems engineering process or
project management process for all types of space systems.
2 Normative references
There are no normative references in this document.
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
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
3.1
management
coordinated activities to direct and control an organization (3.2)
[SOURCE: ISO 9000:2015, 3.3.3]
© ISO 2017 – All rights reserved 1
---------------------- Page: 6 ----------------------
ISO 18676:2017(E)
3.2
organization
person or group of people that has its own functions with responsibilities, authorities and relationships
to achieve its objectives
[SOURCE: ISO 9000:2015, 3.2.1]
3.3
programme
group of projects (3.5) managed in a coordinated way to obtain benefits not available from managing
them individually
[SOURCE: ISO 10795:2011, 1.166]
3.4
process
set of interrelated or interacting activities that use inputs to deliver an intended result
[SOURCE: ISO 9000:2015, 3.4.1]
3.5
project
unique process (3.4), consisting of a set of coordinated and controlled activities with start and
finish dates, undertaken to achieve an objective conforming to specific requirements, including the
constraints of time, cost and resources
[SOURCE: ISO 9000:2015, 3.4.2]
3.6
system
set of interrelated or interacting elements
3.7
systems engineering
interdisciplinary approach governing the total technical and managerial effort required to transform
a set of stakeholder needs, expectations and constraints into a solution and to support that solution
throughout its life
[SOURCE: ISO 24748-1:2016, 2.56]
3.8
systems engineering management
discipline to ensure that system engineering (3.7) is properly applied and can be divided in planning,
control, assessment and decision analysis, including management tools like work breakdown structures,
risk management, requirements traceability and reviews
3.9
stakeholder
customers and/or users or those who will receive the goods or services and are the direct beneficiaries
of the systems (3.6) or other interested parties who affect or are affected by the project (3.5), providing
overarching constraints within which the customers' needs should be achieved
4 Positioning of systems engineering management
4.1 General
This clause aims to justify the space systems engineering management activity in relation to the
management of design and manufacturing engineering activities, in relation to project management
and in relation to the mission/programme/project.
2 © ISO 2017 – All rights reserved
---------------------- Page: 7 ----------------------
ISO 18676:2017(E)
4.2 Need for systems engineering management
This subclause highlights what is special in systems engineering that requires management.
The main aspects to be approached are:
a) requirements not known beforehand but continuously engineered by the systems engineering
process;
b) complexity of the elements in the environment, material, information and energy, that exchange
with the system;
c) quantity and variety of stakeholders, requirements, concepts, functionalities, technologies,
suppliers, contracts and life cycle process implementation organizations;
d) iterative nature of the systems engineering process from requirements until the convergence to a
system solution;
e) recursive nature of the systems engineering process applicable to systems but also to subsystems
in the various layers of the system breakdown structure;
f) risk management when verification activity cannot be exhaustive.
4.3 Systems engineering
Systems engineering provides the identification and understanding of a need and derives, develops and
verifies a solution that will be balanced during the space system life cycle in order to meet that need.
Systems engineering balances the satisfaction of all stakeholders involved in the solution life. Figure 1
presents the V-Model and its set of systems engineering processes in the classical life cycle stages.
The term systems engineering process describes the activities used to transform requirements in an
effective product. These activities enable systems engineers to coordinate the interaction between
engineers, other specialists, stakeholders, operators, and manufacturing.
The classical space systems life cycle is divided into stages, and each stage contains systems engineering
processes. The concept stage includes the concept of the operations process; the development stage
includes the requirements and architecture analysis processes, and detailed design process; the
production stage includes the synthesis process, assembly, integration and verification process, and
system validation process; and the utilization stage includes the operations and maintenance processes.
© ISO 2017 – All rights reserved 3
---------------------- Page: 8 ----------------------
ISO 18676:2017(E)
Figure 1 — Systems engineering V model
Systems engineering is concerned with the delivery of a technical solution that meets stakeholder
needs and provides a set of baseline requirements to be used as a reference for project management.
Project management uses these references provided by systems engineering to compare what is being
implemented to what has been planned.
Project management is responsible for the project organization, and other aspects of the project,
such as, cost, schedules, human resources, communication, programmatic risk, acquisition strategy,
sustainment and external interfaces.
4.4 Systems engineering management
The systems engineering process is managed from the time of need identification to a verified and
validated solution. Also, systems engineering management includes configuration management, data
management, technical risk management, and interface management.
4.5 Systems engineering management relative to the mission/programme/project
Systems engineering management is part of the mission/programme/project, and interacts with other
management disciplines within the mission/programme/project activities.
Figure 2 presents the position of programme management related to systems engineering activities.
The programme management circle consists of the management tasks including planning, assessment
of progress, control actions and trade-offs and decision making to correct the course of the project.
The systems engineering circle is related to the main activities of systems engineering process, such as
stakeholder requirements analysis, system requirements analysis, system architectural design, system
detailed design, assembly and integration, and verification and validation. The intersection circle
corresponds to the interaction between management tasks and the systems engineering activities
required to accomplish the mission/programme/project.
4 © ISO 2017 – All rights reserved
---------------------- Page: 9 ----------------------
ISO 18676:2017(E)
Figure 2 — Position of programme management related to system engineering activities
5 Management of the systems engineering activities
5.1 General
The objective of the management of systems engineering activities is to achieve the required outputs
of the space system project. This management covers the task planning, assessment, control, trade-
offs, and decision making applied to assure the correct management of the project in all phases of the
systems engineering process.
5.2 Planning
Planning refers to the identification of the activities to be performed, their appropriate sequence and
resources needed for their accomplishment. This task consists of preparing the necessary technical
plans and complementary project planning information used to support the mission and the systems
engineering activities, and should include the following.
a) Implementation strategy: Define a strategy for implementing the mission/programme/ project and
the systems engineering activities as a basis for project technical planning;
b) Technical effort: Describe what will be accomplished, how systems engineering will be done, what
resources are needed and how the systems engineering effort will be monitored and controlled in
accordance with the implementation strategy;
c) Schedule and organization: Define how the technical effort will be scheduled and organized;
© ISO 2017 – All rights reserved 5
---------------------- Page: 10 ----------------------
ISO 18676:2017(E)
d) Work directives: Create work directives that implement the technical effort.
5.3 Assessment
Assessment refers to the evaluation of the project’s progress along the planned activities of the systems
engineering process. This task consists of determining progress of the technical effort against the
mission/programme/project planning and the systems engineering activities. This assessment should
be used to determine:
a) definition of the progress and outcome metrics to be used;
b) progress against plans and schedules: assess the progress of the technical effort against the
accomplishments of the systems engineering activities;
c) progress against systems engineering activities: assess the progress of the system development
by comparing mission/programme/project required results against the outcomes of the systems
engineering activities;
d) technical reviews: use technical reviews to evaluate the progress and accomplishments in
accordance with the appropriate technical plans.
Leading indicators (LIs) can be used to evaluate the effectiveness of specific space systems engineering
activities to provide information about impacts that are likely to affect the space programme/project
performance objectives. LIs can be associated with system attributes, such as, process milestone,
phases, disposition actions (opened, started, approved, incorporated, rejected, stopped, closed,
overdue), maturity states (planned, interim, actual), priority levels (critical, high, medium, low), causal
states (error, customer request, external), impact levels (high, medium, low), classification type and
dates/times.
5.4 Trade-offs and decision making
Trade-offs and decision making refers to recommendations and predictions of the results of the
alternative decisions. This task consists of performing trade-off analyses to provide decision makers
with recommendations, predictions of the results of alternative decisions and other appropriate
information to allow selection of the best course of action. This task should include:
a) identifying the alternatives;
b) planning the trade-off analysis: plan the availability of required resources, execution and data
collection requirements, expected outcomes, defined conditions (triggers and rigor), level of
importance, objective, schedule of tasks, selection criteria that will determine desirability
or undesirability of an alternative, weighting factors for each selection criterion, models
(representative or simulation) to be used in the trade-off analysis, and options to be analysed;
c) performing the trade-off analysis: do appropriate effectiveness analysis activities to provide a
quantitative basis for evaluating options, risk analysis activities to quantitatively or qualitatively
assess the risk associated with each option; collect and analyse data to determine the cost, schedule,
performance and risk effect of each option on the system; evaluate options against selection
criteria and weighting factors and identify and define recommendations and communicate
recommendations and impacts to appropriate decision makers;
d) recording outcomes: record the analysis in the information database, including assumptions, details
of the analysis, lessons learned, models used, rationale for decisions made, recommendations and
effects and other pertinent information affecting the interpretation of the decisions made.
5.5 Control
Control refers to the actions to be taken in order to keep the planned activities according to plan, to
correct the course of activities needed to be brought back in line with the plan or to correct the plan.
The control task is used to manage the conduct and the outcomes of the mission, to monitor variations
6 © ISO 2017 – All rights reserved
---------------------- Page: 11 ----------------------
ISO 18676:2017(E)
from the plan, and to prevent anomalies relative to the systems engineering activities, and to ensure
necessary communications are successful. This activity should support:
a) preventive actions: when assessments indicate a trend toward deviation of progress and outcomes;
b) problem resolution: when assessments indicate non-conformance with the outcome metrics, such
as, the performance of systems engineering activities that lead to expected results outside the
bounds of the success criteria;
c) information dissemination: ensure that required and requested information is disseminated in
accordance with the project plans and organization policies.
6 Systems engineering management plan (SEMP)
The SEMP describes how the project will be technically managed. The SEMP is the document that
defines to all project participants how the project will be technically.
The SEMP identifies what, when, where, by whom and how the activities are performed. It specifies
the schedule for the development and the resources required. It is an implementation plan for the
management of the performance of systems engineering activities and the development of systems
engineering products. The SEMP should be aligned with the customer’s Systems Engineering Plan (SEP).
Each project should prepare an SEMP that addresses the requirements of this document and describes
the what, when, where, by whom, and how each is to be implemented.
The SEMP should include:
a) an organization structure along with responsibilities for the systems engineering team;
b) the major trades identified;
c) a schedule and list of resources required for the systems engineering effort.
7 Systems engineering management activities
7.1 Management of stakeholder requirements analysis
The purpose of this activity is to manage the mission and the stakeholder requirements analysis in
order to achieve the expected outputs in the space system project. This management activity covers
the identification of planning, assessment and control tasks to ensure the mission and stakeholder
requirements analysis process.
It assesses whether the stakeholder requirements meet the expectations of the layout of the mission,
the
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.