Tool Crib Management System: Data Model, Fields and Workflow

Key takeaways

• A tool crib system needs eight core entities: item master, serialised item, bulk stock, location, employee, transaction log, calibration record and vendor or regrind order.
• Track serialised items one by one (gauges, holders, torque wrenches) and consumables by quantity (inserts, drills, gloves). Mixing the two is the most common design error.
• Every movement is an append-only transaction: who, what, where, when, which machine and which work order.
• Set stock with reorder point = daily usage × lead time + safety stock. For 6 end mills a day, 5 days lead time and 2 days of cover, that is 42.
• Measure checkout compliance, overdue rate, tool cost per unit and stock-outs.

What a tool crib system records

A tool crib is the controlled store where a plant keeps cutting tools, gauges, fixtures, hand tools, consumables and calibrated instruments.

A tool crib management system records what is in it, who has what, where it is used and what it costs.

This guide lays out that model as field tables you can copy into a specification. If you are comparing products, our tool crib management software roundup covers the market.

The core entities at a glance

Agree on the entities before the fields. Merging two of them into one table is the classic failure.

Item master fields

The item master describes the tool type once. Every serialised item and every bulk stock row points back to it.

The field that matters most is tracking_mode. It decides whether the system expects a serial number or a quantity at every scan.

Serialised item vs bulk consumable

A serialised item is worth tracking individually: a micrometer, a bore gauge, a shrink-fit holder, a torque wrench, a drill jig.

A bulk consumable is issued by count and never comes back: inserts, taps, small drills, gloves, abrasive discs.

Serialised item fields

Bulk stock fields

Keep qty_on_hand as a result of transactions, not a field people type into. A stock-take posts an ADJUST transaction with the difference.

Keep qty_on_order on the item, not on each bin. The reorder check compares the item's total on hand plus on order with its reorder point.

Location, employee and vendor fields

Make machines locations too. A tool sitting in the magazine of CNC-07 then has a real, queryable address instead of "out".

allowed_categories lets you stop an untrained person from checking out a master gauge or a calibrated torque wrench.

The transaction log

The transaction log is the heart of the system. It is append-only: you never edit a past movement, you post a correcting one.

Store unit_cost_at_txn on the row. Prices change, and a cost report built on today's price rewrites last year's history.

Other useful types are RECEIPT (goods in), SEND_REGRIND, RECEIVE_REGRIND, SEND_CAL and RECEIVE_CAL.

Calibration record fields

Gauges and measuring instruments need their own history, because an out-of-tolerance result affects every part measured since the last good calibration.

Where traceability is required, ISO 9001 clause 7.1.5.2 expects measuring equipment to be calibrated or verified at set intervals against traceable standards, identified by status and safeguarded from adjustment. When an instrument is found unfit, the organisation must decide whether earlier results are still valid.

The as_found result matters most. If it was out of tolerance, the log shows which work orders used that gauge since the last pass.

For the full process, see our guide to calibration management, and for one common instrument, torque wrench calibration.

Tool lifecycle statuses and what triggers them

A serialised item has one status at a time, set by a transaction or a timer, never by hand.

OVERDUE is derived, not stored: the record keeps CHECKED_OUT and each overdue check compares now with due_back_at.

A gauge past its calibration_due_date should be blocked from issue, even if it sits in the crib and looks fine.

The checkout and return workflow

Aim for under 15 seconds at the window, or people will reach over the counter.

Checkout

1. Scan the badge. The system checks the employee is active, has fewer than max_open_checkouts and has no overdue items above the limit you set.
2. Scan the machine or work order QR code. This links the tool to where and why it will be used.
3. Scan the tool. For a serialised item, scan its own code. For a consumable, scan the bin label and enter the quantity.
4. The system validates. It blocks the issue if the item is quarantined, calibration is overdue or the category is not allowed for this person.
5. Post the ISSUE transaction. Status becomes CHECKED_OUT and due_back_at is set from default_loan_hours.

Return

1. Scan the tool. The system shows who had it, since when and on which machine.
2. Record the condition. OK, WORN, DAMAGED or MISSING, with a reason code if not OK.
3. Route it. OK goes back to its bin. WORN on a regrindable tool goes to the regrind shelf, or to scrap once regrind_count equals max_regrinds. DAMAGED goes to quarantine.
4. Post the RETURN transaction. The holder is cleared and the status follows the route.

Overdue rules

• Due time: end of shift for hand tools and gauges, end of job for fixtures and tools loaded in a machine.
• Grace period: a fixed margin, for example 2 hours, before the status turns OVERDUE.
• Notice: the holder and their supervisor get a message at the first overdue check.
• Block: an employee with overdue calibrated instruments cannot check out new ones.
• Loss: after a set period, for example 5 working days, the crib posts a SCRAP with reason code lost, at unit cost, so the loss shows in the numbers.

Stock rules: min, max and reorder point

Bulk consumables and serialised tools that wear out, like regrindable end mills, need a reorder point. Returnable tools usually need only a minimum available count, such as "at least 4 bore gauges in the crib".

The standard formula is reorder point = average daily usage × lead time in days + safety stock.

Worked example: 10 mm carbide end mill

When on hand plus on order falls to 42, someone orders up to 102. At exactly 42 that is an order of 60.

During the 5 day lead time the plant uses about 30, so the order arrives with 12 left, the safety stock. Peak stock after receipt is about 72.

Count only new tools issued in daily usage. Reground tools returning from the vendor cover part of the demand and would inflate the figure.

Recalculate the levels each quarter, or when a new job changes usage. Our spare parts management guide applies the same logic to maintenance spares.

Worked cost example: tool cost per part and lost tools

Two calculations with round, illustrative numbers.

Cost per part with and without regrinding

• New end mill: €84, life 400 parts.
• Without regrinding: 84 ÷ 400 = €0.21 per part.
• With 3 regrinds at €18 each: total cost 84 + 3 × 18 = €138.
• If each reground life is 350 parts: 400 + 3 × 350 = 1,450 parts.
• Cost per part: 138 ÷ 1,450 = €0.095 per part, less than half.

That saving needs regrind_count per serial, so worn tools go to regrind instead of the scrap bin.

Cost of lost and untracked tools per month

• Items that go missing: 25 per month at an average of €45 = 25 × 45 = €1,125.
• Time spent looking for tools: 6 searches a day × 12 minutes = 72 minutes a day.
• Over 21 working days: 72 × 21 = 1,512 minutes = 25.2 hours.
• At €40 per hour: 25.2 × 40 = €1,008.
• Total: 1,125 + 1,008 = €2,133 per month, or €25,596 per year.

Replace these numbers with your own before you use them. The point is the method: count the losses from the log, not from memory.

How tool usage ties to machines and work orders

Put machine_id and work_order_id on every issue. That single decision turns a stock list into cost and quality data.

• Tool cost per part number: sum issue cost by work order, divide by good units on that order.
• Tool cost per machine: find the machine that eats twice the inserts of its twin, which often points to spindle runout or a worn fixture.
• Traceability: when a gauge fails calibration, list every work order it measured since the last pass.
• Maintenance link: see whether tool life dropped after a machine repair.

Fixtures, dies and moulds follow the same pattern with longer lives. See tool and die maintenance software and tool and mold management software.

KPIs for a tool crib

Report each KPI with its numerator and denominator, not only a percentage.

For example, 380 open checkouts with 19 overdue is an overdue rate of 19 ÷ 380 = 5.0%.

Checkout compliance is hard to measure directly, because unrecorded issues leave no row. Estimate it from stock-take differences: an ADJUST of minus 40 on a bin that issued 400 suggests 400 ÷ 440 = about 91% compliance, if the count itself is right.

Inventory accuracy and carrying cost matter too. Our guide to manufacturing inventory management software covers the wider set.

Common mistakes in tool crib data models

1. One table for everything

Putting gauges and inserts in the same structure forces either fake serial numbers on inserts or no history on gauges.

Split serialised and bulk from day one.

2. Editable stock quantities

If anyone can overwrite qty_on_hand, nobody can explain a difference later.

Every change must be a transaction with a type, a person and a timestamp.

3. No machine or work order on the issue

Without them you know the crib spent €30,000 on inserts last quarter, but not which part or machine drove it.

4. Treating a regrind as a new tool

Receiving reground tools as new stock resets their history and hides the max_regrinds limit.

Keep the same serial and increase regrind_count.

5. Calibration status stored only on a sticker

A sticker cannot stop a checkout. The due date has to live on the record, where the checkout step can block it.

6. A process slower than walking in

If checkout takes a minute of typing, people skip it and compliance falls. Badge scan, tool scan, done.

Once the crib records every issue and return, the same data feeds a full tooling cost of ownership report.

How Fabrico helps

Fabrico is an OEE platform with a full CMMS built in. It does not have a dedicated tool crib module, kiosk, vending machine integration or RFID.

What it does have covers the bulk stock side of the model: an inventory catalogue with min and max levels, deliveries and stock-takes. Per-employee checkout, loan times and overdue tracking are not part of it, and there is no automatic reorder: your team places the order.

QR codes on parts and machines let a technician scan both from the iOS or Android app, and consumption is recorded against the work order it was used on.

Because OEE, downtime and maintenance history sit in the same platform, the team can compare parts and tooling consumption with how each machine actually ran.

Want to see how your parts and consumables would look in Fabrico? Book a 30 minute demo with a Fabrico consultant, no commitment, or contact us with your questions.