High-level requirements

Maintain a list of vehicles in the scope of TraX deployments in the Vehicle Store.
Ability to automate the commissioning and decommissioning of sensors in the partner's platform (cloud and edge)
Capture, process, and present sensor data.
Share sensor data with SKF.

Vehicle information

Ability to provide a one-way sync of the vehicle information to SKF, and a request/reply flow that enables SKF to ask TSP to enrich vehicles with GPS position. See vehicle store integration for implementation instructions.
Vehicles must be qualified using a TSP-supplied vehicle ID and fleet ID. A vehicle is not allowed to change vehicle ID or fleet ID.
The TSP is required to provide accurate information about vehicles, specifically, these vehicle attributes: VIN, vehicle name/description, brand and model, vehicle longitude, and latitude.

Ability to instruct on-vehicle integration solution to start/stop listening to specific TraX sensors (MAC address filtering).

Optional but recommended capabilities:

Ability to determine currently deployed TraX sensors at vehicles managed by the TSP.
Ability to store TraX sensor configuration attributes for (1) mounting position, i.e. axle number, and left/right wheel, (2) sensor identity (MAC address), and (3) the vehicle that the sensor is mounted on.

Ability to pick up Bluetooth broadcasts (no pairing required) based on MAC address.
Ability to store and parse parts of the BLE frame.
Ability to store parts of the BLE frame AS IS (debug data).

Ability to present the state of wheel-end health to end-users.
Ability to send sensor data back to SKF, ideally in the exact format it was transmitted from the TraX sensor. See the sensor data integration for a complete list of mandatory and optional attributes.