GEIA DMG-2-1989 Automated Data Management Guideline《自动化数据管理指南》.pdf

《GEIA DMG-2-1989 Automated Data Management Guideline《自动化数据管理指南》.pdf》由会员分享，可在线阅读，更多相关《GEIA DMG-2-1989 Automated Data Management Guideline《自动化数据管理指南》.pdf（12页珍藏版）》请在麦多课文档分享上搜索。

1、EIA ENGINEERING PU B LI CATI ON EIA DMG-2 9 = 3234600 OOOLL44 7 / L-c .- -4 i- - -. Automated Data Management Guideline DMG-2 AUGUST 1989 ELECTRONIC INDUSTRIES ASSOCIATION ENGINEERING DEPARTMENT COPYRIGHT Electronic Industries AllianceLicensed by Information Handling ServicesNOTICE EIA Engineering S

2、tandards 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 minimum delay the proper product fo

3、r his particular need. Existence of such Standards and Publications shall not in any respect preclude any member or non-memberof EIA from manufacturing or selling products not conforming to such Standards and publications, whether the standard is to be used either domestically or internationally. Re

4、commended Standards and Publications are adopted by EIA without regard to whether or not their adoption may involve patents on articles, materials, or 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

5、Recommended Standard or Publication, EIA PUBLICATIONS EIA Publications contain information deemed to be of technical value to the industry, and are published at the request of the originating Committee without . necessarily following the rigorous public review and resolution of comments which is a p

6、rocedural part of the development of an EIA Recommended Standard. EIA Publications should be reviewed on an annual basis by the formulating Committee and a decision made on whether to proceed to develop an EIA Recommended Standard on this subject. EIA Publications must be canceled by the Committee a

7、nd removed from the EIA Standards Catalog before the end of their fifth year of existence. COPYRlGHT 1989 Published by ELECTRONIC INDUSTRIES ASSOCIATION 1722 Eye St., N.W. Washington, D.C. 20006 PRICE: $10.00 Printed in U.S.A. All rights reserved COPYRIGHT Electronic Industries AllianceLicensed by I

8、nformation Handling ServicesEIA DMG-2 89 rn 3234600 OOOLL46 O rn DMG-2 PREFACE The present day world of technical advancement sees increasing demands for recorded information. created a new environment in which we must manage and control information. functional responsibilities, we now must be conce

9、rned with electronic storage, retrievability, accessibility, security, efficiency, transmission, data base compatibility, and data media. Our methodology must be modernized to fit into this new environment. Automation has Along with our present Data Management This Automated Data Management Guide ad

10、dresses electronic data management and submittal, Although the basic Data Management requirements remain the same, specific requirements for manual signatures, pagination, specification index page revision records, use of specific government forms, etc., are not consistent with automated techniques.

11、 It will take some time to identify and review required changes and to publish revised Government standards and DIDs. This guide is a ttlivingtt document, revised often to keep current with changed requirements and automated Data Management techniques. This publication, a second in a proposed series

12、 of Electronic Industries Association Data Management Guidelines (see DMG-1 Data Management Guideline dated June 1986) was prepared by the G-33 Data and Configuration Management Committee and Data Management Subcommittee, under the chairmanship of Mr. Dale Willi of Unisys Corporation. i COPYRIGHT El

13、ectronic Industries AllianceLicensed by Information Handling Services. % EIA DMG-2 89 I 3234600 0001147 2 DMG-2 Page 1 AUTOMATED DATA MANAGEMENT GUIDELINE 1.0 SCOPE This document provides guidance in the developing, managing, controlling and transmitting of data in the current electronic environment

14、. 1.1 PURPOSE This document provides guidelines for areas or subjects that must be considered when establishing a capability for electronic data preparations; control, and electronic transmittal/delivery. 2.0 APPLICABLE DOCUMENTS The following documents form a part of this document to the extent spe

15、cified herein: MIL-D-28000 MIL-M-28001 DODD 5230.25 MIL-STD-1840 Digital Representations for Communication of Product Data: IGES Application Subsets Mark-Up Requirement and Generic Style specification for Electronic Printed Output Exchange and Text Withholding of Unclassified Technical Data from Pub

16、lic Disclosure Automatic Interchange of Technical Information COPYRIGHT Electronic Industries AllianceLicensed by Information Handling ServicesEIA DMG-2 89 = 3234b00 OOOL148 4 W DMG-2 Page 2 2.1 REFERENCE DOCUMENTS The following documents are included for reference purposes: 3.0 MIL-R-28002 MIL-D-28

17、003 MIL-M-29532 (EC) MIL-HDBK- 5 9 DATA PREPARATION Raster Graphics Representation in Binary Format, Requirements for Digital Representation for Communication of Illustrated Data: CGM Application Profile Master Library Data Elements (for Technical Publications) , Navy Military Specification Computer

18、-Aided Acquisition and Logistics Support (CALS) Program Implementation Guide 3.1 Source of Data - The source of contractually required electronic data may be new data generated specifically to satisfy the requirements of current contract, existing hard copy data converted to electronic media, or upd

19、ates to previously submitted data. Subsequent updates to submitted data should be in a compatible format. 3.2 Data Format - Whenelectronic control is required, the form(s) (text/graphics) of data shall be considered. The media on which these forms are delivered will include, but not be limited to co

20、mputer output microfilm, magnetic media (such as tapes, disks and diskettes), on-line transmission, video discs and tapes or a combination thereof. form of data is selected, appropriate interface requirements should be applied, such as MIL-STD-1840, to insure transportability and interoperability, a

21、s required. 3.3 Data Base Elements - Categories of data should be prepared for internal functions such as: finance, contracts, logistics, manufacturing, engineering, hardware/software, reliability, maintainability, and data management. For example, data elements supporting data management are: Once

22、the a COPYRIGHT Electronic Industries AllianceLicensed by Information Handling ServicesO O O O O O O EIA DMG-2 89 = 3234600 OOOLL49 b DMG-2 Page 3 Automated document identification numbering system(s) Automated change tracking system Establish and update standard terminology for hardware and softwar

23、e Electronic formatting of existing forms Electronic signature system developed Electronic mail for distribution of changes Automated customer access file 4.0 DATA HANDLING 4.1 Data Base Accessibility - Requirements for electronic data base accessibility are based upon needs for open access and how

24、to restrict those not authorized. Issues concerning data base access must be covered by the contract requirements and internal procedures. 4.2 Marking for Protection - The need to mark for protection must be determined by such requirements as proprietary/intellectual property rights, distribution st

25、atements, and classifications. 4.3 CLASSIFIED DATA SECURITY 4.3.1 Classified In-House Requirements and Controls -1n- house security requirements and suggested guidelines related to computer operators, procedures for handling classified documentation, marking of classified data and transmission, and

26、receiving equipment should be in accordance with in-ho,use policies/procedures and customer guidelines/requirements. 4.3.1.1 Overview - The following should be considered for establishing, operating, and maintaining a secure computing system: o There must be an explicit and well defined policy enfor

27、ced by the system o Individual subjects must be identified (including authorization for access to information) o Audit information must be kept so that actions affecting security can be traced to the responsible party o The computer system must contain mechanisms that can be independently audited o

28、The systems must be protected against tampering and unauthorized change 4-.3.3.,2 Minimum System Requirements - 4.3.1.2.1 Personnel Security - Clearance procedures are covered by Government and company policy/procedures. COPYRIGHT Electronic Industries AllianceLicensed by Information Handling Servic

29、es1 EIA DMG-2 89 3234600 OOOLL50 2 M DMG-2 Page 4 4.3.1.2.2 Procedural Security - Procedures must be established in accordance with Government and specific service standards. Examples : o Classified and marking information o Handling, storage and archiving of media o Computer access security o Reten

30、tion, disposal, or destruction 4.3.2 Government Security Requirements - Data security from unauthorized altering and protection for data of a classified nature must be established. These elements of security must be considered while data resides internal to an agency (contractor or government). Read

31、ily automated data handling and transmission via phone and airways mean that many aspects need to be agreed to and defined such that the participants in a major data base can communicate with each other. The unauthorized altering or reading of privileged data, either from the technical data rights o

32、r security classified aspect, is a concern throughout the computer industry. Further, when such data are being transferred from one system to another, a method of encryption may be necessary. Encryption techniques require standardization to permit for ready communication. Data base size is a concern

33、 since all agencies (contractor or government) are not equipped with resources to handle all demands on a compatible basis. Certainly the individual needs of a related functional area differ such that the equipment used may vary to suit those needs, but the objective still must be to provide for the

34、 integration of data and to assure such integration is cost effective and not redundant. The development of the data base elements and the equipment development and selection process must be tailored toward meeting the objective of an integrated data base. Physical security of information in storage

35、, transmission, and use under ttpaperlesstl conditions must be implemented. Protective schemes have evolved that assure against illegal entry into the storage systems. When stored in the I1paperlesst1 configuration on media different from paper, individual items are not readily marked: entire files

36、are marked. reduced to practice wherein all data stored electronically can be transmitted to another source without human intervention. An entire concept can be Data stored on disk or tape, in which a single page or single paragraph is classified, requires extra attention to assure proper marking an

37、d handling. data requires markings similar to that currently applied, However, the method used to apply these markings and the methods used to transmit the data must be in accordance with contract requirements. All restricted Qr classified COPYRIGHT Electronic Industries AllianceLicensed by Informat

38、ion Handling ServicesEIA DMG-2 89 E 3234600 0001151 4 E DMG-2 Page 5 4.4 Technical Data Rights - Technical data rights and accessibility codes should be predetermined during the proposal and negotiation process. The predetermination agreement must be specifically incorporated in the contract schedul

39、e, unless otherwise specified during negotiations. 4 44.1 Data Management Concerns - Considering the issues and problems previously identified, some primary concerns of the Data Management function in handling data rights are: o Protection from inadvertent and illegal disclosure o Marking restricted

40、 data o Transmitting restricted data o Deliverable data and method o Protection of restricted data upon receipt o Effect upon competition o Limitations imposed upon restricted data o Liabilities that accrue with the acquisition of data o Pricing restricted data consistently and reasonably 5.0 DATA T

41、RACKING 5.1 Automation Requirements - Industry has implemented many automation techniques internal to their operations. Use of word processors, computer-aided design, manufacturing and test tools, the use of personal computers, scanning and digitizing equipment, magnetic media storage devices, etc.,

42、 is prevalent through major Government contractors. with new Government standards that need to be developed, existing Government standards and Data Item Descriptions need to be updated to accommodate automation as they primarily reflect manual methods for data generation and communication. Along 5.1

43、.1 Data Tracking - Automation of data tracking elements must be based on program size, number of data items, delivery requirements, and cost comparisons. The software tool should be capable of automating the labor intensive aspects of data tracking. Candidate data elements for the automation include

44、: Contract Number Data Item Sequence Number Title Responsible Individual Delivery Schedule Generation Status Approval Status Transmittal Letters/DD FORM 250 Dates/NotiEication of Receipt COPYRIGHT Electronic Industries AllianceLicensed by Information Handling ServicesEIA DMG-2 9 m 3234b00 0001L52 b

45、m a DMG-2 ,Page 6 o Forecasting Report o Delinquency Reports o All Aspects of Subcontractor Data Tracking o Distribution statement requirements 5.2 Internal Approval Cycle - Electronic approval must be in accordance with contract requirements and internal procedures. The internal approval cycle proc

46、ess should address the following: o In-series change review could destroy original design, if accessible o Backup approval system o DM does not change data format, content, etc. o Reports go back to originator for changes o Certification of technical data conformity (FAR/DFAR clauses) The following

47、guidelines are.suggested: o Data requiring “Read onlytt approvals must go back to originator for change o Reply via code required to show review by approval authority (negative or positive) o Hard copy capability when available o DM has “read onlytt capability for data validation o Insure FAR clause

48、s on technical adequacy are met through tlOriginal Signed Bytt code o DD Form 250 screen completed in-house 6.0 DATA SUBMITTAL AND APPROVAL 6.1 Data Transmittal - Data transmittal is the formal transfer/exchange of information. data transfer are: Some considerations for o Receipt Confirmation o Tran

49、smission Media o Document Format o Approval Authority for Transmittal a 6.1.1 Submittal - Receipt of internal and external data in the automated environment is accomplished by transmission over electronic systems. Some examples of electronic transfer are: o FAX o Encrypted Lines o Electronic Mail 6.2 BUYER/SELLER INTERFACE 6.2.1 Interface - Interface requirements should be established to insure interoperability and transportability COPYRIGHT Electronic Industries AllianceLicensed by Information Handling ServicesEIA DMG-2 89 3234600 OOOLL53 B t t DMG-2 Page 7 of electronic data tran