Architecture

Roles and Concepts

• Fleet - A fleet owns or rents vehicles. TSPs equip vehicles with devices that enable remote telemetry.
• Telematics Service Provider (TSP) - TSPs are partners of SKF that offer telematic-based services to fleets such as vehicle health monitoring and location tracking.
• Installer - Installers use the TraX mobile app to commission or decommission sensors. This role can be filled by the fleet, the partner, or third-party companies such as repair shops or OEMs.

Technical Architecture

Provided by the TSP

• TSP platform - The TSP is expected to have an IoT platform that includes a central platform and remote computing capabilities on each edge (i.e., vehicle). Each edge is assumed to have a Bluetooth receiver to capture sensor data broadcasts from the TraX sensor, along with processing and remote connectivity capabilities to send the sensor data to the TSP’s central platform for analysis.
• TraX Client - A solution that implements support for the three integrations in TraX: Vehicle Store Integration, Sensor Data Integration, and Sensor Data Integration. 
• Other Components - The TSP usually has components for alarm detection, notification, and presentation of sensor data.

Provided by SKF

• TraX Sensor - The TraX WEM-200/32 is a battery-powered, wireless sensor that can be mounted on a wheel. It monitors the condition of the bearing and measures temperature. The data it collects is sent via Bluetooth Low Energy (BLE) as advertisement frames. The expected behavior of the sensors is detailed in the TraX - WEM200 - Technical Specification Connected document. The sensor firmware can be flashed to suit different use cases. For example, the stable firmware is suitable for production use, whereas different firmware that produced bearing faults, or WEM faults are useful during the implementation phase.
• TraX Mobile App - The app models real-world vehicles designated for TraX deployment. It allows users to commission (add) or decommission (remove) sensors on the vehicle. The app is available for both iOS and Android platforms.
• Partner APIs - The integration architecture features a web API and queues for efficient real-time processing. The web API offers extensive application integration capabilities, while the queue API is restricted to specific events, such as "sensor configuration changed." All connections are initiated by the TSP.
• SKF IoT Platform - TraX is built on SKF’s IoT platform, SKF Enlight Centre. This web-based software facilitates the collection and analysis of machine data, providing insights and actions to improve customer efficiency and reliability. While TraX benefits from the device management, vehicle topology, user management, and access control capabilities of SKF Enlight Centre, only appointed user administrators are expected to use Enlight Centre to provision users and grant them access to vehicles. The component responsible for housing the vehicle topology is called Enlight Hierarchy.
• Vehicle Store - The Vehicle Store allows TSPs to make vehicles searchable in the TraX mobile app. Vehicles must be added to the SKF platform using the TraX mobile apps before sensors can be commissioned. Vehicles are described using names (or titles/descriptions), VINs, and other information. Manually providing this information can be time-consuming and prone to errors, leading to data quality issues. The Vehicle Store acts as a staging table where TSPs can maintain a list of vehicles that become searchable from the TraX mobile app. Uploading a vehicle to the TraX vehicle store does not automatically add it to the SKF platform; it only makes it searchable in the app. Implementation instructions for maintaining a list of vehicles in the Vehicle Store are provided in the Vehicle Store Integration. While SKF provides the TraX vehicle store service, it is the TSP’s responsibility to ensure the vehicle definitions are populated and kept up-to-date.