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
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
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
(periodic or incident triggered) . 46 Annex H (informative) Determination of the appropriate
WBS level of detail . 47 Bibliography . 49
Tables Table F-1 :Management Documents Delivery per Review . 45 Table G-1 : Management documents delivery (periodic or incident triggered) . 46
• 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
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 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
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
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
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
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
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 system concepts to comply with the mission statement, SIST EN 16601-10:2015
• the identification of all activities and resources to be used to develop the space and ground segments of the project,
• the initial assessments of technical and programmatic risk, • initiation of pre-development activities. Phases C and D comprise all activities to be performed in order to develop and qualify the space and ground segments and their products. Phase E comprises all activities to be performed in order to launch, commission, utilize, and maintain the orbital elements of the space segment and utilize and maintain the associated ground segment. Phase F comprises all activities to be performed in order to safely dispose all products launched into space as well as ground segment. Each of the above project phases includes end milestones in the form of project review(s), the outcome of which determines readiness of the project to move forward to the next phase. Requirements on organization and conduct of reviews are provided in ECSS-M-ST-10-01. With the exception of the MDR which normally involves only the project initiator, and the top level customer, all other project reviews up to and including the AR are typically carried out by all project actors down to the lowest level supplier in the customer-supplier chain involved in the project phases containing these reviews. From the PRR to the PDR, the sequence of the reviews is “top down”, starting with the top level customer and his top level supplier, and continuing down the customer-supplier chain to the lowest level supplier. From the CDR to the AR, the sequence of reviews is reversed to “bottom up”, starting with the lowest level supplier and its customer and continuing up through the customer-supplier chain to the 1st level supplier and the top level customer. This so called “V model” is illustrated in Figure 4-4. SIST EN 16601-10:2015
• Elaborate the mission statement in terms of identification and characterization of the mission needs, expected performance, dependability and safety goals and mission operating constraints with respect to the physical and operational environment. • Develop the preliminary technical requirements specification. • Identify possible mission concepts. • Perform preliminary assessment of programmatic aspects supported by market and economic studies as appropriate. • Perform preliminary risk assessment. 4.4.3.2.3 Associated review
The mission definition review (MDR) is held at the end of phase 0. The outcome of this review is used to judge the readiness of the project to move into phase A. 4.4.3.2.4 Main review objective(s)
The primary objective of this review is to release the mission statement and assess the preliminary technical requirements specification and programmatic aspects. 4.4.3.3 Phase A (Feasibility) 4.4.3.3.1 Overview This is mainly an activity conducted by the top level customer and one or several first level suppliers with the outcome being reported to the project initiator, and representatives of the end users for consideration. 4.4.3.3.2 Major tasks
• Establish the preliminary management plan, system engineering plan and product assurance plan for the project. • Elaborate possible system and operations concepts and system architectures and compare these against the identified needs, to determine levels of uncertainty and risks. • Establish the function tree. • Assess the technical and programmatic feasibility of the possible concepts by identifying constraints relating to implementation, costs, schedules, organization, operations, maintenance, production and disposal. • Identify critical technologies and propose pre-development activities. • Quantify and characterize critical elements for technical and economic feasibility. • Propose the system and operations concept(s) and technical solutions, including model philosophy and verification approach, to be further elaborated during Phase B. • Elaborate the risk assessment. SIST EN 16601-10:2015
The preliminary requirements review (PRR) is held at the end of Phase A. The outcome of this review is used to judge the readiness of the project to move into Phase B. 4.4.3.3.4 Main review objective(s)
The primary objectives of this review are: • Release of preliminary management, engineering and product assurance plans. • Release of the technical requirements specification. • Confirmation of the technical and programmatic feasibility of the system concept(s). • Selection of system and operations concept(s) and technical solutions, including model philosophy and verification approach, to be carried forward into Phase B. 4.4.3.4 Phase B (Preliminary definition) 4.4.3.4.1 Major tasks • Finalize the project management, engineering and product assurance plans. • Establish the baseline master schedule. • Elaborate the baseline cost at completion. • Elaborate the preliminary organizational breakdown structure (OBS). • Confirm technical solution(s) for the system and operations concept(s) and their feasibility with respect to programmatic constraints. • Conduct “trade-off” studies and select the preferred system concept, together with the preferred technical solution(s) for this concept. • Establish a preliminary design definition for the selected system concept and retained technical solution(s). • Determine the verification program including model philosophy. • Identify and define external interfaces. • Prepare the next level specification and related business agreement documents. • Initiate pre-development work on critical technologies or system design areas when it is necessary to reduce the development risks. • Initiate any long-lead item procurement required to meet project schedule needs. • Prepare the space debris mitigation plan and the disposal plan. • Conduct reliability and safety assessment. • Finalize the product tree, the work breakdown structure and the specification tree. • Update the risk assessment. SIST EN 16601-10:2015
The critical design review (CDR) is held at the end of phase C. The outcome of this review is used to judge the readiness of the project to move into phase D. SIST EN 16601-10:2015
There are 3 project reviews associated with phase D • The qualification review (QR) held during the course of the phase. • The acceptance review (AR) held at the end of the phase. The outcome of this review is used to judge the readiness of the product for delivery. • The operational readiness review (ORR), held at the end of the phase. 4.4.3.6.3 Main review objectives – Qualification review The primary objectives of this review are: • To confirm that the verification process has demonstrated that the design, including margins, meets the applicable requirements. • To verify that the verification record is complete at this and all lower levels in the customer-supplier chain. • To verify the acceptability of all waivers and deviations. Where development encompasses the production of one or several recurring products, the QR is completed by a functional configuration verification during which: • The first article configuration is analyzed from the viewpoint of reproducibility. • The production master files for the series productions are released. • The series production go–ahead file is accepted by the customer. SIST EN 16601-10:2015
There are 4 project reviews associated with phase E. • The flight readiness review (FRR) is held prior to launch. • The launch readiness review (LRR), held immediately prior to launch. • The commissioning result review (CRR), held after completion of the on-orbit commissioning activities. • The end-of-life review (ELR) held at the completion of the mission. 4.4.3.7.3 Main review objectives - Flight readiness review (FRR) The flight readiness review is conducted prior to launch. The objective of this review is to verify that the flight and ground segments including all supporting systems such as tracking systems, communication systems and safety systems are ready for launch. 4.4.3.7.4 Main review objectives - Launch readiness review (LRR) The launch readiness review is conducted just prior to launch. The objective of this review is to declare readiness for launch of the launch vehicle, the space and ground segments including all supporting systems such as tracking systems, communication systems and safety systems and to provide the authorization to proceed for launch. 4.4.3.7.5 Main review objectives - Commissioning result review (CRR) The commissioning result review is held at the end of the commissioning as part of the in-orbit stage verification. It allows declaring readiness for routine operations/utilization. This Review is conducted following completion of a series of on-orbit tests designed to verify that all elements of the system are performing with
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...