Skip to main content

Condition-Based Maintenance

Some maintenance should follow how hard an asset works, not the calendar. A Condition template raises a work order when an asset's run hours or a counter reach a threshold, or when a tool's life comes due. Technicians respond as in Condition-Based Work.

Create a Run-Hours Template​

For example, CoreForge's spindle service on Machine 1.

  1. Open Configuration → Maintenance → Work Orders and add a template on the Work Orders tab.

  2. Fill in the details:

    FieldExample
    TitleMachine 1 - Spindle service
    AssetCoreForge\Philadelphia\Machining\Machine 1
    Maintenance typePreventive
    Work typeSpindle Service
    PriorityMedium
    Schedule typeCondition
  3. In the Condition section, choose Run Hours and enter the interval in hours.

  4. Set Last serviced on and Last value to say where the count starts.

  5. Save the template and set its version status to Released.

Run hour condition

Choose Counter instead to trigger on an asset counter, such as parts made.

Counter condition

warning

Releasing a Condition template starts the checks straight away. Set Last serviced on and Last value correctly, or a work order may be raised before it is due.

Use Tool Life​

Tool Life is only offered when the template's Asset is a tool, such as a mold, so select the tool first.

  1. Set Asset to the tool.
  2. Choose Tool Life as the condition.
  3. Set Due for to the tool limit the work order covers: its PM, refurbishment or calibration.

A work order is created when the tool reaches its Warn at % of that limit. Completing the work order resets the count, the same as recording it on the tool's Life tab. The work orders for a tool are listed on the Maintenance tab of its tool editor.

Tool life condition

Reference Materials: Schedule Types - One Time, Recurring and Condition.

Schedule Types​

A Work Order template includes a Schedule Type, which determines how work orders are generated. When a template is active i.e. 'Released', the system evaluates its schedule configuration. When the criteria are satisfied, an actual work order is created.

Kanoa Maintenance supports three primary schedule behaviors:

One Time

Use One Time when the template should generate a single work order.

This is useful for:

  • one-off repairs
  • installation work
  • project tasks
  • ad hoc maintenance requests

When a template is configured as One Time, the system generates one actual work order from that template.

Recurring

Use Recurring when the template should continuously generate work orders on a defined schedule.

This is typically used for:

  • preventive maintenance
  • routine inspections
  • repeating safety checks
  • calendar-based maintenance programs

When a template is configured as Recurring, the system creates actual work orders according to the recurrence settings. The schedule's times are in the asset's site time zone (UTC if the site has none), so a work order due at 06:00 stays at 06:00 at the plant across daylight-saving changes.

Recurring schedules are best used when maintenance should happen on a predictable interval, such as:

  • every day
  • every week
  • every month
  • every X days/hours depending on schedule configuration

kanoa-cmms

Condition

Use Condition when the template should generate work orders only after a defined asset condition, counter, or threshold is met.

This is typically used for:

  • runtime-based maintenance
  • counter-based maintenance
  • threshold-triggered inspections
  • condition-based corrective or preventive work

When a template is configured as Condition, the maintenance order can be set to be triggered whenever the asset run hours or counter values reach a certain threshold, or, for a tool, when its tool life comes due. Condition scheduling is useful for maintenance strategies that should not be driven by calendar date alone.


kanoa-cmms


kanoa-cmms


Tool Life works with Kanoa Ops tooling. It's only offered when the template's Asset is a tool, such as a mold, so select the tool first. Set Due for to the tool limit the work order covers: its PM, refurbishment or calibration. A work order is created when the tool reaches its Warn at % of that limit, and completing the work order resets that count, the same as recording it on the tool's Life tab. The tool's work orders are listed on the Maintenance tab of its tool editor.


kanoa-cmms


Reference Materials: Tool Life with Kanoa Maintenance - How a tool raises a work order.

With Kanoa Maintenance​

Tooling tracks a tool's life and records its maintenance on its own; Kanoa Maintenance isn't needed. With a Kanoa Maintenance license, the work can be scheduled as maintenance work orders instead:

  1. In Kanoa Maintenance, create a work order template set to Condition, with the tool as its Asset.
  2. Pick the Tool Life condition and set Due for to the PM, refurbishment or calibration limit.
  3. When the tool reaches its Warn at % of that limit, a work order is created. Completing it resets that count, the same as PM done, Refurbished or Calibrated on the Life tab.

The tool editor's Maintenance tab lists the tool's maintenance work orders; double-click one to open it. See Work Order Creation & Scheduling.

Worked Example​

The CoreForge sample plant raises a spindle service on Machine 1 from its run hours, the same as Developer Training.

Create the Condition Template​

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.

Choose Counter instead of Run Hours to trigger on an asset counter, such as every 50,000 parts on Machine 1's outfeed.

Check Your Understanding​

  1. Name three conditions that can raise a work order.
  2. When is the Tool Life option offered?
  3. What does completing a tool-life work order do?
Answers
  1. Asset run hours, a counter value, or a tool's life reaching its Warn at %.
  2. Only when the template's Asset is a tool, such as a mold.
  3. It resets the tool's count for that limit, the same as recording it on the tool's Life tab.