SIST EN 16601-10:2015
(Main)Space project management - Project planning and implementation
Space project management - Project planning and implementation
The scope of this ECSS Standard is limited to describing the key elements of project planning and implementation and identifying the top level requirements and products that together provide a coherent and integrated project planning across the 3 ECSS branches.
Where other ECSS management, engineering, or product assurance standards contain more specific and detailed requirements related to project planning, references are provided to identify where these can be found within the ECSS system.
This standard may be tailored for the specific characteristic and constrains of a space project in conformance with ECSS-S-ST-00.
Raumfahrt-Projetmanagement - Projektplanung und Implementierung
Management des projets spatiaux - Planification et mise en œuvre du projet
Vodenje vesoljskih projektov - Načrtovanje projekta in izvedba
Področje uporabe tega standarda ECSS je omejeno na opisovanje ključnih elementov načrtovanja projekta in izvedbe ter opredelitev zahtev in proizvodov na najvišji ravni, ki skupaj zagotavljajo povezano in integrirano načrtovanje projektov v okviru treh vej ECSS.
Kadar drugi standardi ECSS za upravljanje, inženiring ali varnost proizvodov vsebujejo bolj specifične in podrobne zahteve v zvezi z načrtovanjem projektov, se zagotovijo reference za opredelitev, kje jih je mogoče najti znotraj sistema ECSS.
Ta standard se lahko prilagodi posameznim lastnostim in omejitvam vesoljskega projekta v skladu s standardom ECSS-S-ST-00.
General Information
Relations
Standards Content (Sample)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Raumfahrt-Projetmanagement - Projektplanung und ImplementierungManagement des projets spatiaux - Planification et mise en œuvre du projetSpace project management - Project planning and implementation49.140Vesoljski sistemi in operacijeSpace systems and operationsICS:Ta slovenski standard je istoveten z:EN 16601-10:2015SIST EN 16601-10:2015en01-april-2015SIST EN 16601-10:2015SLOVENSKI
STANDARDSIST EN 13290-4:2002SIST EN 13290-3:2002SIST EN 13290-2:20021DGRPHãþD
SIST EN 16601-10:2015
EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM
EN 16601-10
January 2015 ICS 49.140 Supersedes EN 13290-2:2001, EN 13290-3:2001, EN 13290-4:2001
English version
Space project management - Project planning and implementation
Management des projets spatiaux - Planification et mise en œuvre du projet
Raumfahrt-Projetmanagement - Projektplanung und Implementierung This European Standard was approved by CEN on 14 December 2013.
CEN and CENELEC 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 be obtained on application to the CEN-CENELEC Management Centre or to any CEN and CENELEC 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 and CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the same status as the official versions.
CEN and CENELEC members are the national standards bodies and national electrotechnical committees of 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, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom.
CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels © 2015 CEN/CENELEC All rights of exploitation in any form and by any means reserved worldwide for CEN national Members and for CENELEC Members. Ref. No. EN 16601-10:2015 E SIST EN 16601-10:2015
EN 16601-10:2015 (E) 2 Table of contents Foreword . 5 Introduction . 6 1 Scope . 7 2 Normative references . 8 3 Terms and definitions . 9 3.1 Terms defined in other standards . 9 3.2 Terms specific to the present standard . 9 3.3 Abbreviated terms. 10 4 Principles . 11 4.1 Project planning . 11 4.1.1 Introduction . 11 4.1.2 Purpose and objectives of the project. 11 4.1.3 Availability of and need to develop new technologies . 12 4.1.4 Availability of and need to reuse existing equipments/products . 12 4.1.5 Availability of and need
for human resources, skills and technical facilities . 12 4.1.6 Risk assessment . 12 4.1.7 Development approach . 12 4.1.8 Project deliverables . 12 4.1.9 Customer requirements and constraints . 13 4.1.10 Project requirements documents (PRD) . 13 4.1.11 Project management plan . 13 4.2 Project organization . 14 4.2.1 Introduction . 14 4.2.2 Organizational structure . 14 4.2.3 Communication and reporting . 14 4.2.4 Audits . 14 4.3 Project breakdown structures . 15 4.3.1 Introduction . 15 SIST EN 16601-10:2015
EN 16601-10:2015 (E) 3 4.3.2 Function tree . 15 4.3.3 Specification tree . 15 4.3.4 Product tree . 15 4.3.5 Work breakdown structure (WBS) . 16 4.3.6 Work package (WP) . 17 4.3.7 Organization breakdown structure (OBS) . 17 4.4 Project phasing . 18 4.4.1 Introduction . 18 4.4.2 Relationship between business agreements and project phases . 20 4.4.3 Project phases . 20 4.4.4 Project specific reviews . 27 5 Requirements . 28 5.1 Project planning . 28 5.1.1 Overview . 28 5.1.2 Requirements on customers . 28 5.1.3 Requirements on suppliers . 29 5.2 Project organization . 29 5.2.1 Organizational structure . 29 5.2.2 Communication and reporting . 30 5.2.3 Audits . 31 5.3 Project breakdown structures . 32 5.4 Project phasing . 33 Annex A (normative) Project management plan (PMP) – DRD . 34 Annex B (normative) Product tree – DRD . 37 Annex C (normative) Work breakdown structure (WBS) – DRD . 39 Annex D (normative) Work package (WP) description – DRD . 41 Annex E (normative) Progress report – DRD . 43 Annex F (informative) ECSS management branch documents delivery per review . 44 Annex G (informative) Management documents delivery
(periodic or incident triggered) . 46 Annex H (informative) Determination of the appropriate
WBS level of detail . 47 Bibliography . 49
SIST EN 16601-10:2015
EN 16601-10:2015 (E) 4 Figures Figure 4-1: Product tree example . 16 Figure 4-2: WBS example . 17 Figure 4-3: Typical project life cycle . 18 Figure 4-4: Review life cycle . 20
Tables Table F-1 :Management Documents Delivery per Review . 45 Table G-1 : Management documents delivery (periodic or incident triggered) . 46
SIST EN 16601-10:2015
EN 16601-10:2015 (E) 5 Foreword This document (EN 16601-10:2015) has been prepared by Technical Committee CEN/CLC/TC 5 “Space”, the secretariat of which is held by DIN. This standard (EN 16601-10:2015) originates from ECSS-M-ST-10C Rev. 1. 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 July 2015, and conflicting national standards shall be withdrawn at the latest by July 2015. 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. This document has been prepared under a mandate given to CEN by the European Commission and the European Free Trade Association. This document supersedes EN 13290-2:2001; EN 13290-3:2001 and EN 13290-4:2001. This document has been developed to cover specifically space systems and has therefore precedence over any EN covering the same scope but with a wider domain of applicability (e.g. : aerospace). According to the CEN-CENELEC Internal Regulations, the national standards organizations 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, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. SIST EN 16601-10:2015
EN 16601-10:2015 (E) 6 Introduction Project planning and implementation is the project function, encompassing a coherent set of processes for all aspects of project management and control. This is done by:
• establishing the project requirements and constraints derived from the mission statement. • defining phases and formal milestones enabling the progress of the project to be controlled with respect to cost, schedule and technical objectives (i.e. project control function). • defining project breakdown structures, which constitute the common and unique reference system for the project management to: identify the tasks and responsibilities of each actor; facilitate the coherence between all activities of the whole project; perform scheduling and costing activities. • setting up a project organization to perform all necessary activities on the project. SIST EN 16601-10:2015
EN 16601-10:2015 (E) 7 1 Scope
The scope of this ECSS Standard is limited to describing the key elements of project planning and implementation and identifying the top level requirements and products that together provide a coherent and integrated project planning across the 3 ECSS branches. Where other ECSS management, engineering, or product assurance standards contain more specific and detailed requirements related to project planning, references are provided to identify where these can be found within the ECSS system. This standard may be tailored for the specific characteristic and constrains of a space project in conformance with ECSS-S-ST-00. SIST EN 16601-10:2015
EN 16601-10:2015 (E) 8 2 Normative references The following normative documents contain provisions which, through reference in this text, constitute provisions of this ECSS Standard. For dated references, subsequent amendments to, or revision of any of these publications do not apply, However, parties to agreements based on this ECSS Standard are encouraged to investigate the possibility of applying the more recent editions of the normative documents indicated below. For undated references, the latest edition of the publication referred to applies.
EN reference Reference in text Title EN 16601-00 ECSS-S-ST-00-01 Space system – Glossary of terms EN 16001-40 ECSS-M-ST-40 Space project management – Configuration and information management
SIST EN 16601-10:2015
EN 16601-10:2015 (E) 9 3 Terms and definitions
3.1 Terms defined in other standards For the purpose of this Standard, the terms and definitions from ECSS-S-ST-00-01 apply. 3.2 Terms specific to the present standard 3.2.1 discipline specific area of expertise within a general subject NOTE
The name of the discipline normally indicates the type of expertise (e.g. in the ECSS System, system engineering, mechanical engineering, software and communications are disciplines within the Engineering domain) 3.2.2 domain general area of interest or influence covering a number of inter-related topics or sub-areas NOTE
The name of a domain normally indicates the area of interest (e.g. in the ECSS System, the Management, Engineering, and Product Assurance branches represent three different domains). 3.2.3 function combination and interaction of a number of operations or processes, which together achieve a defined objective SIST EN 16601-10:2015
EN 16601-10:2015 (E) 10 3.3 Abbreviated terms For the purposes of this Standard, the abbreviated terms from ECSS-S-ST-00-01 and the following apply. Abbreviation Meaning AR acceptance review B/L baseline CBCP current baseline cost plan CDR critical design review CRR commissioning result review DRL document requirements list EAC estimate at completion EGSE electrical ground support equipment ELR end-of-life review ETC estimate to completion FRR flight readiness review GSE ground support equipment ILS integrated logistic support ITT invitation to tender LRR launch readiness review MCR mission close-out review MDR mission definition review MGSE mechanical ground support equipment N/A not applicable OBCP original baseline cost plan OBS organizational breakdown structure ORR operational readiness review PDR preliminary design review PMP project management plan PRD project requirements documents PRR preliminary requirements review QR qualification review RFP request for proposal RFQ request for quote SRR system requirements review WBS work breakdown structure WP work package SIST EN 16601-10:2015
EN 16601-10:2015 (E) 11 4 Principles 4.1 Project planning 4.1.1 Introduction Project planning and implementation encompasses all of the processes carried out in order to plan and execute a space project from initiation to completion at all levels in the customer-supplier chain in a coordinated, efficient and structured manner. It is a project wide activity receiving inputs from all project disciplines and involving close co-operation across the project domains. A space project typically comprises a space segment and a ground segment which are implemented in parallel (see ECSS-E-ST-70). They rely on, and have interfaces with the launch service segment. These three segments comprise a space system. In principle, a proposal to initiate a space project can be raised by any party. However, the most common initiators are: • individual governments, or co-operation between a number of governments; • national, or international space agencies, either singly or collectively; • national or international scientific communities; • operators of commercial space systems. In this ECSS standard, the top level customer is defined as the organization responsible for generating the top level space segment and ground segment business agreements and for interface arrangements with other external space system elements. The following clauses 4.1.2 to 4.1.11 describe the key elements to be addressed, assessed, and balanced when planning a project. 4.1.2 Purpose and objectives of the project The purpose and objectives of the project are defined by the project initiator in the mission statement which includes key performance parameters and technical and programmatic constraints to be applied to the project. They are normally coordinated with the top level customer, if one has been assigned. SIST EN 16601-10:2015
EN 16601-10:2015 (E) 12 4.1.3 Availability of and need to develop new technologies This is an assessment carried out jointly by the customer and supplier to identify the availability of scientific and technological know-how and the technology needed to implement the project. The result of this assessment, which can be a significant cost and schedule driver, is a major input to the assessment of required resources and facilities and to the subsequent technical and programmatic risk assessment. 4.1.4 Availability of and need to reuse existing equipments/products This is an assessment of the feasibility of reusing existing products and is typically carried out as a direct response to a customer requirement. The result of this assessment, which also can have a significant influence on cost and schedule is a major input to the assessment of required resources and facilities and to the subsequent technical and programmatic risk assessment. 4.1.5 Availability of and need
for human resources, skills and technical facilities This is an assessment carried out jointly by the customer and supplier of the resources, skills and facilities required to implement the project. The result of this assessment shows if required resources, skills and facilities are adequate, or if additional skills, resources, or facilities are needed to complete the project.
4.1.6 Risk assessment The initial assessments of the technical and programmatic risks of a project are carried out by the customer, based on the project initiator’s inputs with respect to the purpose and objectives of the project, together with the identified technical and programmatic constraints to be applied to the project. The initial assessment is subsequently regularly expanded to include other relevant parameters as they become available, and as the project matures. Comprehensive risk assessments are conducted at each major project review. 4.1.7 Development approach The development approach for a project is jointly defined by the customer and supplier to comply with the project initiator’s mission statement, requirements and constraints, and balancing these with the outcome of paragraphs 4.1.3 to 4.1.6 above.
4.1.8 Project deliverables The customer has the responsibility for defining the deliverable products, needed to meet the project initiator’s mission statement, taking into account the assessments noted in clauses 4.1.4 to 4.1.7 above. SIST EN 16601-10:2015
EN 16601-10:2015 (E) 13 4.1.9 Customer requirements and constraints
Customer requirements and constraints are prepared by the customer based on the outputs from 4.1.2 to 4.1.8 above and put into a format suitable for direct application in an invitation to tender (ITT). They address technical and programmatic requirements, as well as political, commercial, and industrial constraints to be applied to the project and collectively represent the project requirements documents (PRD). 4.1.10 Project requirements documents (PRD) The project requirements documents are an integral part of an ITT, request for proposal (RFP), or request for quote (RFQ) prepared and released by a customer to potential suppliers.
The PRD typically comprise • Statement of work • Technical requirements documented in Technical Requirements Specification, as defined in ECSS-E-ST-10-06 • Management requirements • Engineering requirements
• Product assurance requirements • Programmatic requirements • Other, project specific requirements (e.g. geographical distribution, model philosophy to be applied) • Documents requirements list (DRL) • Tender requirements Under the ECSS system, management, engineering and product assurance requirements are contained in the M, E, and Q standards, progressively tailored by each customer in the customer-supplier chain to reflect the type and phase of the project covered by the business agreement, as well as the scope of the suppliers’ tasks required by the PRD. 4.1.11 Project management plan The top level project plan is the project management plan which defines the project management approach and methodology to be used throughout the life cycle of the project, together with an overview of all elements of project management disciplines. It includes the definition of the system engineering and product assurance management approach or provides references to separate system engineering and product assurance plans which together make up the total planning documentation used to implement a project. SIST EN 16601-10:2015
EN 16601-10:2015 (E) 14 4.2 Project organization 4.2.1 Introduction The establishment of a well structured and coherent organizational structure for implementing a project at all levels in the customer-supplier chain is a key factor for ensuring an effective and efficient management approach. At each level in the customer-supplier chain a project organization can be built as a self-standing project team containing all necessary disciplines within the team structure or, more often, can be built around a core project team containing key project functions with other necessary functions being provided from outside the project team as external support. Irrespective of the organizational approach followed for a project, the elements summarized below are relevant at all levels in the customer-supplier chain. 4.2.2 Organizational structure It is essential that the project organizational structure is arranged to include all disciplines essential to implement the project with well defined functions as well as clear reporting lines, inter-relationships and interfaces. All project actors below the top level customer and above the lowest level supplier(s) have the roles of suppliers and customers, and their organizational structures are constructed to accommodate both roles. The organizational structure provides a clear and unambiguous definition and allocation of individual roles and responsibilities together with the necessary authority to implement these within the internal project set–up as well as towards project external interfaces. 4.2.3 Communication and reporting Effective means of communication are essential tools for ensuring clear and efficient inter-action between all project actors, as well as between the project team and its external interfaces. Information technology is the primary means for the exchange of information. Communication serves initially to provide clarity about the project’s goals and objectives and subsequently, to support the day to day work of the project team. Regular reporting is an important tool for exchanging information concerning the progress of the project. 4.2.4 Audits Audits are independent examinations to determine whether processes and procedures achieve the specified objective. They are an essential tool to identify problem areas.
SIST EN 16601-10:2015
EN 16601-10:2015 (E) 15 4.3 Project breakdown structures 4.3.1 Introduction Project breakdown structures provide the basis for creating a common understanding between all actors. They break the project down into manageable elements as described in the following clauses 4.3.2 to 4.3.7. 4.3.2 Function tree The function tree is the breakdown of the system performances into functions. Each function is decomposed into sub–functions independent of the type of products involved. The “function” approach is applied during project start–up or during the system definition phase. More details about the function tree are given in ECSS-E-ST-10, function tree DRD. 4.3.3 Specification tree The specification tree defines the hierarchical relationship of all technical requirements specifications for the different elements of a system or product. More details about the specification tree are given in ECSS-E-ST-10, specification tree DRD. 4.3.4 Product tree The product tree is the breakdown of the project into successive levels of hardware and software products or elements, articulated to perform the functions identified in the function tree. However, the function and the product tree do not necessarily mirror each other. The product tree includes the development models, the GSE, the integration tools and test equipment, and external items necessary to validate the end product and ILS items. It includes items submitted to customer configuration control and items that are the subject of a technical requirements specification. The product tree forms the basis for the elaboration of the project work breakdown structure. An example of a product tree is shown in Figure 4-1.
SIST EN 16601-10:2015
EN 16601-10:2015 (E) 16 Space System Space Segment Ground Segment Payload Platform GSE Mission Control Center Payload Control Center Communications System Structure Thermal control On-board power supply Attitude control Data handling Instrument 1 MGSE EGSE Instrument 2 Instrument 3
Figure 4-1: Product tree example 4.3.5 Work breakdown structure (WBS) The WBS is the principal structure used in managing a project and provides a framework for managing cost, schedule and technical content. It divides the project into manageable work packages, organized according to the nature of the work by breaking down the total work to be performed into increasing levels of detail. The WBS is derived from the product tree, selected elements of which are extended to include support functions (i.e. management, engineering, product assurance) and associated services (e.g. test facilities). An example of a WBS is shown in Figure 4-2. SIST EN 16601-10:2015
EN 16601-10:2015 (E) 17 Space System Space Segment Ground Segment Payload Platform GSE Mission Control Center Payload Control Center Communications System Structure Thermal control On-board power supply Attitude control Data handling Instrument 1 MGSE EGSE Instrument 2 Instrument 3 Management tasksEngineering tasksProduct Assurance tasksSupport function extensions Figure 4-2: WBS example 4.3.6 Work package (WP) A WP can be any element of the WBS down to the lowest level that can be measured and managed for planning, monitoring, and control. Control work packages are identified by the supplier at the level in the WBS where visibility and control is required, and for which reporting is to be performed. The control work packages represent the total work-scope and are agreed by the customer. The work of each supplier is explicitly identified in the work breakdown structure by at least one control work package. 4.3.7 Organization breakdown structure (OBS) The OBS depicts the proposed project organization, including the interface and contractual responsibilities, as opposed to company organization breakdown structure, which depicts the functional aspects of the company. The project OBS shows the key personnel and the assigned responsible parties for each work package in the WBS. SIST EN 16601-10:2015
EN 16601-10:2015 (E) 18 4.4 Project phasing 4.4.1 Introduction The life cycle of space projects is typically divided into 7 phases, as follows: • Phase 0 - Mission analysis/needs identification • Phase A - Feasibility • Phase B - Preliminary Definition • Phase C - Detailed Definition • Phase D - Qualification and Production • Phase E –Utilization • Phase F – Disposal A typical project life cycle is illustrated in Figure 4-3.
Project phases are closely linked to activities on system and product level. Depending on the specific circumstances of a project and the acceptance of involved risk, activities can overlap project phases. At the conclusion of the major activities and the related project reviews configuration baselines are established (see ECSS-M-ST-40). ActivitiesPhasesPhase 0Phase APhase BPhase CPhase DPhase EPhase FMission/FunctionRequirementsDefinitionVerificationProductionUtilizationDisposal MDR PRR SRR PDR CDR QR ARORRFRRLRRCRRELRMCR Figure 4-3: Typical project life cycle
Phases 0, A, and B are focused mainly on
• the elaboration of system functional and technical requirements and identification of sys
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.