Decisions:
N/A
Action Items:
Summary | Description | Responsible | Due Date |
---|---|---|---|
Lizanne's presentation - QMA-375Getting issue details... STATUS | Slide deck needs to be on the new template User Survey should be covered by Lizanne in her presentation Campus Champions Climate Study: ok to include higher level findings
Climate study
Like having longitudinal studies being included. If panel makes comment about importance, John could have a conversation with Bob about needing more funds/supplemental request. Don't cut anything–trying to provide more time Be prepared for a homework question or 2 re. clarification on some of this. | ||
Program Office - QMA-376Getting issue details... STATUS | Slide 8:
10
11
A little granular. Talk at a higher level. No individual personnel info. | ||
Financial summary - QMA-377Getting issue details... STATUS | 13: Run another Y axis on % spend on right side 14: Don't try to describe difference in carryover & holdback. Each year end up with some unspent funds. Change Holdback to "Unspent Funds"
Move quickly unless they ask questions If they ask about TACC–say they had carry-forward funds. 16: Categorize L2 areas together. | ||
10-15 minutes time allotment for presentation so plenty of time for questions. Bob suggested adding point to slide 3 (missed what the point was) Include value estimate for XOC or user support? Includes Ops (implicit in things we ask end users). ROI for XSEDE as a whole could we use the value inherent in salary range differences between assistant/standard/senior positions to help define a "value of experience" for staff? Slide 4: Why PY5, 6–no training in PY5, no end user support in PY6. Mention why these are blank
Note that XSEDE delivers things more efficiently than individual universities can. Make visually obvious what numbers go into these. Subdivide into components of value of funding & cost Slide 5: Quantify value of experience–correlate salary ranges for positions based on years of experience as starting point We understand how to quantify... | Craig Stewart |
Notes/ Discussion items: