Summary by new ACCESS PY5 Goals

Here’s a structured synthesis of all the attached documents, framed around the ACCESS Program Wide Metrics you specified.

1. Improve the user experience (e.g., better user guidance, personalization of the user experience, and better insights through usage analysis, …)

2. Increase the value delivered to the ACCESS-Allocated Resource Providers (e.g., easier integration processes, simpler and more effective tools, …)

3. Solidify the programmatic foundation for transitioning to successor awards (e.g., modernizing tools, updating documentation and policies, and improving cross-program operational alignment, capturing lessons learned, …)

4. Better capture and articulate ACCESS scientific impact (e.g., through publications data, new captured metrics, new analysis of existing data captured, …)

1. Improve the User Experience

• ACO: Focus on clearer governance processes, improved communication channels, and community engagement through surveys and events.

• Operations: Streamline allocations/accounting workflows, redesign Operations portal UI/UX, migrate to Django, and simplify user account management.

• Metrics: Provide personalized resource recommendations (“User Like Me”), tailored monthly usage reports, and integrate XDMoD insights into OnDemand.

• Support: Strengthen early-stage onboarding, deliver practical hands-on training, and modernize support tools (ARA, SDS, chatbot).

• Allocations: Introduce personalized recommendations at allocation submission, improve confirmation messaging, and ensure users know how to access awarded resources.

Data drivers: Surveys, allocation usage trends, onboarding challenges, job efficiency metrics, and advisory body feedback.

2. Increase the Value Delivered to Resource Providers (RPs)

• ACO: Leverage advisory bodies (EAB, RAC) to ensure RP needs are addressed and feedback integrated.

• Operations: Improve RP integration processes, cybersecurity documentation, and coordination workshops; expand perfSONAR nodes and regional networking.

• Metrics: Provide RP-facing analytics, workload models, and NAIRR pilot reporting to improve RP visibility and efficiency.

• Support: Develop templates and onboarding consistency with RP collaboration; strengthen partnerships with regional communities.

• Allocations: Outreach to community colleges and non-R1 institutions; amplify publications to highlight RP contributions.

Data drivers: RP surveys, onboarding/offboarding documentation requests, cybersecurity compliance needs, and RP usage reports.

3. Solidify the Programmatic Foundation for Transition

• ACO: Transition planning for tools, processes, and governance; prepare close-out documentation and lessons learned.

• Operations: Update all ACCESS policies and documentation; finalize cybersecurity policies; prepare decommissioning instructions.

• Metrics: Develop sustainable analytics frameworks and reporting pipelines; capture lessons learned from NAIRR pilot integration.

• Support: Package training materials, documentation, and tools for long-term reuse; ensure sustainability of APIs and artifacts.

• Allocations: Address technical debt (OS upgrades, AMIE replacement), strengthen security vetting, and prepare continuity plans.

Data drivers: Risk registers, technical debt reports, NSF expectations for closeout, and lessons learned from XSEDE transition.

4. Better Capture and Articulate ACCESS Scientific Impact

• ACO: Enhance visibility through communications, newsletters, and tracking community engagement events.

• Operations: Highlight RP contributions via workshops and STEP program outputs.

• Metrics: Expand publication metrics, altmetrics, and value analytics (ROI from grants); improve reporting dashboards.

• Support: Showcase training impacts and user success stories; integrate support tools with NAIRR visibility.

• Allocations: Promote publications and citation metrics; amplify impactful science highlights.

Data drivers: Publications database, altmetric scores, survey feedback, and outreach metrics.

• Consistent Themes Across Teams:

  • Improving user guidance and personalization.

  • Strengthening RP integration and value delivery.

  • Preparing for program transition and sustainability.

  • Elevating visibility of ACCESS-enabled science.

• Shared Understanding:
  All teams implicitly agree PY5 is about consolidation, continuity, and maximizing impact rather than major new initiatives.

• Cross-Award Alignment:
  The afternoon synthesis (Raw Notes) consolidated priorities into four overarching themes:

1. Improve the user experience.

2. Increase value delivered to RPs.

3. Solidify programmatic foundation for transition.

4. Better capture and articulate scientific impact.

• Morning: Each award presented data-driven PY5 plans, highlighting user onboarding, RP integration, tool modernization, and transition planning.

• Afternoon: Discussion converged on four ACCESS-wide priorities, reframing earlier themes into a unified set of goals. Debate clarified that responsible AI use is a task under documentation/policy alignment, not a standalone priority.

• Consensus: PY5 is the final year of ACCESS and must focus on strengthening foundations, ensuring smooth transition to successor awards, and demonstrating scientific impact.

• Outcome: The program now has a clear, unified framework for NSF reporting:

• User experience improvements.

• RP value enhancements.

• Transition readiness and sustainability.

• Scientific impact visibility.

This alignment provides a strong narrative for NSF: ACCESS is closing its current cycle by consolidating gains, ensuring continuity, and maximizing its demonstrated value to the research community.