fy 2003 plans

September 10, 2002 1

FY 2003 PlansFY 2003 Plans

Bob Simmons


IntroductionIntroduction

Overview of Project and Engineering PlansProject PlansEngineering PlansWhat You Need to Know


Overview of Project and Overview of Project and Engineering PlansEngineering Plans

D O E O r d e r 4 1 3 .3

N C S X P EP

S y s t e m sEn g i n e e r i n g P l a n

( S EM P )

C o n f i g u r a t i o nM a n a g e m e n t P l a n

( C M P )

D o c u m e n t a n dR e c o r d s P l a n

( D O C )

D a t aM a n a g e m e n tP l a n ( D M P )

In t e r f a c e C o n t r o lM a n a g e m e n tP l a n ( IC M P )

C o n f i g u r a t i o nC o n t r o l

P r o c e d u r e s

P P P LEn g i n e e r i n gP r o c e d u r e s

N C S XP r o j e c t - S p e c i f i cC M P r o c e d u r e s( A s R e q u i r e d )


Project Guidance DocumentsProject 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


Project PlansProject 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


Engineering OrganizationEngineering Organization


Key Features of SEMPKey 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


Key Features of the CMPKey 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


Change Control BoardChange 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


Engineering Change ProposalEngineering 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


Implementation of ECPImplementation 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


Updating Project BaselinesUpdating Project Baselines

S u b m it E C P s f o r s ig n if ic an t c h an g es th a tr eq u ir e an E C P [ W BS M an ag er s ]

Up d ate p r o jec t b as e lin es in c o r p o r a tin gap p r o v ed c h an g es

[ W BS an d P C M g r s ]

D ev elo p ev o lu tio n ar y c h an g es to th e d es ig n[ W BS M an ag er s ]

P er io d ic a lly r ec o n c ile c o s t an d s c h ed u lees tim ates w ith ev o lu tio n ar y c h an g es

[ W BS an d P C M an ag er s ]

D ev elo p o m n ib u s E C P ( if n ec es s ar y ) top r o c es s ev o lu tio n ar y c h an g es n o t

p r ev io u s ly p r o c es s ed an d ac tu a l c o s t an ds c h ed u le p er f o r m an c e [ S E S M g r ]

T r ac k ac tu a l c o s t an d s c h ed u lep er f o r m an c e ag a in s t p r o jec t b as e lin es in

m o n th ly s ta tu s m eetin g s [ P C M g r ]

E s tab lis h P r o jec t b as e lin es[ P r o jec t M an ag er ]


Date Storage and Retrieval Date Storage and Retrieval SitesSites

Storage Location Documents Customer Custodian Access

Project Web General project information, external design review data, physics meetings, advisory committee information, publications, and project directory

General public, Project

Project Manager

Global

Manufacturing Web

All documentation required for potential suppliers to develop proposals and for suppliers to execute their scope of work

Suppliers Engineering Manager (or designee)

Global

FTP Server Large data files primarily used in physics analyses

Physics and engineering analysts

Engineering Manager (or designee)

Global

Intralink Database

Drawings and controlled documents

Project Design Integration Manager

Project (Intralink software required)

Engineering Web All other project documentation including cost and schedule information, design criteria, internal design review data, engineering and project meeting minutes, memoranda, analysis reports, draft versions of controlled documents, and work plans

Project Engineering Manager

Project

Management Web

Documentation that is of a proprietary or sensistive nature

Management Systems Engineering Support Manager

Restricted (password required)


Key Features of the DMPKey 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


Pro/INTRALINK FoldersPro/INTRALINK Folders


Data Management ProcessData Management Process

C M P r o c e s s

C A D D r a w i n g sa n d M o d e l s

O t h e r D o c u m e n ts

D r a w i n g /M o d e lR e l e a s e S c h e m ep e r S e c t i o n 2 .3

S p e c i f i c a t i o n s &P r o c e d u r e s

P r o j e c tM a n a g e m e n t

P l a n s

A p p r o ve d ?It e r a t e U n t i l

A p p r o ve d

If R e q u i r e d , P r o c e s sEC P p e r C M P t o A d dt o /U p d a t e Te c h n i c a l

B a s e l i n e

P o s t U p d a t e d Te c h n i c a lB a s e l i n e a n d D o c u m e n t si n IN TR A L IN K D a t a B a s e

w h e n A p p r o ve d

N o

Y e s

A p p r o ve d ?It e r a t e U n t i l

A p p r o ve d

N o

Y e s

D r a w i n g /M o d e lr e a d y f o r D e s i g nR e vi e w o r M a j o r

C h a n g e ?

It e r a t e P e rIN TR A L IN KP r o c e d u r e s

Y e s

N o


Drawing Release and Drawing Release and Configuration ControlConfiguration 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


Key Features of the DOCKey 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


Types of RecordsTypes 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


Key Features of the ICMPKey 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.


Interface Control ProcessInterface 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 Interface Control Documents (ICDs) at time of PDR => may be in drawing or book entry format

– After PDR, come under configuration control


Interface Control ProcessInterface 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 process until the project is ready for operation


Summary 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