Overview

What are Sensors

Use the Sensors module to collect all the sensor data in a non-aggregated way from the communication units. The Sensors module provides accurate sensor data, which is used by other modules according to the requirements. By delivering data in a non-aggregated way, all the endpoints of the module return data points using UTC date time for all the date time properties.

Sensor data is the output of a device that detects and responds to some input from the physical environment. The output may provide information to an end user, as input to another system, or to guide a process. In SCALAR, a sensor collects the data continuously and thus provides time series data. The time series data is collected at different times and almost always includes a timestamp. In some cases, sensor data is used for historical reporting. The Sensors module provides raw sensor data to customers and/or integrators in the form of feed or bulk.

Why use Sensors

Purpose I: Retrieve sensors data

SCALAR enables you to retrieve the sensor data for any asset and communication unit. Sensor data is collected from multiple sources such as the tpms and ebs, from where we collect tyre pressure, speed, temperature, and power or the reefer from where we collect logger temperatures, set points, and other useful information. Also, details related to an asset such, as latitude, longitude, odometer, axle load, and fuel level, are retrieved. It allows to store any signals received from the fleet. All the real-time data is collected and stored for later use.

Purpose II: Retrieve sensors data for a particular asset

SCALAR allows you to retrieve a list of sensors data for a particular asset ID with all the required details such as axle load, ebs, latitude, and longitude.

Purpose III: Retrieve sensor IDs list

SCALAR allows you to retrieve a list of sensor IDs available for an endpoint. It retrieves all the sensor IDs with their types and descriptions.

Use Cases

Use case I: Generate reports

• Collect raw sensor data and aggregate to generate reports for multiple uses, such as cost and unnecessary journey reduction, reduction of CO2 emissions, optimize fleet maintenance.
• Fleet reporting helps in your fleet's performance analysis. With this information, you can improve efficiency, productivity, and reduce costs to maximize profitability.
• Various reports can be generated by aggregating the raw sensor data such as distance travelled per asset or driver, fuel consumption per asset or driver, average fuel cost per mile or km, the average time taken to complete a trip or job, tyre pressure over time and during driving, loading, unloading.

Use case II: Dashboard and metrics

• Sensor data can be collected for date-time intervals in the past (history endpoint) and displayed using diagrams, gauges, and more to provide the customer with valuable trends about the data.
• Data about different sensors can be presented and compared among each other to discover patterns, anomalies, and get the specific asset usage. For example, you can create a diagram by comparing the speed of the asset with the tyre temperature.
• Also, you can monitor the whole fleet or specific assets across different scenarios, monitor asset usage across time, and optimize fleet usage.

Use case III: Data analysis

• Data can be collected using the feed endpoint and stored in a data lake for further analysis using classical techniques but also ML algorithms.
• Identify the important metrics for the business, define KPIs (Key Performance Indicators) over time and measure by aggregating different sensor data from the data lake.
• Generate smart reports and notifications with useful trends to ensure the fleet's save operation and optimize its use.

Use case IV: Asset insights

• The last value endpoint provides valuable real-time insights about assets such as position, status, speed, and display sensor values in a map or dashboard.