EN 13290-1-1999 en Space Project Management - General Requirements - Part 1 Policy and Principles《航天项目管理 一般要求 第1部分 政策和原则》.pdf

《EN 13290-1-1999 en Space Project Management - General Requirements - Part 1 Policy and Principles《航天项目管理 一般要求 第1部分 政策和原则》.pdf》由会员分享，可在线阅读，更多相关《EN 13290-1-1999 en Space Project Management - General Requirements - Part 1 Policy and Principles《航天项目管理 一般要求 第1部分 政策和原则》.pdf（29页珍藏版）》请在麦多课文档分享上搜索。

1、BRITISH STANDARD AEROSPACE SERIES Space project management - General requirements - Part 1: Policy and principles The European Standard EN 13291:1999 has the status of a British Standard ICs 49.140 BS EN 13290-1: 1999 NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAW STD - BSI b

2、een prepared under the direction of the Engineering Sector Committee, was published under the authority of the Standards Committee and comes inb effect on 15 June 1999 Amd. No. O BSI 06-1999 ISBN O 680 32639 X BS EN 13290-k1999 Date Comments BS EN 13290-1-ENGL 1979 B Lb24bb 0781793 854 m National fo

3、reword This BriW Standard is the English language version of EN 13291:1999. The UK participation in its preparation was entrusted to Technical Committee ACW68, Space systems and operations, which has the responsibility to: - aid enquirers to understand the text; - present to the responsible intemati

4、onavEuropean commitke any enquines on the interpretation, or proposals for change, and keep the UK interests infOIllled; - monitor related international and European developments and promulgate them in the UK. A list of organizations represented on this committee can be obtained on request to its se

5、cretary. Cross-references The British Standards which implement international or European publications referred to in this document may be found in the BSI Standards Catalogue under the section entitled “international Standards Correspondence Index“, or by using the “Find“ facility of the BSI Standa

6、rds Electronic Catalogue. A British Standard does not purport to include all the necessary provisions of a conira O defines the basic management rules for the execution of space projects; 0 defines the applicability of these rules to all the actors in these projects, including for example space agen

7、cies, industry and scientific laboratories; identifies project requirements without imposing a particular organizational structure on the actors; 0 O proposes how these requirements can be tailored to specific project needs. 1.2 Space standards domains The space standards have been grouped in three

8、branches, designated as management, product assurance and engineering. 0 The management standards define the process requirements to be applied to the overall project activities during the life cycle. They describe what needs to be achieved to establish project breakdown structures (e.9. product tre

9、e, work breakdown structure), the project organization and cost and schedule management, and cover also the management of configuration, documentation, and integrated logistic support. The product assurance standards define the requirements for the management and performance of product assurance act

10、ivities during a space project (quality assurance, dependability, safety, EEE components control, materials, mechanical parts and processes control, software product assurance). 0 0 The engineering standards are devoted to the products themselves. They cover: the engineering process as applied to sp

11、ace systems and their elements or functions; technical aspects of parts, assemblies, equipments, subsystems and systems used to accomplish, or associated with, space missions. They include specifications, guidelines, manuals, handbooks and procedures, all identified as space standards. Their objecti

12、ve is to enable engineers to work as efficiently as possible and to achieve the most appropriate product for the project application. Page 7 EN 13290-1:1999 2 Normative references This European standard incorporates by dated or undated reference, provisions from other publications. These normative r

13、eferences are cited at the appropriate places in the text and publications are listed hereafter. For dated references, subsequent amendments to or revisions of any of these apply to this standard only when incorporated in it by amendment or revision. For undated references the latest edition of the

14、publication referred to applies. ECSS-M- 1OA Space project management - Project breakdown structures ECSS-M-20A ECSS-M-30A ECSS-M40A ECSS-M-SOA ECSS-M-GOA Space project management - Project organization Space project management - Project phasing and planning Space project management - Configuration

15、management Space project management - Information/Documentation management Space project management - Cost and schedule management ECSS-M-70A Space project management - Integrated logistic support EN 13291-1 Space product assurance - General requirements - Part 1: Policy and principles EGS-Q-ZOA Spa

16、ce product assurance - Quality assurance ECSS-Q-30A Space product assurance - Dependability ECSS-Q-40A Space product assurance - Safety EN 13292 Space engineering - Policy and principles ECSS- E- 1 OA Space engineering - System engineering ECSS-P-OOlA, Rev 1 ECSS - Glossary of terms IS0 9001: 1994 Q

17、uality systems - Model for quality assurance in design/development, production, installation and servicing 3 Definitions and abbreviations 3.1 Definitions For the purposes of this standard, the definitions given in ECSS-P-001 and the following definitions apply - 3.1.1 Support system The hardware an

18、d software products, together with the necessary human resources, which are essential to enable the supported system to achieve its system functional performance from delivery to the end of the life cycle of the supported system, at minimum total life cycle (discounted cash flow) cost. 3.1.2 Support

19、ed system The hardware and software products, together with the necessary human resources, which are essential to the system functional performance as expected by the consumer. STD.BSI HS EN 13Z90-3-ENLL 3777 W Lb2LibbY 0783803 750 Page 8 EN 13290-1: 1999 3.2 Abbreviations The following abbreviation

20、s are defined and used within this standard. Abbreviation Meaning ECSS European Cooperation for Space Standardization EEE Electronic, Electrical, Electromechanical WBS Work Breakdown Structure 4 Use of space standards to define project requirements 4.1 Policy and principles It is a policy that space

21、 standards should, as far as is practikble, define requirements in terms of what is to be achieved, interface requirements to be satisfied, and constraints which shall not be breached. It is a cardinal principle that no particular methodologies, implementation techniques, or organizational arrangeme

22、nts shall be imposed. Consequently, these documents shall be made applicable on a project by the customer invoking them in the binding documentation in accordance with the relevant business agreement. It is a policy that the supplier shall have the freedom to choose the methodology by which he inten

23、ds to fulfil the project requirements, which reference the space standards, except where methodology guidelines and constraints are made applicable for the project. In order to fulfil the objectives space standards allow for the following functions: a) to enable optimization of aspects of the “custo

24、mer/supplier“ relationship that is established among all the actors of a space project. Consequently, they have been drafted so as to facilitate: the critical stages of the elaboration process of the business agreements and contracts dauses binding the various participants. They cover the preparatio

25、n of an Invitation To Tender (IlT), by the purchaser, the elaboration of the industry proposal and the final negotiation preceding the contract award. During these three stages, the space standards will enable the different actors (customer 0 As with the first level supplier (see above), each lower

26、level supplier acts as customer for the next level below. the supply of one or more constituents of the system. Depending upon the project, space agencies can play different roles. They can be consumer when they will benefit from the services of the system, they can be first level customer under a m

27、andate given by a consumer, but they can be also supplier when they provide products at a given level in the customer- supplier nehivork (.e. Space agency furnished equipment or services). In any case, space standards requirements are applicable. Participants roles in Cu-/ supplie8 nctwor Level O 1

28、2 Note 1 Note 2 Note 3 Note 4 Table 1 - Paraupants roles in customer/supplier netcivork. ow-* I etc I etc lustomcr from iext level Supplier, !tC) qend: R = Responsible for doing the activity; A to be supplied A R R for next A for next level I level A R etc etc I Agreement with activity output e.g. E

29、nd user: commercial organization, space agency, armed forcestcoordinated inter-governmental organization, experimenter. e.g. Space agency, governmental project management office. e.g. Prime contractor. .e. Level 2, 3, 4, etc., repeated as necessary. Supply of outputs R R C = Consulted Page 11 EN 132

30、90-111999 Consumers needs and expectations CONSUMER Standards including management - - FIRST LEVEL CUSTOMER SUPPUER financial obes Selection 81 and constraints political / tailoring Local project context Figure 1 - Principles governing the implementation of the customer-supplier network concept , Im

31、plementation documents L - Q Selection I I 7 8 Respond b l I requirements a Page 12 EN 13290-1: 1999 4.3 Selection and tailoring of standards Space standards draw together a large body of space standards applicable to all the products and projects. However, selection and tailoring of space standards

32、 are needed, at customer level, in order to meet the expectations of the consumer in the most cost-effective way. For that, adaptation of space standards shall be based on identified specific project objectives and constraints. Placing at the actors disposal pre-established requirements in a form su

33、itable for reference or quotation in binding documents is a way to facilitate this process. The tailoring of the space standards to the specific project requirements shall be done according to a number of criteria such as: 0 the overall project risks, their criticality and their consequences with re

34、gard to technical performance, cost and schedule (refer to subclause 5.3); 0 the dass of productc (refer to EN 13292); 0 the project category; industrial policy. Selection can concern the choice of requirements to be taken into account, possible tailoring for some of them, and the practical modaliti

35、es (processes, tooling, described in level 3 documents), whether imposed or not, for some or all of the actors. The principle for drawing up the requirements specific to a project (project requirements documents) and the responses from the different industrial organization levels to these requiremen

36、ts in the form of “implementation documents“ is illustrated in Figure 1. The application principle for the project requirements documents is as follows: they are drawn up by the first level customer and are to be followed by all the levels of the industrial organization, with tailoring specified by

37、each customer to the corresponding supplier, depending on the context. The response from the different levels regarding the project requirements documents can take the form of an individual implementation document for each project requirements document or a single implementation document with a sepa

38、rate chapter for each project requirements document. Tailoring of the space management standards to project specific management requirements can be based on a project ranking according to the prdefined categories given below. Each space project shall be placed in one of the categories defined below,

39、 at the latest by the end of project phase A (definition according to ECSS-M-30) by the first level customer, and the lower levels shall be informed of the applicable project category. The following project categories should be considered: category 1: A project where loss of the mission would be una

40、cceptable. The allocated budgets and development schedules shall be sufficient to obviate major technical deadlocks. All the risks shall be examined and reduced. Confidence levels shall be maximal, management services complete, and full in-depth knowledge of the product shall be acquired. category 2

41、 A project aimed at achieving overall control of project risks. Project rkk/total cost compromises which minimize risk are sought after. Management services are lightened very slightly. Page 13 EN 13290-li1999 category 3: A project aimed at achieving overall containment of cost. Project risk/total c

42、ost compromises which minimize cost are sought after. The level of accepted risk is higher. Management services are lightened. category 4: A minimum cost project. The mission is only worth while if its cost is kept down. The management activities are reduced to a minimum. On that basis, the customer

43、 can select a framework that meets the requirements of the consumer and that is appropriate for the project objectives and constraints. 4.4 Requirements 4.4.1 Business agreement The customers at every level shall specify the minimum requirements necessary for their suppliers to achieve the project o

44、bjectives. AIM: Minimizing requirements is a key factor in minimizing supplier costs and maximizing supplier responsiveness. With the aim of reducing supplier costs, unnecessary non-value-adding requirements shall be avoided, by using standard terrns and conditions wherever practicable. EXPECTED OUT

45、PUT: Business agreements using standard terms and conditions with no overlap with the project requirements documents. Both shall only specify what is to be achieved not how it shall be done. 4.4.2 Statement of compliance In response to the customers requirements, the supplier shall, in a set of docu

46、ments submitted to the customer, demonstrate his compliance. Both customers documents and supplierk documents shall be amended to reflect the requirements that the supplier shall catifi, as agreed by negotiation. AIM: Ensure that the requirements are adequately defined and documented, and that any d

47、ifference between the contract and those of the proposal are resolved. The suppliers documents will comprise the response to the project requirements documents, .e. implementation documents, and statements of cornpliance. The supplier shall not submit a response in conflict with the national and int

48、ernational laws applicable to the project. Once agreed, the customers business agreement documents shall take precedence over the suppliers documents. EXPELiED OUTPUT: Documented statement of compliance (or otherwise) with the customers requirements. 4.4.3 Contract review The contractor shall establ

49、ish and maintain documented procedures for contract review and for the co- ordination of these activities, in accordance with subclause 4.3 of IS0 9001: 1994. AIM: Allow the contractor to check he has the capability to meet the contract requirements. Page 14 EN 13290-1 1999 The contractor shall perform contract reviews at planned events during project execution, and in particular in connection with contract changes and amendments. EXPECTED OUTPUT: Documented contract review and coordination procedures. 5 Project management 5.1 Objective Project management is a process,