Alert Strategy Configuration: Unified Management by Account, Group, or Device
Feature Overview
Alert strategies define what counts as an exception and how the platform should notify users after the trigger. The platform usually supports strategy settings at different levels:
- Account level: the global default strategy
- Group level: rules that override or supplement one specific group
- Device level: finer rules for an individual device
You will usually see two modes, inherit from upper level and custom configuration, which determine how strategy overrides are applied.
Common Strategy Types
- Geofence alerts: enter, exit, or both
- Overspeed: trigger when a defined threshold is exceeded
- Stop overtime: trigger when stop duration exceeds the threshold
- Offline overtime: trigger when the offline period exceeds the threshold
- ACC-related alerts: trigger based on switch state when supported
Configuration Steps (Recommended Practice)
- Start with a base strategy at the account level as the default rule for the team.
- For groups that need differences, switch them to custom configuration and change only the parts that need to differ.
- Use device-level adjustments only when a single device truly needs finer rules, so maintenance cost stays manageable.
- After saving, validate the logic with one device to confirm that the trigger behavior matches expectations.
FAQ
Q: Why did I change the group configuration but the device behavior did not change?
A: The device may still be in inherit mode, or the device level may already have a higher-priority custom configuration. Check the current node's configuration mode.
Q: Why can't I see some configuration items?
A: Visible strategy types may differ based on account permissions or enabled modules. Ask the administrator to confirm what is available for your environment.