Summary by Team for the new PY5 Goals

Summary by Team for the new PY5 Goals


Here’s a structured summary for each team, framed against the new PY5 goals you outlined. Each team’s plan is organized into the below headers.

 

 

ACCESS Coordination Office (ACO)

PY5 Focus

  • Governance refinement and communication improvements.

  • Leverage advisory bodies (EAB, RAC).

  • Transition planning and project close‑out.

  • Community engagement and satisfaction surveys.

Data that Drives the Priorities

  • Meeting notes and attendance records (EC, SC/WGs, EAB, RAC).

  • Advisory body recommendations.

  • Surveys (community, staff, RP).

  • Communication analytics (newsletter stats, social media reach, website visits).

  • Risk register and financial reports.

Team Goals and Relation to Program Wide Goals

  • Improve user experience: Better communication channels and survey feedback loops.

  • Increase RP value: Advisory body recommendations integrated into governance.

  • Solidify transition: Transition plans for tools, processes, and reporting.

  • Capture scientific impact: Enhanced visibility through communications and outreach.

Impact on the Community

  • Stronger governance inspires confidence.

  • Advisory body integration ensures responsiveness to RP and community needs.

  • Transition planning minimizes disruption for successor awards.

  • Improved communication expands ACCESS visibility and user engagement.

Collaborations and Dependencies

  • Relies on EAB, RAC, EC, SC/WGs, and RP teams.

  • Input from communications committees and web presence SC.

Risks and Capacity

  • Risks: Governance responsiveness (RR‑110, RR‑112, etc.), communication gaps.

  • Capacity: Requires proactive engagement from EC and SC/WG leads.

Operations

PY5 Focus

  • Infrastructure integration (new ACSS systems).

  • Streamlined allocations/accounting workflows.

  • Cybersecurity policy updates and incident response exercises.

  • RP coordination workshops and STEP program contributions.

  • Networking and data transfer improvements.

Data that Drives the Priorities

  • Documentation gaps (cybersecurity, RP onboarding).

  • RP feedback from workshops.

  • Monitoring data (perfSONAR, CiDeR).

  • Technical debt in integration frameworks.

Team Goals and Relation to Program Wide Goals

  • Improve user experience: Simplify account workflows, redesign portal UI/UX.

  • Increase RP value: Easier RP integration, cybersecurity documentation, regional networking.

  • Solidify transition: Updated policies, decommissioning instructions, roadmap documentation.

  • Capture scientific impact: STEP program outputs and RP workshop outcomes.

Impact on the Community

  • Easier RP onboarding and integration.

  • Stronger cybersecurity and compliance.

  • Improved resource discovery and user workflows.

  • Expanded training opportunities for students.

Collaborations and Dependencies

  • Works with Allocations (AMIE), Metrics (perfSONAR data), Support (tool integration), RPs, OmniSOC, FABRIC.

Risks and Capacity

  • Risks: Cybersecurity compliance, integration complexity, documentation gaps.

  • Capacity: Requires renewed resources for cybersecurity and RP coordination.

 

Metrics

PY5 Focus

  • Personalized usage intelligence (“User Like Me”).

  • Tailored monthly reports for users and PIs.

  • XDMoD integration with OnDemand.

  • CI simulator and workload analysis.

  • NAIRR pilot support and reporting.

  • Value analytics and publication metrics.

Data that Drives the Priorities

  • XDMoD usage data and job efficiency statistics.

  • NetSage network flow data.

  • NAIRR pilot usage reports.

  • Publication and ROI metrics.

Team Goals and Relation to Program Wide Goals

  • Improve user experience: Personalized reports, resource recommendations, job efficiency insights.

  • Increase RP value: RP‑facing analytics, workload models, NAIRR pilot reporting.

  • Solidify transition: Sustainable analytics frameworks and reporting pipelines.

  • Capture scientific impact: Value analytics, publication metrics, ROI dashboards.

Impact on the Community

  • Reduced time‑to‑science through actionable insights.

  • Improved throughput and efficiency awareness.

  • Greater visibility of ACCESS contributions to NSF and institutions.

Collaborations and Dependencies

  • Works with Allocations, Support, Operations, NAIRR pilot partners, RPs.

Risks and Capacity

  • Risks: Limited adoption of tools, awareness gaps.

  • Capacity: Requires training, outreach, and integration support.

 

Support

PY5 Focus

  • Stronger early‑stage onboarding support.

  • High‑impact, hands‑on training modules.

  • Modernization and integration of support tools (ARA, SDS, chatbot).

  • Preparing tools and artifacts for long‑term use.

Data that Drives the Priorities

  • Surveys on onboarding challenges and tool usage.

  • Workshop feedback and participation metrics.

  • AI/HPC readiness trends.

  • Tool adoption statistics.

Team Goals and Relation to Program Wide Goals

  • Improve user experience: Clearer onboarding, practical training, modernized tools.

  • Increase RP value: Templates and onboarding consistency with RP collaboration.

  • Solidify transition: Packaging training materials and artifacts for reuse.

  • Capture scientific impact: Showcase training impacts and user success stories.

Impact on the Community

  • Easier entry for new users, especially in AI/HPC.

  • Practical training builds confidence and skills.

  • Sustainable tools and documentation ensure long‑term value.

Collaborations and Dependencies

  • Depends on SCIPE ambassadors, RPs, SMEs, ACO, NSF.

  • Works with Operations and Metrics for tool integration.

Risks and Capacity

  • Risks: Staffing shortages for training, unclear stewardship of tools post‑PY5.

  • Capacity: Requires RP collaboration and NSF clarity on sustainability.

 

Allocations

PY5 Focus

  • Personalized recommendations at allocation submission.

  • Improved confirmation messaging and onboarding clarity.

  • AMIE replacement and security enhancements.

  • Outreach to community colleges and non‑R1 institutions.

  • Amplification of publications and science highlights.

Data that Drives the Priorities

  • Allocation request trends and usage gaps.

  • Publication metrics and citation data.

  • Outreach metrics from PY4.

  • Security incident reports.

Team Goals and Relation to Program Wide Goals

  • Improve user experience: Personalized recommendations, onboarding clarity.

  • Increase RP value: Easier RP integration via AMIE replacement, security vetting.

  • Solidify transition: Address technical debt, prepare continuity plans.

  • Capture scientific impact: Promote publications and amplify impactful science.

Impact on the Community

  • Faster onboarding and time‑to‑usage.

  • Improved security and RP integration.

  • Greater visibility of ACCESS‑enabled science.

  • Expanded outreach to underrepresented institutions.

Collaborations and Dependencies

  • Works with Operations (AMIE), RPs, ACO, Support.

  • Relies on cross‑award input for outreach and publications.

Risks and Capacity

  • Risks: Security changes, technical debt, delays in AMIE replacement.

  • Capacity: Requires additional tools, development time, and staffing