1. Module 3 Data Management’s Role in Acquisition
In this module, we will discuss the role of data management in the acquisition process. “Acquisition” used to mean “purchase”. Today, it can mean digital access and even formal delivery and acceptance of data digitally, by organizations and users. Designing and operating the proper DM solution is the outcome of defining a system that meets data requirements, and includes an understanding of factors which condition and enable the scope and range of the DM solution. By understanding the desired outcome, the data manager can structure a solution that is appropriate and effective.

2. Module 3: Data Management and Acquisition
Learning Objectives:
Awareness of DM’s role from contract conception forward
Interpreting guidance to establish good DM methods and processes
Learning Outcomes:
How to define the DM program that meets user needs
Knowing areas of constraint, and special aspects of DM for the lifecycle
Presentation:
A section which addresses awareness of data management’s role from concept to retirement of a system, and the commensurate guidance which provides the focus for a successful solution. The student will be familiar with how a contemporary DM program is developed to sustain user needs, and have working knowledge of the areas which are constrained in that solution, and why.
References:
Principles 2 and 3

3. Acquisition to sustainment focus – data to sustain life cycle needs
DM and Acquisition
DM’s purpose is to identify and provide data
Responsive to customer needs
Digitally, if possible
Acquiring minimum essential data
Access versus acquisition versus acceptance
Premises that are central to contemporary DM
Rules-based processes that present options and sometimes cost consequences for the user
Acquirer and Provider roles
Data delivery can be digital access and data rights can be purchased for digital products
Industry to government
Industry to industry
Government to government
Internally or externally
Customers come from both sources
Ownership versus stewardship role
Format contract or terms of agreement
In the past, data was acquired almost without consideration to cost, use, or obligation. This was due, primarily, to the fact that larger defense budgets provided nearly unlimited funds to procure data – even when it was not necessarily required for the system development effort. It was easier to call for all data to be delivered, in the form of a technical data package. This data was archived against what were often unclear intentions or understanding about the content and the use of that data. As technology and time have evolved, it is possible for data to be acquired digitally, to be accessed without additional costs, to be presented for acceptance – all functions of the traditional data management suite of services. Today, data can be accessed and purchased online, and in the case of additional costs for access, the user clearly sees that costs are levied for data not originally ordered by the acquirer. Data rights are protected through rules-based processes, as is data marking. It is important for the data manager to know that customers are internal or external – and that his or her role is that of a data steward who protects the interests of those who are owners or the data. The broader perspective of DM – which looks from acquisition phase down the road to sustainment of the system in the field.
Acquisition to sustainment focus – data to sustain life cycle needs

4. Alternative Ways to Provide Data
Hard copy
However, increasingly electronic
Access to a database, PDM system, or repository
Data is used through “views”, or mined for information to gain insight and knowledge into program status
Ad hoc reports or standard report formats
“Data product” is a dynamic representation, in this environment
Collaborative development
Iterative data production, review, acceptance, and disposal between the acquirer and the provider
Data planning that is deliberately linked to acquisition strategy and data concept of operations
How the data will be used, for what purposes, and by whom
Data requirements authentication process
Preceded by a risk analysis
What if the data is purchased and no delivery or access is established?
Are there risks in overprocuring data? (obsolete data, insufficient data)
There are several ways to provide data, and all of them incorporate elements of the current digital environment. Data used to be provided in hard copy format, though that is done less frequently today. The costs of hard copies are the primary drivers to digital format alternatives. Dynamic access to data is preferred, allowing for collaboration and exchange of data products during development. The new DM approach also includes forward planning for data, with emphasis on the acquisition strategy, life cycle considerations, and system use. An understanding of these factors assists the data manager to determine the types and formats of data that will be needed. An important part of the contemporary DM model is the risk analysis – which allows a view into whether or not data should be purchased or simply accessed along the life cycle, as well as a determination of whether or not a disproportionate amount of money could be spent on data which becomes obsolete, or which evolves over the life cycle.
New aspects in the contemporary DM model or process

5. Data Acquisition Enablers
Review project strategy
and planning
Establish
general
requirements
for data
Develop data
strategy and
data concept
of operations
Determine
specific data
requirements
Authenticate
data
requirements
Award
contract
for data
Context?
Decision support?
Too early?
Obsolete?
Perform
data risk
analysis
The process includes a review of the project strategy, and an assessment of the general needs and use for data across the lifecycle functions. We begin with establishing the data requirements – usually done through a data call to affected functions and areas within the organization. From a determination of the general requirements, it’s possible to develop a a data strategy, or a mapping of what data will be used by whom. Redundant data needs can be normalized during this step. The data concept of operations allows this mapping to evolve to what formats and frequencies the data should be provided, in order to assist with insight into program development. Specific data requirements emerge to complement the data strategy and concept of operations. Data requirements are then validated, and a risk analysis is needed to determine if and when data should be purchased or accessed, and what point on the timeline the data is sufficiently mature for purchase, if that is the decision made. A formal or working agreement codifies the data requirements to be passed on to the acquiring organization. This exchange of information clarifies the expectations and needs of both the provider and the acquirer of the data, and also allows concrete costs to be assigned and understood.
Review the project strategy and determine the general needs for data
over the product life cycle

6. Assessing Risk Two major considerations Other risk factors
Over-provisioning
Providing data that is not useful or providing data prematurely, to the detriment of its accuracy and potential value
Under-provisioning
Failure to provide data when it is needed
Other risk factors
Inability to retrieve data (bad cataloguing or metadata development)
Loss of data (natural disaster, misplacement, or theft)
Obsolete data (retaining data that has no value)
Compromise of intellectual property
In conducting a risk analysis, there are two major considerations – acquiring too much, or the wrong, data, and failing to provide or acquire data that is critical to life cycle needs (as in data for spares, repairs, or reprocurement needs). Other risk factors range from the inability to retrieve the data, due to poor identification of the data or due to poor management of the data, over time - and the failure to protect data, whether it results from poor marking of the data to ineffective data control, or compromise of data which has been identified and stipulated as competitive edge, intellectual property, or proprietary in nature. The challenge of identifying and protecting data in the digital environment is especially difficult and must be rigorously performed by acquirers and providers, alike.

7. Data Environmental Assessment
Understand
strengths
Understand
threats
Understand
stakeholders
Understand
weaknesses
Understand
opportunities
Understand
power
sources
The data strategy and data concept of operations are key in determining the size, shape, and focus of the DM solution. That’s best done through a look at who wants what solution, to what use, and why. The data environmental assessment measures those factors. From this assessment of constituent elements of the DM solution, a clear understanding of the DM environment emerges.
Understanding
of DM
Environment

8. Quiz Alternative ways to provide data rather than hard copy include ..
Access to a database
Collaborative development environments
Data strategies and data concepts of operation
Data requirements authentication processes
Data is not purchased in industry to industry transactions. True or False?
Developing data strategy and a concept of operations is key to determining solution context.
True or False?
Risk analysis is designed to support buy or access decisions. True or False?
The major considerations in risk assessment for DM are ..
Systems engineering and test and evaluation data needs
Data obsolescence
Theft or other loss of data
Compromise of intellectual property
Underprovisioning or poor planning for the system in the field
All of the above, or none of the above?
Understanding the data environmental factors involves identifying strengths and weaknesses that are present. True or False?