BS ISO 17255-2014 Space systems Programme management Statement of work《空间系统 项目管理 工作状态》.pdf

1、BSI Standards PublicationBS ISO 17255:2014Space systems Programmemanagement Statement ofworkBS ISO 17255:2014 BRITISH STANDARDNational forewordThis British Standard is the UK implementation of ISO 17255:2014. The UK participation in its preparation was entrusted to TechnicalCommittee ACE/68/-/5, Spa

2、ce systems and operations - Programme management.A list of organizations represented on this committee can be obtained on request to its secretary.This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. The British S

3、tandards Institution 2014.Published by BSI Standards Limited 2014ISBN 978 0 580 80663 6ICS 49.140Compliance with a British Standard cannot confer immunity from legal obligations.This British Standard was published under the authority of the Standards Policy and Strategy Committee on 30 June 2014.Ame

4、ndments/corrigenda issued since publicationDate T e x t a f f e c t e dBS ISO 17255:2014 ISO 2014Space systems Programme management Statement of workSystmes spatiaux Gestion de programme Dclaration de travailINTERNATIONAL STANDARDISO17255First edition2014-06-01Reference numberISO 17255:2014(E)BS ISO

5、 17255:2014ISO 17255:2014(E)ii ISO 2014 All rights reservedCOPYRIGHT PROTECTED DOCUMENT ISO 2014All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posti

6、ng on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISOs member body in the country of the requester.ISO copyright officeCase postale 56 CH-1211 Geneva 20Tel. + 41 22 749 01 11Fax + 41 22 749 09 47E-mail copyrightis

7、o.orgWeb www.iso.orgPublished in SwitzerlandBS ISO 17255:2014ISO 17255:2014(E) ISO 2014 All rights reserved iiiContents PageForeword ivIntroduction v1 Scope . 12 Normative references 13 Terms, definitions and abbreviated terms 13.1 Terms and definitions . 13.2 Abbreviated terms . 24 Statement of wor

8、k null Purpose and description . 25 Process for establishing a statement of work 25.1 General . 25.2 Prerequisite for establishing a statement of work . 35.3 Steps for establishing a statement of work 36 Content of statement of work 76.1 Introduction 76.2 Work task requirements description . 86.3 De

9、liverables requirements description . 86.4 Project management requirements description 86.5 Engineering service requirements description .116.6 Product assurance requirements description . 116.7 Access requirements description . 116.8 Verification requirements description 126.9 Operation requirement

10、s description 126.10 Data and documents requirements description .127 General requirements for statement of work .127.1 General 127.2 Responsibility . 127.3 Data management . 127.4 Integrity . 127.5 Configuration management 137.6 Supplementary information . 137.7 Restrictions . 138 Requirements for

11、writing the statement of work .13Annex A (informative) Example of contents of statement of work .14Annex B (informative) Recommendations for the wording of requirements .17BS ISO 17255:2014ISO 17255:2014(E)ForewordISO (the International Organization for Standardization) is a worldwide federation of

12、national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. Inte

13、rnational organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.The procedures used to develop this document and those int

14、ended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of ISO documents should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see ww

15、w.iso.org/directives).Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. Details of any patent rights identified during the development of the document

16、will be in the Introduction and/or on the ISO list of patent declarations received (see www.iso.org/patents).Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement.For an explanation on the meaning of ISO specific terms and expre

17、ssions related to conformity assessment, as well as information about ISOs adherence to the WTO principles in the Technical Barriers to Trade (TBT) see the following URL: Foreword - Supplementary informationThe committee responsible for this document is ISO/TC 20, Aircraft and space vehicles, Subcom

18、mittee SC 14, Space systems and operations.iv ISO 2014 All rights reservedBS ISO 17255:2014ISO 17255:2014(E)IntroductionThis International Standard defines the process and contents of statement of work (SOW) for space systems. The SOW shall define the customer management requirements and activities

19、to satisfy the contract requirements. The SOW is the baseline of business agreement to develop the management requirements of a space system.This International Standard contributes to the satisfaction of quality and on time delivery of space systems, subsystems and components.This International Stan

20、dard provides the significant process and tools to meet the contract management requirements and acts as a supplement to ISO 14300-1.This International Standard helps to develop a statement of work applicable to all types of space systems, all product elements, and projects. ISO 2014 All rights rese

21、rved vBS ISO 17255:2014BS ISO 17255:2014Space systems Programme management Statement of work1 ScopeThis International Standard provides an overview of the purpose and descriptions of statement of work (SOW), its required contents, and process for developing the document.This International Standard i

22、s applicable to all types of space systems, product elements, and projects.2 Normative referencesThe following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated refe

23、rences, the latest edition of the referenced document (including any amendments) applies.ISO 10007, Quality management systems Guidelines for configuration managementISO 10795, Space systems Programme management and quality VocabularyISO 14300-1, Space systems Programme management Part 1: Structurin

24、g of a projectISO 14300-2, Space systems Programme management Part 2: Product assuranceISO 16091, Space systems Integrated logistic supportISO 16192, Space systems Experience gained in space projects (Lessons learned) Principles and guidelinesISO 17666, Space systems Risk managementISO 27026, Space

25、systems Programme management Breakdown of project management structures3 Terms, definitions and abbreviated terms3.1 Terms and definitionsFor the purposes of this document, the terms and definitions given in ISO 10795 and the following apply.3.1.1management requirementformalized statement in the sta

26、tement of work made exclusively to describe what to deliver and to specify the work to be performed, excluding the technical performance3.1.2mission statementdocument expressing the set of collected needsNote 1 to entry: The mission statement is a document established by the customer, which reflects

27、 the users needs, and is used as input to all phases of a space system project.INTERNATIONAL STANDARD ISO 17255:2014(E) ISO 2014 All rights reserved 1BS ISO 17255:2014ISO 17255:2014(E)3.1.3scope statementdocument expressing the project scope, including major deliverables, project assumptions, projec

28、t constraints and a description of work, that provides a documented basis for making further project decisions and for conforming to or developing a common understanding of project scope among the stakeholdersNote 1 to entry: Project scope refers to the work that must be performed to deliver a produ

29、ct, service, or result with the specified features and functions.3.1.4statement of workSOWcontractual document prepared during project initiation and planning that describes what the project shall deliver and outlines all work required to complete the projectSOURCE: ISO 10795:2011, definition 1.2163

30、.2 Abbreviated termsThe following abbreviated terms are defined and used within this document.CM Configuration ManagementPA Product AssuranceILS Integrated Logistic SupportSOW Statement Of WorkWBS Work Breakdown Structure4 Statement of work null Purpose and descriptionA statement of work (SOW) defin

31、es what is to be delivered and to be done by the supplier in terms of requirements, not how to accomplish the work by supplier.The SOW is a valuable tool to capture the work to be done by the supplier for contract management.The SOW is one of the attachments in the business agreement and is consiste

32、nt with all sections of the business agreement.The SOW is the major document in the business agreement which forms the basis for effective management of a project. A SOW serves as the standard for determining if the supplier meets the stated management requirements.The requirements in the SOW are st

33、ated in terms of results needed rather than how to proceed in order to achieve those results.5 Process for establishing a statement of work5.1 GeneralA systematic process for SOW development begins with an analysis of what work is to be performed and the work breakdown into components. It ends with

34、a clear description of output requirements.The process for establishing the SOW should be implemented during Phase A of the systems engineering life cycle.2 ISO 2014 All rights reservedBS ISO 17255:2014ISO 17255:2014(E)5.2 Prerequisite for establishing a statement of workA team shall be set up as th

35、e prerequisite for establishing the SOW. The team should:a) Use work breakdown structure (WBS) in developing the SOW. The requirements for WBS are defined in ISO 27026.b) Ensure that only those tasks which add value to the project are included in the SOW.c) Identify the required documents which prop

36、erly authorize the project and define its basic objectives.d) Prepare a bibliography referring to the specific portions of all applicable specifications and standards with which the project must comply.e) Categorize the work described by WBS into that which will be done by the customer and that whic

37、h needs to be contracted.f) Identify all organizations and persons who will participate in preparing the SOW, and determine the participants areas of responsibility.g) Identify the work and resources which the customer needs to provide during the process that the supplier accomplishes the work.h) Pr

38、epare the SOW following the requirements of this International Standard.5.3 Steps for establishing a statement of workThe process for establishing the SOW should comprise 8 steps. Steps 1 to 4 establish a Preliminary SOW which is used for invitation to tender as a part of the Request For Proposal (R

39、FP). Steps 5 to 8 establish a Final SOW which is used for developing as a part of the business agreement. The 8 steps are as follows:1) Step 1:prepare for establishing SOW;2) Step 2:structure the management requirements;3) Step 3: assess the management requirements;4) Step 4: establish preliminary S

40、OW;5) Step 5: negotiate the management requirements in preliminary SOW with supplier;6) Step 6: adjust and complete the management requirements;7) Step 7: agree on the management requirements;8) Step 8: issue the final SOW.The steps for establishing the SOW are summarized in Figure 1.The outcome of

41、this process is an agreed set of management requirements issued by the customer and to be included in the business agreement for development. ISO 2014 All rights reserved 3BS ISO 17255:2014ISO 17255:2014(E)#a#b#e#f#gcustomerStep 1Prepare for establishing SOWStep 8Issue the g976inal SOWStep 6Adjust a

42、nd complete themanagement requirementsStep 5Negotiate the management requirements InPreliminary SOW with supplierStep 7Agree on the management requirementssupplier#cMission statementNeed analysisLessons learnedWith:#a = Rough management requirements#b= Structured management requirements#c = Accessed

43、 ma nagement requirements#d= Preliminary SOW#e = Management requirements with amendmentfrom the negotiation process#f= Draft of statement of work#g = Agreed draft of statement of workGeneral recommendation for SOWInvitation to tenderSuppliers constraintHistory dataRelevant standardsRelevant standard

44、s#dGeneral recommendation for SOWStep 4Establish the Preliminary SOWStep 3Access the managementrequirementsStep 2Structure the managementrequirementsFigure 1 Steps for establishing a SOW4 ISO 2014 All rights reservedBS ISO 17255:2014ISO 17255:2014(E)5.3.1 Prepare for establishing SOWThe following is

45、 a summary of the procedural steps for preparing a SOW (see Figure 2):a) Establish a preliminary scope statement according to the mission statement and need analysis (i.e. the purpose or objective of procurement): Identify the objective or purpose of the procurement; Describe the work to be performe

46、d; Define the magnitude of work to be performed; Define the boundaries of performance and responsibilities.b) List the tasks to be performed: Group similar and related tasks; Categorize tasks as either major or sub-tasks; Add any additional task.NOTE Take care not to overly constrict the methods whi

47、ch the supplier must use to perform the work.c) Organize the tasks in logical sequence: Chronological order, time-phase, discipline; Ensure that each task required meets each mission requirement; Ensure that no unnecessary or repetitive tasks are included.d) Identify the output (Required results or

48、deliverables): Identify required results or deliverables (products, services, meetings, reports); Ensure that each output has been verified to meet the requirements.e) Identify the input: Identify the required resources for each task (may be labour, equipment and material, documentation); Identify a

49、ny operating restrictions or procedures.f) Identify the time limit or frequency of the deliverables referring to lessons learned and historical data.g) Develop the parameters for acceptable quality referring to lessons learned and historical data: Develop a performance standard or acceptance criteria; Include elements such as “what”, “when”, “where”, “how many times”.h) Determine how to monitor the deliverables referring to lessons learned and historical data: Appropriate for the contract; E