Configuring Pipelines
Pipeline configuration in EZ Ops defines the structure of your pipeline network — grouping line segments from one or more sender locations to a receiver, so that pigging activity, batch events, and right-of-way inspections can be tracked accurately. The configuration has three layers: Pipeline Groups, Line Groups, and Lines.
Key point: Pipeline configuration must be built in order — Pipeline Groups first, then Line Groups within them, then individual Lines within each group. The IDs generated at each layer are required to link the next layer. Initial large-scale pipeline setup is done by the EZOPS team; admins can add and edit pipelines once the initial structure is in place.
Why Pipeline Configuration MattersAccurate pipeline configuration is essential because:
- Pigging tracking - Every pig send and receive is tied to a specific sender/receiver line in the configuration
- Schedule accuracy - Pig schedules are attached to sender line groups; an incorrect structure means incorrect schedule tracking
- Inspection coverage - Right-of-way inspections attach to line groups; missing line groups means missing inspection records
- Reporting - The Sent Pigs/Batches report and Pipeline Group Overview rely on correct structure to display meaningful data
The Three-Layer Hierarchy
Understanding the hierarchy is essential before configuring anything:
Pipeline Group (the entire pipeline system — named after receiver and senders)
└─ Line Group (one group if single sender; one per sender if multiple senders)
└─ Lines (individual licensed pipe segments in order from sender to receiver)
Pipeline Group
The top-level container for a complete pipeline system. A pipeline group is attached to a plant.
Standard naming convention (single sender):
[Sender LSD] to [Receiver Location] [Diameter]" ([licence lines in order, sender to receiver])
Example:
100/06-22-047-15W5/00 to 04-33-047-16W5 Battery 4" (23801-1, 23801-2)
For multi-sender pipelines the naming convention is determined during setup with the EZOPS team, as the grouping of senders and shared segments requires a custom structure.
Line Groups
Line groups separate the pipeline into sections based on flow direction. For a pipeline with:
- One sender: A single line group contains all segments from sender to receiver — no additional groups are needed
- Multiple senders: One line group per sender. The
Next Line Groupfield on each sender's line group points to where it merges into the downstream group, showing the flow relationship and direction between them
Lines
Individual licensed pipe segments. Each line has physical attributes (diameter, wall thickness, length, material, operating pressure) and licence information. One line within the group is flagged as the sender (linked to the sending location) and one as the receiver (linked to the receiving location).
Initial Setup: EZOPS Team vs. Admin
EZOPS team handles:
- Large-scale initial pipeline import (hundreds of pipeline groups, line groups, and lines loaded via direct database import)
- The import process requires three sequential Excel files imported in strict order, with IDs from each step carried forward into the next — this is a technical database operation
Admins can handle:
- Adding individual new pipeline groups, line groups, and lines via the app UI
- Editing existing pipeline configurations
- Creating and managing pig schedules
- Deactivating and restoring pipelines
How to Create a Pipeline (UI)
Step 1 — Create the Pipeline Group
- Navigate to Pipeline Configuration - Go to Admin → Pipelines → Pipeline Groups
- Click "Add Pipeline Group"
- Fill in the details:
- Name - Descriptive name for the pipeline system
- Plant - The plant this pipeline group belongs to
- Max Pigs - Maximum number of pigs that can be in this pipeline at one time
- Active - Set to active
- Save - The pipeline group is created
Step 2 — Create Line Groups
- Open the pipeline group you just created
- Add a Line Group for each sender, plus one for the receiver/shared path:
- Name - Descriptive name (e.g., "Well 1 Sender Lines" or "Main Receiver Lines")
- Has Sender / Has Receiver - Flag which groups contain a sender or receiver line
- Next Line Group - For sender groups in a multi-sender pipeline, set this to the line group they flow into after the merge point
- Save each line group before moving to lines
Step 3 — Add Lines to Each Line Group
- Open the line group and add lines in order from sender to receiver:
- Licence Number - The regulatory licence number for this pipe segment
- From / To - LSD locations for this segment
- Physical attributes - Outside diameter (mm), wall thickness (mm), length (km), material, material grade, maximum operating pressure (kPag)
- Is Sender - Flag the line at the sender end; link it to the sending Plant or Well
- Is Receiver - Flag the line at the receiver end; link it to the receiving Plant or Well
- Set the line order - Lines within a group are ordered from sender to receiver. Drag and drop to set the correct order.
- Save each line
Step 4 — Configure the Sender
- Open the Senders configuration (Admin → Pipelines → Senders or within the pipeline group)
- Set pig type on the sender:
- Required Pig Type - Operators must use this type or enter a reason for deviation
- Recommended Pig Type - The send pig form pre-fills with this type, but operators can change it
- Sender Alias - An optional display name for the sender (instead of the LSD)
Step 5 — Create Pig Schedules
- Open the line group that has a sender
- Add a Pig Schedule:
- Schedule Type - The type of pig (configured in Drop Down Lists)
- Last Sent Date - The last time a pig of this type was sent
- Next Send Date - When the next pig is due
- Frequency - How often this type of pig should be sent
- Repetition Type - Dynamic, Static, or Window
- Save - The schedule appears on the dashboard when due
About the Bulk Import Process
For large organizations setting up hundreds of pipelines at once, the EZOPS team performs a structured Excel import directly into the database. The process:
- Pipeline Groups import first — standalone records, no dependencies
- Export the pipeline groups from the database to get their auto-generated IDs
- Line Groups import second — uses an XLOOKUP in Excel to map pipeline group names to their new IDs; the
pipeline_group_idcolumn in the line groups file must be filled with the real database IDs before import - Export the line groups from the database to get their IDs
- Lines import last — uses an XLOOKUP to map line group names to their IDs; the
line_group_idcolumn must be filled before import
Deactivating Pipelines
Pipeline Groups (Admin)
Deactivating a pipeline group automatically:
- Deactivates all pig schedules on its sender line groups
- Deactivates all active inspections on the line groups
To deactivate: open the pipeline group and toggle the Active status to inactive.
To restore: find the pipeline group in the admin list, filter for inactive groups, and restore it.
Line Groups (Admin and End Users)
Individual sender line groups can also be deactivated independently of the pipeline group. This is useful when a specific line is shut in — temporarily or permanently — while the rest of the pipeline remains active.
Admin can deactivate sender line groups directly from the pipeline configuration in the Admin panel.
End users can also deactivate a sender line group from the front end of the app, if Allow Users to Deactivate Senders is enabled in the Pigging section of Organization Settings. This is the typical path when an operator shuts in a line and needs to take it out of active tracking without waiting on an admin. Operators must enter a reason, and the change is recorded in the pigging records.
When a sender line group is deactivated it no longer appears as an active sender on the pigging screens.
What happens to its pig schedules depends on a separate organization setting. Deactivate Pig Schedules with Sender is off unless someone enables it, and while it is off, deactivating a sender leaves its pig schedules running — the line stops being pigged but keeps generating obligations and going overdue. With it on, the schedules deactivate with the sender and come back when it is reactivated, limited to pig schedules, batch schedules, or both depending on the accompanying dropdown. A schedule that is currently deferred is excluded either way.
An operator-initiated deactivation may end on its own. If the organization allows a reactivation date, the sender becomes active again when that date arrives with no action from anyone. The furthest-out date an operator can choose is capped at 90 days unless the organization has set its own limit, counted from the day of deactivation. The alternative mode leaves the sender off until a person reactivates it.
Deactivating a sender is separate from deferring an individual pig schedule, which pushes one schedule to a later date while the line keeps flowing. Deferral is capped by its own organization setting — a number of days measured from the date the last pig was sent, 90 by default, set separately for pig and batch schedules.
Common Issues
"Pig schedules aren't appearing on the dashboard"
- The pipeline group must be active, the line group must have a sender, and the pig schedule must be active
- Sync operators' devices — pig schedule due dates appear on the dashboard and require a sync to show
- Check that the next send date is set correctly on the schedule
"I can't link the sender to a location"
- The Plant or Well must exist and be active before it can be linked as a sender or receiver
- Set the
is_senderflag on the correct line and use the sender locationable field to link the location
"A line is appearing in the wrong order"
- Line order within a group is set manually via drag-and-drop in the line group — reorder as needed
"Multi-sender pipeline isn't flowing correctly in the app"
- The
Next Line Groupfield on each sender line group must point to the correct downstream group - Check that only sender line groups have a Next Line Group set — the receiver/main group should not point to anything
"A deactivated sender is still generating overdue pig schedules"
- Deactivate Pig Schedules with Sender is off in the Pigging section of Organization Settings, so deactivating the sender never touched the schedules
- Or it is on but limited to pig schedules or batch schedules only, and the overdue ones are the other type
- Or those schedules were deferred when the sender was deactivated, which excludes them from both deactivation and reactivation
"Operators can't deactivate a sender"
- Allow Users to Deactivate Senders is off in the Pigging section of Organization Settings — deactivation is admin-only from the pipeline configuration until it is enabled
- If the sender is already inactive, it has to be reactivated before it can be deactivated again
Best Practices
- Name pipeline groups descriptively - Include receiver and sender location names so operators can identify the pipeline in the dashboard and reports
- Set licence numbers on all lines - Regulatory compliance depends on accurate licence data; enter licence numbers at configuration time
- Enter all physical attributes - Diameter, wall thickness, and material data feed into minimum pig size calculations
- Create pig schedules immediately - A sender line group without a pig schedule won't show pigging obligations on the dashboard
- Coordinate with the EZOPS team for initial setup - For new organizations or large pipeline networks, let the EZOPS team handle the bulk import and validate the structure before operators start using it
Quick Tips
- The Pipeline Group Overview report shows the full structure visually — use it to verify configuration is correct after setup
- A pipeline must be active for its pig schedules and inspections to appear
- Sender aliases are optional but make the send pig screen much more user-friendly when LSD names are not intuitive
- Right-of-way inspections are assigned to line groups — ensure line groups are set up before creating pipeline inspections