# Presentation: 721383

***The DMCC Perspective on the Application to Meteorological Software of DOE’s SQA Requirements***

- Walt Schalk / Carl Mazzola / Cliff Glantz
- 5 May 2008

## DMCC INTEREST IN SQA PROBLEM

**  ****2000****:  DNFSB Technical Report 25                     **
**   ****(SQA need for nuclear safety-related software)**
**  ****2002****:  DNFSB letter to DOE Secretary**
**   ****(need to establish sound SQA program PRONTO!)**
**  ****2003****:  DOE established Central Registry **
**   ****(ID’d CA codes that meet DOE O 414.1C and **
**    ****DOE G 414.1-4)**

## DMCC INTEREST IN SQA PROBLEM (cont.)

**  ****DMCC Review of DOE O 414.1C & DOE G 414.1- 4                     **
**   ****Hazards Assessment Software  =  “****Safety**** Software”**
**INCONSISTENCY Found**
**HA modeling often uses quality-assured on-site Met data**
**  ****Errors in Met software can affect CA & HA model output**
** ****	****> Wind Direction – coming from / blowing to**
**   ****	****> Scalar vs. Vector averaging for winds**
**    ****	****> Wind speed accuracy at near-calm conditions**
**    ****	****> Rounded NWS/FAA Wind Direction **

## ESTABLISHING QA REQUIREMENTS FOR METEOROLOGICAL PROGRAMS

**   ****Emphasizes dependence of Atmospheric Transport and Dispersion modeling on-site meteorological data.**
**  ****DOE O 414.1C and DOE G 414.1 – 4**
**        ****- Defines ****SAFETY**** software**
**        ****- Establishes SQA requirements for ****SAFETY**** software**
**        ****- Establishes SQA requirements for **
**	****SAFETY-RELATED**** software**

**ESTABLISHING QA REQUIREMENTS FOR METEOROLOGICAL PROGRAMS**

## BUT........

**It follows that:**
**    ****If ATD models must adhere to SQA requirements.....**
**    ****....Then, it is reasonable for meteorological data software be pedigreed to ensure credibility/defendability. **
**BUT........**

**ESTABLISHING QA REQUIREMENTS FOR METEOROLOGICAL PROGRAMS ****(cont.)**

##  The Implications are HUGE !

**ESTABLISHING QA REQUIREMENTS FOR METEOROLOGICAL PROGRAMS ****(cont.)**

**The BIG QUESTION  for all DOE **
**Meteorology Programs is...**
**Is our Meteorological Software      ****SAFETY***** *****or**** ****SAFETY-RELATED***** *****?**
** ****The Implications are ****HUGE**** ****!**

## What is the COST ?      *** HUGE ***

**   **
**DOE/HS *****could ****** *****decide Met Data Software that generates data for ****SAFETY**** software must also be ****SAFETY**** software.**
**What is the COST ?      ******* HUGE *****
***   ******The Secret***

**ESTABLISHING QA REQUIREMENTS FOR METEOROLOGICAL PROGRAMS ****(cont.)**

##       The Answer

**   **
**  ****How:  *****Voluntarily adopt  *****Standard for SQA, based on**
** ****Met Software ****is**** ****SAFETY-RELATED ****not**** ****SAFETY**** ****Software****.**
***  *****Proactive:  *****We Define  *****Guidance for ****SAFETY-RELATED**** and “Near-Safety” Applications ***** ******BEFORE******  ***** we are TOLD.**
***      ******The Answer***

**ESTABLISHING QA REQUIREMENTS FOR METEOROLOGICAL PROGRAMS ****(cont.)**

## DMCC PROPOSED ACTION TO DEVELOP MET SOFTWARE SQA GUIDANCE 

**DMCC PROPOSED ACTION TO DEVELOP MET SOFTWARE SQA GUIDANCE **

***Goals***

**IMPROVE**** current SQA Practices**
**Met Software will meet a ****“reasonable” ****set of SQA Requirements for ****SAFETY-RELATED**** software.**
**APPLY**** consistent ****Standards**** across DOE (and vendors) for Met Software  development and maintenance.**
**   **

##  Consistent with  ANSI/ANS-3.11  and  DOE/EH-0173T.

**DMCC PROPOSED ACTION TO DEVELOP MET SOFTWARE SQA GUIDANCE ****(cont.)**

** ****Encourage ****Technical Innovation ****and AVOID “stifling” ****SAFETY**** software SQA requirements for Met Applications.**
-  **Consistent with  ****ANSI/ANS-3.11****  and  ****DOE/EH-0173T****.**
**  ****Based on ten element  ****DOE G 414.1 – 4 **** ****framework.**
**    ****- SQA **_***Project Management ***_**and **_***Quality Planning ***_
**       ****Documentation**
**    ****	****- **_***Identify risks ***_**from using or**
**	****  ****modifying software**
**    **

## DMCC PROPOSED ACTION TO DEVELOP MET SOFTWARE SQA GUIDANCE (cont.)

**    ****- Develop a **_***Configuration Management Plan***_
**    ****- SQA Plan for Acquired Software; **_***Problems & Patches***_**.**
**    ****- Document **_***software function, performance, ***_
***       ***_***installation, maintenance and security requirements***_**.**
**    ****	****	****- Document **_***Software Design and ***_***	******	******   ******	****** ******	******   ***_***Implementation ***_**to ensure **
**	****	****   ****continuity.**

**DMCC PROPOSED ACTION TO DEVELOP MET SOFTWARE SQA GUIDANCE ****(cont.)**

## DMCC PROPOSED ACTION TO DEVELOP MET SOFTWARE SQA GUIDANCE (cont.)

**    ****- **_***Identify consequences ***_**of Software failure.**
**    ****- Design, conduct, and document **_***V & V TESTING***_**.**
**    ****- Develop and implement **_***Problem Reporting/Tracking***_**.**
**    ****- **_***Software Design, Development, & Testing Training***_**.**

**DMCC PROPOSED ACTION TO DEVELOP MET SOFTWARE SQA GUIDANCE ****(cont.)**

## DMCC PROPOSED ACTION TO DEVELOP MET SOFTWARE SQA GUIDANCE (cont.)

**    ****- Determine SQA activities needed for ****near-safety**
**      ****software  ( the “right” level of detail )**
**    ****- SQA applied for developing new software and **
**       ****modifying current software.**
**    ****	****	****- Prepare *****User Documentation & ***
***	******    ******	******  ******Instructions***

**DMCC PROPOSED ACTION TO DEVELOP MET SOFTWARE SQA GUIDANCE ****(cont.)**

## DMCC PROPOSED ACTION TO DEVELOP MET SOFTWARE SQA GUIDANCE (cont.)

**    ****- LEGACY Software:  No SQA requirement, but improvements to code and V & V Testing documentation, if practical.**
**    ****- Communicate SQA requirements to Commercial Software Vendors – they can provide documentation.**

**DMCC PROPOSED ACTION TO DEVELOP MET SOFTWARE SQA GUIDANCE ****(cont.)**

## ANSI / ANS-3.11 and DOE/EH-0173T: Outline a proper Meteorology Program to support  ATD modeling.

DOE O 414.1C and DOE G 414.1 – 4: Defines SAFETY software and establishes SQA requirements for SAFETY and SAFETY-RELATED software.

DMCC: Plan future Meteorological Requirements and Promote Meteorological Applications to DOE/NNSA. 

**DOE O 414.1C and DOE G 414.1 – 4: ****Defines ****SAFETY**** software and establishes SQA requirements for ****SAFETY**** and ****SAFETY-RELATED ****software.**
**DMCC: ****Plan future Meteorological Requirements and Promote Meteorological Applications to DOE/NNSA. **

**CONCLUSION**

## DMCC will draft and propose SQA guidance for Meteorological Data Software.

DOE G 414.1 – 4 ten element framework will be used for developing guidance. 

Legacy Software SQA will focus on code and V & V documentation.  Vendors to provide documentation.

Upon acceptance, DMCC will distribute and promote.

**DOE G 414.1 – 4 ten element framework will be used for developing guidance. **
**Legacy Software SQA will focus on code and V & V documentation.  Vendors to provide documentation.**
**Upon acceptance, DMCC will distribute and promote.**

***The DMCC Perspective on the Application to Meteorological Software of DOE’s SQA Requirements***
***ANS - 2******nd****** Joint Emergency Preparedness and Response & Robotics and remote Systems Topical Meeting***

**CONCLUSION**

## Discuss Draft SQA Plan at May 2008 DMCC Annual Meeting 

Get additional input at June 2008 NUMUG Meeting ( Private Sector Input )

Issue SQA Guidelines and post on DMCC website by December 2008  

**Get additional input at June 2008 NUMUG Meeting ( Private Sector Input )**
**Issue SQA Guidelines and post on DMCC website by December 2008  **

**PATH FORWARD**

## ?

**QUESTIONS / COMMENTS**