1 / 16

Facility Preparation May 2005

Facility Preparation May 2005. 2M. Upon successful completion of this topic, the student should be able to:. Describe facility preparation considerations including: Planning Timing Verification. Planning for Failure. Project Management. Define the work scope . . .

iman
Download Presentation

Facility Preparation May 2005

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. Facility PreparationMay 2005 2M

  2. Upon successful completion of this topic, the student should be able to: • Describe facility preparation considerations including: • Planning • Timing • Verification May 2005 Revision

  3. Planning for Failure May 2005 Revision

  4. Project Management • Define the work scope . . . • Construction, modification, support SSCs . . . • Equipment testing and subsequent repairs . . . • Documentation development-DSA, procedures, etc. . . . • Training, qualification, surrogate operations . . . • Identify task relationships . . . • Predecessor: Procedures . . . • Successor: Operator Training . . . • Plan realistic task duration . . . Essential! • When changes occur, identify all affected tasks . . . May 2005 Revision

  5. The Authorization Basis • Authorization Basis means the combination of information relating to the control of hazards at a nuclear facility (including design, engineering analyses, and administrative controls) upon which DOE depends for its conclusion that activities at the facility can be conducted safely. May 2005 Revision

  6. Authorization Basis (continued) • The Authorization Basis is described in documents such as: - Facility DSA/SARs/BIOs/HAR, other safety analyses; - TSRs/OSR/ABCD . . . • Safety Evaluation Reports (SERs) . . . • Facility-specific implementing mechanisms to comply w/ DOE Orders, policies, or other contract provisions (infrastructure program) . . . • Permits . . . May 2005 Revision

  7. Definition: Safety Analysis • A documented process to: • Provide a definition of the work and identification of hazards within a DOE activity or facility; • Analyze and evaluate potential accidents and their associated risks; • Evaluate measures (hardware, procedures, systems) to reduce the probability and/or consequences of potential accidents; • Develop/define specific engineered and administrative controls to provide an acceptable level of risk. May 2005 Revision

  8. Technical Safety Requirements (TSRs) • The TSR and its appendices constitute an agreement or contract between the DOE and the facility operating management regarding the safe operation of the facility. • As such, they cannot be changed without DOE approval! • OSRs have similar expectations. May 2005 Revision

  9. Safety Evaluation Reports (SERs) • The DOE will/should: • document its review of an DSA/SAR with a Safety Evaluation Report (SER) . . . • impose conditions of approval, which might include constraints on TSRs, additional or alterations to other commitments . . . May 2005 Revision

  10. Implementation ofDSA/SAR/TSR/BIO/JCO • A critical element of achieving readiness: • Identify commitments; • Develop implementing mechanisms; • Develop implementation matrix; • Track implementation to closure; • Verify implementation is complete and accurate. May 2005 Revision

  11. Implementation Means: • Engineered controls in place and tested; • Procedures complete, V&V, CM; • Training complete; • Surveillances demonstrated and current; • Management programs in place: • Specific Administrative controls implemented and verified effective. • Issues and other Tracking systems functioning. May 2005 Revision

  12. If it’s so easy... Why is it so hard? • Started before readiness was achieved . . . And / or . . . • Preparation = ORR/RA review areas! May 2005 Revision

  13. Overcoming the Barriers • Plan for achieving readiness = POA = ORR/RA; • POA adequately specific . . . • POA with proper prerequisites . . . • POA done EARLY . . . • Thorough MSA . . . • In process evaluation; QA criterion 9 . . . • Don’t start early! May 2005 Revision

  14. Prerequisites • Detailed and Measurable . . . • Specific Startup Requirements: • Identify ALL SSCs including support systems . . . • Tied to Core Requirements - are they met? • Specific Actions: • Operator Training Requirements Completed; • Procedures Finalized (V&V); • Test Program Complete, results approved; • DSA fully implemented; etc; . . . • Part of Project Planning: Demonstrated Success! May 2005 Revision

  15. Plan to Achieve Readiness • Address Achieving Core Requirements in the Schedule: • Prerequisites! • Allow Time for Implementation: • Training . . . • Procedure V&V . . . • Practice . . . • Can’t Start Too Early! May 2005 Revision

  16. Commitment to Achieve Readiness • A “failed” ORR is “not a good thing”! • The best manager can control schedule OR cost, but not both in preparing for the ORR/RA! • Make decision: cost versus budget; take action early . . . • Watch for symptoms of failure . . . • You get what you INSPECT . . . • Parallel MSA will reduce rework, cost, and schedule impact if management is “Serious” . . . • “Pay me now, or Pay me later”. . . May 2005 Revision

More Related