1、EIA DMG-3 6 32346000003333 7 JANUARY 1986 DATA MANAGEMENT IMPLEMENTATION .GUIDE Engineerng Deportment ELECTRONIC INDUSTRIES ASSOCIATION 2001 EYE STREET, N.W. WASHINOTON, D.C. 20006 -_ COPYRIGHT Electronic Industries AllianceLicensed by Information Handling ServicesNOTICE b EIA DMG-1 b = 3234600 0001
2、114 9 S 1 EIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimm d
3、elay the proper product for his particular need. Existence of such Standards and Pub- lications shall not in any respect preclude any member or non-member of EIA from manufacturing or selling products not conforming to such Standards and Publications, nor shall the existence of such Standards and Pu
4、blications preclude their voluntary use by those other than EIA members, whether the standard is to be used ei ther domestically or internationally. Recommended Standards and Publications are adopted by EIA without regard to whether or not their adoption may involve patents on articles, materials, o
5、r processes. By such action, EIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Recom- mended Standard or Publication. Published by b ELECTRONIC INDUSTRIES ASSOCIATION Engineering Department 2001 Eye Street, N,W. Washington, D.C.
6、 20006 Printed in U.S.A. ? COPYRIGHT Electronic Industries AllianceLicensed by Information Handling ServicesY b- -* EIA DMG-L b m 3234600 OOOLlL5 O m DMG- 1 PREFACE To the reader, this publication may appear to have been prepared solely to provide guidance for companies doing business withthe Depart
7、ment of Defense (Don). The DoD,as the largest procurer of data, has the greatest number of regulations governing the acquisition of data, and, therefore, presents the most problems to the data provider, principles which apply to all data acquisitions and their implementation can Such is not the case
8、. However, be tailored to satisfy various customers. The present day world of technical advancement sees increasing demands for recorded information. technical ideas, presents plans for developing them, gives instructions to those who will build, operate and service hardware, records the results of
9、technical performance tests and evaluation, and provides visibility for managing technical and business aspects that are necessary to assure program success. As the volume of recorded information has increased, there has been a growing effort to limit, organize, improve, and control the recorded inf
10、ormation. effort has resulted in customer requirements for a separately identified This documentation provides a means for communicating O This activity that has been given the label of Data Management. This publication was prepared by the 6-33 Data and Configuration Management Committee under the c
11、hairmanship of-Mr. John Hart of Boeing Aerospace Company. COPYRIGHT Electronic Industries AllianceLicensed by Information Handling Services EIA DMG-L b = 3234b00 OOOLLLh 2 DATA MANAGEMN“ IMPLEMENATION GUIDE TABLE OF CONTENTS Paragraph SECTION 1: DATA MANAGEMENf 1.1 Introduction 1.2 What is Data Mana
12、gement? 1.3 Data Responsibility and th Data Manager 1.4 Magement of Contractor Data and Reports 1.5 Data Requirement Identification and the Program Life 1.6 The Relationship Between the Statement-of -Work and Contract Data Requirements List Cycle SECTION 2: DATA TOPICS 2.1 Deferred Types of Data 2,2
13、 Reprocurement Data 2.3 Federal Acquisition Regulations (FARs) - Dob FAR Supplement 2.4 Pricing Data 2.5 Rights in Data and Computer Software 2.6 Assuring the Data Quality 2.7 Subcontractor Data SECTION 3: SCIENTIFIC AND TECHNICAL INFORMATION 3.1 STINFO and Data Management SECTION 4: DEFINITIONS 4.1
14、 Acquisition 4.2 Acquisition Management Systems and Data Requirements 4.3 MDL Document 4.4 I Acquisition Management System Control (AMSC) Number 4.5 Administrative Data 4.6 Application 4.7 Application Process 4.8 Content 4.9 Contract 4.10 Contract Data Requirements List CDRL, DD Form 1423 4.11 Contr
15、actor 4.12 Contractual Data Rwuirement 4.13 Data 1 4.14 Data Generating Requirements 4.15 Data Item Description DID) DD Form 1664 4.16 Data Product 4.17 DoD FAR Supplement 4.18 Defense Standardization and Specification Program (DSSP) 4.19 Deliverable Data 4.20 DoD Component Control List (AMSDL) Page
16、 1 1 1 4 4 8 10 13 13 14 14 15 15 16 17 17 19 20 20 * 20 20 20 20 21 21 21 21 21 21 22 22 22 22 22 22 . 22 22 23 i COPYRIGHT Electronic Industries AllianceLicensed by Information Handling ServicesEIA DMG-L b m 3234600 OOOLLL7 4 m Paragraph 4.21 4.22 4.23 4.24 4.25 4.26 4.27 4.28 4.29 4,30 4.31 4.32
17、4.33 4.34 4.35 4.36 4.37 4.38 4.39 4.40 4.41 4.42 4.43 TABLE OF cX“S (cant) Page DoD Data Management Focal Point DoD Index of Specifications and Standards (DaDISS) DoD AMSDL Clearance Officer Executive Branch Financial Branch Form Format Functional Area Assignments Lead Service Lead Service Activity
18、 Management Data Military Specification Military Standard Office of Management and Budget (OMB) 4B Number and EWATE Office of Primary Responsiblity (OPR) Preparing Activity (PA) Project Public Law or Law Revised DID Source Document Tailoring of Data Requirements Technical Data FIGURES Figure 1-1 Con
19、tract Data Requirements List, DD Form 1423 Figure 1-2 Types of Data Figure 1-3 Typical Data Flow - Proposals Figure 1-4 Typical Data Flow - Contract Signed Figure 1-5 Data Item Description, DD Form 1664 . Figure 2-1 Typical Subcontractor and to produce, sup- port, operate, maintain, and display defe
20、nse material. Data also supports research, engineering development, production, cataloging, procurement, training, deployment, maintenance,.and related logistics functions. The term “data“ includes all administrative, management, financial, scientific, engineering, and logistics inforharion .- that
21、are generated during performance of a contract. For this guide and for clarity,dataacquired from a contractor via a DD Form 1423 Contract Data Requirements List (CDRL), (Figure 1-i), as a part of system/equipment procurements are essentially anything other than hardware, firmware, or computer progra
22、ms depicted by Figure 1-2. The term “technical data“ is further defined in Federal Acquisition Regulations (FAR) 27.401. 1.2 What fs Data Management? The Data Management function is defined as allows: Data Management is the process of applying policies, systems, and procedures for identification and
23、 control of data requirements; or the timely and economical development of those data, the preparation of which satisfies specific criteria; or assuring the adequacy of such data for full compliance with the contract and for its intended 1 COPYRIGHT Electronic Industries AllianceLicensed by Informat
24、ion Handling Servicesc s DMG 1 EIA DMG-1 6 m 323LIbOO OOOLlL9 B m f L Figure 1-1. Contract Data Requirements List, DD FORM 1423 2 COPYRIGHT Electronic Industries AllianceLicensed by Information Handling ServicesEIA DMG-1 b 3234600 O001120 4 M L. DMG-1 MOTION TCHNICAI MANUALS TCTCIS for the distribut
25、ion or communication of the ata to the point of use; and for use analysis. procured from suppliers and that developed by thepontractor. These responsibilities cover both data O The adequacy of technical data and information submitted in fulfillment of contractual data requirements should be determin
26、ed by the contractor prior to submittal to the customer. Determination that data is complete, accurate, and in compliance with applicable standards is confirmed by an acceptable contractor data management system with government and/or higher tier contractor sur- veillance and review. 1.3 Data Respon
27、sibility and the Data Manager Now that the objectives and the requirements for a Data Management function have been established, the function itself must be defined. The increasing quantity and complexity of contractually required deliverable data may require that for- mal imposition of Data Managem
28、ent be applied to those programs responding to CDRL requirements. Since company policies vary, it is not possible to prescribe where the Data Management function should fit into any companys organizational structure. Figures 1-3 and 1-4 illustrate how the typical Data Management func- tion may relat
29、e to performing organizations during the proposal and contract phases A Data Manager, either full-time or part-time, depending on the magnitude of the program/project is generaly appointed to insure that specified company func- tions perform required data management tasks or to accomplish the requir
30、ed tasks utilizing assigned personnel, or this function may be subcontracted. The Data Manager should work with and look to the technical/functional managers to accomplish their data tasks within schedule and budget and should work clo- sely with contracts administration. Once the requirements are o
31、n contract, the Data Manager administers and monitors the preparation and submittal of the data to insure adequacy and timely delivery. O While the Data Manager is the catalyst for Data Management, all technical/ functional managers who are responsible for generating data and contract admi- nistrati
32、on personnel who negotiate the contract and modifications, share in the responsibility of data management. 1.4 Management of Contractor Data and Reports The Data Management activity must see to.it that several functions are carried out during the program. These include: Identification - The total da
33、ta requirements for each contract must be identified to the pro ject/program. listing which defines each requirement and assigns the requirement to a specific organization/person responsible for performing This normally accomplished via a Justification - Each data item must be examined for cost effe
34、ctiveness and each documentation requirement must be examined to avoid duplication 4 COPYRIGHT Electronic Industries AllianceLicensed by Information Handling ServicesEIA DMG-1 6 m 3234600 OOOl1122 i.e., the list should be boiled down to the essential items and the final selection assures the adequac
35、y of the recorded information for the needs of the program. Acquisition - Each required data itm.must be acquired from ihat portion of the company organization best suited to provide it in a timely and economi- cal. manner, or to supervise its procurement from subcontractor or suppliers organization
36、s. Each item or sub-item of data is scheduled for delivery from a designated responsible organization, in much.the same manner as the delivery of hardware is scheduled. The list should identify each justifiable . Control 0 For many years progress in the development, manufacture, and delivery of cont
37、ract hardware has been tracked by the use of “control“ methods of various types, These “controls“,prouide management with the. visibility necessary for informed management judgement. for the preparation and delivery of contract data items must now be pro- vided . Similar “control“ Since data is gene
38、rated by many activities, central control and authority within the company or within each program/prject is necessary to achieve uniformity and timely submittal of data. Withthe establishment of a function, a charter and responsibilities of the Data Manager can be promulgated. The responsibilities o
39、f the Data Manager include the tiame responsibilities that all managers have but those that relate solely to the managing of data include: 1, 2. 3, 4. 5. 6 7, Reviewing the customers data requirements list, contract provisions and statement of work for data items and data management tasks. Designati
40、ng a function responsible for each data item and discuesing the requirements with each fesponsible function far setting up methods for preparation aiid publication of the required data. - Preparing Data Management: plans as required. Establishing procedures and coiitrols to ensure the preparation, r
41、eview, approval, publicatioa; and submittal of timely, economical, quality data. Reviewing all data to be delivered to verify that it is complete and, except for technical conteht, complies with the contract requirement. This review must be Coordinated with the originator and nonconforming data retu
42、rned to originator for rework. Assisting in the preparation of recommended Contract Data Requirement Lists (CDRLs) for customer consideration for draft Request for Proposals (RFPs) and multi-year procurements. Developing Supplier Data Requirement Lists (SDRLsr and Data Item Descriptions (DIDS) for i
43、nelusion in subcontracts and purchase orders 7 COPYRIGHT Electronic Industries AllianceLicensed by Information Handling ServicesEIA DMG-Ii b m 323YbOO OOOLL25 3 m DMG- 1 8. Establishing procedures to ensure that supplier data meets the same quality, format, and timeliness requirements as prime contr
44、actor generated data. Preparing and publishing master contract dam delivery schedules depicting all data requirements. Maintaining records showing delivery performance and report to management as required. O 9. 10. Assisting in establishing the work breakdown structure for data items to ensure that
45、adequate funds are allocated to each data item in con- sonance with the items established price group. and monitoring costs for each data element throughout the period of performance to ensure the production of quqlity data. Distributing funds 11. Establishing and maintaining a data repository for a
46、ll program data except drawings and computer tapes/disks/cards. latter are properly stored and maintained. Ensuring the proper preparation of letters of transmittal and/or DD Form 250 which transmit all contractual data to the customer. Ensuring that these 12. The end result of Data Management shoul
47、d be the delivery of quality data in a timely manner at the lowest possible cost to the customer. should be each companys policy to tailor the Data Management organization in depth and in application to the need of that company and to the particular phase of the program. Each program should be revie
48、wed on a regular basis to ensure that the data is generated at the lease cost and is delivered on schedule. Where an existing company organization has responsibility for a function (e.g., quality is responsible for data inspection) the function should not be reassigned to Data Management automatical
49、ly. To this end, it 1.5 Data Requirement Identification and the Program Life Cycle Data Management begins with the conceptual phase of a program and continues through the life cycle of the program. During the life cycle of the program requirements for data vary from at least a final report for the conceptual phase to detailed and extensive requirements for the full scale development and pro- duction phase. All requirements for data are identified by the goverqment Data Management Officer (DMO). The DMO accomplishes this by issuing a data
