2025-12-16 - ACCESS EC Meeting Agenda & Summary

2025-12-16 - ACCESS EC Meeting Agenda & Summary

 

 

Attendees:

  • RAMPS: Stephen Deems (v), Dave Hart

  • MATCH: Shelley Knuth (v), Alana Romanella, Jim Griffioen

  • CONECT: Tim Boerner (v), Leslie Froeschl

  • MMS: Tom Furlani (v), Joe White

  • RP: Eric Adams (v), Virginia Trueheart

  • EAB: Chuck Pavloski

  • OpenCI: John Towns (v), Amit Majumdar, Misha Shah, Lisa Kaczmarczyk, Shannon Bradley

  • NSF: Sharon Geva, Ed Walker

  • Additional - Nathan Tolbert, Bruno Abreu

Parking Lot

  • Cancelled Meetings:

    • December 23 - Christmas week cancelled

    • December 30 - cancelled

  • EC representative for the RAC - follow up in January

  • Shelley out Jan 6 - Alana will fill in


Decisions made during the meeting:

Use Decision Macro - Tool (under Insert Elements in the toolbar)

Agenda


  1. Consent Agenda @Shelley Knuth (5 mins)

    1. Approval of summaries from prior EC meeting - https://access-ci.atlassian.net/wiki/spaces/ACP/pages/1803780097

  2. Informational Items

  3. Allocations @Stephen Deems (Unlicensed)

    1. HR changes

  4. Support@Shelley Knuth /Alana/Jim

    1. working on workshops/classes

    2. close to signing contract for one in Denver in June

    3. McClenney - leaving team - not anticipating backfilling

  5. Operations @Tim Boerner /Leslie

    1. nothing to report

  6. Metrics @Tom Furlani @Joseph White

    1. no update

  7. RP Forum @Eric Adams (RCAC) @Virginia Trueheart

    1. No update

  8. EAB @Chuck P

    1. Vivian HuangFu has requested to end her EAB term on Dec 31, 2025

      1. We need to go through the process of filling her vacant spot ASAP, need to determine procedure

    2. One-on-Ones with EAB

      1. Operations scheduled Thursday, January 8, 2026

      2. Metrics scheduled Friday, January 9, 2026

      3. Next will be ACO and RP

  9. ACO @John Towns

    1. Nothing to report

  10. NSF - Sharon and Ed -

    1. nothing to report

  11. Standing Committee Updates - EC Liaison - (Chuck lead)

    1. https://docs.google.com/document/d/1pNfsXwr7640_7zk03mJu2jDUqDAsG37fOezlqNYcX0E/edit?usp=sharing - need to get Infrastructure, Cybersecurity and Ticketing to schedule interim communications with the EC in Jan/Feb 2026

    2. Communications Standing Committee

      1. Newsletter content needed by December 29; please share here.

      2. SC wrap-up

        1. 160 new emails added to our mailing list with Welcome to ACCESS email sent

        2. Feedback ACCESS users (via QR code at booth)

        3. ACCESS won 3 HPCWire Awards! We also published a story about RP wins.

    3. Cybersecurity Standing Committee

      1. Approved two policies last week. CGC moving on to additional policy document updates.

    4. Evaluation Standing Committee

      1. no report

    5. Infrastructure Standing Committee

      1. no report

    6. Ticketing Standing Committee

      1. no report

    7. Web Presence Standing Committee

      1. no report

  12. Milestone Review: (Link Below)

  13. EC Meeting To Do / Follow Ups: (Link Below)

  14. Reminders

    1. don't forget to review Engagement Tracker and Risk Register Review

      1. Upcoming Meetings & Events (https://docs.google.com/spreadsheets/d/1_EXKUOXmY-TVkDWaHR1-SuiKt404uGEnGSr6uQCkwzw/edit?gid=0#gid=0 )

      2. https://access-ci.atlassian.net/jira/core/projects/RR/list?sortBy=assignee&direction=DESC&filter=status%20in%20(%22Execute%20Contingency%22%2C%20Monitor%2C%20Review)

        1. ACO went through the Risk Register and assigned risks that were unassigned

    2. create a ticket if you have anyone onboarding or offboarding and need access permissions set properly


Additional Agenda Items

  1. Allocations HR Changes - 10 min - Dave H

    1. Email from Stephen - see below: https://access-ci.atlassian.net/wiki/spaces/ACP/pages/1829273601/2025-12-16+-+ACCESS+EC+Meeting+Agenda+Summary#HR-Changes

    2. Will be at PSC till Jan 9, 2025

    3. Dave last day is Friday - this is his last EC meeting

    4. Laura is leaving Illinois - Jan 2 last day

    5. Bruno Abraeu - will replace Stephen as PI of Award - will need to be approved by NSF -

    6. Nathan Tolbert - will take over for Laura H for the Sub-Award at NCSA - needs to be approved by NSF

    7. NCAR Sub - is TBD on how it will be handled

    8. Ken Hackworth and Rob Light will be made co-PIs on award - have worked with Nathan before

    9. Stephen and Dave going to Internet2

    10. Introduce Bruno A - from PSC - will be spreading Stephen’s tasks around with Ken and Rob

    11. What is likelihood that award will follow Dave? Dave will not know for a while

    12. John - Dave has played a key role in standing committees - how will these committees be covered

      1. Dave - Stephen was in web group and on Eval - Dave will need a new rep from Allocations

      2. Cassian from Support is leaving and Alana is wanting to step back

        1. Jason will be stepping in

      3. This will all be addressed as we go forward

      4. Amit - can help make sure the surveys go out for next year

      5. Hopefully there will not need to be a mad scramble

    13. Shelley - what is going on with NAIRR and allocations

      1. John - Ken H will step in for Dave for NAIRR-OC - this should put us in good shape

    14. Tom - what about XRAS and AMIE

      1. talk to Nathan or Rob Light

      2. Nathan says the only changes should be who is leading what meeting

    15. Sharon - Eric can spread the word to the RPs - make a good bounce-back reply on his email - that will help

  2. We need an EC representative for the RAC - 10 min - John Towns

    1. Recognized this when doing review of ACO Goals - looking at communications between standing committees and the EC - found there was no Rep to bring back and provide info to RAC/EC

    2. Overview of EC Sponsors and their support of the working groups for Bruno

      1. Laura will transition that to Bruno - so it would make sense for him to be the sponsor

    3. Can come back and confirm with Bruno - Tom says he will help overview and provide some info for background

    4. Follow up on this in January

  3. EAB - Chuck Pavloski

    1. Vivian Heng Fu will be retiring from the EAB at the end of the year

    2. We need to know how to fill her position - it is in the EAB charter

      1. https://drive.google.com/drive/u/1/folders/1JK7Yc-lK1q0hHiMx4vnVsGIU5hUfg-sE

      2. There is no defined procedure for EAB member replacement mid-term

    3. Still need ACO and RAC appointments with the EAB

  4. Dec Quarterly Meeting (20 min)

    1. Background Info:

      1. Notes: https://access-ci.atlassian.net/wiki/spaces/ACP/pages/1815052432

      2. Morning Note Synthesis: https://access-ci.atlassian.net/wiki/spaces/ACP/pages/1815052432/EC+Quarterly+Meeting+Notes#Synthesis-of-the-morning-notes%3A

      3. Summary of Planned Goals/Actions - by team: https://access-ci.atlassian.net/wiki/spaces/ACP/pages/1820852243

      4. Summary of Planned Goals/Actions - by PY5 ACCESS Wide Goals: https://access-ci.atlassian.net/wiki/spaces/ACP/pages/1819869206

      5. PY5 Summary White Sheet: https://access-ci.atlassian.net/wiki/spaces/ACP/pages/1820688409

    2. PY5 ACCESS Wide Goals Priorities or Focus Areas

      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, …)

    3. These are not ACCESS wide goals - these are PY5 Priorities or Focus Areas

    4. Summary Priorities by Team

    5. Next we should come back together once we have metrics around how to evaluate them

    6. For instance ACO will review our Goals and see how they fit with the Priorities

    7. John - we should have some shared text and slides that we all use in our reviews

    8. Tom - would take improve user experience - not sure if we should have metrics/outcomes for each Goal / Priority

    9. Shelley agrees - these should guide what her team is doing and there would be metrics/outcomes for the Priorities

    10. John - each team will review the priorities and how their awards will support them - but Sharon might ask for metrics

    11. Tom - next step might be generate slides and review together

    12. Shelley - thought Sharon’s interest was in team metrics and goals

    13. Shannon - If we divide the goals and the priorities - I think we can say the Priorities drive the goals and those goals can have metrics and outcomes within the teams

    14. Steps Forward

      1. Tom will make a power point with what his team will do

      2. John - we will need to do this in January

      3. By Feb we will have an EAB meeting where we have to talk about this

Operations PY5 Priorities

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

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.


HR Changes

Over the next 2-3 weeks, Laura, Dave, and I will be leaving our respective organizations. We have been working on the transition processes of our roles and responsibilities related to the ACCESS program and the Allocations project. We’d like to note that this was not a fully coordinated exit, but has quite some coincidence to it.

We have been working closely with the senior personnel on the project, along with NSF, to transition them into co-PI roles, as well as onboard a new PI.

Dr. Bruno Abreu, PSC’s Deputy Scientific Director, will be the PI of the award. Bruno brings deep experience as an ACSS end user, a reviewer for XSEDE, ACCESS, and NAIRR Pilot proposals, and has worked at two ACCESS RP sites (at NCSA prior to PSC).

PSC will also request adding two co-PIs:

  • Rob Light, PSC’s Principal Systems Software Engineer Manager, already Senior Personnel and co-lead for software infrastructure.

  • Ken Hackworth, PSC’s Senior Allocations Manager, also Senior Personnel and lead for front-line support of community members requesting projects. 

For Laura’s co-PI role at NCSA, Nathan Tolbert, another Senior Personnel member and co-lead for software infrastructure, will step in.

The discussions on the NCAR sub award are still underway with the new leadership team and all relevant parties.

All involved are working toward a smooth transition of operations so as to have as little disruption as possible to our team, the program, and the broader ecosystem. 

Thank you for your previous support and the future support of the new team. 

On behalf of Dave, Laura, and myself it’s been an honor to serve this project and this community.

While I’m out (this was a scheduled message) please follow-up with Dave, Laura, Ken, Rob, Nathan, and/or Bruno for any immediate needs.

Continued best wishes,

Stephen Deems

Dave Hart

Laura Herriott


Next Meeting: January 6, 2026

 

LINKS

Program Milestones

 

EC Meeting Task Tracking + Quarterly and Annual Meetings To Do Follow Ups