Data collecting

FidTrace is collecting and monitoring data sent by data collecting devices with mobile connection to Internet and to display received data and alerts in most user-friendly form. 
The user may define custom features of objects (e.g. car, fuel tank, diesel-generator etc) being monitored via data of appropriate sensors attached to this object. The geocoordinates for stationary objects are related to settings, for moving objects – to data.

Sensors

Information is coming to data server via communication channels from Devices with sensors connected. Each data packet related to a Device and its Sensors is received and recorded in the Database with its time/date stamp. The sensors (or, more precisely, sensor data) may be grouped into four classess according the nature of information provided:

• Continuous sensors (fuel level, temperature, voltage, power etc.)
• Logical sensors (tamper, door, ignition, switch, alarm, button etc.)
• Virtual sensors (processing of “physical” sensor data)
• UID (person, car etc., related to access control)
• Geocoordinates of moving object.

Data from continuous sensors are converted to physical units via Calibration Tables. Virtual sensors may be defined and used e.g. for calculating level deviation, average level of few sensors, power dispersion etc. For each of these sensors the users can define several thresholds and alerts as well as appropriate actions like e-mail, SMS, voice call etc. in order to provide prompt reaction to any situation.
Sensor groups may be predefined by the users in order to simplify the process of prompt selection of sensors and objects in order to watch only important information (like the well known Favorite concept in Windows).

Events

Events are defined by the user. For logical sensor it is just state nickname (e.g. Alarm when Tamper is ON), for continuous sensor an event start/end occurs when the value or it's derivayive crosses a predefined threshold (e.g. Critically Low Level for Fuel Sensor or Critically Down for virtual FuelChange sensor). There is also a set of Hardware events related to Devices and Sensors - like SensorFailure or MainPowerAlarm events. Severity level and an Alert Responce procedure are assigned to each event.
Event window shows all pending events, Statistical reports may be generated about all Events that provide full information about the Objects.

OrgUnits

The objects in an Enterprise normally are incorporated into a geographically distributed administrative structure that in FidTrace may be viewed as a tree with several levels (orgunits) that ends up with Objects and sensors.

Operators

Users are allowed only to watch information related to the Enterprise as real-time data, reports, alerts. Their access rights are limited by Administrators of this Enterrprise. A Transaction Journal allows to view all important User & Administrator actions.

Table and Map monitoring

These two sections provide pending information about sensors that are selected in the object tree. This info is represented in a form of a table or a map with object icons. The colour of table raw or object icon reflects the state of sensor/object.

Statistical reports

Users may select the time/date period and get a chart for selected sensor values in this period of time. Another kind of reports similar to well known Excel Pivot Tables is related to events and logical sensor states. Users have many options of getting statistics across sensors and objects as well as an option to drill down the report in order to see each particular event.

 Report Templates

The users may save frequently used report templates under appropriate names (like Favorites in Windows). These templates will be available as icons below the Object tree that will carry selected sensors/objects, time interval, fields and settings. It is also possible to create templates that will be public, i.e. can be seen and used by other users.