New Features
Insights: Minimum duration for exceedance events (22 Oct)
We’ve extended the flexibility of Insights Event Rules with a new Minimum Duration (s) setting.
Previously, events triggered as soon as a single data point exceeded a threshold. Now, you can define how long that threshold must be exceeded before the event activates — from 1 second (default) up to 600 seconds.
All existing and new rules will automatically include this setting, defaulting to 1 second — except Peak G-Force, which remains at 0 seconds since those events are already processed in Spider X.
Why this matters:
This update helps filter out short, noisy spikes to reduce false positives and makes event definitions much more accurate — especially for operational or engine exceedance events that require a sustained condition to be valid.
Where to find it:
When editing an Event Rule, you’ll now see a Minimum Duration (s) field beneath your threshold settings.
Bug Fixes and Minor Improvements
Flying page:
- Aircraft list is now narrower on PC's with horizontal resolution under 1600 pixels, and on mobile displays. This helps balance screen real-estate with the map. (3rd Oct)
Integrations:
- Added the ability to transfer bluetooth Tags (1st Oct)
Invoices:
- Invoice PDF's now include a link to our payment provider for customers that haven't registered a payment card (15th Oct)
- Invoice PDF's updated to Vellox Group Fleet Manager branding. Invoices are still issued by Spider Tracks Limited (4th Nov)
Comments
0 comments
Article is closed for comments.