Tracking Serialized Parts Across Tool Rebuilds: From Paper Manuals to a Searchable History

Why paper manuals lose the part's history

A paper maintenance manual is organised around the tool. Page after page lists the slots in that tool's parts list, and for each slot the technician writes the serial that went in, ticks the inspection box and signs. As a record of one rebuild of one tool, it works well.

The problem shows up when the question is about a part instead of a tool:

• Parts move. A housing removed from one tool goes to quarantine, is inspected, returns to stock and is fitted to a different tool months later. Its history is now split across two tools' manuals.
• Serials get struck through. When a part is replaced, the technician strikes through the old serial and writes the new one beside it. On paper that is clear. In a spreadsheet, someone has to notice it and type both.
• Retyping introduces errors. Every time a serial is copied from paper into a spreadsheet or ERP, an O becomes a 0 or a digit is dropped. A wrong serial does not look wrong; it just breaks the chain.
• Nobody can search a cabinet. When a part fails on a job, the question "which other tools has this part, or this batch, been in?" takes hours, if it can be answered at all.

What a searchable part history needs

To follow a part across rebuilds, the record has to be organised around the part's serial as well as the tool's. In practice that means five things.

1. One history per part serial

Every time a rebuild fits a part, inspects it, replaces it or removes it, that event is written to the part's own history with the tool, the cycle, the person and the time. Looking up the serial then shows the tools it has been in, every inspection decision, who signed and when it was replaced.

2. One part, one place

A part cannot be in two tools at once. If a manual records a serial that is already on record in another tool, that should stop the line for a person to resolve rather than quietly moving the part. The same applies to removed parts: a part taken out goes to quarantine until someone decides what happens to it.

3. Lots for consumables

Not everything carries a serial. Fasteners, springs and O-rings are tracked by batch or lot. The history for those is "which lot went into which build, and how much", with the stock count moving at the same time. A lot that has expired should be flagged before it goes into a build, not discovered afterwards.

4. Corrections beside the original, never over it

A traceability record is only as good as its weakest edit. When something on record turns out to be wrong, the correction should be recorded as an amendment beside the original, with the person and the time, so the history shows both what was believed and what was corrected.

5. Search that understands serials

A history is only useful if you can find it. Search should cover tool and part serials, part numbers, batch numbers, shop orders and job numbers, and rank an exact match above a partial one.

Wurxa Workshop keeps all five: history per part serial across tools, a serial on record elsewhere blocked rather than moved, consumables by lot with stock deducted at the rebuild, amendments beside the original, and one search box across serials, lots, shop orders and jobs.

Getting from paper to a searchable history without retyping

The obvious way to build that history is to type every filled manual into a system. It is also the reason most attempts stall: nobody has time to retype forty lines of serials per rebuild, and the typing is where errors come in.

Wurxa Workshop takes a different route. Technicians keep filling in the same manual on the bench, with the same sign and witness columns. Afterwards, someone takes phone photos or a scan of it and uploads it. Then:

When the manual is applied, every part event lands in each part's own history, stock moves lot by lot, and the original scan stays attached to the cycle.

In our own reading test on a real, filled maintenance manual, all 79 serial entries were read correctly or flagged for a person to check, none was wrong without a flag, and all 17 struck-through replacements were caught.

• Wurxa reads the page and proposes each line. It reads the parts list, the serials, the batch numbers and the ticks, and compares them with what the tool had last cycle.
• Two independent readers read every page. Where they disagree, the line is flagged.
• Strike-throughs are proposed as replacements. A serial struck through with a new one written beside it is proposed as a replacement of the old part by the new one. A replacement only counts when the printed serial it replaces can be read.
• Doubt goes to a person. An entry written over, an unclear tick or an unreadable value is flagged and shown beside an enlarged crop of that row from the page, so the technician can type the value or keep the one already on record.
• A person confirms. Every flagged line is confirmed, edited or rejected on its own; only lines with nothing flagged can be confirmed together. Nothing is saved until a person confirms it.
• You see the effects before you apply. Before applying, Wurxa shows what the manual will do: parts reinstalled, replaced and recorded for the first time, stock per lot before and after, and the release checks it affects.

Starting with the history you already have

You do not need to digitise years of manuals first:

• Set up each tool type once. Enter the parts list by hand or from a CSV, or upload the manual and let Wurxa draft the parts list for a supervisor to check. Mark which lines carry a serial and which are batch tracked.
• Import your tools. A CSV of serials, tool types and configurations, with a preview before anything is saved.
• Upload each manual as tools come back. Every rebuild from now on adds to the part histories automatically. Within a few cycles, the parts that move most have a full trail.
• Use search when a question comes. When a part fails or a customer asks, look up the serial or the lot.

What it gives the workshop

Wurxa Workshop is built in the UAE for oil and gas workshops in Abu Dhabi, Mussafah, ICAD, Dubai and across the region. It is free for 10 tools, 3 staff and 5 document reads a month, with no card and no time limit. Start free, or see how Wurxa Workshop tracks tools and parts and book a 20-minute walkthrough with one of your own filled manuals.

• Answers in minutes, and fewer typing errors. Serials are read from the page and checked by a person, not copied by hand.
• Records ready for an audit. Quality audits, such as API Q1/Q2 or ISO 9001 audits, ask to see the per-serial maintenance, inspection, test and release records. With every part event on file, never overwritten, those records are an export rather than a project. (Software keeps records; it does not certify a workshop.)
• No change on the bench. Technicians keep the manual they know.