What’s New


1. Validation in password for Length and number of characters
We have changed the password validation method for the password for a newly created user. Now the password that is auto generated and shared over email for a newly created user will follow our minimum password requirements.

2. Active Filter Count in Notification Log

 In the notification log table, when a filter was applied there was no way for the user to see this.There has been a change made where in the main menu of the notification log the count of number of filters that have been applied is shown. 

3. The tags with stats email alarms set should also consider NanoAI. 

Previously the notification logic would ignore NanoAI threshold when a “email alarm” existed for the same graph. This has been changed and now Nano AI will also be considered for the alert setting along with the email alarms, so depending on alert logic both email alarm and NanoAI thresholds will be used for same graph.

4. Stable Time waveform and Spectrum During Zoom
Previously on the waveform and spectrum graphs when zoomed in to the graph and a marker was selected, then the graph would automatically reset to the zoomed out state.
This has now been fixed and the graph remains as same zoom level when adding markers and does not reset the zoom level making it easier for users to use this functionality. Also, there was an issue when zooming in after adding a marker that the initial zoom would give a distorted graph and user would have to reset zoom and do it again for it to work, this has also been resolved.

Bugs Fixed

There have been some bug fixes also been made to improve the overall technical depth of the dashboard and improve the backend services. Some more noteworthy issues that have been resolved are seen below.

1. NanoAI update timestamps will not shows as empty points in trend graph anymore
The timestamp when NanoAI was updated would show in the trends graphs as an “empty” data point as no vibration/sound data was available for that point. This logic has been updated to not show time stamps in the trend which only have a updated NanoAI threshold

2. Manual set stage 4 would get reset when updating info through DIY
An issue has been resolved where updating a DIY config would reset any manually set stage 4 thresholds for that component.

3. Issues with Sensor Health Pie chart resolved
Different issues with Sensor Health Pie charts have been resolved to assure accurate info is displayed regardless of what combination of filters is being used.


1.Updated NanoAI Threshold Limits:
We have increased the NanoAI limit to 100% of the sensor’s maximum range to better utilize sensor capabilities and reduce false alarms about sensor saturation. For example, sensors with a 16g range will now have a NanoAI peak threshold set exactly at 16g.

2.Enhanced Sensor Utilization:
This adjustment reduces saturated sensor notifications by approximately 20-30%, as seen in our data analysis, particularly improving performance in applications like those at TATA.

3.Correction to RPM Calculation Method:
We’ve resolved an issue where the RPM calculation for driven components incorrectly switched from multiplying to dividing by the entered speed ratio after April 8th, affecting accuracy; we are ensuring consistent application of the correct formula: Master RPM * ratio = Slave RPM.

4.Enhanced Database Efficiency in Analytics Service:
Optimized the CDM/Analytics service to batch insert CDP processed data, significantly reducing I/O operations and improving overall processing time.

5.Refined Fault Notification Process:
Updated DTM and CDP services to include specific bearing numbers in fault notifications for enhanced tracking and direct dashboard linkage, improving accuracy and response time in fault management.