Framework for Risk Analysis in Multimedia Environmental Systems Version 2 (FRAMES-2) Workshop U.S. Nuclear Regulatory Commission Rockville, Maryland Pacific Northwest National Laboratory November 15-17, 2005

2 Contributing Members DoDERDCNRCResearch Facilitating cooperation, coordination, and exchange of technical information, related to the multimedia environment EPA ORD DOE EM PNNLDOE EPA ORIA

3

 Initial idea for RAPS  Initial proposal of RAPS to DOE  Initial proposal of MEPAS to DOE  Version 1.0 of MEPAS  Initial idea for RAAS  Version 2.0 of MEPAS with DOS user interface   DOE’s Environmental Survey using MEPAS   MEPAS used to conduct risk-based characterization on SST analytes  Version 3.0 of MEPAS  Version 4.0 of MEPAS  Version 4.1 of MEPAS  Initial idea for FRAMES  Version 1.0 of FRAMES  Version 1.1 of FRAMES  Initial idea for Modular Risk Analysis (MRA) approach   Use of MEPAS & MRA approach on HRA-EIS   MEPAS used DOE’s PEIS   MEPAS used DOE’s BEMR  Initial funds from EPA for 3MRA-HWIR   Use of MEPAS & MRA on WIPP-SEIS II   Pantex RA uses FRAMES 1.0  Merged System  Unified Life Cycle Analysis Time Line of Multimedia Modeling Developments at PNNL FRAMES: $8M/10 yrs Multimedia Modeling: $23M/23 yrs

FRAMES-2.0 EPA-ORD 3MRA-2.0 Site Specific FRAMES Development History FRAMES-1.0 EPA-ORD/OSW FRAMES-3MRA-1.0 (National Assessment) EPA-ORD FRAMES-3MRA-1.x (UA/SA) FRAMES-1.1 to 1.7 FRAMES-3MRA DoD-ERDC ARAMS EPA-ORIA SuperMUSE Framework Independent Component NRC DoD-ERDC ARAMS-2.0 EPA-ORIA IWRMS (King County) SuperMUSE

6 Purpose: Merged the best attributes of 3MRA, ARAMS, GENII, and FRAMES-V1 Objective: Design a software system that allows the non-parochial communication between disparate models, databases, and frameworks. Design a functionally easy system which can be modified and updated by “users.” Constraints: Follow requirements outlined at the NRC-hosted 2000 workshop, documented in the Proceedings of the Environmental Software Systems Compatibility and Linkage Workshop

7 FRAMES-2FRAMES-2 Middleware Middleware  Collaboration and Communication Allows for the seamless transfer of data between disparate models, databases, and modeling systems. User gets to pick models and databases of choice. Intuitive system that can be modified and updated by users.

Simple Medium Complex Model Type 1 (e.g., Source Model) Model Type 2 (e.g., Aquifer) FRAMES = Data processor = Modules Model Type 3 (e.g., Risk Model) 3 2 1

9 FRAMES-2.0FRAMES-2.0 FRAMES-1.x – Site-Specific analyses 3MRA – National, Complex-wide analyses FRAMES-2.x – FRAMES-2, using the best features of FRAMES-1 and 3MRA Build Site-Specific Assessments, then role results up into Complex-Wide Analyses Many non-Environmental Uses

10 Design Goals of FRAMES-2 Design a software system that allows the non-parochial communication between disparate models, databases, and frameworks. Design a functionally easy system which can be modified and updated by “users.” Provide a platform that allows “objects” to ACCESS information generated/produced by other “objects.” Keep it simple, not simplistic Make it understandable Standardize and develop consistent and repeatable protocols Reproducibility means Credibility Visualize the problem -- PICTURES Visualize the results -- PICTURES Provide Sensitivity/Uncertainty Capabilities

11 Static Telephone Book Dynamic Telephone Books Design Aspects Backward Compatibility

12 Conceptual Site Model and Drag & Drop Feature

Visualization of S/U Output Results

Probability of Exceedence (%) Inventory (g) Distance from Source (cm) Probability of a Peak Benzene Concentration Being Above the Acceptable Limit of 4.6E-02 mg/L Visualization of S/U Output Results Probability of Exceedence (%)

15 Automation and Reproducibility (Some Quick Examples) RAGS Generation as a Quick Example Automated Testing

16 FRAMES-2 Key Concepts Identify and agree upon a specific “Contract” as to how data/information are packaged and passed (DIC) Identify and agree upon how data are measured and what they mean (i.e., metadata) (DIC Editor and [(Units) Conversion Editor] Define what your model/DB is (Domain editor) Define the direct contextual relationship of your model/DB to other components in the system [Module (DES) Editor and Simulation Editor] Define very clear and strict data/information protocols

17 Seamless and Transparent Communication Through ARAMS/FRAMES for Linking Disparate Objects Model 2 Model 1 Model Output Model Output Model Input Database Data User-Specified Input FRAMES-2 infrastructure is interested in the I/O, not the Objects (e.g., models, DBs) User-Specified Input Model wrapping in FRAMES-2 requires adding dictionary and description files, and model switches Forward→ FRAMES-2 Communication

18 Standard DICtionary Describing Concentration as a Function of Time and Location

19 Defining Connection Schemes Model 1 Produce DIC 6 Consume DIC 1, 2, 3 Scheme # Connection Scheme 1 Model 1 Produce DIC 3, 5 Consume DIC 4, 6 Model 1 Produce DIC 1, 2, 6 Consume DIC 1, 3, 4, 5 2 3

20 Applicable Models Plug & Play Feature

21 Plug & Play Feature Non-applicable Models

22 Model Developer Database OwnerUser (Analyst) Build or Import DICs Define Units Build/Import Modules Set up Domain Define Connection Schemes Tools: (Units) Conversion Editor DICtionary Editor Domain Editor Module (DES) Editor Dataset Editor Map DB Schema Develop DB Extraction Plans Tools: Data Owner Tool Data Extraction Tool Select Domain Select Icons Connect Icons Select Models & Databases Run Extraction Plans Tools: Simulation Editor Data Client Editor (GMUI) Dataset Editor

23 FRAMES-2 Editors DICtionary Editor – Allows the user to add new or edit existing DICtionaries. (Units) Conversion Editor – Allows the user to add additional or edit existing unit conversions supported by the system. Module (DES) Editor – Allows the user to input and edit the DEScription (DES) DICtionary, which contains information about the model (e.g., icon Class, which Boundary Condition and Input DICs are consumed and which Boundary Condition DICs are produced, who to contact for more information, etc.). Domain Editor – Allows the user to define where the model fits in the system (e.g., icon type, Domain, Group, and Subgroup, etc., but not Class). Simulation Editor – Allows the user to edit the Conceptual Site Model (CSM) work space, containing the Drag & Drop functionality of constructing a CSM and linking modules together. This editor is the FRAMES CSM interface.

24 Current FRAMES-2 Activities Groundwater Modeling System (NRC Research) Adaptive Risk Assessment Modeling System (DoD-ERDC) Multi-media, Multi-pathway, Multi-Exposure Risk Assessment (3MRA) Methodology (EPA-ORD) SuperMUSE Parallel Processing System (EPA-ORD) Rapid Risk Assessment (Emergency Preparedness and Response) (PNNL-DOE) Biologically Based Modeling (PNNL-DOE) Universal Linkage to Databases (PNNL-DOE) Data Access Network (DOE-Hanford) Integrated Water Resource Modeling System (IWRMS)

25 SummarySummary Design, based on March 2000 Workshop Requirements Middleware, designed for seamless transfer of data between Disparate Models Disparate Databases Disparate Modeling Systems (Frameworks) Intuitive system, which can be modified and updated by “users.” Not Necessarily Environmental Centric Multimedia Modeling: $23M ($8M for FRAMES)