National Institute of Standards and Technology (NIST)- Department of Commerce
Community Resilience Center of Excellence Program
The Research Office, Office for Research Development is requesting letters of intent for the National Institute of Standards and Technology (NIST)- Department of Commerce-Community Resilience Center Of Excellence Program
Office for Research Development Letter of Intent submission deadline: Monday, August 18, 2014
Agency Deadline: Friday, September 12, 2014
Synopsis of Program:
This program is about measurement standards with the goal "to develop systems-based modeling methods for assessing resilience at the community-scale. While limited methods exist to evaluate vulnerability of independent assets (e.g., buildings or power grids) to specific hazards, there is no existing tool to evaluate the expected performance of buildings and infrastructure systems from a community-resilience perspective. NIST is initiating research to develop a systems-based modeling environment for evaluating the impacts of loss of function in the built environment and the consequential effect on community response and recovery. The envisioned computational modeling environment is a research tool that will establish a scientific basis for understanding resilience at a community level. The long-term objective is to provide decision-makers and professionals with methods and tools to support cost-effective infrastructure designs and investments that make our communities more resilient. However, the performance criteria for the built environment must be flexible, so that they can be tailored to the needs of each community, including social needs." An informational webinar is scheduled for August 5th http://www.nist.gov/el/community-resilience-center-of-excellence-webinar.cfm
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 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)
- 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