Framework for Risk AnalysisFramework for Risk Analysisin Multimedia Environmentalin Multimedia Environmental

Systems - Version 2 (FRAMES-2)Systems - Version 2 (FRAMES-2)

OverviewOverview

Framework for Risk AnalysisFramework for Risk Analysisin Multimedia Environmentalin Multimedia Environmental

Systems - Version 2 (FRAMES-2)Systems - Version 2 (FRAMES-2)

OverviewOverview

FRAMES-2.0 WorkshopU.S. Nuclear Regulatory Commission

Bethesda, MarylandNovember 15-16, 2007

Pacific Northwest National LaboratoryRichland, Washington

2

Contributing MembersContributing MembersContributing MembersContributing Members

3

Conceptual Site Model

4

ObjectiveObjectiveObjectiveObjective

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 Workshophttp://www.ISCMEM.org

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

MiddlewareMiddleware

6

7

Design GoalsDesign GoalsDesign GoalsDesign 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

Seamless and Transparent Communication Through ARAMS/FRAMES for Linking Disparate Objects

Seamless and Transparent Communication Through ARAMS/FRAMES for Linking Disparate Objects

Model 2

Model 1

ModelOutput

Model Output

Model Input

Database Data

Database Data

User-SpecifiedInput

FRAMES-2 infrastructure is

interested in the I/O, not the Objects

(e.g., models, DBs)

User-SpecifiedInput

Model wrapping in FRAMES-2 requires adding dictionary and description files, and model switches

FRAMES-2 CommunicationFRAMES-2 CommunicationFRAMES-2 CommunicationFRAMES-2 Communication

9

ChemAquiferConcDissolved chemical concentrationsVersion: 2Privilege: System Boundary

Name Description Unit Measure Type Range S D U K Prep Indices

ConcThe dissolve-phase concentration associated with water

mg/L Mass/Volume FLOAT 0 - 1E+30 N 3 Y NAquiferPoints.Feature ChemList.CASID TimePts

TimePts Concentration time point yr Time FLOAT 0 - 1E+08 Y 3 N NAquiferPoints.Feature ChemList.CASID

Legend

Column Name

Meaning

S Self-IndexedD Dimensional SizeU Uncertainty can apply (Stochastic)K Is the variable a key to others

Metadata Describing Concentration as a Function of Time and Location

Example DictionaryExample DictionaryExample DictionaryExample Dictionary

10

Defining Connection SchemesDefining Connection SchemesDefining Connection SchemesDefining Connection Schemes

Model 2ProduceDIC 6

ConsumeDIC 1, 2, 3

Scheme # Connection Scheme

1

Model 2ProduceDIC 3, 5

ConsumeDIC 4, 6

Model 2Produce

DIC 1, 2, 6

2

3

11

Conceptual Site Modelin the Simulation Editor

12

Applicable Models

Non-applicable Models

13

FRAMES-2 EditorsFRAMES-2 Editors(User-Friendly Wizards)

FRAMES-2 EditorsFRAMES-2 Editors(User-Friendly Wizards)

System InformationDICtionary Editor – Add/Edit DICtionaries

(Units) Conversion Editor – Add/Edit units and conversions

Model InformationModule (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 SpaceSimulation Editor – Conceptual Site Model (CSM) work space, containing the Drag & Drop functionality.

14

SummarySummarySummarySummary

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.