Maintenance from IoT alerts: one order per machine, filled in, and costed to repairs

An alert on a machine that already has an open condition order joins it; a new alert order is filled from the machine and the rule; maintenance cost posts to a repairs account and the order’s cost center; tasks record who performed them and whether the reading was in spec; readings stamped in the future are refused.

• One condition order per machine: an alert on equipment that already has an open condition-based order is linked to that order rather than raising another.
• A new alert order takes its work center, location and cost center from the machine, its priority from the rule’s severity, an assignee (the rule’s notify role, else the maintenance planner), and the condition plan’s tasks and spares.
• Alert pages are titled with the rule, the machine and the time.
• Order Tasks: Performed by, Performed at, and In spec, worked out from the task’s spec limits.
• Maintenance cost posts to a repairs and maintenance account, never to a utilities expense account, and carries the order’s cost center (defaulted from the machine), so a fund-accounting company derives the fund. If the posting fails, the order says why.
• A reading stamped more than 5 minutes in the future is refused, so a gateway with a wrong clock cannot write tomorrow’s readings.
• Maintenance planners hold the task grants; maintenance roles can look up cost centers; warehouse roles can read spares and maintenance parts.
• The 360 panel reloads when you move to another record.