Overview

What are Sensors

Use the Sensors module to collect all 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 provides time-series data. This data is collected at different times and includes a timestamp. Sensor data is used for historical reporting, real-time monitoring, and decision-making.
The Sensors module integrates with teams and activities management to streamline operational efficiency. For example, sensor data can now inform activity definitions and team assignments for integrators, ensuring a more connected data ecosystem.

Why use Sensors

Purpose I: Retrieve sensors data

SCALAR enables retrieval of sensor data for any asset and communication unit. Data from multiple sources—such as TPMS and EBS—is collected for parameters like tire pressure, speed, temperature, and power. Similarly, reefer data such as logger temperatures and set points are also captured. Key asset details like latitude, longitude, odometer, axle load, and fuel level are retrieved and stored for both real-time and historical analysis.

Purpose II: Retrieve sensors data for a particular asset

SCALAR allows the retrieval of detailed sensor data for a specific asset ID, including axle load, EBS, latitude, and longitude.

Purpose III: Retrieve sensor IDs list

SCALAR provides a list of sensor IDs for an endpoint, along with their types and descriptions, ensuring seamless integration into activities and team operations.

Integration with Activities and Teams

The Sensors module integrates closely with the Activity Definition Manager and Teams for Integrators to enable advanced functionality:

• Activity Definition Integration:
  • Sensor data supports activity tracking by providing real-time and historical data on driver activities, such as loading, unloading, and refueling. This integration allows dispatchers to monitor driver actions with accurate sensor-based timestamps, positions, and additional metrics.
  • Activity reminders and corrections are supported by utilizing sensor data, ensuring all driver activities are properly logged and adjusted when necessary.
• Teams for Integrators Integration:
  • The Sensors module respects team assignments by restricting sensor data access based on team allocations. Integrators can only access data for assets assigned to their teams, ensuring data privacy and relevance.
  • The Teams Manager facilitates managing the relationship between sensors, assets, users, and integrators, leveraging the DataHub API to enforce access restrictions and ensure appropriate data visibility.

Use Cases

Use case I: Generate reports

Aggregate raw sensor data to generate insightful reports for optimizing fleet management. These reports include:

• Distance traveled per asset or driver
• Fuel consumption and cost analysis
• Trip duration and job completion times
• Tire pressure monitoring over time

Use case II: Dashboard and metrics

Display sensor data visually for historical and real-time trends. Diagrams, gauges, and maps provide actionable insights for:

• Comparing data points, such as speed versus tire temperature
• Monitoring fleet or specific asset performance
• Optimizing fleet usage

Use case III: Data analysis

Store sensor data in a data lake for advanced analysis using classical methods or machine learning algorithms. Define KPIs and measure business performance by aggregating and analyzing sensor data over time.

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.

Use Case IV: Asset Insights

Real-time sensor insights, such as position, status, and speed, are available through endpoints. These insights are invaluable for dashboards, maps, and fleet monitoring.
Benefits of Integration

• Enhanced Transparency: Sensor data combined with activity logs ensures full visibility into driver and asset operations.
• Optimized Access Control: Integration with Teams for Integrators ensures data is accessible only to relevant stakeholders, enhancing security and operational relevance.
• Improved Operational Efficiency: Data-driven insights from sensors support decision-making, reduce inefficiencies, and optimize fleet usage.

Conclusion

The Sensors module’s integration with the Activity Definition Manager and Teams for Integrators strengthens its utility, making it a cornerstone for efficient fleet management and data-driven operations. By bridging sensor data with activity and team management, SCALAR delivers an unparalleled level of operational intelligence.