Purpose
The User Acceptance Test (UAT) protocol aims to ensure that the TraX solution from SKF, integrated with TSP’s solution, meets the end customers’ needs for condition monitoring using the TraX sensor.
Scope
This protocol outlines the MVP Usability plan and protocol for user scenarios relevant to TSPs.
Test Methodology
Overview
Issues identified during testing should be categorized as follows:
- Show Stopper: Prevents the user from completing a critical action, halting the day-to-day work process. Classified as "failed" in the report.
- Major: Prevents the user from completing a critical action, but can be bypassed with a workaround, allowing the user to continue daily work. Classified as "passed conditionally" in the report.
- Minor: Prevents the user from completing a non-critical action, not affecting daily work. Classified as “passed conditionally” in the report.
- Not Applicable (NA): No issue found.
Acceptance Criteria
All requirements and deliverables must be met. If issues are found, the following table defines the maximum allowable number of issues:
| Issue Severity | Maximum number of issues |
| Show stopper | 0 |
| Major | 5 |
| Minor | NA |
If the number of issues found is less than the maximum allowed, each issue must have an open ticket in SKF TraX support and be documented in the report to pass the test.
Note: Each feature can generate a maximum of one issue. For example, if testing feature 3.2.1 across two different companies results in three major issues, they will be counted as one issue.
Requirements
UAT testing should be conducted in the production environment with the actual customer’s fleet. The following requirements must be met to perform UAT testing:
- The customer’s fleet must be properly configured in TSP’s systems (production environment).
- The customer’s fleet must be properly configured in the SKF TraX production environment.
- All necessary credentials for the production environment must be shared with TSP.
- All connectivity tests for the production environment must be successful.
- TSP’s integration solution must be verified as part of the development activity with no show-stoppers found.
- The person performing the tests must have user admin privileges in the Enlight center to add installers and manage access levels.
Test Protocol
| # | User Stories | Steps | Expected results |
|---|---|---|---|
| 1 | Confirmation that the fleet is supported in SKF systems (Optional) |
Go to Enlight Center and check that TSP is selected correctly. If you have access to several TSP select TSP in the upper right corner. Go to the Hierarchy tab and check that the needed fleet is selected in the left upper corner of the page. By default, the fleet to which the user belongs will be shown. In case the user has access to a few fleets it’s necessary to select the proper fleet. |
The fleet should be presented in the Hierarchy of Enlight Center. In case the fleet is not presented contact SKF to establish support for the fleet from the SKF side. |
| 2 |
Addition of installers. Permission management. (only if TSP is in charge of installation) |
In Enlight Center go to the “User Admin” tab and check that installers are presented in the table with “Company Users”. Add an installer by clicking on “Create user”, fill in the details about the installer, and select the fleet that the installer should have access to. For “User Access” part select Hierarchy and TraX. Click save and check with the installer that the invitation was sent. More details on how to add users are here |
Admin User(s) should be able to add installers and add or remove fleets that installers should have access to. |
| 3 | Mounting sensors |
Check that the size of the plate of the TraX sensors is suitable for the vehicle/model. The sizes of the plates are presented here and here;
|
The installer should be able to mount the sensor on a customer’s vehicle. The size of the sensor plate should be suitable for the particular customer's vehicle. |
| 4 | Access to the TraX Mobile application (Production) |
Download and install the TraX mobile application:
Log in to the application using Enlight Center credentials. |
The user should be able to download and log in to the TraX mobile application. |
| 5 | Search for vehicles in the TraX app. |
After Logging in to the TraX application use the search field and find one of the vehicles from the fleet that is configured for TraX use. Use VIN and vehicle name to search for the vehicle, click on the vehicles from the results list, and check the details of the vehicle. Make sure that the vehicle details in the TraX application are the same as in the TSP system. Fill in/Correct additional details like vehicle type or a number of axles. Add new vehicles in TSP’s vehicle store, and check that it’s possible to find a newly added vehicle in SKF’s vehicle store. Click on the vehicle and look at the “Vehicle Overview” page. Check the information there. Continue with 2-3 different vehicles. |
The user should be able to find any vehicle from the fleet that is configured for support in TraX. The user should be able to search with both VIN and vehicle name. It should be possible to find a newly added vehicle. Vehicle details are the same in the TSP system and the TraX mobile application. The “Vehicle Overview” page represents a vehicle with the correct number of axles with their type (driven/non-driven) |
| 6 | Commissioning of a sensor to a vehicle |
Continue the previous use case and for the selected vehicle try to commission a sensor. Before commissioning a sensor, it should be mounted on a vehicle. On the “Vehicle Overview” page check that the wheel where the sensor was just mounted is empty. Press on the “+” sign and activate the sensor using a magnet. Click “Search for sensor” and review the results of the search. From the search results select the sensor with the same Mac address that is written on the sensor and click “Add sensor”. Click “Close” and check that the sensor for a specific axle and side is added. Check if the sensor was added to TSP systems. Repeat for 3-4 different sensors for different vehicles. |
The user should be able to mount and activate the sensor with the magnet. The “Vehicle Overview” page should represent all sensors that were commissioned for a specific vehicle. The TraX Application should be able to find an activated sensor and add it to the systems. The commissioned sensor should appear in TSP’s systems. |
| 7 | Updating the firmware of the sensor (Recommended when update is available) |
Once the sensor is activated and commissioned it’s possible to check information about the sensor by clicking on it on the “Vehicle Overview” page. By clicking on the page “Update to XXXXX” near the firmware version it's possible to update the firmware version. Also, during the commissioning or resetting of a sensor firmware update will be suggested if new firmware is available. A firmware update can take up to a few minutes. After the firmware update follow the instructions in the TraX mobile application and reactivate the sensor with the magnet. |
The firmware of a sensor is successfully updated. Sensor with updated firmware is commissioned and continues to send data to the gateway. |
| 8 | Getting data from the sensor |
The commissioned sensor transmits two different types of data that should be captured by an onboard gateway: temperature data and vibration data. It’s necessary to check both types of data. Temperature data: Temperature data is transmitted by the sensor every 30 minutes. Check that the sensor transmits the current temperature and max-min temperatures Vibration data: Vibration data will be transmitted only when the vehicle is moving at a speed of 40 mph or more. Check that when the vehicle is moving vibration data is transmitted by commissioned sensors. Check that if a vehicle is moving at a speed less than 40 mph vibration data will not be sent by the sensor. All measurements (temperature and vibrational data) should appear in TSP’s systems. |
Information about temperature and vibrational data should be sent by the sensor, captured by an onboard gateway, and sent to the TSP’s cloud and other systems. Vibrational data should be sent only when the vehicle is moving. Temperature data should be transmitted regardless vehicle is moving or not. |
| 9 | Notification about the faults (if found) |
In case a vehicle has problems with bearings this information will also be sent by the sensor. Except for bearing issues, the sensor will also send information about battery status, incorrect mounting, and internal failures. In the TSP’s system find a sensor that represents one of the possible failures. Check that the LED indication on the failed sensor is RED. |
The user should be notified through TSP’s systems about any faults that the sensor is capable of detecting. The sensor itself should change the LED light color in case a fault is detected. |
| 10 | Resetting sensor (in case sensor with wheel-end failure) |
Find a sensor that is reporting bearing failure. After maintenance when the bearing is replaced reset the sensor. To do this in the TraX mobile application find a vehicle where the bearing was changed, and open the “Vehicle Overview page” Click on the sensor that indicates “Bearing fault” and click “Reset sensor”. Put the magnet in the targeted place on the sensor. When the light of the sensor turns green remove the magnet and follow the instruction in the TraX app. |
The sensor that detected a bearing fault should be properly reset and continue to measure all necessary parameters. |
| 11 | Replacing/Removing the sensor |
Replacement of the sensor is needed when the sensor has some internal faults or the battery level is low. To do this in the TraX mobile application click on the sensor that was commissioned to one of the axles and click “Replace sensor”. Follow the instructions in the TraX Application. To remove the sensor in the TraX mobile application click on |
The sensor should be replaced or removed |
Resource & Environment Needs
- Establish support for the new fleet in SKF.
- Ensure active production Enlight accounts for installers.
- Have a fully prepared TSP integration solution (both software and hardware).
- Access to customer vehicles.
- Use the production version of the TraX mobile application.
- Access to TraX sensors.
- Equip vehicles with TSP equipment, eg. gateways.
Comments
0 comments
Article is closed for comments.