OCRWM Test and Evaluation Master Plan (TEMP) · 2014. 12. 8. · DOE/RW-0478 OCRWM Test and...

оашттп

Office of Civilian Radioactive Waste Management

OCRWM Test and Evaluation Master Plan

(TEMP)Revision 0

(A 0 O 0 0 0 0 0 Q -0 0 8 1 1 -4 6 0 0 -0 0 0 0 9 )

r,crElVE D A4S" ,W 5SEM t S B _ __ _ ̂

V I Л!Вм —* *M- «•«- J » -« - Ш Л---------- . Q <2 I I ümCf Or UVm r nOWCInf vtW ММЦВМт

ТЬЫмп OCRWM Fropam-Levfi CONTROLLED DOCUMENT. ТЪе holder ideatlfledMlbe Иве p«ge It гмрошМе tor kaqpiagtfckdKD- nett cvfM t by tacorportttefilNbteqvatf гетЫоовмЛеуяге dhlrlwled eié fcr bsftag d ii d o * * ! reed8y Sfileblii * ijsel I» HdtMdrKtHtCoBtt'oMlcopjfMBbcnfff м1|м41о1мН?Мм1|» TtelaantaatfvqpwrffeifarMtotMatlLW talbBlBnHba* Imvcs the рмШов» htfahi Ы to nttm it ¿э fte PBCCB BnMlvt в в М н Ы к п А м м Ы М и гя м м о!»

Ш^<ЛО,Сои1гд1ЫРосии»1й1,у<1Янш|101м1ММс§оП1>е

ГОИЦуМЬЦШСШгОИИРКИЮЮуЦГу^бИМаИВНнУ)

DOE/RW-0478

OCRWM Test and Evaluation Master Plan

W (TEMP)Revision 0

(A00000000-00811-4600-00009)


August 1995

CAS. Department o f Energy Office Ы O vitltn KtdkMtctfve Wâste Mtntgement

WuNngton, DC 20585

DISTRIBUTION OF THIS DOCUMENT IS UNLIMITED

U U Prinud with toy Ink on m qreM pap*

MASTER


QA: n /a|1 Of: ll

BCP^9S-0014 Ilt. KrNV. 11b.- I“

D I S P O S ! Í ЮГ. S I J M M A R V

Initial of the OCRWM TEMPProgram - Level 1

BOARD MEMBER RECOM M ENDATION'S)

Dooald Hoitoo, RW-3 Approve

I m Bmee, RW-10 Approve with cooditiacu (RESOLVED]

RotuM Milner, RW-30 Approve

Samuel Roaao, RW-40 Approve with caaditkas [RESOLVED]Wesley Barnes, YMSCO Approve with conditions (RESOLVED]

6. •CHAHWMOW» JUCmCA-nON/CONOmomfUMITATIONS f

N/A

□ 8m Continuation Paeo____

1. RW-30 ahall update the Syatem Engineeriiif Management Plan to be consistent with tbe Teat and Evaluation Maater Plan(TEMP).

2. RW-40 ahall develop teat and evaluation plans in accordance with die TEMP.

3. YMSCO dull develop test and evaluation plans in accordance with the TEMP.

П 8 м Continuation 9шал7. ОКСПУЕЛМ РиМ ВГГМ в MSIKUCnONS FOR M PACTB) CONFKIURATION ITEMM

N/A

□ 8 м Continuation Ржу

0244 (Rav. 07/18/94)

DI: AOOOOOOOO-00811-4600-00009 REV 00 WBS: 92.1

QA: N/A

Civilian Radioactive Waste Management System Management & Operating Contractor

OCRWM TEST AND EVALUATION MASTER PLAN

Revision 00

August 1995

Prepared for

U.S. Department of Energy Office of Civilian Radioactive Waste Muiagement

1000 Independence Avenue, S.W. Washington, DC 20585

Prepared by:

TRW Environmental Safety Systems Inc. 2650 Park Tower Drive

Suite 800 Vienna, Virginia 22180

Under Contract Number DE-AC01-91RW00134

с

THIS PAGE INTENTIONALLY LEFT BLANK

с TABLE O F CONTENTS

Pace

1. INTRODUCTION ....................................................................................................... 1

1.1 DOCUMENT PURPOSE ..................................................................................... 11.2 SCOPE................................................................................................................. 11.3 REVISIONS TO THE TEST AND EVALUATION MASTER PLAN (TEMP) . . . 11.4 CONTENTS......................................................................................................... 2

2. DESCRIPTION ........................................................................................................... 3

2.1 MISSION DESCRIPTION ................................................................................... 32.2 SYSTEM DESCRIPTION..................................................................................... 3

2.2.1 Key Technical Characteristics ..................................................................... 32.2.2 Key Operational Characteristics................................................................... 32.2.3 Key Regulatory Characteristics ................................................................... 42.2.4 Interfaces ................................................................................................... 4

3. PROGRAM SUMMARY............................................................................................. 5

ЗД POLICY............................................................................................................... 53.2 TEST AND EVALUATION (T&E) OBJECTIVES............................................... 5

3.2.1 Support System Design and Development ................................................... 63.2.2 Verify Compliance with Requirements......................................................... 63.2.3 Support Assessment of Operational Effectiveness......................................... 83.2.4 Support Regulatory Compliance Activities................................................... 8

3.3 APPROACH......................................................................................................... 83.4 MANAGEMENT AND RESPONSIBILITIES........................................................ 13

3.4.1 Office of Program Management and Integration........................................... 133.4.2 Project Offices............................................................................................. 153.4.3 Interface Organizations ............................................................................... 153.4.4 Documentation ........................................................................................... 16

3.5 TEST AND EVALUATION (T&E) INTEGRATION ........................................... 17

3.5.1 Program ..................................................................................................... 173.5.2 Waste Acceptance, Storage, and Transportation (WAST) Project................ 173.5.3 Yucca Mountain Site Characterization Project (YMP) ................................. 20

iii

TABLE OF CONTENTS (C ontinued)

Fate

3.6 INTEGRATED SCHEDULE................................................................................. 233.7 QUALITY ASSURANCE PROGRAM................................................................. 23

4. DEVELOPMENT TEST & EVALUATION (DT&E)................................................... 25

4.1 TECHNICAL CHARACTERISTICS..................................................................... 254.2 DT&E TO DATE................................................................................................. 254.3 FUTURE DT&E .................................................................................................... 25

4.3.1 Transportation System Element................................................................... 294.3.2 MPC............................................................................................................ 294.3.3 Waste Acceptance System Element............................................................. 304.3.4 Waste Package ........................................................................................... 304.3.5 Repositoiy................................................................................................... 31

5. OPERATIONAL TEST & EVALUATION (OT&E)..................................................... 33

5.1 OPERATIONAL CHARACTERISTICS ............................................................... 33 ^5.2 OT&E TO DATE................................................................................................. 33 >5.3 FUTURE OT&E.................................................................................................... 35

5.3.1 Transportation System Element................................................................... 375.3.2 MPC............................................................................................................ 375.3.3 Waste Acceptance System Element............................................................. 395.3.4 Waste Package ............................................................................................ 395.3.5 Repository.................................................................................................... 40

6. REGULATORY COMPLIANCE TEST AND EVALUATION..................................... 43

6.1 REGULATORY CHARACTERISTICS................................................................. 436.2 REGULATORY COMPLIANCE T&E TO DATE................................................. 456.3 FUTURE REGULATORY COMPLIANCE T&E ................................................. 45

6.3.1 Transportation System Element................................................................... 456.3.2 MPC............................................................................................................ 456.3.3 Repository/Waste Package........................................................................... 47

7. T&E RESOURCE SUMMARY .................................................................................... 49

8. REFERENCES............................................................................................................... 51

iv

TABLE O F CONTENTS (C ontinued)

APPENDIX A - ACRONYMS

APPENDDC В - GLOSSARY

L IST O F FIGURES

Page

3-2. System Test Pyramid................................................................................................. 12

3-3. Program-Level Test and Evaluation Process............................................................... 18

3-4. WAST Test Activities............................................................................................... 19

3-5. YMP Test Activities ................................................................................................. 21

3-6. TEMP Integrated Schedule .............................................................. ..................... 24

4-1. TEMP Integrated Schedule: DT&E ......................................................................... 26

5-1. TEMP Integrated Schedule: OT&E ......................................................................... 34

6-1. TEMP Integrated Schedule: Regulatory Compliance T&E ....................................... 46

3-1. T est and Evaluation Process................................................................................................... 10

vi

r

LIST OF TABLES

Page

3-1. Example Requirements Traceability/Conformance Verification Matrix (RT/CVM) . . . 7

4-1. DT&E Phase............................................................................................................ 27

5-1. OT&E Phase............................................................................................................ 35

6-1. Regulatory Compliance Phase .................................................................................. 44

1. INTRODUCTION

1.1 DOCUMENT PURPOSE

The Office of Civilian Radioactive Waste Management (OCRWM) Test and Evaluation Master Plan (TEMP) describes the program Test and Evaluation (T&E) policy, objectives, requirements, geneial methodology (test flow and description of each T&E phase), responsibilities, and scheduling of test phases for the Civilian Radioacli ve Waste Management System (CRWMS). This TEMP is a program-level management planning document for all CRWMS T&E activities and will be used in conjunction with Section 11 of the Quality Assurance Requirements and Description (QARD) (Reference 1), as appropriate, as a guide for the projects in developing their T&E plans. In the OCRWM document hierarchy, that is described in the OCRWM Systems Engineering Management Plan (SEMP) (Reference 2), the TEMP is subordinate to the program SEMP. To ensure CRWMS operates as a.” integrated system, the plans for verifying die performance and evaluating the operational suiti and effectiveness of the overall system are also described.

Test and evaluation is an integral part of the systems engineering process. Key aspects of the systems engineering process, more fully described in the OCRWM SEMP, are discussed in this TEMP to illustrate how T&E supports die overall systems engineering process.

U SCOPE

The process described in this TEMP applies to engineering and scientific activities associated with the design, development, and operation of the CRWMS over the life cycle of the program. These activities include the testing not only of manufactured items, but also of natural objects or systems. Activities related to items on the Q-List will comply with requirements specified in the QARD. From a program perspective, the TEMP describes how T&E activities will address integration between projects and, from a project perspective, furnishes guidance on T&E activities including the development of T&E planning documents. This first version of the TEMP focuses on how T&E supports the integration between major items of the Yucca Mountain Site Characterization Project (YMP) and the Waste Acceptance, Storage and Transportation (WAST) Project, including the rationale for the various test phases and categories. Test and evaluation plans for each project, which specify actions to be taken in implementing test and evaluation at the project level, will be prepared by project managers. HLW and testing required to verify that the vitrified HLW meets performance specification for disposal in the repositoiy will be covered in future versions. For software that will be used in support of work subject to QARD requirements, verification and validation procedures will be conducted in accordance with applicable sections of tbe QARD.

О REVISIONS TO THE TEST AND EVALUATION MASTER PLAN (TEMP)

The TEMP has been developed as a guidance document that establishes the content and conduct of the OCRWM T&E program. It assigns primary responsibility for execution of the T&E program to the projects and establishes Program responsibilities related to T&E activities. This TEMP reflects current program activities consistent with the CRWM Program Plan (Reference 3).

1

Tbe TEMP will be revised as required, to incorporate future changes in the concept of operations; requirements, including interface requirement changes; architectural changes such as inclusion of an interim storage facility, and organization. As the program matures, the TEMP will be updated in step with program needs. The TEMP and updates to the TEMP will be approved by the Program Baseline Change Control Board (PBCCB).

1.4 CONTENTS

The TEMP contains the following sections:

Section 1 provides an introduction that states the purpose, scope, revisions, and contents of the document

Section 2 provides a description of the test and evaluation program, including the CRWMS mission description; system description: key technical, operational, and regulatory characteristics; and interfaces.

Section 3 provides a program summary that establishes the policy, objectives, approach, management and responsibilities of the OCRWM Program Office, integrated activities, schedule of major program milestones, and quality assurance program.

Section 4 describes the Development Test and Evaluation (DT&E) phase of the T&E process. It provides the critical technical characteristics, rationale for DT&E tests, and planned OCRWM DT&E activities.

Section 5 describes the Operational Test and Evaluation (OT&E) phase of the T&E process It provides die critical operational issues, rationale for OT&E tests, and planned OCRWM OT&E activities.

Section 6 describes the Regulatory Compliance Test and Evaluation phase of the T&E process. It provides the regulatory characteristics, rationale for regulatory compliance tests, and planned OCRWM regulatory compliance T&E activities.

Section 7 identifies die T&E resource categories that will be considered for project- and program- level tests.

Section 8 provides a list of reference documents.

Appendix A provides a list of acronyms.

Appendix В provides a glossary.

2

2. DESCRIPTION

Z1 MISSION DESCRIPTION

The Nuclear Waste Policy Act o f 1982 (NWPA), as amended (Reference 4), assigned to die Department of Energy (DOE) the responsibility for managing die disposal of spent nuclear fuel (SNF) and high-level radiou~tive waste (HLW) of domestic origin, and established the Office of Civilian Radioactive Waste Management (OCRWM) for that purpose. The mission of the OCRWM program is to provide for permanent isolation of SNF and HLW in a geologic repository in a timely manner that protects the health and safety of the public and of workers, and maintains the quality of the environment

2.2 SYSTEM DESCRIPTION

The Civilian Radioactive Waste Management System (CRWMS) is comprised of four system elements: Waste Acceptance, Transportation, Storage, and Mined Geologic Disposal System (MGDS).

The Waste Acceptance, Storage, and Transportation (W AST) Project is responsible for die accept, transport, and stoic waste functions included in the Waste Acceptance, Transportation, and Storage System Elements. The WAS! Project is managed by the Office of Waste Acceptance, Storage, and Transportation (OWAST), headed by the Office Director.

The Yucca Mcav.ain Site Characterization Project (YMP) is responsible for determining the suitability of the Yucca Mountain site through appropriate designs for test, scientific studies, tests and evaluations. If the site is determined suitable, the YMP develops the MGDS system element of the CRWMS. The YMP is managed by the Yucca Mountain Site Characterization Office (YMSCO), headed by the Project Manager.

2.2.1 Key Technical Characteristics

The key technical characteristics will be used to assess how well equipment or items will perform. Key characteristics include radiological limits for personnel protection, limits for concentrations of radioactive material in water and air, criticality protection, capacity, and thermal characteristics as allocated to specific CRWMS items. Development test and evaluation (described in Section 4) will be conducted against these characteristics to demonstrate compliance with requirements and to support evaluation of key operational characteristics.

Ш Key Operational Characteristics

The key operational characteristics are those aspects of the system against which the system will be evaluated. In general, they reflect performance parameters, consistent with operational requirements, that will indicate how well the system meets mission requirements. The operational characteristics originate in the system Measures of Effectiveness (МОЕ). Operational MOEs are used to assess the ability of the system to perform the mission tinder regulatory <\nd environmental

3

constraints. Typical MOEs and key operational characteristics include performance; operational availability (which is affected by system reliability); operations and maintenance concepts; system throughput; and system efficiency. The operational test and evaluation process (described in Section 5) will be conducted against these characteristics to ultimately evaluate CRWMS operational effectiveness. Further discussion of the application of MOEs to the CRWMS may be found in System Evaluation Criteria (Reference S).

2 2 3 Key Regulatory Characteristics

The key regulatory characteristics are program requirements that apply to activities associated with supporting the development and operation of the CRWMS. These requirements, which are contained in various regulatory documents, are divided into four areas of regulatory requirements: site suitability, licensing, environmental compliance, and safety and health compliance. The approach to complying with these regulatory characteristics is outlined in the Regulatory Guidance Document (ROD) (Reference 6). Regulatory compliance test and evaluation (described in Section 6) will be conducted to demonstrate regulatory compliance against these requirements.

2.2.4 Interfaces

Interface requirements include both external and internal interfaces. External interfaces, e.g., to contractors, utilities, or local governments, are addressed within the system element and design requirements documents. Internal interfaces are those between elements of the CRWMS or between segments of an element The System Requirements Document (SRD) for each element describes program level requirements for interfaces between it and other elements and between internal segments of that element Interfaces between elements are further described in Program Interface Control Documents (ICDs) under development The current element interfaces are Waste Acceptance (WA)-Transpoitation (Trans), Storage-Trans, Mined Geologic Disposal System (MGDS)-Trans, MGDS-Storage, WA-Storage, and WA-MGDS. At the project level the Design Requirements Documents (DRDs) identify CI-CI interfaces for Configuration Items (CIs). The CI- CI interfaces identified in a DRD are not limited to the CIs of a given DRD or segment but can identify interfeces with CIs in another element

The program Interface Control Working Group (ICWG) will facilitate the development of ICDs that will be used to help identify tests to verify interface requirements. Testing of interfaces will be conducted by the projects consistent with design agreements documented in the ICDs. Responsibilities for testing interfaces are presented in Section 3.4.

4

С

3. PROGRAM SUMMARY

3.1 POLICY

The implementation of this TEMP is based on the following T&E p jlicies:

• Planning

- Both the Yucca Mountain Site Characterization Project (YMP) and the Waste Acceptance, Storage, and Transportation (WAST) Project will use the Program TEMP as a guide to develop, review, and approve project test plans.

- The DOE has approval authority for all test plans and procedures developed by contractors.

• Implementation

- All testing will be executed by die projects, either under their own authority or as a designated agent of the Program.

- The DOE will identify test activities that will be witnessed by the DOE or its designated representative.

- Projects aie responsible for testing their own interfaces to existing systems. When a project interfaces to another system that is not available the project will test the interface as much as is practical. The projects, in coordination with the program office, will determine which project has responsibility for the final system integration test

• Evaluation

- Test reports will clearly identify test purpose, objectives, results, conclusions, and the need for any retest

- To ensure an integrated program, both projects will adhere to the technical reviews and audits as described in the Program Systems Engineering Management Plan (SEMP) (see Reference 2) and Baseline Management Plan (BMP) (Reference 7).

• Test planning, implementation, and evaluation work processes pertaining to Q-List items willcomply with Section 11 of the QARD (see Reference 1).

3.2 TEST AND EVALUATION (T&E) OBJECTIVES

Test and evaluation is an integral part of the systems engineering process that is used to attainOCRWM objectives. Therefore, T&E objectives have been derived to support the systems

f *\ engineering process. Four general objectives of the T&E program are: (l)co support system designand development, (2) to verify compliance with requirements, (3) to estimate the operational

5

suitability and effectiveness of the system, and (4) to support regulatory requirements. Although the relative emphasis on each of these objectives will change during different program phases, all four are important to program success. Specific objectives applicable to die CRWMS are categorized and discussed below.

311 Support System Design and Development

The T&E program supports the design and development effort by providing data required to manage program risk, monitor technical performance, and resolve technical issues (e.g., support tradeoff studies). Developmental data from development testing and Technical Performance Measurement (TPM) are key sources of the data needed to perform these functions as described in the SEMP. By estimating performance parameters, TPM will be used to identify technical risk areas, assess their potential impact to system performance, and determine an approach to reducing risk. Specifically, trend analysis of these parameters will be used to forecast performance parameters, measure differences between the parameters achieved and those allocated to an item, and determine the impact of die differences on system performance. TPM will be used to mitigate or resolve issues, as part of die risk management process, through tests or support to tradeoff studies. In the early stages of the CRWMS program, development testing to support TPM will be used to minimize program risk by assessing alternative design concepts and continually monitoring technical progress. Development testing, described in Section 4 as part of TPM, will be performed by the projects.

ЪЛЛ Verily Compliance with Requirements

Requirements conformance verification is a principal systems engineering function ensuring that the system is designed and built as specified in the requirements documents. The need to verify compliance with requirements and design is identified in the Program SEMP, and defined in the Glossary of die QARD. It can be viewed as the overall process that ensures configuration items meet their design requirements. Section 3.2.4 of die QARD identifies design review, alternate calculations, and qualification testing as design verification methods. Section 3.2.7 further describes qualification testing requirements. To ensure conformance with requirements contained in the System Requirements Documents (SRDs) (References 8-11), conformance verification matrices (CVM) are included in Section 4 of the SRDs. The CVMs include the requirements and type of verification method (i.e., test, examination, analysis and/or demonstration) and are intended as a guide for the projects to develop their own CVM as part of die DRDs. As verification activities are completed they will be documented in the project CVM and program Requirements Traceability/Conformance Verification Matrix (RT/CVM), shown in Table 3-1, which is essentially an extension of the conformance verification matrices presented in Section 4 of the SRDs. When information from the RT/CVM is incorporated into the Automated Requirements Management System (ARMS), die ability to monitor program performance will become more efficient A description of how compliance with requirements will be verified is described in Section 3.3. The focus of the verification effort is on verification of technical requirements. The process for identification and verification of programmatic requirements is under development

8 1 fII 2s S £

ШII II II < 03 U

■8sÜ

!iï

e•B• s l lc >% oIllsiS < S н

•-Î (4 <n ^

Ш Support Assessment of Operational Effectiveness

The assessment of operational effectiveness is a means to monitor the effectiveness of the CRWMS. Specifically, this assessment will determine whether the as-built system adequately performs the CRWMS operational mission, not just meets technical requirements. The TPM combined with measures of effectiveness will quantitatively provide a means to assess how well the CRWMS is performing. MOEs important in complying with the CRWMS enabling legislation are identified in the reference, System Evaluation Criteria (see Reference S). Those MOEs are intended to be used in system-level CRWMS studies. As an example, several MOEs were evaluated to determine whether the incorp station of die Multi-Purpose Canister (MPC) into the CRWMS technical baseline was feasible. The MOEs that were evaluated include cost, schedule, health and safety impacts, stakeholder acceptance, and programmatic risk. The evaluation of diese MOEs is presented in a series of system studies that support the decision to use the MPC and is incorporated as part of the MPC Conceptual Design Report, Volume V (Reference 15). MOEs will need to be tailored to support the assessment of operational effectiveness as part of the T&E process. Operational effectiveness is presented as a test category in Section 5.

3.2.4 Support Regulatory Compliance Activities

Regulatory compliance activities include those related to licensing, certification, and environmental impact The licensing process involves tests necessary to obtain approval from die Nuclear Regulatory Commission (NRC) for demonstrating compliance of storage and repository facility designs with requirements described in 10 CFR 72 (Reference 16) and 10 CFR 60 (Reference 17) respectively. For example, surveys and monitoring will be required to comply with radiation dose limits as described in 10 CFR 20. The certification process requires tests to demonstrate compliance of cask designs with requirements described in 10 CFR 71 (Reference 18) for transportation and 10 CFR 72 for storage. To comply with the provisions of the National Environmental Policy Act (NEPA) (Reference 19), test data may be required to support de velopment of environmental impact statements. Regulatory Compliance T&E is described in Section 6.

3.3 APPROACH

The approach used by OCRWM to conduct T&E is based on achieving the T&E objectives described above. For items on the Q-List Section 11.0 of the QARD applies. Several tenets used to develop this approach include:

• Tailor the process described in this program TEMP to identify test requirements as early as possible

• Integrate the test approach across the program

• Build a system test process that supports a logical hierarchy of design.

A summary of the approach that is now being implemented by both the projects and die program office is depicted in figure 3-1. As part of the planning stage, the CRWMS mission and major program plan objectives and milestones were used as a basis to develop this TEMP.

Baseline test requirements identified in the TEMP were extracted from the CRWMS Requirements Document (CRD) (Reference 20). These requirements have been allocated to elements described in the four System Requirements Documents (SRDs) and further allocated to project configuration items described in documentation such as design requirements documents and the YMP Site Design and Test Requirements Document (Reference 21). The latter defines project test requirements. Supporting documentation used to obtain test requirements includes the conceptual system description and system concept of operations documents, the SEMP, and other appropriate sources. The system concept of operations is particularly important since it will be used during test planning to ensure identification and prioritization of operational test sequences.

.As part of program test requirements analysis, requirements were placed into test phases and test categories. The phases and categories were sequenced to provide a logical series of tests to systematically evaluate portions of the CRWMS and ultimately the entire CRWMS. The phases include: Development Test and Evaluation (DT&E), Operational Test and Evaluation (OT&E), and Regulatory Compliance Test and Evaluation. DT&E conducted by the projects supports the design and development effort OT&E, which is also conducted by (he projects, as agents of die program office, supports the assessment of the system in an operational environment The Regulatory compliance phase will occur in parallel with the DT&E and OT&E phases, and T&E will be conducted by the projects to support licensing, compliance of designs, and environmental impact statements. Program-level test categories allocated to the projects include DT&E tests conducted at the system element level and system level, and OT&E tests. The projects will map diese test categories/requirements against their Configuration Item (Cl) hierarchy. Program level test requirements analysis is continually being conducted to ensure that a complete set of documented test requirements is available. For example, concept of operations documents, which are being developed, will be used to derive operational requirements that will subsequently be used to support die program-level test design effort The program-level test design effort will ensure that tests provide information consistent with planned system operations.

The next series of steps, as shown in Figure 3-1, will continue to be conducted as a joint program/project development effort since any test design, resources, and test procedures proposed by the program would be used by the project Further, this integrated effort will ensure efficient use of resources, prevent any overlap in tests, and facilitate the development of the project Test and Evaluation Plan (TEP) which will include plans for program level tests.

As part of this integrated development, analysis of test requirements at the project level will be conducted in which each requirement will be assigned a particular method of verification using the CVM in Section 4 of the SRDs as a guide. The requirements verification process will consist of a combination of examination, analysis, demonstration, and test activities to prove that requirements have been met that requirements are reflected in the design, and that system elements are qualified for the program mission. To achieve requirements verification at the lowest program cost the mix of verification methods will require careful planning and analysis using a concurrent

Figur

e 3-1

. Te

st and

Ev

aluati

on

Proc

ess

1 0

engineering approach. Each requirement froro the SRDs down through the DRDs will be examined with respect to the Cl to be tested to determine whether analysis, examination, demonstration, or tests, or a combination thereof, is most appropriate. In this context and throughout this document (except where indicated otherwise), 'test" encompasses the four types of verification methods indicated in Table 3-1 and is used to mean test, analysis, examination, or demonstration designed to obtain, verify, or provide data for the evaluation of progress in accomplishing development objectives, or performance and operational capability of systems, subsystems, components, and equipment As verification activities are completed, they will be documented in the project CVM and program Requirements Traceability/Confoimance Verification Matrix (RT/CVM), shown in Table 3-1. The program RT/CVM will be used to monitor program performance and to assist in audits and reviews by allowing users to check the status of verification activities (e.g., completion of verification event). A RT/CVM for each system element will be included as an appendix to this TEMP.

An integration sequence using the C l architecture will be developed based on the concept of successive integration and test steps as shown in Figure 3-2. At the base o f the system test pyramid, the appropriate level CIs (i.e., subsystem element since requirements have not yet been allocated to element and component CIs) will be tested and then integrated into subsystem CIs, which will be tested as entities, integrated at the next higher level, which will be tested as an entity, etc. The purpose of this process is to progressively assemble and integrate lower level CIs into upper level CIs up to and including the CRWMS system. Each step will start with a collection of tested items (i.e., to ensure compliance with requirements and interfaces operate properly) from the preceding lower level, which will then be integrated and tested to ensure that die assembly functions as a system. This process will continue until the CRWMS is tested as a system. A key decision will be the determination of CIs in areas where projects have not defined CIs, since the test results o f lower CIs in the test pyramid support higher level CIs. Tests are not shown in Figure 3-2 for Component and Element CIs a t the base of the pyramid since no requirements have been allocated to these CIs.

The integrated project TEP developed by each project will translate the integration sequence applied to project CIs into specific test objectives, schedules, organization responsibilities, and resources. The development of the plan is shown occurring prior to development of die test design because the initial version of the plan may not contain a complete list of resources. As the test design becomes more refined the resource requirements will be updated. Moreover, depending on the scope and complexity of a particular project and project test objectives, there may be a multivolume test plan that includes an overall integrated T&E plan supplemented by several test plans. Test plans « ill be developed in accordance with Section 11 of the QARD. Test plans and reports are managed in accordance with Sections 6 and 17 of the QARD.

The refinement of test design will identify resources for performing tests and develop the basis for generating procedures. Tbe test design, which will be organized into test cases, will serve as a foundation for the more detailed test plans and will specify test objectives and rationale for the test test prerequisites, tes.* configuration, and test method. In the process of developing test design, resource requirements will be identified in the areas of test articles; test facilities; test support equipment; special purpose hardware and software; personnel and training; test data reduction; and

11

Figur

e 3-2

. Sy

stem

Test

Pyra

mid

unique requirements. These test resources will be documented in both the integrated project test plan and the prog.’am TEMP. Test procedures will contain objectives, test configuration and set up instructions, evaluation criteria, test instructions and expected results, and data management A set o f test instructions will be prepared to establish the (¿tailed procedures for administration, control, and performance of tests. These procedures will be documented in detailed test plans.

Prior to performing the test a test readiness review will be conducted to ensure procedures and resources are ready to support die test The review will be tailored to match the scope and complexity of the test The implementation stage of the T&E process will consist of performing the test in accordance with the test procedures. The evaluation stage will involve an assessment of test results compared to test objectives. The evaluation will build upon analysis that will identify implications of the test and may apply data from other sources to generalize the results or extrapolate to other conditions. Problems may occur during the test that are related to implementation of specifications, procedures, or personnel errors, etc. Resolution of these problems, which may require a peer or other type o f review, range from modifications to die test purpose to changes to requirements. Results and evaluation of the test will be documented in a test report and will be used to support a specific project or program objective. For those test activities related to Q-List items, the test report will be documented in accordance with Section 17 of the QARD.

3.4 MANAGEMENT AND RESPONSIBILITIES

The overall management of the CRWMS Program is the responsibility of the Director, OCRWM. The CRWMS Program Office includes: (1) the Office of Quality Assurance; (2) the Yucca Mountain Site Characterization Office; (3) the Office of Waste Acceptance, Storage and Transportation; (4) the Office of Program Management and Integration; and (S) the Office of Human Resources and Administration.

Program-level T&E functions are within the responsibility of the Director of the Office of Program Management and Integration (OPMI). OPMI is responsible for integration at the program level. This Office is supported by the Systems Engineering Division that is responsible for developing the TEMP. Project-level T&E falls within the two CRWMS Projects.

3.4.1 Office of Program Management and Integration

The OPMI test and evaluation responsibilities flow down from the OCRWM mission and function statements. OPMI has responsibility to support both the Director, OCRWM and the projects to fulfill the OCRWM mission. Support to the Director, OCRWM ensures an integrated CRWMS by using the systems engineering process across the program. Support to the projects serves to expedite acquisition and also ensures an integrated system (e.g., compatible interfaces) at the program level. Specific OPMI T&E responsibilities to support the Director, OCRWM and the projects are as follows:

• Planning

- Develops the Program TEMP that establishes integrated policy, program-level requirements, and responsibilities for managing the T&E program and ensuring compliance with requirements

- Participates in an integrated test planning working group to ensure efficient use of program and project resources

- Specifies program-level and interface requirements for projects to test and identifies a program-level integration test sequence

- Provides requirements interpretation to projects in support of verification methods

- Participates in reviews of die project Test and Evaluation Plans (TEPs), acceptance plans, and other T&E documentation; and in test readiness reviews

- Assigns appropriate projects) as agent(s) for execution of program-level testing.

• Implementation

- Participates in appropriate testing as an independent observer of tests

- Participates in the Interface Control Working Group (ICWG) to facilitate the documentation, approval, and control of interface design information for interfaces identified in the SRDs.

• Evaluation

- Ensures test data from program-level tests are used to monitor program performance, resolve technical issues identified in tradeoff studies or risk plans, and support program regulatory compliance activities

- Verifies program-level requirements and documents the verification report or event in the RT/CVM (including consistency checks with project level traceability and conformance verification matrices') to support audits and reviews

- Participates in reviews conducted by the projects to include formal qualification reviews

- Reviews and evaluates project and/or contractor test reports

- Provides guidance on audits conducted by the projects to include functional configuration audits (FCAs) and physical configuration audits (PCAs).

Personnel participating in die auuits will use the program RT/CVMs to support the acceptance ofitems from contractors.

1 TracMbffity »ad cooformtace verification m m îm m «cd u the project level te еаюге prejett level reqoirtmmti не ц*се»Ые to deaif and are verified by specific reports, analyses, aad/or contract deliverables.

The Project Offices are responsible for developing, coordinating, and implementing T&E activitiesfor subsystems they are acquiring. Specific T&E responsibilities are as follows:

• Planning

- Develops the Project TEP that includes objectives, requirements (including program-level), test flow and description of each T&E category, responsibilities (including those of contractors), scheduling of tests, and resource requirements

- Establishes and implements concurrent engineering project level teams and participates ' i program-level test planning to ensure integration

- Conducts reviews of project test plans, acceptance plans, and other T&E documentation to ensure, among other objectives, that the test for each requirement is clearly defined

- Conducts test readiness reviews

- Ensures each test supports test plans that are part of an integrated test sequence identified in the project TEP.

• Implementation

- Conducts and monitors tests

- Executes program level tests consistent with Program assignments.

• Evaluation

- Evaluates test results with respect to objectives

- Develops test reports

- Reviews and evaluates contractor test reports

- Verifies requirements and documents the verification report or event in the project level CVM to support audits and reviews

- Conducts reviews to include formal qualification reviews

- Conducts audits to include functional configuration audits (FCAs) and physical configuration audits (PC As).

3.43 Interface Organizations

Several other organizations are an integral part of the T&E process. These organizations containfunctional areas in quality assurance, regulatory integration, and performance modeling. The

3.4Л Project Offices

15

quality assurance organization is responsible for ensuring that T&E activities pertaining to Q-List items meet requirements in accordance with the QARD. Further, as part of the quality assurance program they will conduct audits and surveillances o f T&E activities. Personnel within the regulatory integration area have the primary responsibility for determining specific requirements o f regulations that must be addressed during the design, construction, and operation of the CRWMS. Regulatory organizational responsibilities are outlined in the Regulatory Guidance Document (see Reference 6). Personnel within the area of performance assessment and modeling develop a series of models and provide assessments on an iterative basis to support analysis and reporting. In the process, they identify data needs and requirements for additional testing.

In addition to the responsibilities described above there are other forums that identify responsibilities. For example, the Interface Control Working Group (ICWG) will identify responsibilities for ICWG members to identify and document interface design activities impacting on their organizations. The interface design agreements, documented in Interface Control Documents (ICDs), will be used to formulate integration tests.

3.4.4 Documentation

The OCRWM TEMP is the top-level test and evaluation planning document Each project manager will be responsible for developing a project TEP. Project TEPs will be prepared in accordance with this program TEMP, and tailored to match the scope and complexity of a particular project For example, projects may elect to develop an overall master plan, as a supplement to the Project TEP, depicting aU T&E activities. Thus, die Project TEP may have multiple major sections or be comprised of multiple documents. As a minimum, the project TEP will identify die following:

• A list of key project technical and operational characteristics and their correlation to the Technical Performance Measurement (TPM) program

• The methodology to be used for implementing test and evaluation within the project consistent with program guidance

• The organizational structure and responsibilities for implementing T&E including those of contractors

• An integrated T&E schedule depicting major project milestones and T&E activities in support o f those milestones

• An outline of each of the major T&E phases including identification of the C l being rsted, test objective, and scope of the test

• A summary of the T&E resources required for execution of the T&E program

• Documentation to be developed and maintained, including traceability and conformance verification matrices.

16

3.5 TEST AND EVALUATION (T&E) INTEGRATION

The OCRWM has established an integrated T&E approach from two perspectives. First, the approach is integrated between the projects, facilitated by the Program Office at headquarters. Second, both projects have developed an integrated T&E approach within their respective projects to achieve their objectives.

Ш Program

The program’s contribution to the integrated T&E process will occur primarily by providing support to the projects. As shown in Figure 3-3, the program-level T&E process begins with the development of program level requirements and designs that include functional, performance, and interface requirements as documented in the CRD and SRDs. Interface design or constraints between system element CIs will be documented in ICDs. The program office through Configuration Management is also responsible for assisting the projects to establish CIs. The Cl hierarchy is important since test requirements mapped to CIs will form the basis for the system test pyramid or architecture. A test sequence that includes an operational integration test to assess the readiness of people, procedures, and systems prior to CRWMS operation is presented in this TEMP. Tests allocated to the projects include DT&E tests conducted at the system element and system level, and OT&E tests. The program will monitor project tests, review and evaluate test results, and use those results to support CRWMS T&E objectives such as monitoring program performance by using program level conformance verification matrices.

Ш Waste Acceptance, Storage, and Transportation (WAST) Project

WAST test and evaluation activities support the acceptance of waste, the availability of MPCs, the capability to accept and transport waste from reactors to a potential interim storage facility, and the capability to transport to and dispose of waste at a repository. Specific activities include verification of waste acceptance procedures; verification of transportation procedures, including those related to planning, service and maintenance, and field operations; testing of transportation casks; and testing of MPCs. The project T&E approach, which can be tailored to specific WAST CIs, is shown in Figure 3-4. Since the majority o f near term test activities are concerned with the MPC the T&E approach is briefly described in die following paragraphs for die MPC.

The project has adopted a systematic approach for verifying requirements and design for CIs that constitute the MPC system. The approach consists of developing plans; conducting tests, audits, and reviews; and documenting results. As shown in Figure 3-4, requirements have been identified, and allocated from the CRD through die SRDs to CIs described in the DRDs. The DRDs contain the Design Procurement Specifications (DPSs) that are included as requirements in the MPC System procurement The MPC contractor’s final design report, which «dll be accepted based on criteria established in the M PC System Acceptance Plan (Reference 22), will contain conformance verification matrices. Information (e.g., reference to test results) from the MPC contractor’s conformance verification matrices will be used to update the project’s CVM as an appendix to the project TEP. Subsequently the program office will update the RT/CVM as an appendix to the Program TEMP. These conformance verification matrices will include requirements against tes t analysis, examination, and demonstration conformance methods.

IT

Figur

e 3-3

. Pr

oera

m-L

evd

Test

and

Evalu

ation

Pr

oce

r

18

Figur

e M

. W

AST

Test

Activ

ities

Dcsig

nffiu

ild

The MPC contractor will develop a series o f complementary test plans that reflect the verification methods for a particular C l as determined by the project These tests, performed on prototypes, will include an integration test to ensote that CIs of the MPC system are compatible. The project will conduct Test Readiness Reviews (TRR) prior to tests, and review and evaluate test results contained in vendor test reports. If test objectives are not met other actions such as changes to the test purpose, procedures, or test requirements may occur. The test reports documenting specific test, analysis, examination, or demonstration results will be used to update the project CVM and program RT/CVM to support the Functional Configuration Audit (FCA) and Formai Qualification Review (FQR). The FCA and FQR are depicted as a combined activity, to avoid duplication of activities.

Acceptance criteria will be documented in the individual C l acceptance plans and will be used as a basis to accept CIs from the MPC contractor. Tests to support acceptance will be conducted on the first production unit of each Cl and test results will be used to support the Physical Configuration Audit (PCA) that will be used to establish the MPC product baseline. Actions required by contractors for items not meeting the acceptance criteria will be identified on the item acceptance form provided in die MPC System Acceptance Plan, which may include conducting another test After acceptance, OT&E phase tests will focus on die integration of the MPC with other CRWMS CIs and operational procedures. To assess the effectiveness o f the MPCs, an operational effectiveness test program to monitor and evaluate MPC performance will be established beginning at the time of MPC deployment

To demonstrate that the design meets regulatory requirements, the contractor will perform regulatory compliance testing, engineering tests, and data evaluation in order to provide test results to the NRC as required to obtain Certificates of Compliance under 10 CFR 71 for transportation and under 10 CFR 72 for storage.

3.53 Yucca Mountain Site Characterization Project (YMP)

The YMP test and evaluation activities support the three main project objectives identified below:

• Determine suitability of the Yucca Mountain site and if found suitable, develop a site recommendation report

• Develop the License Application (LA) for MGDS

• Develop the Environmental Impact Statement (EIS) for MGDS.

Since the designs for Surface-Based Testing Facilities (SBTF), Exploratory Studies Facility (ESF), repository and waste package are integrated with and support these objectives, the approach taken by the project will be to provide integration among tests to support the three major project objectives. As shown in Figure 3-5, the test requirements begin with the identification of requirements at the program level that will be allocated to the project level in Design Requirements Documents (DRDs). The documents to support site suitability include the Surface-Based Testing Facilities Requirements Document Exploratory Studies Facility Design Requirements Document

20

and tbe Site Design and Test Requirements Document The documents to support repository/waste package design and regulatory requirements include the Repository Design Requirements Document and Engineered Barrier Design Requirements Document Design reports will contain traceability matrices and Conformance Verification Matrices (CVM) that form the b aas for conformance verification. In parallel with this effort the project will work with the program office to establish CIs for items whosi performance parameters and physical characteristics are presently undefined. As the CIs become defined and baselined they will be linked with tests to form die basis for die test plan. Thus it is important to design the MGDS test pyramid when establishing CIs. For example, to confirm rock characteristics as part of the repository/waste package design, rock impacted by a thermal disturbance may be considered as a geologic Cl. For consistency among test activities, die Yucca M ountain Site Characterization Project T&E Plan, Rev. 1 (Reference 23) provides guidance on how specific tests are defined, designed, and conducted. A major challenge for the project will be to identify relationships among all tests and then determine schedules and priorities for all tests in order to accomplish test objectives.

The near term focus of tests and concomitant resources is to provide a basis to evaluate the suitability or unsuitability o f the mountain based on require ments contained in Subpaits С and D of 10 CFR 960 (Reference 24). As part o f site characterization, the tests can be viewed as qualification tests d u t are part of the design verification of the geologic setting segment of the repository. Surface-based tests and tests in the Exploratory Studies Facilities are underway that will provide data to determine support to relevant disqualifying or qualifying conditions. Test reports (technical basis reports) developed by the project will contain an understanding of alternative models or interpretations permitted by die data, and bounds on conditions and processes. This information will be used to help the Director make a technical site suitability recommendation with respect to Subpaits С and D of 10 CFR 960. If die site is found suitable, site characterization activities will focus support on license application activities including thermal testing to characterize the effects to natural and engineered systems from heated conditions.

The tests conducted for the repository and waste package will be primarily concerned with conformance verification of repository and waste packagit requirements and design, including advanced conceptual design. Reference to test reports will be included in the project Conformance Verification Matrices (CVMs) and program RT/CVM to support reviews and audits that will ultimately lead to government acceptance of the repository/waste package. An acceptance plan will provide the basis for further testing, reviews, and inspection (e.g., Title Ш) leading to the acceptance decision. After acceptance the OT&E phase will consist of tests to assess the integration of people, procedures, and other CRWMS CIs prior to repository operations. Test results that support site suitability will also be used to support the repository/waste package design. For example, there is a complementary overlap in test plans developed for site suitability and repository/waste package design, both of whose test objectives include assessing thermal and hydrologie characteristics of the host rock. These complementary tests provide data for design, verify the suitability of the design, and support the total system performance assessment Facility test requirements, as part of die test program, will become part o f the Exploratory Studies Facility (ESF) or Surface-Based Testing Facilities (SBTF) and, therefore, wQl be integrated into the repository design.

The project is also responsible for developing an EIS consistent with die National Environmental Policy Act (NEPA). Specific data needs (e.g„ collection of existing data or new test data) for the EIS will be defined during the EIS scoping process. To ensure efficiency of test resources die development of the EIS will draw on test results of site suitability, ongoing site characterization, and license application studies.

Test results and analyses in the farm of Prelicensing Evaluation Reports support die license application. The project will use most of the results that supported site suitability to support the LA. The criteria that address DOE site suitability conditions (10 CFR Part 960) are consistent with those used by the NRC in licensing (10 CFR Part 60), although additional information is required to support some aspects of design that do not affect considerations of site suitability. Evaluations for LA will reflect more extensive data and more mature analyses gained in the period between site suitability evaluation and preparation of the LA. The data supporting the central technica' argument and conclusions in the LA will need to be qualified per the QARD Supplement 3, if not collected under an approved QA program and if not corroborated by collection and analysis of additional data under an approved QA program. The results of in situ thermal tests will provide a basis for evaluating a wider range o f thermal loading. Since testing will need to be continued beyond initial license application, test plans to address thermal loading will be included in the initial LA. Test results and analysis will be incorporated into specific chapters of the Mined Geologic D isposal System License Application Annotated Outline (Reference 25). As shown in Figure 3-5, there may be a need to add or revise tests. These revised or new tests are shown emanating from Chapter 8, Performance Confirmation Program, since tests will support the monitoring of repository operations until closure of die repository.

3.6 INTEGRATED SCHEDULE

Figure 3-6 depicts major CRWMS milestones and an overview of CRWMS test phases and categories. YMP and WAST milestones are presented across the top of the figure and major CIs and their test phases and categories to support these milestones are listed below the milestones. To ensure the CRWMS functions as an integrated system, five major T&E integration thrusts are presented. They include: (1) integration tests to support MPC deployment at reactor sites; (2) integration o f the disposal container and MPC based on the availability o f a protor r - disposal container, (3) integration of the repository/waste package using portions o f the reposiu. ■ t , (4) final integration o f the four CRWMS system elements to support waste acceptance at the reposi^.y; and (5) a shakedown test A description of the phases and categories for each of the CIs is presented in Sections 4, 5, and 6.

3.7 QUALITY ASSURANCE PROGRAM

The T&E process described in this plan supports those QA T&E activities identified in the Quality Assurance Requirements and Description document (QARD). Test activities subject to the QARD will be conducted in accordance with applicable implementing procedures. The preparation of test plans, performance of tests, and preparation of test reports will be performed in accordance with Sections 3 ,6 ,11 , and 17 of the QARD. Verification and acceptance activities discussed in Section3.2 will be performed in accordance with Sections 3.2 and 7.2 of the QARD respectively. The relationship of other system engineering activities to the QARD, such as interface management configuration management and readiness reviews are discussed in the program SEMP and BMP.

Figure 3-6. TEMP Integrated Scbeduie

24

4. DEVELOPMENT TEST & EVALUATION (DT&E)

DT&E will be conducted to assist in the CRWMS engineering design and development process and to verify that technical performance specifications have been m et It will involve the use of simulations, models, and in-situ tests as well as full scale engineering development models or prototypes of system components. It will include T&E of components and subsystems and design qualification and production testing. DT&E will be conducted by the projects. DT&E of program level interest includes tests related to requirements at die system element and system level as described in SRDs and CRD, particularly those requirements assessed during integration tests across system elements. Although DT&E and OT&E phases may overlap, DT&E will be generally concluded when item(s) are accepted from contractors by the government

4.1 TECHNICAL CHARACTERISTICS

Technical characteristics provide quantitative measures against which system performance will be evaluated during DT&E. These characteristics are documented as requirements in a series of requirements documents (e.g., CRD, SRDs, and DRDs). DT&E will be conducted to ensure these requirements will be m et

Within DT&E there are several categories of T&E that are intended to be progressively applied to requirements. The test categories are shown in Table 4-1 along with corresponding program- level technical requirements contained in the CRD, and a rationale for each test category. These test categories are sequenced to provide the basis for T&E planning of individual projects. The projects will tailor the development design qualification, system logistics and support, integration, and acceptance tests in Table 4-1 to their CIs, and based on mission objectives, co st and other project factors, will develop their DT&E test sequence. Not all the DT&E phases will be required for every Cl, and individual phases may be combined at the discretion of the project Further, the procurement of some Commercial Off the Shelf (COTS) items and Non Developmental Items (NDI) will require limited DT&E.

DT&E tests of program interest include design qualification tests at the system element level, particularly those related to capability, functional performance, and reliability requirements; and integration tests. Test objectives for DT&E integration tests between system elements will be based on interface design agreements established in interface control documents.

4.2 DT&E TO DATE

In updates to the TEMP, DT&E already conducted will be summarized and presented in this section to establish a reference point for future DT&E. Reference will be made to published test reports as appropriate. More detailed DT&E information will be provided in the project TEPs. If deficiencies are found the need for retest will be identified.

4.3 FUTURE DT&E

Figure 4-1 presents the integrated test schedule with DT&E categories shaded. The categories within the DT&E phase were developed by tailoring Table 4-1 to major OCRWM CIs to support

25

Figure 4-1. TEMP Integrated Scbedule: DT&E

N0T6 • echa** to МапМ to be UNd lot piMnfeig pwpoMt, not tar mwaging or eoniraang TiE MMttM.

ТаЫ

е 4-

1.

DT&

E Ph

ase

27

Table

4-1.

DT

&E

Phase

(Co

ntin

ued)

28

OCRWM milestones. For example, tbe sequence and duration of MPC Subsystem DT&E tests will occur prior to OT&E tests to support MPC deployment The test durations for all tests are depicted as occupying a wide time range to allow flexibility in planning until specific test objectives become m ore defined. Further, the tests aie intended to be representative and the actual tests may vary depending on the scope and complexity of project test objectives. The CIs and their test categories are described below.

4.3.1 Transportation System Element

Since die MPC subsystem procurement contains CIs from die Transportation System Elem ent the Transportation System Element presented here excludes MPC items, which will be discussed in Section 4.3.2. Test objectives include a near term focus to obtain legal weight truck (LWT) casks to support utilities that cannot accommodate rail casks or prefer truck casks. The longer term focus includes sustaining support for MPC deployment and preparing for repository operations. Test categories and rationale for tests to be performed on transportation CIs are outlined below:

• Development testing will be conducted to provide a basis for die use of bumup credit and its impact on criticality control. Testing activities will be coordinated so that data will address not only transportation, but also disposal needs.

• Performance tests w ill be part of the design certification process for die GA-4/9 transportation casks. Test activities will include an assessment of performance characteristics, and operations and maintenance manuals. The tractor and trailer designed to transport the cask will undergo performance testing to assess characteristics of the legal weight truck system.

• System logistics and support and integration test activities will occur over several years, initially to support MPC deployment and longer term to ensure the transportation system is fully operational prior to repository operations. These activities could be viewed as a "pre- operational" phase. System logistics tests will include assessing planning, tracking, traffic management field operations, maintenance concept documentation and manuals, and training. In particular, an assessment of training in procedures will be conducted in the following areas: cask handling, M PC handling, quality assurance, incidental cask maintenance, cask or MPC loading, and cask testing. To ensure a compatible interface between a cask and Purchaser’s SNF storage facility, an assessment will be made of all special handling devices, as well as testing, maintenance, and inspection equipment as identified in the Campaign K it

4 3 2 MPC

1 ’ . MPC subsystem, which is comprised o f configuration items from the Transportation System Element and the Storage System Element is being obtained through a competitive procurement T he procurement approach contains an initial phase and two optional phases. If both optional phases are exercised, full scale prototypes and production fabrication of MPCs will be obtained. T est objectives contained in the procurement support the goal of deploying MPCs in 1998. An outline of representative tests and rationale for the tests to be performed on MPC CIs is presented below:

29

• Candidate TPM performance measures to be selected by tbe project as part of development testing include those related to MPC basket material neutron absorption capability. Specific technical parameters for the test will be defined by die project

• Design qualification, system logistics, and integration tests will be performed to assess system functions and performance. Information on the design will be integrated into die preliminary design of the waste package. Design qualification tests will assess specifications, and installation and removal of removable components. Test would include measurements of SNF locations in MPC baskets, and installation and removal o f lids, plugs, etc. Integration tests will be conducted based on the "MFC test pyramid" with integration occurring from subsystems up through subelements.

• Acceptance tests will be conducted based on an acceptance plan that will, among other objectives, identify tests to demonstrate that the MPC subsystem meets its design requirements. Test results will support conformance verification and acceptance of the MPC system.

• Design qualification and acceptance tests will also be performed on production MPCs. The scope of diese tests will be determined by the project

4.3.3 Waste Acceptance System Element

The Waste Acceptance System Element is comprised of hardware, software, facilities, and equipment necessary to manage the acceptance of waste and account for die inventory of die waste. Near term test activities support deployment of MPCs while longer term activities focus on additional procedures necessary for waste acceptance at die repository as shown below:

• Design qualification tests will be conducted to assess the verification system, which will consist o f hardware, software, data, and procedures, to be used for verifying the material control and accounting (MC&A) data system, SNF records, and site characteristics. Verification of SNF characteristics will be a continuing effort

• System logistics and support and integration tests will be conducted to evaluate MC&A activities prior to MPC deployment The adequacy of training for personnel to conduct MC&A and verification audits in accordance with procedures will be assessed. Safeguards and security standards established by Waste Acceptance, including physical protection standards o f nuclear material, will be assessed based on NRC documents and International Atomic Energy Agency (IAEA) requirements. Analysis of logistics and integration with the MPC system is necessary to ensure all documentation and personnel are in place to support MPC deployment

4.3.4 Waste Package

The MGDS System Element contains the Site Segment Engineered Barrier Segment and the Repository Segment The Waste Package C l is contained within the Engineered Barrier Segment and the disposal container CIs are contained within the Waste Package Cl. For purposes of this

document, reference to th *. disposal container will mean MPC disposal container since T&E of disposal containers for uncanistercd fuel and High Level Waste (HLW) is not included in this document To ensure die design of the disposal container is integrated with the MPC design, relevant information (e.g., materials selection) from the waste package Conceptual Design Report (CDR) will be used to support the MPC Safety Analysis Report (SAR) design. The tests associated with die disposal container will further ensure that this integrated design continues. An example of potential tests for the disposal container is presented below:

• Development testing on materials for the disposal container will continue. Tests will consist of characterization of waste forms, and engineered materials testing to support the waste package design concept and to refine waste package/Engineered Barrier Segment predictive performance models. Degradation and corrosion tests will be performed on containment barrier material including basket materials. As previously identified in Section 4.3.2 the basket material testing will be part of the TPM program. Tests may also include long term spent fuel oxidation tests. However, the timeframe necessary to perform long term degradation tests may not allow for completion o f these tests prior to prototype development

• Design qualification, system logistics, and integration tests will be performed on the disposal container prototype to assess system functions and performance including an assessment of structural integrity to withstand retrieval. The assessment is based on a performance allocation of such requirements as radiation and heat transfer to die disposal package. Also, materials testing relating to die compatibility with MFC materials will be performed. Retrieval of the disposal container prototype is discussed in Section 5.3.4.

• Acceptance tests will be conducted based on an acceptance plan that will, among other objectives, identify tests to demonstrate that the waste package meets its design requirements. Test results will support conformance verification, and acceptance of the waste package.

• Design qualification and acceptance tests will also be performed on production disposal containers. The scope of these tests needs to be determined.

4.3.5 Repository

The Site Segment and Repository Segment are both discussed here since the Site Segment will cease to exist when the Repository Segment is initiated, and portions of the Site Segment will eventually become part of the repository. The near term focus o f test activities on the Site Segment will be to support the evaluation of technical suitability of the mountain by 1998. These tests will also support die repository/waste package design. The following outline summarizes test activities:

• The site characterization activities to support the suitability or unsuitability of the mountain based on DOE’s siting guidelines in 10 CFR 960 can be viewed as many design qualification tests to determine the natural settings (e.g., geologic cha '^eristics, and ground water travel time) of the mountain. Tests will include both surface —sed tests and testing in the underground exploratory facility. The tests will support the К "ing guideline compliance assessments/higher-level findings:

31

- Surface Processes- Pieclosure Radiological Safety- Seismic/Tectonic/Volcanism- Reasonably Available Technology- Geochemistry/Rock Characteristics- Geohydrology/Transport- Total System Performance Assessment

The test results will be used to support the technical site suitability evaluation. Site characterization tests, which include those related to site suitability, are outlined in the Site Characterization Plan (Reference 26).

• If the site is found suitable, design qualification tests may be required to address the remaining guidelines in 10 CFR 960 concerning environmental quality, socioeconomic impacts, and transportation.

• As part of the TPM program (development testing), thermal testing will continue to characterize die thermal response o f the mountain under various thermal loads to support the license application. Specific technical measurement parameters will be defined by the project See Section 6.3.3 for tests in support of licensing.

The draft MGDS СП architecture for the Site Segment includes the ESF and SBTF. Although not initially part o f the repository, the system logistics and support and integration tests associated with this segment are included here since they will need to be conducted prior to integration with the repository. An outline of the tests is presented below:

• As part of the potential repositoiy, construction of the ESF Cl will continue (e.g., the North Ramp and access drifts to the Ghost Dance fault and drifts for heater test #2, etc.).

• Prior to underground portions of the ESF becoming part of the repository, design qualification, logistics, and integration tests will be performed to ensure die ESF meets the requirements of the repositoiy design. Similarly, these tests will also be performed on the SBTF design requirements.

• The Test Program, as part of the site segment ensures site facilities and support services for all field activities supporting site characterization will be provided.

• Design qualification through integration testing o f the CIs within (he repository segment will support the overall integration testing of the MGDS System Element Design qualification tests will include an assessment of the waste handling area of the surface facility, and an assessment of the shaft conveyances, ventilation, and seals (e.g., to ensure materials and placement methods reduce preferential pathways for groundwater to contact die waste packages) of the subsurface. Also, the performance of the shaft seals, as well as the backfill will be assessed. Integration tests will be based on the "MGDS test pyramid" and will include integration of the repositoiy with the Engineered Barrier Segment (e.g., to assess waste emplacement locations, ventilation, utilities, logistics, and other safety services); integration between surface and subsurface facilities; and integration among the waste package, backfill, and seals CIs.

32

5. OPERATIONAL TEST & EVALUATION (OT&E)

Operational test and evaluation will be conducted from a différent perspective than DT&E since it will be performed under as realistic operating conditions as possible. It will determine the effectiveness and suitability of the CRWMS for use in accepting, transporting, storing, and disposing of SNF and HLW. An independent organization usually performs OT&E. However, for the CRWMS, program-level OT&E will be conducted by the projects. Prior to deployment into an operational environment the equipment, facilities, people and procedures for each system element, and ultimately the entire CRWMS, will be assessed by the program office with project test support This step will ensure that the system elements are compatible and interact collectively to meet CRWMS requirements. The majority o f OT&E will be completed upon fielding of the system, but die assessment of operational effectiveness, as part of OT&E, will continue well beyond repository operations.

5.1 OPERATIONAL CHARACTERISTICS

Operational characteristics provide both quantitative and qualitative measures that will be used to evaluate die operational suitability and effectiveness of the system. These characteristics are contained in requirements and operational concept documents. They are the requirements against which the CRWMS will ultimately be evaluated through OT&E.

OT&E will be conducted within categories, each sequenced to results from previous categories. The test categories are shown in Table 5-1 along with corresponding program-level technical requirements contained in the CRD, and a summary of the rationale for each test category. In particular, the operational and maintenance requirements for die CRWMS are critica.' requirements for OT&E since OT&E requires operational realism. These test categories will provide a basis for T&E planning by individual projects. The projects, in conjunction with the program office, will tailor the tests in Table 5-1 for operational suitability, operational integration, and operational effectiveness to their CIs, and based on mission objectives, cost and other project factors, will develop their OT&E test sequence. Not all the OT&E phases will be required for every Cl, and individual phases may be combined at the discretion of the project

OT&E integration tests will include verification of physical and functional interfaces in addition to verification of operational interfaces. OT&E integration tests will build upon test results obtained during DT&E integration tests and will be concluded when all interfaces to the Cl being tested have been verified. The projects may elect to include some OT&E test objectives in the DT&E phase to gain early insight into how portions of the system will perform in simulated operating environments.

5J OT&E TO DATE

There has been no OT&E conducted to date for the CRWMS. As OT&E results become available they will be summarized in this section to establish a reference point for future OT&E. Reference will be made to published test reports as appropriate. More detailed OT&E information will be provided in the project TEPs.

F lg o re M . TEMP Integrated Schedule: OT&E

NOT! • SehedMe m n w * e W wed I » p w rtn g pwpeeee. n « lor m eegtog er cam ralng T IE « м ь * .

53 FUTURE OT&E

Figure 5-1 presents the integrated test schedule with OT&E categories shaded. The OT&E phase and categories within that phase were developed by tailoring the tests in Table 5-1 to major OCRWM C b to meet OCRWM operational milestones. Due to tbe many operational procedures (e.g., SNF verification, MC&A data collection and processing, and MFC loading and handling) that will be required to make die CRWMS an effective operational system, several stages of operational integration are planned to progressively integrate die operational procedures to function as a complete system. As shown in Figure 5-1 there are five thrusts to this integration that include integration tests to support the deployment of MPCs at reactor sites; integration of the disposal container and MPC based on the availability of a prototype disposal container; integration of the repository/waste package using portions of the repositoiy; final integration of die four CRWMS system elements to support waste acceptance at tbe repository; and an operational shakedown test ТЪе operational shakedown test will be conducted during the first delivery of SNF from a reactor site to tbe repository. This test will assess the degree to which die CRWMS meets operational requirements when radioactive materials are used and when the system is operated and maintained by CRWMS personnel. Additional test sites may also be used if the program office determines that additional tests are required. Test data from die final operational integration test will be used to determine appropriate test scenarios and the need for additional tests.

ТаЫе 5-1. OT&E Phase

Test Category CRDSection

Rationale

Operational Suitability

Human Factors 3.2.4.2,3.2.4.4,3.3.7

Determine the degree to which interaction of personnel with the system is accommodated

H Operational 1 Requirements

5.2* Support validation or refinement of operational requirements

О System Safety 3.3.6 Determine that the system meets system safety requirements (See MO^STD-882C for guidelines)

I Reliability, Availability, 1 Maintainability (RAM)

3.2.5 Verify if RAM requirements, including accessibility, are achieved under operating conditions

I Degraded Operations 3.2.1.1 G, H, 3.2.1.2, 3.2.1.33.2.6.1 3.3.6.10 С

Verification of shutdown, degraded operations, ar.d startup procedures

ТаЫе 5-1. OT&E Phase (Continued)

I Test Category CRDSection

Rationale

Site Adaptation11 TBD Ensure site unique data have been developed (e.g„ for OSTS)

Security 3.2.4.3 Ensure effectiveness of allowing only authorized use

O perational Integration

Procedures 5.2e Refine operational procedures (e.g., operation and maintenance)

Logistics 3.5 Determine how maintenance philosophy, spares, test equipment, and training support maintenance of system

Documentation 3.4 Review documents to ensure accuracy and completeness

Certification Test 3.3.4 Ensure compliance with applicable standards and procedures (Excluding NRC certification)

Operational Shakedown 5.2 С 3.7^"

First assessment o f the degree to which system meets requirements in an operational environment

O perational Effectiveness 5.2е Determine the degree to which CRWMS performs continually as intended

* United detail » Section 5.2; Opemiooa) concept Аким ц aid operational requirements Med to be obtained.

k Plea » for generic design to be aite adapted by mfflúes.

* Seeooce«.

* Syatetn-wide reqoietneatt bcktdusg Centra] Management and Operations Coecrd Center (CMOCC) and Information Management System (IMS).

* See note a.

The sequence of these five thrusts is based on planned milestones and will be updated as test results become available. Test phases encompass a wide time span to allow flexibility in planning and will become more specific as test objectives aie defined. The CIs and their test categories aie depicted in Figuie 5-1 and described on the following pages.


These near term tests for the transportation system will focus on preparation for waste acceptance at the reactor sites and longer term tests will focus on transportation activities prior to waste acceptance at die repository. A summary of the potential tests is presented below:

• An operational suitability test for prototype GA-4/9 casks will include human factors and system safety evaluations of tbe cask, Tlie LWT system to transport the cask will undergo testing to assess human factors and support refinement of operational requirements.

• An operational suitability test will be performed on the transportation system as a first assessment of operational requirements. The output of this test will be used to refine these requirements.

• An operational integration test will be conducted by WA, in coordination with the transportation system, to ensure waste acceptance and transportation procedures are in place to support loading of MPCs. Site specific operating procedures that will also be assessed include cask handling, MPC handling, incidental maintenance, vehicle safety inspections, and radioactive contaminated tool/equipment replacement These procedures will be developed in conjunction with and approved by the Purchaser. Procedures also assessed include those supporting W A requirements including Material Control and Accounting (MC&A), verification, physical protection, and how WA keeps the transportation system apprised of changes to delivery commitment schedules and coordination required for approving site specific servicing plans. Feedback on procedures will be included in Campaign Completion Reports (CCRs).

• An operational integration test will be performed on the transportation system, waste package, and repositoiy to ensure they operate as a system. Although the primary focus o f die test is on the repository/waste package interface, the transportation system is included to refine operational procedures for the MGDS and Transportation System Element interface.

• A final operational integration test with all four system elements to assess the integration of people, procedures, and equipment will be conducted. The focus of the test for the transportation system will be to assess the procedures and logistics of the transportation system. For example, procedures and logistics for truck and rail carrier services, intermodal transfer, maintenance services, and the operations control center will be assessed.

• After the license to operate the repositoiy is received an operational shakedown test will be conducted as part of the initial deliveries of waste from reactor sites to the repository. The test will be performed primarily to assess procedures addressing the handling of radioactive waste such as radiological inspections.

53.2 MPC

The initial focus o f tests conducted on the MPC will ensure the MPC is ready for operation at reactor sites. As the disposal container prototype is developed, the focus o f tests will shift to the

integration o f the MFC and disposal container. The final integration test will be conducted to support waste acceptance at the repository. An outline of the tests is presented below:

• Operational suitability and operational integration tests will be performed among storage system items (Le., MPC, transportation, and waste acceptance items) primarily to ensure procedures are integrated prior to waste acceptance at reactor sites. The tests will be based on site specific operating procedures for the cask and MPC operations that will be developed in conjonction with and approved by the Purchaser.

• Prior to integration with the disposal container, an operational integration test o f tbe MPC system will be conducted as part of phase 3 of the MPC System procurement The test will build upon the results of the previous integration tests (described above) and is intended to add more realistic scenarios to test procedures such as the use of dummy fuel assemblies. Coordination o f this integration test with integration tests of the MPC and disposal container will ensure efficient use of resources.

• An operational integration test ofthe MPC and prototype disposal container will be conducted. Although this test will occur during initial production of MPCs it can occur no sooner than after the fabrication of the prototype disposal container. It is intended to ensote that MPCs are compatible with the disposal container. The operation of test equipment related to waste package performance, which is necessary to support performance confirmation tests, will also be evaluated.

• An operational integration test with the repository/prototype disposal container will be conducted. As die repository construction proceeds, portions of the facility will be available in which to conduct a test to assess the transfer of the canister from transportation to disposal and the transfer o f the cask from disposal to retrieval. This test will be conducted prior to fabrication of the disposal containers to ensure die repository/waste package functions as an integrated system. Additionally, this test will provide insight into waste handling operational procedures (e.g., those at the surface facility) that will be refined prior to final integration.

• The final operational integration test constitutes an assessment of die integration of people, procedures, and systems into the CRWMS prior to waste acceptance at the repository. I t will include all four elements of the system and will be scheduled well in advance of waste acceptance at the repository. An operational shakedown test will be conducted as part of the first deliveries of SNF from reactors to the repository.

• An operational effectiveness test will be conducted to determine the degree to which the MPC system performs its function in die storage mode at reactor sites. The selection o f measures of effectiveness will determine the scope of the tes t The Campaign Completion Report (CCR), which contains issues, recommended solutions, and changes to the CRWMS that arise during the campaign, will be used as an input to assess effectiveness.

Near terra tests on the Waste Acceptance System Element will ensote WA supports MPC deployment at reactor sites and tests performed in the long term support WA at the repository. A summary of die tests is presented below:

• An operational suitability test will be conducted to assess operational WA requirements necessary to support deployment of MFCs at reactor sites, such as requirements for development, review, and approval of delivery schedules and fuel description; verification; MC&A; and physical protection.

• An operational integration test will be conducted with the transportation system to ensure waste acceptance and transportation procedures are in agreement and in place to support loading o f MPCs. For example, these procedures address how WA keeps the transportation system apprised of changes to delivery commitment schedules and coordination required for approving site specific servicing plans. Further, procedures for item control (e.g., to monitor the transfer of items and the status of safeguards and security measures for all OCRWM system elements) will be assessed.

• A final operational integration test will be conducted with other CRWMS elements in preparation for waste acceptance at the repository. The test will be used to assess the integration of people, equipment, and any remaining procedures such as those used to support loading of MPCs into transport casks at reactor sites and those related to the operations center. An operational shakedown test will be conducted as part of the first deliveries of SNF from reactors to the repository.

5.3.4 Waste Package

The operational integration tests to be perforated on the waste package will build upon the development tests conducted on the prototype disposal container. A summary of the tests is presented below:

• Prior to conducting an operational integration test with the MPC, the operational suitability of the prototype disposal container will be assessed with a focus on operational requirements. For example, any changes in requirements for transferring the waste package (Le., transferring the MPC to a disposal container, placing the waste package on an emplacement cart, placing the cart in a shielded rail transfer cask, and off loading the waste package to a waste emplacement drift) will be made prior to conducting integration tests across system elements.

• An operational integration test with die MPC and prototype disposal container will be conducted. This test will occur after initial production of MPCs and is intended to ensure that, in the future, production of MPCs will not have to be modified as a result of an interface incompatibility with the disposal container. The operation of test equipment related to the waste package performance, which will be necessaiy to support performance confirmation tests, will also be evaluated. Results from laboratory tests during DT&E that focused on the

Ш Waste Acceptance System Element

internal condition of the disposal container will be used to refine test objectives. This test needs to be coordinated with tests proposed for phase 3 of die MPC System procurement

• Operational integration tests with the repository will be conducted. As the repository construction proceeds, portions o f the facility will be available in which to conduct tests to assess the receipt transfer, disposal, and retrieval of casks and canisters. The disposal and retrieval tests will be conducted with a prototype disposal container and shielded transfer cask to ensure the waste package/repository functions as an integrated system. Results of this test will be used to support the license application.

• The final operational integration test constitutes an assessment of the integration of people, procedures, and systems into die CRWMS prior to waste acceptance at die repository. It will include all four elements of the system and, if feasible, will begin during initial fabrication of production waste packages. An operational shakedown test will be conducted as part of the first deliveries o f SNF from reactors to the repository.

5.3.5 Repository

Operational integration tests conducted on the repository will be coordinated closely with those of the waste package. A summary o f the tests is presented below:

• Prior to conducting an operational integration test with the waste package, an operational suitability test will be conducted that will focus on the refinement of operational requirements of the repository. For example, any changes needed in requirements for transferring the waste package into the repository will be made prior to integration at higher levels.

• Operational integration tests with the waste package will be conducted. As die repository construction proceeds, portions o f the facility will be available in which to conduct tests to assess the receipt transfer, disposal, and retrieval of canisters and casks. Assessment of disposal and retrieval will be conducted with a prototype disposal container and shielded transfer cask to ensure the waste package/repository functions as an integrated system. Additionally, this test will provide insight into waste handling operational procedures (e.g., those at the surface facility) that will be refined prior to final integration.

• An operational integration test to assess the integration of people, procedures, and equipment will be performed that will include all four elements of the system. If feasible, it will be scheduled to begin during initial fabrication of production waste packages. An operational shakedown test will be conducted as part of the first deliveries of SNF from reactors to the repository.

• An operational effectiveness test will be performed to assess how well the CRWMS is performing its mission. The scope of the tests will depend on the selection of measures o f effectiveness. As a minimum, the tests will include the Performance Confirmation (PC) program carried out in accordance with Subpart F of 10 CFR 60, including tests related to the CRWMS ability to maintain radiation doses, levels, and concentrations o f radioactive material within prescribed limits, as well as thermal loading effects on waste isolation. During early

stages of construction, the repository will be capable of supporting in-situ testing of features such as access seals, backfill, and thermal interaction of subsystems in the Engineered Banier Segment to establish a baseline for the PC program. Tests will also be conducted during the preclosure period to evaluate die thermal effects o f actual emplaced waste. Long term portions of the PC program will confirm barrier and seal performance. Data will be collected until permanent repository closure to ensure that the performance of the natural and engineered features are within design limits.

С41

6. REGULATORY COMPLIANCE TEST AND EVALUATION

Regulatory Compliance T&E will be conducted by the projects with program assistance to support compliance with regulatory requirements and will occur in parallel with DT&E and OT&E phases. Although integrated within the overall CRWMS T&E program, it is included in this TEMP as a separate T&E p*iase because of the unique aspects of the regulatory requirements. Within OCRWM the Regulatory Guidance Document (RGD) provides policy and guidance to the program and projects regarding compliance with regulatory requirements in the areas of site suitability, environmental compliance, safety and health compliance, and licensing. In the context of the systems engineering process, the RGD allocates regulatory requirements at a top level by identifying the principal regulatory laws or regulations. A mote comprehensive set of regulatory requirements, with which compliance must be demonstrated, will be included in a Regulatory Compliance Plan (RCP), developed by each project The RCP will contain a comprehensive list o f all applicable requirements and the functional area to which each requirement applies. It will also identify the method o f implementation of the requirements, method of verification, form of the data used for verification, and frequency of implementation of the compliance strategy.

As with verification o f technical requirements, the mix of verification methods used to ensure compliance with regulatory requirements will depend on mission objectives, cost, and other project factors. Further, to ensure efficiency of resources, the project will need to integrate verification activities planned for technical requirements identified in the DRDs as well as verification activities planned for regulatory requirements identified in the RCPs. The allocation o f requirements to technical and regulatory functions will be documented and managed through die use of automation tools. Tools such as ARMS can be used to support this integration effort Planning for these integration activities w ill be documented in the project TEP and RCP.

6.1 REGULATORY CHARACTERISTICS

Regulatory characteristics contained in various regulatory documents apply to activities supporting the development and operation of the CRWMS. These requirements support the program technical baseline requirements identified in the CRD and SRDs. The top-level program compliance approach to meeting regulatory requirements is identified in the RGD. The four areas of regulatory requirements identified in the RGD include site suitability, environmental compliance, safety and health compliance, and licensing. Site suitability is presented in this TEMP under the DT&E phase. The RGD provides a matrix of environmental regulations allocated to appropriate CRWMS elements, and a matrix o f applicable safety and health regulations allocated to safety and health functional areas within each project Requirements contained in these matrices will be verified through T&E. However, major near term T&E activities are focused on licensing. Thus, this section of the TEMP will highlight T&E related to licensing, including cask certification. The highlighted categories o f Regulatory Compliance T&E are shown in Table 6-1 along with the corresponding program-level regulatory requirements section of the RGD, a reference to CRD related technical requirements, and a summary of the rationale for each test category. The environmental impact statement (EIS) T&E is also included in the table since several OCRWM milestones are linked to the EISs.

43

ТаЫе 6-1. Regulatory Compliance Phase

Test Category RGDSection

CRDSection

Rationale

Licensing 5. (3.7.4.2,3.7.3.2)*

Support license application to NRC (including support for the SAR) for Yucca Mountain and storage facility

Licensing (Certification) 5. 3.1.6* Support NRC test requirements to obtain a CoC for transportation and storage casks/modules

Environmental (EIS) 6. 3.3.11 Determine the degree to which system complies with environmental requirements (e.g., National Environmental Policy Act as implemented by 10 CFR 1021) 1

* Addreaes 10 CFR 60 for Yocca Moaataia tad 10 CFR 72 for storage facility.

* Section 3.1.6 U Major Coatkkmioniaad Аид nptioa« Alto iacfadea Anociatioa c i American Railroad»* approval <rf tafl can.

Specific regulatory requirements for the repository, contained primarily in 10 CFR 60, include the establishment of a performance confirmation program, which is discussed in Section 5.3.5 of this TEMP. In addition, 10 CFR 60.74, Tests," states that, "DOE shall perform...such tests as the Commission2 deems appropriate or necessary..." Therefore, the YMP needs to make allowances for such Commission requests.

Specific test requirements for the transportation cask are contained in 10 CFR 71 Subpart F, "Package and Special Form Tests" and in 10 CFR 72 Subpart L, "Approval of Spent Fuel Storage Casks,” for the storage cask. The type of testing, which can be viewed as qualification tests, to meet these regulatory requirements will also require interaction with the Commission, and will be affected by the specific test requirement and cost, among other factors. The mix of design verification methods will consist of a combination of examination, analysis, demonstration, and test activities acceptable to the Commission. For example, the effects of specified tests on the transportation cask will be determined by subjecting a scale model cask to test, or by other methods o f demonstration acceptable to die Commission. Thus, the WAST Project has to also make allowances for Commission requests and policy options.

3 "Commuskxf refer* to tbe Nodear Regulatory Сопшмпов.

&2 REGULATORY COMPLIANCE T&E TO DATE

In updates to the TEMP, Regulatory Compliance T&E already conducted will be summarized and presented in this section to establish a reference point for future Regulatory Compliance T&E. Reference will be made to published test reports as appropriate. More detailed Regulatory Compliance T&E information voll be provided in the project TEPs. If deficiencies are found the need for retest will be identified.

6.3 FUTURE REGULATORY COMPLIANCE T&E

Figure 6-1 presents the integrated test schedule with Regulatory Compliance T&E categories shaded. The Regulatory Compliance T&E phase and categories within that phase were developed by tailoring die tests in Table 6-1 to major OCRWM CIs to support OCRWM regulatory milestones. The CIs and their test categories are described below.


Near term regulatory compliance tests will focus on obtaining certification of designs for the legal weight truck (LWT) casks. The Certificate of Compliance (CoC) from the NRC will be for the design for die advanced technology GA-4 and GA-9 LWT casks. The certification process will include testing a half-scale cask model.

6.3.2 MPC

Regulatory compliance test activities related to the MPC include obtaining CoCs from the NRC. These activities are summarized below:

Regulatory compliance testing will be performed to obtain:

• CoC under 10 CFR 71 for the design of the small and large MPC Transportation Cask Subsystem Elements. The design would include MPCs for BWR and PWR fuel.

• CoC under 10 CFR 72 for the design of the small and large OSS and OST Segments. The design would include MPCs for BWR and PWR fuel.

Testing will also be required to periodically confirm and document cask compliance with the CoC. These tests will be defined during cask certification and will most likely require that leak testing be performed on a periodic basis and impact limiters be inspected. To ensure compatibility with the rail transportation system, approval will be obtained from the Association of American Railroads (AAR) for the small and ¡arge MPC Transportation Cask Transporter Subsystem Element

An EIS is being developed to assess potential impacts of fabricating and deploying MPCs. Data gathering for the EIS is complete. Thus, any testing in support o f the MPC EIS may be conducted in response to public comments or to activities resulting to m Draft EIS preparation.

45

Figure 6-1. TEMP Integrated Schedule: Regulatory Compliance T&E

ШПЕ • Schxfalt m inundad te b» mod lor ptmninq purpom . not lor гмподид er contwHnp TtEoetfciti»».

46

6.3.3 Repository/W aste Package

Regulatory compliance test activities will support the development of the license application and repository Q S as described below:

• Test activities to support the licensing process include those being conducted as part of á te suitability and other tests (e.g., thermal tests to support die system wide thermal management strategy) needed to update the Annotated Outline (AO) and support the license application. Test data to support the LA will be needed in the areas o f natural banier system performance (specifically in the areas of geology, tectonics, hydrology, climate, and thermal effects), engineered barrier systems, overall system performance, and performance confirmation. Early thermal tests, which will consist of in situ tests and laboratory thermal process tests, will serve as preliminary information to support suitability conclusions and will demonstrate an understanding of the localized effects of thermal loads. Test data from repository/waste package tests will be integrated with test data of the natural settings to assess compliance with allocated and overall performance requirements. Feedback from the NRC on the sufficiency of information provided in the AO will be used to determine what additional analyses or tests are needed to support the LA. Performance confirmation, considered part o f OT&E operational effectiveness is discussed in Section 5.3.5.

• The purpose of tests to support the EIS will be to describe the characteristics of the existing environment and to assess die effects construction, operation, and post closure performance will have on the environment The repository EIS will incorporate test data from die environmental monitoring program that began in 1985; new site characterization activities; where appropriate, the MPC EIS; and other related DOE ElSs. Test data to support the description of the existing environment will be needed in the areas of air quality, terrestrial ecosystem, radiation, water resources, soils, and noise. Also, information on the effects of thermal loading may be required. Specific information needs will be defined during the EIS scoping process conducted after the Notice of Intent (N01). The issuance of an EIS N01 is planned for fiscal year 1995.

47


48

7. T&E RESOURCE SUMMARY

Adequate resources are required to ensure that project tests are effectively implemented. Projects will identify resources in their test plans and specifically identify resources required for program level tests such as those in the OT&E phase. Subsequent TEMP updates will identify those resources in this section. A description of diese resources will be presented in a tabular format with resources linked to each test Resources will include test articles; test sites/instrumentation; test support equipment; simulators, models, and testbeds; personnel/training; test data reduction requirements; and any unique requirements.

49

T ras PAGE INTENTIONALLY LEFT BLANK

50

r >w

8. REFERENCES

1. U.S. Department o f Energy, Quality Assurance Requirements and Description (QARD), Revision 2, DOE/RW-0333P, Washington, D.C., Match 1995.

2. U.S. Department of Energy, Systems Engineering Management Plan (SEMP), Revision 3, DOE/RW-0051, Washington, D.C., June 1994.

3. U.S. Department of Energy, Civilian Radioactive Waste M anagement Program Plan, DOE/RW-0458 (three volumes), Washington, D.C., December 1994.

4. U.S. Congress, Nuclear Waste Policy A ct (NWPA) o f l982, as amended by the Nuclear Waste Policy Amendments A ct (NWPAA) o f1987, PL 97-425, U.S. Code, Title 4 Г Sec. 10101 et seq.

5. CRWMS M&O, System Evaluation Criteria, Revision 3, Draft, prepared for the DOE/OCRWM under contract no. DE-AC01-91RW00134, Vienna, VA, January 7,1994.

6. U.S. Department o f Energy, Regulatory Guidance Document (RGD), Revision 0, DOE/RW- 0441, Washington, D.C., May 1994.

7. U. S. Department of Energy, Baseline Management Plan (BMP), Revision 0, DOE/RW-0381P,^ Washington, D.C., November 1992.J

8. U.S. Department of Energy, M ined Geologic Disposal System Requirements Document (MGDS-RD), Revision 1, DOE/RW-0404P, Washington, D.C., March 1994.

9. U.S. Department of Energy, M onitored Retrievable Storage System Requirements Document (MRS-SRD), Revision 1, DOE/RW-0420, Washington, D.C., Match 1994.

10. U.S. Department of Energy, Transportation System Requirements Document (Trans-SRD), Revision 1, DOE/RW-0425, Washington, D.C., March 1994.

11. U.S. Department of Energy, Waste Acceptance System Requirements Document (WA-SRD), Revision 1, DOE/RW-0351P, Washington, D.C., March 1994.

12. CRWMS M&O, System Requirements Issue Resolution Plan, Preliminary Draft, prepared for the DOE/OCRWM under contract no. DE-AC01-91RW00134, Vienna, VA, March 31,1994.

13. U.S. Department of Energy, MPC Transportation Cask Subsystem Design Requirements Document, Revision 0, DOE/RW-0467, Washington, D.C., February 1995.

14. U.S. Department of Energy, M ulti-Purpose Canister (MPC) Subsystem Design Requirements Document, Revision 0, DOE/RW-0466, Washington, D.C., February 1995.

51

15. CRWMS M&O, M ulti-Purpose Canister (MPC) Implementation Program Conceptual Design Phase Report, Volume V - MPC Supporting Studies and Reports, Revision 0, prepared for tbe DOE/OCRWM under contract no. DE-AC01-91RW00134, Vienna, VA, September 1994.

16. 10 CFR Part 72, Licensing Requirements fo r the Independent Storage o f Spent N uclear Fuel and High-Level Radioactive Waste, Code of Federal Regulations.

17. 10 CFR Part 60, Disposal o f High-Level Radioactive Wastes in Geologic Repositories, Code of Federal Regulations.

18. 10 CFR Part 71, Packaging and Transportation o f Radioactive M aterial, Code of Federal Regulations.

19. U.S. Congress, National Environmental Policy A ct (NEPA), U.S. Code, Title 42, Sec. 4321 et seq., 1969.

20. U.S. Department of Energy, Civilian Radioactive W aste Management System Requirements Document (CRD), Revision 1, DOE/RW-0406P, Washington, D .C , March 1994.

21. Y ucca Mountain Site Characterization Project, Site Design and Test Requirements Document, Revision 1, YMP/CM-0021, Las Vegas, NV, August 1994.

22. CRWMS M&O, M&O MPC System Acceptance Plan, Revision 0, A20000000-01717-4600-00007, Vienna, VA, March 31,1995.

23. Yucca Mountain Site Characterization Project, Test and Evaluation Plan, Revision 1, Las Vegas, NV, May 1993.

24. 10 CFR Part 960, General Guidelines fo r the Recommendation o f Sites fo r Nuclear Waste Repositories, Code of Federal Regulations.

25. Yucca Mountain Site Characterization Project, M ined Geologic Disposal System license Application Annotated Outline, Revision 0 (three volumes), YMP/94-05, Las Vegas, NV, March 1995.

26. U.S. Department of Energy, Site Characterization Plan, DOE/RW-0199, (eight volumes). Yucca Mountain Site, Nevada Research and Development Area, NV, December 1988.

APPENDIX A • ACRONYMS

AAR Association of American RailroadsAO Annotated OutlineARMS Automated Requirements Management SystemBMP Baseline Management PlanBWR Boiling Water ReactorCCR Campaign Completion ReportCDR Conceptual Design ReportCFR Code of Federal RegulationsC l Configuration ItemCU N Contract Line Item NumberCMOCC Central Management and Operations Control CenterCoC Certificate of Compliancecars Commercial Off the ShelfCRD CRWMS Requirements DocumentCRWMS Civilian Radioactive Waste Management SystemCVM Conformance Verification MatrixDOE Department of EnergyDPS Design Procurement SpecificationDRD Design Reouiiements DocumentDT&E Development Test and EvaluationEIS Environmental Impact StatementESF Exploratory Studies FacilityPCA Functional Configuration AuditFMEA Failure Modes and Effects AnalysisFQR Formal Qualification ReviewHLW High-Level Radioactive WasteIAEA International Atomic Energy AgencyICD Interface Control DocumentÎCWG Interface Control Working GroupIMS Information Management SystemLA License ApplicationLWT Legal Weight TruckMC&A Material Control and AccountingMGDS Mined Geologic Disposal SystemМОЕ Measures of EffectivenessMPC Multi-Purpose CanisterMRS Monitored Retrievable StorageN/A Not ApplicableNDI Non Developmental ItemNEPA National Environmental Policy ActN01 Notice of IntentNRC Nuclear Regulatory CommissionNWPA Nuclear Waste Policy Act of 1982

OCRWM Office o f Civilian Radioactive Waste ManagementOFMI Office o f Program Management and IntegrationOSS On-Site StongeOST On-Site TransferOSTS On-Site Transfer and StorageOT&E Operational Test and EvaluationOWAST Office o f Waste Acceptance, Storage and TransportationPBCCB Program Baseline Change Control BoardPC Performance ConfirmationPCA Physical Configuration AuditPWR Pressurized W«ter ReactorQA Quality AssuranceQARD Quality Assurance Requirements and DescriptionRAM Reliability, Availability, and MaintainabilityRCP Regulatory Compliance PlanRGD Regulatory Guidance DocumentRT/CVM Requirements Traceability/Conformance Verification MatrixSAR Safety Analysis ReportSBTF Surface-Based Testing FacilitiesSEMP Systems Engineering Management PlanSNF Spent Nuclear FuelSRD System Requirements DocumentT&E Test and EvaluationTBD To Be DeterminedTBR To Be ResolvedTEMP Test and Evaluation Master PlanTEP Test and Evaluation PlanTPM Technical Performance MeasurementTRR Test Readiness ReviewsWAST Waste Acceptance, Storage, and Transportation ProjectYMP Yucca Mountain Site Characterization ProjectYMSCO Yucca Mountain Site Characterization Office

54

Г

APPENDIX В - GLOSSARY

Acceptance is the documented determination by the receiving organization that a work product is suitable for the intended purpose.

Campaign is defined as the activities required to prepare for and execute a consecutive set of shipments from a given shipping (originating) site to a single delivery site over a fixed period of time.

Campaign Completion R eport (CCR) records issues, recommended solutions, and changes to the CRWMS that arise during the campaign.

Campaign K it is the collection of equipment required to interface a cask with the Purchaser’s SNF storage facilities in order to accomplish the campaign.

Configuration Item (C l) is an aggregation of facilities, hardware, software, or any o f their discrete components that satisfies individual physical, functional and/or interface characteristics, and is controlled by configuration management CIs vary in complexity, scope, size, and type. CIs are those items whose performance parameters and physical characteristics are separately controlled and defined to achieve the overall end use function and performance during design and development, manufacturing, construction, installation, operation, maintenance, and decontamination and decommissioning.

C l Architecture consists o f seven indenture levels. In descending order, each level is defined as follows: 1) System, 2) System Element, 3) Segment, 4) Subsystem, S) Subsystem Element, 6) Component, and 7) Element The Cl architecture is modified for the Storage System Element and includes one additional indenture level. The C l architecture for the Storage System Element is defined as follows: 1) System, 2) System Element 3) Subelement, 4) Segment 5) Subsystem, 6) Subsystem Elem ent 7) Component and 8) Element

Development Test and Evaluation (DT&E) is the T&E conducted throughout the acquisition process to assist in engineering design and development and to verify that technical performance specifications have been m et DT&E supports die system design process through a test-analyze-fix- retest approach that involves both contractor and government personnel.

Disposal means the emplacement in a repository or HLW, SNF, or other highly radioactive waste with no foreseeable intent of recovery, whether or not such emplacement permits recovery of such waste.

High-Level Radioactive W aste (HLW) means (1) the highly radioactive material resulting from the reprocessing of spent nuclear fuel, including liquid waste produced directly in reprocessing, and any solid material derived from such liquid waste that contains fission products in sufficient concentrations; and (2) other highly radioactive material that the Nuclear Regulatory Commission, consistent with existing law, determines by rule requires permanent isolation.

Interface means the functional and physical characteristics required to exist at a common boundary between two or more items. Interfaces are of two types: (1) functional interfaces that indicate a flow between a sequence of activities, and (2) physical interfaces that indicate a necessary fit between architectures.

Key Operational C haracteristics are requirements o f specific configuration items, including the system, that have a significant impact on system operation and are critical to the success of the program. These requirements provide quantitative and qualitative measures against which operational suitability and effectiveness will be evaluated during OT&E.

Key Technical Characteristics are requirements of specific configuration items that have a significant impact on subsystem performance and are critical to the success o f the program. They provide quantitative measures against which performance will be evaluated during DT&E.

Key Regulatory Characteristics are program requirements that apply to the activities associated with supporting the development and operation of the CRWMS. These requirements, which are contained in various regulatory documents, are divided into four categories: site suitability, licensing, environmental compliance, and safety and health compliance.

M easure o f Effectiveness (МОЕ) is a metric used to quantify the performance of integrated system solutions (people, product, and process) in terms that describe the utility or value when using those solutions to meet customer needs.

M ulti-Purpose Canister (MPC) refers to a sealed, metallic container maintaining multiple SNF assemblies in a dry, inert environment and overpacked separately and uniquely for the various system elements of storage, transportation, and disposal.

Operational Effectiveness is the overall degree of mission accomplishment of a system when used by representative personnel in the environment planned or expected for operational employment, considering organization and operational approach.

O perational Integration addresses the degree to which the system, personnel, and procedures, and associated training and logistics have been integrated into the CRWMS in accordance with requirements. It is concluded with an operational shakedown test which reflects the integrated readiness of the system, people, and procedures to assume full operational status.

Operational Suitability is the degree to which a system can be placed satisfactorily into operation when operated and maintained by the users considering human factors, operational requirements, safety, reliability, availability, maintainability, security, and unique requirements.

Operational Test and Evaluation (OT&E) is the field test, under realistic conditions, of any item or key component for the purpose of determining the effectiveness and suitability of the item for use by typical users; and the evaluation of the results o f such test

Performance Assessm ent is anv analysis that predicts the behavior of a system or system component under a given set of constant and/or transient conditions. Performance assessments will include estimates of the effects 01 oicertainties in data and modeling.

Performance C onfirm ation is the ; : vram of tests, experiments, and analyses that is conducted to evaluate the accuracy and adequacy of the information used to determine with reasonable assurance that the performance objectives [set for the repository] for the period after permanent closure can be m et

Program Interface is 1) a physical, functional, or operational boundary between elements of the CRWMS or between CRWMS elements and outside entities, or 2) a physical, functional, or operational boundary between element subsystems whose performance has direct and measurable impact on achieving CRWMS system element performance objectives.

Program-Level T est is a test that verifies compliance with requirements that have direct and measurable impact on achieving CRWMS system element performance objectives as stated in the CRD and/or SRDs or a test that verifies performance of program interfaces.

Quality Assurance (QA) is the planned and systematic action necessary to provide adequate confidence that an item conforms to established technical requirements and achieves satisfactory performance in service.

Regulatory Com pliance Test and Evaluation is the T&E conducted to support compliance with regulatory requirements. Regulatory Compliance T&E is conducted in parallel with DT&E and OT&E phases.

R isk Management is an organized means of identifying and measuring risk (risk assessment) and developing, selecting, and managing options (risk analysis) for resolving (risk handling) these risks.

S ite Characterization is the program o f exploration and research, both in the laboratory and in the field, undertaken to establish the geologic conditions and the ranges of those parameters of a particular site relevant to the requirements under 10 CFR Parts 60 and 960. Site characterization includes borings, surface excavations, excavation of exploratory shafts, limited subsurface lateral excavations and boxings, and in situ testing at depths needed to determine the suitability o f the site fo r a geologic repository, but does not include preliminary borings and geophysical testing needed to decide whether site characterization should be undertaken.

Spent Nuclear Fuel (SNF) is fuel that has been withdrawn from a nuclear reactor following irradiation, the constituent elements of which have not been separated by reprocessing.

Storage means retention of spent nuclear fuel or radioactive wastes with the intent and capability to readily retrieve such fuel or waste for subsequent use, processing, or disposal.

System is a composite, at any level of complexity, of personnel, procedures, materials, tools, equipment facilities, and software. The elements of this composite entity are used together in the

57

intended operational or support environment to perform a given task or achieve a specific production, support, or mission requirement

Systems Engineering is the logical sequence of activities and decisions that transform an operational need into a description of system performance parameters and a preferred system configuration.

Test 1. An element o f verification for the determination of the capability of an item to meet specified requirements by subjecting the item to a set o f physical, chemical, environmental, or operating conditions. 2. Used in a broad sense it describes die four types of verification methods (i.e., tes t examination, analysis, or demonstration).

T est Resources is a collective term that encompasses all elements necessary to plan, conduct, collect and analyze data from a test event or program. Resource elements include test articles; test sites/instrumentation; test support equipment; simulators, models, and testbeds; personnel/training; test data reduction requirements; and any unique requirements.

Technical Perform ance M easurement (TPM) is the product design assessment that estimates, through engineering analyses and tests, the values of essential performance parameters of the current design of work breakdown structure product elements. TPM is used to forecast the values to be achieved through the planned technical program effort measure differences between achieved values and those allocated to the product element by the systems engineering process, and determine the impact of these differences on system effectiveness.

Verification is the process that is performed to determine by investigation of objective evidence the adequacy of and compliance with established implementing documents and die effectiveness o f implementation.

W aste Package is the waste form and any containers, shielding, packing and other absorbent materials immediately surrounding an individual waste container. Tests with the waste package will not include the waste form until shakedown tests as part of the first deliveries from reactor sites.

58

Tbe following number is for OCRWM Records Management puiposes only and should not be

used when ordering this publication.

Accession No. HQ0*950821 *0001

OCRWM Test and Evaluation Master Plan (TEMP) · 2014. 12. 8. · DOE/RW-0478 OCRWM Test and...

Documents

Transcript of OCRWM Test and Evaluation Master Plan (TEMP) · 2014. 12. 8. · DOE/RW-0478 OCRWM Test and...