1. Framework for Risk Analysis in Multimedia Environmental Systems - Version 2 (FRAMES-2) Overview FRAMES-2.0 Workshop U.S. Nuclear Regulatory Commission Bethesda, Maryland November 15-16, 2007 Pacific Northwest National Laboratory Richland, Washington

2. 2 Contributing Members

3. 3 Conceptual Site Model

4. 4 ObjectiveObjective Design a software system that allows for 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 http://www.ISCMEM.org

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

6. 6

7. 7 Design Goals 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

8. 8 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 FRAMES-2 Communication

9. 9 Metadata Describing Concentration as a Function of Time and Location Example Dictionary

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

11. 11 Conceptual Site Model in the Simulation Editor

12. 12 Applicable Models Non-applicable Models

13. 13 FRAMES-2 Editors FRAMES-2 Editors (User-Friendly Wizards) System Information DICtionary Editor – Add/Edit DICtionaries (Units) Conversion Editor – Add/Edit units and conversions Model Information Module (DES) Editor – Module info: Icon type, Schemes, I/O DICs. Domain Editor – Where the model fits in the system (e.g., Icon, Domain, Group, and Subgroup, but not Class). Work Space Simulation Editor – Conceptual Site Model (CSM) work space, containing the Drag & Drop functionality.

14. 14 SummarySummary The strength of FRAMES lies with its peripherals: wizards, editors, user-friendly interfaces, etc. The user supplies the components: models, databases, spreadsheets, etc. QA/QC designed: Reproducible at the touch of a “GO” button.