1 / 25

Framework for Risk Analysis in Multimedia Environmental Systems Version 2 (FRAMES-2)

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. Contributing Members. EPA ORD. DOE EM. Facilitating cooperation,

salinan
Télécharger la présentation

Framework for Risk Analysis in Multimedia Environmental Systems Version 2 (FRAMES-2)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 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 EPA ORD DOE EM Facilitating cooperation, coordination, and exchange of technical information, related to the multimedia environment EPA ORIA PNNL DOE NRC Research DoD ERDC 2

  3. 3

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

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

  6. Purpose: Merged the best attributes of 3MRA, ARAMS, GENII, and FRAMES-V1Objective: 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 Workshophttp://www.ISCMEM.org 6

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

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

  9. FRAMES-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 9

  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 10

  11. Static Telephone Book Dynamic Telephone Books Design AspectsBackward Compatibility 11

  12. Conceptual Site Model and Drag & Drop Feature 12

  13. Visualization of S/U Output Results

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

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

  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 16

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

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

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

  20. Plug & Play Feature Applicable Models 20

  21. Plug & Play Feature Non-applicable Models 21

  22. Model Developer Database Owner User (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 22

  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. 23

  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) 24

  25. Summary • 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) 25

More Related