DATA MANAGEMENT PLAN
This template is meant to assist investigators and their administrative staff in developing a Data
Management Plan consistent with NSF’s requirement, effective January 18, 2011, that all proposals to NSF include
a supplementary document, not to exceed two
will describe how the proposal will conform to the NSF
Data Sharing Policy.
Once a draft of the Data Management Plan has been completed by the investigator or a member of
the research team, before inclusion in the final NSF pro
posal, please forward a copy of that draft Plan to
IT Manager/Staff or (if appropriate)
the LSA Computer Support Group (
The following resources may be
helpful in drafting a Data Management Plan:
NSF Overview of the Dissemination and Sharing of Research Results
NSF Data Sharing Policy:
NSF Data Management Plan Requirements:
NSF Data Management Plan “Frequently Asked Questions”:
University of Michigan Data Sharing Resource Center:
Here are some storage and backup o
this is not a complete list
(LSAIT Systems group)
Contact LSA RSG group.
IT Security and Asset Management
UM Library information on Data Managem
Qualtrics Data Survey (Gloria Love B
rand Administrator for LSA)
Elements of a Data Management Plan
No Detailed Plan is Required:
While all NSF proposals must include a Data Management Plan, for various
reasons a detailed Plan may not be necessary. Oftentimes this occurs because it is not anticipated that the
project will generate data. Regardless of the reason however, if a Plan
asserts that no detailed Plan is
required, it must include a clear justification for why the investigator or the research team reached that
determination. Thus no proposal may include a Data Management Plan that simply states that a plan is
Data Management Plan Template:
NSF has stressed that the content of a successful Data Management Plan will
be determined by peer review and standards that represent best practices for a discipline. However, they have
suggested broad categories of content
, which include:
Types of data, samples, and other materials to be produced in the course of the project.
This section should provide a general overview of the nature of the data or other materials produced under the NSF
sponsored project. These could in
clude data characteristics such as
observational, experimental, reference, derived,
simulated, and/or other.
The data types referenced could include
data generated by computer, data collected from
sensors or instruments, images, audio files, video files,
reports, surveys, patient records, and/or other.
Also, if the
project will be collecting data of a sensitive nature, this should be noted here and will be reflected in subsequent
sections of the Plan.
Standards to be used for data and metadata format and
This section should identify the format in which the data will be stored as well as the types of metadata that will be
included. These standards will often be determined by the accepted best practices of your discipline and should
relevant existing College standards.
Additional resources on this topic will be forthcoming.
for providing access and enabling sharing.
This section should detail the specific mechanisms that will be utilized to provide the requisite
level of access
well as the Disaster Recovery plan
(DR plan should include redundancy, business continuity, and recovery plans as
appropriate for the specific type of data. This could simply be the DR plan of the storage service used for this
deposit in a UM or third party controlled database, posting to a publicly available website,
through direct request to the data steward, etc. If the data is of a sufficiently sensitive nature (human subjects
concerns, potential patentabilit
y, etc.) that general public access is inappropriate, this sections should also articulate
the means by which granular control and access will be achieved
i.e. data requestors will only be able to access
the data provided a data use agreement is first ex
ecuted, data will only be available within a secure virtual network,
etc. To determine the extent of available resources for providing this type of access and control, contact your
departmental IT Manager.
Provisions for re
distribution, and the
production of derivatives.
Similar to the preceding section, here
you should identify
any potential limitations on the data requestor’s ability to
use or re
distribute the data or mat
erials. This could be because of the sort of sensitivity identified a
because the source of some of the data collected for the project has placed limitations on the re
distribution of those
data and materials. Be sure to review any applicable agreements with such parties to determine the extent of re
ribution you are allowed to guarantee in your Data Management Plan.
Methods for archiving and preserving access to data and materials.
In this section identify the means by which the data and materials will be stored to enable future access and sharing
this includes the Disaster Recovery plan, which could be that of the archival service used)
. The duration for which
this access must be maintained will be determined by your discipline’s best practices, but otherwise it should be
anticipated that this is
for an indefinite period of time. Potential solutions include College and University supported
facilities (e.g. Deep Blue, faculty websites, museums and archives) as well as third party options.