Controls Group Meeting, February 22, 2006

Attendees:

Agenda:

1. Discuss Safety topics
2. Review network plans.
3. Review the schedule.

Previous Actions:

1. None from last week.

New Actions: (summary; see details below)

1. Doug will check that a router can successfully route all required traffic, including AFS, to and from a private Class A IP Address range.

Minutes:

1. Patrick Bong asked if a weekly status report is required if there's nothing new or substantial to report. Hamid said Yes, he needs an indication of what is being worked on.
2. Hamid discussed Safety issues at SLAC, and how the DOE tracks our safety record.
   1. Last year's record was good, but now the bar has been raised. Various metrics are being gathered, and small things are being noticed.
   2. Hamid mentioned that the number 1 source of injury comes from moving materials. He said that we as individuals are responsible for preventing injuries.
   3. Mario suggested that some of these small injuries might be avoided if people plan to pre-install crates and instrumentation in central areas, such as Bldg 24.
   4. Kristi asked if we could call upon people from the labor pool for moving this equipment, it was agreed that we could.
3. Doug presented plans for the Controls Network
   1. Basic requirements were presented, as well as various design options.
   2. We discussed physical aspects of the network, as well as logical topology; there was discussion of the choice of a private IP address range.
   3. Stephanie once again voiced a concern about being able to access AFS from the control system if it uses Class A private addressing. AFS will be made available for use at specific times for debugging purposes from the controls network. ^Action: Doug will check that the router can successfully route all required traffic, including AFS, to and from a private Class A IP Address range. ^
   4. Tentative schedules were included. The network to the injection area is still scheduled to be ready by May 15, 2006.
4. We then discussed the overall controls installation and commissioning schedule
   1. All of our subsystem work require schedules to be done
   2. A physics schedule is being produced, including a high level plan for commissioning.
   3. Kathleen Ratcliffe is working on a low-level detailed installation schedule. Many engineering and development details are being included, down to hourly access and coordination schedules.
   4. Procurement could be an issue; the project plan currently expects us to be spending twice as much compared to our current "burn rate".
   5. The cables have been added to the schedule, and cable contingency is included.
   6. Our schedule must also include details like:
      1. The Controls network infrastructure
      2. The action of preloading racks and crates in Bldg 24.
      3. The transport of loaded racks to sector 20.
      4. Associated wiring installation.
      5. Other elements of infrastructure, such as timing.
   7. Kristi asked if BC1 is still required, since it was added to the controls work list somewhat recently. Patrick said that beam would first go to straight-ahead beam dump (the injection spectrometer, or 135 MeV beam line), then to BC1.
      1. Patrick wondered if we still plan to get beam to end of sector 30. Hamid said he is looking at requirement details now.
      2. Hamid said we should discuss this with everyone in the same room. Patrick suggested we minimize requirements that are above and beyond the original schedule. Everyone agreed, and Hamid summed up by saying we need to constrain requirements to infrastructure and fundamental needs of injection commissioning.