Menu
Departmental Representative to the Defense Nuclear Facilities Safety Board
Recommendation 2002-1, Quality Assurance for Safety-Related Software
2002-1 BY YEAR:
2010 2009 2008 2007 2006 2005 2004 2003 2002
This page last updated Tuesday, February 26, 2013
Key Documents & Information
- Board Recommendation: from Chairman Conway to Secretary Abraham, dated September 23, 2002.
- Department Response: from Secretary Abraham to Chairman Conway, dated November 21, 2002.
- Department Implementation Plan: dated March 13, 2003.
- Board Closure: dated April 14, 2010.
Chronicle of Related Correspondence
- April 14, 2010, Board letter closing Recommendation 2002-1, Quality Assurance for Safety-Related Software.
- February 5, 2010, Department letter requesting closure of Recommendation 2002-1.
- No document links for 2009
- February 26, 2008, Department letter regarding commitment 4.3.2.1 in the DOE's Implementation Plan for Board Recommendation 2002-1, Quality Assurance for Safety Related Software.
- February 7, 2008, Department letter regarding Commitment 4.2.1.3 of the Department's Implementation Plan for DNFSB Recommendation 2002-1, Quality Assurance for Safety Related Software.
- No document links for 2007
- November 3, 2006, Department letter reporting completion of Commitment 4.3.3 in the 2002-1 implementation plan, Quality Assurance for Safety Software at Department of Energy Defense Nuclear Facilities, which requires the NNSA and Site Offices to review safety Software Quality Assurance directives and determine the actions necessary to implement the requirements.
- July 25, 2006, Department letter forwarding information regarding its review of DOE Orders of Interest to the Board and supplemental directives.
- April 10, 2006, Department letter forwarding the approved Los Alamos Site Office Functions, Responsibilities, and Authorities Manual (FRAM).
- February 14, 2006, Department letter providing status of Commitment 4.3.3 in the 2002-1 implementation plan, Quality Assurance for Safety Software at Department of Energy Defense Nuclear Facilities, which requires NNSA and Site Offices to review safety Software Quality Assurance (SQA) directives and determine the actions necessary to implement the requirements.
- November 21, 2005, Department letter providing status on Commitment 4.3.3 in the 2002-1 implementation plan, Quality Assurance for Safety Software at Department of Energy Defense Nuclear Facilities, which requires the NNSA and Site Offices to review software quality assurance (SQA) directives and determine actions to implement DOE Order 414.1C, Quality Assurance.
- September 28, 2005, Department letter reporting completion of the Office of Environmental Management's portion of Commitment 4.3.3 in the Department's Software Quality Assurance (SQA) implementation plan which requires the issuance of new or revised directives for safety software quality assurance.
- September 9, 2005, Department letter reporting completion of Commitment 4.1.6, with one exception, in the 2002-1 implementation plan, Quality Assurance for Safety Software of Department of Energy Defense Nuclear Facilities, which requires the NNSA to revise its Headquarters and Site Office Functions, Responsibilities and Authorities Manuals (FRAMs) to incorporate Federal responsibilities and authorities for Software Quality Assurance (SQA).
- July 28, 2005, Department letter reporting completion of Commitments 4.2.3.3 and 4.2.4.2 in the 2002-1 implementation plan, Quality Assurance for Safety Software at Department of Energy Defense Nuclear Facilities, which requires NNSA to complete the identification, selection, and assessment of safety system software and firmware at defense nuclear facilities and for NNSA to complete the assessments of the processes in accordance with the schedule established in 4.2.4.2, respectively.
- July 25, 2005, Department letter reporting completion of Commitment 4.1.4 in the 2002-1 implementation plan, Quality Assurance for Safety Software at Department of Energy Defense Nuclear Facilities, which requires NNSA personnel assigned to Software Quality Assurance (SQA) positions to achieve qualifications according to the requirements of the Safety SQA Functional Area Qualification Standard.
- June 29, 2005, Department letter reporting completion of Commitments 4.3.2 and 4.4.1 in the Department's Software Quality Assurance (SQA) implementation plan.
- May 31, 2005, Department letter forwarding NNSA's Roadmap for Nuclear Facility Quality Assurance Excellence, NNSA's planning basis for effective Quality Assurance at NNSA facilities.
- February 28, 2005, Department letter regarding interim status of Commitment 4.3.2.1 in the 2002-1 implementation plan, Quality Assurance for Safety-Related Software, which requires the Department to establish a schedule to develop, revise, approve, and issue software quality assurance directives.
- February 28, 2005, Department letter forwarding NNSA Safety Management Functions, Responsibilities and Authorities Manual (FRAM) Revision 1.
- January 10, 2005, Department letter regarding status of Commitment 4.3.2.1 in implementation plan 2002-1, Quality Assurance for Safety-Related Software, which requires the Department to establish a schedule to develop, revise, approve, and issue software quality assurance directives.
- December 29, 2004, Department letter reporting completion of the Office of Environmental Management's (EM) portion of Commitment 4.2.3.3 in the 2002-1 implementation plan, Quality Assurance for Safety-Related Software at Department of Energy Defense Nuclear Facilities, which requires the assessment of EM's safety software.
- November 29, 2004, Department letter reporting completion of the Office of Environmental Management (EM) portion of Commitment 4.1.4 in the 2002-1 implementation plan, Quality Assurance for Safety-Related Software, which requires at least one qualified Software Quality Assurance (SQA) person in EM non-closure sites.
- November 23, 2004, Department letter providing status of NNSA's portion in Commitment 4.1.4 in the 2002-1 implementation plan, Quality Assurance for Safety-Related Software, which requires NNSA personnel assigned to Software Quality Assurance positions to have qualifications in accordance to the Technical Qualification program.
- October 1, 2004, Department letter providing status on personnel quality and software assessments relative to the Department's 2002-1 implementation plan, Quality Assurance for Safety Software at Department of Energy Defense Nucler Facilities.
- July 13, 2004, Department letter reporting completion of three Environmental Management commitments in the Quality Assurance Improvement Plan and implementation plan 2002-1, Quality Assurance for Safety-Related Software.
- June 29, 2004, Department letter forwarding the updated code-specific guidance reports for the safety analysis toolbox codes relative to Commitment 4.2.1.4 in the 2002-1 implementation plan, Quality Assurance for Safety-Related Software.
- June 4, 2004, Department letter forwarding the National Nuclear Security Administration (NNSA) Site Office Functions, Responsibilities and Authorities Manuals (FRAMs), and plans for updating safety-related Orders, Standards, and supplemental Directives.
- May 12, 2004, Department letter forwarding the final gap analyses report for the MACCS2, ALOHA, EPICODE, MELCOR, GENII, and CFAST toolbox codes relative to Commitment 4.2.1.3 in implementation plan 2002-1, Quality Assurance for Safety-Related Software.
- May 6, 2004, Department letter providing status of commitments on Software Quality Assurance (SQA) and forwarding the revised Office of Environmental Management Headquarters Functions, Responsibilities, and Authorities (FRA) document.
- May 5, 2004, Department letter providing status on commitments from the Office of Environmental Management to the Board that are past due.
- May 3, 2004, Department letter providing a revision to Commitment 4.2.1.3 in implementation plan 2002-1, Quality Assurance for Safety-Related Software, which requires the Department to perform a gap analysis on the six toolbox codes.
- April 5, 2004, Department letter regarding status update on Software Quality Assurance (SQA) deficiencies at Pantex.
- March 25, 2004, Department letter forwarding a report on Safety-Related Design Code Survey relative to Commitment 4.2.1.5 in implementation plan 2002-1, Quality Assurance for Safety-Related Software.
- March 25, 2004, Department letter providing status on updating the NNSA Site Office Functions, Responsibilities and Authorities Manuals (FRAMs).
- March 22, 2004, Department letter providing the address to access the Department's newly-developed Software Quality Assurance Knowledge Portal.
- February 23, 2004, Department briefing to the Board on Software Quality Assurance.
- January 29, 2004, Department letter providing status of Commitments 4.1.3, 4.2.1.5, 4.2.3.2, and 4.2.4.2 in implementation plan 2002-1, Quality Assurance for Safety-Related Software.
- January 29, 2004, Department letter reporting interim status on Commitment 4.2.1.3 in implementation plan 2002-1, Quality Assurance in Safety-Related Software, which requires a gap analysis on toolbox codes.
- December 31, 2003, Department letter reporting completion of Commitments 4.2.2 in implementation plan 2002-3, Requirements for the Design, Implementation, and Maintenance of Administrative Controls and Commitment 4.1.5 in the Department's Software Quality Assurance Implementation Plan with the submission of the DOE Technical Standard on Specific Administrative Controls and the revised DOE Safety Management Functions, Responsibilities and Authorities Manual (FRAM).
- December 24, 2003, Department letter regarding Commitment 4.2.1.5 in implementation plan 2002-1, Quality Assurance for Safety-Related Software, requiring the Department to conduct a survey of design codes currently in use to determine if any should be included as part of the toolbox codes.
- December 22, 2003, Department letter reporting completion of site specific schedules required by Commitments 4.2.3.2 and 4.2.4.2 in implementation plan 2002-1, Quality Assurance for Safety-Related Software, with the submission of site specific schedules to complete the identification, selection, and assessment of safety system software and firmware at defense nuclear facilities; and to complete the assessment of the processes in place to ensure safety software used support the analysis and design of nuclear facilities is adequate.
- December 18, 2003, Department letter reporting completion of Commitment 4.4.3 in implementation plan 2002-1, Quality Assurance for Safety-Related Software, which requires the Department to establish relationships and collaborate with outside organizations that have an interest in Software Quality Assurance.
- December 9, 2003, Department letter reporting completion of Commitment 4.1.3 in implementation plan 2002-1, Quality Assurance for Safety-Related Software, which requires the NNSA to identify Federal positions whose duties and responsibilities is to provide assistance, guidance, direction, oversight, or evaluation of Safety Software Quality Assurance activities.
- December 3, 2003, Department letter reporting status and partial completion of Commitment 4.2.1.3 in implementation plan 2002-1, Quality Assurance for Safety-Related Software, which requires a gap analysis on toolbox codes relative to Software Quality Assurance criteria.
- November 20, 2003, Department letter forwarding the Safety Software Quality Assurance Functional Area Qualification Standard relative to commitment 4.1.2 in implementation plan 2002-1, Quality Assurance for Safety-Related Software.
- November 13, 2003, Department letter informing the Board of the status of four EM commitments in the Department's Implementation plan for Board recommendation 2002-1, Quality Assurance for Safety-Related Software.
- October 31, 2003, Department letter reporting completion of Commitment 4.4.2 in implementation plan 2002-1, Quality Assurance for Safety-Related Software, which requires the identification of methods for capturing and communicating SQA lessons learned.
- October 31, 2003, Department letter regarding Commitment 4.3.2.1 in implementation plan 2002-1, Quality Assurance for Safety-Related Software, requiring the establishment of a schedule to develop, revise, approve, and issue software quality assurance directives.
- October 30, 2003, Department letter to the Board informing them that an additional 45 days to meet Commitment 4.2.3.2 and Commitment 4.2.4.2 of the Recommendation 2002-1, Quality Assurance for Safety-Related Software.
- October 28, 2003, Department letter providing status of Commitments 4.2.3.1 and 4.2.4.1 in implementation plan for 2002-1, Quality Assurance for Safety-Related Software.
- September 30, 2003, Department letter reporting completion of Commitments 4.2.1.2, requiring the establishment of the SQA plan and criteria for the toolbox codes, and 4.2.1.4, requiring the issuance of code-specific guidance reports for the safety analysis toolbox codes, in implementation plan 2002-1, Quality Assurance for Safety-Related Software.
- September 30, 2003, Department letter reporting completion of Commitment 4.3.1 in implementation plan 2002-1, Quality Assurance for Safety-Related Software, which requires a review identifying industry or Federal agency standards appropriate for Department safety software.
- August 29, 2003, Department letter informing the establishment of the Central Registry for DOE Toolbox Codes in completion of commitment 4.2.2 of implementation plan 2002-1, Quality Assurance for Safety-Related Software.
- July 16, 2003, Department letter providing status of two commitments in the 2002-1 implementation plan, Software Quality Assurance.
- May 23, 2003, Department letter regarding Software Quality Assurance deficiencies at Pantex.
- May 8, 2003, Department letter providing status of the Quality Assurance Improvement Plan.
- May 8, 2003, Department letter regarding schedule of planned On-Site Reviews of the National Nuclear Security Administration Field Element Performance in relation to the Department's Quality Assurance Improvement Plan.
- April 28, 2003, Department letter providing status on a requested report on actions being taken to improve Software Quality Assurance for Integrated Electronic Procedures and the Move-Right system.
- April 10, 2003, Board letter accepting implementation plan for 2002-1, Quality Assurance for Safety-Related Software.
- April 4, 2003, Department memorandum regarding investigation of the use of improperly heat-treated aluminum parts supplied by Temperform USA.
- March 28, 2003, Department memorandum regarding designation of initial Safety Analysis Tool Box Codes.
- March 25, 2003, Board letter establishing a 30-day reporting requirement regarding Software Quality Assurance at Pantex.
- March 13, 2003, Department letter forwarding implementation plan 2002-1, Quality Assurance for Safety Related Software.
- December 13, 2002, Federal Register publication of the Department's response to Recommendation 2002-1, Quality Assurance for Safety-Related Software.
- November 22, 2002, Department letter forwarding the Department's Quality Assurance Improvement Plan for the Defense Nuclear Facilities.
- November 21, 2002, Department letter acknowledging receipt of and accepting Board Recommendation 2002-1, Quality Assurance for Safety-Related Software.
- October 9, 2002, Federal Register publication of DNFSB Recommendation 2002-1, Quality Assurance for Safety-Related Software.
- September 30, 2002, Department memorandum regarding Recommendation 2002-1, Quality Assurance for Safety-Related Software.
- September 23, 2002, Board letter forwarding Recommendation 2002-1, Quality Assurance for Safety-Related Software.
Prior to Recommendation
- August 29, 2002, NNSA Report on Selection of Computer Codes.
- February 22, 2002, Board letter enclosing comments on the Draft DOE Quality Assurance Improvement Plan.
- October 2, 2000, Department letter responding to the issues raised in the Board's Technical Report 25, Quality Assurance for Safety-Related Software at the Department of Energy Defense Nuclear Facilities.
- January 20, 2000, Board letter forwarding Technical Report 25, Quality Assurance for Safety-Related Software at Department of Energy Defense Nuclear Facilities. It establishes a 60-day reporting requirement on actions needed to address the deficiencies and potential improvements identified in the report and the schedule for completing these actions.
