Condition-Based Maintenance
Some maintenance should follow how hard a machine works, not the calendar. A machine that ran three shifts last week needs its spindle serviced sooner than one that ran one. A Condition template generates a work order each time an asset's run hours or one of its counters passes a threshold. Because Machine 1's run hours come from Kanoa Ops, nobody has to log them.
-
In Configuration → Maintenance → Work Orders, add a template:
Field Value Title Machine 1 - Spindle serviceAsset CoreForge\Philadelphia\Machining\Machine 1Maintenance type Preventive Work type Spindle ServicePriority Medium Schedule type Condition -
In the Condition section, choose
Run Hoursevery1hrs. A real spindle service would be hundreds of hours; one hour lets you see it work during training. -
Set Last serviced on to now and Last value to
0. -
Save and release the template.
- Make sure Machine 1 is running in Production, as in Starting Production.
- After an hour of run time, check Maintenance → Work Orders for a new
Machine 1 - Spindle servicework order. - Reopen the template. Kanoa records when it last generated a work order and the run-hour value at the time, and counts the next hour from there.
Choose Counter instead of Run Hours to trigger on an asset counter, such as every 50,000 parts on Machine 1's outfeed.
Conditions are checked periodically by checkWorkOrderConditions, so a work order can appear shortly after the threshold rather than exactly on it.