Process Engineering Design Basis Review: A Brownfield Checklist

A practical brownfield process engineering design-basis review checklist covering operating cases, PFDs, P&IDs, hydraulics, safeguards, interface ownership and assumptions.

A process design basis is often treated as a document produced early in a project and filed away. On a brownfield modification, it should be a live engineering reference: a clear account of what the existing facility can safely do, what is proposed to change, which assumptions have evidence, and what must be verified before approval. A new pump, compressor tie-in, control valve or process-routing change can alter more than the design duty of the affected equipment.

This practical review guide is written for engineers preparing brownfield process modifications in Australian industrial facilities. It is a planning aid, not a design standard or a substitute for site engineering governance, competent review or applicable legislation. Each project must apply its own approved documents, risk criteria and assurance requirements.

1. Start with the actual decision and existing operating envelope

Record the proposed modification, operating problem, expected benefit and constraints in one short statement. A useful scope names the equipment, operating modes, upstream and downstream limits, interfaces, and cases that will not be assessed. Distinguish normal operation, startup, shutdown, turndown, recycle, blocked flow, standby and temporary maintenance arrangements where relevant. For a tie-in project, include how the plant will operate before, during and after the change.

The existing design case and the actual operating case are not always the same. Set out source records for current throughput, pressure, temperature, composition, equipment condition, alarm limits and observed operating restrictions. Where measured data conflict with drawings or old datasheets, record the discrepancy for resolution instead of silently adopting the most convenient value.

2. Build a controlled document register

Maintain a register that records the revision, owner, purpose and status of each engineering input. Typical entries include PFDs, heat and material balances, P&IDs, equipment and instrument datasheets, control narratives, cause-and-effect diagrams, relief and blowdown philosophies, operating procedures, relevant hazard studies and management-of-change records. Tag each source as approved, under review, superseded, provisional or missing. A document can be available without being suitable for the present decision.

For background, the US OSHA Process Safety Management rule lists process technology, equipment information, piping and instrumentation diagrams, relief-system design basis and material and energy balances among its process safety information requirements for facilities within its scope. That is a US rule, not an Australian legal requirement for your project. Its document categories are nevertheless useful prompts for engineers developing a project-specific input register. See OSHA 29 CFR 1910.119(d).

3. Reconcile the PFD, process balance and P&IDs

Check that main process streams, equipment tags and flow directions agree across the PFD, heat and material balance and P&IDs. For each relevant case, confirm composition, mass flow, pressure, temperature, density or phase basis and the treatment of recycle, vent, drain and utility flows. Avoid using a steady-state simulation case as proof that every transient or upset condition has been resolved.

A PFD communicates the main process and design cases. P&IDs communicate the detailed equipment, piping, valves, instrumentation and interfaces needed for engineering review. The diagrams serve different purposes and should be consistent, not assumed interchangeable. Verify that equipment duties on the balance match datasheet design and operating duties, and clearly identify assumptions carried from vendor or earlier-stage documents.

4. Separate design limits from operating limits

Prepare an operating-envelope table with normal, minimum, maximum, startup and shutdown conditions as appropriate. Separate operating limits, alarm settings, shutdown setpoints, mechanical design ratings and relief or depressurisation design assumptions. They may be related but are not synonymous. Note ambient and utility conditions, fluid-composition variation, degradation, fouling and equipment turndown where these affect performance or safety.

For a compressor modification, for example, a revised suction-pressure case may affect recycle demand, anti-surge controls, settle-out pressure, downstream hydraulic limits and the shutdown sequence. A nominal duty-point check is not sufficient to establish that all these aspects remain acceptable. Record who owns each interface and which calculations or tests demonstrate the available margin.

5. Check equipment and hydraulic interactions

Identify hydraulic boundaries and pressure sources. For relevant cases, evaluate pressure drop, pump head, compressor operating range, control-valve authority, flow distribution, pipe velocity and equipment minimum-flow requirements. Confirm that proposed changes do not exceed equipment, line or instrumentation limitations. Document any unresolved vendor information or relief-system dependency, with the required owner and due date.

Do not infer mechanical integrity from a process simulation alone. Changes to loading, pressure cycling, thermal movement or fluid properties may require mechanical, materials, corrosion, vibration or inspection specialist review. The engineering basis should indicate when specialist assessments are required rather than imply that one discipline has covered them all.

6. Review safeguarding and control interfaces

Map the proposed modification against control loops, alarms, shutdown functions, isolation valves, permissives and package-system boundaries. Identify changed initiating causes, consequences and potential dependencies between safeguards. Confirm what is documented and what is merely a verbal account of how the plant has operated. Where controls are being credited as protection, use the facility’s prescribed risk assessment and functional-safety methods rather than informal reliability assumptions.

Changes to design intent, operating parameters or protective functions may affect earlier hazard assessments. Consider whether a targeted HAZOP, HAZID, LOPA, functional safety or other review is required under the site’s management-of-change process. See our HAZOP facilitation service and management-of-change hazard-study guide for related review scopes.

7. Treat brownfield isolation and tie-in stages as separate operating cases

Temporary arrangements can create hazards different from the final modification. Define the isolation philosophy, required process inventories, access and permits, commissioning boundaries, temporary utilities and sequence for introducing hydrocarbons or other hazardous substances. The design package should identify what is to be physically verified on site and what must be incorporated in operations instructions, testing and handover. Do not assume a final design drawing adequately describes intermediate construction states.

The Safe Work Australia guide for safe design of plant discusses design, redesign and modifications across a plant lifecycle. Queensland’s codes of practice provide local context, including managing risks of plant in the workplace. Check the requirements applicable to the facility and jurisdiction rather than treating a broad guidance document as a universal process-industry rule.

8. Carry uncertainty forward visibly

Build a short assumptions and decisions register. Each item should say what is unknown, why it matters, the potential consequence if incorrect, the evidence needed, the owner and the decision it may block. Separate assumptions that can be bounded conservatively from those requiring plant verification. For example, an unconfirmed normally open bypass valve, unverified line capacity or outdated trip setpoint should not disappear into a calculation note.

Use confidence labels if useful: verified, documented but unconfirmed, inferred or unknown. A risk review can then focus on the remaining uncertainty rather than rechecking data already supported by current records. Where evidence arrives late, identify which previous conclusions must be reassessed.

9. Define a review and approval package, not just a calculation package

Before issue, assemble the design-basis note, revision-controlled source list, relevant calculations, a diagram mark-up register, interfaces, assumptions, unresolved risks, an action list and the project decision record. Cross-check the final conclusions against the modifications actually proposed. Ask operations, maintenance, control-systems and other specialists to challenge areas where the model does not reproduce real plant constraints.

Document acceptance criteria and who has authority to close each item. A technical recommendation should not be described as approved just because the calculation has been signed. Show the relationship between engineering outputs, hazard-study recommendations, management-of-change approvals and commissioning handover.

Worked example: revising a transfer-pump duty

Imagine a hypothetical brownfield facility increasing throughput through an existing transfer system. A preliminary calculation shows adequate pump head at the intended flow. The engineering review then finds that the normal-control case was modelled with clean strainers, while operating records show frequent fouling. The P&ID also shows a minimum-flow recycle path, and the downstream equipment datasheet imposes a pressure limitation.

A defensible review would confirm the fouled case, pump curve, minimum-flow requirement, downstream protection and control-valve operating range before endorsing the modification. It would track whether any alarm or shutdown setpoints need a controlled review. The result might still be an acceptable design, but it should be accepted on explicit evidence rather than a single optimistic hydraulic case. This example is illustrative only and provides no plant-specific operating instruction.

Practical close-out checklist

  • Project objective, boundaries and affected operating cases are agreed.
  • Current PFDs, balances, P&IDs and datasheets are revision-controlled.
  • Design ratings and operating envelopes are distinguished.
  • Hydraulic, equipment and control-system interfaces are reviewed.
  • Process-safety and safeguarding implications have a documented review route.
  • Brownfield isolation, commissioning and temporary states are included where applicable.
  • Open assumptions have named owners, evidence requirements and decision gates.
  • Engineering conclusions, management-of-change requirements and handover records are linked.

For support with engineering design reviews, optimisation or brownfield modifications, see Pro Engineers’ process engineering services. A useful design basis makes the next decision reviewable by the people responsible for operating the plant.