10.12.2012 Views

Euradwaste '08 - EU Bookshop - Europa

Euradwaste '08 - EU Bookshop - Europa

Euradwaste '08 - EU Bookshop - Europa

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

10-11 June 2008. The workshop was attended by 16 participants drawn from regulators and other<br />

organisations with close interests in the management of uncertainties in the safety case for geological<br />

disposal of radioactive waste. The workshop was facilitated by Roger Wilmot of GSL, and a<br />

workshop report is available [5].<br />

The workshop was grouped into three main sessions with contributed presentations, which provided<br />

a stimulus for wider discussion of the issues:<br />

1. Uncertainties in the safety case. This session addressed some of the key issues relating to the<br />

treatment of uncertainty that are faced by regulators, and included summaries of previous work.<br />

2. Regulatory guidance on the treatment of uncertainties. An important means for regulators to<br />

influence the treatment of uncertainties is through guidance. This session described recent experience<br />

in developing regulatory guidance.<br />

3. Regulatory review of uncertainty treatment. Reviews and assessments of safety cases and license<br />

applications allow regulators to determine whether their requirements and expectations<br />

concerning the treatment of uncertainty have been met. This session described some recent review<br />

experience.<br />

A final discussion session that considered points that had been raised throughout the workshop is<br />

summarised in Section 4.2. Key messages from the workshop are summarised in Section 4.3.<br />

4.2 Discussion<br />

Discussion of the regulatory review process highlighted some general points. First, the regulator<br />

does not need to replicate the full safety assessment produced by a developer (a situation that pertained<br />

earlier in the UK). Instead, the regulator is concerned with reviewing the research, development<br />

and demonstration (RD&D) programme or safety case submitted by a developer, and in doing<br />

so it will use its own capabilities to assess and evaluate key processes and uncertainties. Following<br />

a review, a regulator is in a position to require the developer to carry out what it considers to be<br />

necessary further research, site characterisation or assessment.<br />

There is the question of when should the regulator request a developer to do a piece of research<br />

rather than doing it itself. Research pursued by a regulator or regulatory support organisation is<br />

likely to be focused on obtaining improvements in scientific and technical knowledge as a basis for<br />

effective reviews and for maintaining and developing regulatory competence. In addition, a regulator<br />

may carry out some ‘seed’ research in order to demonstrate to the developer that a research area<br />

should be investigated in more detail. The Swiss regulator places importance on its experts staying<br />

at the forefront of science and performing quality ‘independent’ research.<br />

Although a developer has the primary responsibility to verify its codes, the question of how much<br />

involvement a regulator should have in code verification was posed for discussion. During the<br />

compliance certification (authorisation process) of the Waste Isolation Pilot Plant (WIPP) in the<br />

US, the regulator requested the developer to re-run the assessment using regulator-provided parameter<br />

values. Although this was not a code verification exercise, it circumvented the problem that<br />

the regulator had no code to carry out its own independent assessment calculations. On the other<br />

hand, the French, German, Swedish and Swiss regulators develop and maintain their own codes and<br />

an independent capability for modelling radionuclide transport and PA. This is considered important<br />

for verifying the developer’s results, for consideration of the assumptions buried in the codes,<br />

384

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!