LANL Engineering Standards Program Programmatic Requirements in the LANL Engineering Manual

1
LANL Engineering Standards ProgramProgrammatic
Requirements in the LANL Engineering Manual

• Tobin Oruch
• 5-8475, oruch_at_lanl.gov
• June, 2002
• Facility and Waste Operations Division (FWO)
• Systems, Engineering and Maintenance Group

2
Outline

• Background
• The Issues
• Path Forward

3
Background -- 1998

• LIR220-03-01, Facility Engineering Manual, issued
  1997
• Mandated the pre-flatland Facility Engineering,
  Construction Spec, and Drafting Manuals
  (developed over past 20 years)
• Designated Facilities Eng as OIC
• Committees with POCs maintain each discipline
  chapter
• Scope was facilities design engineering
• New facilities and modification of existing
  facilities
• Purposes included
• Aid in Works Smart Standard implementation
• Ensure safety and long-term cost effectiveness
• by considering OM costs and issues

4
Standards Team Structure, 2000-2001
5
Background -- circa FY01

• 10 CFR 830 rev clarifies activities included,
  must follow tech standards DNFSB expects same
• No LANL-wide vehicle existed to promulgate
  technical standards to programmatic groups
• TA-55 Type A Incident needed to include material
  not primarily facility-related
• Swagelok fitting installation
• Teflon seals in radioactive service
• Glovebox design and installation

6
10 CFR 830.122 1/2001

• (e) Criterion 5--Performance/Work Processes
• (1) Perform work consistent with technical
  standards, administrative controls
• (f) Criterion 6 -- Performance/Design
• (1) Design items and processes using sound
  engineering/scientific principles and appropriate
  standards

7
Background, FY01 cont.

• LIR revised June 2001
• Renamed Facility Eng Manual to LANL Eng Manual
  (LEM)
• Made most Chapter POCs the AHJ for that
  discipline
• e.g., Mechanical POC is AHJ for piping issues
• Included programmatic work in scope, but to
  impose requirements
• Each must be specifically identified in manuals
  and
• to help programs easily identify them
• Need consensus of Lab POCs on final review

8
Today -- FY02

• The Engineering Manual is being revised
• As of 6/2002, Type A driven and some Mechanical
  and IC requirements have been identified for
  programs
• Required codes and standards (selected)
• Gloveboxes, Teflon, and compression fittings
• Pressure systems
• Requirements for nuclear systems
• Some other aspects, though potentially
  applicable, were consciously not. Some
  mechanical examples
• cross-connection control
• freeze protection
• high-value equipment protection
• liquid waste

9
The Issues

• Limited scope Liability with not identifying all
  potentially applicable requirements.
• Involvement Little programmatic representation
  on discipline or steering committees, only final
  review.
• Authority Who has the knowledge and authority
  to waive programmatic compliance?
• Currently Facilities Division Leader must concur
  with Programmatic Division Leader (per Variance
  LIR process).

10
Current Team Structure Lacks Program Input
11
Path Forward

• Work with programmatic Divisions to appoint one
  or more POCs who can work with Standards Program
  to resolve scope, involvement, and authority
  issues
• Further possibilities
• POCs elect programmatic representative(s) to the
  LEM oversight board
• POCs select representatives to LEM discipline
  technical committees