1、 i ANSI/AIAA G-043A-2012 (Revision of G-043-1992) Guide American National Standard Guide to the Preparation of Operational Concept Documents AIAA standards are copyrighted by the American Institute of Aeronautics and Astronautics (AIAA), 1801 Alexander Bell Drive, Reston, VA 20191-4344 USA. All righ
2、ts reserved. AIAA grants you a license as follows: The right to download an electronic file of this AIAA standard for storage on one computer for purposes of viewing, and/or printing one copy of the AIAA standard for individual use. Neither the electronic file nor the hard copy print may be reproduc
3、ed in any way. In addition, the electronic file may not be distributed elsewhere over computer networks or otherwise. The hard copy print may only be distributed to other employees for their internal use within your organization. This page is intentionally blank. ANSI/AIAA G-043A-2012 (Revision of G
4、-043-1992) American National Standard Guide to the Preparation of Operational Concept Documents Sponsored by American Institute of Aeronautics and Astronautics In cooperation with the International Council on Systems Engineering Approved July 2012 American National Standards Institute Abstract A rec
5、ognized systems engineering best practice is early development of operational concepts during system development and documentation of those operational concepts in one or more operational concept documents. Recognizing this best practice, U. S. Department of Defense (DoD) and NASA standard procedure
6、s have required that information relating to system operational concepts is prepared in support of the specification and development of systems. In the past, the DoD has published Data Item Descriptions (DIDs), and NASA has published Data Requirements Documents (DRDs), which describe the format and
7、content of the information to be provided. This AIAA Guide describes which types of information are most relevant, their purpose, and who should participate in the operational concept development effort. It also provides advice regarding effective procedures for generation of the information and how
8、 to document it. ANSI/AIAA G-043A-2012 (Revision of G-043-1992) ii Approval of an American National Standard requires verification by ANSI that the requirements for due process, consensus, and other criteria have been met by the standards developer. Consensus is established when, in the judgment of
9、the ANSI Board of Standards Review, substantial agreement has been reached by directly and materially affected interests. Substantial agreement means much more than a simple majority, but not necessarily unanimity. Consensus requires that all views and objections be considered, and that a concerted
10、effort be made toward their resolution. The use of American National Standards is completely voluntary; their existence does not in any respect preclude anyone, whether he has approved the standards or not, from manufacturing, marketing, purchasing, or using products, processes, or procedures not co
11、nforming to the standards. The American National Standards Institute does not develop standards and will in no circumstances give an interpretation of any American National Standard. Moreover, no person shall have the right or authority to issue an interpretation of an American National Standard in
12、the name of the American National Standards Institute. Requests for interpretations should be addressed to the secretariat or sponsor whose name appears on the title page of this standard. CAUTION NOTICE: This American National Standard may be revised or withdrawn at any time. The procedures of the
13、American National Standards Institute require that action be taken to affirm, revise, or withdraw this standard no later than five years from the data of approval. Purchasers of American National Standards may receive current information on all standards by calling or writing the American National S
14、tandards Institute. Published by American Institute of Aeronautics and Astronautics 1801 Alexander Bell Drive, Reston, VA 20191 Copyright 2012 American Institute of Aeronautics and Astronautics All rights reserved No part of this publication may be reproduced in any form, in an electronic retrieval
15、system or otherwise, without prior written permission of the publisher. Printed in the United States of America American National Standard ANSI/AIAA G-043A-2012 (Revision of G-043-1992) iii Contents Foreward . vi 1 Introduction 1 1.1 Purpose . 1 1.2 System . 1 1.3 Operational Concept Document Versus
16、 Concept of Operations Document. 1 1.4 Other Sources 4 1.5 Structure of the Guide 7 2 Scope. 7 3 Tailoring . 7 4 Applicable Documents . 8 5 Vocabulary . 8 5.1 Acronyms and Abbreviated Terms . 8 5.2 Terms and Definitions 9 6 Operational Concepts 12 6.1 Purpose of the OCD. 13 6.2 Operational Concept D
17、ocument in the Development Process . 16 6.3 Perspectives on Operational Concept Analysis . 17 6.4 Operational Concept Documents and Use Cases . 21 6.5 Intended Audience . 21 6.6 When to Generate an OCD 23 6.7 OCD Maintenance . 23 7 Operational Concept Development Guidance 24 7.1 Establish OCD Develo
18、pment Team . 24 7.2 Participants 24 7.3 Generating OCD Content . 25 7.4 Agreed Format and Style . 30 8 Bibliography . 31 Annex A Recommended OCD Content (Informative) . 35 A.1 Scope. 36 A.2 Referenced Documents . 36 A.3 Background Information . 36 A.4 Existing Systems and Operations 37 A.5 Proposed
19、System Operational Overview . 37 A.6 System Overview . 40 ANSI/AIAA G-043A-2012 (Revision of G-043-1992) iv A.7 Operational Processes. 41 A.8 Other Operational Needs . 42 A.9 Analysis of the Proposed System 43 A.10 Appendix A: Acronyms, Abbreviations, and Glossary . 44 A.11 Appendix B: System Operat
20、ional Scenarios . 44 Annex B Background to this Guide (Informative) 46 Figures Figure 1 Single organization-wide concept of operations may lead to many operational concepts. 4 Figure 2 Operational concept grows through the product life cycle. 5 Figure 3 Strategy-to-task-to-need links organization (e
21、nterprise) policies to operational concepts. 16 Figure 4 An operational concept document describes the system and its context with both text and graphics in the users terminology. 17 Figure 5 An effective operational concept document will “tell a story” from the operators users point of view to a wi
22、de and varied audience. . 19 Figure 6 EIA 632 “Building Block” Model provides guidance in determining system scope and boundaries. 26 Figure 7 The key to a successful operations concept document is the development of operational scenarios. 27 Figure 8 Outline for operations concept document. . 31 Ta
23、bles Table A.1 Mapping of annex clauses to OCD sections 35 ANSI/AIAA G-043A-2012 (Revision of G-043-1992) v Change History Change Number Change Date Comments 1 14 December 2010 Ballot Draft 2 2 26 March 2011 Ballot Draft 3 ANSI/AIAA G-043A-2012 (Revision of G-043-1992) vi Foreword This Guide for the
24、 Preparation of Operational Concept Documents (OCD) has been sponsored by the American Institute of Aeronautics and Astronautics (AIAA) as a part of its Standards Program. It is an update and extension of the original ANSI/AIAA Guide (ANSI/AIAA G-043-1992), incorporating new insights, knowledge, and
25、 experience that have been recognized since the Guides original publication. The original Guide was developed by the AIAA Software Systems Committee on Standards and formed a sound foundation for this updated version. This edition of the Guide has been prepared by the AIAA Systems Engineering Commit
26、tee on Standards, the AIAA Software Engineering Technical Committee, and the Requirements Working Group of the International Council on Systems Engineering. At the time that the original Guide was published, various government standards required the generation of operations concept information. The
27、U.S. Department of Defense (DoD) had developed Data Item Descriptions (DIDs), but little information was provided describing the manner in which an Operational Concept Document should be used in support of a system development. No guidelines were provided regarding which information was most useful,
28、 how to develop that information, which developer and customer personnel should participate, or how to document it. Subsequent to the publication of the original Guide, the DoD embarked on a substantial acquisition reform activity, which resulted in the cancellation of many standards that had guided
29、 the development of systems and software in favor of comparable commercial standards. In the same time period, guides to the preparation of Operational Concept Documents were published by the Institute of Electrical and Electronic Engineers (IEEE 1362) and by ISO (ISO 14711:2002 (E). Lastly, many ad
30、vances have been made in the last decade in methods used in systems and software development, not the least of which has been the expansion of object orientation and the development of the Unified Modeling Language (UML) and the Systems Modeling Language (SysML). The original Guide, ANSI/AIAA G-043-
31、1992, was subject to review and revision in 1997. At approximately that time, members of the International Council on Systems Engineering Requirements Working Group (INCOSE RWG) had recognized a need for such a Guide and had begun work on their own document. After discussion between both organizatio
32、ns, the INCOSE RWG and the AIAA Systems Engineering Committee on Standards (SE CoS) decided to work jointly on the revision of the ANSI Guide. In addition, the INCOSE Net-Centric Operations (NCO) Working Group has worked jointly with the AIAA SETC in reviewing the G-043 document. The NCO Working Gro
33、up has concurred with the contents. Although the review and revision process was begun in 1997, it was not completed until 2011. The current Guide for the Preparation of Operational Concept Documents, in addition to including new information, has been broadened to encompass the development of all sy
34、stem types, including software-intensive systems, and to reflect technological advances of the last decade. Development of the current Guide has benefited from the cooperative effort between the AIAA and INCOSE by providing a broad systems-level viewpoint and inclusion of international knowledge, in
35、formation, and experience. This publication is a Guide and contains no normative material. It is informative only. At the time of approval, the members of the AIAA Systems Engineering Committee on Standards were as follows: Satoshi Nagano, Chair The Aerospace Corporation James R. van Gaasbeek, Co-Ch
36、air Northrop Grumman Corporation Michelle Bailey Defense Acquisition University South Dexter Lee Blackstock NASA Langley Research Center ANSI/AIAA G-043A-2012 (Revision of G-043-1992) vii Shirley Brandt Jacobs Engineering John W. Dahlgren MITRE John Eiler Stellar Solutions Howard Estes Estes Researc
37、h Matt French Rolls-Royce Mahantesh Hiremath Space Systems Loral John C. Hsu California State University, Long Beach Stephen Jensen NASA Dryden Flight Research Center Rosemary Matty Arnold Engineering Development Center John C. Muehlbauer Lockheed Martin Aeronautics Company Eric E. Nichols Orbital S
38、ciences Corporation Brian Selvy Pratt and Whitney Rocketdyne William W. Vaughan University of Alabama, Huntsville Tony Williams Jacobs Engineering (NASA Johnson Space Center) The following individuals made particular contributions to the preparation of the document: Kurt Dittmer Northrop Grumman Cor
39、poration Andrew Gabb Consultant Alvaro Gracia Northrop Grumman Corporation Raymond Jorgensen Rockwell Collins Jrme Loubersac Integrate Systems Engineering George Strengers BAE Systems, Australia John Tiehen Northrop Grumman Corporation The AIAA Systems Engineering Committee on Standards (Satoshi Nag
40、ano, Chairperson) approved this document for publication in February 2012. The AIAA Standards Executive Council (Laura McGill, Chairperson) accepted this document for publication in June 2012. The AIAA Standards Procedures provide that all approved Standards, Recommended Practices, and Guides are ad
41、visory only. Their use by anyone engaged in industry or trade is entirely voluntary. There is no agreement to adhere to any AIAA standards publication and no commitment to conform to or be guided by a standards report. In formulating, revising, and approving standards publications, the Committees on
42、 Standards will not consider patents, which may apply to the subject matter. Prospective users of the publications are responsible for protecting themselves against liability for infringement of patents or copyrights, or both. ANSI/AIAA G-043A-2012 (Revision of G-043-1992) 1 1 Introduction 1.1 Purpo
43、se The purpose of this Guide is twofold. First, the Guide describes a time-tested process for operational concept development. Second, it is intended to recommend how to compile the information developed during operational concept development into one or more Operational Concept Documents (OCDs) enc
44、ompassing the full range of the product lifecycle (Haskins, 2010): concept, development, production, utilization, support, and retirement stages. 1.2 System The Operational Concept is prepared initially to support the concept and development stages of the system life cycle. The Operational Concept i
45、s then maintained throughout the Program to support the production, utilization, support, and retirement stages of the system life cycle. As the concept of “system” is central to the Operational Concept and its preparation and maintenance, for the purposes of this Guide, a system is defined as: A co
46、mbination of interacting elements organized to achieve one or more stated purposes. A system may be considered as a product or as the services it provides. In practice, the interpretation of its meaning is frequently clarified by the use of an associative noun (e.g., aircraft system). Alternatively,
47、 the word “system” may be substituted simply by a context-dependent synonym (e.g., aircraft), though this may then obscure the system principles perspective after ISO, 2008. Early in the system development activity, a system is conceptual in nature. As the development effort continues, the system be
48、comes realized in hardware, software, materials, personnel, facilities, and processes. A system may consist of several levels where each element at each lower level may by this definition itself be considered a system (i.e., a subsystem of a large system may itself possess all of the attributes of a
49、 system). 1.3 Operational Concept Document Versus Concept of Operations Document The terms “operational concept” and “concept of operations,” and the terms “operational concept document” and “concept of operations document,” are often used interchangeably in system development. Although there are similarities between the two terms in each set, there are also significant differences. It is important to understand the term “concept of operations” and “operational concept” before trying to understand the terms describing the documents. For the purposes of this Guide
