Skip to content
English
  • There are no suggestions because the search field is empty.

Pipelines and Pigging

 What is the Pipelines Module?

The Pipelines module in EZ Ops is used to document pipeline structure, track pig and batch activity, manage pigging schedules, and record right-of-way inspections. It connects sender locations, receiver locations, and the line segments between them into a single organized view.

Key point: Every pig sent is tracked from the sender to the receiver — it stays in a "pending" state until it is received, giving operators and foremen a live view of what is in the pipeline at any time.

Why Pipelines Matter

The Pipelines module is essential because:

  • Pig tracking - Know exactly which pigs are in the pipeline and how long they have been pending
  • Schedule compliance - Pigging schedules ensure lines are pigged at the required frequency, with a full history of all activity
  • Documentation - Every pig send and receive event is recorded, including form data, comments, and the operator who performed the action
  • Right-of-way inspections - Pipeline segment inspections are tracked on schedule using the same inspection system as other inspectable items
  • Batching records - Batch events (chemicals sent down the line) are documented alongside pigging activity for a complete pipeline history
Pipeline Structure

A pipeline in EZ Ops is built from line segments organized into line groups, connected from one or more senders to a single receiver:

  • Sender - The location where a pig or batch is launched
  • Receiver - The location where pigs are received after travelling through the line
  • Line segments - The individual licensed or physical pipe segments that make up the route
  • Line groups - Collections of segments organized from each sender to the receiver

Pipelines can have one sender (simple) or multiple senders (complex), each tracked independently. Each sender can have its own pig size requirement, pigging schedule, and pigging form.

Pigging Schedules

Pigging schedules track how frequently each sender in a pipeline needs to be pigged:

  • Each schedule is linked to a specific sender location and a schedule type (e.g., Foam Pig, Gauge Pig, Inspection Pig)
  • Schedules have a last sent date, a next send date, and a frequency
  • Due and upcoming pig schedules appear on the dashboard so operators can see what needs to be done
  • Sending a pig always resets the schedule — regardless of how many cycles were missed, the schedule resets from the date the pig was sent
  • Pigging schedules use the same repetition types as other schedules (Dynamic, Static, or Window)
Pig Types and Requirements

Each sender can be configured with a required or recommended pig type:

  • Required pig type - Sending any other type of pig requires the operator to enter a reason
  • Recommended pig type - The form pre-fills with the recommended type, but the operator can change it without a reason
  • If no pig type is set, the pig size displayed to operators is determined in this order: required pig type → recommended pig type → custom pigging size → calculated minimum size
How to Send a Pig
  1. Navigate to the sender location - Go to the plant or field location that has the pig sender
  2. Open the Senders section - Use the EZ-Nav to find Senders
  3. Select the correct sender - Find the sender for the pipeline you are pigging
  4. Click "Send Pig" - This opens the send pig workflow
  5. Complete the pigging form - If a pigging form has been configured for this pig type, fill out all required questions. Pigging forms have two sections:
    • Sending section - Questions that apply when launching the pig
    • Receiving section - Questions that become available when the pig is received at the other end
    • Questions not assigned to a section are available at both stages
  6. If no form is configured - Confirm that the pig has been gauged using the checkbox and enter any relevant comments
  7. Submit - The pig is now in a pending state and will appear in the pending pigs list until received
How to Receive a Pig
  1. Navigate to the receiver location - Go to the location that has the pig receiver
  2. Open the Receivers section - Use the EZ-Nav to locate the receiver
  3. Find the correct pending pig - Locate the pig in the list of pending pigs for that receiver
  4. Click "Receive" - This opens the receive workflow
  5. Complete the receiving section of the pigging form - Fill out any questions assigned to the receiving section
  6. Submit - The pig is marked as received. The pipeline overview updates and the completion is recorded in the pigging report
Pending Pigs

Once a pig is sent, it enters a pending state and remains there until it is received:

  • The dashboard shows all currently pending pigs and the pipelines they belong to
  • Pending pigs are also visible on the Pipeline Group Overview report
  • There is no automatic timeout or escalation for pigs that have not been received — they stay pending until manually received
Batching

Batching is the process of sending a sequence of pigs and batch fluids through the pipeline, which may include pigs before and after the fluid slugs. Batch events are recorded similarly to pig events but with some differences:

How batching differs from pigging:

  • A batch event can include a combination of pigs, batch fluids, and more pigs sent as a single event
  • The batch form documents the liquids and volumes being sent, based on what is configured in the batch schedule
  • A batch event records the entire train as one entry rather than separate pig sends

How to send a batch:

  1. Navigate to the sender location
  2. Open Senders and find the correct sender
  3. Click "Batch" instead of "Send Pig"
  4. Review the liquids and volumes required by the batch schedule configuration
  5. Complete the batch form and submit

Batch records can be viewed in the Pipeline Group Overview and the Sent Pigs/Batches report.

Deferring a Pig Schedule

Deferring pushes a pig schedule out to a later date. Use it when the pipeline is still flowing but the pig run cannot happen — weather, access, equipment, or crew. If the line is no longer flowing at all, deactivate the sender instead.

How to defer a schedule

  1. Navigate to the sender location - Go to the plant or field location that has the pig sender
  2. Open the Senders section - Use the EZ-Nav to find Senders
  3. Find the pig schedule and click Defer
  4. Pick the new date - The date picker only offers dates your organization allows. The earliest is tomorrow. Window schedules do not offer a date picker — they move to the next window automatically
  5. Choose who to notify - Optional. Some people receive an email automatically based on their user settings
  6. Leave a comment - Required. This is the permanent record of why the pig run did not happen
  7. Click "Defer Pig" - The schedule moves to the new date

Until your device syncs, you can reverse a deferral with Undo Defer on the same schedule.

How far out you can defer

Your organization sets a deferral limit as a number of days — not a number of deferrals. The default is 90 days, and pig schedules and batch schedules are limited separately.

The furthest date you can defer to is:

The date the last pig was sent + your organization's limit

Three things follow from that, and they are the source of most confusion about deferrals:

  • Deferring does not move that date. Every deferral on the same schedule comes out of the same fixed window, so your second and third deferrals are shorter than your first
  • Waiting does not move it either. The window does not start over when it runs out. Once that date has passed, the schedule cannot be deferred at all — by any amount — until a pig is sent
  • Sending a pig is the only thing that moves it. A pig run sets a new last sent date, and the window starts over from there

If a pig has never been sent on that schedule, the date the sender was created is used as the starting point instead.

Because the count starts at the pig run rather than at the due date, the delay you can actually add is always less than the limit. With a 120-day limit, a pig sent January 1 on a schedule that comes due February 1 can be pushed to May 1 — 89 days of delay, not 120. The month the schedule spent running normally is part of the same window.

Example with a 120-day limit: a pig goes in on January 1, so the schedule can be deferred to any date up to May 1. Deferring to March 1 and later to April 15 are both fine — they are inside the window. A further deferral to June 1 is refused, because it is past May 1. Waiting until May 2 and trying again does not help either — the window is gone, and Defer is refused outright. Sending a pig on April 20 moves the window to August 18, and deferrals are available again.

When a schedule cannot be deferred at all

If the window has been used up, opening the Defer form shows this instead of a date picker:

This schedule cannot be deferred. The last pig was sent on [date]. Your organization has set a deferral limit of [N] days, which would put the next allowable deferral date at [date], exceeding the limit.

The three values in that message are the whole explanation: when the clock started, how many days you get, and the date that would have resulted. If the line genuinely cannot be pigged, talk to your administrator — the limit is an organization setting and changing it takes effect immediately.

Deactivating a Sender

Deactivating a sender marks a pipeline as no longer flowing, so it stops appearing as an active sender on the pigging screens. Use it when the line is shut in, not when a single pig run is inconvenient.

Not every organization allows operators to do this. If your organization does, an Active / Inactive power button appears beside the sender on the pigging screen.

How to deactivate a sender

  1. Navigate to the sender location and open the Senders section
  2. Click the Active power button beside the sender
  3. Choose when it should come back - Depending on your organization's configuration you may see one or both of:
    • A given date - The sender turns itself back on when that date arrives. Nobody has to do anything
    • Someone reactivates it - No end date. It stays off until a person turns it back on
  4. Enter a reason - Required, and recorded in the pigging records
  5. Choose who to notify - Optional
  6. Submit - The sender shows as Inactive

To bring it back, use the same button and add optional notes.

How long a sender can stay deactivated

If you pick a reactivation date, your organization caps how far out that date can be — 90 days unless your organization has changed it. That window is counted from the day you deactivate, so it is not affected by when the last pig was sent.

Unlike a deferral window, a deactivation window renews. Every deactivation gets the full allowance again, so there is no equivalent of a schedule running out of room. A sender only has to be active before it can be deactivated again:

  • Wait for the reactivation date to arrive. The sender reactivates itself — an automated service turns it back on overnight and emails the people who receive pipeline notifications. You can deactivate it again the same day
  • Or reactivate it yourself first, at any point, and deactivate it again immediately for a fresh full window

Sending a pig has nothing to do with this. Pig sends only affect how far a schedule can be deferred.

Deactivating a line repeatedly is recorded every time — the reason you enter is kept in the pipeline's history and an email goes out on each change — so use it for a line that is genuinely not flowing rather than as a way to keep pigging obligations off the dashboard.

What happens to the pig schedules

This depends on how your organization is configured, and it is worth knowing which way yours is set:

  • If schedule deactivation is switched on, the sender's pig schedules are deactivated with it and come back when it is reactivated. Your organization may limit this to pig schedules only, batch schedules only, or both
  • If it is switched off, the schedules keep running. The sender shows as Inactive, but its schedules keep coming due and going overdue on a line nobody is pigging

A schedule that is currently deferred is skipped either way — it is not deactivated with the sender, and it is not reactivated with it.

Right-of-Way Inspections

Pipeline segments can be assigned inspection schedules for right-of-way (ROW) inspections. These work exactly the same as other inspection types in EZ Ops:

  • Inspections are created and assigned by administrators on the pipeline configuration page
  • Due inspections appear on the location page for the relevant pipeline segment
  • Failed questions automatically generate tasks
  • The inspection moves to Rectified when all auto-generated tasks are completed
Viewing Pipeline Activity

Dashboard:

  • Pig schedules due or due within two days are listed in the pigging section
  • The number of pending pigs is visible at a glance

Pipeline Group Overview (online):

  • View all pipeline groups (senders to receiver)
  • See all pending pigs, recently received pigs, batch events, and current/previous inspections for each pipeline segment

Sent Pigs/Batches Report (online):

  • View all pig and batch events for a plant over a selected date range
  • Pigs are colour-coded: green = received, red = still in the receiver (not yet received), blue = batch event
  • Click on a row to see all details including form data

Pig Schedules Report (online):

  • View all active pig schedules and export to CSV
Common Issues

"I don't see any pig schedules on my dashboard"

  • Sync your device to get the latest schedule data
  • Pig schedules only appear on the dashboard when they are due or due within two days
  • Confirm with your administrator that pigging schedules have been created for your senders

"I can't find the sender I need"

  • Navigate to the specific location that houses the sender — senders are tied to the location they are configured on
  • If the sender is missing, contact your administrator to confirm pipeline configuration

"The pig schedule didn't reset after I sent a pig"

  • Sync your device — the schedule reset happens after the send event is synced
  • Confirm the pig send was fully submitted and not just started

"I need to use a different pig type than what is required"

  • If a pig type is required, you can still use a different type — you will be prompted to enter a reason for the deviation, which is recorded permanently

"This schedule cannot be deferred, but I have only deferred it once or twice"

  • The limit is a number of days, not a number of deferrals. The schedule has reached the last pig sent date plus your organization's limit, however many deferrals that took
  • The on-screen message names the last sent date, the limit, and the date that would have resulted — those three values are the full explanation
  • Sending a pig starts a new window. If the line cannot be pigged, ask your administrator about the limit

"I deactivated a sender but its pig schedules are still going overdue"

  • Deactivating a sender only deactivates its schedules if your organization has that switched on — otherwise the schedules keep running on their own
  • Your organization may also have it limited to pig schedules only or batch schedules only, so the other type keeps coming due
  • A schedule that was deferred at the time is skipped and stays active

"I can't deactivate a sender for another period"

  • The sender is still inactive from the last time. Reactivate it — or wait for its reactivation date to arrive — and then deactivate it again for a fresh window
Tips & Recommendations
  • Always complete the pigging form - Form data provides the full documentation record of each pigging event; forms should always be configured for active pipelines
  • Send and receive on the same visit when possible - Completing both ends in one session keeps the record clean and the pending pig list accurate
  • Defer for a delayed pig run, deactivate for a shut-in line - Deferring keeps the schedule alive and moves it; deactivating takes the sender out of service entirely and is recorded against the pipeline
  • Write the deferral comment for someone reading it in a year - It is the only record of why the pig run did not happen, and repeated deferrals on one schedule are exactly what gets reviewed later
  • Watch for a pig that has been pending an unusually long time - There is no automatic timeout or escalation, so a stale pending pig stays on the list until someone acts on it

Remember: Deferring a pig schedule never extends the window it comes out of — the window runs from the last pig sent date, so only an actual pig run gives the schedule a full deferral allowance again.