FY 2003 Plans

1. FY 2003 Plans Bob Simmons September 10, 2002

2. Introduction • Overview of Project and Engineering Plans • Project Plans • Engineering Plans • What You Need to Know September 10, 2002

3. Overview of Project and Engineering Plans September 10, 2002

4. Project Guidance Documents • DOE Order 413.3 • Provides DOE guidance for the management of DOE projects • Project Management and Critical Decisions • Configuration Management • Project Control • Acquisition Execution Plan • High level Project response to DOE O 413.3 • Mission • Technical, cost, and schedule objectives (targets) • Procurement strategy • Major project milestones • To be Approved by Under Secretary of Energy September 10, 2002

5. Project Plans • Project Execution Plan (PEP) • Broader discussion of mission and technical objectives • Related to FESAC and Fusion Energy Science Goals • Broad description of project • Outlines project organization and management structure • Outlines management processes (e.g., WBS, project baselines, systems engineering, configuration management, funds management, etc.) • Defines project completion criteria • Approved by Associate Director for Fusion Energy Sciences • Systems Engineering Management Plan (SEMP) • Defines how the Engineering organization will operate September 10, 2002

6. Engineering Organization September 10, 2002

7. Key Features of SEMP • Systems Integration Team • Forum for discussing and resolving engineering issues • Responsible for risk management at the system level • Members • Project Manager, Deputy Project Manager for Programs, Engineering Manager, Physics Manager, Project Control Manager, Systems Engineering Support Manager, Project Engineers (as appropriate) • Specification Hierarchy • “Design to” vs. “Build to” specs • “Design to” specs by PDR • “Build to” specs by FDR • General Requirements Document (GRD) is the highest level specification (ASPEC) • Allocation and flow-down of requirements to lower level specifications • Three project baselines • Technical ( Pro/E models/drawings, specs, etc.), cost (P3 data base), schedule (also in P3 data base) • Changes to these baseline only modified by configuration control process September 10, 2002

8. Key Features of the CMP • Outlines configuration management and details of change control processes • Not all CIs come under Configuration Control at the same time • Initial baselines established at the start of Preliminary Design (Oct 2002) • Developmental “baselines” evolve as the design matures • At design review, unless major change occurs, baselines will be updated and more CIs and documentation placed under Configuration Control • ECP is the vehicle by which the baselines are revised • Stand-alone ECP for significant changes • “Omnibus” ECP September 10, 2002

9. Change Control Board • Change Control Board (CCB) is normal means of reviewing and approving ECPs • Senior NCSX management team members of CCB, but NCSX Project Manager is the Chair => all others in advisory role • Expedited ECP Process • In special circumstances (e.g., critical procurement pending, field activities may be delayed, etc.) special “expedited” process where NCSX Project Engineer reviews and approves ECP with only abbreviated input from others • Full CBB will review ECP “after the fact” to ensure no serious omissions/errors September 10, 2002

10. Engineering Change Proposal • Anyone can initiate a change • Type of change => technical, cost, or schedule (or combination of all) • Reason for change • Impacted WBS elements • Impacts of change => design, performance, requirements, cost, schedule, maintenance, ES&H, RAM • Assessment of other options • Backup detail to support proposed change • Initially will be a paper format, but hopefully, within 6 months, this and many other NCSX engineering forms will be on an interactive web environment • Extensive list of reviewers to mitigate impact of omissions/errors • If DOE approval required, CCB and Project manager will recommend approval and forward to DOE September 10, 2002

11. Implementation of ECP • Status of pending ECP and detailed implementation of ECP will be tracked monthly • Monthly meeting with WBS Managers for status will include discussion of implementing approved ECPs September 10, 2002

12. Updating Project Baselines September 10, 2002

13. Date Storage and Retrieval Sites September 10, 2002

14. Key Features of the DMP • Electronic Project Files • Pro/INTRALINK data base will be the repository for all models and drawings as well as approved and controlled technical and project documents (e.g. specs, plans, etc.) • Pro/INTRALINK Users Manual being prepared • Other sites may also contain critical design information and details September 10, 2002

15. Pro/INTRALINK Folders September 10, 2002

16. Data Management Process September 10, 2002

17. Drawing Release and Configuration Control • Technical baselines established at start of Preliminary Design • Drawing release promotion proposed as lead-in to design review • Following design review and incorporation of CHITS, ECP processed to reflect changes • Baselines updated • Release level finalized and “frozen” to document the baseline • As-built drawings part of the NCSX plan September 10, 2002

18. Key Features of the DOC • Defines the official docments and records for NCSX • Purpose • Content • Format • Approval level • Records retention requirements • Document naming convention • Defines how NCSX Project will meet the requirements of the applicable DOE orders and implementing PPPL policies September 10, 2002

19. Types of Records • Project Definition Agreements • AEP • Project Plans • PEP, SEMP, CMP, DOC, ICMP, etc. • Requirements Documents • GRD and other specs • NEPA Documentation • EA, NEPA Planning Forms, SAD • Quality Assurance Records • Training Records • Other Documents • Memoranda • WBS dictionaries • Cost and schedule documents • Design review records • ECPs September 10, 2002

20. Key Features of the ICMP • Interface Definition • An interface represents a technical agreement between two or more activities or Work Breakdown Structure (WBS) • Documents the functional, performance, and physical characteristics required to exist at a common boundary between the activities or WBS elements. • Interfaces serve as integration constraints to ensure that systems and subsystems mutually can be assembled and/or function together. • Primary interface item • Exists between two separately deliverable items (referred to as Configuration Items/CIs in systems engineering terms) when the mutual boundary area is not controlled by a single WBS manager • Project Engineer determines the interface to be critical to the performance of the NCSX program • ICMP only addresses primary interface definition and management • Secondary interface item • Lies solely within the control of a single WBS Manager, even though it might cross WBS boundaries. September 10, 2002

21. Interface Control Process • Throughout project life cycle • Begins with the concept design phase and with the identification of the basic interface boundaries, continues through the design and fabrication phases, the operational phases, and ends with project shutdown and decommissioning. • Concept design phase • Major functional interfaces identified for each concept being considered • Reflected in the overall Pro/Engineer (Pro/E) models • Preliminary design phase • Scope sheets are prepared early in the preliminary designto initiate agreements that define the primary interfaces required between participants • Scope sheets converted to InterfaceControl Documents (ICDs) at time of PDR => may be in drawing or book entry format • After PDR, come under configuration control September 10, 2002

22. Interface Control Process • Final design process • Primary interfaces defined at the completion of PDR continue to be refined and increased in detail • Functional integration tests using prototypes (when available) and/or increasingly more detailed models and drawings verify that the design has resulted in compatible items • Existing scope sheets and ICDs are updated and any new scope sheets and ICDs representing new primary interfaces are developed as part of the Final Design Review (FDR) package • Fabrication phase • As the need for modifications are identified, the established interfaces are examined for impacts • This iterative process of refining and redefining interfaces continues via the configuration change control processuntil the project is ready for operation September 10, 2002

23. Summary • This presentation has just covered the surface of the content and purpose of each plan under preparation for the preliminary design • Other plans and procedures will be developed to flesh out additional details • Sample of some other plans that will be developed • Experimental Plan (EXP) – provides and overview of the planned phases of NCSX operation • Test and Evaluation Plan (TEP) – provides outline of how the integrated system testing will be performed and managed September 10, 2002