Pipe Tracking on Pipeline Projects: Why You Need Your Own Record

Line pipe is one of the largest single line items on a pipeline project, and on a lot of projects it's the one the owner has the least direct visibility into.

‍

That's not a criticism of anyone. It's how the supply chain is set up. The mill keeps its records. The coating facility keeps its own. The railroad has a manifest. The contractor runs a tracking system that works for the contractor. By the time a joint is strung along the right-of-way, it has passed through half a dozen hands, and each of them has a record - none of which belongs to you.

‍

If that describes your project, you might not have a problem. Plenty of operators run this way and reconcile at the end. But a lot of the project teams we talk to have found themselves in the same spot: needing to answer a question about their own pipe, and realizing the answer lives in someone else's system.

Where the pipe record usually lives

On most projects the record is spread across four places:

‍

• Mill and coating records. Accurate, but they describe what was shipped - not what arrived, or where it went after.
• The contractor's tracking system. Built to manage the contractor's work and support the contractor's invoicing. It's not wrong. It's just not yours.
• Yard counts. Physical inventories, done periodically, usually by hand.
• Spreadsheets. Someone on your team stitching the other three together.

‍

Each of those is a legitimate source. The gap is between them.

Four questions that get hard to answer with someone else's data

You may recognize some of these.

‍

"Do we have enough pipe in the yard for Monday?" Stringing is scheduled. The crew is mobilized. Whether there's 7,000 feet of line pipe and 12,000 feet of heavy wall actually sitting in the yard - not on a rail car, not in transit - is a question that shouldn't take a phone call and a drive to answer.

‍

"The contractor says the joints are short." A complaint about average joint length affects pay items. If your answer depends on counting, you're negotiating. If your answer is "440 joints, averaging 75 feet, here's the list," you're done.

‍

"Are we paying for pipe we haven't received?" Invoices tied to shipping records mean you may be paying for pipe that's still on a rail car. Invoices tied to physical acceptance mean you pay for what's in your yard.

‍

"Where did the last thirty joints go?" Pipe walks. Sometimes it's a paperwork error and sometimes it isn't. Either way, finding out at the closeout inventory is the expensive way to find out.

‍

None of these are exotic. They're Tuesday. And they share a cause: the record of your pipe isn't being kept by you.

We can't tell you whether this is your problem. Here's what we built for the teams where it was.

Cobra is Steel Shire's pipe tracking application. It gives the owner an independent record of every joint, from the mill to the right-of-way, that the owner controls.

Every joint, seven stages

Cobra follows pipe through the full journey: rolled at the mill, coated, loaded to rail, offloaded at the spur, stacked in the yard, loaded to truck, and delivered to the ROW for stringing.

‍

The first two stages are tracked as running counts - how much has been rolled, how much has been coated - so you always know where the order stands against what's been delivered. From rail onward, tracking moves to the individual joint: each one is recorded as it's offloaded, accepted into the yard, loaded out, and delivered to the ROW. That's the stretch where pipe changes hands most often and where an owner's own record matters most. Receipt is a recorded event, not an assumption.

Acceptance happens on a phone, at the yard

Inspectors accept pipe into the yard from a phone, not a tablet with a legacy interface. Acceptance takes seconds, which means it actually gets done at the moment the pipe arrives rather than reconstructed later. We've heard from multiple inspectors in the field that this is much easier than the systems they've used in the past.

Inventory is live

At any point, Cobra shows what's physically in the yard by type and footage. The Monday question answers itself.

You pay for what you've accepted

Because acceptance is a recorded event, payment can be tied to it. Pipe on a rail car isn't accepted pipe.

The data outlasts the project

Cobra keeps the history. Joint-length trends from similar projects in the same region inform the next estimate. Surplus pipe shows up during the project - not after - so a diameter you don't need can be released to a project that does.

Unused pipe moves with you to the next project

Surplus pipe on one project is inventory on another, but only if the record moves with it. Cobra can transfer accepted joints from one project to the next today, with their history intact, so the receiving project starts with a real count instead of a guess. That transfer is a process we run with you right now; a native, self-serve transfer is on the roadmap and in development. If moving pipe between projects is something you do often, tell us - it's shaping how we build it.

What Cobra is not

It isn't a replacement for the contractor's system, and it doesn't ask the contractor to change how they work. It runs alongside. The point is that when the two records disagree, you have your own to compare against - and both sides are looking at the same information, which tends to resolve discrepancies quickly.

It also isn't a judgment about your contractor. Good contractors run good systems. The owner still benefits from an independent record.

How it fits with the rest of the project

Cobra connects to the same map the rest of the project runs on. When a centerline changes in Arpium, the pipe requirement updates with it - line pipe and heavy wall. Daily construction reports in Havoc tie back to the same joints. At closeout, the pipe record, the daily reports, and the tract data are one record, not three.

Common questions

We already use the contractor's tracking system. Why would we need another one? You might not. If the contractor's data has always matched your invoices and your closeout inventory, keep going. Cobra is for owners who want their own verification - the same reason a project manager keeps their own daily report even when the contractor files one.

Does it work offline? Yes. Rail spurs and pipe yards don't always have signal. Acceptance records sync when the device reconnects.

What does it take to get started? Your joint list from the mill, your yard locations, and a short session with us to configure the stages the way your project actually runs. Most teams are accepting pipe within days.

Can we use it on one project first? That's how most teams start.

‍

If any of the four questions above sounded familiar, book a demo on the left, and we'll walk through Cobra on a real project structure and you can decide whether it fits yours.

‍