Changes between Version 1 and Version 2 of BluePrintExerciseManagement


Ignore:
Timestamp:
03/20/12 09:22:28 (13 years ago)
Author:
Gavin Treadgold
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • BluePrintExerciseManagement

    v1 v2  
    11== Overview ==
    2 This blueprint is based on the need to an application to allow the management or exercises (or simulations) for training purposes. This is an application that provides the management tools associated with preparing, delivering, and reviewing exercises.
     2This blueprint is based on the need to an application to allow the management or exercises (or simulations) for training purposes. This is an application that provides the management tools associated with preparing, delivering, and reviewing exercises. Some of these requirements have been based on requirements when Sahana Software Foundation products have been tendering for Emergency Management Information System tenders.
    33
    44 * Domain contributors: Gavin Treadgold
    55
    66== Concepts ==
    7 * Exercise Timeline - the fundamental tool of an exercise is a timeline. A timeline generally consists of 'messages' that record:
    8  * DateTime - the date and time the message is due to be communicated to the relevant exercise participants
    9  * From - who the message is 'from', usually it is from Exercise Control, or Exercise Control on behalf of one of the Exercise Participants
     7* Exercise Master Log - the fundamental tool of an exercise is a master log. A master log generally consists of 'message injects' that record:
     8 * Date and Time - the date and time the message is due to be communicated to the relevant exercise participants.
     9 * From - who the inject is 'from', usually it is from Exercise Control, or Exercise Control on behalf of one of the Exercise Participants
     10 * To - who the inject is 'to', usually one or more Exercise Participants. These could be organisations, groups, roles or people.
     11 * Message - the actual message inject that will be sent to the relevant participants.
     12 * Note - a note field that is usually only available to Exercise Control and contains guidance about this inject to those delivering the exercise. Some inject entries may be just notes to Exercise Control to see if certain states or conditions have been reached in the exercise.
     13* Participants Directory - the list of all exercise participants that is generally available to all of the exercise organisers
    1014
    11 === Users ===
     15== Users ==
    1216These are the broad classes of users commonly associated with exercises.
    1317* Exercise Control - a group of people that have full access to the tools to manage exercises. This group is responsible for the development and delivery of the exercise
    14 * Exercise Facilitators/Coordinators - a second group that has read-only access to the exercise information, often a subset that is relevant only to the group that they are overseeing in the exercise.
    15 * Exercise Participants -
     18 * Exercise Facilitators/Coordinators - a second group that has read-only access to the exercise information, often a subset that is relevant only to the group that they are overseeing in the exercise. Facilitators/Coordinators are a subset of Exercise Control.
     19* Exercise Participants - the end users that 'experience' the simulation.
    1620
    17 === Information ===
    18  * Participants Directory - the list of all exercise participants that is generally available to all of the exercise organisers
    19 
    20 
    21  * Integrated with Organisations/Roles/People
     21== Requirements ==
     22A fundamental requirement of delivering an exercise is an internal messaging system that simulates email/messaging.
     23=== Exercise Development ===
     24 * Integrated with Organisations, Groups,  Roles, and People
    2225 * Supports self-registration of participants
    23 
    24 
    25 
    26 == Capabilities ==
    27 === Development Capabilities ===
    28 *
    29 
    30 === Delivery Capabilities ===
    31 *
    32 
    33 === Review Capabilities ===
    34 * Able to package the whole exercise details (organisations, participants, exercise timeline etc) up into a package, and transfer it to another machine
    35 
     26 * Allows Exercise Control members to construct a Master Log and create and view the message injects
     27 * Able to produce a pdf file for each message inject for emailing and/or printing on a message inject template (GT can provide examples)
     28=== Exercise Delivery ===
     29* Able to deliver messages at the time specified in the master log to the specified participants
     30* Able to capture messages between exercise participants
     31* Produce a master log of exercise injects and participants actual messages
     32* Able to package the whole exercise details (organisations, participants, injects and messages etc) up into a package, and transfer it to another machine
     33* Allow participants/exercise control to record actions e.g. that they have undertaken a certain action at that time and record it in the master log
     34=== Exercise Review ===
     35* Able to play through a recorded 'exercise'
     36* Able to filter messages to/from a particular organisation, group, role or person.