NIF USER’S GROUP DISCUSSIONNIF HAZARD MANAGEMENT

Contact NIF & PS Principal Directorate Training Privacy & Legal Notice

March 1&2, 2016

L L N L - P R E S - 6 8 4 8 9 1

USER’S GROUP DISCUSSION POINTS

- Target Chamber - Entrant Component Hazard Management Processes

- Beryllium use in Targets

- Potential changes to Max Cred Yield Memo’s

HAZARDOUS MATERIAL USE AT NIF

• Hazardous materials are used at NIF

• Subject of experiment, e.g. Pu, Pb

• Enhance experiment, e.g. U, Be

• Care and diligence is essential to protect worker health and the environment

• In addition, NIF has an established operational safety basis, which defines an envelope of safe and permitted operations

• The safety basis is derived from the Site-Wide Environmental Impact Statement

• The safety basis includes clear limits on hazardous material use

HAZARD MANAGEMENT PROTOCOLS

• NIF has a materials database used for cleanliness purposes

• This database has recently been expanded to include hazardous materials

• Hazardous materials that have been approved for use and associated restrictions on their use

• https://materials.llnl.gov/

• Typical hazardous material entry

Uranium (or U alloy) is mildly radioactive and toxic. Small quantities (approximately 1g or less) of uranium

may be used in target assemblies subject to restrictions in NIF-1000713412, "TC Entrant Materials Hazard

Management".

HAZARD MANAGEMENT PROTOCOLS

• Targets

• Shot Work Authorization Point (WAP) checklist includes a review by the NIF Hazards Review Committee (HRC)

• In addition, materials for each target are reviewed by the HRC prior to use

• The materials database should be used by the target designers/fabricators when considering target materials

• Entrant Diagnostics

• For diagnostic materials, Diagnostic WAP’s include an HRC review

• In addition, the materials database should be used by diagnostic designers/fabricators when considering diagnostic materials

BERYLLIUM AT NIF

• In CY 2015, NIF deployed 525 mg of Be material as target components in 51 experiments.

• Diagnostic filters made of beryllium are also commonly used but remain intact during experiments

• The initial controls for Be-containing targets, which included respiratory protection and Be Work Area designation, have been relaxed

• Based on extensive survey data that has expanded NIF’s knowledge regarding the fate of this material when used in targets.

• Currently, no additional PPE/Postings (above those used for tritium) are used for routine (<20 mg) beryllium target shots

MORE BERYLLIUM AT NIF

• NIF’s use of beryllium is expanding

• As of last week, 247 mg used in 18 Targets for 2016

• About ½ of mass of CY15

• About 70% of Be mass is used in reshock/shear-shock experiments

• Contribution of Be samples, capsules and windows/filters is small

• We have measurable accumulation (<RL) from reshock shot series

• RWP now calls for routine wipe down of entrant components after Be shot

BE TARGET MATERIAL FATE

• First-wall panel was removed from the TC and analyzed for Be material

• About 90% of Be adheres tightly to first-wall panel surfaces

• About 10% is removable (swipe)

• Based on use rate and noted fixed/dispersible relationship, current contamination levels in the TC are now expected to be slightly above the release limit

BE USE - CONCERNS• As contamination builds –

• Hazard management during TC entries becomes more burdensome

• There is a concern that elevated levels of dispersible Be could eventually impact entrant components on non-Be shots (dragging down shot rate)

• In addition, safety rules associated with Be use are getting stricter and may lead to increased hazard management burdens

• As such, using Be in targets should be considered carefully

• In addition, the mass of Be used should be minimized when Be is determined to be essential

POTENTIAL MCY CHANGES

• Maximum Credible Yield (MCY) evaluations are used to determine how the facility is configured to address radiological hazards

• The level of facility time and effort increases significantly from Cat A to Cat B to Cat C shots

In addition to cycling 47 shield doors and physically sweeping all levels of the TB/SYs, Cat C experiments require a 7-hour, pre-shot

Restricted Access period

POTENTIAL MCY CHANGES

Experiment Type # Shots in 2015

Current Yield Bin

ReclassYieldBin

SymCap, ConA w/ DT gas 6 C B

EXPL w/DT & glass capsule 2 C B

Symcap with with deuterated buried layer capsule and TH fuel 9 C A

PDD with 100%D 5 B A

SymCap, ConA w/ 100% D2 gas 10 B A

There is currently an effort to reclassify the categories of some experimental configurations based on experience (empirical data) and better refinement of variables.

If effort is successful, only ignition experiments will be current campaign involving Cat C shots

HAZARDOUS MATERIALS AT NIF

• If you have any questions about

• Material use

• Control processes

• Approval/Authorization processes

• Or how NIF Operations might help you with your experimental endeavors

• Please contact

Ken Kasper, CIH, CHPNIF Radiological Operations ManagerHazards Review Committee Chair925-423-6151kasper8llnl.gov

LLNL-PRES-684891This work was performed under the auspices of the U.S. Department of Energy by Lawrence Livermore National Laboratory under contract DE-AC52-07NA27344. Lawrence Livermore National Security, LLC

CMT to SRE Transition PlansNIF User Forum

Douglas SpeckShot Configuration Team Lead

March 1 & 2, 2016

LLNL-PRES-xxxxxx14

What is SRE?

Key features of the migration

Advantages of the planned migration approach

How can users help?

Agenda

LLNL-PRES-xxxxxx15

Web-based editor

Similar “spreadsheet” style primary interface but with many enhancements— Permits simultaneous editing of experiments from multiple campaigns— Enables simultaneous editing of different data groups within an

experiment by different users— Updated version of CMT’s “Laser Editor”— “Express” target diagnostic setups to offer simplified interfaces and more

automation (in addition to traditional detailed view)— Will leverage “Common Data Model” to inherit data directly from Shot

Planner - “reuse” instead of “re-entry”— Plots of time-domain setup data, push notifications, rich experiment

histories, and more…(eventually)

You know what CMT is, what is SRE?

LLNL-PRES-xxxxxx16

Planned transition migrates CMT setups, adds new TDs and new features over ~five quarters “Bridge” features will ease dual-editor workflow

— Bi-directional launch of the other editor into same experiment— Traditional “experiment scope” operations (validation, save, submit all, export) will

still span all data groups regardless of where they live

CMT will shrink as SRE grows— A data group (e.g. a target diagnostic) will be editable in either CMT or SRE, never

both• Software complexity for overlapping edit capability is high, decreasing reliability and

performance, increasing maintenance cost• Continuing support for all data groups in CMT until it’s eliminated would mean much larger

dev team workload – not feasible

Eliminating CMT is a primary goal; realizing full suite of new features will follow that— But many new features will be enabled early on as they are tied to basic architecture

(e.g., editing experiments from multiple campaigns simultaneously)

Program has agreed to cap new CMT development following a few high priority additions

LLNL-PRES-xxxxxx17

Multiple motivations and priorities to consider— Support new TDs in SRE first so everything is supported somewhere— Major programmatic goals carrying large existing investments and/or high

payoff (TanDM, Gatling, new TDs)— Shot RI’s have requested that the Laser setup be a priority— Target Systems has planned significant rework, but won’t happen in CMT— Free developer resources from focusing on CMT ASAP

Emerging priorities1. Subset of new TD deployments (deferred to minimize effort in CMT)2. Laser setup3. TanDM/DIM needed for ICCS Jan 2017 – requires DIMs and DIM-based TDs4. Target Systems (still needs priority discussion)5. Non-DIM TDs6. Gatling support7. Remaining new features, assistant applications

Detailed migration plan is under development

LLNL-PRES-xxxxxx18

A few migration plans are firm now

Q4 FY16 Q4 FY17

DIM, TanDM, DIM-based diagnostics

AXIS

Laser

Target Systems

Other TD

Other TD

Other TD

Other TD

FFLEX, EHXI

GCD

SPBT Fibers

OTS

RT NADCMT

SREDIM, TanDM, DIM-based diagnostics

Laser

Target Systems

Other TD

Other TD

Other TD

Other TD

FFLEX, EHXI

DIM, TanDM, DIM-based diagnostics

Target Systems

Other TD

Other TD

Other TD

Other TD

FFLEX, EHXI

DIM, TanDM, DIM-based diagnostics

Target Systems

Other TD

Other TD

Other TD

Other TD

FFLEX, EHXI

AXIS

SPBT FibersSPBT Fibers

GCD

AXIS

DIM, TanDM, DIM-based diagnostics

Laser

FFLEX, EHXI

Laser

SPBT Fibers

AXIS

Laser

Laser

Other TD

Initial release

TanDM/DIM 1/17

Migration Plans

Firm: First release will have FFLEX & EHXI

Pretty firm: AXIS & deferred new TDs (some) next

Firm: TanDM/DIM needed for ICCS 1/17

Then what?

Target Systems

*Migration order shown is not definitive

LLNL-PRES-xxxxxx19

A “big bang” deployment – flip the switch from CMT to SRE in one step – would entail high risk and would delay use of new editor until it’s complete (end of FY17)

Opportunity to verify basic functionality of new code while main production burden is still carried by CMT

Opportunity to evolve and refine the GUI as user base increases in steps

Incremental training of users

Most users will be able to use the new tool well before the migration is complete

The dual editor migration increases user tool count, but also offers valuable long-term benefits

LLNL-PRES-xxxxxx20

Let the program know your migration priorities

Participate with the Dev Team – this is your tool, not ours— Come to Shot RI/Dev team meetings (every two or three weeks), observe

demo and share your ideas— Diagnostic RS’ needed to work with Dev Team to define what an

“express” setup is for their TD

Take advantage of the transition time after initial release to help us evolve tool to be the best it can be— Developer resources will move on to other projects after major

milestones are completed in late FY17, lessening subsequent pace of development

Work with other users to arrive at consensus opinions about desirable features and priorities

How can the user community help?