Applies to: Inspections, Defects, Assets, Work orders
Triggers
The trigger is the event that starts the automation. Each automation has one.
Trigger | Fires When |
Inspection submitted | Someone submits an inspection - at the moment of submission, whatever the result |
Defect created | A defect is raised. It doesn't matter how: from an inspection, added manually or reported by a diagnostic code. |
Conditions available in step 2 change depending on which trigger you picked in step 1.
Conditions
Conditions are optional. Which ones you can use depends on the trigger you chose.
With Inspection submitted
Condition | Continues only when |
Inspection has passed or failed | The inspection's overall result matches the outcome you choose |
Submitted on a specific form | The inspection used one of the forms you select. You can select several. |
Submitted on a specific asset | The inspection was carried out on one of the assets you select |
With Defect created
Condition | Continues only when |
Defect is on a specific asset | The defect was raised against one of the assets you select. |
Defect has a specific severity | The defect's severity matches the one you choose. |
How conditions combine
Every condition you tick must be satisfied. They combine with and, never or.
So a rule with both failed and accident report form ticked will only continue for inspections that were both failed and on that form. A failed inspection on a different form doesn't match. A passed inspection on the accident form doesn't match either.
If you need "or" — say, the accident form or the roadside form — you have two options. Some conditions let you select several values at once, which behaves like "or" within that one condition: Submitted on a specific form accepts multiple forms. Where that isn't available, build two automations.
Ticking no conditions at all means the automation runs every time the trigger fires. Before you do that, work out roughly how often the event happens in your fleet in a normal week.
Actions
At least one action is required. You can choose several, and they run together.
Action | What it does |
Mark the asset as out of service | Takes the asset off the road using the reason you provide. The reason is stored with the record and shoes in the asset's out of service log. |
Update severity of all defects | Sets every defect raised on that inspection to the severity you choose - useful when the context matters more than the individual fault. |
Create a work order | Raises a work order for the asset, assigns the due date what you want and assigns the work order to a particular mechanic/vendor or a third party of your choice. |