Skip to main content

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.

Create the condition template
  1. In Configuration → Maintenance → Work Orders, add a template:

    FieldValue
    TitleMachine 1 - Spindle service
    AssetCoreForge\Philadelphia\Machining\Machine 1
    Maintenance typePreventive
    Work typeSpindle Service
    PriorityMedium
    Schedule typeCondition
  2. In the Condition section, choose Run Hours every 1 hrs. A real spindle service would be hundreds of hours; one hour lets you see it work during training.

  3. Set Last serviced on to now and Last value to 0.

  4. Save and release the template.

Watch it trigger
  1. Make sure Machine 1 is running in Production, as in Starting Production.
  2. After an hour of run time, check Maintenance → Work Orders for a new Machine 1 - Spindle service work order.
  3. 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.

note

Conditions are checked periodically by checkWorkOrderConditions, so a work order can appear shortly after the threshold rather than exactly on it.