The Throughput Score Report is specifically useful for troubleshooting potential connectivity issues. This article shows how to utilise the Throughput Score report.
The Throughput Score will give you the number of packets of data that should have been received over a certain timeframe, compared with the number of packets of data that were received over this timeframe.
The Benefit of the Throughput Score Report:
- The Throughput Score report is a valuable tool for troubleshooting connectivity issues with a sensor. By checking if the sensor has previously recorded data and analysing the quality of its connectivity during that time, you can identify whether the problem is due to the sensor's location (such as network interference) or the type of asset being monitored (e.g., metal enclosure acting as a Faraday cage and in which case an external antenna may be required). This information is crucial in pinpointing the root cause of the issue and finding a solution.
Learn More about Troubleshooting Network Connectivity issues.
To effectively use the Throughput Score report, it is recommended to first check the Communication Alert report. This will help confirm the exact day when the sensor stopped sending data to the platform. After identifying that day, go back one day and then analyse the Throughput Score for usually 30 days leading up to it (you can do any number of days prior to the day the sensor stopped communicating. This process combined with images of where the asset is located (environment) and how the sensor is installed will provide valuable insights into the connectivity issues and help determine whether they are related to the sensor's location or the type of asset being monitored.
- Log into your Superfy Account
- Click on the 'Hamburger' Menu located on the top left-hand side of the screen
- Select Reports from the listed menu
Alternatively, click on the 
icon located on the right-hand panel of the Map View
- Scroll down to and select Throughput Score from the list of report menus
Within this report, users can filter by;
- Zones
- Zone Groups
- Asset Tags
- Asset Types
- Date/Time
- Assets
- Sensors
Click on the Submit Filter button when using any of the above filters.
For more meaningful and valuable insights, it is highly recommended to filter the data by selecting the specific Asset that is no longer communicating and a Date Range (excluding the day the sensor went offline). This will provide a clearer understanding of the connectivity issues and help in finding the root cause of the problem.
On the Result table, you are presented with the following information:
- Asset
- Zone
- Connectivity Type
- Number of Packets Received
- Number of Packet Should Have Received
- Throughput Score
If the Number of Packets Received is much lower than the Number of Packets Should Have Received, or if the Throughput Score is below 90% (as highlighted in above image), it typically suggests that the sensor is experiencing connectivity issues. This indicates that further investigation is needed to determine if the problem is related to the environment, asset, or sensor itself.