Title Page

1. Title Page • Title of Project • Principal Investigators & Institutions • Associate Investigators & institutions • Private Sector Or Other Project Participants

2. Contact Information • Provide contact information (phone, email and surface mail) for PIs, associate PIs and private sector / other partners

3. Project Description • A concise statement of the purpose of the project and project outcome • A concise statement describing how the project purpose relates to homeland security critical infrastructure protection

4. Capability Requirement Gap • Describe the federal, state, local, or tribal homeland security requirement being met • Review current knowledge, practices, or operations … are there activities similar to this project – what makes this project unique or different - what is the value added of this project (e.g., landscape assessment) • Describe how the product resulting from the project will improve current knowledge, practices, or operations • Define the characteristics of the product of this project that sets it apart from similar products • Provide a cost/benefit analysis for the project

5. Technical Review/Project Content • Technical presentation about the project (no limit on number of slides) • Detailed evidence supported by technical data that demonstrates progress toward the planned outcome

6. Collaborative Opportunities • Present results of product assessments and/or training by potential customers and end-users • Address collaborations with federal, state, local or tribal agencies • Address opportunities to leverage results from other SERRI projects • Present any needs that may exist that would • Enhance the application of the product of the project or • Facilitate the advancement of the project through the research phase • Other PIs in the audience may have access to solutions that could support the project

7. Project Timeline (Gantt Chart Required) Display end-to-end period of performance • Highlight benchmark events (as defined by the PI) which have occurred • Advise on current status • Highlight anticipated benchmark events yet to occur and anticipated completion

8. Budget Status: 60 % of budget expended. Technical Status: 50 % of project completed. Schedule Status: 55 % of performance period completed. Project Progress Summary 0 10 20 30 40 50 60 70 80 90 100 Comments Use this section for Comments on the Progress Graph Without showing budget dollar amounts, describe the progress of the project to-date. Describe the progress on the project by examining the history to-date of the project. Display a chart similar to the one above comparing percent of budget expended to technical accomplishments vs. percent of schedule completed. Provide an explanation/interpretation of the above chart. For example, for the above chart, one would explain why spending has exceeded schedule and technical accomplishments. Hence, there is an indication that the project may likely encounter an over-run. If such should be the case then what are the plans to get the project back on track?

9. Technology Readiness Level (TRL) Assessment(Use this chart only if appropriate for the research project) • Assess/validate the extent of product development to-date using TRL metric • Forecast the level of product development at the end of the project using TRL metric • Describe how the product will be transferred to potential customers and/or end-users

10. Summary & Conclusions • Summarize new knowledge discovered and/or the capabilities/features of new product/tool developed. • Describe actual accomplishments to date versus planned accomplishments • Unexpected developments encountered during the project (the positives as well as the negatives), issues, risks, • Plans to correct lack of progress if project is not on schedule (mitigation strategy) • Explain any developments that may alter the anticipated outcome of the project • Plan of work for the next six months • Anticipated schedule or budget adjustments; changes in key personnel.