National Science Foundation
Innovation Corps - Regional Node Program (I-Corps Node)
The Office for Research Development is requesting letters of intent for the National Science Foundation (NSF) –Innovation Corps - Regional Node Program (I-Corps Node)
The National Science Foundation (NSF) seeks to further develop and nurture a national innovation ecosystem that builds upon fundamental research to guide the output of scientific discoveries closer to the development of technologies, products, processes and services that benefit society. The goal of the program is to dramatically reduce the period of time necessary to bring a promising idea from its inception to widespread implementation.
- Organizations may only be a participant in one proposal per deadline. In addition, organizations may only be associated with one I-Corps Node that is receiving funding from NSF at a given time.
- PLEASE NOTE: Institutions that are the Lead organization for an existing Node may only participate in a Track 2 proposal submission.
Research Office Letter of Intent Deadline: February 28, 2017
Agency Letter of Intent Deadline: March 9, 2017
Agency Full Proposal Deadline: May 9, 2017
Anticipated Funding Amount: $2,000,000
Estimated Number of Awards: 4
Limit on Number of Proposals per Organization: 1
In an effort to provide the highest level of excellence and viability for funding, a review process will be put in place if more than one proposal is submitted. The finalist will be asked to represent Oregon State University and to submit their proposal to the NSF-(I-Corps Node) program by the NSF deadline of May 10, 2016
Information: Mary Phillips, Director, Office for Research Development at email@example.com
General guidance for preparation of letters of intent to the Research Office:
COVER SHEET (1 page)
- Solicitation Name and Descriptive Title
- Project Summary: 3 or 4 sentences or bullet points that provide an overview of the objective of your proposed research, how you plan to do it, and the expected outcome.
- Unique Aspects: 3 or 4 sentences that highlight how your research/approach is different/better.
- Key PI/co-PIs: 5 or 6 sentences or bullet points that highlight team expertise as it relates to the project.
- Budget: Example: The total cost of the project is anticipated to be $ X, with $ Y being requested from the NSF. NSF funds will be used for: $ A for personnel; $ B for operations, and $ C for broader impacts/subcontracts etc.
- Justification for NSF support: One paragraph explaining why this research fits with the RFP and strategic goals of NSF.
PROJECT DESCRIPTION (1 - 4 pages)
- Problem statement - Clear and concise statement of 1) research question(s) and how the project will address the research question(s); 2) what technical barriers need to be overcome to perform the research; and 3) how the proposed research can lead to the advancement of research/knowledge in this area.
- Conceptual framework: Conceptual framework describing, for example, how the synthesis of various project components, approaches, and participant expertise are linked together to address the problem of interest. Graphics may be used.
- Proposed activities: Describe the project to be undertaken and provide the technical specifications of the research activities and timelines that will be undertaken.
- Expected results: Describe the outcome you anticipate from the research. (Remember your initial motivation for wanting to do this!)
- Peer Groups: Who else is doing something similar, why their discoveries are useful for you, and what discriminates you.
- Broader Impact/Metrics for Success: What metrics are the most appropriate for evaluating the success of the proposed project (e.g., peer-reviewed papers, policy-directed efforts, databases, models, development of new resources, etc.)? If successful, who would most likely use the knowledge or tools developed?
- Fundraising: List any matching fund requests, industry commitments etc. List any similar current proposals pending.
Suggested Reviewers: (1 page) Optional – but as you write envision who might be a reviewer of your proposal or the Program Officer.
- Reviewer 1: Area of expertise
- State why you think this person would be a good reviewer.
Submit electronically as a PDF document to: Research.Development@oregonstate.edu