2026-04-28 - ACCESS EC Meeting Agenda & Summary

2026-04-28 - ACCESS EC Meeting Agenda & Summary

Attendees:

  • RAMPS/Allocations: Bruno Abreu (v), Nathan Tolbert

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

  • CONECT/Operations: 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

  • Speakers:

Parking Lot


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 completed/read offline

If possible, please fill in this info prior to the meeting - thank you!

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

    1. Last Meeting Notes: 2026-04-21 - ACCESS EC Meeting Agenda & Summary

  2. Informational Items

    1. Link to ACCESS swag shop - https://dixon-graphics.com/access-ci/shop/home

  3. Allocations - @Bruno Abreu

    1. Updated user information campaign

      1. First mass mail sent to all ACCESS; approx. 10% response

      2. New email directly to “non-compliant” users to be sent on April 30. It will include what’s missing in their profile and instructions on how to update it

      3. Glitch with logging in through the ACCESS-CI landing page

    2. International users

      1. Started rolling out the plan; existing allocations cannot add international users

    3. Allocations NCAR subaward discontinued on May 1st 2026

    4. New Allocations subaward to Internet2, co-PI Dave Hart joins Bruno, Ken, Rob, Natha. Dave will lead I2’s team focusing on:

      1. Dave: subaward management, support for incorporating new ACCESS/NAIRR resources, ACCESS Evaluation/Survey SC, allocations metrics and data analysis, reporting

      2. Stephen Deems: coordination of Allocations-related communications (including joining Comms SC) across service tracks and RPs

      3. Lauren Michael: intake, tracking and resolution of Allocations stakeholders feedback; continuous improvement cycles (including webinars)

      4. Timothy Middlekoop: analysis of feedback specifically related to Allocations; continuous improvement cycles; allocation mechanisms for emerging and novel resource types

    5. Bruno and Nathan continue to be Allocations EC reps and points of contact for Allocations-related matters.

  4. Support - @Shelley Knuth /Alana/Jim

    1. Chatbot Update

      1. At this point, you can see that the chatbot is implemented on the NAIRR website, and does not require a login.  https://nairrpilot.org/

        On ACCESS, we have updated the Support portion of the website to also have the chatbot not require logging in https://support.access-ci.org/.  However, the other teams need to update their webpages to reflect the new chatbot (for example, the homepage still has the login required) https://access-ci.org/.  Once those are updated, you should see a seamless experience.  We have talked to your teams about this, but feel free to remind folks as necessary.

        We are managing this on the back end with rate limiting, and there are some measures in place to determine whether someone is a bot (such as if there are too many questions asked in too short of time).

  5. Operations Tim/Leslie

    1.  

  6. Metrics @Tom Furlani @Joseph White

    1.  

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

  8. EAB @Chuck P

  9. ACO @John Towns

  10. NSF - Sharon and Ed -

    1.  

    2.  

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

    1. https://docs.google.com/document/d/1pNfsXwr7640_7zk03mJu2jDUqDAsG37fOezlqNYcX0E/edit?usp=sharing - Need to schedule interim meetings with each SC/WG to interact with the EC

    2. Communications Standing Committee

      1. EC report scheduled for May 5, 2026

    3. Cybersecurity Standing Committee

      1. EC report scheduled for Jun 30, 2026

    4. Evaluation Standing Committee

      1. no report

    5. Infrastructure Standing Committee

      1. EC report scheduled for Apr 28, 2026

    6. Ticketing Standing Committee

      1. no report

    7. Web Presence Standing Committee

      1. EC report scheduled for May 5, 2026

    8. Data Architecture WG (Proposed)

      1. Charter approval vote scheduled for Apr 28, 2026

  12. Milestone Review: (Link Below) - We have a lot of things coming up in May

    image-20260421-183900.png

     

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

    image-20260421-183955.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)


Additional Agenda Items

  1. Standing Committee Reports

    1. Infrastructure Portfolio Expansion Committee Report (JP Navarro and Joe White)

    2. Presentation: https://docs.google.com/presentation/d/1oHbL1JvOYWJ-hNz1aswe3bIiCnNkWzwf/edit?slide=id.p1#slide=id.p1

    3. Using Standard Terms and Definitions

      1. Allocated, Enabled, Aligned

        1. Tim explained why Aligned was needed - more for RPs to use to say they are aligned with us

        2. Enabled is a debated definition

      2. Impacted Resources

    4. Shelley: Where does NSF stand on this? Does the decision truly land with the EC?

    5. Sharon - the definition they gave is what they are adamant about - if the ones in the list is for national use then this is what falls into the category they defined

      1. if the bottom two end up being national scale then they qualify - but if they are only regional they do not fall into the category NSF defined

      2. More than likely we will have to say no at this point

      3. They say they have aspirations to be national - they want to grow beyond their initial - they are not prevented from being part of the RP forum to give them that exposure - but they cannot be fully integrated

        1. need to check the Charter to make sure unintegrated providers into the RP forum

        2. ACCESS Resource Provider Forum

        3. https://operations.access-ci.org/pub/rpf

    6. Tim: Now we need to flesh out the path to request an exception - these requests should come to the EC

    7. Tim and Leslie - they have drafted the form about why they want to participate - they haven’t received anything - but no process has been drafted on how that comes to the EC yet

    8. Sharon - The bottom two resources only have 4 months left in their project funding time - even if they are continuing the projects they are very “long in the tooth”

      1. She can’t see where they have been extended

    9. Should grandfather in Science Gateways and approve ACCESS Enabled Regional Peering Network

    10. No ACCESS Enabled Compute, cloud, or Storage Roadmaps or ACCESS Aligned Roadmaps

    11. Discussion taking more time than slot allowed - need to bring it up again next week for more discussion

      1. JP and Shelley can talk offline

      2. There are some complexities that Shelley doesn’t understand

  2. Discussion and approval of the ACCESS Data Working Group Charter (Joe)

    1. https://docs.google.com/document/d/1Giav9FwV8ZCDnLCcUhu_zcFhgEHapG07Glys3YeYN8k/edit?tab=t.0#heading=h.ykwf2htpnts

    2. Review and Vote

    3. Tim - talking about maintenance and who is responsible - needs determined - this is the last edit

    4. We can call for a vote during the week via email once the change is made if everyone is ready

  3. EAB Follow-Up Document - (Chuck)

    1. Report back from EC to EAB ready to go. https://docs.google.com/document/d/1gvl4GBlMWuBNhqK27IZdv0f0ZcNyTbytpfXT4w6tz4A/edit?pli=1&tab=t.gkljtfrdcnel

    2. need final approval from EC to send

    3. There are some words that need defined by the EAB before approval - Chuck will reach out

  4. Planning Summer Virtual ACCESS Quarterly Meeting

    1. Typically these are in June

    2. We need to set a date

    3. We need to start planning an agenda

    4. Put out a call for topics to see if we have enough topics - Shannon work with Cindy

  5. Follow up on Correspondence: Tom F - FYI

    1. From: Hongbo Zhang

      1. Abstract:

        1. I will submit  May 1st if possible. I attached the abstract.

          The idea is to have a conference. I will work with farmers, robotics researchers, data scientists to have workshops. Through the process, we will be able to collect online data and my group own data and use these data as the farming robotics data standard including communication, AI, navigation, spray, harvesting etc….  With these rich data, we will discuss the potential standard and how to make the platforms more standardized to make sure manufactures can produce tractor like robots widely to be adopted by farmers. 

          For ACCESS, we will use the data to run some benchmarks on cluster so we can know the data are AI-ready. For example, we will run crop disease identification model. We will also run the harvesting models with deep learning,  LLM, agent, and world models. 

          If it is possible, we may can host some workshops in your areas and we can budget some workshops in the application. 

          If there is anyway who can serve as the senior personnel, consultant, or simply collaborator role, I can put it in the description. 

          The director gave the ceiling of the budget as 100K.

      2. Hongbo - happy to chat offline and you can let me know what you need from me.

        Shelley


Next Meeting: May 5, 2026

 

LINKS

Program Milestones

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


Reference:

Risk Register:

Project Change Request: