2026-01-06 - ACCESS EC Meeting Agenda & Summary

2026-01-06 - ACCESS EC Meeting Agenda & Summary

Attendees:

  • RAMPS/Allocations: Bruno Abreu (v), Rob Light, Ken Hackworth, Nathan Tolbert

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

  • CONECT: Tim Boerner (v), Leslie Froeschl

  • MMS/Metrics: Tom Furlani (v), Joe White

  • RP: Eric Adams (v), Virginia Trueheart

  • EAB: Chuck Pavloski

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

  • NSF: Sharon Geva, Ed Walker

Parking Lot

  • EC representative for the RAC - follow up in January - addressed

  • Fill EAB spot vacated by Vivian HuangFu

  • Shelley out Jan 6 - Alana will fill in


Decisions made during the meeting:

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

Agenda


Consent Agenda - Updates for the team that should be read offline

  1. Consent Agenda - @Tom Furlani (5 mins)

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

  2. Informational Items

  3. Allocations - @Bruno Abreu

    1. Spinning up

  4. Support - @Shelley Knuth /Alana/Jim

    1. no update

  5. Operations Tim/Leslie

    1. no update

  6. Metrics @Tom Furlani @Joseph White

    1. EAB - Metrics meeting on Friday Jan 9th

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

    1. There is a meeting next Thursday - formal vote for vice-chair

  8. EAB @Chuck P

    1. (See below)

    2. Will continue to ask reps to update the section below

    3. We will need to addr ess Vivian’s replacement

      1. lesson learned - make sure to define the process for replacing someone mid-term

      2. https://access-ci.atlassian.net/browse/ATT-230

  9. ACO @John Towns

    1. Collaborating with ACCESS copy has been added to the About page

  10. NSF - Sharon and Ed -

    1. Everyone is now teleworking

    2. Sharon will be giving us spend authority for the final year - it could be blocked by a report that is overdue (possibly by a co-pi or something) - should have come in within the past couple weeks

  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. no report

    3. Cybersecurity Standing Committee

      1. Privacy and Acceptable Use policies updated and accepted

      2. CGC is now turning to additional document updates:

        1. ACCESS Policy Minder Responsibilities

        2. ACCESS Privacy Policy Minder Responsibilities

        3. ACCESS Training and Awareness Policy

    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

    8. Data Architecture WG (Proposed)

      1. no report

  12. Milestone Review: (Link Below)
    - Who should Shannon move Stephen’s tasks to - Bruno? yes
    - Is ECMT-121 now considered finished? - yes

    image-20260105-160252.png
  13. EC Meeting To Do / Follow Ups: (Link Below)
    - is ATT-215 complete? we cannot use grant funds as a sponsor - John has been using ACO/ICR funds for this - Tom will ask on his side - John believes it was $5000

    image-20260105-160538.png
  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)

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

      1. What changes to permissions should Shannon be making for: remove access

        1. Laura Harriott

        2. Dave Hart

        3. Stephen Deems


Additional Agenda Items

  1. Quarterly Meeting Update - @Shannon Bradley

    1. Hotel - Hilton Garden Inn - Chicago Central Loop -

      1. The contract is at the U of I campus for signature

      2. I asked our Hotel contact for the room block link today - she cannot give us the block link till we get the signed contract back from campus

      3. We will be eating buffet breakfast at the hotel because it is less expensive and logistically easier than catering breakfast to the Illini Center

    2. Meeting - at the Illini Center (https://illinicenter.illinois.edu/ )

      1. They have provided a formal invoice - they do not have formal contracts with signatures.

      2. We process journal vouchers for university events once per month and will process this with the rest of our February JVs on or around February 27, 2026.

    3. Catering -

      1. Because the catering is delivered and there are no kitchen facilities at the Illini Center catering All the food is delivered and set up in disposable trays for any vendor we coordinate with.

        1. Can we clean up after ourselves? or would we need a staff to stay and clean up?

      2. I will need the agenda done soon so the caterers know when the breaks and lunch will be

        1. I am aiming for 10am break, 12pm lunch, 3 pm break

      3. I will need dietary requirements again in the planning document

        1. Can you please start filling in your headcount and dietary needs? https://docs.google.com/spreadsheets/d/1ufIhfLOpaOm8-xmhzITII6lhcBnRHQQ8EZxCSjW6irc/edit?gid=531229141#gid=531229141

    4. Agenda Planning

      1. Stephen did a lot of leading this - what happens now?

      2. Cindy, Amit, Misha, me - please put Cindy on the agenda for next week to start planning

      3. Team time - Tuesday afternoon - if anyone wants to participate

        1. need to reconfirm with Support if they are meeting or not

    5. EAB

      1. needs to be solidified

      2. Chuck did send around a notice to EAB members so they can save the dates

  2. We need an EC representative for the RAC -

    1. It would make sense for Bruno to be the sponsor - yes - he is prepared

    2. Tom says he will help overview and provide some info for background - Laura was going to review with Bruno as well

    3. 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

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

        1. Debate is whether or not it is worth it at this point to fill the position

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

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

        1. https://access-ci.atlassian.net/browse/ATT-231

    2. Still need ACO and RAC appointments with the EAB

  4. Finalize Shared Priorities

    1. PY5 ACCESS Shared Priorities - these are approved

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

    2. To do next

      1. Summary Priorities by Team - done below

      2. Each team review their team goals and see how they fit with the priorities

      3. The Priorities drive the team goals and those goals can have metrics and outcomes within the teams

      4. Create shared text and slides that we all use in our reviews

    3. Steps Forward

      1. Each team edits their bullet text on the 4 shared priority slides - https://docs.google.com/presentation/d/1V1VOE0gNfv3w2_tnaYcAY0aCvsC-B-TZ/edit?slide=id.p1#slide=id.p1

        1. Each team can add supplemental slides containing greater detail on their contributions to the 4 shared priorities (if desired)

          1. Metrics included examples in the google doc slides

          2. Everyone should update this deck and highlight their section in red when it is done - when all are red we are ready to go

          3. Shannon send Tom the generic template for ACCESS

            1. https://access-ci.atlassian.net/browse/ATT-232

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

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

      4. Shared version is the slide with the 4 priorities

  5. year4 surveys out in Jan-Feb 2026 - @majumdar

    1. As you all know Dave Hart, chair of the Eval SC is not with ACCESS anymore. Given that it is the time to start preparing (which we have been doing for a while already) the three (RP, Staff and Community) Year4 surveys and send out the surveys, I had some discussion with the Eval SC members in late Dec and with their approval, I am sharing this note to you. All of this is known to you and have been discussed before by Dave and in that sense nothing is new.

      The good thing is that over the last few months we have completed the intellectual part of the planning for the RP, Staff and Community surveys for Year4. We are mostly left with the mechanical part where Cindy does her magic (and the tremendous hard work behind it) to get the surveys out, send reminders, get results back, format the results in presentable form, and share with the Eval SC members. 

      I am summarizing here the plan, and all of these are known to all of you. If you have any comments, suggestions, please let us know by Jan 14th. Our plan is to start sending out the surveys in late-Jan to early-Feb timeframe. That will be fine for getting the survey results back and do a prelim analysis and include in the annual reports if any ACCESS team wants to do that.

      Here is the summary:

      1. No change in the Staff survey from the Year3 survey; ACO will provide the list to whom the survey will be sent

      2. Pretty much no change in the RP survey from the Year3 survey (Ops will be removing some items from the RP survey in favor of interviews that they will conduct); Winona is assembling a tailored list of "guaranteed RP responders"

      3. Community survey has been brought down to 7 questions (Dave shared the update with EC on Dec 9th and EC was fine with it https://docs.google.com/presentation/d/1WE-9j2dLfVjsqaEaXkkGitylTfGb8zy36wRGxJzHcvo/edit?slide=id.p1#slide=id.p1)

      Community Survey: Will be the deduplicated UNION of three sources:

      • Allocations: All persons who interacted with Allocations site in 2025.

      • Metrics: All persons who recorded some resource usage in 2025.

      • Support: All non-bouncing addresses on the Support newsletter mailing list. 

    2. Cindy sent out info this morning and is getting things started

Background Info:

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

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

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

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

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

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.