How the NCSX Project Does Business Specifications and Statements of Work 12/3/2004 Module 3

Purpose Provides review of how the NCSX Project does business This module will focus on: Specifications Design Criteria Statements of Work 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 12/3/2004 Module 3

Specifications and Statements of Work (SOW) Statement of Work Guidelines GRD Specifications Specification Format Guidelines Statements of Work (SOWs) 12/3/2004 Module 3

Types of Specifications General Requirements Document (GRD) Top level NCSX Project technical specification and provides a complete set of performance requirements and constraints at the overall project level Overall system requirements in the GRD allocated down to a set of specific developmental requirements and further down to the appropriate product component/procurement level Development (Performance) Specifications Document design requirements for cog engineers System Requirements Documents (SRDs), generally prepared for each 2-digit WBS, are the prime examples Product Specifications Serve as a basis for a procurement or fabrication Product function spec defines the product by specifying its functionality – used when supplier does the design Product fabrication spec defines the product by specifying the design – used when project does the design Other Product specs to be added as necessary Other Specifications Situations may occur that require specifications such as processes or materials Product Requirements List (PRL) Used to specify minimum requirements when purchasing a catalog item when a formal specification would be overkill 12/3/2004 Module 3

General Requirements Document (GRD) Latest version of GRD available on the NCSX Engineering Web Major parts of the GRD System Requirements (Details in Appendix A of GRD) Definition - system elements and functions Characteristics – performance; external interfaces; & physical characteristics (e.g., maximum lift, maximum dimensions, and maximum floor loading) System quality factors – RAM; design life; and transportability Design and Construction – materials, processes and parts; nameplates and product marking; workmanship, interchangeability; ES&H; and human engineering Documentation Logistics – maintenance; supply; and facilities Personnel and training Characteristics of subordinate elements – allocation of requirements down to lower level subsystems (Details in Appendix B to GRD) Verification of Requirements General overview Inspection Verification Methods Quality Conformance (Details in Appendix C of GRD) Notes Section will contain definitions and acronyms 12/3/2004 Module 3

Sample Pages from GRD 12/3/2004 Module 3

Developmental (Performance) Specifications State the requirements for the design or engineering development of a product during the developmental stage (usually preliminary design) – sometimes referred to as System Requirements Documents (SRDs) Should be of sufficient detail to describe effectively that each component within that subsystem is to achieve when it evolves into the detailed design phase Maintained current during development and subsequent production when it is desired to retain a complete statement of performance requirements for a particular subsystem Lower level developmental specifications may be prepared if deemed appropriate NCSX Engineering Web has link to format guidelines for developmental specifications OPTIONAL?? 12/3/2004 Module 3

Developmental Specification Guidelines 12/3/2004 Module 3

Product Specifications Applicable to any component below the subsystem level May be one of several types of product specifications Functional (performance) requirements where the supplier will do the detailed design Format guidelines still under development Fabrication (detailed design) where the project does the detailed design – essentially a “build to print” procurement Format guidelines available 12/3/2004 Module 3

Fabrication Product Specification Guidelines Functional Product Specification Guidelines - TBD Fabrication Product Specification Guidelines Still Out of date Web needs to be updated to reflect PRLs 12/3/2004 Module 3

Other Specifications May be other situations that might require specifications Processes Materials Format guidelines for these specifications will be develop on a case-by-case basis 12/3/2004 Module 3

Product Requirements Lists (PRLs) Used to specify minimum requirements when purchasing a catalog item when a formal specification would be overkill No sample PRL available yet Format guidelines to be developed later 12/3/2004 Module 3

Subsystem Specifications Example: Modular Coils Links to specific WBS element specifications Production Modular Coil Winding Forms 12/3/2004 Module 3

Statements of Work (SOW) Purpose of a Statement of Work (SOW) is to detail the work requirements for projects and programs that have deliverables and/or services performed SOW covers the work requirements and, in conjunction with applicable performance/design requirements contained in specifications, is used for contractual agreements The SOW defines (either directly or by reference to other documents) all non-specification requirements for the supplier effort Technical qualitative and quantitative design and performance requirements are contained in specifications and referenced standards – SOWs typically do not contain technical requirements Typically used to task a supplier to establish, implement, and control specific management programs in terms of results needed rather than “how to manage” procedures SOW also used to require a supplier to establish, implement, and control specific specialty programs (e.g., maintainbility, reliability, configuration management and control, etc.) 12/3/2004 Module 3

Statements of Work Guidelines 12/3/2004 Module 3

Statements of Work (SOW) Single page with links to all the current versions of Statements of Work (SOW) Example: VVSA 12/3/2004 Module 3

Summary This training module has focused on specifications and statements of work Specs define technical qualitative and quantitative design and performance requirements SOWs define (either directly or by reference to other documents) all non-specification requirements for the supplier effort Several types of specifications exist General Requirements Document – top level project specification Requirements and constraints allocated down to lower level subsystems and components Developmental - document design requirements at the system level Product – functional (performance based) and fabrication (“build to print” based) Other – process and material or perhaps others Product Requirements List (PRL) - specifies minimum requirements when purchasing a catalog item when a formal specification would be overkill Statement of Work – usually non-technical in content – sets management systems and specialty systems engineering processes required 12/3/2004 Module 3