1:02

Randy’s Rundowns

Randy

• Welcome Grant!

• Council is focusing on return to on site work

  • How are we going to do in person meetings?

  • i.e. this meeting might now be too crowded for Ed Stone CR

  • What will be the flexible work policy?

• SSC meeting tomorrow

• CI process was “fruitful”

• Randy on vacation May 26 to June 13. Jim will be delegate, but can’t fire Marc.

1:10

Age vs Maintenance costs proxy for Risk analysis

Kassis

• SSC Meeting will touch on white papers in addition the instrument project updates (KPF, KCRM, ORCAS)

• Interest in retirement and risk metrics

• Asked for global risk analysis for instruments

• Marc framed this as about age and maintenance costs

• Marc makes presentation he will give to SSC tomorrow

• Randy: another possible factor is configurability

• Josh: are there critical vulnerabilities of things which are difficult or impossible to replace? (e.g. MOSFIRE CSU)

• Percy: also there’s an accessibility or recovery time axis. e.g. Easy to fix failed filter wheel on LRIS, but not on MOSFIRE.

• Marc: Perhaps talk about risk and recovery time estimates for our SSC update in November

• SSC should coalesce around retirement strategies at Nov meeting

• Only past metric has been needed space on the deck

1:41

Nightlog tickets

• more details please

• more follow-up

Jim

• Lots of documentation in disparate locations

• Night log and day log is living documentation

• 8am meeting to go over night log tickets

• Follow up is helpful to fill in details for documentation

• Josh: Should we set up a regular meeting for this group to go over tickets?

• Randy: we used to have rooting schedule of SA to attend SWOC meetings

• Josh: Dedicate one SA Coffee session next week (Tuesday) to reviewing night log tickets.

• Carolyn: use the OA action dialog to let OAs know what they can do in the future

  • OA action: is for actions the OAs can and should do

• Carlos: sometimes hard to sort though many tickets, we should use these meetings to move troubleshooting tips to the troubleshooting pages

• Kyle: what is the value/use of “closing” a ticket? How should we use that?

  • All: unclear

2:12

Pau!