2023-01-25 OpenCI Leadership Meeting Agenda & Summary

Attendees:

• Present: Jay Alameda, Cynthia Dillon, Shawn Strande, Cindy Wong, Ron Payne, Lizanne DeStefano, John Towns, Dina Meek, Lavanya Podila

Agenda/Notes

1. Debrief on EC meeting2023-01-03 ACCESS EC Meeting Agenda & Summary@John Towns

2. Deliverable Status (see below)

3. Follow up on external evaluator feedback @John Towns

   1. This week’s focus topic: In what ways can we engage more deeply witht he Service Teams to understand their context and to understand how best to help?

   2. Some initial thoughts (from John):

      1. Its all about communications and we don't have enough communications with each service team individually; we typically work with them as a group

      2. Closely related is fostering cross-award communications

      3. Possible actions:

         1. establish regular interactions between ACO and each service team

            1. Monthly or bi-weekly (perhaps to start) meetings with ACO team and PI and leads for each service team.

         2. Establish something akin to the May 2022 meeting for the program as a whole

         3.  

4. EAB Updates @Shawn Strande

5. Evaluation Update @Lizanne DeStefano (Unlicensed)

6. Communications Update@Dina Meek

7. Community Engagement Update@Jay Alameda

   1. Terminology and Language Policy - interest from CB&E to see this supported across tracks

   2. Allocations: invited us to review and add to their DEI outreach tracker and planning spreadsheet

   3. Yesterday’s meeting: in spirit of “engaging more deeply with tracks”, “understanding needs and constraints”, and “engaging outside of EC meetings” - devoted the call to focusing on what service areas need from the ACO.

      1. Note that the problem of defining relationships between awards: not a new problem but goes back to (at least) the transition from PACI to TeraGrid (the whole notion of resource providers and their relationship to a central integrator: developed in this context).

      2. ACO: seen as a having a role in streamlining operations, making things more efficient, while allowing service areas autonomy. Analogy to air traffic controller

         1. Note that we may want to build channels to other community building efforts such as NASA TOPS (Transform To Open Science - NASA Science ) and DOE Office of Science:

            1. eg, NASA offers a significant amount of data via TOPS, we could similarly offer a significant amount of easily-accessed compute resources. Could formalize some of this through the ACO?

      3. ACO: seen as taking a lead on branding and consistency among tracks, including inclusive language policy

         1. Would be good to drive to consistent language so that ACCESS is viewed as a more singular enterprise, and that we have a level of coherence and seamless experience with interactions through ACCESS

         2. Some survey efforts in planning: RPs, AARC, …

         3. Benefit of the CB&E group: taking a ticket not being handled but mentioned in slack directly to the service area contact working in CB&E - and helping to make sure the issue is indeed resolved.

      4. ACO role in communications: lots of point-solution work going on (eg, reaching out directly to many groups about the CSEP program) and risking communication fatigue or lack of recognition that these are ACCESS communications (by virtue of the fact that they are coming from individuals within ACCESS). A lot of interest in working together on coordinated communications, through the ACO.

         1. One idea: ACO builds the base level to create communication channels, and then we all work together to extend these and fill with content

8. Project Office & Tools Update @Ron Payne

 Near-Term ACO Deliverables

Reference - ACO Action Tracker

Next Meeting: 1 February 2023