Pigging Schedule Configuration
The Pigging section of Organization Settings controls two things operators can do in the field when a pipeline cannot be pigged on schedule: defer a pig schedule to a later date, and deactivate a pig sender so the line stops producing pigging obligations altogether. The settings decide whether operators may do these at all, how far out they may push a date, and what happens to the pig schedules on a deactivated sender.
These are separate actions for separate situations. The app states the distinction in its own tooltips:
- Defer a pigging event when the pipeline is still flowing, but pigging cannot occur for a given reason
- Deactivate the pig sender when the pipeline is no longer flowing
- They put a ceiling on how long a line can go unpigged - Without a limit, a schedule can be pushed forward indefinitely, one deferral at a time, and nothing in the app pushes back
- They decide who can take a line out of service - Sender deactivation can be left to admins only, or handed to the operators who are actually standing at the line
- They control whether a deactivated sender keeps generating overdue pig schedules - Deactivating a sender does nothing to its pig schedules unless you configure it to
Go to Org Configuration in the main navigation and scroll to the Pigging section.
The whole Pigging section only appears if the Pigging module is enabled for your organization in the Modules list at the top of the same page.
| Setting | What it does | Default when unticked |
|---|---|---|
| Pig Type Filtering | Adds All Pigs / Filtered Pigs buttons to the Send Pig screen. Filtered Pigs narrows the pig type list to types that suit the pipeline's minimum size or the sender's custom pigging size | No filter buttons; the full pig type list is shown |
| Allow Users to Deactivate Senders | Gives operators the Active / Inactive power button on a sender in the field | Only admins can deactivate senders, from the pipeline configuration in the Admin panel |
| Deactivation Options | Controls which end-date choices the operator is offered: Reactivation date only, Until someone reactivates it only, or Both | Both choices are offered |
| Custom Pig Sender Deactivation Limit | The furthest-out reactivation date an operator may pick, in days | 90 days |
| Deactivate Pig Schedules with Sender | Deactivates the sender's pig schedules when the sender is deactivated, and reactivates them when it comes back | Pig schedules are not touched at all — they stay active and keep coming due on a dead line |
| Pig Schedules Types To Deactivate With Sender | Limits the above to Pig schedules, Batch schedules, or all | Not applicable unless the setting above is ticked |
| Custom Pig Deferral Limit | The maximum number of days a normal pig schedule may be deferred | 90 days |
| Custom Batch Deferral Limit | The maximum number of days a batch schedule may be deferred | 90 days |
Pig and batch deferrals are limited separately, so a line can allow a 120-day pig deferral and a 180-day batch deferral.
How Deferral Limits WorkThe limit is a number of days, not a number of deferrals
There is no cap on how many times a schedule can be deferred. The limit is a date ceiling, and operators may defer as many times as they like as long as each new date lands on or before it.
The ceiling is measured from the last pig sent date
The furthest date an operator can defer to is:
Last pig sent date + your deferral limit
If a pig has never been sent on that schedule, the sender's creation date is used as the starting point instead.
Deferring does not move the ceiling, and neither does the passage of time. Every deferral draws down the same fixed window, so repeated deferrals get progressively shorter until there is nothing left to give — and when the ceiling passes, the window does not start over. The schedule simply becomes undeferrable and goes overdue until a pig is sent.
Because the count starts at the pig run rather than at the due date, the delay an operator can actually add is always less than the limit you configure. Under a 120-day limit, a pig sent January 1 on a schedule due February 1 can be pushed to May 1 — 89 days of delay, not 120. Set the limit to the longest you will allow between pig runs, not to the longest single delay you want to permit.
Sending a pig is what moves the ceiling
Sending a pig records a new last sent date, and the ceiling moves with it — a full deferral limit forward from the day the pig went in. This is why deferrals appear to "reset" after a pig run.
Worked example, with a 120-day pig deferral limit:
- A pig is sent on January 1. The schedule may now be deferred to any date up to May 1 (January 1 + 120 days)
- The operator defers to March 1. The ceiling is still May 1
- The operator defers again to April 15. Still allowed — April 15 is before May 1
- The operator tries to defer a third time to June 1. Blocked. June 1 is past the ceiling
- The operator waits until May 2 and tries again. Still blocked — the schedule cannot be deferred by any amount, because the ceiling is now in the past and the earliest selectable date is tomorrow
- A pig is sent on May 5. The ceiling moves to September 2 (May 5 + 120 days), and deferrals are available again
The number of deferrals a schedule gets before running out is not a setting — it falls out of the schedule's frequency against the limit. A monthly schedule under a 90-day limit tends to allow about three, which is where the "three deferrals" belief comes from, but the count is a side effect and it changes with the frequency.
Window schedules
Window schedules behave differently: they can only be deferred one window at a time, and the operator cannot pick an arbitrary date. If the end of the next window would fall past the ceiling, the schedule cannot be deferred at all.
What operators see when a schedule is out of room
Opening the Defer form on a schedule that has used up its window shows the reason 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.
If no pig has ever been sent, the message names the sender's creation date instead.
What operators fill in
A deferral requires a comment, and optionally notifies selected users. Until the device syncs, the action can be reversed with Undo Defer on the schedule.
How Sender Deactivation WorksWith Allow Users to Deactivate Senders on, operators see an Active / Inactive power button beside the sender on the pigging screen. Deactivating requires a Reason; reactivating takes optional notes. Either way, the change is recorded in the pigging records and can notify selected users.
The two ways a deactivation ends
Deactivation Options decides which of these the operator is offered:
- A given date - The operator picks a reactivation date. The sender reactivates itself when that date arrives — nobody has to do anything
- Someone reactivates it - No end date. The sender stays inactive until a person turns it back on
The Custom Pig Sender Deactivation Limit applies only to the first one. It has no effect on an open-ended deactivation.
The deactivation limit is counted from the day you deactivate
The furthest reactivation date an operator can pick is the limit counted forward from tomorrow — so a 180-day limit allows a date up to roughly six months out from the day the sender is switched off.
Unlike the deferral ceiling, this is not anchored to the last pig sent date. It is a fresh window every time a sender is deactivated.
Deactivating the same sender again
A sender has to be active before it can be deactivated, so a sender that is already off cannot be given a second deactivation stacked on the first. To start a new window:
- Wait for the reactivation date to pass, which reactivates the sender automatically, or reactivate it manually from the same power button
- Deactivate it again. The full limit is available again, counted from that day
Sending a pig is not part of this. Pig sends move the deferral ceiling; they have no bearing on how long or how often a sender can be deactivated.
This is the opposite of how deferral limits behave, and the difference matters when you are setting the numbers. A deferral window is anchored to the last pig run and does not renew with time — when it is used up, the schedule stays undeferrable until a pig goes in. A deactivation window is anchored to the act of deactivating, so it renews in full the moment the sender is active again.
The limit caps one period, not total downtime
Because every deactivation gets a fresh window, deactivations can be chained indefinitely — a 180-day limit does not prevent 180 days, then another 180, then another. The app does not track cumulative downtime for a sender and does not refuse a repeat deactivation.
What you get instead is a record rather than a control: every deactivation requires a reason, every one is written to the pipeline's activation history, and the Pipeline Notifications email goes out each time. If a line being shut in for long periods is a compliance concern, that history and those emails are the thing to review — the limit setting will not enforce it.
What happens to the pig schedules
Deactivate Pig Schedules with Sender decides this, and if it is off, deactivating a sender leaves its pig schedules running — the line stops being pigged but keeps generating obligations and going overdue.
With the setting on, deactivating the sender deactivates its schedules and reactivating the sender brings them back. The dropdown limits which ones are affected:
- Pig - Everything except batch schedules
- Batch - Batch schedules only
- all - Both
A schedule that is currently deferred is skipped. It is not deactivated along with the sender, and it is not reactivated with it either.
Automatic reactivation
A scheduled job reactivates senders whose reactivation date has passed, clears the date, and sends the Pipeline Notifications email attributed to EZ Ops Automated Service rather than to a person. Nobody needs to be in the app for this to happen.
Automatic reactivation is broader than a manual one. It reactivates every inactive pig schedule on that sender's line, without applying the Pig Schedules Types To Deactivate With Sender scoping above. On an organization that deactivates only one type with the sender, a schedule of the other type that was switched off separately and deliberately can come back on when the sender auto-reactivates.
NotificationsPipeline deactivation and pig deferral notify separately, and both are per-user checkboxes an admin sets on the user record:
- Receive Pipeline Notifications - Emails the user when a pipeline or sender is deactivated or reactivated by an operator
- Receive Pig Deferral Notifications - Emails the user when a pig or batch schedule is deferred by an operator
Both only cover locations the user is connected to. Operators can also pick additional people to notify at the moment they defer or deactivate.
Common Issues"A schedule says it cannot be deferred, but we have not deferred it three times"
- The limit is days, not deferrals. The schedule has reached its last pig sent date plus the deferral limit, whatever number of deferrals that took
- The on-screen message names the last sent date, the configured limit, and the date that would have resulted — read those three numbers back to confirm
- Sending a pig is the only thing that moves the ceiling. Raising the limit in Organization Settings also makes room immediately
"The window ran out — can they defer again once the deferred date has passed?"
- No. The window does not renew with time. Once the ceiling is in the past the schedule cannot be deferred by any amount, and it stays that way until a pig is sent or the limit is raised
- This is the most common wrong assumption about the setting, because a deferral that used the whole window looks like it should be followed by another one
"A deactivated line is still showing overdue pig schedules"
- Deactivate Pig Schedules with Sender is off, so deactivating the sender never touched the schedules
- Or the dropdown is set to Pig or Batch and the overdue schedules are the other type
- Or those schedules were deferred at the time the sender was deactivated, which excludes them
"We cannot deactivate a sender for a second period"
- The sender is still inactive from the first deactivation. Reactivate it — or wait for its reactivation date to arrive — and then deactivate it again for a fresh full window
- There is no limit on how many periods a sender can have. Unlike a deferral window, a deactivation window renews every time
"Our deactivation limit is not stopping lines from sitting inactive for a year"
- It was never going to. The limit caps the length of one deactivation, and each new deactivation gets the full limit again
- Review the pipeline's activation history and the Pipeline Notifications emails to see the pattern; the app does not total up a sender's downtime anywhere
"Operators cannot pick a reactivation date, only 'someone reactivates it'"
- Deactivation Options is set to Until someone reactivates it only. Switch it to Both or Reactivation date only
- Set Deactivate Pig Schedules with Sender deliberately - It is off unless someone ticks it, and leaving it off is the single most common reason a shut-in line keeps reporting overdue pigs
- Set the deferral limit from your compliance interval, not from a deferral count - Decide the longest a line may go between pigs and enter that as the limit; the number of deferrals will follow from the schedule frequency
- Raise the limit rather than sending a pig to buy time - Changing the limit in Organization Settings takes effect on existing schedules immediately, because the ceiling is recalculated from the last sent date each time the Defer form is opened
- Do not rely on the deactivation limit as a downtime cap - It bounds a single period and renews on every new deactivation, so treat it as a prompt to revisit the decision rather than as an enforced maximum
- Turn on Pipeline and Pig Deferral notifications for whoever owns compliance - Repeated deferrals and repeated deactivations are both invisible on the dashboard, which keeps showing a future due date or an inactive sender; the emails are the only push signal that a line is being pushed out
Remember: A deferral ceiling is fixed at the last pig sent date plus your limit and does not move when a schedule is deferred — so the second and third deferrals on the same schedule are shorter than the first, and only sending a pig gives the line a full window again.