REG NASA-HDBK-0008-2012 NASA PRODUCT DATA AND LIFE-CYCLE MANAGEMENT (PDLM) HANDBOOK.pdf

1、 APPROVED FOR PUBLIC RELEASEDISTRIBUTION IS UNLIMITED NASA TECHNICAL HANDBOOK NASA-HDBK-0008 National Aeronautics and Space Administration Approved: 12-17-2012 Washington, DC 20546-0001 NASA PRODUCT DATA AND LIFE-CYCLE MANAGEMENT (PDLM) HANDBOOK MEASUREMENT SYSTEM IDENTIFICATION: NOT MEASUREMENT SEN

2、SITIVE Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NASA-HDBK-0008 APPROVED FOR PUBLIC RELEASEDISTRIBUTION IS UNLIMITED 2 of 75 DOCUMENT HISTORY LOG Status Document Revision Approval Date Description Baseline 12-17-2012 Initial Release Provided by

3、 IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NASA-HDBK-0008 APPROVED FOR PUBLIC RELEASEDISTRIBUTION IS UNLIMITED 3 of 75 FOREWORD This Handbook is published by the National Aeronautics and Space Administration (NASA) as a guidance document to provide enginee

4、ring information; lessons learned; possible options to address technical issues; classification of similar items, materials, or processes; interpretative direction and techniques; and any other type of guidance information that may help the Government or its contractors in the design, construction,

5、selection, management, support, or operation of systems, products, processes, or services. This Handbook is approved for use by NASA Headquarters and NASA Centers, including Component Facilities and Technical and Service Support Centers. It provides information on product data and life-cycle managem

6、ent (PDLM) and general guidance to adapt the methods needed to implement the requirements in NPR 7120.9, NASA Product Data and Life-Cycle Management (PDLM) for Flight Programs and Projects. This Handbook also addresses elements to consider when developing the PDLM Plan so that enablers and users of

7、the product are better equipped to recognize and avoid pitfalls that might otherwise be experienced. Requests for information, corrections, or additions to this Handbook should be submitted via “Feedback” in the NASA Standards and Technical Assistance Resource Tool at https:/standards.nasa.gov. Orig

8、inal Signed By: 12-17-2012 Michael G. Ryschkewitsch NASA Chief Engineer Approval Date Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NASA-HDBK-0008 APPROVED FOR PUBLIC RELEASEDISTRIBUTION IS UNLIMITED 4 of 75 SECTION TABLE OF CONTENTS PAGE DOCUMENT

9、HISTORY LOG . 2 FOREWORD . 3 TABLE OF CONTENTS . 4 LIST OF FIGURES . 6 LIST OF TABLES . 6 1. SCOPE . 7 1.1 Purpose . 7 1.2 Applicability . 9 2. APPLICABLE DOCUMENTS . 10 2.1 General 10 2.2 Government Documents . 10 2.3 Non-Government Documents . 11 2.4 Order of Precedence . 11 3. ACRONYMS, ABBREVIAT

10、IONS, AND DEFINITIONS . 11 3.1 Acronyms and Abbreviations . 11 3.2 Definitions 13 4. PDLM STRATEGY . 17 4.1 Governance . 18 4.2 Technology . 19 5. PDLM FRAMEWORK 20 5.1 Security Architecture 21 5.2 Information Support System Architecture (ISSA) . 21 5.3 5.4 5.5 5.5.1 5.5.2 Data Architecture Process

11、Architecture . Models-Based Design . Models and Simulations (M therefore interoperability from beginning of life to end of life is a staple and a requirement of PDLM. Product data management (PDM) provides key capabilities that underlie product life-cycle management (PLM) and is widely considered a

12、precursor requirement to effective PDLM. PDLM does not negate product data management. A process for management of technical data is required by NPR 7123.1, NASA Systems Engineering Processes and Requirements, for ensuring that the data required are captured and stored, data integrity is maintained,

13、 and data are disseminated as required. PDLM augments PDM and addresses the acquisition and storage of all program/project datanot just technical data used in the life cycle of a system. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NASA-HDBK-0008

14、APPROVED FOR PUBLIC RELEASEDISTRIBUTION IS UNLIMITED 8 of 75 Figure 1Data over the Program/Project Life Cycle (Sample OnlyNot All Inclusive) PDLM consists of disciplined, collaborative processes and systems that plan for, acquire, and control product definition data (PDD) and associated product-rela

15、ted data, including engineering, design, test, procurement, manufacturing, operational, and logistics information throughout the product and data life cycles. PDLM is the set of processes and associated information used to manage the entire life cycle of product data from its conception, through des

16、ign, test, and manufacturing, to service and disposal. To do so requires managing the creation and changes to product definition, product configurations, affiliated engineering data, data on the performance of the product components in mission environments, and product software and hardware. As indi

17、cated in figure 2, PDLM Framework, PDLM is the framework that integrates data, processes (elements), tools, and business systems to provide users with a product information backbone for NASA programs/projects. A life-cycle-oriented approach to PDLM is intended to reduce or eliminate redundant develo

18、pment activities, increase collaborative design and analysis, and reduce time to complete informed decision making throughout the program/project life cycle. PDLM can be implemented using the traditional document-centric approach or with a hybrid approach where both modeling and documents are combin

19、ed to meet the programs/projects PDLM needs. To achieve the highest level of collaboration, interoperability, efficiency, and data availability, the implementation of a fully digital PDLM environment, Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-N

20、ASA-HDBK-0008 APPROVED FOR PUBLIC RELEASEDISTRIBUTION IS UNLIMITED 9 of 75 referred to as a PDLM Collaborative Environment (PCE), as defined in this Handbook, is necessary. PDLM requires that information technology (IT) systems across NASA be made interoperable or integrated to the extent needed to

21、provide a secure, readily accessible environment to enable required collaborative PDLM capabilities. PDLM is intended to increase the probability of mission success by increasing the availability, effectiveness, and efficiency of data interchange and integration across disparate systems and the avai

22、lability of the right data for the right people at the right time, thereby reducing risk. Figure 2PDLM Framework 1.2 Applicability This Handbook is applicable to the following: a. Current and future NASA space flight single-project and tightly coupled programs and their projects subject to NPR 7120.

23、9. b. It is also recommended that this Handbook be considered for guidance in all other NASA programs/projects. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NASA-HDBK-0008 APPROVED FOR PUBLIC RELEASEDISTRIBUTION IS UNLIMITED 10 of 75 This Handbook

24、 is approved for use by NASA Headquarters and NASA Centers, including Component Facilities and Technical and Service Support Centers. This Handbook may also apply to the Jet Propulsion Laboratory or to other contractors, grant recipients, or parties to agreements only to the extent specified or refe

25、renced in their contracts, grants, or agreements. This Handbook, or portions thereof, may be referenced in contract, program/project, and other Agency documents for guidance. When this Handbook contains procedural or process requirements, they may be cited in contract, program/project, and other Age

26、ncy documents. 2. APPLICABLE DOCUMENTS 2.1 General The documents listed in this section are applicable to the guidance in this Handbook. 2.1.1 The latest issuances of cited documents shall apply unless specific versions are designated. 2.1.2 Non-use of specific versions as designated shall be approv

27、ed by the responsible Technical Authority. The applicable documents are accessible via the NASA Standards and Technical Assistance Resource Tool at https:/standards.nasa.gov or may be obtained directly from the Standards Developing Organizations or other document distributors. 2.2 Government Documen

28、ts National Aeronautics and Space Administration NPR 2800.1 NPR 2810.1 NPR 7120.9 NPR 7123.1 NPR 7150.2 NASA-STD-0007 (including the interim version) NASA-STD-7009 Managing Information Technology Security of Information Technology NASA Product Data and Life-Cycle Management (PDLM) for Flight Program

29、s and Projects NASA Systems Engineering Processes and Requirements NASA Software Engineering Requirements NASA Computer-Aided Design Interoperability Standard for Models and Simulations Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NASA-HDBK-0008 A

30、PPROVED FOR PUBLIC RELEASEDISTRIBUTION IS UNLIMITED 11 of 75 2.3 Non-Government Documents None. 2.4 Order of Precedence This Handbook provides guidance on PDLM to adapt the methods needed to implement the requirements in NPR 7120.9 and addresses elements to consider when developing the PDLM Plan but

31、 does not supersede nor waive established Agency requirements/guidance found in other documentation. 3. ACRONYMS, ABBREVIATIONS, AND DEFINITIONS 3.1 Acronyms and Abbreviations 2D two dimensional 3D AP API BOM CAD CAE CAM CDR CGM CIO CM COLLADA COTS CSV DDT generally, these states represent maturity

32、levels or indicate suitability for, or restrictions on, use. (Source: NPR 7120.9, NASA Product Data and Life-Cycle Management (PDLM) for Flight Programs and Projects) Data Management: The process used to: a. Provide the basis for identifying and controlling data requirements. b. Responsively and eco

33、nomically acquire, access, and distribute data needed to develop, manage, operate, and support system products over their product-line life. c. Manage and dispose data as records. d. Analyze data use. e. If any of the technical effort is performed by an external contractor, obtain technical data fee

34、dback for managing the contracted technical effort; and f. Assess the collection of appropriate technical data and information. g. Effectively manage authoritative data that defines, describes, analyzes, and characterizes a product life cycle. h. Ensure consistent, repeatable use of effective PDLM p

35、rocesses, best practices, interoperability approaches, methodologies, and traceability. (Source: NPR 7123.1, NASA Systems Engineering Processes and Requirements) Data Model: Identifies the data, their attributes, and relationships or associations with other data. (Source: Department of Defense Direc

36、tive 8320.03, Unique Identification (UID) Standards for a Net-Centric Department of Defense, March 2007) Delivery: Applies to the hand-off, which may be physical or virtual in the case of data, at initial delivery of an item during development, for collaboration, in support of reviews, at the time o

37、f acceptance, and for subsequent modifications, maintenance, refurbishment, or any other Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NASA-HDBK-0008 APPROVED FOR PUBLIC RELEASEDISTRIBUTION IS UNLIMITED 15 of 75 activity that produces new data. (So

38、urce: NPR 7120.9, NASA Product Data and Life-Cycle Management (PDLM) for Flight Programs and Projects) End Item: A product to be delivered under contract as an intact unit or to be assembled, completed, and made ready for use as a unit. (Source: NPR 7120.9, NASA Product Data and Life-Cycle Managemen

39、t (PDLM) for Flight Programs and Projects) Engineering Release: An action whereby engineering documentation or an item is officially made available for the intended use. (Source: Modified from NASA-STD-0005, NASA Configuration Management (CM) Standard) Firmware. The combination of a hardware device

40、and computer instructions and data that reside as read-only software on that device. Notes: (1) This term is sometimes used to refer only to the hardware device or only to the computer instructions or data, but these meanings are deprecated. (2) The confusion surrounding this term has led some to su

41、ggest that it be avoided altogether. (Source: IEEE-STD-610.12-1990, IEEE Standard Glossary of Software Engineering Terminology) Governance Model: The frameworkprinciples and structuresthrough which the Agency manages the mission, roles, and responsibilities. (Source: NPD 1000.0, NASA Governance and

42、Strategic Management Handbook) Metadata: Data about data, including information describing aspects of actual data items, such as name, type, format, content, and other descriptive information. (Source: NPR 7120.9, NASA Product Data and Life-Cycle Management (PDLM) for Flight Programs and Projects) M

43、odel: A description or representation of a system, entity, phenomena, or process. (Source: NASA-STD-7009, Standard for Models and Simulations) Product: A part of a system consisting of end products that perform operational functions and enabling products that perform life-cycle services related to t

44、he end product or a result of the technical efforts in the form of a work product (e.g., plan, baseline, or test result). (Source: NPR 7123.1, NASA Systems Engineering Processes and Requirements) Note: Products include, but are not limited to, spacecraft, launch vehicles, instruments, payloads, soft

45、ware, launch platforms, and other elements that are necessary components to deliver a completed vehicle. Product Breakdown Structure: A hierarchical view of the relationship of products and component products. (Source: NPD 7120.4, NASA Engineering and Program/Project Management Policy) Product Data

46、and Life-Cycle Management (PDLM) System: A combination of the information technology applications, users, and processes that implement the management of product data across the product life cycle. (Source: NPR 7120.9, NASA Product Data and Life-Cycle Management (PDLM) for Flight Programs and Project

47、s) Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NASA-HDBK-0008 APPROVED FOR PUBLIC RELEASEDISTRIBUTION IS UNLIMITED 16 of 75 Product Data Management (PDM): The framework that enables organizations to manage and control engineering and technical in

48、formation, specifically data surrounding the products design, definition, and related engineering, manufacturing, and logistics processes and is a key element of PLM. Note: From the product perspective, PDM organizes data required for design evolution, tracks versions and configurations of evolving design concepts, and manages archived data and other product-specific information. PDM tools provide access to product structures and other engineering data such as requirements, as-built, and safety and mission assurance data. From the process perspective, PDM systems offer the ca