The development of technical data is an inherent part of the engineering design, development and manufacturing of products. The acquisition and management of technical data has become innate to the way the Department of Defense (DOD) acquires and manages weapon systems. New business practices that use digital methodologies and products have demonstrated cost savings, process improvements, and expanded capability for interoperability. DoD has expressed goals for an interoperable digital logistics product/technical data environment to improve warfighter support, and reduce the total costs to operate and maintain defense systems. IETMs, or Interactive Electronic Technical Manuals, provide dialog driven interaction with the user, guided diagnostic troubleshooting & fault isolation, and integration with training and other logistics support functions.
A number of important things related to technical data rights and data management strategies (DMS) have transpired since July 2006, including:
1) issuance of a 3 May 06 Secretary of the Air Force Memo "Data Rights and Acquisition Strategy"
2) issuance of a Jul 06 GAO Report "Weapons Acquisition: DOD Should Strengthen Policies for Assessing Technical Data Needs to Support Weapon Systems"
3) passage of Congressional Language in PL 109-364, FY07 John Warner National Defense Authorization Act
4) issuance of USD AT&L 19 July 07 Policy Memo "Data Management and Technical Data Rights" requires Program Managers to assess long-term technical data requirements for all ACAT I and II programs, regardless of the planned sustainment approach and reflect that assessment in a Data Management Strategy (DMS).
5) Data Management and Technical Data Rights verbiage is being added to the next update of the DoD Instruction 5000.02
6) issuance of a DFARS Interim Rule Issued 6 Sep 07
In order to encourage creative and well-thought out Data Management Strategy (DMS) (which may well include access vice procurement of data) development, DoD has not issued a standard DMS format/template. However according to the OSD staff, as a minimum, a DMS should address:
-- Discussion of specific data items required to be managed throughout the program's life cycle
-- Design, manufacture and sustain the system
-- Re-compete for production, sustainment or upgrade
-- Program's approach to managing the data during acquisition and sustainment (i.e. access, delivery, format)
-- Contracting strategy for technical data and intellectual property rights
-- Includes requirements/need for a priced option
-- Discussion of any unique circumstances
See also the Acquisition Logistics Technical Data site, the DAU Data Management (DM) Community of Practice (CoP) , and the Air Force Technical Order site for additional information.
