User guide

ALEOS 4.2.3 User Guide
134 20080616
Figure 10-1: Events Reporting Concept
The procedure of how Events Reporting works is described below:
1. The user configures the events and actions.
2. After deployment, the device begins measuring a physical input.
3. The measurement is compared to the user-configured threshold or state
change. If there is no change, then another measurement is performed. If a
state change (or threshold crossing) occurs, then the flow moves to step 4.
4. The Action associated with the Event. In this step, a report may be generated
or some other activity performed. Afterwards, the flow returns to step 1.
Additional Behavior and Features
Events/Actions are not one shot activities. After an Action is performed, the Event
is still active and will trigger the next time the state change or threshold crossing
occurs.
A single Event may activate one or more Actions. For example, if RSSI is below
threshold, the user can turn off data services (Action 1) and send an SMS
message (Action 2).
A single Action may be activated by one or more Events. For example, if user
speed (in a vehicle) is above a threshold or if the vehicle heading changes, either
Event can perform the same action.
After defining an Event, always select the Apply button to save these definitions
and apply them to an Action.
Selecting the Delete button on the Events Reporting tab will delete all current
Event and Action data.
3) Threshold
Exceeded or
State Change?
1) User Configuration of
Events And Actions
2) Measure
Physical Input
One of the following : RSSI, Digital Input ,
Speed , Heading , etc.
Physical Input
4) Perform Activity
Send Report , change digital
signal, turn off services, etc
Event
Action
Y
N