Asset Assignment Violation
An Asset Assignment Violation alert will be triggered when at least one asset assignment violation is raised as a result of asset assignment operations, and no matching pending/open alert is already recorded. In cases where the assignment violation is a time overlap with another asset assignment, each overlapping asset assignment will raise violations. If the asset assignment is associated with a load or trip, the escalation basis is the earlier of the asset assignment start date/time or the load/trip start date/time. For unassociated asset assignments, the escalation basis is the asset assignment start date/time.
- Return Type Violation
This violation is raised if the Asset’s Return Type is IMMEDIATE and the End Location does not reflect the asset as returning to its site of origin (Start Location). This violation check is skipped on unassociated assignments (presumed to represent an intentional placement/allocation of that asset, and therefore exempted). The violation can be overridden by permitted users.
- Time Overlap Violation
If the asset assignment is associated with a load or trip, the escalation basis is the earlier of the driver assignment start date/time or the load/trip start date/time. For unassociated driver assignments, the escalation basis is the driver assignment start date/time.
The violation also considers the Asset’s required Minimum Hours Between Usage so that violation is raised if an asset is reused before the minimum required “down time” (between assignments) as indicated by this value. The violation can be overridden by permitted users.
Notes:
- Violations on existing Asset Assignments can be viewed from the Asset Assignment Properties > Violations tab.
- When creating an assignment, the violation can be detected in Asset Candidates Override Required or Ineligible tabs by looking for values populated in certain fields. For example, if Equipment Type is populated on one of these tabs, the Equipment Type Violation was raised for this asset. Each Asset entry may exhibit multiple violations.
See Also