Opening a ticket only moves the exception from the device to a to-do. Missed handling happens later: nobody claims it, the claimant gets busy, the same fault opens ten tickets, or someone taps Complete. Put gates at those four points.
What leaks is rarely “we did not know.” It is “we can pretend we did not know.”
Paper and pop-ups both allow pretending. Without timeout escalation, a busy shift drops the ticket. Escalate to a role, not one person’s WeChat. How an alert first becomes an assignable ticket: Fewer screens to watch: how alerts become assignable tickets. Missed patrol items should use the same pipe, not a remark. See Why paper patrol checklists fail at scale and Device patrols: from paper checklists to a closed loop.
Close checks matter more than nagging
Nudges only raise anxiety. Require a floor write-back on close—temperature, pressure, reset, spare issue number—or missed handling hides. Audits depend on this step: What device records must prove in a safety audit. The gap with and without a closed loop: With devices in the business vs. without: what exception handling looks like.
Cover high-consequence events in phase one
Not every blip needs a ticket. Start with downtime, safety and metering, run the five steps, then expand. DaXi Technology sets suppression and escalation by event type so week one does not drown the crew. To cut missed handling, go to the Hardware-software service page and say who follows a ticket after it opens. For noisy alerts, start with The system never alerts, or alerts too much. How to diagnose.
Duplicate tickets and orphan tickets leak in opposite directions
Ten tickets for one heat rise teach maintenance to ignore them. One ticket with no owner overnight is the same as never opening it. Tune the suppress window and claim timeout together. Night shifts can escalate faster, but do not dump every info-level alert on the lead’s phone. After week one that channel gets muted and missed handling returns.
A ticket should still trace to a device event ID so an audit can pull one chain. Keep the trigger snapshot, not only the title. If cameras are only attachments, you still have not moved from watching to tickets: Cameras without work orders are not software. Energy over quota uses the same five steps: Energy into MES: crews stop copying meters by hand.
Crews will push hard tickets back to the pool as “busy”
Allow return after claim, but require a reason and count it as unfinished. Otherwise veterans dump hard tickets and new hires only get blips. Shifts and skill groups belong in the system, not a group announcement. Access failures and missed warehouse scans can share the queue with different skill tags: Scan into WMS so books and stock stay closer and Access control tied to HR: access dies when employment does.
Do not kill phone repair on day one of trial. For two weeks compare how many phone calls already had a ticket and how many the system missed. Add rules for misses; tighten thresholds for noise. Close the parallel channel only after it converges. How a project closes from brief to launch: From brief to launch: how a hardware-software project runs.