Oilfield Tool Tracking Software: Serial Numbers, Rebuilds and Who Has What

Oilfield tool tracking software keeps one permanent record for every downhole tool, tied to its serial number, so each rebuild, each replaced part and each movement is attached to the tool rather than to a person's memory or a spreadsheet row. A downhole tool has a serial number, a rebuild history and a running cost. Most workshops keep all three in different places.

That split is the real problem. The serial is on the tool, the rebuild history is in a paper manual in a filing cabinet, and the question "where is it now?" lives in a supervisor's head or a message thread. Each place is fine alone. Together they cannot answer the questions a workshop is asked every week.

Start with the unit that matters: the tool, identified by its serial number. Everything else hangs off that.

A useful record holds four things:

If any one of these lives somewhere else, you have a tool register, not a tool history. We go deeper on the first two in what a downhole tool workshop needs to track.

Identity. The serial, the tool type, and the configuration it was built to. Two tools of the same type often carry different part counts, and the record needs to know which build it is.
Parts. The serialised components inside it, and the batch-tracked parts counted per build. The parts list comes from your own manual, not from a generic template.
Cycles. Each time the tool comes back from a job, a new cycle opens. Inspection, decisions on each part, tests and release all belong to that cycle.
People and time. Who made each decision, who signed, and when.

How do you track a downhole tool through a rebuild?

A rebuild is where records usually die. The tool arrives, gets stripped, parts are inspected, some are reused, some replaced, and it goes out again. On paper, that is a few pages in a manual. In a register, it is often one edited cell.

The better pattern is to treat every return as its own cycle:

Because each cycle is kept, you can open a tool next year and see what it looked like at this rebuild, not just what it looks like now. The detail on serialised parts across rebuilds is in tracking serialised parts across tool rebuilds.

The tool is received, which opens a cycle against its serial.
Each part slot gets a decision: reuse, replace, review or scrap, with a note.
A replaced serialised part is recorded as a change: the old serial out, the new serial in, who did it.
Tests are recorded against the cycle.
The tool is released only when the cycle is complete.

Why do spreadsheets fall over?

Spreadsheets fail at the exact moment the work gets interesting.

None of this is a criticism of spreadsheets. They hold a current state well. A tool workshop needs a history, and a history is append-only: a correction sits beside the original with the person and time, and the original stays.

Parts move between tools. A pump stack from one tool ends up in another. A row per tool cannot say that, so the history of the part is lost.
Edits overwrite. Change a serial in a cell and the old value is gone. There is no record of who changed it or why.
Two people, one file. Two technicians update at once and one set of changes wins silently.
No decision trail. Reuse or replace is a judgement. If two people disagree, a spreadsheet keeps whichever was typed last.

How do you know which tool is where?

"Who has what" is the question that costs the most time, because the answer changes daily and the person asking is often the client.

The practical answer has two parts. Each tool carries a stage in the workshop (received, in inspection, awaiting release, ready), so the workshop floor is visible. And movements in and out, to a job or a location, are recorded against the serial with a job number and a date. If those movements already exist in your ERP, importing them as a CSV is cheaper than retyping them.

The same logic is behind custody trails for company assets: a record of who held a thing, from when to when, settles an argument before it starts.

Where does Wurxa fit?

Wurxa Workshop is the oilfield tool module in Wurxa. You set up each tool type once from your own manual: the parts list, how many of each part a build takes, which parts carry a serial and which are batch tracked, and the tests and sign-offs the manual records. Tools are then added by serial, singly or by CSV import with a preview before anything is saved.

From there each return opens a cycle, each part gets a decision, a disagreement between two people is held for a supervisor to resolve with a note, and every change is written to an activity trail with the person and time. Nothing in the history is overwritten.

Technicians do not have to change how they work. They fill in the same paper manual, and a scan or phone photos of the filled pages are read against the tool type's setup. The reader proposes each line, flags anything unclear, such as a serial struck through with a new one written beside it, and a person confirms before it is saved.

There is a plan that costs nothing to start with, and paid plans for larger tool counts. See Wurxa pricing for the current plans, and Wurxa Workshop for oilfield tools for how it works in more detail.

What is the first step if our records are on paper?

Do not try to digitise the whole archive. Pick one tool type, write down its parts list from the manual, and enter the tools you have of that type by serial. Run the next real rebuild through it. One tool type done properly teaches you more about your own process than a month of planning, and it gives your team something real to react to.

If you want to try that with your own manual, ask Sara on wurxa.com, or message us and we will help you set up the first tool type.

Put the workflow into practice.

Start with every Wurxa feature for 14 days. No credit card required.

Start free trial

Frequently asked questions

What is oilfield tool tracking software?

It is software that keeps one record per downhole tool, identified by serial number, with every inspection, rebuild, test and movement attached to it. The point is that anyone can open a tool and see what it is made of, what was done to it and where it is now.

Is a spreadsheet enough to track oilfield tools?

It works for a handful of tools and breaks as soon as parts are swapped between tools or two people edit it at once. A spreadsheet holds a current state, not a history, so it cannot tell you what a tool looked like at the last rebuild or who changed a serial.

How do you track parts that are replaced during a rebuild?

Each serialised part is recorded against the tool it sits in, and a replacement is recorded as a change with the old serial, the new serial, the person and the time. Parts tracked by batch are counted per rebuild instead of by serial.

Do technicians have to stop using paper manuals?

No. In Wurxa Workshop technicians keep filling in the same paper manual at the bench, and the filled pages are scanned or photographed afterwards. The software proposes each line and a person confirms it before anything is saved.

Can tool movements from our ERP be brought in?

Wurxa Workshop imports tool movements from a CSV export, with serial, from and to location, job number and date. A serial it does not recognise goes to a needs-attention list rather than being guessed. There is no live two-way ERP connection today.