<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"> Dear Colleagues:<br>
<br>
The following message will be of interest to your membership. NSF would greatly appreciate your disseminating as soon, and as widely, as possible.<br>
If you have any questions, please don’t hesitate to let me know.<br>
<br>
Many thanks!<br>
<br>
Best,<br>
<br>
Jean <br>
<br>
<b>Jean Feldman</b><br>
<b>Head, Policy Office</b><br>
<b>Division of Institution & Award Support</b><br>
<b>National Science Foundation</b><br>
<b>4201 Wilson Boulevard</b><br>
<b>Arlington, VA 22230</b><br>
<b>voice: 703.292.8243</b><br>
<b>email: <a href="mailto:jfeldman@nsf.gov">jfeldman@nsf.gov</a> <br>
</b><br>
_______________________________________________________________________________<br>
<br>
On January 26, 2015, the National Science Foundation (NSF) will implement changes in FastLane to support the revised version of the
<a href="http://www.nsf.gov/pubs/policydocs/pappguide/nsf15001/index.jsp">Proposal and Award Policies and Procedures Guide (PAPPG)</a> and to run additional automated compliance checks on proposals.<br>
<br>
<i>Proposal and Award Policies and Procedures Guide (PAPPG) (NSF 15-1)<br>
</i><br>
A revised PAPPG was issued on November 20, 2014, which incorporates OMB’s <i>Uniform</i>
<i>Administrative Requirements, Cost Principles, and Audit Requirements for Federal Awards</i> (Uniform Guidance), as well as other policy updates. The following changes will be made to FastLane to support the revised PAPPG:<br>
<br>
· <b>Budget Form Update:</b> The budget form will be updated so that the “Residual Funds” line (Line K) will not be editable for all programs except Small Business Innovation Research/Small Business Technology Transfer (SBIR/STTR). As this field is currently
used for the purpose of collecting fees, “Residual Funds” will be renamed to “Small Business Fee.”<br>
<br>
· <b>Budget Justification Upload:</b> Budget justification can no longer be entered as text. Awardees will be required to upload a budget justification for each organization added to the budget via an upload screen. Already, 95% of proposers take advantage
of the upload option.<br>
<br>
<s>· </s><b>Cost Sharing Notifications Requirement:</b> The existing requirement that only awards with cost sharing of $500,000 or more must submit a cost sharing certificate will be modified to support the revised policy which specifies that cost sharing
notifications must be submitted by <i>all</i> awardees with awards that include cost sharing.
<br>
<br>
· <b>New Funding Mechanism:</b> The FastLane proposal cover sheet will be updated to include the new funding mechanism type, Ideas Lab. Ideas Lab is designed to support the development and implementation of creative and innovative project ideas. These
projects will typically be high-risk/high-impact as they represent new and unproven ideas, approaches, and/or technologies.
<br>
<br>
<br>
<i>Automated Compliance Checks<br>
</i><br>
FastLane will begin to run an additional 24 automated compliance checks on proposals to ensure they comply with requirements outlined in the PAPPG, Chapter II.C.2 of the Grants Proposal Guide (GPG). These checks will validate a proposal for compliance with
page count, proposal sections per type of funding mechanism and budget related rules for proposals submitted in response to the GPG, Program Announcements and Program Descriptions. At this time, these checks will not be enforced for proposals submitted in
response to Program Solicitations.<br>
<br>
· <b>Page Count: </b>Page count rules will be enforced on the following proposal sections<b>:<br>
</b><br>
o <b>Project Description:</b> 15-page limit [exceptions: 8-page limit for Early-Concept Grants for Exploratory Research (EAGER), and 5-page limit for Rapid Response Research (RAPID)]<br>
<br>
o <b>Budget Justification</b>: 3-page limit for the proposing institution and a separate, 3-page limit for each sub-recipient organization<br>
<br>
o <b>Mentoring Plan</b>: 1-page limit<br>
<br>
o <b>Data Management Plan</b>: 2-page limit<br>
<br>
· <b>Budget: </b>Budget-related checks will focus primarily on proposal duration and requested amount. For example, the system will enforce a maximum requested amount of $200,000 for a RAPID proposal and $300,000 for an EAGER proposal.<b>
<br>
</b><br>
· <b>Proposal Section: </b>Proposal sections will be enforced by their funding mechanism for Program Announcement, Program Description and other GPG-type funding opportunities. For example, an error message will appear if a Project Description was not
provided for an EAGER proposal.<b> <br>
</b><br>
<br>
The checks detailed above will be triggered when the “Check Proposal,” “Forward to SPO,” or “Submit Proposal” functions are selected by a proposer or proposing organization. Depending on the rule being checked, a warning or error message will display when a
proposal is found to be non-compliant. If an error message appears, the organization will not be able to submit the proposal until it is compliant. To view a detailed list of all compliance checks, click
<a href="http://www.nsf.gov/bfa/dias/policy/autocheck/compliancechecks_jan15.pdf">
here</a>.<br>
<br>
We encourage you to share this information with your respective organization. Please contact
<a href="mailto:policy@nsf.gov">policy@nsf.gov</a> for any further questions.<br>
<br>
Thank you,<br>
<br>
Jean Feldman<br>
Head, Policy Office<br>
Division of Institution & Award Support<br>
National Science Foundation<br>
4201 Wilson Boulevard<br>
Arlington, VA 22230<br>
voice: 703.292.8243<br>
email: <a href="mailto:jfeldman@nsf.gov">jfeldman@nsf.gov</a><o:p></o:p></p>
</div>
</body>
</html>