BS EN 9200-2005 Programme management Guidelines for project management specification《项目管理 项目管理规范指南》.pdf

1、BRITISH STANDARD AEROSPACE SERIES BS EN 9200:2004 Programme management Guidelines for project management specification The European Standard EN 9200:2004 has the status of a British Standard ICS 49.140 BS EN 9200:2004 This British Standard was published under the authority of the Standards Policy an

2、d Strategy Committee on 31 January 2005 BSI 31 January 2005 ISBN 0 580 45362 6 National foreword This British Standard is the official English language version of EN 9200:2004. The UK participation in its preparation was entrusted to Technical Committee ACE/1, International and European aerospace po

3、licy and processes, which has the responsibility to: A list of organizations represented on this committee can be obtained on request to its secretary. Cross-references The British Standards which implement international or European publications referred to in this document may be found in the BSI C

4、atalogue under the section entitled “International Standards Correspondence Index”, or by using the “Search” facility of the BSI Electronic Catalogue or of British Standards Online. This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its

5、 correct application. Compliance with a British Standard does not of itself confer immunity from legal obligations. aid enquirers to understand the text; present to the responsible international/European committee any enquiries on the interpretation, or proposals for change, and keep the UK interest

6、s informed; monitor related international and European developments and promulgate them in the UK. Summary of pages This document comprises a front cover, an inside front cover, the EN title page, pages 2 to 45 and a back cover. The BSI copyright notice displayed in this document indicates when the

7、document was last issued. Amendments issued since publication Amd. No. Date CommentsEUROPEANSTANDARD NORMEEUROPENNE EUROPISCHENORM EN9200 November2004 ICS49.140 Englishversion AerospaceseriesProgrammemanagementGuidelinesfor projectmanagementspecification SriearospatialeManagementdeprogramme Recomman

8、dationpourunespcificationdemanagement deprojet LuftundRaumfahrtProgrammManagementRichtlinie freineProjektmanagementSpezifikation ThisEuropeanStandardwasapprovedbyCENon4June2004. CENmembersareboundtocomplywiththeCEN/CENELECInternalRegulationswhichstipulatetheconditionsforgivingthisEurope an Standardt

9、hestatusofanationalstandardwithoutanyalteration.Uptodatelistsandbibliographicalreferencesconcernings uchnational standardsmaybeobtainedonapplicationtotheCentralSecretariatortoanyCENmember. ThisEuropeanStandardexistsinthreeofficialversions(English,French,German).Aversioninanyotherlanguagemadebytra ns

10、lation undertheresponsibilityofaCENmemberintoitsownlanguageandnotifiedtotheCentralSecretariathasthesamestatusast heofficial versions. CENmembersarethenationalstandardsbodiesofAustria,Belgium,Cyprus,CzechRepublic,Denmark,Estonia,Finland,France, Germany,Greece,Hungary,Iceland,Ireland,Italy,Latvia,Lith

11、uania,Luxembourg,Malta,Netherlands,Norway,Poland,Portugal, Slovakia, Slovenia,Spain,Sweden,SwitzerlandandUnitedKingdom. EUROPEANCOMMITTEEFORSTANDARDIZATION COMITEUROPENDENORMALISATION EUROPISCHESKOMITEEFRNORMUNG ManagementCentre:ruedeStassart,36B1050Brussels 2004CEN Allrightsofexploitationinanyforma

12、ndbyanymeansreserved worldwideforCENnationalMembers. Ref.No.EN9200:2004:EEN 9200:2004 (E) 2 Contents Page Foreword3 Introduction.4 1 Scope 4 2 Programme Management6 3 Normative references 6 4 Terms and Definitions .6 5 Project context.15 6 Project establishment .16 7 Project planning.17 8 Risk manag

13、ement 25 9 Configuration management27 10 Documentation management .30 11 Interfaces with other disciplines32 12 Project monitoring and control 36 13 Resource Management .39 14 Quality assurance41 15 Project Closure 42 Annex A (informative) Documents of accompaniment .43 Bibliography44 EN 9200:2004 (

14、E) 3 Foreword This document (EN 9200:2004) has been prepared by the European Association of Aerospace Manufacturers - Standardization (AECMA-STAN). After enquiries and votes carried out in accordance with the rules of this Association, this Standard has received the approval of the National Associat

15、ions and the Official Services of the member countries of AECMA, 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 May 2005, and conflicting national standards shal

16、l be withdrawn at the latest by May 2005. According to the CEN/CENELEC Internal Regulations, the national standards organizations of the following countries are bound to implement this European Standard: Austria, Belgium, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hu

17、ngary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom. Annex A is informative. EN 9200:2004 (E) 4 Introduction Project management aims at planning, monitoring and control of a

18、ll 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 their

19、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 managed. In thi

20、s 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 the supply

21、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 establishment of the

22、 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 with the obje

23、ctive 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 procedures

24、meet this recommendation. 1 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 supplier, and henc

25、e 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 organisation, work b

26、reakdown 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, quality assurance, project clo

27、sure. EN 9200:2004 (E) 5 Figure 1 Document organisation The terminology employed is explained in clause 4. It is limited to specifying the context in which potentially ambiguous terms are employed. As far as possible, this terminology includes definitions already appearing in various normative docum

28、ents, preferably international standards. Project planning (clause 7) Technical performance control (subclause 12.1) Schedule control (subclause 12.3) Cost control (subclause 12.2) PROJECT MANAGEMENT Quality assurance (clause 14) Resource management (clause 13) Project establishment (clause 6) Proje

29、ct monitoring and control (clause 12) Risk management (clause 8) Configuration management (clause 9) Documentation management (clause 10) Interfaces with other disciplines (clause 11) EN 9200:2004 (E) 6 2 Programme Management Referring to the definitions of project and project management as given in

30、 clause “0 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 with one anoth

31、er, 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 references The fol

32、lowing 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. This document is consistent with the quality management

33、requirements as considered in normative references: EN ISO 9000:2000, Quality management systems Fundamentals and vocabulary (ISO 9000:2000) EN ISO 9001:2000, Quality management systems Requirements (ISO 9001:2000) ISO 10006:2003, Quality management systems Guidelines for quality management in proje

34、ct ISO 10007:2003, Quality management systems Guidelines for configuration management EN 9100:2003, Aerospace series Quality management systems Requirements (based on ISO 9001:2000) and Quality systems Model for quality assurance in design, development, production, installation and servicing (based

35、on ISO 9001:1994) EN 9130: 2001, Aerospace series Quality management systems Record retention IEEE 1220:1998, Standard for Application and Management of the Systems Engineering Process IEEE Computer Society Document 1)4 Terms and Definitions For the purposes of this European Standard, the terms and

36、definitions given in EN ISO 9000:2000 and the following apply. 4.1 acceptance (of a product or a document) decision pronounced by the customer, acknowledging that the product or the document is in conformity with the contractual commitments NOTE The acceptance of a document does not involve the resp

37、onsibility from the authority which accepts it, on the use of the document. 4.2 acquisition strategy set of principles defined by a customer as regards technologies, performances, costs, schedules, co-operations to lead the project, 1) Published by Institute of Electrical and Electronics Engineers I

38、nc 445 Hoes Lane P.O.Box 1331 Piscataway, NJ 08855-1331 - USA EN 9200:2004 (E) 7 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 nonconformity or a defect. 4.4 applicable configuration configuration of

39、a product identified by its changes from the configuration baseline 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 d

40、ocument contents. 4.6 as built configuration configuration of one product 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 satisfi

41、ed This audit is carried out by one or more persons independent from 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

42、 characteristics of a product as defined in technical documents and achieved in the product ISO 10007:2003 4.10 configuration baseline configuration of a product formally established at a specific point in time, which serves as reference for further activities ISO 10007:2003 4.11 configuration item

43、aggregation of hardware, software, processed materials, services, or any of its discrete portions, that is designated for configuration management and treated as a single entity in the configuration management process ISO 10007:2003 4.12 contractual hierarchy stacking customer/supplier such as the s

44、upplier of level N becomes customer of the level N+1 EN 9200:2004 (E) 8 4.13 corrective action action to eliminate the cause of a detected nonconformity, or other undesirable situation EN ISO 9000:2000 4.14 critical path sequence of tasks where any delay affects the final date 4.15 design (of a prod

45、uct or a system) set of technical output data of the 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.16 design data file a structured set of documents constituting the response of the product design

46、er to the technical requirements of the applicant All 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 manu

47、facturing and inspection file and its operating documentation. 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 sha

48、ll satisfy 4.18 design justification plan document 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 requirements of a product prior to realisation EN ISO 9000:2000 NOTE A deviation permit is generally given for a limited quantity of products or period of time, an