Equipment, faults and maintenance

Schedule maintenance when equipment reaches its interval

Done by about 1.4 million people across 2 job roles, daily.

On a schedule Every day at 6am, checking equipment against maintenance intervals → then Schedule equipment maintenance appointment

Acts when the maintenance variance is at least 0. Otherwise it logs that the equipment has not yet reached its maintenance interval, and stops.

Reads

equipment id, equipment name, last maintenance date, maintenance interval days, location

Evidence

Proved in test: n8n execution 1387, 12 of 20 nodes ran in 494 ms.

Notify staff when equipment problems are detected

3 builds of this one. The same workflow, fitted to what each business calls it and the field it checks — listed in the teardown below.

Done by about 4.5 million people across 39 job roles, several times a day.

When a maintenance or equipment problem is detected → then Notify designated personnel of the problem

Acts when the severity level is at least 3. Otherwise it logs that the severity is below the reporting threshold, and stops.

Reads

problem id, equipment name, problem description, severity level, detected at

Evidence

Proved in test: n8n execution 1320, 12 of 20 nodes ran in 564 ms.

Surface the repair manual for the job

Done by about 2.2 million people across 13 job roles, several times a day.

When a repair or maintenance job is assigned for an equipment model → then Send the technician the matching repair manual

Acts when the manual available is true. Otherwise it logs that no matching manual exists for this equipment model, and stops.

Reads

work order id, equipment model, technician email, manual available, assigned at

Evidence

Proved in test: n8n execution 1421, 12 of 20 nodes ran in 559 ms.

Log hardware benchmark results against spec threshold

Done by about 1.8 million people across 6 job roles, daily.

When a hardware performance test finishes running → then Log benchmark result against spec threshold

Acts every time the trigger fires.

Reads

test id, device id, benchmark score, spec threshold, test type

Evidence

Proved in test: n8n execution 1258, 9 of 11 nodes ran in 352 ms.

Flag temperature readings outside safe range

Done by about 3.9 million people across 1 job role, several times a day.

On a schedule Every 15 minutes, poll equipment temperature sensor → then Flag temperature reading above safe limit

Acts when the temp over limit is more than 0. Otherwise it logs that the reading is within the safe range, and stops.

Reads

equipment id, equipment type, reading f, max safe f, reading at

Evidence

Proved in test: n8n execution 1168, 12 of 20 nodes ran in 591 ms.

Log cost and type after each repair job

Done by about 1.5 million people across 2 job roles, daily.

When repair or maintenance job is marked complete → then Log repair cost and type

Acts every time the trigger fires.

Reads

job id, asset id, repair type, cost, completed at

Evidence

Proved in test: n8n execution 1244, 9 of 11 nodes ran in 354 ms.

Flag facility metrics that leave normal range

Done by about 1.2 million people across 5 job roles, several times a day.

When a monitored facility or system metric reading is captured → then Flag facility metric deviation

Acts when the variance over tolerance is more than 0. Otherwise it logs that the metric reading stayed within its normal range, and stops.

Reads

metric id, metric name, metric value, normal target, normal tolerance

Evidence

Proved in test: n8n execution 1147, 12 of 20 nodes ran in 618 ms.

Log pass or fail after each diagnostic test

Done by about 146,000 people across 1 job role, more than weekly.

When diagnostic test procedure finishes on target system → then Log diagnostic test pass/fail result

Acts every time the trigger fires.

Reads

test id, system id, test name, result, completed at

Evidence

Proved in test: n8n execution 1270, 9 of 11 nodes ran in 358 ms.

Alert when AV quality drifts out of spec

Done by about 1,000 people across 1 job role, several times a day.

When an AV signal reading is captured during monitoring → then Log AV quality-fault alert

Acts when the variance over tolerance is more than 0. Otherwise it logs that the AV signal stayed within tolerance of spec, and stops.

Reads

signal id, room id, signal value, spec target, spec tolerance

Evidence

Proved in test: n8n execution 964, 12 of 20 nodes ran in 440 ms.

Log completed service or repair activity

Done by about 2.1 million people across 5 job roles, several times a day.

When service or repair task is marked completed → then Log completed service or repair activity

Acts every time the trigger fires.

Reads

record id, worker id, service type, asset id, completed at

Evidence

Proved in test: n8n execution 1234, 9 of 11 nodes ran in 430 ms.