
% APPENDIX 6: DATA MANAGEMENT PLAN

% Provide a Data Management Plan (DMP) that addresses the following requirements:

% 1. DMPs should describe whether and how data generated in the course
% of the proposed research will be shared and preserved. If the plan is
% not to share and/or preserve certain data, then the plan must explain
% the basis of the decision (for example, cost/benefit considerations,
% other parameters of feasibility, scientific appropriateness, or
% limitations discussed in #4). At a minimum, DMPs must describe how
% data sharing and preservation will enable validation of results, or
% how results could be validated if data are not shared or preserved.

% 2. DMPs should provide a plan for making all research data displayed
% in publications resulting from the proposed research digitally
% accessible to the public at the time of publication. This includes
% data that are displayed in charts, figures, images, etc. In addition,
% the underlying digital research data used to generate the displayed
% data should be made as accessible as possible to the public in
% accordance with the principles stated in the Office of Science
% Statement on Digital Data Management
% (http://science.energy.gov/funding-
% opportunities/digital-data-management/). This requirement could be met
% by including the data as supplementary information to the published
% article, or through other means. The published article should indicate
% how these data can be accessed.

% 3. DMPs should consult and reference available information about data
% management resources to be used in the course of the proposed
% research. In particular, DMPs that explicitly or implicitly commit
% data management resources at a facility beyond what is conventionally
% made available to approved users should be accompanied by written
% approval from that facility. In determining the resources available
% for data management at Office of Science User Facilities, researchers
% should consult the published description of data management resources
% and practices at that facility and reference it in the
% DMP. Information about other Office of Science facilities can be found
% in the additional guidance from the sponsoring program.

% 4. DMPs must protect confidentiality, personal privacy, Personally
% Identifiable Information, and U.S. national, homeland, and economic
% security; recognize proprietary interests, business confidential
% information, and intellectual property rights; avoid significant
% negative impact on innovation, and U.S. competitiveness; and otherwise
% be consistent with all applicable laws, regulations, and DOE orders
% and policies. There is no requirement to share proprietary data.

% DMPs will be reviewed as part of the overall Office of Science
% research proposal merit review process. Applicants are encouraged to
% consult the Office of Science website for further information and
% suggestions for how to structure a DMP:
% http://science.energy.gov/funding-
% opportunities/digital-data-management/

% Additional Guidance

% The Principal Investigator should determine which data should be the
% subject of the DMP and, in the DMP, propose which data should be
% shared and/or preserved in accordance with the Requirements.

% In determining which data should be shared and preserved,
% researchers must consider the data needed to validate research
% findings as described in the Requirements, and are encouraged to
% consider the potential benefits of their data to their own fields of
% research, fields other than their own, and society at large.

% DMPs should reflect relevant standards and community best practices
% for data and metadata, and make use of community accepted
% repositories whenever practicable.

% Costs associated with the scope of work and resources articulated in
% a DMP may be included in the proposed research budget as permitted
% by the applicable cost principles.

% To improve the discoverability of and attribution for datasets
% created and used in the course of research, the Office of Science
% encourages the citation of publicly available datasets within the
% reference section of publications, and the identification of
% datasets with persistent identifiers such as Digital Object
% Identifiers (DOIs). In most cases, the Office of Science can provide
% DOIs free of charge for data resulting from DOE-funded research
% through its Office of Scientific and Technical Information (OSTI)
% DataID Service.

% --------------------
% even more ... 
% https://science.energy.gov/funding-opportunities/digital-data-management/suggested-elements-for-a-dmp/ 

% ------------------- 
% Important:

% Digital Research Data:
% The term digital data encompasses a wide variety of information
% stored in digital form including: experimental, observational, and
% simulation data; codes, software and algorithms; text; numeric
% information; images; video; audio; and associated metadata. It also
% encompasses information in a variety of different forms including
% raw, processed, and analyzed data, published and archived data.

% Validate:
% In the context of this statement, validate means to support,
% corroborate, verify, or otherwise determine the legitimacy of the
% research findings. Validation of research findings could be
% accomplished by reproducing the original experiment or analyses;
% comparing and contrasting the results against those of a new
% experiment or analyses; or by some other means.

% Data Preservation:
% Data preservation means providing for the usability of data beyond
% the lifetime of the research activity that generated them.

% Data Sharing:
% Data sharing means making data available to people other than those
% who have generated them. Examples of data sharing range from
% bilateral communications with colleagues, to providing free,
% unrestricted access to the public through, for example, a web-based
% platform.

% --------------------- 
% The following list of elements for a DMP provides suggestions
% regarding the data management planning process and the structure of
% the DMP:

% Data Types and Sources. A brief, high-level description of the data
% to be generated or used through the course of the proposed research
% and which of these are considered digital research data necessary to
% validate the research findings.


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Boiler Plate text for inclusion in the data management plan section
% of DoE/ASCR Proposals

% Part 1: General

% DUNE Data Management plan should be cited.  Currently this is
% available as DUNE-DocDB-5759

\newcommand{\thisProposal}{\textcolor{red}{\textit{Insert title of
this proposal}}\xspace}
\newcommand{\hostLab}{\textcolor{blue}{\textit{host laboratory or institution}}\xspace}
\newcommand{\theExperiments}{\textcolor{green}{\textit{DUNE, NOvA, CMS, Atlas}}\xspace}

The \thisProposal will utilize data from flagship experiments from
across the high energy physics intensity frontier and energy frontier
portfolios.  This will include data from the \theExperiments
experiment(s).  Each of these experiments has well defined and
documented policies on data management that conform to the
U.S. Dept. of Energy's policies on data management and data
preservation\cite{dune_datamanagement_plan}.  Each of these policies
is additionally underpinned by service level agreements (SLAs) with
the host laboratory which provide the service and support needed to
fulfill the policies.  The SLAs pertaining to the \theExperiments data
management are publicly available from Fermilab\cite{scd_dm_service,
scd_database_service, scd_database_applications_service,
scd_foundation_SLA, scd_storage_service, scd_web_service}.

All of the data that is used by the \thisProposal will be carried out
in conjunction with and under the direction of the P.I.s and research
staff who are senior members of the \theExperiments scientific
collaborations and in such a manner will be analyzed, disseminated and
retained according to the policies of the governing experiment
(i.e. work on neutrino oscillation measurement DUNE data and the
results generated from that work will be carried out in accordance
with ``Policies on the Retention, Archiving and Dissemination of Data
for the DUNE Experiment (FNAL-E1071)''
\cite{dune_datamanagement_plan}).  In particular, all data and the
scientific code that is used to produce scientific research or results
will be published and made available through the portals and tools
already established by the \theExperiments collaboration(s).  The data
provide includes all of the figures, underlying distributions
(e.g. $\chi^2$ surfaces) and information used to produce the
scientific results in digital form, and with descriptions of the data
and any software needed to read or ingest the data into standard
analysis software and software suites.  It is expected that future
experiments that the P.I. may engage in as part of \thisProposal will
adopt similar policies and dissemination portals, which will be used
by the project for data management ment specific to those experiments.

Data and software tools not specifically associated with a major HEP
experiment, but of value to the greater HEP, applied mathematics or
computing science communities will be managed and made accessible to
those communities through a portal hosted by \hostLab.  The portal,
similar to the hosted portals for \theExperiments, will
provide access to the data, associated software and tools,
documentation regarding the data and associated software and
scientific results from the project in digital form.  The portal will
provide both interactive (web base) access to the data a programmatic
interface that allows for automated retrieval and use of the data.

All of the data hosted by FNAL will be retained in an archival manner,
consistent with the FNAL policies on archival storage and data
preservation.  The policies are implemented utilizing the long term
archival storage systems provided by the laboratory's ``Enstore'' tape
library.  This system has the capacity to storage in a redundant
manner, in excess of 500~PB of data using current tape technologies.
The Enstore system is the standard for data archiving for the
\theExperiments experiments and provides public portals for data
redistribution and dissemination.  The data and software produced by
\thisProposal will be retained in similar fashion to the retention
plans from \theExperiments for no less than 5 year past the conclusion
of the project and the dissolution research collaboration.  Data
relating to published scientific results will be retained for no less
than 10 years past the conclusion of the project and dissolution of
the collaboration.

\paragraph{Disclaimer}
The project will not produce or utilize any data that will impact
personal, national, or economic security, or affect proprietary
interests or business confidential information.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Some proposals require additional information and details these
% sections are just examples of what some announcements are looking
% for should be customized to the
% needs of the given agency or proposal type being submitted

\subsection{Types of data}

The \thisProposal project is anticipated to have the
following data sources and generate/use the
following data types over the course of the project.  These data are
considered to fall under the purview of the data management policies
for either the \thisProposal project or the experiments
associated with the project \theExperiments.

The classifications and descriptions of these data are shown in
Table~\ref{tab:dataclass}.  Data is classified as either ``Experiment
Data'' for data that falls under the specific jurisdiction of the
experiment's data management policy, ``Digital research data'' for
data falling specifically under the <your proposal title>, and
``Independent Policy'' for software not falling under these policies.

A detailed descriptions of these data types follow below.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Customize to your proposal if needed

\begin{table}[th]
\fontsize{8}{10}\selectfont
\begin{center}
\begin{tabularx}{0.99\textwidth}{| X | X | X |}
\hline
Data Type & Description & Classification \\
\hline \hline
Experimental data & analysis results, reconstruction and raw
  data & Experiment Data\\
\hline
Ancillary conditions data & calibration constants & Experiment
  Data \\
\hline
Experimental simulation & Monte Carlo simulations & Experiment Data \\
\hline
Exp. simulation data & physics event generators and detector
  simulation, project-generated simulation data & digital research
  data \\
\hline
Physics application configuration data and scripts & used and
  created &  digital research data \\
\hline
Metadata & experiment specific (used) and generated created & digital research data \\
\hline
Project-written applications & source code & digital research
  data \\
\hline
Performance data & raw, summary, analysis results &   digital research data \\
\hline
Performance analysis & source code and results &  digital research data \\
\hline
Performance analysis (config) &  configuration and metadata & digital
  research data \\
\hline
Project study results &  data, source code, analysis results &
  digital research data \\
\hline
ASCR and HEP community-written software &  packaged source code and
  executable code & modification/enhancements are classed as
  digital research data\\
\hline
Experiment-owned software & source code and executable code &
  modification/enhancements are classed as
  digital research data \\
\hline
External software dependencies & source code or executable
  code & Independent policy\\
\hline
\end{tabularx}
\caption[Data Classification]{ \label{tab:dataclass}Classification of
  data sources and results for the purpose of data management policy}
\end{center}
\end{table}

\paragraph{source code} The computer source codes (executable scripts
or source files) developed within this project will be maintained in
source code repositories. Standard global git repositories Github and
Bitbucket will be preferred.  Standard Open Source Software permissive
licenses BSD and Apache will be preferred and applied.  All source
code and algorithms will be reviewed by laboratory (or university)
intellectual property offices for correct export controls, inherited
license problem from external dependent software products, and other
issues regarding patentable material.  Nearly all the source codes
used within this project are expected to be developed and supported
using more than one funding source, and those code will already have
licenses attached.  The resources available at repository providers
will be used for maintaining a project web presence describing the
software that is available.  

\paragraph{application configuration} Any program configuration data or
scripts and workflow configuration data or scripts used in the
generation of physics results, validation results, performance study
results, or project analyses will also be stored in source code
repositories, as specified in the computer source codes paragraph.
This includes all application configuration used in the generated of
data used to publish results.

\paragraph{publication data} Any summary data, configuration data, and
source code used in the publications will be made available through
the project's result repository web site.

\paragraph{consumed data} This project will consume measurement and
simulation data from HEP experiments, along with configuration and
ancillary data.  These data will be already managed by experiments
within HEP with full data management plans.  Read-only copies will be
made of all necessary input data, thus relying on already-existing
data management processes.  

\paragraph{produced data} Throughout its lifetime, this project will
be producing all levels of physics data.  For existing software
applications, all data will be written in standard HEP file formats.
These formats contain metadata describing all conditions and
attributes regarding processing and configuration.  We will rely on
this data for provence tracking and reproducing results.  New storage
formats results from this project will start from and build upon the
metadata and provenance tracking mechanism currently available in HEP
software.  All data products (application configuration, final
results, intermediate data, and simulation output) that are used for
publication, acceptance testing, and comparison studies and must be
retained will be migrated to Fermilab archival storage systems.  This
project will request permanent disk and tape-backed storage resources
as required for data product retention.

\paragraph{software used}
This project will utilize specific laboratory and university developed
and maintained research tools and software packages, along with wider
HEP and ASCR supported community software and industry-wide tools such
as GCC.  The project will rely on the data management principles
established for those packages.  This includes both executable and
source code forms of these types of packages.  The project will make a
copy of a product or package version whenever executable or source
code availability cannot be guaranteed.  If the underlying operating
system availability cannot be guaranteed, VM or container technology
will be used for replicating the run-time environment.



%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%  Include only if required by your FOA

\subsection{Data access}

The physics data used by this project will come from major experiments
in the HEP community and in association with senior researchers on the
\thisProposal project who are also senior members of the
\theExperiments collaborations.  The data for each of these
experiments is provided and accessed through the standard facilities
provided by the experiments.  These data include:

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Customize as required, Omit otherwise
\begin{enumerate}
\item DUNE archive of detector and simulation data, including production
  processing (reconstruction) datasets, filtered datasets, and physics
  analysis results;
\item LHC, Tevatron, and LEP public physics results;
\item ATLAS-specific physics applications and required configuration
  data;
\item DUNE-specific physics applications and required configuration;
\item Other energy and intensity frontier experiment-specific
  physics applications (simulations) as needed for testing,
  validation, and extended use-case evaluation.
\end{enumerate}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Customize IF required by your FOA

The DUNE dataset archives which include all collected data,
simulation and analysis results are located at Fermilab.  Access to
the data is provided to members of the DUNE collaboration and to
scientists collaborating with DUNE on specific research projects.
Access to the datasets is managed through VOMS (Virtual Organization
Membership Services) to the collaboration and collaborating
scientists.  The DUNE collaboration has in place extensive policies
and provisions for collaborative efforts with external researchers to
grant access to these datasets.  The P.I. and researches in the HEP
Data and Analytics team have an extensive history of collaborating
with DUNE in this fashion.

As with prior collaborative projects, we will request access to
datasets as they are needed, relying on HPC access protection to keep
data private.  Results from this project that involve private
\theExperiments datasets will be reviewed by the collaboration(s)
before release. Summarized data for \theExperiments becomes available
as physics results are published in accordance with the governing data
management policys\cite{dune_datamanagement_plan}.

%The DUNE experiment software and all underlying software products,
%including the FNAL developed and supported software suites, and those
%software suites supported by external scientific organizations, are
%available and distributed to the public through the Fermilab release
%servers.  These software distributions include both source code and
%binary packages.  Software for other Fermilab intensity
%frontier experiments relevant to this project (DUNE, ProtoDUNE) are
%distributed in an identical fashion and through the same servers.

%LHC results needed for physics event generators is made available in
%the Rivet package or in HEPDATA when physics results are made public.
%There are no access problems with this data. LHC experiment software
%is available on publicly available repositories (ATLAS and CMS).

% END DATA MANAGEMENT PLAN BOILER PLATE
%--------------------------------------------------------
