Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device.
Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
EC Approved Infrastructure Portfolio Expansion Committee definitions of Allocated, Enabled, Aligned, and Services and how they determine whether a resource will be approved to be part of ACCESS
Approved: Policy, (opens new window) NSF request regarding restricting users from non-authorized countries - ready to implement as long as we move to remove users who have non institutional emails now
ACO has decided to better utilize time and follow the recommendation of people at the February Quarterly Meeting and reduce the time length of this meeting from 1.5 hours to 1 hour - from 1:00 pm to 2:00 pm CST (11:00 am to 12:00 pm PST)
Issue: When On-Boarding and Off-Boarding staff - teams will send in a help Ticket for on-boarding and Off-boarding when people join and leave the project. This will ensure that proper access to systems is provided and removed as needed.
Approved EC response to EAB questions from EAB Recommendations Discussion - Sept 4 2025
Approved RP terminology and application docs - Infrastructure Expansion Standing Committee is proposing new terminology regarding various levels of ACCESS resource providers be adopted and new application form for non-ACSS resources who would like to apply to be an ACCESS RP
Who are our users: Revised approved Text: Our primary user audience includes researchers and educators who consume ACCESS-allocated resources, with active support prioritized for those directly using these resources. At the same time, ACCESS secondarily supports prospective users and broader communities who may benefit from our services, training materials, documentation, and outreach. To meet varying user needs, we tailor support and materials to users at all experience levels.
ACO will support and steer the EC to sharing plans for PY4 early - possibly as early as Dec Quarterly Meeting - so we can make sure all are aware of priorities of other teams so all can be aligned