Short answer
A tools-and-materials list names every tool, consumable and part a procedure needs, ideally with quantities and identifiers. It lets a planner check preconditions, lets a perception team build the object set a task requires, and gives annotators a vocabulary. It does not show how the objects are handled, and the list says nothing about where they are right now.
Why this small asset punches above its size
Many procedures open with a short block: "You will need: 10 mm socket, torque wrench, two M6 bolts, lint-free wipes." It is easy to ignore. For a robotics buyer it is one of the cleanest links between text and the physical world, because it turns a paragraph of instructions into a set of named objects.
That set answers three practical questions. Which objects must a perception system recognize for this task? What must be on hand before the first step? And what is missing when a task fails because something was not where it was expected?
Compared with a full SOP, the list is short, structured and usually less sensitive. Compared with a catalog, it is task-specific. That combination is the reason to source it separately.
Forms the list takes in real workplaces
- Header blocks in SOPs and work instructions listing tools, PPE and consumables.
- Bills of materials (BOMs) attached to assembly or repair procedures.
- Kitting lists and pick lists that group parts per job.
- Job packs and work-order parts lists from maintenance systems.
- Setup sheets with tooling and fixtures for a machine changeover.
- Illustrated assembly manuals with parts callouts. A published example, IKEA-Manual, pairs 102 IKEA objects with their assembly manuals and annotates decomposed parts, assembly plans, manual segmentation and 2D-3D correspondence (Wang et al., 2022). It shows what a fully structured version of this link can look like, though it concerns furniture, not workplace procedures.
See illustrated assembly manuals for the manual-based route.
What this data can support and what it cannot
It can support:
- Precondition checks. A planner can test whether required items are present before it starts. See preconditions and postconditions.
- Defining a workplace object set for perception and evaluation, as in a workplace benchmark object set.
- Linking steps to object classes so annotators label the right things.
- Scoping coverage: counting distinct objects across a task family shows how long the object tail is.
It cannot support:
- Handling. Knowing a torque wrench is needed does not teach a robot to grip it, align it or apply torque. Control needs robot or teleoperation data, not lists or SOPs alone.
- Appearance. A name is not an image. Without a catalog entry or photos, a list does not train a detector. See object attribute schema for the data you add.
- Substitutes and variants. The list names the nominal tool; sites often use alternatives.
- Location. A list gives need, not storage position.
Quality problems typical of these lists
Lists tend to be copied from older procedures and are rarely audited. Typical defects include generic entries ("tools as required"), brand names where a type would do, mismatched quantities, items used in steps but absent from the header, and items listed that no step uses. A supplier can only be confident in the list if someone reconciled it against the steps.
Illustrative per-procedure object table
The table below is Illustrative. Identifiers and values are synthetic.
| Field | Example | Purpose |
|---|---|---|
procedure_id | proc_0877 | Link to the procedure |
step_ref | 4 | Where in the procedure the item is first used |
item_name | "torque wrench, click type" | Surface form from the document |
item_class | tool / consumable / part / PPE | Routes to different handling |
quantity | 1 | Precondition check |
identifier | asset_tag_0442 or catalog ID | Link to an object record |
substitutes | "adjustable wrench (site_017 only)" | Variants seen in practice |
If you are specifying this as a delivery, include a row-level flag for items that appear in the steps but not in the header, because the gap between the two is a quality signal.
Acceptance criteria you can set
- Reconciliation rate. What share of items named in steps also appear in the header list, and vice versa?
- Identifier rate. What share of items link to a catalog, register or asset ID?
- Specificity. How many entries are generic placeholders?
- Quantity and unit presence. Is every consumable quantified?
- Class coverage. Are PPE and consumables included, or only tools?
Preparation work to expect
Parsing header blocks out of PDFs, splitting multi-item lines, normalizing units, resolving brand names to item classes, and mapping to a shared object schema. Suppliers with structured systems (a maintenance database, a PLM tool) can often export lists directly; others need document parsing, as in procedure step schema work.
Questions to ask suppliers
- Are tools and materials stored as structured data, or only as text inside documents?
- Has anyone reconciled lists against the procedure steps?
- Do entries carry catalog, asset or part-number identifiers?
- Are quantities and units stated for consumables?
- Do any entries include customer-specific or proprietary part numbers?
- Are substitutions and site-specific variants recorded?
- Are PPE items listed separately?
- Who can license BOMs that originate with a vendor or manufacturer?
Permissions and provenance
Part numbers, supplier names and BOM structure can reveal sourcing relationships and product design. A BOM for a customer product may belong to the customer. Ask which lists were authored by the operator and which were supplied by manufacturers or clients. Removing part numbers is a preparation step, but it does not settle who may license the list.
Item names in the list only become useful when they match the site language, which is the job of a workplace glossary.
Discuss your requirements
If your project needs structured object lists linked to procedures, describe the task family, identifiers and permitted uses to SourceX. SourceX reviews the requirement and looks for US businesses that may hold suitable lists, checks the data and the supplier's licensing permissions, and follows up about potential sources. A request does not guarantee a match. Start at the procedures hub or the humanoid training data guide for neighboring asset types, and see the catalog listing for CAD and engineering files for the nearest existing category.
Discuss your humanoid training-data requirements with SourceX
Sources
- IKEA-Manual: Seeing Shape Assembly Step by Step — assembly manuals paired with parts, plans and 2D-3D correspondence.