BS EN 9320-2014 Aerospace series Programme Management General guidelines for acquisition and supply of open systems《航空航天系列 项目管理 开放系统获取和供应的通用指南》.pdf

《BS EN 9320-2014 Aerospace series Programme Management General guidelines for acquisition and supply of open systems《航空航天系列 项目管理 开放系统获取和供应的通用指南》.pdf》由会员分享，可在线阅读，更多相关《BS EN 9320-2014 Aerospace series Programme Management General guidelines for acquisition and supply of open systems《航空航天系列 项目管理 开放系统获取和供应的通用指南》.pdf（48页珍藏版）》请在麦多课文档分享上搜索。

1、BSI Standards PublicationBS EN 9320:2014Aerospace series ProgrammeManagement Generalguidelines for acquisition andsupply of open systemsBS EN 9320:2014 BRITISH STANDARDNational forewordThis British Standard is the UK implementation of EN 9320:2014.The UK participation in its preparation was entruste

2、d to TechnicalCommittee ACE/1, International and European Aerospace Policy andProcesses.A list of organizations represented on this committee can beobtained on request to its secretary.This publication does not purport to include all the necessaryprovisions of a contract. Users are responsible for i

3、ts correctapplication. The British Standards Institution 2014. Published by BSI StandardsLimited 2014ISBN 978 0 580 83573 5ICS 35.080; 49.020Compliance with a British Standard cannot confer immunity fromlegal obligations.This British Standard was published under the authority of theStandards Policy

4、and Strategy Committee on 31 December 2014.Amendments issued since publicationDate Text affectedBS EN 9320:2014EUROPEAN STANDARD NORME EUROPENNE EUROPISCHE NORM EN 9320 December 2014 ICS 35.080; 49.020 English Version Aerospace series - Programme Management - General guidelines for acquisition and s

5、upply of open systems Srie arospatiale - Management de Programme - Recommandations gnrales pour lacquisition et la fourniture de systmes ouverts Luft- und Raumfahrt - Programm-Management - Allgemeiner Leitfaden fr Erwerb und Lieferung von offenen Systemen This European Standard was approved by CEN o

6、n 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

7、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

8、 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,

9、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 EUROPEN DE NORMALISATION EUROPISCHES KOMITEE FR NORMUNG CEN-CENELEC Management

10、 Centre: Avenue Marnix 17, B-1000 Brussels 2014 CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Members. Ref. No. EN 9320:2014 EBS EN 9320:2014EN 9320:2014 (E) 2 Contents Page Foreword . 3 1 Scope . 4 2 Normative references . 5 3 Terms and definitions

11、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 con

12、trol 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 pr

13、ocess 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 BS EN 9320:2014EN 9320:2014 (E) 3 Foreword This document (EN 9320:2014)

14、 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

15、 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 2

16、015. 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 organiz

17、ations 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, Ma

18、lta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. BS EN 9320:2014EN 9320:2014 (E) 4 1 Scope These general guidelines cover the open system acquisition and supply processes. There is an increasing requirement for system

19、s 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 wi

20、th 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:

21、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 IS

22、O/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 companys processes (project systems). Several stakeholders, with their own assignments, cultures, jobs and geographical loca

23、tions, 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 causin

24、g 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: Abili

25、ty 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) auto

26、nomously, 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. BS EN 9320:2014EN 9320:2014 (E) 5 2 Normative ref

27、erences 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.

28、 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

29、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 Practi

30、ce 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

31、.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 relat

32、ionship 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, hu

33、man 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 BS EN 9320:2014EN 9320:2014 (E) 6 3.1.5 flexibility ability of a system to continue to fulfil its mission by dynamically or stat

34、ically 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 t

35、he 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.),

36、 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, replac

37、ed 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 product life cycle this covers all the situations the product goes thro

38、ugh during its life from statement of requirement to withdrawal from whatever service is provided SOURCE: NF X 50-100:1996 3.1.12 reusability for a hardware or software component, ability to be used, unchanged, in a system or subsystem other than the one for which it was originally developed For a s

39、ystem or subsystem, ability to use, unchanged, hardware or software components which were not originally developed for it 3.1.13 reversibility ability of a system, subsystem or component to be modified and updated by a manufacturer other than the one that produced it 3.1.14 open system assembly incl

40、uding software and hardware elements and operating procedures, designed by humans. These elements interact to satisfy the requirements (including interface requirements) defined, published and maintained by general consensus by a group Modular construction created so that its modules are defined pre

41、cisely and have public interfaces allowing independent suppliers to provide new capacities and innovative modules Modular Open System Architecture BS EN 9320:2014EN 9320:2014 (E) 7 3.1.15 openness the characteristic of openness for a system is defined by all the following properties: Interchangeabil

42、ity, Interoperability, Upgradability, Reusability, Reversibility, Flexibility, Affordability. 3.1.16 system of systems (SoS) the characteristics of a system of systems are: Operational independence of the systems, Managerial independence of the systems, Emergence of new services, Upgradable configur

43、ations, Geographic distribution of the systems, 3.1.17 technical facts key technical event, anticipated or unexpected, in the life cycle of a product 3.1.18 upgradability potential ability of a system, subsystem or component to respond to changes in operational requirements and anticipated or forese

44、eable technical changes without affecting the basis of its structure 3.1.19 validation comparative assessment to confirm that the requirements of stakeholders are properly satisfied. If discrepancies are found, they are recorded and lead to corrective action. Validation is ratified by the stakeholde

45、rs SOURCE: ISO/IEC 15288:2008 3.1.20 verification demonstration, through assessment of the product, that the system has been designed correctly, i.e. that it complies with the specifications according to which the product was made SOURCE: ISO/IEC 15288:2008 BS EN 9320:2014EN 9320:2014 (E) 8 3.2 List

46、 of abbreviations NCOIC Network Centric Operations Industry Consortium OTS Off-The-Shelf IADT Inspection Analysis Demonstration Test OS Open System MMI Man Machine Interface SoS System of Systems SMART Specific, Measurable, Achievable, Realistic and Time-constrained. STEP Standard for the Exchange o

47、f Product model data TRL Technology Readiness Level IRL Integration Readiness Level SCOPE Systems Capabilities, Operations, Programmes and Enterprises UML Unified Modelling Language SysML System Modelling Language 4 Acquisition process The organisations are producers and consumers of systems, which

48、may make products or perform services. These systems are produced by some or implemented or consumed by others within the context of the relationship between buyers (those who purchase and consume or use) and suppliers (those who produce and sell). Buyer/supplier relations are maintained through con

49、tracts. Acquisition of an open system requires specific activities to be carried out to optimise signature of contracts to obtain a product/service that satisfies the openness requirements. The purpose of the process described in this chapter is to characterise these activities. The level of detail of each activity depends on the complexity of the system to be acquired. 4.1 An acquisition strategy is established 4.1.1 Define an openness strategy Define the openness level required depending on,