Inventory & Procurement

Tools & Equipment Management

Right tool, on the job sheet, in one trip

A technician gets a breakdown call, walks to the tool crib, and only there discovers he needs a clamp meter he didn't carry down. Or a contract worker services a hydraulic press with a torque wrench that was never calibrated for that spec — nobody thought to check because nobody wrote down which instrument the job needed in the first place. Tools & Equipment Management in AssetAI fixes the first problem cleanly: it standardises which torque wrench, multimeter, or gauge belongs to which asset, and puts that list on the job sheet before the technician leaves the store. It does not try to solve the second problem, and we'd rather tell you that upfront than let you find out later.

What Gets Standardised

Every asset in your registry can carry a list of the tools and instruments needed to service it. This sits alongside three other requirement blocks on the same asset record — required skills, safety measures, and criticality — so that when someone opens an asset, they see the full job standard in one place: who can do this, what they need to carry, what precautions apply, and how critical the machine is. This is deliberate. A tool list without the skill and safety context next to it is just a shopping list; together, the four blocks describe what a competent job actually looks like on that specific machine.

  • Tool and instrument masters are maintained centrally, under the masters permission — one list, one naming convention, no technician inventing his own shorthand for "the yellow multimeter."
  • Each asset then maps to whichever tools from that master list its maintenance work requires.
  • The mapping is a simple link between asset and tool, nothing more — no quantity field, no serial number, no date attached to it, because that isn't what this record is for.

If your plant is still working off memory and word-of-mouth for "what does the fitter need for this compressor," this is the layer that turns it into a written standard anyone can look up, including a new contract hire who's never touched that compressor before.

From Asset Record to Job Sheet

The real payoff shows up when a work order gets raised. The tool list mapped to that asset loads automatically onto the work order form and prints on the job sheet — so the technician sees it before he leaves the store, not after he reaches the machine and finds the wrong kit in his bag. If an asset has no tools mapped yet, the job sheet doesn't leave a blank space or throw an error; it prints "No specific tools mapped — standard toolkit," so the document is always complete and technicians know a plain toolkit is genuinely sufficient for that job rather than wondering if something was missed.

This connects directly into how work orders get planned and dispatched, but the tool list itself lives on the asset, not on the work order — map it once per asset and every future job sheet for that asset carries it forward.

What This List Deliberately Does Not Track

This is the part worth being explicit about, because plants often expect a tool master to behave like a mini tool crib, and it doesn't.

  • There's no tool inventory or stock count — the system doesn't know how many multimeters you own, only that a multimeter is needed for this asset.
  • There's no issue, return, or custody log. It won't tell you which technician currently has the torque wrench, and it won't chase anyone to bring it back.
  • There's no calibration due date, no certificate record, no calibration alert. If your quality system requires calibration-driven control of measuring instruments — relevant if you're working toward ISO 9001 or similar frameworks under ISO standards — that tracking has to happen outside this module today.
  • There's no cost, purchase, depreciation, or condition tracking on tools. A tool record here is just a code and a name — reference data, not an asset in its own right.

A tool, in this system, is metadata that answers "what should I carry," not a physical object with a life-cycle of its own.

If You Actually Need to Stock or Value Tools

Some plants do need quantity, cost, and stock movement against their instruments — a torque wrench that's a controlled, calibrated, capital item is a different animal from a spanner that's part of every fitter's kit. For anything you need to stock, issue, return, or value, the correct object in AssetAI is a Spare, not a Tool. Spares carry stock levels, movements, and cost the way tools deliberately don't. If your torque wrench needs a quantity on hand, a reorder point, or a purchase value, model it as a spare and let the tool master stay what it's meant to be: a reference list of what's required, unclouded by stock-keeping logic it was never built to carry.

Getting Started Without Overbuilding It

Tool masters ship empty for every company — there's no default library of instruments waiting to be pruned. That's a feature, not a gap: you add the torque wrenches, multimeters, and gauges that actually exist on your plant floor, in the terms your own technicians use, rather than editing down a generic list built for someone else's machines.

  • Creating tool masters needs the masters permission, so the naming stays controlled by whoever owns your standards, not created ad hoc by every planner.
  • Mapping tools to an asset needs asset edit rights — the same permission gate that protects the rest of the asset record.
  • The uniqueness constraint on the asset-tool link means you can't accidentally map the same tool twice to one asset; the list stays clean by design.

Start with your critical assets — the ones already flagged through criticality assessment — and map their tool requirements first. A multi-lingual shop floor with rotating contract labour benefits most from job sheets that spell things out plainly, in a shared vocabulary, rather than relying on the senior fitter's memory of what the old machine needs.

Where This Fits in a Broader Maintenance Standard

Tool mapping is one input into a larger discipline — total productive maintenance thinking asks you to standardise the small procedural details, not just the big PM calendars, and a printed, consistent tool list is one of the smaller but more visible ways that shows up on the floor. It sits well next to your preventive maintenance schedules and your asset criticality work, each covering a different layer of the same job standard. If you're building this out plant-wide, our use cases page has more on how manufacturing units in India structure these masters, and if you want a fuller walkthrough, book a demo and we'll show you the asset record end to end.

Rolling This Out Without It Becoming Shelfware

The mistake most plants make is trying to map every tool to every asset in one sitting. That week never comes free, and the master list ends up half-built, which technicians then distrust more than no list at all. A cleaner rollout goes asset-by-asset, starting with your top criticality machines — the same list you'd already have from a criticality assessment — and expands as work orders naturally surface gaps. If a technician flags a missing instrument on a job sheet, that's the trigger to add it, not a quarterly audit.

  • Start with high-criticality and high-breakdown-frequency assets; a 40-machine unit doesn't need all 40 mapped before the feature earns its keep.
  • Assign one person the masters permission for tool creation — if everyone can add tools, you'll get "Multimeter," "multi-meter," and "MM Digital" as three separate entries within a month.
  • Let asset-edit rights (not masters rights) stay with the planning engineer who actually knows the job — mapping tools to assets is a different call from naming the tools.
  • Review the "No specific tools mapped" job sheets periodically. A long list of them usually means real gaps, not genuinely toolkit-only jobs.

What to Watch, Not What to Count

There's no percentage to report here — no "tool availability rate" or "mapping compliance score" exists in the data, and we won't invent one. What you can watch is simpler and more honest: are technicians walking back to the crib mid-job because the job sheet didn't warn them? Are contract workers asking supervisors which spanner size a job needs, on a machine that's been running for years? Both are signs the mapping is thin or stale, and both are fixable by editing the asset record, not by adding a dashboard.

Where This Genuinely Doesn't Fit

If your real pain is a tool crib — technicians signing tools out, supervisors chasing returns, someone losing a borescope for three months — this module will disappoint you. There's no issue log, no custody trail, no "who has the clamp meter right now." That's a different system with different data (quantities, holders, due-back dates), and pretending a reference list can do that job only delays the real fix.

The same honesty applies to calibration. If your quality system requires a torque wrench certified to a spec, with a due date and an alert before it lapses, AssetAI's tool mapping will not track that — there's no calibration due date or certificate field here. Plants operating under ISO calibration requirements should treat this as a naming and job-standard tool, not a calibration control, and keep that governance in whatever system already owns certificates.

When a Tool Is Actually a Spare

Torque wrenches and multimeters are usually genuinely reference tools — one wrench, many jobs, no consumption. But some "tools" in a plant are really consumables with a shelf life: grinding wheels, test lamps that burn out, gauges that get damaged in the field. If you find yourself wanting to know how many are left in stock or what they cost, that's a sign the item belongs in Spares, not in the tool master — spares carry stock, movement history and cost; tools deliberately don't.

Fitting Into the Bigger Picture

None of this replaces a preventive maintenance schedule or a work order system — it feeds them. The tool list only becomes useful the moment it's attached to a real job sheet, printed and carried to the machine. Plants building out a full maintenance management practice, or benchmarking against TPM discipline, will find this one of several building blocks — see the full features list or book a demo to see how it sits alongside skills and safety on a live asset record.

Tools & Equipment Management FAQs

Which torque wrench or multimeter should a technician carry for a specific press or motor in our plant?

AssetAI answers this directly on the asset record itself — each machine carries its own list of the tools and instruments needed to service it. When a technician opens a job for that asset, this list appears on the job sheet before he leaves the tool crib, so he picks up the clamp meter or torque wrench for that specific machine rather than guessing or walking back later. This list sits next to the required skills, safety measures, and criticality rating for the same asset, so the tool requirement isn't an isolated note — it's part of the full job standard. You can see how this fits with the rest of the asset registry on the features page.

Does AssetAI track calibration due dates for torque wrenches and measuring instruments?

No — AssetAI standardises which tool or instrument belongs to which asset, but it does not verify whether that instrument is currently calibrated for the job. The tool list on the asset record tells a technician what to carry; it doesn't check the calibration certificate against the spec required for that particular hydraulic press or gearbox. This is a deliberate boundary we're upfront about rather than a hidden gap. If calibration tracking is something your plant needs solved alongside tool standardisation, it's worth discussing directly — you can raise it when you book a demo.

Where do I maintain the master list of tool and instrument names so every technician uses the same terminology?

Tool and instrument masters are maintained centrally, under the masters permission, so there is one list and one naming convention across the plant. Instead of each technician inventing his own shorthand for "the small torque wrench" or "the yellow gauge," the name used on the asset record's tool list is the same name used everywhere else in the system. This central control matters because the tool list only works as a reliable job requirement if everyone means the same physical instrument when they read it. It's the same registry logic used across the rest of a CMMS, where consistency in naming keeps records usable.

How does AssetAI connect tool requirements to the skills and safety precautions needed for a job?

They sit together on the same asset record, as four linked requirement blocks — required tools, required skills, safety measures, and criticality. Opening an asset shows all four at once: who is qualified to do the work, what they need to carry, what precautions apply, and how critical the machine is to production. The reasoning is that a tool list alone is just a shopping list; it only becomes a real job standard when read alongside who's allowed to do the job and what safety steps apply. This structure is part of how asset records are built across features in AssetAI, not a separate module bolted on.

Can a contract worker see which tools and instruments a job requires before starting work on our equipment?

Yes — the tool and instrument list attached to the asset appears on the job sheet before the worker leaves the store, whether he's an in-house technician or a contractor. This means the list of what to carry is visible upfront rather than discovered mid-job at the machine. What it does not do is confirm that the specific instrument a contractor brings is calibrated to the correct spec for that asset — that verification sits outside this feature. For plants that rely heavily on contract labour, this visibility is worth reviewing alongside other use cases to see where the boundary of the feature lines up with your process.

Does the tool requirement list also show how critical a machine is, so we can prioritise which breakdowns get attention first?

Yes — criticality is one of the four requirement blocks stored on the same asset record as the tool list, alongside required skills and safety measures. When someone opens an asset, they see its criticality rating right next to what needs to be carried for the job, rather than having to look it up separately. This keeps the tool list from being read in isolation — a low-criticality machine and a high-criticality one might need the same gauge, but knowing which is which on the same screen helps with sequencing work. More on how criticality and other asset fields are structured is covered under industries.

If a technician borrows a tool for one job but forgets to return it, how do we track where it went?

AssetAI logs tool check-outs with technician ID, job reference, and expected return date. When a tool isn't checked back in by the deadline, the system flags it and notifies supervisors. You can then search which technician has the tool and follow up. This prevents tools disappearing into workshop corners and helps recover lost equipment quickly.

See Tools & Equipment Management on your own machines

A 30-minute demo on your plant, not our slides.

Put your plant on autopilot

Free for 14 days. Import your Excel, print QRs, and see your first honest downtime report this week.