Technical Data Management
Data management is the process of applying policies, systems and procedures for identification and control of data requirements; for the timely and economical acquisition of such data; for assuring the adequacy of data for its intended use; for the distribution or communication of the data to the point of use; and for use analysis.
Data management documents and maintains the database reflecting system life cycle decisions, methods, feedback, metrics, and configuration control. It directly supports the configuration status accounting process. Data Management governs and controls the selection, generation, preparation, acquisition, and use of data imposed on contractors.
DoD Instruction 5000-2R says that System Analysis and Control activities shall include an integrated data management system to capture and control the technical baseline (configuration documentation, technical data, and technical manuals); provide data correlation and traceability among performance requirements, designs, decisions, rationale, and other related program planning and reporting elements; facilitate technology insertion for affordability improvements during reprocurement and post-production support; support configuration procedures; and serve as a ready reference for the systems engineering effort.
Data are the "knowledge products" of the acquisition process, as well as the sustainment process. They are the basis for most, if not all acquisition, design, development, production, operation, support, and maintenance decision-making. Being able to access the right data at the right time to make the right decisions does not happen by chance. Nor does it happen as a result of ordering excessive data, just in case.† Rather, it is the product of an effective data management process.
Technical data is recorded information (regardless of the form or method of recording) of a scientific or technical nature (including computer software documentation.)† Technical Data:
The more common technical data products are:
A Technical Data Package is a technical description of an item adequate for supporting an acquisition strategy, production, engineering, and logistics support.† The description defines the required design configuration and procedures required to ensure adequacy of item performance.† It consists of all applicable technical data such as drawings and associated lists, specifications, standards, performance requirements, quality assurance provisions, and packaging details.† A Technical Data Package normally contains:
Planning for Technical Data Management commences early in the program concurrently with developing the strategy and concepts for Configuration Management, Acquisition Logistics Support, and Maintenance Concepts.
Prior to preparing a contract Statement of Work (SOW), a data call elicits data requirements to be incorporated into the SOW and the Contract Data Requirements List (CDRL).
The entire Program Management Team participates in determining data requirements and in preparing the contracting documentation.† Someone on the Project Team should be designated the Data Manager to oversee the contractor preparation and delivery of the required data items and to determine their acceptability.
Terms and Definitions:
Web Sites for Discretionary References:
Data Required By Contract
Data is defined as recorded information, regard-less of form or characteristic, and includes all the administrative, management, financial, scientific, engineering, and logistics information and documentation required for delivery from the contractor. Contractually required data is classified as one of three types:
Data is acquired for two basic purposes:
Data analysis and management is expensive and time consuming. Present DoD philosophy requires that the contractor manage and maintain significant portions of the technical data, including the Technical Data Package (TDP).† Note that this does not mean the government isnít paying for its development or shouldn't receive a copy for post-delivery use. Minimize the TDP cost by requesting the contractor's format (for example, accepting the same drawings they use for production), and asking only for details on items developed with government funds.
Data Call for Government Contracts
As part of the development of an Invitation for Bid or Request for Proposals, the program office convenes the Program Management Team (IPPD Process) and presents the planned procurement and asks integrated team members and affected functional managers to identify and justify their data requirements for that contract. A description of each data item needed is then developed by the Program Management Team and reviewed by the Program Manager. Data Item Descriptions, located in the Acquisition Management Systems Data List (AMSDL) can be used for guidance in developing these descriptions.
Concurrent with the DoD policy on specifications and standards, there is a trend to avoid use of standard Data Item Descriptions on contracts, and specify the data item with a unique tailored data description referenced in the Contract Data Requirements List.
The Statement of Work, CDRL, and Tracking Tool (SCATT) is available within MARCORSYSCOM (http://www.marcorsyscom.usmc.mil/sites/scatt/) to assist in the preparation of the SOW and the CDRL.
Acceptance and Use of Contractor Data Deliverables
A member of the Program Management Team should be designated the Data Manager to monitor the contractor preparation and delivery of required Technical Data.† This should include the following:
Use of a Contractor Integrated Technical Information System (CITIS)
Technical data does not have to be delivered in hard copy in most cases.† Also, it is not always necessary for the Government to physically maintain storage of the delivered information.†
The application of CITIS on the contract can provide a combined Government/Contractor database where all authorized persons can access data they need.† In order for the contractor to propose and provide an acceptable CIIS, the solicitation must include the Government Concept of Operation (GCO) and data interface requirements.† Assistance for preparation of the GCO can be found in the DoD Deskbook; an extract is included in this Navigator.
At the end of the contract, the Government should take custody/possession of the technical data in the CITIS.
Engineering Drawings versus Provisioning Documentation
Engineering Drawings are prepared to the Level of Design while Engineering Data For Provisioning (EDFP) is prepared to the level of maintenance or support.
With the procurement of fewer design drawings, EDFP should be retained [not discarded after National Stock Numbers (NSN) are assigned] and cross checked with the Engineering Drawings to assure that the CSA database has as much information as it needs to assure re-supply activities during the systemís Operation and Support Phase.
In developing acquisition strategies, acquisition program managers should ensure data management expertise is included in all such efforts in order to ensure the: