Lesson 9: Structure of an NCSE. Outline   Accident presentations   LA report in Public area   Structure of an NCSE   Example DOC in Public area.

Slides:



Advertisements
Similar presentations
DT Coursework By D. Henwood.
Advertisements

Software Quality Assurance Plan
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
First Article Inspection Report
Anatomy Laboratory Write up Emulate standard Scientific Paper (few exceptions)
Project Bidding Procedures Enhancing Data and Presentation Skills for Engineers EDASPE Writing the RFP Training Courses – July 2004.
Copyright © 2003 by The McGraw-Hill Companies, Inc. All rights reserved. Business and Administrative Communication SIXTH EDITION.
Chapter 18 Working Drawings.
Technical Writing II Acknowledgement: –This lecture notes are based on many on-line documents. –I would like to thank these authors who make the documents.
PURPOSE OF DFMEA (DESIGN FAILURE MODE EFFECTS ANALYSIS)
Writing tips Based on Michael Kremer’s “Checklist”,
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 9 Kendall & Kendall Systems Analysis and Design, 9e Process Specifications.
Secure System Administration & Certification DITSCAP Manual (Chapter 6) Phase 4 Post Accreditation Stephen I. Khan Ted Chapman University of Tulsa Department.
Chapter 1 Program Design
Build a Thermometer Screen Design and Technology – Thermometer Screen Project Name___________ Date ___________.
Software Development, Programming, Testing & Implementation.
The Project AH Computing. Functional Requirements  What the product must do!  Examples attractive welcome screen all options available as clickable.
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 9 Kendall & Kendall Systems Analysis and Design, 9e Process Specifications.
Unit 2: Engineering Design Process
 For the IB Diploma Programme psychology course, the experimental method is defined as requiring: 1. The manipulation of one independent variable while.
CS 501: Software Engineering Fall 1999 Lecture 16 Verification and Validation.
Data Structures & AlgorithmsIT 0501 Algorithm Analysis I.
FCS - AAO - DM COMPE/SE/ISE 492 Senior Project 2 System/Software Test Documentation (STD) System/Software Test Documentation (STD)
Fundamentals of Data Analysis Lecture 9 Management of data sets and improving the precision of measurement.
Lesson 3: Hand calculations
Introduction Algorithms and Conventions The design and analysis of algorithms is the core subject matter of Computer Science. Given a problem, we want.
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
1 CMPT 275 Software Engineering Requirements Gathering Activity Janice Regan,
© 2001 Business & Information Systems 2/e1 Chapter 8 Personal Productivity and Problem Solving.
Lead Black Slide Powered by DeSiaMore1. 2 Chapter 8 Personal Productivity and Problem Solving.
BSBPMG505A Manage Project Quality Manage Project Quality Project Quality Processes Diploma of Project Management Qualification Code BSB51507 Unit.
Algorithms and Algorithm Analysis The “fun” stuff.
Lesson 5: ANSI/ANS standards. Organizations  American National Standards Institute (ANSI)  Promulgation of standards  Nation’s point guard for international.
Introduction To Engineering Bike Lab 1 – 4 Report Agenda: Lab Report Format Team Writing Outline Lab 1 Report.
NCHRP Project Development of Verification and Validation Procedures for Computer Simulation use in Roadside Safety Applications SURVEY OF PRACTITIONERS.
Apply Quality Management Techniques Project Quality Processes Certificate IV in Project Management Qualification Code BSB41507 Unit Code BSBPMG404A.
CMSC 345 Fall 2000 Requirements Overview. Work with customers to elicit requirements by asking questions, demonstrating similar systems, developing prototypes,
Building Simulation Model In this lecture, we are interested in whether a simulation model is accurate representation of the real system. We are interested.
Implementation Phase CS4311 – Spring 2008 References: Shach, Object Oriented and Classical Software Engineering E. Braude, Software Engineering, an Object-Oriented.
The Software Development Process
PROGRAM DEVELOPMENT CYCLE. Problem Statement: Problem Statement help diagnose the situation so that your focus is on the problem, helpful tools at this.
Hazard Categorization Reduction via Nature of the Process Argument Chelise Van De Graaff J. Todd Taylor Chad Pope, PhD, PE Idaho National Laboratory.
Healthy Futures Performance Measures Session. Session Overview Combination of presentation and interactive components Time at the end of the session for.
BSBPMG404A Apply Quality Management Techniques Apply Quality Management Techniques Project Quality Processes C ertificate IV in Project Management
Lesson 2: MAGICMERV  Get SCALE  Thinking like a neutron  MAGICMERV.
DESIGNING AN ARTICLE Effective Writing 3. Objectives Raising awareness of the format, requirements and features of scientific articles Sharing information.
1 The Software Development Process ► Systems analysis ► Systems design ► Implementation ► Testing ► Documentation ► Evaluation ► Maintenance.
Internal assessment, Results, Discussion, and Format By Mr Daniel Hansson.
Copyright © 2011 Pearson Education Process Specifications and Structured Decisions Systems Analysis and Design, 8e Kendall & Kendall Global Edition 9.
Program Design. Simple Program Design, Fourth Edition Chapter 1 2 Objectives In this chapter you will be able to: Describe the steps in the program development.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
Assistant Instructor Nian K. Ghafoor Feb Definition of Proposal Proposal is a plan for master’s thesis or doctoral dissertation which provides the.
Sample paper in APA style Sample paper in APA style.
Abstract  An abstract is a concise summary of a larger project (a thesis, research report, performance, service project, etc.) that concisely describes.
Computer Security: Principles and Practice First Edition by William Stallings and Lawrie Brown Lecture slides by Lawrie Brown Chapter 17 – IT Security.
Report Writing Lecturer: Mrs Shadha Abbas جامعة كربلاء كلية العلوم الطبية التطبيقية قسم الصحة البيئية University of Kerbala College of Applied Medical.
SENIOR THESIS Chapters IV & V. Chapter IV: Presentation of Findings  show and tell the results of your research  Just a few pages!  Introduction 
World Health Organization
3.1 Fundamentals of algorithms
Software Requirements
Tutorial 5: Working with Excel Tables, PivotTables, and PivotCharts
Topics Introduction to Repetition Structures
Lab Roles and Lab Report
Forecasting Project Format
Data Analysis & Report Writing
Software Documentation
An Introduction to Structured Program Design in COBOL
Introduction to Engineering Design II (IE 202)
MECH 3550 : Simulation & Visualization
Speaker’s Name, SAP Month 00, 2017
Presentation transcript:

Lesson 9: Structure of an NCSE

Outline   Accident presentations   LA report in Public area   Structure of an NCSE   Example DOC in Public area

Accident presentations

Accident presentation   LA report in Public area   Use but not ONLY. Do some (internet) research   Not only the descriptions in LA-13638, but also look at p and Appendix B   Assignments and instructions in Public area

Structure of an NCSE

Cover sheet   Strict format: see example   Evaluation is YOUR first three initials plus -01

Outline of Typical CSE  Introduction  Description of process  Computational methodology  Discussion of contingencies  Evaluation and results  Design features and administrative controls  Summary & conclusions  Appendices

Introduction  Why the work is being done  Revision history  Necessary administrative boilerplate

Outline of Typical CSE  Introduction  Description of process  Computational methodology  Discussion of contingencies  Evaluation and results  Design features and administrative controls  Summary & conclusions  Appendices

Description of process  Necessary description of the process  Overview of the procedural steps  Important interactions with preceding and following processes (and any others)  Necessary description of the hardware  Gloveboxes, canisters, storage racks, etc.  Relative positions, etc.  Special materials  Different variations allowed in geometry and process (important to criticality)  Compare to the Contingency Table to make sure that all of the relevant MAGICMERV normal parameters are mentioned

Outline of Typical CSE  Introduction  Description of process  Computational methodology  Discussion of contingencies  Evaluation and results  Design features and administrative controls  Summary & conclusions  Appendices

Computational Methodology  Non-KENO  Indication that relying on ANS-8.1 limits and/or hand calculational techniques  KENO  Indication that relying on criticality calculations+ Basis of criticality control (k-safe) Basis of criticality control (k-safe)  Boilerplate on the codes used  Description of the computer used Point to the verification document Point to the verification document  Summarize validation and point to the Validation appendix

Outline of Typical CSE  Introduction  Description of process  Computational methodology  Discussion of contingencies  Evaluation and results  Design features and administrative controls  Summary & conclusions  Appendices

Discussion of contingencies  Parametric review: Checklist of parameters important to criticality in THIS analysis  mass, absorbers, geometry, interaction, concentration, moderation, enrichment, reflection, volume  Contingency analysis  Definition of normal case vs. parameters  Definition of credible accidents vs. parameters  Contingency table including controls

Discussion of contingencies (2)  Summarized in the table  Mass: Normal and Contingency should have included his actual mass limits (3.1*1.2 and 3.1*1.2*2 kg)  Geometry: Should have said cylinder  Enrichment: Normal should have said 100%, not N/A  Volume: Should have done the math under Normal and said 4.4 L

Discussion of contingencies (3)  There is one subsection per MAGICMERV parameter  All contingencies in the category should be listed and described  Each should include a statement of why it is unlikely  Student was counted off for saying UNUSED parameters were “not considered as a contingency” rather than “not controlled”

Outline of Typical CSE  Introduction  Description of process  Computational methodology  Discussion of contingencies   Evaluation and results  Design features and administrative controls  Summary & conclusions  Appendices

Evaluation and results  Materials discussion, including assumptions (point to appendix)  Normal Model development  Normal & accident  Simplified through the use of parametric studies  Contingency case models as variation on normal model

Evaluation and results (2)  JUST DO IT: Calculate the normal case and each of the contingencies you have identified  Table of results that stands alone  Like Tables in Section 6.4 of ExampleCSE  Enough column to differentiate cases (repeat columns from contingency table, if desired)  Keff+/-sigma column AND Keff+2sigma column  Mark the limiting case with BOLD or larger font (or both)  Discuss results in text

Evaluation and results (3)  Table of results that stands alone  Like Tables in Section 6.4 of ExampleCSE  Enough column to differentiate cases (repeat columns from contingency table, if desired)  Keff+/-sigma column AND Keff+2sigma column  Mark the limiting case with BOLD or larger font (or both)

Table x. Calculational Results Case Description column(s) keff k-eff+2  21

Outline of Typical CSE  Introduction  Description of process  Computational methodology  Discussion of contingencies  Evaluation and results  Design features and administrative controls  Summary & conclusions  Appendices

Design features and administrative controls  Description of:  Engineered safety features  Posted controls  Most important and most often referred to  Very controlled format  Control 7.x.x: Actual posting wording  Basis: Follow the example, pointing back to the text  In addition, Appendix C contains PowerPoint slide examples of the Postings themselves

WHAT you control  Limits are set so that criticality cannot occur when operators comply with the limits  Examples  Mass limit is 350 g 235 U (i.e., maximum mass)  Mass limit is 200 g 239 Pu (i.e., maximum mass)  Concentration limit is 1 g 235 U/liter (i.e., maximum concentration)  Moderation limit is H/U = 4 (i.e., maximum moderation)  Volume limit is 4 liters (i.e., maximum volume)  Container limit is 4 containers (i.e., maximum number of containers)  Spacing limit is 2 feet (i.e., minimum spacing)  Stacking limit is 4 high (i.e., maximum number of items in a stack)

HOW you control  The example did NOT use Engineered safety features, which I like to see  Remember our preference 1. Passive control: railroad bridge over highway 2. Active control: lights and gate at railroad crossing 3. Administrative: stop sign at railroad crossing

Design features and administrative controls (2)  As we discussed before, Section 7 contains the postings and basis for each  In addition, Appendix C contains PowerPoint slide examples of the Postings themselves

Outline of Typical CSE  Introduction  Description of process  Computational methodology  Discussion of contingencies  Evaluation and results  Postings & controls  Summary & conclusions  Appendices

Summary & conclusions  Summary  Conclusions

Appendices  A. Materials and compositions  B. Input and output listings  C. Postings  D. Comment review sheets (N/A)  E. Validation check sheets (N/A)  F. IDC Listing for wet residues (N/A)  G. Validation report  H. Parametric studies

Final report requirements In the final report, you need to add the remaining sections:  Section 8, Summary and conclusions  References  App. A, Material and geometry descriptions  App. B, Input and output listings  App. D, Comment review sheets  App. G, Validation Plus, clean up the other sections based on my comments The Final Report MUST stand alone—no cutting and pasting required by the professor!

Parametric study example (worksheet) 31

Control Selection  Passive engineered control examples  Mass: container design (i.e., limit container size)  Absorption: solid poisons (Raschig rings, boron-Al plates  Geometry: container design (slab tanks, pencil tanks, bottle diameter)  Interaction: spacers (storage racks, bird cages, carts)  Moderation: sealed containers or systems (covers on storage racks to exclude sprinkler water)  Reflection: spacers (storage racks, bird cages)  Volume: container design

Writing Controls  Clear  Concise  Unambiguous  Doable  Simple and easy to perform  Directly controllable by operator  Language that an operator will understand  Relates to upset/change that needs to be prevented

Procedures- General  Procedures provide instructions to perform tasks:  Administrative  Technical  Maintenance  Emergency  Ranked according to safety significance  Procedures for fissionable material operations are reviewed by NCS Engineers  Should be scheduled  Comments should be documented  Comment resolution/procedure approval is documented  Good “conduct of operations” requires verbatim compliance with procedures (so make sure it is possible!)

 Immediate information that the operator would NOT be expected to remember from training  Very controlled format in Sect. 7  Control  Basis: Tied directly to Section 5 (Do not add or subtract)  Similarly controlled format in the posting itself:  Important words CAPITALIZED and possibly in a stand-out color  Few articles (a, an, the)  No convoluted IF/THEN syntax (KISS) Postings

Outline of Typical CSE  Introduction  Description of process  Computational methodology  Discussion of contingencies  Normal & accident analysis  Postings & controls  Summary & conclusions  Appendices

Summary & conclusions  Summary  Conclusions

Appendices: Follow examples  A. Materials and compositions  B. Input and output listings: Use COURIER NEW font for listings  C. Postings: WYSIWYG using colors  D. Comment review sheets (Deleted - no longer required)  E. Validation check sheets (Deleted - no longer required)  F. IDC Listing (Deleted - no longer required)  G. Validation report: Which we covered last time  H. Parametric studies: See following slides 38

Appendix C: Postings (Example) Nuclear Criticality Safety Limits and Controls NO MORE than 4300 kg Plutonium per 8-liter container. NO MORE than ONE operator may carry ONE 8-liter container at a time to the drum loading area.

App. H: Parametric Studies  Stand alone pre-analysis studies in order to refine the normal case (What is normal?)  Ideal: Perturbations on limiting case  At minimum:  PS#1 = Worst case of concrete  PS#2 = 12” of water is infinite  PS#3 = 6% water for sprinkler is conservative  Follow format of AppendixH.doc in public area 40

Parametric studies  Arise out of modeling questions  Most reactive material makeup  Most reactive reflection  Most reactive placement of fissile (primary)  Most reactive arrangement of other material (including other fissile elements)  Acceptability of modeling simplification (e.g., leaving out walls, ceilings, etc.)  Sometimes order matters—you want to clear up the most “independent” modeling questions first to use in the others 41

Parametric study example  You are analyzing storage of four 10 liter canisters in a 90x90x90 cm glovebox against a wall (Pu-239/water mixture)  Assume the “normal” case still has the following ambiguities:  H/D range of.8 to 1.2  Placement of canisters in glovebox  Type of concrete (among 4 SCALE choices)  Optimum H/X ratio  What parametric studies would you run?  In what order? 42