ICS – Software Engineering Group

1

Status of SNS

Carl Lionberger

ICS – Software Engineering Group

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.

ICS – Software Engineering Group

3

SNS Construction Progress

ICS – Software Engineering Group

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

675,000

725,000

775,000

825,000

875,000

925,000

975,000

1,025,000

1,075,000

$ x

1,00

0

BCWS 725,986 748,313 772,047 801,414 827,466 862,289 889,503 917,496 942,960 970,402 993,860 1,032,874

BCWP 706,250 726,079 753,394 777,779

ACWP 703,753 725,446 756,820 780,541

Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep

….. BCWS

___ BCWP

___ ACWP

ICS – Software Engineering Group

5

Multi-Lab project

ICS – Software Engineering Group

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

SNS Staffing - ORNL

0

100

200

300

400

Plan 320 319 347 264

Average 107 177 238 291 326

FY99 FY00 FY01 FY02 FY03 FY04 FY05 FY06

SNS Staffing - Other Labs

0

100

200

300

400

Plan 294 174 51 4

Average 151 252 315 314 280

FY99 FY00 FY01 FY02 FY03 FY04 FY05 FY06

SNS Staffing - AE/CM

0

100

200

300

400

Plan 56 14 2 0

Average 17 89 122 77 66

FY99 FY00 FY01 FY02 FY03 FY04 FY05 FY06

ICS – Software Engineering Group

7

Multiple Labs Advantages

• Many teams working concurrently• Labs working on parts that are their

specialties

ICS – Software Engineering Group

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

ICS – Software Engineering Group

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

ICS – Software Engineering Group

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.

ICS – Software Engineering Group

11

EPICS components 2

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

ICS – Software Engineering Group

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.