Working principles of events and rules

1. The user creates a rule. If the rule is saved and activated, SeeMe will start analysing the incoming data.
2. If SeeMe identifies a piece of information in the incoming data that matches the definition in the rule, it will be called an event and the following will occur:
   1. This event will be added to the list of events (in the events module)
   2. The procedure linked to the event will be carried out. 

Adding an event rule

To set up an event rule, the administrator user should go to Settings > Events. The list on the left-hand side will display all the event rules that have been created in the respective organisation. If the description  of the event is greyed out and the box next to it has not been ticked then the event rule is currently inactive. Events in black and with boxes ticked are active and currently valid.

To add an event rule, click Add new above the list of events.

Components of events and rules

1. Name
   All events must have a simple description. For instance, Speeding or Stopping for too long are good descriptions of rules.
2. Condition(s)
   The user must select the most important component of the event rule – a parameter or a set of parameters to be monitored by SeeMe. The following choices and additional parameters are available:
   1. Entering area
   2. Leaving area
   3. Stopping time
      (there is an option to specify the duration)
   4. Starting to move
   5. Speed
      (there is an option to specify the speed limit and the duration in terms of time and distance travelled)
   6. Moving while the ignition is turned off
   7. Turning ignition on
   8. Turning ignition off
   9. Voltage
      (there is an option to specify the voltage limit and the duration of the respective voltage level in terms of time and the distance travelled)
   10.  There are an additional 5–6 conditions that can be used in specific instances.
3. Restrictions
   1. Vehicle(s)
      This allows the user to specify which vehicles are covered by a particular event rule. The following choices are available:
      1. All vehicles
         The rule will apply to all vehicles. Any vehicles added subsequently will be automatically covered by the rule.
      2. Vehicles by region and/or type
         The rule will apply to vehicles selected on the basis of a combination of region and vehicle type. If the parameters of a vehicle are changed, so as they match a combination defined in the event rule, the rule will automatically apply to this vehicle as well.
      3. Individual vehicles
         The rule will apply only to individually selected vehicles, regardless of any other parameters.
   2. Location
      This allows the user to specify which vehicles are covered by a particular event rule, based on the location of the vehicle. The following choices are available:
      1. Everywhere
         The scope of the rule is not limited by location and  so it will apply everywhere.
      2. Inside any area
         The rule will apply within areas defined by the users of the organisation.
      3. Inside a group of areas
         The rule will apply within a group of areas. Any areas added to the respective group will be automatically covered by the rule.
      4. Inside individual areas
         The rule will only apply within individually selected areas.
      5. Outside a group of areas
         The rule will apply outside the areas contained within the selected group.
      6. Outside individual areas
         The rule will apply outside individually selected areas.
   3. Time
      This allows the user to define the time when the event rule will apply to vehicles. The following choices are available: 
      1. Always
         The application of the rule is not limited by time; it will apply always.
      2. During working time
         The rule will apply to vehicles only while they are being used within working time.
      3. Outside working time
         The rule will apply to vehicles only while they are being used outside working time.
      4. At a specific time
         This allows the user to specify the exact time when you the respective rule is to be applied.
   4. Actions
      When an event occurs, it is automatically added to the list of events module, but it is also possible to perform several different actions. The following choices are available:
      1. SeeMe notification
         At the moment an event occurs, a notification window – displaying the description of the vehicle and the event – will pop up on the screens of all users who are currently logged in.
      2. SeeMe sound signal
         At the moment an event occurs, all users who are currently logged in will be notified by a sound signal.
      3. E-mail
         At the moment an event occurs, previously specified users will be sent an e-mail. This e-mail can be sent to several addresses at the same time; each address must be separated by a comma. A sample e-mail would look like this:
         
         

         Event name: Ignition of the vehicle in the parking area – name of the event rule
         Data: 1 – the value of the parameter triggering the event (here, the ignition value has changed from 0 to 1)
         Started: 10.02.2011 16:27:16 – the exact moment that the event occurred
         Vehicle: 123ABC – the vehicle linked to the event
         Place(s): Parking lot – the location linked to the event

          
      4. SMS
         At the moment an event occurs, an SMS (with contents similar to those in the e-mail) will be sent to previously specified numbers. This can also be sent to several numbers at the same time; each number must be separated by a comma. Note that the phone numbers of the recipients must have the full country calling code in front of them (e.g. in Estonia this would be +372 xxxxxx).
         
         
         If necessary, it is possible to carry out one more action (HTTP POST):
      5. HTTP POST
         At the moment an event occurs, a HTTP POST request will be made to a previously specified web address. This allows the client organisations to perform certain other actions in their information systems at the moment the event occurs.