NCSX Web Pages  

Project | Management | Physics | Procurement | Manufacturing

NCSX FTP Sites  

Project FTP Server | Supplier FTP Server

Navigation Trail  

Engineering > Documentation of Analyses

Design basis analyses shall be documented and checked prior to completion of final design.  The PPPL procedure defining these requirements is ENG-033 Design Verification.  On the NCSX project, we will apply ENG-033 with the following stipulations for [1] using a graded approach, [2] documenting analyses in formal analysis reports, [2] documenting independent analyses (performed for the purpose of checking) in formal analysis reports, and [3] archiving data files.  Eventually, these changes will be captured in an NCSX-specific procedure for documentation of design basis analyses.


[1] Graded approach.  A graded approach should be followed when performing and checking design basis analyses.  The level of analysis and checking should be commensurate with the associated safety, technical, cost, schedule, and environmental risks.  At a minimum, all design basis analyses shall be formally documented.  A draft analysis report shall be reviewed by a qualified reviewer.  When the reviewer's concerns have been addressed, the analysis report should be signed by the analyst and reviewer.  The analyst's signature verifies that any and all results and recommendations have been accurately recorded along with any caveats and concerns.  The reviewer's signature verifies his or her concurrence with analysis methodology and inputs and with the reasonableness of the results and their interpretation.


For analyses that might have serious consequences if the analysis is flawed, an independent calculation may be warranted to confirm the results of a design basis calculation.  Judgments by the cognizant WBS Manager regarding where independent calculations are (and are not) warranted should be reviewed with the cognizant Project Engineer.  When independent calculations are performed, they shall be documented in formal analysis reports just like the original calculations.


[2] Formal analysis reports.  Formal analysis reports shall be used to document design basis analyses rather than the calculation form provided in ENG-033 Attachment 1. [Note that the items on the calculation form are addressed in the format requirements for the formal analysis reports.]  Analyses should be documented with sufficient rigor that the results are auditable and could be reproduced at a later date.  Data files should be systematically archived. The analyst is responsible for documenting any caveats or concerns regarding the interpretation or application of the results by design engineers and line management.  The analyst is also responsible for identifying additional work that would be appropriate to establish an adequate design basis.   Analysis reports will be numbered per the Document and Records Plans, e.g. NCSX-CALC-14-007-02 where 14 is the (hypothetical) WBS identifier,  007 is the (hypothetical) sequential analysis report number corresponding to that WBS identifier, and 02 is the (hypothetical) revision number.  A cover sheet (in MS Word) can be downloaded by right-clicking here.  Signed analysis reports should be forwarded to the WBS Manager.  The WBS Manager should forward the analysis report to the Engineering Manager (or designee) for posting with instructions detailing what aspect of the design basis is established by the report and if it supersedes any previous reports (which would then be un-posted). (This satisfies the requirement to send the analysis report to the Ops Center because NCSX Project Files are a satellite of the Ops Center.)


Formal analysis reports shall be generated in the following format:


1. Executive summary.  Provide an executive summary of the analysis, documenting the purpose of the analysis and significant conclusions and recommendations. Identify whether this analysis supersedes any previously documented design basis analysis.  Provide references to related documentation.


2. Assumptions. Discuss modeling assumptions.  Highlight those which require further action to validate.


3. Analysis methodology and inputs.  Discuss analysis methodology.  Identify relevant performance requirements and design criteria. Identify inputs to the analysis, including drawings and material properties.


4. Results and interpretation. Provide a discussion of the results of the analysis.


5. Summary and Recommendations.  Provide a summary of the key results along with any caveats or concerns regarding the interpretation or application of the results by design engineers and line management.  Identify additional work that would be appropriate to establish an adequate design basis.


6. Attachments.  Attach input files and/or the location where the input files are archived.  Include the reviewer's notes and calculations as attachments.

[3] Data file archival.  Data files generated as part of the design basis analysis shall be properly archived and identified in the formal analysis report if they are not included directly.


Revised 06/30/2004

Privacy and Security Notice

Please forward comments and questions to the Webmaster