| | | |
|---|
1:04 | Words from John | John | Board and SSC meetings coming up March 8-10 Pictures of new instruments are nice for the Board Could emerge from March meeting with Board having endorsed strategic plan Jim and Randy have seen it, but waiting on Board approval to circulate Science strategic plan has ~$350M cost
Lots of work on how to schedule 23B to minimize collisions between AO ops and development Team Keck deadline is coming up Raja and John talked about growing “shadow the scientist” program
|
1:11 | LRIS refurbishment | Percy | To address 3 issues: transport mechanism, 6 weeks with another 2 weeks as contingency coat the collimator and clean field lens, 5-6 weeks improving latching for the mask box 1 week
|
1:18 | Remote work policy | Jim/John | John: The non-experimental version of the policy is coming out Flexible != Remote: Policy is difficult because we’re mid-sized, so hard to make something that works for everyone, but also needs flexibility Next week will be released to managers and supervisors for feedback Primary thing John wants to articulate is that the policy is a best practices guide for working with your supervisor How do we guarantee a high level of engagement between our staff? This is a work perk, but one that this group has had for a long time Don’t view policy as a threat, view it as how to evolve Observatory in to new world of work (opportunity not threat)
Jim: Important to have this during hiring for clarity for candidates Rest of observatory is not as in tune with the night schedule as our group Intent is to provide flexibility for supervisors There are some oddly specific things in the policy which are not for us
Will be company wide software “people planner” that will show contact info when WFH Randy is interested in having days where we all default to being in the office Kyle: document suggests Wednesday’s as suggested organization wide collaboration day, what does that mean? Network: Sys Admin is prototyping new WiFi system to help with in office
|
1:38 | UNO PDU GUI | Caleb | 2 main parts: front end and back end, will cover both for this group Components: PDU + KTL dispatcher + config file + PDU GUI Eaton PDUs (a few APCs grandfathered in) using SNMP. In some instruments + 83 for UNO Each PDU has its own KTL dispatcher, means they don’t affect one another if problems Configuration file created to spool up PDU, with unique two letter designation (AA, AB, etc.). Allows PDUs to move between KTL services freely backup is made nightly Config file allows swapping hardware if it needs replacement Make it easy to bring up a new PDU
Uses standard keywords for each strip and outlet Demo of GUI
|
2:09 | Instrument Retirement Metrics | Marc | |
| identify next meeting lead | All | |
2:39 | Pau | | Carlos to lead next meeting |