Projects for the November 6, 2017 have been selected.
Next due dates are:
November 07, 2018
November 06, 2019
NSF Advanced Informal STEM Learning (AISL) is now limited. See below.
August 28, 2017 LOI Intent deadline 5pm pacific standard time. firstname.lastname@example.org
Note the changes:
Interested - please email Susan.Emerson@oregonstate.edu
ORD LOI Due Date: Monday, August 28, 2017 - 5 pm PST.
NSf Due Date: November 06, 2017
The Advancing Informal STEM Learning (AISL) program seeks to advance new approaches to and evidence-based understanding of the design and development of STEM learning opportunities for the public in informal environments; provide multiple pathways for broadening access to and engagement in STEM learning experiences; advance innovative research on and assessment of STEM learning in informal environments; and engage the public of all ages in learning STEM in informal environments.
The AISL program supports six types of projects: (1) Pilots and Feasibility Studies, (2) Research in Service to Practice, (3) Innovations in Development, (4) Broad Implementation, (5) Literature Reviews, Syntheses, or Meta-Analyses, and (6) Conferences.
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 National Science Foundation- program Advancing Informal STEM Learning (AISL) by the NSF letter of intent deadline.
Information: email Research.Development@oregonstate.edu
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 or bullet points 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)
Please note if this project is a resubmit or is brand new.
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?
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