Skip to main content

Preventative Maintenance, Maintenance Routines, and Usage.

Configure usage tracking, maintenance routines, tool maintenance, and usage limits to identify service needs, control item availability, and document completed maintenance.

Overview

Preventative Maintenance brings usage tracking and maintenance together in Builds. You define what to track once for the whole workspace, attach it to your parts, tools and locations, and set rules that tell you when maintenance is coming due.

It replaces the older maintenance schedules and part and tool usage tracking. If your team used those, your schedules, history and usage were moved over automatically.

Key terms

  • Usage type: something you track, such as cycles, runtime hours, pressure or oil color. Defined once for the workspace in Builds > Settings > Usage Types.

  • Usage limit: an optional maximum or range for a usage type on a part, tool or location, with a rule for what happens when it's reached. Set on the part, tool or location edit page.

  • Usage card: shows an item's current usage values and full history, and lets you record or reset usage. Found on the Execution tab of inventory item and tool instance pages.

  • Record Usage block: the procedure content block that records usage during a run.

  • Maintenance routine: a reusable maintenance plan that can be linked to many parts, items, tools, tool instances or locations. Listed in Builds > Maintenance > Routines.

  • Trigger: the rule inside a routine that makes maintenance come due: a schedule, a usage amount or a number of check-outs. Each trigger has its own procedure.

  • Due state: where an item stands for a trigger: Due Soon, Due or Overdue. Shown in Builds > Maintenance > Status.

How it fits together

  1. Create usage types in Builds > Settings > Usage Types.

  2. Add them to parts, tools or locations, with limits if you need them.

  3. Record usage on the Usage card or with a Record Usage block in a procedure.

  4. Create maintenance routines whose triggers watch the calendar, the usage or the check-outs.

  5. Watch Builds > Maintenance > Status, and record maintenance when it's done, deferred or canceled.

Steps 1 to 3 are only needed for usage-based maintenance and usage limits. A routine with only a schedule trigger works without any usage types.

Create usage types

Usage types are shared across the whole workspace. Parts, tools and locations pick from this one list instead of each typing its own names, so "Cycles" means the same thing everywhere.

  1. Click the gear icon next to Builds in the left menu, then choose Usage Types.

Builds Settings with Usage Types and Add Usage Type highlighted

  1. Click Add Usage Type.

  2. Enter a Name for what you're tracking.

  3. Under How should readings be tracked? choose one of the four options below.

  4. Fill in the settings for that option, then click Save.

Add Usage Type dialog with Running Total selected

The four ways to track readings:

  • Running Total: the total since it was last reset or maintained. Keeps adding up, for example cycles or runtime hours. Set a Unit of measurement and Decimal places, and choose whether to Allow negative readings and Allow manual resets.

  • Current Measurement: the latest level or reading, for example pad depth or pressure.

  • Category: the latest observed condition from a set of options, for example oil color. Add the Options operators will choose from, and drag them into order.

  • Timer: total time tracked with a start/stop timer. Keeps adding up, for example spindle runtime or burn time. You can choose Allow manual resets.

Category option with the Options list

The Usage Types list shows each type's units, decimals, whether negative readings and resets are allowed, and its Scope. Every workspace has the built-in cycles and time types (scope System). Types you add have scope Team.

Important: Usage types can't be renamed for now, because older usage blocks in procedures find their type by name. Choose names carefully before you add them to parts and procedures.

Add usage types to parts, tools and locations

Once a usage type exists, add it to whatever needs tracking. You set it up once on the definition and every item or instance gets it:

  • Part → every inventory item of that part

  • Tool → every tool instance of that tool

  • Location → that location

Add usage tracking to a part

  1. Open the part from Builds > Parts and click Edit.

  2. Scroll to the Usage section and click Add Usage Type.

  3. Choose a type in the Usage Type list. Click Add Usage Type again to track more than one.

  4. To set a limit, click the ⋮ menu at the end of the row and choose Add Limit (see below).

  5. Click Save.

Usage section on the Edit Part page with a limit and the When exceeded options

Add usage tracking to a tool or location

  • Tool: the New Tool and edit pages have the same Usage section. Every instance of the tool picks up the types you add.

  • Location: open the location and add usage types in the same way.

Usage section on the New Tool page with two usage types

Set a usage limit

Limits are optional and set per usage type, on each part, tool or location. After you choose Add Limit, fill in:

  • Limit: the maximum, in the type's units.

  • Warn At: an optional level at which the item shows as near its limit.

  • When exceeded: what happens once the limit is reached:

  • Allow use: the item can still be used. The limit shows as a warning only.

  • Warn and confirm: the user sees a warning and must confirm before using the item. This is the default.

  • Block use: the item can't be used.

Limit warnings also appear in the inventory pickers for check-out, kitting and install.

Use past a limit? confirmation in a run's kit picker, with Use Anyway highlighted

With Warn and confirm, choosing an item past its limit in a run asks for confirmation. Using it anyway is noted in the item's activity history.

An item's Details panel shows how many limits apply and whether any are reached, for example 1 limit, 1 at limit. Items at or near a limit also show the At Usage Limit or Near Usage Limit alert in the Inventory and Tool Instances lists.

Note: Usage limits and maintenance blocking are separate controls. A limit stops use based on a usage value. A routine can separately block use while maintenance is due.

Record and review usage on the Usage card

The Usage card sits on the Execution tab of an inventory item or tool instance. It shows each usage type's current value, how close it is to its limit, and every reading.

Use it to record usage outside a procedure or to reset a counter.

  1. Open the inventory item and go to the Execution tab.

  2. On the Usage card, click the ⋮ menu next to the usage type and choose Record Usage.

Usage card with the usage type menu open, showing Record Usage and Reset

3. Choose how to enter the reading:

  • Add new amount: enter the usage since the last reading.

  • Set new total: enter the current total shown on the equipment.

4. Enter the value and click Record.

Record Usage dialog with Add new amount and Set new total

The card's Summary now shows the new total, the percentage of the limit used, and the limit status (for example Within Limit).

Usage card summary showing 240.0 hours, 48% of a 500-hour limit

Tip: Use Add new amount for routine logging, such as "ran 3 more hours". Use Set new total when you're reading a meter that shows the running total.

Reset a counter

If the usage type allows manual resets, click the ⋮ menu next to it and choose Reset, then confirm. The counter goes back to zero. Earlier readings stay in the history but stop counting toward the current value. If operators read the value from a meter, zero the meter on the equipment as well.

Reset confirmation dialog

View usage history

Click History on the card to see every reading: the usage type, the value, who recorded it and when, and the procedure run it came from. The Run History section below it lists usage recorded during runs.

Usage card History view

Record usage in procedures

The Record Usage content block records usage during a run. It works with parts, tools and locations, and with every kind of usage type. One block can hold several rows, so a single step can capture several readings.

Add a Record Usage block

  1. Open a procedure draft in the editor.

  2. In the step, click Add Content and choose Record Usage under Usage.

Add Content menu with Record Usage highlighted under Usage

  1. Set Items allowed: Any item lets operators add their own rows during the run; Listed rows only limits them to the rows you add.

  2. Set Entry: Add new amount or Set new total.

  3. Click Add to add a row, then choose the Type (part, tool or location), the Item and the Usage Type.

  4. Optionally tick Also apply usage to component items to apply the same usage to the components in the item's as-built BOM. Include in Summary adds the readings to the run summary.

  5. Save, then send the procedure through your normal review and release.

Record Usage block in the procedure editor

Record usage during a run

  1. In the run, go to the step with the Record Usage block.

  2. Choose the Instance (the serial or lot). The picker shows maintenance badges such as Due Soon.

  3. Enter the Value. The current total shows underneath.

  4. Sign off the step. The usage is recorded at sign-off and appears in the item's Usage card history, linked to the run.

Record Usage block in a run, with the value and Signoff highlighted

Older Record Part Usage and Record Tool Usage blocks

Record Part Usage and Record Tool Usage are deprecated and no longer appear in the Add Content menu. Procedures and runs that already use them keep working, and they record against the new usage types.

In the procedure editor, each old block shows a Deprecated tag with a one-click option to convert it to Record Usage. You can convert them at your own pace.

  1. Open a draft of the procedure.

  2. Find the block tagged Deprecated.

  3. Click the convert option to turn it into a Record Usage block.

  4. Check the new block's rows, then save and release the procedure as usual.

Create maintenance routines

A maintenance routine says what gets maintained, when it comes due and which procedure to run. Routines replace the older maintenance schedules. One routine can be linked to many parts, items, tools, tool instances or locations, so you build it once and reuse it.

Where routines live

Builds > Maintenance > Routines lists every routine in the workspace, with its triggers, what it tracks, when it comes due and how many records use it.

Routines tab with the New Routine button highlighted

A part's Maintenance tab with New Routine and Link Routine

Create a routine

  1. Click New Routine, either on the Routines tab or on a record's Maintenance tab. A routine started from a record is linked to it automatically.

  2. Enter a Name.

  3. Click Add Trigger and choose Schedule, Usage or Check-outs.

Add Trigger menu with Schedule, Usage and Check-outs

  1. Enter a Trigger name, choose the Procedure to run (optional), and fill in the trigger's settings (see below).

  2. Set the thresholds: Flag Due Soon, Escalate to Due (required) and, optionally, Escalate to Overdue. A line under the trigger sums it up, for example Comes due every 250 hours.

A Usage trigger with procedure, usage type and thresholds filled in

  1. Add more triggers if you need them, and drag them by their handles into priority order.

  2. Under Settings, optionally tick Block item use when maintenance is due. While maintenance is due or overdue, the covered items, tool instances and locations can't be used, except to check them back in.

  3. Click Create Routine.

Routine settings with Block item use when maintenance is due ticked

Trigger settings

  • Schedule: a Start Date, an Interval (every so many days, weeks, months or years), an End (Never, After or On Date), a Schedule Basis such as From actual completion, and Schedule On Calendar Days or Working Days. Thresholds are set in days before or after the target date.

  • Usage: the Usage type and Count from (When added or All history). Usage counts from when the trigger was added, the last reset or the last maintenance. Thresholds are set in the usage type's units.

  • Check-outs: the number of check-outs before maintenance comes due. Tools only.

Ranking triggers

Triggers are in priority order. Completing a trigger resets every trigger below it, never the ones above. Drag a trigger by its handle to move it.

For example, put an annual overhaul above a 250-hour service. When the overhaul is done, the hour count starts over too, so nobody does a service the day after an overhaul.

Routine editor showing the priority order note and drag handles

Edit, link or archive a routine

  • Edit: click the routine's name on the Routines tab. The panel has Details and Where Used tabs, with Save and Archive at the bottom.

  • Link: use Link Routine on a record's Maintenance tab. Linking a part covers all of its inventory items, and linking a tool covers all of its tool instances.

Note: New items and tool instances come due from their own creation date, not from the date the routine started.

Monitor status and record maintenance

Builds > Maintenance > Status lists every upcoming occurrence your routines cover: the item, the routine, the target date, the status and the procedure. Usage occurrences show progress, such as 260.0 of 250.0 hours. Statuses include Scheduled, Due Soon, Due and Overdue.

Status tab with Due and Scheduled occurrences

There are two ways to record an occurrence.

Run the maintenance procedure

Click Run in the Procedure column. The run starts linked to that item. When the run is ended as completed, the occurrence is recorded as Executed automatically, with a link to the run.

Record it by hand

  1. Tick the occurrence's checkbox.

  2. Click Record Maintenance.

  3. Choose the Outcome and fill in its fields:

  • Executed: the work was done. Enter the Date recorded and optional Notes. The next occurrence is measured from the date recorded.

  • Deferred: the work moves to a later date. Enter the New target date and a Reason for deferring.

  • Canceled: this one occurrence won't be done. The routine carries on from the next occurrence.

  1. Click Record.

Record Maintenance dialog with the Outcome list open

Record Maintenance dialog for a deferral, with a new target date and reason

Important: When a trigger has a procedure, it can only be recorded as Executed by finishing that procedure's run. Record Maintenance then offers only Deferred and Canceled. Usage and check-out occurrences that have a procedure can't be recorded by hand at all.

Review maintenance history

The History tab lists every recorded occurrence with its trigger, outcome (Executed, Deferred or Canceled), run and who recorded it.

History tab showing Executed and Deferred outcomes

Find items that need attention

Maintenance and usage alerts are built into the Inventory list and the Tools > Instances list, so you can find items that need attention without opening each one.

  • Open Builds > Inventory or Tools > Instances.

  • Click Filters, then open Alerts.

  • Tick the alerts you want: Expired, Expiring Soon, At Usage Limit, Near Usage Limit, Maintenance Overdue, Maintenance Due or Maintenance Due Soon.

Inventory Filters menu with the Alerts options

To see due states in the grid, click the column picker, search for Maint, and tick Maintenance. The column is hidden by default.

Column picker with Maintenance ticked

The Maintenance column shows how many routines apply and how many are due, for example 2 routines, 1 due.

Inventory list filtered to Maintenance Due, with the Maintenance column

What moved: The old Log Maintenance button and the Maintenance filter on a part or tool's Inventory tab are gone. Use the Alerts filter on the main lists, and record maintenance from Builds > Maintenance > Status. Saved views that used the old Maintenance filter or column need to be set up again.

What happens to existing data

You don't need to rebuild anything. Existing usage types, limits, usage history, maintenance schedules and maintenance history were all moved over automatically with the release. Some things may look a little different afterwards.

Usage types

  • Names that differ only in capitals or spacing were merged into one type (for example "A12" and "a12 "). A name that matched a type you already had joined that type and took its spelling.

  • Part usage named "time" became Time (Part), so it isn't confused with tool Time, which is measured in seconds.

  • Only "cycles" became the built-in Cycles type. "cycle" and other spellings stayed as separate types.

  • Names used only in procedures or history, and not on any part, became archived types.

Limits

  • Limits on parts and tools carried over. Items already past a limit show At Usage Limit straight away.

  • Limits set to 0, blank or a negative number were not carried over. These already meant "no limit".

Usage history

  • Item and tool usage totals are unchanged.

  • Usage entered as 0 in a step now shows as a 0 reading. You may see more history rows, but totals don't change.

  • Usage recorded on an item whose part doesn't have that usage type is kept, with a Not Declared warning.

  • If your team already used the new usage types, old and new readings are added together.

  • History for deleted items and tool instances was not carried over.

Maintenance

  • Each schedule became a routine with one trigger, linked to the same records and the same procedure. Past maintenance is in the routine's history.

  • Anything that showed Overdue before now shows Due. For moved-over triggers, Due Soon starts 7 days before a time-based due date, or 10% before a usage or check-out amount.

  • Usage-based maintenance now counts from the latest usage reset and reads the item's usage history. The old schedules ignored resets and read a separate log, so some due states may have shifted.

  • Tool instances that were never maintained come due on the routine's regular dates.

  • Maintenance done on schedules that were later deleted shows in history only. Unfinished maintenance records that weren't tied to a run were not carried over.

Procedures and saved views

  • Nothing in your procedures was rewritten. Old usage blocks and runs already in progress keep working.

  • Saved views that used the old Maintenance filter or column lose it. Rebuild them with the Alerts filter and the Maintenance column.

Frequently asked questions

Do I need to recreate my maintenance schedules?

No. Each schedule was turned into a routine automatically, with its links, procedure and history.

Where did Maintenance Routine and Log Maintenance go on the tool and inventory pages?

Routines are now created or linked from the Maintenance tab on a part, item, tool, tool instance or location, and all routines are listed in Builds > Maintenance > Routines. Record maintenance from Builds > Maintenance > Status.

Can one routine cover several items?

Yes. Link it to as many records as you like. Linking a part covers all its items, and linking a tool covers all its instances.

Can one routine have more than one trigger?

Yes. Each trigger has its own procedure. Rank them so that completing a bigger job resets the smaller ones below it.

Can I record usage without a procedure?

Yes. Use Record Usage on the item, tool instance or location's Usage card.

Will my procedures with the old usage blocks stop working?

No. They keep working and record against the new usage types. Convert each block to Record Usage when you next edit the procedure.

Can I rename a usage type?

Not at the moment, because older usage blocks find their type by name.

Why did an item's due state change after the release?

Usage-based maintenance now counts from the latest reset and reads the full usage history, and Overdue items now show as Due. Compare the trigger, the last completed maintenance and the usage history to see why.

Why does a reading show a Not Declared warning?

The reading was recorded against a usage type that the item's part doesn't have. Add the type to the part, or leave it if the reading is only historical.

Where did the Maintenance filter on the Inventory tab go?

Use the Alerts filter on Builds > Inventory or Tools > Instances, and turn on the Maintenance column if you want it in the grid.

Related articles

Did this answer your question?