Most pipeline pigging schedules are still set the same way they were decades ago, on a fixed calendar interval that has almost nothing to do with how fast wax, corrosion debris, or scale is actually accumulating inside a specific line. A pipeline running heavier crude in colder ambient conditions can build a restrictive wax layer in a fraction of the time a lighter, warmer line takes, and a schedule built around a company-wide average misses that difference entirely. The result is either an unnecessary run that adds cost and stuck-pig risk, or a skipped one that lets deposits build past the point a standard pig can safely clear. See how AI matches pigging frequency and pig type to what a line is actually doing at ifactory support.
AI Pigging Optimization
Stop Pigging on a Calendar. Start Pigging on What the Line Is Actually Doing.
AI that predicts wax and debris buildup rate from live flow, temperature, and pressure data, recommends the right pig type for current line conditions, and times every run before restriction risk or stuck-pig risk sets in.
Condition-Based
Scheduling driven by actual buildup rate, not a fixed calendar
5+ Pig Types
Matched to line condition and cleaning requirement
Feedback Loop
Every run's results refine the next schedule
Why "Every 90 Days" Is Usually the Wrong Answer
A fixed pigging calendar is easy to plan around, which is exactly why so many pipeline operators still run on one. The problem is that wax deposition, corrosion debris accumulation, and scale buildup do not follow a calendar, they follow crude composition, ambient and process temperature, flow velocity, and how those variables have shifted since the last run. A line that was pigged confidently on schedule for two years can suddenly accumulate wax three times faster after a change in crude source or a colder-than-usual season, and a fixed interval has no mechanism to notice that until flow restriction or a pressure drop forces the question.
Running too often carries its own cost too, and it is not just the direct expense of an unneeded pig run. Every trip increases cumulative wear on launcher and receiver seals, adds handling risk, and, if the wrong pig type is sent through a line that has not actually built up much deposit, can scrape bare pipe wall in a way that is not free of consequence either. The goal is not more frequent pigging or less frequent pigging, it is pigging at the point where a run is actually warranted by the deposit condition inside that specific line.
Calendar-Based
How most pigging schedules are still set today
A fixed interval applied uniformly, regardless of how fast that specific line is actually building up deposit.
Composition-Driven
What actually controls wax buildup rate
Crude wax content, flow temperature, and ambient conditions, all of which shift over a pipeline's operating life.
Both Directions
How a fixed schedule can fail
Over-pigging adds cost and stuck-pig exposure, under-pigging lets restriction and corrosion under deposit build unchecked.
Run-to-Run
What each pig run's debris data should actually inform
The next scheduled interval and pig type, rather than being logged and left unused until the following run.
Matching Pig Type to What the Line Actually Needs
Not every pig is built for the same job, and sending the wrong type through a line is a common cause of either an ineffective run or a stuck pig incident. The right choice depends on how much deposit has actually accumulated, the pipeline's internal condition, and its geometry.
Foam Pig
Lightweight and flexible, suited to lines with light deposit buildup, tighter bends, or where a lower-force cleaning pass is appropriate.
Cup Pig
Sealing cups drive liquid and debris ahead of the pig, effective for batching and general debris removal in straighter line sections.
Brush Pig
Wire or polyurethane brushes scrape hardened wax, scale, or corrosion debris from the pipe wall, suited to heavier, more adhered deposits.
Gel Pig
A chemical batch rather than a mechanical tool, used to dissolve and carry away wax in lines where mechanical pigging risk is elevated.
Smart / Intelligent Pig
MFL or UT-instrumented pigs that inspect wall thickness and metal loss rather than clean, run on their own inspection cadence distinct from cleaning pigs.
The Three Inputs That Actually Drive Buildup Rate
Predicting when a line needs pigging starts with tracking the conditions that actually cause deposit to form, not with waiting for a symptom like a pressure differential increase to show up first.
Fixed-Interval Scheduling vs AI-Driven Scheduling
Scheduling Approaches Compared
See Your Own Pigging Schedule
Find Out What Your Current Interval Is Actually Missing
Bring your current pigging schedule and recent run debris data to the call. We will walk through how AI-driven scheduling would compare against what you are running today.
How AI Actually Builds a Pigging Recommendation
The recommendation is not a single calculation, it is a continuous loop that gets more accurate every time a pig actually runs and reports back what it found.
1
Monitor Deposition Indicators
Flow temperature, velocity, differential pressure trend, and crude composition are tracked continuously per line.
2
Predict Buildup Rate
Wax and debris accumulation are modeled forward against current operating conditions, not a fixed historical average.
3
Recommend Pig Type
Predicted deposit thickness and composition are matched against pipeline geometry to select the appropriate pig.
4
Schedule the Run
A timing window is set before predicted buildup reaches a restriction or stuck-pig risk threshold, not after.
5
Analyze Run Results
Recovered debris volume and composition from the completed run feed directly back into the next prediction cycle.
What Actually Causes a Stuck Pig
A stuck pig is rarely a random event, it is almost always the downstream result of one of a handful of predictable conditions that a fixed calendar schedule has no way of anticipating.
Excessive Wax Buildup
Deposit has accumulated well beyond what a routine cleaning pass was designed to clear, common when an interval has run too long.
Geometry Mismatch
A pig selected without accounting for a tight bend radius or diameter transition the line actually contains.
Wrong Pig Type for Deposit Condition
A foam or cup pig sent through a line with hardened, heavily adhered deposit better suited to a brush or gel pass.
Insufficient Differential Pressure
Driving pressure too low relative to deposit resistance, causing the pig to lose momentum partway through the run.
What Condition-Based Scheduling Actually Changes
Schedule Matched to Actual Buildup
Condition-based timing versus a uniform fixed interval
Pig Type Matched to Line Condition
Predicted deposit profile driving selection instead of habit
Prior Run Data Actually Used
Debris findings feeding the next recommendation instead of sitting in a report
Not sure if your current pigging interval matches your actual buildup rate? Talk to our team and we will help you find out.
A Common Starting Point: The Interval Nobody Has Revisited
Most operators approaching this already have a pigging program in place, they simply have never gone back to question whether the original interval still fits current conditions. A typical starting point looks like this: an interval was set years ago based on early operating experience, crude source or seasonal conditions have shifted since, and the schedule has never been formally revisited because nothing has gone catastrophically wrong yet. Debris recovered from each run gets logged for compliance purposes and rarely feeds into a decision about whether the next interval should change.
The shift that actually improves outcomes starts with treating every completed run as new evidence rather than a closed event. Once deposit volume, composition, and pipeline condition indicators are tracked continuously and compared against the assumptions the original interval was built on, it usually becomes clear that some lines are being over-pigged relative to their actual buildup rate while others are running closer to restriction risk than anyone realized. That gap is exactly what a condition-based schedule closes.
Four Mistakes That Undercut a Pigging Program
Keeping a Fixed Interval After Conditions Change
Leaving a schedule set years ago untouched even after crude source, temperature, or flow rate has shifted materially.
Using One Pig Type for Every Line
Standardizing on a single pig type across a fleet with very different geometry and deposit conditions per line.
Not Feeding Run Data Back Into Planning
Logging recovered debris volume and composition without using it to adjust the next interval or pig selection.
Ignoring Geometry When Selecting a Pig
Choosing pig type based on deposit condition alone without checking it against the line's actual bend and diameter profile.
Frequently Asked Questions
How does AI actually predict when a pipeline needs pigging?
The prediction is built from continuous flow temperature, velocity, differential pressure trend, and crude composition data, modeled forward against how wax and debris accumulate under those specific conditions rather than a fixed historical average. As conditions shift, whether from a crude source change or a seasonal temperature swing, the predicted buildup rate updates accordingly.
Talk to our team about how this would apply to your specific lines.
Can this recommend pig type as well as timing, or just when to run a pig?
Both, since timing and pig type selection depend on the same underlying deposit prediction. A line predicted to have light, fresh wax buildup gets a different recommendation than one predicted to have hardened, heavily adhered deposit, even if both happen to fall due around the same date.
Book a scoping call to see how this would work across your pipeline fleet.
Does condition-based scheduling reduce the number of pig runs, or increase them?
It typically does both at once across a fleet, since some lines have been running on a schedule tighter than their actual buildup rate requires while others have been running looser than is safe. The net effect is usually fewer unnecessary runs on low-buildup lines and earlier intervention on high-buildup lines before restriction or stuck-pig risk sets in.
What role does smart pig inspection data play in this compared to cleaning pig scheduling?
Smart or intelligent pig runs, using MFL or UT inspection tools, follow their own regulatory and integrity-driven cadence focused on wall thickness and metal loss rather than cleaning. That inspection data is still valuable input, since a line showing active internal corrosion is one where cleaning pig frequency and debris analysis matter even more.
Reach out to our team for a sense of how the two programs fit together.
How much history is needed before AI scheduling recommendations become reliable?
A useful starting recommendation can be built from current operating conditions and available prior run debris data immediately, and accuracy improves further with each subsequent run as recovered deposit volume and composition confirm or adjust the prediction model. The system is designed to get more precise over time rather than requiring a long baseline period before it can be used.
Stop Pigging on a Guess.
Get a Condition-Based Pigging Schedule for Your Fleet
Bring your current pigging schedule and recent run debris data to the call. We will walk through how AI would time your next run and which pig type it would recommend.
Predictive
Buildup modeling
