CHE3166 Chap.4 Piping, Instrumentation and Process Safety
Piping, Instrumentation and Process Safety
Read a P&ID as cause and effect. For every loop, identify the measured variable, target, manipulated variable and expected process response. For every hazard, separate basic control, alarms, operator action, trips and relief protection. Isolation, drainage and fail positions must support credible operating and maintenance states.
Begin by tracing the physical process path, then read each instrument loop from sensing point to final element. State why the target matters and how changing the final element affects the process variable. Check measurement range, response, installation location and failure indication. A tag does not prove that the device can detect the scenario in time.
Review loss of signal, air and power, and confirm that valve fail position supports the desired process response. Keep normal control and protection distinct. Basic control manages variation near the operating target. An alarm communicates a condition and relies on a defined response. A trip automatically moves equipment toward a safer state.
A relief device limits containment pressure when other actions do not stop accumulation. Shared transmitters, power or final elements can create common dependencies, so independence must be demonstrated rather than assumed. Hazard analysis should follow one deviation from cause to consequence.
Identify credible initiators, physical inventory and energy changes, affected people or equipment, existing safeguard functions and residual risk. State where relieved material goes, what happens after a pump stops or valve closes, and how the final state is verified. Maintenance isolation also belongs to safety: identify stored energy, backflow, trapped pressure, vents, drains and safe discharge.
A cause-and-effect schedule, set-point list and P&ID must describe one consistent sequence.
What this chapter covers
- 01
Piping and equipment layers
- 02
Measurement and control-loop intent
- 03
Valve action and fail position
- 04
Isolation, vents and drains
- 05
Hazard deviations, causes and consequences
- 06
Alarms, trips and relief functions
Worked example · free
Protect a vessel against a blocked outlet
- +2Define the deviation, initiating cause and physical overpressure consequence.
- +3Distinguish normal pressure control, alarm response and an independent high-high trip.
- +3Provide a relief path for remaining overpressure and verify its safe destination.
Key terms
- Safe state
- The defined equipment or process condition intended after a protective action.
- Relief path
- A pressure-protection route sized and directed to manage material released during an overpressure case.
Piping, Instrumentation and Process Safety FAQ
Does an alarm count as automatic protection?
An alarm detects and communicates a condition. Risk reduction depends on a defined, timely operator action unless a separate automatic trip changes the process. The response time must also be demonstrated.
Why does valve fail position matter?
Loss of signal, air or power can move a valve to its fail position. That position must be checked against the hazard and the desired safe response.
What should the project P&ID show beyond equipment?
The assignment brief requires pipeline sizes and materials, associated controls and alarms, and maintenance provisions including isolation valves, vents and drains. It also asks for a separate cause and effect matrix describing safety relationships. Check these layers together so the drawing shows how equipment is connected, controlled, made safe and prepared for maintenance.
Assessment move
Take one deviation at a time and write cause, consequence, control response, alarm action, trip action and relief role. Then trace those functions on an original P&ID sketch. For each control loop, write measured variable, set point, controller output, manipulated variable and expected direction of response.
Challenge the loop with loss of signal, power or utility and decide whether the fail position is safe for the stated scenario. Build a cause-and-effect table with condition, detector, threshold, logic, final action and resulting process state. Mark shared dependencies that weaken independence. Practise explaining why an alarm is not the same as a trip and why a trip is not the same as relief protection.
For maintenance cases, trace every possible source of pressure or backflow and identify safe vent and drain destinations. Finish each problem with a verification method: proof test, functional test, relief basis review or controlled operating check. In project work, compare P&ID tags against the control narrative and set-point list after every revision.
Work through an original vessel system in normal operation, start-up and blocked-outlet conditions. Draw the process path first, then add measurement points only where the variable can be sensed meaningfully. For each loop, predict the response direction before assigning a valve action. Challenge signal loss, air failure, power failure and a stuck final element.
Build a table that separates basic control, alarm, operator response, automatic trip and relief protection, and write one sentence explaining the independent purpose of each. Trace stored pressure, backflow, venting and drainage for a maintenance isolation. Add set points only after the physical consequence and safe state are defined. Review shared transmitters, supplies and valves for common dependencies.
Specify how the complete detection-to-action path will be tested and how bypasses are controlled and restored. Compare the P&ID, control narrative and cause-and-effect schedule after a change. In revision practice, remove one safeguard and identify the earliest unsupported risk claim rather than simply adding another device.
This approach keeps the analysis tied to one credible scenario and avoids lists of protection that cannot be verified. Use a second colour on the sketch to trace mass and energy after the protective action. This reveals trapped inventory, continued heat input or an unsafe discharge that a purely electrical cause-and-effect table can miss.
Keep the final recommendation tied to the stated basis, and record the observation that would require a revised engineering decision.
