2026-07-07 - ACCESS EC Meeting Agenda & Summary

Consent Agenda - @Tom Furlani (5 mins)

1. Last Meeting Notes: last meeting cancelled

2.  

Informational Items

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

Allocations - @Bruno Abreu / @Tolbert, Nathan L

1. nothing new

Support - @Shelley Knuth /Alana/Dave

1. no updates

Operations Tim/Leslie

1. no updates

2. Leslie added notes into EAB section about NIST

Metrics @Tom Furlani @Joseph White

1. Making progress on User Like Me

RP Forum @Eric Adams (RCAC) @Virginia Trueheart

1. no updates

EAB @Chuck P

1. working on task list as promised at EAB meeting - https://docs.google.com/spreadsheets/d/1CtAMssCnj8RNfWk7M7K4RvZG-rBdNJsuFseFVQWuP5s/edit?gid=0#gid=0

2. received report from Nitin - https://drive.google.com/file/d/1zXMQQhpWHMHWaR0V9hByIRjfLrA8evSU/view?usp=drive_link

   1. added relevant tasks to the task list

      1. There was only one for the RPs that I added, the rest were either things we are doing anyway or will be done as part of the next EAB meeting

         1. Response from Cybersecurity team about the NIST recommendation: ACCESS RP systems are open science and not designed to handle CUI data, and while RP sites have various security controls in place, they are not strictly compliant to CMMC nor NSPM-33 for CUI data. Some sites operate separate systems designed to handle such controlled data, but I'm not aware of any that are allocated through ACCESS (at least at this time). These are not regulations that one can simply upgrade a system to - many of the requirements need to be designed into the infrastructure up front, and there are lots of additional staff and operational costs related to maintaining compliance and record-keeping for data access, data handling, and data destruction. Compliance with these are individual RP decisions and not one ACCESS has influence over.

      2. Amit - this is exactly accurate - this should not be a discussion really - the above answer is to the point

      3. Shelley - CUI should be systems level but not ecosystem level

ACO @John Towns

1. Working on Quarterly Report

2. Submitted list of priorities for PY6 to Sharon

   1. Leslie - still working on

   2. Nathan - still working on

   3. Tom - submitted

NSF - Sharon and Ed

1. absent

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

   1. NOTE - Scheduling for reports/interactions in Q3 2026 starting now

2. Communications Standing Committee

   1. If you’re attending PEARC and know your schedule, please consider signing up for at least one shift at the booth. Thanks!

3. Cybersecurity Standing Committee

   1. Was supposed to report on 6/30/26 but meeting was cancelled - may need to reschedule

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. Home page has been refreshed with updated hero-image graphics, more prominent link to our Impact page and (scrolling down) a single video (testimonials, our newest).

8. Data Architecture Working Group

   1. no report

Milestone Review: (Link Below) - please review some of these (especially the Upcoming ones) - will we really be working on them during PY5?

EC Meeting To Do / Follow Ups: (Link Below)
Is this complete?

Open

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)