Virtual Plumes Workshop Paul Holland, Exelon nbs

Document Sample
Virtual Plumes Workshop Paul Holland, Exelon nbs Powered By Docstoc
					Virtual Plumes Workshop

   Paul Holland, Exelon
    Pat Mulligan, NJDEP
         Workshop Objectives
   Background
   What is Virtual Plumes?
   What are the Benefits?
   What Virtual Plumes is Not!
   Developing Data Sets
   Scenario Development
   Running a Scenario
   Post Exercise Evaluation
What it was like (not so long ago)
           Reams of paper
           Over reliance on controllers
           No onus on players performance
           “Perfect Data” every time!
           Overall negative training and re-
            enforcement
           No opportunity to learn or interpret
            “real” conditions
        What’s Wrong with that?
   Realized there was little training benefit to our
    current process both in the field and in our
    assessment centers
   The meter needle needed to move
   There was a lack of understanding of basic RP
    principals
   The world is not a perfect place (though we play
    like it is)
What would make this better?

         Need to put the player in as
          realistic situation as possible
         Meters need to respond as if the
          plume actually existed
         Put the onus on the player to
          collect the data rather than the
          controller to provide the data
            Virtual Plumes
   Software
     Simulates a radioactive plume released to the
      environment
     Mapping program that connects software to
      hardware
   Hardware
     GPS
     Controller interface via computer
     Simulation Equipment
       Player/Controller Benefits
   Provides real time data to the
    individual using the meter
   Forces the player to really know how
    to use the meters
   Provides a true training opportunity
    and experience
   Re-enforces good RP practices
       Player/Controller Benefits
   Reduces Controller errors
   Allows the evaluator to really observe the
    players performance
   MAKES THE PLAYERS IN THE FIELD
    AND AT THE ASSESSMENT CENTER
    THINK!
             Developer Benefits
   Consistency in Development Process

       One method (tool) to develop scenarios
       One computer used to develop scenarios
       Assumptions and defaults are not varied (at
        least not unintentionally)
       Encrypted Data Files
              Developer Benefits
   Speed
     Planning  sessions are not complicated
     Limited upfront planning required (limited data
      required for development)
     Draft scenarios can be developed in minutes for
      stakeholder review
     Scenarios can be modified “on the fly” during a
      planning session
Developer Benefits
   Reuse existing data
     Release   points
     PIN  sets
     Instrument sets
     Evacuation Sets
            What VP is Not!
   Dose Assessment Model
   Cannot be used in a real emergency
   Not designed to match any particular dose
    assessment model (in fact it is better if it
    does not)
   Will not accurately generate very close in
    dose rates
Baseline Development Data Sets
           Release Points
           Key Distance
           Pin Sets
           Instrument Sets
           Evacuation Areas
Release Points
Key Distance
   THE most important concept for
    developers to understand!



   If you understand Key Distance the
    rest is gravy!
Key Distance
   Key distance is the basis for all
    calculations
   Virtual Plumes uses Gaussian
    distribution
   Key distance is the reference point
    for the calculations
   Determines values for any point in
    space
Key Distance
   Must be greater than 1 mile
   NOT direction specific
   Match key distance to an available
    point in dose assessment model.
   Available stability classes can be
    affected by the chosen key
    distance.
Pin Sets
   Supply fixed survey or reference
    points
   User has the option which pin sets
    are displayed
   Need to associate Pin Sets during
    development
   Pin Data (dose rates and air conc.)
    may be displayed real time
Working with Pin Sets
Instrument Sets
   Equalize variations in instruments
    used by different response groups.
        Samples
     Air
     Sample counting

   All players get the same answer
    regardless of instrument used.
Configure Instrument Sets
Evacuation Area
   Labor Intensive to develop
   Reusable once developed
   Must be associated during
    development
   Can be displayed/removed at any
    point during scenario
Evacuation Areas
                Program Defaults
   For experienced and advanced users Only!
   Many, many options available
   You really need to understand what you are
    actually changing
   Some of the settings have very little
    consequences
    Some settings will significantly change the way
    calculations are performed.
              External Interface
   Allows Virtual Plumes to be a database engine
    for other programs
   Receive data requests and send data through
    TCP/IP interface
   Requires creation of a common command
    structure
   Flexible and easily modified
   Uses last location or Lat/Lon data requests
External Interface
Instrument Interface
   Built in interface for configuring
    Teletrix™ instruments
   Others instruments can access the
    TCP/IP interface
   Don’t need instruments to run the
    scenario
Instrument Interface
Configure GPS Device
   Virtual Plumes has a GPS
    interface for determining field team
    location in real time
   Eliminates the need for the
    controller to manually locate field
    teams on the map
   Reduces controller errors
Configure GPS Device
               Configuring Dosimeters
   Virtual Plumes has an interface that will enable
    real time simulation of an electronic dosimeter
    (not required)
   Not a real dosimeter, electronically tracks dose
    and responds with audible dose and dose rate
    alarms
Configure Dosimeters
Scenario Maintenance
   Three key parameters are needed
    to start the development of a
    scenario
     ReleasePoint
     Plume Path
     How Deposition is Calculated
            Release Point
   Select release point from the drop down list
    available (These are the ones you have
    created)
   Remember that there may be multiple release
    points for any one facility (eg. Elevated,
    ground, turbine building, etc.)
Plume Path
   User defined path – User defines
    where the plume will travel.

   Straight Line Gaussian – Virtual
    Plume calculates the path based
    on user defined meteorological
    conditions
User Defined Plume Path
        Calculating Deposition

   Virtual Plumes is capable of calculating
    deposition from a plume but will not display it on
    the map
   The user can draw deposition areas that can be
    seen on the map and assign predetermined dose
    rates to each one
   Either method will provide data from Virtual
    Plumes through the TCP/IP interface or
    Instrument interface.
Predetermined Deposition
Straight Line Gaussian
    Key Plume Dose Rate

   Value used to initiate indication that a
    release is in progress
   Threshold value where centerline indicator
    turns from green (no release) to red
    (release)
   Does not have any influence on calculation
    of field measurements
   Default values are fine!
Default Instrument Set

        Sets the default instrument set for
         the scenario.
        All instrument sets are available for
         the default setting
        Can be modified by the user when
         starting the scenario or while the
         scenario is running
       Correction Factors
   Used to adjust Plume Dose Rates for
    predetermined distances
   User defines the percentages for whole
    body and thyroid at each distance
   VP uses the calculated value and applies
    the correction factor defined by the user
    (%)
    Correction Factor
Dose Rate




            Distance
Correction Factor
Dimensions
   Used to disable GPS altitude



   Normally not disabled
            Customization
   Allows limited customization by program
    administrators (typically allowed by scenario
    developer)
     GPS   Units
     Instrument Sets
     Pin Sets
     Dosimeters

   Does not allow administrators to change
    scenario data
             Map Overlays
   Allows customization of what is displayed on the
    maps
     Airports
     City and County Names
     Political Boundary Shading
     Highways
   No effect on data calculations
   Set it to your personal preferences then leave it
    alone
          Evacuation areas
   Makes predetermined evacuation zones
    available for display while running the
    scenario
   Previously created by the user
   Feature added mostly for printed maps
            Scenario Data
   Three pieces of data required to create a scenario
     Meteorological
     Radiological
     Timeline

   Specific times and dates for the exercise are not
    required to develop the scenario
   Data is entered in time increments so scenarios
    can be reused many, many times.
Meteorological
Radiological
        Completing the Scenario
   Associate Pin Sets

   Save the scenario

   Calculate the scenario

   Test/Evaluate the Scenario
Evaluation Data Tables
       Scenario Evaluation
   Allows developer to review centerline
    airborne concentrations and dose rates in
    the evaluation mode.
   Scenario is run at an accelerated speed
    during evaluation
   Simultaneously evaluate wind direction
    changes
   Allows developer to capture maps for drill
    manuals.
Printing Scenario Materials
        Printing Options
   Many reports available
   Many options associated with each report
   Output in:
     Print
     Excel
     Word
     Access   Database
   Report outputs can be customized
                 Scenario Security
   Security
     Is   the scenario tamper proof?
             encrypted
        Files

        Unreadable

     Scenario Timeline, meteorological and radiological
      data can only be modified by the drill developer on
      the computer used for development
     Scenario Distribution
   Electronically send the calculated file to
    end users

   Users copy file into their VP scenarios
    directory

   The file is plug and play
          Running the Scenario
   Open the file
   What you need to start
     Scenario  start date and time
     GPS Device (not required)
     Instrument set
     Interface testing (not required)

   Start
   Sit back and relax (if you are using GPS and
    instruments)
Control Panel
      Field Data Tab
   Location

   Meteorological Data

   Radiological Data

   Dosimeter Readings
Field Data Tab
            Additional Data Tabs

   Scenario: general scenario data
   Historical: recall marked data points
   Sample: allows user to change instrument
    sets or sample criteria
   Pins: displays a listing of the available pin
    data
Scenario Data Tab
Historical Data
     Tab
Sample Data
   Tab
Pin Data
  Tab
Pin Data Display Screen
          System Vulnerabilities
   GPS malfunctions: Point and click
   Instrument Interface Malfunction: Controller
    provided data
   Computer Crash: Single Point Failure
     Option 1: Paper backup (very difficult)
     Option 2: Take team out of play
     Option 3: Dispatch a back up computer (if
      practical)
         Scenario Replay
   Two Scenario Replay Modes
     Single   Team Replay
        Immediately   available for debriefing teams
     Multiple   Team Replay
        Needs  to be compiled on a single computer
        for later evaluation
             Scenario Replay
   VP captures all the data calculated based on
    team position throughout the scenario
   Historical record of field team movements and
    data
   Allows training team to evaluate command and
    control functions, sampling plan and data
    collection
   Allows team members to see their relative
    position to the plume
State of NJ Lessons Learned
        Field team members are more confident in their
         abilities to collect and assess radiological data
        Assessment center personnel no longer have an
         unrealistic expectation for “perfect data”.
        What’s close enough?
            Players perspective
            Controllers perspective
        Better questions and experiences shared during
         training sessions
        So many years of negative training, players are
         unwilling to believe real data. Difficult to
         overcome mindsets.
Changes to drill preparation
       Different drill preparation
        processes
       Controllers need additional training
       Licensees need to provide
        scenarios in Virtual Plumes format
       Single point failure if field team
        computer fails (paper backup)

				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:20
posted:8/17/2010
language:English
pages:73