<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#ffffff">
Dear All - <br>
I just wanted to remind everyone that we no longer need a PDoc
mentorship statement if the PDoc is listed as Senior Personnel on
the NSF Budget. <br>
Cheers,<br>
Sheila<br>
<br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">Subject: </th>
<td>[Flex] NEW NSF GPG -- NSF 11-1</td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">Date: </th>
<td>Sat, 02 Oct 2010 21:47:04 -0400</td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">From: </th>
<td>Sheila Clifford <a class="moz-txt-link-rfc2396E" href="mailto:sclifford@whoi.edu"><sclifford@whoi.edu></a></td>
</tr>
<tr>
<th valign="BASELINE" align="RIGHT" nowrap="nowrap">To: </th>
<td><a class="moz-txt-link-abbreviated" href="mailto:flex@whoi.edu">flex@whoi.edu</a></td>
</tr>
</tbody>
</table>
<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
Dear Flex-ers - <br>
<br>
The new NSF GPG is out: NSF 11-1<br>
<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.nsf.gov/pubs/policydocs/pappguide/nsf11001/gpg_2.jsp">http://www.nsf.gov/pubs/policydocs/pappguide/nsf11001/gpg_2.jsp</a><br>
<br>
<br>
Please see the "summary of significant changes" here:<br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.nsf.gov/pubs/policydocs/pappguide/nsf11001/gpg_sigchanges.jsp">http://www.nsf.gov/pubs/policydocs/pappguide/nsf11001/gpg_sigchanges.jsp</a><br>
<br>
<br>
After a quick glance, the most significant change seems to be the
requirement of a Data Management Plan. I have copied that info
below. Andy Maffei (CIS) and others are working on possible
boilerplate material for the PIs to use.<br>
<br>
Also - when I first began working on NSF props (back in the stone
age), the Facilities Section was optional. I don't remember NSF
ever saying that it became mandatory. However, if you read the
third "significant change" regarding Cost Sharing, it suggests (to
me) that the Facilities section is not as "optional" as it might
have been - even when cost sharing isn't a consideration. I'm also
curious about the statement that the Facilities description "should
be narrative in nature". Come January, I will be interested to see
what the Facilities page looks like in Fastlane.<br>
<br>
Finally, it's good to see that we do NOT need a PDoc mentorship
statement if the PDoc is listed as Senior Personnel on the NSF
Budget<br>
<br>
Let me know if you see anything new or if you have questions.<br>
Regards,<br>
Sheila<br>
<br>
------------ Data Management Plan------------<br>
<br>
<ul>
<li>Plans for data management and sharing of the products of
research. Proposals must include a supplementary document of no
more than two pages labeled “Data Management Plan”. This
supplement should describe how the proposal will conform to NSF
policy on the dissemination and sharing of research results (see
<a moz-do-not-send="true"
href="http://www.nsf.gov/pubs/policydocs/pappguide/nsf11001/aag_6.jsp#VID4">AAG
Chapter VI.D.4</a>), and may include:</li>
<br>
<ol>
<li>the types of data, samples, physical collections, software,
curriculum materials, and other materials to be produced in
the course of the project;</li>
<br>
<li>the standards to be used for data and metadata format and
content (where existing standards are absent or deemed
inadequate, this should be documented along with any proposed
solutions or remedies);</li>
<br>
<li>policies for access and sharing including provisions for
appropriate protection of privacy, confidentiality, security,
intellectual property, or other rights or requirements;</li>
<br>
<li>policies and provisions for re-use, re-distribution, and the
production of derivatives; and</li>
<br>
<li>plans for archiving data, samples, and other research
products, and for preservation of access to them.</li>
</ol>
<p>Data management requirements and plans specific to the
Directorate, Office, Division, Program, or other NSF unit,
relevant to a proposal are available at: <a
moz-do-not-send="true"
href="http://www.nsf.gov/bfa/dias/policy/dmp.jsp">http://www.nsf.gov/bfa/dias/policy/dmp.jsp</a>.
If guidance specific to the program is not available, then the
requirements established in this section apply. </p>
<p>Simultaneously submitted collaborative proposals and proposals
that include subawards are a single unified project and should
include only one supplemental combined Data Management Plan,
regardless of the number of non-lead collaborative proposals or
subawards included. Fastlane will not permit submission of a
proposal that is missing a Data Management Plan. Proposals for
supplementary support to an existing award are not required to
include a Data Management Plan.</p>
<p>A valid Data Management Plan may include only the statement
that no detailed plan is needed, as long as the statement is
accompanied by a clear justification. Proposers who feel that
the plan cannot fit within the supplement limit of two pages may
use part of the 15-page Project Description for additional data
management information. Proposers are advised that the Data
Management Plan may not be used to circumvent the 15-page
Project Description limitation. The Data Management Plan will be
reviewed as an integral part of the proposal, coming under
Intellectual Merit or Broader Impacts or both, as appropriate
for the scientific community of relevance.<br>
</p>
<p>--------------------------------<br>
</p>
</ul>
<br>
<br>
</body>
</html>