What's new
- Service checklists. A checklist template of type Service can now be attached to a service, so the work is done to the same list every time. The technician answers each item when completing the service, and a service with a checklist can't be completed until every required item has an answer.
- A default for each machine. Set a Default service checklist on a machine, or on its license group. A new service starts with the machine's own default, or its group's if the machine has none. You can still choose a different one when you create the service.
- A failed critical item holds the machine. When a service is completed and a critical item on its checklist is marked Fail, the service still completes with every answer recorded, and the item gets a defect: the machine's open defect for that item, or a new Critical defect that names the service. That defect takes the machine Out of Service: every pre-start on it fails until the defect is closed, and closing it lifts the hold. It is the same rule as a critical item failing on a pre-start.
- A repair that doesn't fix the fault. When a service raised to repair a defect fails a critical item on its checklist, that defect is not resolved. It stays open, gets a comment naming the items that failed, and holds the machine Out of Service until it's closed.
- People are told. Your Administrators and Account Owner hear about a repair that failed its checklist, and each new hold sends the Equipment is locked out email, as a hold from a pre-start does.
Good to know
- The emergency bypass still works. If a held machine has to move, the in-app bypass still unlocks it for a short, logged window. It doesn't lift the hold: the next pre-start still fails until the defect is closed.
- A technician's lockout stays theirs. An Out of Service lockout a Technician or Lead set by hand is unchanged by any of this, and still has to be lifted by hand.
- Services without a checklist complete exactly as before.
See Services and Maintenance Workflow for the full picture.