1 / 12

Status of SNS

The Spallation Neutron Source (SNS) project progresses efficiently, funded adequately with stellar ES&H performance, on track for a 2006 completion. Teams manage challenges of multiple labs, realizing EPICS controls integration benefits but acknowledging further coordination needs for successful operation.

mazar
Download Presentation

Status of SNS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Status of SNS Carl Lionberger

  2. Spallation Neutron Source • The SNS will begin operation in 2006 • At 1.4 MW it will be ~8x ISIS, the world’s leading pulsed spallation source • The peak neutron flux will be ~20-100x ILL • SNS will be the world’s leading facility for neutron scattering.

  3. SNS Construction Progress

  4. Project Status • The FY 2003 request was $225M, fully funded minus $3M due to rescission • Impact being evaluated • The FY 2004 request is $143M as expected • Overall project design is 87% complete • Overall the project is 58% complete (through January 2003) and within budget and schedule constraints • $1.4B and June 2006 completion • Contingency is adequate at 19% • ES&H performance outstanding • >1.9 million construction site work hours without lost workday injury ….. BCWS ___ BCWP ___ ACWP

  5. Multi-Lab project

  6. SNS Project Staffing • FY 2003 Project Average Staffing Through Jan. 2003: • 2 FTEs above the FY 2003 plan average - 670 • 672 FTEs, a decrease of 4 FTEs from December • Staffing Actuals for Jan. 2003: • 655 FTEs, a decrease of 38 FTEs from 693 FTEs in December

  7. Multiple Labs Advantages • Many teams working concurrently • Labs working on parts that are their specialties

  8. Multiple Labs Problems • All using EPICS, but often differently • Naming conventions and other standardizations are more important than they seem • Last minute integration (at least from ORNL point of view) • Developers don’t come with the system

  9. How far along are controls? • Much is still at other labs but ready for installation; task of local staff largely integration. • CF, Front end and 2 DTLS as well as overall patterns of timing, MPS, PPS and vacuum controls done. • 25 iocs out of 150 online • Also 250 NADS

  10. EPICS components • Operator screens • We have lots, often eng level • Alarm Handler previously not used- next run will indicate current success. • Archiver – archiving lots of channels, needs some refinement • Lots of physics apps that use JCA are well along. • Matlab also useable tool with MCA • BURT not in use previously – we have developed jburt - again, next run will tell.

  11. EPICS components 2 • Striptool heavily used in operations • Bumpless reboot widely used • Elog developed and used • IOC logging using EPICS logserver

  12. Conclusions • We couldn’t do things this way without EPICS • Need fewer people • Equipment shows up with a compatible control system • Even with EPICS there are still ownership and local practices issues • We have a lot of work left to do.

More Related