1/18/2005Module 41 How the NCSX Project Does Business Work Planning & Design Review Processes

1/18/2005Module 42 Purpose Provides review of how the NCSX Project does business This module will focus on: Work Planning Processes on NCSX, including: Work Plans Jobs/WAFs WP to WAF mapping Later modules to will address other parts of how the NCSX Project will do business Modules 1 & 2 are intended to provide overview of the NCSX Project Web and the NCSX Engineering Web Modules 4-10 will focus other aspects of how the NCSX Project will do business The NCSX Engineering Web is, to a major extent, the electronic NCSX filing system Exceptions are the models and drawings contained in the Pro/INTERALINK data base and the hard copy supplier and other PPPL documents stored in the PPPL Operations Center However – bulk of files stored electronically on this web

1/18/2005Module 43 Work Planning Work Plans Per ENG-032 Jobs (WAFs) Essentially P3 resource loaded schedules Provides authorization to start work WP to WAF Mapping Ensures that every WP has at least one job/WAF associated with it

1/18/2005Module 44 PPPL Work Planning Processes Defined by PPPL Engineering Procedure ENG-032 Applicable to all activities at PPPL involving physical changes to engineering, facilities, control computing, and technical infrastructure and equipment or involving collaborations for others NCSX Project will follow ENG-032 Purpose of ENG-032, Work Planning Procedure, is to: Establish criteria by which work planning will proceed Integrates safety into work planning Organizes the systematic avenues by which changes will be planned, prepared, reviewed, implemented, and documented Key decision maker in this process is the Responsible Line Manager (RLM) List of RLMs found at: RLM will approve Work Plans (WPs) As required, the PPPL Deputy Director shall convene a Work Planning Review Board to review WPs in process to ascertain whether they comply with the graded approach guidelines contained in ENG-032

1/18/2005Module 45 When is a WP Required? RLM, in consultation with the Cognizant Engineer (usually Job Manager), will determine whether or not a WP is required Graded approach provides options that balance priorities, identify ES&H requirements, ensures proper controls, and provide an auditable package upon which to base authorization Graded approach permits alternative procedure to be utilized vs. WP to plan work and mitigate hazards, but the default it to require a WP Regardless to graded approach, a WP is always required if the change: Is large or complex or represents a new installation into a usable space Has a significant ES&H impact Involves Tritium or other radioactive contaminated or activated equipment Impact multiple projects, systems, or groups Changes the scope or intent of the original design

1/18/2005Module 46 Guides to Preparing a WP Work Planning Form is electronic Will need to authenticate to get to this web page: Electronic submittal and signatures PROC-004 provides good guidelines to assist in preparing WP (especially for PDR or FDR) WP leads to preparation of a Job in the Primavera (P3) database

1/18/2005Module 47 What Does a WP Achieve? Systematic way to plan the anticipated requirements of a job Defines the scope of the job Performs Hazard Analysis Factors into planning all potential environmental, safety, and health issues Establishes procedural and testing requirements Establishes clear approval indicating ownership of the work

1/18/2005Module 48 PPPL Work Planning Web Page Useful links for using PPPL WP System Sample WP

1/18/2005Module 49 NCSX Design Review Process Design reviews are performed to clarify and verify compliance with functional, project, ES&H, and quality requirements NCSX Project will follow ENG-033 Peer Reviews, Conceptual Design Reviews (CDRs), Preliminary Design Reviews (PDRs), and Final Design Reviews (FDRs) will be conducted and follow requirements of ENG-033 – Design Review Reports, CHITs, etc. In general, all CHITs should be resolved prior to the next design review, and in some instances much sooner Major difference is that on NCSX, all the design review documentation will be stored in an electronic format vs. in hard copy in the Ops Center

1/18/2005Module 410 Guidelines for Conducting Design Review Both ENG-033 and PROC-004 contain design review objectives and design review input documentation The input documentation should be completed and provided to the Design Review Board prior to the review Until all prerequisite design review documentation is completed, the review will NOT be scheduled or held

1/18/2005Module 411 A Process for Electronically Documenting Design Reviews has been Implemented

1/18/2005Module 412 NCSX CHIT/Audit Tracking Log

1/18/2005Module 413 Summary This training module has focused on the work planning and design review processes The NCSX Project is committed to following the requirements and processes contained in: PPPL ENG-032 – Work Planning PPPL ENG-033 – Design Verification (as it pertains to Design Reviews) NCSX PROC-004 augments and supplements ENG-032 and ENG- 033 No exceptions or modifications from compliance with ENG-032 No exceptions or modifications from compliance with ENG-033 with the exception that NCSX design review records will be stored electronically on the NCSX Engineering Web vs. in the Ops Center