Pipeline Pigging Programs Generate
200+ Data Points Per Run
The Challenge
Pig tracking data not recorded at passage points
Pig passage indicators at valve stations and intermediate points confirm the pig is moving through the line. Paper-based tracking misses passage times or records them inaccurately, making it impossible to calculate pig speed and identify restrictions.
Launcher and receiver procedures skipped or incomplete
Pig launching and receiving involves pressure equalization, valve sequencing, and vent procedures. Crews familiar with the process skip documentation steps because they know the sequence. When an incident occurs, the missing documentation becomes the problem.
Debris volume and composition not consistently measured
What a pig pushes out of a pipeline reveals internal conditions — wax, water, scale, sand, or corrosion products. Paper logs say "debris recovered" but rarely document volume, composition, or comparison to previous runs.
Pig type selection rationale undocumented
Choosing between foam pigs, solid cast, bi-directional, or gauge plates depends on pipeline conditions and objectives. The engineering rationale for pig selection is discussed verbally but rarely documented. When a pig gets stuck, nobody can explain why that pig was chosen.
The POD Advantage
Voice-logged pig tracking
Speak pig passage times at every tracking point along the route. POD calculates pig speed between stations and flags abnormal travel times that indicate restrictions, bypasses, or stalls.
Procedural step verification
Every launcher and receiver procedure step documented with timestamps and parameter readings. POD enforces that pressure equalization, valve sequences, and vent procedures are recorded before proceeding.
Debris tracking and trending
Debris volume, composition, and color documented at every pig receive. POD trends debris data across runs to show whether the pipeline is getting cleaner or conditions are changing.
Pig selection documentation
Pig type, size, durometer, and selection rationale documented before every run. POD links pig selection to pipeline conditions, run objectives, and historical run results for engineering traceability.
Pigging Operations Intelligence
“We ran a cleaning pig through a 24-inch crude line and recovered 400 gallons of debris. But nobody recorded the debris composition or volume at the receiver. When engineering asked what we pulled out of the pipe, all we had was a photo of a dirty pig trap.”
— Pigging Coordinator, Crude Oil Pipeline Operator
Industry-Specific KPIs That Update Themselves
POD tracks hundreds of KPIs from a 5-minute voice report. Here are just 2 of them.
Safety Performance
Earned Value Performance
Both cost and schedule under pressure
These update in real time from a 5-minute voice report. No spreadsheets. No data entry.
Frequently Asked Questions
Turn Pig Run Data Into Pipeline Intelligence
See how POD captures complete pigging operation records from launcher to receiver.