EOT PACI Leadership Meeting

1
EOT PACI Leadership Meeting

• NPACI All Hands Meeting
• San Diego, CA
• February 9, 2000

2
EOT PACI has a lot of high quality, high impact
projects

• Shift our focus from organization of EOT PACI
  projects to outcomes of projects.

• Synthesize outcomes of existing projects into a
  coherent story.
• Our organization is the means to the end, the
  outcomes are the end.

3
Action Plan for FY01 Site VisitFocus on Outcomes

• Software infrastructure
• Users
• Dissemination
• Human resources infrastructure
• Numbers and names
• Testimonials
• Curriculum infrastructure
• Body of knowledge infrastructure
• Publications and books
• Partnership infrastructure

4
EOT PACI issues for FY01 site visit

• Are we producing prototype infrastructure or real
  infrastructure?
• How to select affiliates? What does affiliation
  mean? Whole greater than sum of parts? Outcomes?
  Jeff Husskamp ECU.
• EOT PACI website. Is it useful and to what
  communities? Website or portal? Impact.
• Educational technology software produced and its
  impact.

5
EOT PACI issues for FY01 site visit

• Books and publications and their impact.
• Scaling of exemplary programs. Accomplishments
  and impact. Dissemination.
• Undergrad computational science curriculum.
  Number of students impacted. Lessons learned.
• K-12 professional development impact. Numbers and
  names of teachers. Testimonials.
• Underrepresented groups in computational science.
  Numbers and names of students. Testimonials..

6
EOT PACI issues for FY01 site visit

• Mentorship. lessons learned. Testimonials
• New communities that have joined HPC.
  Testimonials.
• Role of evaluation on EOT PACI. Its impact.
  Dissemination.
• Leveraged funds. EdGrid. MSI. SC2000.
• Systemic change.
• Collaborative NPACI and NCSA.

7
EOT PACI issues for FY01 site visit
8
EOT PACI issues for FY01 site visit
9
Timeline
Renewal
FY02
Site visit
FY01
Today
FY00
FY99
Organizing EOT PACI
FY98
Start, finding our way
10
Plans

• Mock site review in place of FY00 SV.
• FY00 site review if it happens.
• Another serious evaluation meeting
• Facilitated strategic planning meeting in
  preparation for SV01. Story boarding. Build the
  story that we will tell at SV01.
• Best possible story about each project. Call the
  project PIs. Use a script for consistency.
  Produce script.
• Funding decisions. Gap analysis. Must be
  consistent with funding cycle process.
• Project stories Gap analysis FY01 funding
  decisions - Strategic planning meeting for SV01.