Events

The Events module allows you to get notifications on important activities that are taking place with your vehicles or review a history of these activities. What activities are to be treated as Events is customizable.

The Events module is accessed by clicking the Events button on Ecofleet bar.

events-1-en

 

Purposes of the Events module

  • Allows you to get real-time notifications of important activites with vehicles in your organization.
  • You can also review the history of events to draw conclusions about the trends.
 

Main view in the Events module

The right side of the screen displays the map. The left side of the screen displays a list of events for the selected period.

events-2-en

When you select an event from the list, an arrow on the map points out the location of the event and the following information is displayed about an event in in the list:

  • Rule. Type of the condition.
  • Event. The circumstances with which the Condition was met. For example, if the rule is “Voltage < 12.9 volts”, this line might display “Voltage = 11.4 volts”.
  • Area. The name of the area in relation to which the event activated.
  • Time. The time when the event took place.
  • Duration. The length of time the event was active.

Not all information is relevant or is displayed in case of every event.

 

Creating and editing events

New events may be created, and existing events edited, under the Settings > Events tab.

Click Add to create a new event. Alternatively, select an existing event. The list is searchable with the search box above the list.

events-settings-list

Click Delete to remove a selected event. Please note that there may be events that cannot edit or delete due to a lack of user privileges.

Events can be either active or inactive. Active events have the checkbox before their names checked. You can temporarily disable an event by unchecking the checkbox.

The following is displayed about an event:

events-settings-rulecreation1

 

Name

Each rule has a name. When naming an event it is recommended to choose a brief and descriptive name, for example “Speeding” or “Lengthy stop”.

 

Condition

Each rule is linked to a particular condition, a circumstance like vehicle stopping or battery voltage changing. The condition chosen is the key element of an event. The following conditions are available:

  • Entering area.

  • Leaving area.

  • Stopping [length of stop can be specified]

  • Starting to move

  • Speed [can be specified to be either smaller or greater than a chosen speed, also duration can be specified]

  • Moving while ignition off

  • Turning ignition on

  • Turning ignition off

  • Voltage [can be specified to be either smaller or greater than a chosen voltage, also duration can be specified]

  • Din turned on [Digital input # can be chosen]

  • Din turned off [Digital input # can be chosen]

  • Status on [Number of status can be chosen]

  • Status off [Number of status can be chosen]

  • Temperature [Can specify any or all sensors, choose temperature as smaller or larger than target, also can specify duration]

  • Vehicle hasn't sent any data [Can specify duration]

  • GPS with status false [Can specify duration]

  • Fuel decreasing

  • Event with code [Event code can be specified]

  • Device SMS contains [Can specify SMS contents]

  • Device with no MPS [Duration can be specified]

  • Track visit [Interval, tolerance and target number of occurrences can be specified]

    When the rule has track visit set to all vehicles the event only appears once - when none of the vehicles has made a visit. In that case random vehicle is displayed as an event creator.

  • Trip end [Duration can be specified]

  • GH ButtonID [Number can be specified]
 

Restrictions

events-settings-rulecreation2

By default the condition applies to all vehicles in all locations at all times. There are three ways to restrict the condition: by vehicle, location and time.

Vehicles

The condition may apply to every vehicle in the organization (default) or to a subselection. Options:

  • All vehicles. The rule is applied to all vehicles in the organization.

  • Vehicles by groups. Allows you to choose vehicle group(s) from selection.

  • Individual vehicles. Allows you to choose from a list of all vehicles in the organization. Multiple individual vehicles may be chosen.

Location

The condition may apply everywhere (default) or only in particular areas (as defined in the Areas module). Options:

  • Everywhere. Applies irrelevant of location.

  • Inside any area. Applies inside any area that has been defined in the organization.

  • Inside area group. Select an area group. The rule applies if the vehicle is inside any area within the group.

  • Inside individual areas. Select individual areas from a list. The rule applies if the vehicle is inside any area selected.

  • Outside of area group. Select an area group. The rule applies if the vehicle is outside every area of the area group.

  • Outside of individual areas. Select individual areas from a list. The rule applies if the vehicle is outside all of the areas selected.

Time

The Condition may apply at all times (default) or at selected times, for example at working hours.

Options:

  • Always. The rule applies at all times.

  • At working time. The rule applies during working time.

  • Outside of working time. The rule applies at any time that is not inside working time.

  • At specified time. You can specify weekdays and time ranges at which the rule applies.

What the organization considers working time can be defined under Settings > Organization Settings. Alternatively, working time for an individual vehicle can be defined under Settings > Vehicles > Working time.

 

Actions taken in case of an event

The other half of an event, besides the elements, is the action. Actions define what happens if the conditions are met. If no action has been chosen, Ecofleet will still show the event in the events list. The following actions are possible:

  • Ecofleet notification. If the event occurs, all users logged in will see a grey pop-up box with the name of the event and the concerned vehicle.

  • Sound signal. If the event occurs, all users logged in will hear a sound signal

  • E-mail. An e-mail will be sent to the specified user. Multiple users can be specified, the e-mail addresses should then be separated by commas. The e-mail sent will have the following content:

    • Event name: Name of the event as entered under Settings > Events.
    • Data: Numerical value of the event.
    • Started: 10.02.2011 16:27:16 The start of the event.
    • Vehicle: 123ABC. Info of the vehicle.
    • Place(s): Location where the event took place.
  • SMS. An SMS will be sent to the specified user. The country code should be entered with the phone number (eg in case of Estonia + 372...) Multiple users can be specified, the phone numbers should then be separated by commas.

  • SMS with template. An SMS will be sent to the specified user with detailed description of the event and the vehicle involved. An SMS can contain following parameters that will be replaced with equivalent information for the user:

{VAR:vehicleName} - name of the vehicle

{VAR:vehiclePlate} - plate number of the vehicle

{VAR:vehicleMake} - make of the vehicle

{VAR:vehicleModel} - model of the vehicle

{VAR:vehicleId} - ID of the vehicle

{VAR:vehicleExternalId} - external ID of the vehicle

{VAR:vehicleGroup} - group of the vehicle

{VAR:eventName} - name of the event

{VAR:eventAddress} - address of the event

{VAR:eventDateTime} - date and time of the event (yyyy-mm-dd hh:mm:ss)

{VAR:eventLatitude} - latitude of the event

{VAR:eventLongitude} - longitude of the event

{VAR:eventGMapsLink} - google maps link of the event

Example.

SMS sent to user:

Your car {VAR:vehicleName} with plate number {VAR:vehiclePlate} is stopping at {VAR:eventAddress}. Name of the event is {VAR:eventName}.

SMS recieved by user:

Your car Company car 3 with plate number 333GGG is stopping at Pikk 34, Tartu, Estonia. Name of the event is Vehicle hasn't sent any data.

You can also add vehicle custom data form fields to your message: {VAR:filed name} - will be replaced with the value of the field.

Please see also the chapter "Vehicle custom data": https://manuals.ecofleet.ee/en/#Vehiclecustomdata

  • HTTP POST. A POST request is performed to the specified HTTP address. This makes it possible for the organization's own information systems to utilize the event data sent by SeeMe.

events-sms-template-eng

 

Examples of Events

 

Example 1: Speeding

A client is concerned with the public image of trucks marked with its logo. News articles on a number of speeding incidents have been appeared in print.

An event is set up as follows:

  1. Condition: Speed. Speed is set to "> 90 km/h". No duration is set.
  2. Restrictions: No restrictions are applied. If there were vehicles for whom the considerations didn't apply -- for example if the vehicles were without logos -- such vehicles could be excluded either individually or as a group.
  3. Actions: A SMS notification is set up. That way the client's employees can be informed about the event while away from computer.

This event allows the client to take timely measures whenever a driver is speeding, for example calling the driver or adopting pay incentives.

 

Example 2: Geofencing

A client whose vehicles operate machinery on certain known routes wants to be notified whenever a vehicle leaves the route.

Route-shaped areas are defined with the help of Distance Calculator on the necessary routes as described in Areas chapter. All of them are defined to belong to the area group "Mandatory Routes".

An event is set up as follows:

  1. Condition: Leaving area.
  2. Restrictions: Location - Outside of area group - Mandatory Routes
  3. Actions: A SeeMe notification and sound signal will be sufficient, assuming there is a dispatch officer on duty.

Setting up this event allows the client to get instant notifications whenever a vehicle veers off the planned route.

 

Example 3: Ignition on at weekends

A client wants to be informed when one of his freight trucks has ignition switched on outside of working times.

An event is set up as follows:

  1. Condition: Turning ignition on.
  2. Restrictions: Time - Outside of working time. (What is considered working time, can be configured in Settings > Organization settings.)
  3. Actions: An e-mail can be sent to the client's inbox, to be read whenever she gets around to reviewing incoming e-mail. This way there is no pressure to deal with the issue outside working hours.