Pipeline Operations
This domain tests the day-to-day operation of a pipeline: holding MAOP, interpreting pressure and flow data, running pigs, aligning valves, recognizing leaks, and responding through the control room and field procedures. Expect questions that mix equipment knowledge with operating decisions and documentation.
Operating limits and monitoring
- MAOP is established from design (ASME B31.4 for liquids, B31.8 for gas) and the applicable federal code (49 CFR 195 or 192). It is not the same as hydrostatic test pressure.
- Overpressure protection includes relief valves, high-pressure switches, and control-room alarms; setpoints must be below MAOP with documented margin.
- SCADA and computational pipeline monitoring compare pressure, flow, and volume balance. An alarm is a prompt to verify, not proof of a leak.
- Control-room management rules cover shift turnover, fatigue, alarm response, and simulator training.
Pigging, valves, and right-of-way
- Utility pigs clean or batch; in-line inspection pigs gather integrity data. Track launch, differential pressure, speed, and receipt.
- Line-break valves, check valves, and ESD valves have normal positions and operating authority that must be confirmed before movement.
- Call 811 before excavation; pipeline markers locate the right-of-way but do not guarantee depth or exact position.
Worked example
A 12.75-in OD liquid line has 0.250-in wall, SMYS 52,000 psi, design factor 0.72, and seam/joint factors of 1.0. Using P = 2St/D × F × E × T: 2 × 52,000 × 0.250 ÷ 12.75 = 2,039 psi; × 0.72 = 1,468 psi MAOP. A proposed 1,500-psi operating pressure exceeds MAOP, so it must not be accepted even if a hydrostatic test once reached a higher pressure.
Traps that cost marks
Confusing MAOP with test pressure; treating a SCADA leak alarm as confirmed; ignoring pig speed or differential pressure; changing valve lineup without authorization or documentation; using nominal pipe size instead of actual OD and wall for pressure calculations.