Shared Fixtures and Gauges: A Reservation and Return Register

Before releasing two jobs that share a fixture or gauge, reserve the physical item for a defined time window, confirm its condition and record who will return it. A machine slot is usable only when the required tooling will also be ready.

This control is for the tool-room owner and production planner when a job waits for a fixture that appears available in the plan. Start with one frequently shared item. You need its unique identity, storage location, current holder, compatible jobs, condition status and next required time.

Make the physical item identifiable

“Assembly fixture” is too broad when several similar fixtures exist. Give each usable physical fixture its own identity and distinguish a complete assembly from a loose component. List the pins, clamps, stops and other parts that must accompany it.

Keep fixture condition and measuring-gauge status as different checks. A complete fixture can still be damaged. A gauge can be present but unsuitable for the measurement range or outside its approved control status. NIST's calibration guidance explains why there is no single recalibration interval for every instrument; requirements and instrument behaviour matter. Do not invent an annual interval for every gauge in the register.

Reserve time for the whole handoff

The conflict is 15 minutes even if Job A finishes on time. A calendar that shows only machining time misses the return and check. If Job A finishes at 10:50, the proposed ready time becomes 11:05 under the same 15-minute handoff assumption. The tool-room owner must confirm condition before marking the item ready.

This example does not prescribe a cleaning method or duration. Use the fixture's approved handling instructions and a measured handoff allowance.

Run issue and return as separate transactions

At issue, record fixture ID, job, machine, person receiving it, issue time, expected return and the complete-kit check. For a gauge, also record the applicable measurement range and approved status reference. Keep the physical tag readable and consistent with the digital identity.

At return, check the kit before accepting custody. Record missing parts, damage or a condition requiring review. A returned item should not automatically become available to the next job. Use states such as returned-awaiting-check, ready and held, with an owner for each transition.

If an operator passes the fixture directly to another cell, record that transfer. Otherwise the tool-room screen may still show the first holder while the second job is running. The planner should resolve reservation conflicts; operators should not have to negotiate competing priorities at the machine.

Handle loss, damage and urgent borrowing

When a clamp is missing, mark the fixture incomplete and name the person responsible for recovery. Do not substitute an unapproved clamp because its dimensions look similar. The responsible engineer decides whether an alternative is suitable and what validation it needs.

For an urgent borrowing request, show the displaced reservation and ask the planner to approve a revised sequence. Record the new return time and notify the next holder. A verbal promise leaves both jobs believing they own the same tool.

Start a pilot with five high-conflict tooling items. At each shift handover, check that every issued item has a holder and expected return, every upcoming reservation has a condition decision and every conflict has an owner. Measure jobs delayed by missing tooling separately from machining downtime. Set a local response target for overdue returns and review the exceptions daily.

Configure a shared-tooling register in Optiwise

Optiwise's no-code modules support relational records, date fields, calendar views, forms and event-based notifications. You can configure tooling records linked to production jobs, with issue, return and condition evidence. Our shop-floor planning already uses machine calendars, worker skills and availability; the configured tooling workflow adds the resource handoff your team needs.

This is a proposed configuration, not a claim that a dedicated fixture-reservation module is enabled in every installation. Define the conflict rule and test two competing reservations before release.

Questions about shared tooling

Should gauges and fixtures share one status field?

They can share location and custody fields, but keep condition, completeness and measurement-control status distinct. “Available” alone cannot express all three.

What is the first acceptance test for the register?

Reserve one item for overlapping jobs, issue it, return it with a missing component and confirm that the next job sees the unresolved conflict and hold.

Bring your shared-tooling list to an Optiwise demo so we can map custody, reservations and condition checks to your jobs.