Events

Events are meant to provide dynamic aspects to the simulation. They are used to execute activities.

Types of events

Currently the following types of events will be modelled:

• Incidents (see (https://github.com/mapto/sprks/tree/master/static/incidents))
  • system-initiated, incidents, for examples check demonstrator-1july branch:
  • static/incidents/infrequent_use.json; static/incidents/eternal.json
  • for more on incidents, see the corresponding section in Realtime-UX
• Interventions - e.g. incentives, training/awareness
  • user-initiated - interventions, e.g. staff awareness campaign, security video tutorials, one-day conference. These will also be specified statically and used as "boosters"
• System events that drive when certain features (i.e. score, incident, feedback graphs) are disclosed to the user

Events as Modifiers

Currently we will use a simple model of events. Each event will be applied on a risk/cost combination and will change them. Compare this to modifier cards as they are used in Munchkin (e.g. http://dicegamers.com/files/munchkin_cards.jpg) when each card increases or decreases player properties (level, strength, etc)

Could be implemented by adding a filter/decorate to the simulation. The way it should work should be that it takes the estimated values and adjusts them according to the event.