Parts are the materials and spares your team uses to complete maintenance work.
Tracking inventory in Limble keeps part quantities accurate at each site, so the right parts are on hand when work comes up.
Parts
A part is a consumable item or component used in maintenance work, such as a filter, belt, or bearing.
Limble tracks how many of each part you have at each site. When your team uses a part on a task, that amount comes out of inventory.
To get started, read:
Important to know: Part quantity and price include parts received on purchase orders. A part's price is the average of its general stock price and the prices paid on received purchase orders.
Inventory tasks
Inventory tasks help you keep your parts stocked and your counts accurate. Limble creates them automatically based on the thresholds and schedules you set.
The execution of inventory tasks happens with maintenance tasks.
There are two types of inventory tasks:
Task type | When Limble creates it |
Part threshold task | When a part's quantity or usage crosses a threshold you set |
Cycle count task | When a cycle count schedule you set comes due |
Part threshold tasks
Part thresholds tell Limble when a part needs attention. Thresholds stay off until you set them for a part.
Two kinds of thresholds create tasks:
Minimum quantity threshold: When a part's quantity drops below the minimum you set, Limble creates a task reminding someone to check stock and order more.
Stale threshold: When a part hasn't been used on a task for a set number of days, Limble creates a task to flag it. For example, a stale threshold of 365 creates a task if a part hasn't been used in a year. Stale thresholds help you find obsolete parts you can sell or remove, and they help you plan your parts budget.
You can also set a maximum quantity threshold. It doesn't create tasks. Instead, when a minimum threshold task is created, Limble uses the maximum to show how many parts to restock: the maximum minus your current quantity.
By default, part threshold tasks count as unplanned work. You can change the default so threshold tasks count as planned instead. Part settings also control who threshold tasks are assigned to and when they're due. These settings apply to all parts at a site unless you change them for an individual part.
Cycle count tasks
A cycle count is a regular audit that checks whether the part quantities in Limble match what's on your shelves. Instead of counting everything at once, your team counts a set number of parts on a schedule you choose.
When you set up a cycle count, you choose:
How often it runs
How many parts to count at a time, and how many parts go on each task (up to 500 per task)
Who the tasks are assigned to
Which parts to include or exclude
When a count comes due, Limble creates cycle count tasks. Your team enters the quantity they count for each part, and completing the task updates inventory to match. You can download a report that shows the difference between inventory before and after the count.
Blind cycle counts hide current quantities during a count, so the person counting isn't influenced by the number Limble expects. Blind counts are on by default, and a super user can turn them on or off for all sites.
Important to know: when you complete a cycle count, Limble treats the quantities you enter as correct, even if stock changed while the task was open.