EN 9320:2014

SLOVENSKI STANDARD
01-marec-2015
Aeronavtika - Vodenje programov - Splošne smernice za nabavo in dobavo/oskrbo
odprtih sistemov
Aerospace series - Programme Management - General guidelines for acquisition and
supply of open systems
Luft- und Raumfahrt - Programm-Management - Allgemeiner Leitfaden für Erwerb und
Lieferung von offenen Systemen
Série aérospatiale - Management de Programme - Recommandations générales pour
l’acquisition et la fourniture de systèmes ouverts
Ta slovenski standard je istoveten z: EN 9320:2014
ICS:
35.080 Dokumentiranje razvoja Software development and
programske opreme in system documentation
sistemov (sistemska
dokumentacija)
49.020 Letala in vesoljska vozila na Aircraft and space vehicles in
splošno general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD
EN 9320
NORME EUROPÉENNE
EUROPÄISCHE NORM
December 2014
ICS 35.080; 49.020
English Version
Aerospace series - Programme Management - General
guidelines for acquisition and supply of open systems
Série aérospatiale - Management de Programme - Luft- und Raumfahrt - Programm-Management -
Recommandations générales pour l'acquisition et la Allgemeiner Leitfaden für Erwerb und Lieferung von offenen
fourniture de systèmes ouverts Systemen
This European Standard was approved by CEN on 28 June 2014.

CEN 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 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 member into its own language and notified to the CEN-CENELEC Management Centre has the same
status as the official versions.

CEN members are the national standards bodies 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.
EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels
© 2014 CEN All rights of exploitation in any form and by any means reserved Ref. No. EN 9320:2014 E
worldwide for CEN national Members.

Contents Page
Foreword . 3
1 Scope . 4
2 Normative references . 5
3 Terms and definitions and abbreviated terms . 5
4 Acquisition process. 8
5 Supply process . 12
6 Life cycle model management process . 13
7 Infrastructure management process . 13
8 Budget management process . 14
9 Resource management process . 14
10 Quality management process . 16
11 Project planning process . 16
12 Project control and assessment process. 17
13 Decision-making process . 18
14 Risk management process . 18
15 Configuration management process . 21
16 Information management process . 23
17 Measuring process . 25
18 Requirement establishment and analysis process . 28
19 Architecture design process . 35
20 Execution process . 37
21 Integration process . 37
22 Verification process. 38
23 Validation process . 40
24 Qualification process . 41
25 Operating process . 41
26 Maintenance process . 43
27 Withdrawal from service process . 43
Bibliography . 44

Foreword
This document (EN 9320:2014) has been prepared by the Aerospace and Defence Industries Association of
Europe - Standardization (ASD-STAN).
After enquiries and votes carried out in accordance with the rules of this Association, this Standard has received
the approval of the National Associations and the Official Services of the member countries of ASD, prior to its
presentation to CEN.
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 June 2015, and conflicting national standards shall be withdrawn at the latest
by June 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.
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.
1 Scope
These general guidelines cover the open system acquisition and supply processes.
There is an increasing requirement for systems designed and produced by industry, particularly in the
aeronautic, space and defence fields, to be used with other systems designed, produced, acquired and operated
independently.
The concept of open systems is touched upon in many systems engineering documents. This document deals
specifically with this subject. To this end, through the various processes applied, it provides information to
stakeholders (buyers, suppliers, designers, subcontractors, supervisors, etc.) on the best practice to be adopted.
The specific nature of openness for a system is defined by all the following properties:
 Interchangeability,
 Interoperability,
 Upgradability,
 Reusability,
 Reversibility,
 Flexibility,
 Affordability.
These properties are defined in the glossary for these general guidelines.
These general guidelines are largely based on the structure and system life cycle processes described in
standard ISO/IEC 15288:2008.
The characteristics of openness also relate to:
 The products or services offered by the company (target systems resulting from use of company processes).
 The company’s processes (project systems). Several stakeholders, with their own assignments, cultures,
jobs and geographical locations, different working methods, modelling frameworks, standards, tools and
aids, etc. are involved in the activities, which are sometimes multidisciplinary, of the internal and external
processes of a company. These diverse elements are not necessarily all suited to working together without
causing certain risks, a loss of autonomy, effectiveness and/or efficiency, etc. A company must, for example,
develop its ability and capacity in terms of interoperability both internally (between the systems of which it is
made) and externally (with other partners), including, by way of an example:
 Ability of each stakeholder and each department involved to maintain efficient and trusting relationships
with other stakeholders, taking into account deadline, cost and quality objectives,
 Ability to exchange, communicate and use the necessary flows (data, information, knowledge,
materials, energy) autonomously, without error and dynamically throughout the life cycle of the target
system,
 Ability to coordinate, synchronise and manage common tasks and share and use resources (human,
machine or application) and services efficiently and appropriately.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are indispensable
for its application. For dated references, only the edition cited applies. For undated references, the latest edition
of the referenced document (including any amendments) applies.
ISO 9001:2008, Quality management systems — Requirements
ISO 9241-210:2010, Ergonomics of human-system interaction — Part 210: Human-centred design for interactive
systems
ISO 10007:2003, Quality management systems — Guidelines for configuration management
ISO 10303-1:1994, Industrial automation systems and integration — Product data representation and exchange —
Part 1: Overview and fundamental principles
ISO/IEC 15288:2008, Systems and software engineering — System life cycle processes
ISO/IEC 9126-1:2001, Software engineering — Product quality — Part 1: Quality model
IEEE 830:1998, IEEE Recommended Practice for Software Requirements Specifications
IEEE 1471:2000, IEEE Recommended Practice for Architectural Description for Software — Intensive Systems
3 Terms and definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1.1
affordability
ability of a system to have acceptable operational performance for an acceptable cost of ownership, resulting
from a compromise after negotiation between the Parties
[SOURCE: IEEE 1471:2000]
3.1.2
architecture
fundamental organisation of a system described by its components, the relationship between these components
and with the environment, and the principles guiding its representation and its development. The relationships
between the components are described in the interfaces
3.1.3
capacity
capacity is represented by the consistent integration of a Policy, an Organisation, human resources, training,
Support and Equipment
3.1.4
component
product that cannot be broken down from the point of view of a specific application
[SOURCE: ISO 10303-1:1994]
3.1.5
flexibility
ability of a system to continue to fulfil its mission by dynamically or statically adapting to anticipated or
foreseeable changes that may occur in its environment
3.1.6
interchangeability
ability of a hardware or software component to be replaced, with no change to the components connected to it,
by another that meets the same requirements
3.1.7
interface
an interface is the part of a system or piece of equipment that communicates with another system or piece of
equipment
3.1.8
interoperability
interoperability can be defined as the ability of systems to exchange, with no loss or ambiguity, various object
flows (data, information, knowledge, materials, energy, etc.), then to be capable of using these objects
independently to fulfil their own assignments or to fulfil a shared assignment for a given purpose with no change
to their structure, behaviour or operation
3.1.9
key interface
the interface of a module that needs to be interoperable, easy to change, replaced or isolated due to its
complexity, obsolescence or the costs involved
3.1.10
operational assignment
operational assignments are the parts of department activities that may be repetitive, planned and of limited duration
3.1.11
produ
...