New DOE Software Quality Assurance Requirements: Implications for Meteorological Software Cliff Glantz Pacific Northwest National Laboratory

Slides:



Advertisements
Similar presentations
Ways to Improve the Hazard Management Process
Advertisements

EMS Checklist (ISO model)
Course Material Overview of Process Safety Compliance with Standards
Quality Assurance Update Presented byRay Hardwick Presented by: Ray Hardwick.
Department of Energy Quality Assurance Updates Frank Russo Deputy Assistant Secretary Office of Corporate Performance Assessment Energy & Environmental.
The DMCC Perspective on the Application to Meteorological Software of DOE’s SQA Requirements Prepared by: Cliff Glantz (PNNL) Carl Mazzola (Shaw Env.)
Safety Software QA at BNL’s Collider-Accelerator Department (C-AD) Accelerator Safety Workshop E. Lessard Collider-Accelerator Department August 12-14,
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
CENTRAL CONTRACTOR REGISTRATION (CAGE CODES) DFARS Case 2003-D040 DFARS Parts 204, 212, 213 and 252 are amended to remove policy on Central Contractor.
Lindy Hughes Fleet Fire Protection Program Engineer Southern Nuclear Operating Company June 4, 2013 Fire Protection.
What is Program Management?
1 Regulatory Challenges During and Following a Major Safety or Security Event Muhammad Iqbal Pakistan Nuclear Regulatory Authority Presentation at General.
Developing a Chemical Risk Management Program
Mitun PatelMXP07U. Organisational structure Top management; this includes the organisation’s general manager and its executives Department managers; this.
CHDCCS Business Service Center, Information Technology and Financial Planning Employee Safety Training March 29, 2002.
Defense Nuclear Facilities Safety Board
1 MEASURING THE EFFECTIVENESS OF THE NATION’S FOODSERVICE AND RETAIL FOOD PROTECTION SYSTEM.
Protection Against Occupational Exposure
ToR of GEOSAF2 WG on Operational Safety Review of WG2.
OHT 19.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Controlled documents and quality records Definitions and objectives.
Software Quality Assurance Implementation Plan June 15, 2004 Defense Nuclear Facilities Safety Board Chip Lagdon Director Office of Quality Assurance Programs.
Configuration Management Publications at IAEA
Occupational Health Programs
Introduction to Software Quality Assurance (SQA)
U.S. Department of Transportation Pipeline and Hazardous Materials Safety Administration Harold Winnie, CATS Manager (Central Region) Leak detection for.
Safety Analysis Working Group FY2010 EFCOG Semi-Annual Meeting Brad Evans, Chair Pacific Northwest National Laboratory Rob McKeehan, Vice-Chair Oak Ridge.
An Educational Computer Based Training Program CBTCBT.
CPIS 357 Software Quality & Testing I.Rehab Bahaaddin Ashary Faculty of Computing and Information Technology Information Systems Department Fall 2010.
N.C.A. Quality Assurance Review Commendations and Recommendation Status Red Rock Day School January 27, 2011.
Nov Readiness Review Course Implementation Plan - Mod 8 Screening or Scoping Meeting (ORR vs RA, Authorization Authority (AA) Defined, Startup Notification.
Quality Assurance Program National Enrichment Facility Warren Dorman September 19, National Energy and Environmental Conference.
OHT 25.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The quality assurance organizational framework Top management’s quality.
QA Requirements for DOE Accelerator Safety System Software K. Mahoney Group Leader, Safety Systems TJNAF Presented at the 2008 DOE Accelerator Safety Workshop.
1 DOE IMPLEMENTATION WORKSHOP ASSESSING MY EMS Steven R. Woodbury
ISMS QMS Integration Dr. Thomas Helms, Parsons DOE SRS SWPF Project.
Cultivating a Safety Culture within a Creative Environment Frances Alston Manager, Environmental, Safety & Waste Management.
Software Project Management
Breakout Group 2: Software Quality Assurance Objectives and Goals 8/18/10 1.
ASSURANCE PINNACOL ASSURANCE Wants you to know about : EMERGENCY/DISASTER PREPAREDNESS.
Prime Responsibility for Radiation Safety
JLab Software Assurance Program A Risk Based Approach to Software Management.
Scott Butson District Technology Manager. Provide professional to all district staff Professional development has been provided on a regular basis to.
Using ISMS Principles and Functions in Developing an ARRA Readiness Review Process Presented by Linda K. Rogers Assessments & Readiness Programs Manager.
SMS Planning.  Safety management addresses all of the operational activities of the entire organization.  The four (4) components of an SMS are: 1)
College Reviews An Overview Presented by Howard Lutwak, CIA Director of Internal Audit January 2004.
C O N T R A C T O R I N F O R M A T I O N E X C H A N G E LashCIE Presentation 1/98 1 Recent Accomplishments and Future Directions Dan Giessing U.S. Department.
C O N T R A C T O R I N F O R M A T I O N E X C H A N G E Reister CE Presentation 1/98 1 Program Elements and Related Activities Rich Reister U.S. Department.
Over View of CENELC Standards for Signalling Applications
Specific Safety Requirements on Safety Assessment and Safety Cases for Predisposal Management of Radioactive Waste – GSR Part 5.
Bechtel National Inc. 1 Using Human Performance Analysis to Eliminate Errors Presented September 13, 2006 DOE Integrated Safety Management Best Practices.
Software QA Safety Systems at SLAC Enzo Carrone Controls Department – Safety Systems SLAC National Accelerator Laboratory.
Fulfilling Nuclear Emergency Preparedness Data needs with PI. By Paul Sunderland & Kevin Rumbaugh.
IAEA International Atomic Energy Agency IAEA Safety Standards for Research Reactors W. Kennedy Research Reactor Safety Section Division of Nuclear Installation.
Working Group 3 Murmansk. SC structure – Assessment context has to be more elaborate and detailed – Optimization. Provide justification based on the document.
James C. Liu 1 and Lawrence S. Walker 2 1. SLAC National Accelerator Laboratory, CA, USA 2. Brookhaven National Laboratory, NY, USA 1. Introduction ANSI.
Independent Oversight Status Report on Workplace Exposure Monitoring ISM Workshop 2007.
0 Software Quality Assurance Implementation Plan Briefing to the Board June 20, 2003.
Qualification & Training of Work Planners Steven K. Little Work Control Department Manager.
SE513 Software Quality Assurance Lecture10: Documentation and Quality Records Control Galin, SQA from Theory to Education Limited.
1 Quality Assurance Software Quality Assurance Implementation Plans October 16, 2003 Defense Nuclear Facilities Safety Board Beverly Cook Assistant Secretary.
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
INFORMATION DISASTER PREPAREDNESS PLANNING (IDPP).
Instructor: Lloyd Hancock
Occupational Radiation Protection during High Exposure Operations
Software and Systems Integration
Ensuring Nuclear Safety Culture in Ghana: Regulatory Perspective
Flooding Walkdown Guidance
Life at SRS After RADCALC
Cybersecurity Special Public Meeting/Commission Workshop for Natural Gas Utilities September 27, 2018.
Risk Management NDS Forum June 23rd 2010.
Presentation transcript:

New DOE Software Quality Assurance Requirements: Implications for Meteorological Software Cliff Glantz Pacific Northwest National Laboratory Presented at NUMUG 2006 – St. Louis

2 OverviewOverview Background information on the new DOE Software Quality Assurance (SQA) Order and Guide What type of software does this new Order impact? What will be required? What does this mean for DOE- related meteorological programs and vendors of meteorological software?

3 Background Info Defense Nuclear Facility Safety Board (DNFSB) issued “Quality Assurance for Safety Related Software at Department of Energy Defense Nuclear Facilities” in January 2000 Little progress was made in addressing issues raised by the DNFSB

4 Background Info (cont) DNFSB issued Quality Assurance for Safety-Related Software in September 2002 Calls for prompt actions in: Defining SQA responsibility and authority Recommending standards for computer codes used for safety analysis and design

5 Implementation Plan for DNFSB Recommendation DOE accepted the DNFSB Recommendation in November 2002 Issued Implementation Plan in March 2003 Prepared and issued an SQA Order and Guide for Safety Software in the summer of 2005

6 Safety Software is Defined to Include: (1) Safety System Software. Software for a nuclear facility that performs a safety function as part of a structure, system, or component (SSC). (2) Safety and Hazard Analysis Software and Design Software. Software that is used to classify, design, or analyze nuclear facilities. This software helps to ensure the proper accident or hazards analysis of nuclear facilities or an SSC that performs a safety function

7 Safety Software defined (continued) (3) Safety Management and Administrative Controls Software. Software that performs a hazard control function in support of nuclear facility or radiological safety management programs or technical safety requirements or other software that performs a control function necessary to provide adequate protection from nuclear facility or radiological hazards. This software supports eliminating, limiting, or mitigating nuclear hazards to workers, the public, or the environment…

8 Application of the SQA Order SQA requirements apply to consequence assessment models used for: hazards assessment/safety planning purpose. emergency response purposes and provide a direct hazard control function. These are models used to make protection action recommendations (PARs), such as HOTSPOT, EPI, ALOHA,…

9 Application (cont) SQA requirements appear to apply to meteorological software that is used to : provide data/information used in a safety or hazard analysis provide data used in emergency preparedness and response, fire protection, waste management, or radiological protection.

10 Applications (cont) Applicable meteorological software is used to: measure, process, store, and communicate data at meteorological monitoring locations process, store, and communicate meteorological data at central weather stations or data repositories process, store, and display meteorological data at Emergency Operation Centers.

11 SQA Requirements in a Nutshell Five types of software are mentioned in the Order: 1.Custom developed 2.Configurable 3.Acquired (includes commercial off-the-shelf meteorological software) 4.Utility calculations 5.Commercial design and analysis tools. ABC For each type of software, three different levels (A, B, or C) can be assigned based on how the software is being used. Ten work activities are required. Depending on the assigned SQA level, a full or graded approach to the work activity is required.

12 Work ActivitiesCustom A B C COTS A B C 1. Software Project Management and Quality PlanningFULL FULL FULL GRADE GRADEGRADE 2. Software Risk ManagementFULL GRADE GRADE FULL 3. Software Configuration MgmtFULL FULL FULL GRADE GRADEFULL FULL FULL GRADE GRADE 4. Procurement & Vendor MgmtFULL FULL FULL FULL 5. Software Requirements Identification and ManagementFULL FULL FULL FULL 6. Software Design & ImplementationFULL FULL FULL NA NA NA 7. Software Safety DesignFULL FULL FULL GRADE GRADEFULL FULL FULL GRADE GRADE 8. Verification & ValidationFULL GRADE GRADE FULL 9. Problem Reporting & Corrective ActionFULL FULL FULL FULL GRADE GRADE 10. Training of PersonnelFULL FULL FULL GRADE GRADEFULL FULL FULL GRADE GRADE

13 DOE/EH SQA Webpage

14 What Does this Mean for Vendors? DOE customers may be coming back to you for additional information on your SQA practices and documentation DOE customers will be asking more of you in the SQA arena when they acquire new software A vendor’s existing SQA program may be sufficient to meet DOE needs. Vendors should review the DOE SQA Order and Guide to prepare for questions their DOE customers may have.

15 ConclusionsConclusions DOE Sites will need to make sure that their meteorological software complies with the DOE SQA Order and Guide. Software vendors will be asked to provide documentation to ensure that their software design, development, testing, and maintenance program is in compliance with the SQA Order and Guide.