-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
A: When you work on a component, ALWAYS downgrade it if you are not the final signoff to ensure other affected groups get notified, or if the component is not operational for more than a shift. You can downgrade components via the link in ATLis which takes you directly to HCO. Remember to always make a comment in HCO and upgrade the component once it is returned to operability. Operations rely on this information to understand the day-to-day state of the machine.
A: Yes. The accelerator is a large machine that will rarely, if ever, have every component working. During the initial startup we wanted to make sure that the tool showed that we were completely ready (all green). However, this didn’t mean that everything worked. Some components were masked. After we started operating, components began to break and require repair. The repair process is coordinated through the Ops PR process. If repairs cannot be made during the shift, HCO should be downgraded so that Crew Chiefs are aware of the state of the machine. We still want HCO to be “green” at a start of a run, but we acknowledge that the program changes during a run. This means some components will not be ready, or will have scheduled repairs, and we want to make sure the crew chief can review HCO and understand the actual state of the system.
A: Component signoffs were negotiated with system owners and group leaders during the initial HCO system design. There are still subsets of systems that require additional or no signoffs by some groups. If you work on some of the components in a subsystem, but not all, you can use the N/A signoff for those you don’t work on. The HCO system is designed to make sure at least one group works on all components in the accelerator. This means that if everyone tries to pick “N/A” then the last group will not be allowed to do so. If you believe that corrections are necessary, please submit a question using the feedback form on HCO “Help” tab.
A: There are typically two stages to the lab’s HCO process. The first stage is designed to make the machine ready for machine lockup. These include things like alignment of components, vacuum work, diagnostic health checks, etc. These checks occur during the SAD preceding the week before tunnel lockup. The second stage of the process involves tunnel lockup. This includes Box Power supply checks and RF checks. This is done the week preceding beam operations, starting on Monday, with operations turn over being completed by Friday morning.
A: Use the feedback form on the “Help” tab in the HCO tool. The message goes to all the team members so that we make sure concerns are properly addressed.
A:
- HCO/SRM property only, not set or read by CED
- Set by individual group on a component (i.e. can have one group still sign-off on the component, with another group's sign-off marked NA)
- No expiration, persists until user action is taken to place it at {Not Ready, Checked, Ready, Masked}
- Intended to be used for removing a group's sign-off on a single component that they never check out, but because the component is part of a system where they normally do sign-off on components within
- Example: CEBAF BoxPSs — Most of these are PSS-interlocked, so SSG has sign-off for the HCO/SRM System Box Power Supplies. But, a handful of the 41 BoxPSs aren't PSS-interlocked, so for these (TAG5C, PT0L02, BE3H05) SSG's sign-off is set to NA — this can be undone by-hand if need be, but the sign-off will remain NA until such time
A: See Unpowered vs Masked