ASD-STAN PREN 9277-2013 Aerospace series Programme Management Guide for the management of Systems Engineering (Edition P 1).pdf

1、ASD-STAN STANDARD NORME ASD-STAN ASD-STAN NORM prEN 9277 Edition P 1 January 2013 PUBLISHED BY THE AEROSPACE AND DEFENCE INDUSTRIES ASSOCIATION OF EUROPE - STANDARDIZATIONRue Montoyer 10 - 1000 Brussels - Tel. 32 2 775 8126 - Fax. 32 2 775 8131 - www.asd-stan.orgICS: Descriptors: ENGLISH VERSION Aer

2、ospace series Programme Management Guide for the management of Systems Engineering Srie arospatiale Management de Programme Guide pour le management de lingnierie Systme Luft- und Raumfahrt Programm-Management Leitfaden fr das Management von Systemtechnik This “Aerospace Series“ Prestandard has been

3、 drawn up under the responsibility of ASD-STAN (The AeroSpace and Defence Industries Association of Europe - Standardization). It is published for the needs of the European Aerospace Industry. It has been technically approved by the experts of the concerned Domain following member comments. Subseque

4、nt to the publication of this Prestandard, the technical content shall not be changed to an extent that interchangeability is affected, physically or functionally, without re-identification of the standard. After examination and review by users and formal agreement of ASD-STAN, it will be submitted

5、as a draft European Standard (prEN) to CEN (European Committee for Standardization) for formal vote and transformation to full European Standard (EN). The CEN national members have then to implement the EN at national level by giving the EN the status of a national standard and by withdrawing any na

6、tional standards conflicting with the EN. Edition approved for publication 31 January 2013 Comments should be sent within six months after the date of publication to ASD-STAN Engineering Procedures Domain Copyright 2013 by ASD-STAN prEN 9277:2013 (E) 2 Contents Page Foreword 3 Introduction . 4 1 Sco

7、pe 5 2 Normative references 5 3 Terms and definitions . 6 4 Symbols and abbreviations 7 5 Positioning of Systems Engineering and SE management within a Programme . 7 6 Systems Engineering process . 11 7 Principle for defining requirements and elements of the management plan 18 8 Examples of manageme

8、nt requirements and elements of the management plan concerning Systems Engineering 21 9 Interfaces between Systems Engineering management and the other Programme Management disciplines . 29 10 Specialty engineering activities . 31 Annex A (informative) Areas covered by standards covering Systems Eng

9、ineering 33 Annex B (normative) Method for identifying management requirements . 34 B.1 “SE management generic requirements” table 34 B.2 Method for using the “SE Management generic requirements” table . 35 B.2.1 For drafting SE management requirements 35 B.2.2 To draft elements concerning the manag

10、ement plan SE 36 Annex C (normative) Implementation example: “solution definition” activity . 37 C.1 Filled out table . 37 C.2 Requirements and elements of the management plan 38 C.2.1 Management requirements (see 8.6.1) 38 C.2.2 Elements of the management plan (see 8.6.2) 39 Annex D (normative) Des

11、cription of SE process activities 41 D.1 Expression of need by the Acquirer 41 D.2 Acquirers needs analysis and system requirements definition 41 D.3 Requirements validation . 41 D.4 Solution definition . 41 D.5 Modelling and simulation 42 D.6 System analyses 42 D.7 System verification 42 D.8 System

12、 validation 43 Annex E (normative) Description of certain objects in the SE process 44 Annex F (normative) Mapping between systems engineering processes and Human-centred design for interactive systems processes and principles 45 F.1 Mapping with ISO/IEC 15288:2008 Technical processes . 45 F.2 Mappi

13、ng with ISO/IEC 15288:2008 others processes than technical ones . 45 Bibliography 46 prEN 9277:2013 (E) 3 Foreword This standard was reviewed by the Domain Technical Coordinator of ASD-STANs Engineering Procedures Domain. After inquiries and votes carried out in accordance with the rules of ASD-STAN

14、 defined in ASD-STANs General Process Manual, this standard has received approval for Publication. prEN 9277:2013 (E) 4 Introduction This document aims to address the current challenges of the programs that are: the multi projects approach, the multi-disciplinary approach, new methods of acquisition

15、 the increasing complexity of systems to be acquired, the evolving aspects of the system and its incremental development, the complexity of the management of programs in terms of organization, the evolution of the industrial sectors. In this document the system considered comprises a target system

16、and elements (products, processes, etc.) needed for developing, producing and using it, in other words a range of end products and products supporting the lifecycle of the target system. The case where the system is only an element of the service provided (no system is acquired, service only) is not

17、 adressed in this document. Systems Engineering (SE) cover a set of activities which, based on a perceived operational need and via an organized approach, aims to: describe this need in technical terms, gradually transform it into a system solution, at each stage, demonstrate that this system is com

18、pliant with the need. Systems Engineering: considers the system as a whole and in all situations of its lifecycle, provides a framework for combining various technical disciplines (electronics, data processing, mechanics, ergonomics, etc.) and some enterprise functions (design, production, logistics

19、 tests, etc.) without necessarily intervening in these disciplines and functions, aims for the overall optimization of the solution in a field of constraints (costs, schedule, performance, strategy, etc.) established by the Programme management, guarantees consistency between all components of the

20、solution (functional and physical interfaces). In this document, the organisational dimension is essential to reach the overall objectives. The complexity of the system and the complexity of the organisation are correlate (the more complex the system is, the more control of the organisation is neces

21、sary). This document is a continuation and development of paragraphs 3.1 “Performance Management” and 3.2 “Systems Engineering” of EN 9200. Its position with respect to other normative documents handling Systems Engineering (ISO/IEC 15288, EIA 632,IEEE 1220, EN 9200) is represented in Annex A. This

22、document falls within the scope of EN 9200 and ISO/IEC 15288, focusing on aspects linked to the management of the technical activities of SE with a higher level of detail. It relies partly on the SE process described in ISO/IEC 15288:2008 and if necessary with addition from EIA 632, adding the Progr

23、amme phasing and scheduling aspect. It overlaps little with IEEE 1220 as such, which concentrates primarily on SE technical activities. prEN 9277:2013 (E) 5 1 Scope Based on the following considerations: reminder of Systems Engineering and its scope of application, positioning of SE management in Pr

24、ogramme Management and in relation to Systems Engineering technical activities, identification of interfaces between SE management and the other disciplines linked to Programme Management, the purpose of this standard is: to help the acquirer and the Organization to establish management requirements

25、 for SE activities, to help the supplier to construct the elements of the management plan (explain how to reply in particular to the management requirements). This standard applies to the various levels of the product tree for the products that can be considered as systems: in the general case of an

26、 supplier which, with the help of one or more suppliers, develops a system on behalf of an acquirer, in the case of an integrated team (sharing of SE roles, responsibilities and risks). NOTE ISO/IEC/IEEE 24765:2010 integrated team should include organisation discipline and functions which have a sta

27、ke in the success of the work products. This standard constitutes a guide illustrating the requirements and possible responses for SE management. It can be used as a check-list which should be adapted or completed according to the specific context of each Programme. 2 Normative references The follow

28、ing referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. EN 9200, General recommendation for the project management

29、specification EN 12973, Value management EN ISO 9000:2005, Quality management systems Fundamentals and vocabulary ISO 9220, Metallic coatings Measurement of coating thickness Scanning electron microscope method EN ISO 9241-210:2011, Ergonomics of human-system interaction Part 210: Human-centred desi

30、gn for interactive systems ISO/IEC 15288:2008, Systems and software engineering Systems life cycle processes ISO/IEC/IEEE 24765:2010, Systems and software engineering Vocabulary EIA 632:2003, Processes for Engineering a System 1)IEEE 1220:1999, Standard for Application and Management of the Systems

31、Engineering Process 2)1) EIA National (US) Electronic Industries Association http:/www.eia.org/ 2) IEEE International Institute of Electrical and Electronical Engineers http:/www.ieee.org/ prEN 9277:2013 (E) 6 3 Terms and definitions The following referenced documents are essential for the applicati

32、on of this document. For dated references, only the written issue applies. For the purposes of this document, the following terms and definitions apply. ISO/IEC/IEEE 24765:2010 Systems and software engineering vocabulary should be used for the definition. In addition, the following standards should

33、be used for definition as ordered: ISO/IEC 15288:2008, Systems and software engineering Systems life cycle processes EN ISO 9241-210:2011, Ergonomics of human-system interaction Part 210: Human-centred design for interactive systems EIA 632:2003, Processes for Engineering a System IEEE 1220:1999, St

34、andard for Application and Management of the Systems Engineering Process EN ISO 9000:2005, Quality management systems Fundamentals and vocabulary 3.1 complexity characteristic of a process linked to the number and diversity of participants, components and technologies, involved in the design and pro

35、duction of products and the supporting logistics 3.2 iterativity characteristic of a process which is repeated several times in full or in part, with a search for convergence towards a product meeting the expressed need 3.3 recursivity owing to the system breakdown into sub-systems, repetition of th

36、e SE process at various breakdown levels with strong interaction between the levels 3.4 system set of complex hardware, software, personnel and operational processes, organized so as to satisfy the needs and fulfil the expected services, in a given environment 3.5 systems engineering interdisciplina

37、ry approach governing the total technical and managerial effort required to transform a set of customer needs, expectations, and constraints into a solution and to support that solution throughout its life NOTE Includes the definition of technical performance measures; the integration of engineering

38、 specialties toward the establishment of architecture; and the definition of supporting lifecycle processes that balance cost, performance, and schedule objectives. 3.6 scalability the ability to change the component configuration of a system to fit desired application context NOTE Component configu

39、ration changes may be obtained by deployment of items or by setting configuration parameters of each item. 3.7 upgradability potential ability of a system, subsystem or component to respond to changes in operational requirements and anticipated or foreseeable technical changes without affecting the

40、basis of its structure See ISO 9220. prEN 9277:2013 (E) 7 4 Symbols and abbreviations For the purpose of this document, the abbreviations used are clarified below: CAD : Computer Assisted Design FS : Functional Specifications ILS : Integrated Logistics Support MP : Management Plan MS : Management Sp

41、ecification (N)TS : (Need) Technical Specification PDCA : Plan/Do/Check/Act PTS : Product Technical Specification SE : Systems Engineering TS : Technical Specification 5 Positioning of Systems Engineering and SE management within a Programme 5.1 The need for Systems Engineering Management Within the

42、 business activities, two different and complementary visions co exist. SE vision highlights the following main objectives: a) The management of SE activities giving assurance that all SE activities are identified, planed, monitored and controlled: before launch of the project/program through the id

43、entification of the technical activities to perform during the project/program to satisfy needs of the system development and project/program constraints (costs, schedule, performance), during the project/program through the identification of the engineering tasks, the relevant resources including h

44、uman resources, the appointment of the main responsibles, the reporting needed to monitor and control the progress of the engineering, along the project/program maintain the compliance of the system design and definition with the requirements. b) Contribution of the Systems Engineering to the Progra

45、mme: converting a set of needs into a system meeting the set of needs, through a systematic approach contributing towards an integrated design of the product and associated manufacturing, testing and support processes, from a technical point of view, managing and optimizing the system performance in

46、 accordance with the Programme objectives and constraints, prEN 9277:2013 (E) 8 enable to deploy a gradually demonstration that this system meets the set of needs, identifying the system technical risks and conducting risk mitigation actions, and contributing to the overall risk management process.

47、A strong coordination and integration is essential, justifying the creation of formalized specific SE management, for example through an SE specification and MP. Indeed, some main characteristics differentiate the SE with respect to conventional engineering activities and justify the need for specif

48、ic SE management: a lack of imprecise requirements, which are refined during development, supplemented by assumptions; complexity of the environment, interacting closely with the system (Man Machine Interface, field of operation, etc.); complexity linked to the number and diversity of stakeholders,

49、the number of different technologies, the products themselves and the supporting logistics (system dedicated to multi acquirers on multi markets); iterativity; recursivity of project processes; scalability of the system; upgradability of the systems, sub-systems and components. Systems Engineering involves both the Acquirer and the Supplier(s) of the Organization and comprises the various technical processes which iteratively and exhaustively contribute to ensur