Child pages
  • 20210831- XSEDE reporting plan through project end
Skip to end of metadata
Go to start of metadata

Decisions:

 Summary

Description

IPR18

Submit IPR18 in August 2022 with data through July 2022. 

Final report approachFinal project report submitted in early September would have table data through August but no analysis of the data. This would allow NSF data to have complete data for the project. This report to include impacts/analysis. 
Production of shorter "glossy" version of final report might be consideredExplore interest in CISE & others having a shorter version of the final report with impacts etc. in a glossy print format.


Action Items:

Summary
Description
Responsible
Due Date

Review previous final report guidance received QMA-490 - Getting issue details... STATUS

John Towns to look at what we received in guidance the last couple times from program officers. 


Develop outline of what final report will include exactly QMA-491 - Getting issue details... STATUS

John will take the first stab at developing an outline. This will be shared so everyone can provide input/feedback. Final outline to be ready by December Quarterly.




 

Notes/ Discussion items:

  • How to handle reporting through end of project. 
  • Final report to include long final quarter. 
  • Chance that project could be extended, which could complicate final reporting. 
  • John brought up with Bob/Al, and they have no guidance yet. Instructed to tell them how we think the final report should be handled. 
    • Ability to recommend what should be included in final report. 
  • Lots of data we have to pull together. Want to avoid getting so wrapped up in that that we can't focus on lessens learned etc. 
  • Final outcomes/impact report could talk about impacts to community, longitudinal study data
    • 1 longitudinal study done now. 
    • Want to run many as long as possible.
    • Could provide lessons learned/synopsis along the way and focus on publications after that. 
  • Thoughts: 
    • Do this in steps as we go and top it off at the end. Wise to do it while we have people's attention as much as possible.
  • Should there be an IPR18 that is submitted in August 2022 (includes data for May-July 2022). Then work on completing final report (which is different in character) by early September. 
  • If we can get template for final report early, we can start writing it in August (or earlier). Then just plug in final numbers at the last minute. If we don't do that, will be scrambling on ACCESS transition with people overwhelmed instead of focusing on developing a strong final report. 
    • Won't do anything until we have approval from Bob. 
  • Alternative: Submit IPR18 in August 2022 with data through July 2022. Final project report submitted in early September would have table data through August but no analysis of the data. This would allow NSF data to have complete data for the project. This report to include impacts/analysis. 
  • What do we really want in the final report. 
    • Metrics appendix
    • Highlight longitudinal studies, ROI, advances/improvements in some metrics over time. 
      • Climate study data clearly shows 3-5 years on the project is the "sweet spot"–could be something important to share. 
      • Lessons learned  
      • Opp for CEE to use data to report importance of investing in BP rather than piece-meal. A way to use data to deliver a message. 
      • Chance for us to tell our story in a way that we can't do with just metrics data. 
      • Highlighting some of the more exceptional work & how that has impacted the community. 
      • Final report could be about bringing people together in an org; intended/unintended consequences of doing that. All the students that have come through our programs who are now going out into the community as professionals. 
        • Go back and talk to students/staff/those associated with major sciences successes–here is how that impacted my career... Longitudinal studies will do some of this. 
        • Trust relationships–trust developed over time with staff/researchers, staff/students
  • Need to work on what exactly final report will include. Don't want it to be crazy long. Exec summary needs to be compelling, report needs to be concise. 
    • John to look at what we received in guidance the last couple times from program officers. 
    • Need elements of lessons learned, best practices, not great practices, impact we've had. 
    • John to take first cut at this. Over next month, everyone provide input to John to refine. 
    • Goal to finalize by December QM 
  • Glossy version of final report to be produced? 
    • Possibly a shorter version... 
    • Likely can't use project funds if produced after end of award
  • No labels