1、AECMA STANDARD NORME AECMA AECMA NORM Edition approved for publication prEN 9200 Edition P 1 December 2001 Comments should be sent within six months after the date of publication to Procedure and Process Domain PUBLISHED BY THE EUROPEAN ASSOCIATION OF AEROSPACE INDUSTRIES - STANDARDIZATION (AECMA-ST
2、AN) Gulledelle 94 - 8-1200 BRUXELLES - Tel. (+32) 2 775 81 10 - Fax. (+32) 2 775 81 11 ICs: Descriptors: ENGLISH VERSION Aerospace series Programme management Guidelines for project management specification Srie arospatiale Luft- und Raumfahrt Recommandation Richtlinie Management de programme Progra
3、mm-Management pour une spcification de management de projet fr eine Projektmanagement-Spezifikation This “Aerospace Series“ Prestandard has been drawn up under the responsibility of AECMA-STAN (The European Association of Aerospace Industries - Standardization). It is published on green paper for th
4、e needs of the European Aerospace Industry. It has been technically approved by the experts of the concerned Domain following member comments. Subsequent to the publication of this Prestandard, the technical content shall not be changed to an extent that interchangeability is affected, physically or
5、 functionally, without re-identification of the standard. Afer examination and review by users and formal agreement of AECMA-STAN it will be submitted as a draft European Standard to CEN (European Committee for Standardization) for formal vote. 2001-12-28 AECM A-STAN Gulledelle 94 8-1200 BRUXELLES M
6、r Zagonel 1 I aecma 200 Page 2 prEN 9200: 2001 Contents Page O 1 2 3 4 5 6 6.1 6.2 6.3 6.4 6.5 6.6 7 7.1 7.1 . 1 7.1.2 7.1.3 7.2 7.2.1 7.2.2 7.2.3 7.2.4 7.3 7.3.1 7.3.2 7.4 7.4.1 7.4.2 7.4.3 7.4.4 7.4.5 8 8.1 8.2 8.3 8.3.1 8.3.2 8.4 8.5 8.6 8.7 9 9.1 9.2 9.3 9.4 9.5 9.6 Normative references . Terms
7、and Definitions . Project objectives . . Resource assessment Project business case Project planning Purpose Application to all the Management plan . Purpose . Requirements relating to the project progress evaluation Setting-up of the wor . . Purpose Risk management Purpose . . Organisation of the ri
8、sk management . Risk identification . Lessons learnt . Systematic analysis . Risk evaluation and characterisation Risks management process Human factor Configuration management Purpose . Configuration Management processes Configuration Identification Establishment of Configuration Baselines Configur
9、ation Contro Configuration Status 4 4 6 6 6 15 15 15 16 16 16 16 16 17 17 17 17 17 18 18 18 19 19 20 20 20 21 21 21 22 23 24 24 24 24 25 25 25 25 25 26 26 26 26 27 27 27 28 28 Page 3 prEN 9200: 2001 9.7 9.8 io 10.1 10.2 10.3 10.4 10.4.1 10.4.2 10.4.3 10.4.4 Il 11.1 11.2 11.2.1 11.2.2 11.2.3 11.3 11.
10、3.1 1 1.3.2 11.4 11.4.1 1 1.4.2 12 12.1 12.1.1 12.1.2 12.2 12.2.1 12.2.2 12.2.3 12.2.4 12.3 13 13.1 13.2 13.3 13.4 13.5 13.6 14 14.1 14.2 14.3 14.4 14.5 15 15.1 15.2 15.3 Annex A Annex B Configuration Review/Audit Configuration Management Plan . Documentation management . List of documents to be app
11、lied and reference documents . Documentation management plan Documentation management requirements . Documentation management Documentation identification Document validation . Management requirements due to the systems engineering activities RAMS (Reliability - Availability . Maintainability . Safe
12、ty) . . . . . Technical performance control . Performance optimisation . Verification and validation, justification and qualification . Schedule control . Resource Management . General . Resource Assessment Resource Acquisition / Staffmg of the Project Resource Allocation . Training/Development o Fa
13、cilities and Infrastructure Quality assurance Purpose Requirements of quality assurance in a project . Quality assurance plan . . Project organisation . Project quality assurance au . Project Closure . Scheduled Project Closure . Unscheduled closure of the project (informative) Bibliography . Genera
14、l . (informative) Documents of accompaniment . 28 28 29 29 29 29 29 29 29 30 30 31 31 31 31 31 32 33 33 33 34 34 34 35 35 35 35 36 36 36 37 37 38 38 38 38 38 39 39 39 39 39 40 40 40 40 40 40 41 41 42 43 Page 4 prEN 9200: 2001 O Foreword Project management aims at planning, monitoring and control of
15、all aspects of a project, and the motivation of all those involved in it, to achieve the project objectives, on time and to the specified cost, quality and performance. It requires: - the definition of the activities, - the roles and the responsibilities for the various actors, - consistency between
16、 their activities, - capacity for communication between them, - a stable and rigorous project organisation. To achieve these objectives, the present document describes the key best practices for the management of an aerospace project, to be adapted specifically for each particular project to be mana
17、ged. In this standard, the customer is either an external identified customer, or an internal entity within the organisation, in charge of receiving or accepting the product. Additionally, this standard may also be used as a basis for the relationship between customers and suppliers at any level of
18、the supply chain. Prior to contract negotiations, the customer will issue a management specification, against which a supplier will submit a management plan. This document will assist in that process by indicating the major issues presented in both documents. The customers in charge of the establish
19、ment of the project management specification should be aware that any management requirement has an impact on the costs and that, as in the case of the requirements for a product, the minimum acceptable requirements should be an objective. The project management specification is to be established wi
20、th the objective of achieving the highest effectiveness in this discipline. In particular, attention is drawn to the possibility for suppliers to use, to the maximum extent, their own internal methods and procedures, in order to obtain quality, reliability and limitation of costs, provided internal
21、procedures meet this recommendation. I Scope For a given aerospace project, the present document is intended to be used as a reference to current best practices. These can be used as a guideline for the creation and negotiation of the project management specification between a customer and a supplie
22、r, and hence lead to the creation of the project management plan. It may be used for any project utilising several actors at different levels. In particular in the case of large projects it presents provisions recommended for the management of a project according to (see figure 1): - project organis
23、ation, - work breakdown structure, - phasing and scheduling, - risk management, - configuration management, - documentation management, - interfaces with other disciplines, - project monitoring and control, - technical performance control, - cost control, - schedule control, - resource management, -
24、 quality assurance, - project closure. Page 5 prEN 9200: 2001 PROJECT MANAGEMENT ., - Risk management (clause 8) 4 Configuration management (clause 9) Documentation management (clause IO) Interfaces with other disciplines (clause 11) +- I / 8 u Quality assurance (clause 14) I I Technical performance
25、 control (subclause 12.1) II Project monitoring and control (clause 12) Cost control Schedule control (subclause 12.2) (subclause 12.3) I 1 I I Resource management (clause 13) Figure 1 - Document organisation The terminology employed is explained in clause 4. It is limited to specifying the context
26、in which potentially ambiguous terms are employed. As far as possible, this terminology includes definitions already appearing in various normative documents, preferably international standards. Page 6 prEN 9200: 2001 2 Programme Management Referring to the definitions of project and project managem
27、ent as given in clause “O Foreword“, programme management may be considered as the directing of a portfolio of projects which benefit from a consolidated approach or towards one specific objective. The common element of the projects in a portfolio is that they run simultaneously, or at least overlap
28、 with one another, they share a number of common resources and are supposed to generate some income. Under this definition, Programme Management is typically concerned with activities at a much higher level within the organisation. This standard will only focus on project management. 3 Normative ref
29、erences The following normative references contain provisions that, through reference in this text, constitute provisions of this International Standard. At the time of publication, the edition indicated was valid. All standards are subject to revision, and parties to agreements based on this Intern
30、ational Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. Members of IEC and IS0 maintain registers of currently valid International Standards. This document is consistent with the quality management requirements as consider
31、ed in normative references : IS0 9000: 2000 IS0 9001: 2000 IS0 10006: 1997 IS0 10007: 1995 EN 9100: 2001 IEEE 1220: 1998 Quality management systems - Fundamentals and vocabulary Quality management systems - Requirements Quality management - Guidelines to quality in project management Quality managem
32、ent - Guidelines for configuration management Aerospace series - Quality management systems - Requirements (based on IS0 9001: 2000) and Quality systems - Model for quality assurance in design, development, production, installation and servicing (based on IS0 9001 : 1994) 1) Standard for Application
33、 and Management of the Systems Engineering Process IEEE Computer Society Document 2) 4 Terms and Definitions For the purposes of this standard, the terms and definitions given in IS0 9000 apply. 4.1 acceptance (of a product or a document) decision pronounced by the customer, acknowledging that the p
34、roduct or the document is in conformity with the contractual commitments The acceptance of a document does not involve the responsibility from the authority which accepts NOTE it, on the use of the document. 4.2 acquisition strategy set of principles defined by a customer as regards technologies, pe
35、rformances, costs, schedules, co-operations to lead the project, . . . 1) Published as AECMA Prestandard at the date of publication of this standard 2) Published by Institute of Electrical and Electronics Engineers Inc - 445 Hoes Lane - P.O.BOX 1331 - Piscataway, I NJ 088551331 - USA Page 7 prEN 920
36、0: 2001 4.3 anomaly gap between a current situation and an expected one NOTE An anomaly justifies an investigation which might lead to the discovery of a non-conformity or a defect. 4.4 applicable con fig u rat ion configuration of a product identified by its changes from the configuration baseline
37、At a given moment, a product may have several applicable configurations. 4.5 approval formal agreement allowing the use or the application of a document NOTE The approving authority commits its own responsibility on the use of the document contents. 4.6 as built configuration configuration of one pr
38、oduct item identified by its gaps of conformity with respect to its applicable configuration 4.7 audit systematic and objective activity undertaken to determine to what extent the requirements related to the agreed topic are satisfied This audit is carried out by one or more persons independent from
39、 what is being audited. 4.8 change changes to document content submitted to configuration control (Technical specification, Design data file, . . .) and characterised by their impact on their use 4.9 configuration functional and physical characteristics of a product as defined in technical documents
40、 and achieved in the product IS0 10007:1995 4.1 O configuration baseline configuration of a product formally established at a specific point in time, which serves as reference for further activities IS0 1 0007: 19951 4.1 I configuration item aggregation of hardware, software, processed materials, se
41、rvices, or any of its discrete portions, that is designated for configuration management and treated as a single entity in the configuration management process IS0 10007:1995 4.1 2 contractual hierarchy stacking customer/supplier such as the supplier of level N becomes customer of the level N+1 Page
42、 8 prEN 9200: 2001 4.1 3 corrective action action to eliminate the cause of a detected nonconformity, or other undesirable situation IS0 9000: 20001 4.14 critical path sequence of tasks where any delay affects the final date 4.1 5 design (of a product or a system) set of technical output data of the
43、 design process describing the functional and physical characteristics of a product or a system NOTE The data is structured in the design data file. 4.1 6 design data file a structured set of documents constituting the response of the product designer to the technical requirements of the applicant A
44、ll the verifiable product characteristics (including the acceptance criteria) could be expressed in this document, and the prescribed processes to produce it are indicated. This file allows identification of the product, in order to prepare its manufacturing and inspection file and its operating doc
45、umentation. 4.17 design justification data file document gathering the whole set of information on studies and tests showing that a product is compliant with its design data file and meets the specification expressing the need which this product shall satisfy 4.1 8 design justification plan document
46、 established by the supplier describing the set of needed works in order to demonstrate that a product compliant with its Design data file, meets the specification expressing the need which this product shall satisfy 4.19 deviation permit permission to depart from the originally specified requiremen
47、ts of a product prior to realisation IS0 9000: 20001 NOTE specific use. A deviation permit is generally given for a limited quantity of products or period of time, and for a 4.20 execution plan document established by every supplier which: - describes: - the main tasks and their logic (it ensures th
48、e consistency and integrates work of the different disciplines such as management, systems engineering, integrated logistics support and RAMS, .), - the resources (hardware and software) needed for their realisation; - presents the schedule of works and in particular the critical paths of the projec
49、t and the particular actions to be carried out. 4.21 function actions of a product or one of its components expressed exclusively in terms of finality Page 9 prEN 9200: 2001 4.22 functional analysis approach which consists in defining, ordering, characterising, prioritising and/or giving value to the functions NOTE 1 The Functional analysis applies to creation or improvement of a product, it is in this case the fundamental base of value analysis. Applied to the need only, it is the base for the establishment of the functional performance specification. NOTE 2
