2023-12-07 Meeting notes

1:03

Words from Randy

Randy

• Expectation on director search is that the new director should be named in the next few weeks. It is in the board’s hands. They’ve done their interviews.

• Reminder to charge time to instrument maintenance when appropriate. Remind others to do the same (software, summit etc.).

• Also charge to appropriate CI project when appropriate

• Grant: summit staff should also use RaP project per instrument codes for certain tasks

• Randy will be working on 24A support schedule toward end of Dec, so get support block out dates in.

1:10

UNO Documentation and Training Needs

Josh

Draft list from Josh:

• VWA and cameras.

  • How do we access VWA cameras?

  • How do we troubleshoot?

• A complete and detailed run down on the day crew’s departure criteria under the UNO scheme.

• Event Notifier training

  • Should instruments be put in that?

• A complete and detailed run down on the new OA procedures for safely handling remote ops and how it might affect night time operations.

• Power outage procedures, so we can understand how they will affect instruments.

  • What happens when no one is on the summit?

  • When are things powered down? Who does it?

  • Will we send someone up to open cabinets and doors for cooling?

• Departure screen.  General knowledge plus how do we add instrument status to it if/when needed?

  • Is it change managed? (e.g. ECR)

• Nighttime cameras (cloud and all sky).  How to troubleshoot and how to get access to raw and processed data.

• Power strips. We’ve had Caleb come and talk to us about the power GUI, so that’s a good start on the remote power cycling abilities.

  • Troubleshooting procedures?

  • Are all outlet labels verified?

• What are procedures for sending people to summit?

  • When invoked, we need to make sure those people (we’ll need 2 for safety) can easily and efficiently get a vehicle which is fueled up and ready.

• Training on Alerton.

  • Is Alerton on sysadmin login plans? Will this change?

• Fire alarm system basic training (including in RO). What to do if it is beeping?

Discussion

• Is departure time still 4:20pm? Yes

• John V has noted that power outage procedure is out of date for instruments

  • Can now do targeted shutdowns of instruments, so this is emoting we might take advantage of

• Kyle: Do power outage procedure elements need to be integrated to AFP?

• Percy: how do we get another PDU installed and configured for an instrument?

  • Ask Kyle or Caleb

• Percy: what if instrument fails and is not recoverable? Do we have alternate engineering programs if PI has no science use for available instruments?

  • Similar to current situation, but don’t have step of NA troubleshooting

  • Randy: will need policies to decide when to send people up

• Carolyn: training on lighting and Alerton?

  • They are intending to pull lighting out of Alerton

• Event Notifier intended users: OAs and SAs and anyone else who wants to keep an eye on a system

  • EN has same reliance on keyword monitoring that keyword history does, so reliability will be the same

1:37

Instrument Look-ahead

Jim

• One of the many roles Dwight filled was to see what was coming for the instrument suite and triage the efforts

• Includes, what services are needed? Which instrument(s) will be on the pump? When to go cold/warm?

• Propose that each SA take a monthly rotation to do the look ahead. Spreads the load and gives each of us the opportunity for overall view

• e.g. we have 3 main vacuum pump stations, so we can’t pump all of KCWI and LRIS at the same time.

• They are recruiting for a replacement for Dwight’s position

• Josh: what about using KNIT meeting? Use first part of meeting for this.

• Should we set up cryo and vacuum calendars?

• Marc: should be coordinated with servicing missions

1:49

Instrument PM’s and E-Maint

Grant

• Brief intro / start of Grant and SA’s learning E-Maint, configuring instrument PM’s

• RaP project has half a dozen components/systems

• Grant is “System Lead” for instruments

• One task is to get instrument PMs going again

• eMaint looks good for technicians, improvement over IPM for them. They have tablets on summit which sync when docked and have task lists and procedures.

• For anyone trying to administer tasks or examine how progress is being made, it is not intuitive

  • e.g. not clear how many instrument tasks exist

• Craig is local expert

• System generates work order based on calendar, not based on time from last completion

  • Can be changed, but probably on a per task basis

• Currently only sending work orders to Dennis, regardless of nature of the work order

• SAs to look at eMaint and contact Grant if you want to try to add tasks for your instrument
  
  

• Repair and Prepare resources allocations sheet https://keckhawaii.sharepoint.com/:x:/r/sites/Projects/RaP/Planning%20Documents/RaP%20Resources%20Rev%20B.xlsx?d=w402039847dd941e487446126e87c2137&csf=1&web=1&e=1dd3Oz

2:19

LRIS Split Nights

Jim

• Config form overwrites

• Recommend SA-led pre-observing meeting similar to how we used to do LGS

•  

2:27

Pau!