10.12.2012 Views

Euradwaste '08 - EU Bookshop - Europa

Euradwaste '08 - EU Bookshop - Europa

Euradwaste '08 - EU Bookshop - Europa

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

and for independently investigating the possible impact of alternative PA parameter values and assumptions.<br />

The Finnish regulator plans to use a simple code to verify what the developer has modelled.<br />

The UK environmental regulators rely on consultants to develop and run codes only as necessary.<br />

The question was discussed of how distant or close the regulator should be to the developer during<br />

the development of the safety case to avoid compromising its review process during a licence application<br />

stage. Although the onus for developing the safety assessment, safety case and licence application<br />

rests with the developer, it is the regulator that grants the licence or authorisation, and it is<br />

the regulator, not the developer, which has to defend and justify to the public and other stakeholders<br />

the decision to dispose of waste. Stakeholders must recognise that although a regulator must not be<br />

compromised in any way and should have freedom to make decisions once a licence application is<br />

submitted, it nevertheless needs detailed knowledge of the safety assessment and safety case in order<br />

to review the application and defend its decision to grant or recommend a licence or authorisation.<br />

Ideally, regulatory decisions should not be bound by any commitments made to the developer<br />

prior to receipt of the application. Basic scientific knowledge can be jointly gained and commonly<br />

understood, but it is used differently by the developer and regulator.<br />

A pre-application review procedure means, by necessity, that a regulator will advise or require a<br />

developer at various intervals to do specific pieces of research or investigation, and this appearance<br />

of working together needs to be explained to stakeholders in order to avoid misunderstanding during<br />

the licensing process. A regulator might pose questions to, and place requirements on, the developer<br />

via regulatory review, but the regulator should not provide the answers.<br />

A formal process of staged authorisation has been outlined in the UK in new regulatory guidance on<br />

requirements for authorisation for geological disposal facilities, with a series of formal hold-points<br />

to be decided by the regulator [6]. If adopted, this regulatory process will formalise the need for<br />

dialogue between the regulator and the developer.<br />

4.3 Main Messages<br />

Some key messages arising from the workshop were:<br />

Although international harmonisation of dose and risk constraints would be ideal for communication<br />

with the public, the practicalities of national contexts mitigate against this being achieved.<br />

There is now less emphasis than before being placed in the safety case on the traditional comparison<br />

between safety assessment calculation results and dose/risk criteria set by the regulator.<br />

Optimisation and safety functions are increasingly being used as alternative safety indicators or<br />

additional arguments in a safety case in support of compliance with the regulatory dose/risk criteria<br />

and to build confidence in long-term safety. These changes in the emphasis of safety cases<br />

may require additional regulatory research and capabilities.<br />

Most regulators want to match the level of scientific understanding and knowledge of the developer/implementer<br />

in order to be capable of performing meaningful reviews of RD&D programmes,<br />

safety cases and licence applications.<br />

Many regulators have taken steps to have modelling capabilities independent of the developers’<br />

capabilities in order to be able to verify the results of the developers’ assessment calculations<br />

and to investigate alternative conceptual or models.<br />

385

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

Saved successfully!

Ooh no, something went wrong!