Vendor Package HAZOP: An Interface Information Checklist
Prepare vendor package HAZOP interfaces with a practical register covering process connections, utilities, controls and evidence ownership.
A packaged compressor, dosing skid or treatment unit can arrive with its own drawings and hazard review while still leaving important questions at the connection to the host facility. Who owns the inlet conditions? Which system receives a trip signal? What happens to a shared utility when another package stops?
A vendor package HAZOP interface review makes those boundaries explicit before the workshop. This guide gives project engineers a practical information checklist and a worked interface-register example. It complements HAZOP study preparation and facilitation; it does not prescribe a safe design or replace the multidisciplinary assessment of the actual installation.
Start with the installed system, not only the purchase boundary
A commercial supply boundary describes who provides equipment. A hazard-study boundary also needs to capture interactions that can create a cause or consequence outside that supply. A vendor drawing ending at a flange does not, by itself, explain the upstream process, downstream destination or shared services.
The UK Health and Safety Executive notes that a plant modification can affect parts of the plant remote from the change. Its plant modification guidance supports reviewing those wider effects and keeping a traceable technical basis. It is UK guidance, not a statement of Australian legal obligations.
Before choosing nodes, ask the host facility and vendor to agree which interfaces the study will examine and who can answer each question. Use the existing node selection and workshop preparation guide for the wider study structure.
Build one interface register with evidence references
A short register can prevent assumptions from disappearing between the vendor’s documentation and the host project’s records. The following fields are a suggested working format, not a prescribed regulatory template:
- Interface identifier: a unique reference linked to the relevant drawing connection or signal.
- Connected systems: the package and the host equipment or service on the other side.
- Required information: the condition, function or boundary the team needs to understand.
- Evidence: document number, revision, section and the responsible technical source.
- Status: confirmed, awaiting clarification or affected by a proposed change.
- Review owner: the person or discipline responsible for resolving the information gap.
- Study consequence: which node, scenario or decision depends on the answer.
Keep an assumption separate from a verified fact. A vendor email can identify a question without becoming an approved design basis. The project’s document-control and technical-review arrangements determine what evidence is acceptable.
1. Process connections and operating cases
For each inlet, outlet, vent, drain and return, gather the relevant process description and controlled drawings. Ask the responsible engineers to identify the operating cases covered by the information, including modes such as normal operation, start-up, shutdown and maintenance where applicable.
Check that the vendor and host documents use consistent equipment tags, connection references and units. Record where information about composition, pressure, temperature or flow is missing or still under development. The facilitator should be able to trace the stated design intent to its source rather than infer it from an equipment name.
This is an information-preparation step. The correct operating limits and credible deviations must be established by the competent project team for the specific process.
2. Utilities and dependencies outside the package
List the utilities on which the package depends, such as electrical power, instrument air, cooling water or other project-specific services. For each, identify the responsible owner and the documents describing the package’s behaviour when that service changes or becomes unavailable.
Look for shared dependencies. Two packages may appear separate on their own drawings while relying on the same utility or upstream equipment. Record the relationship for assessment; do not assume that a shared dependency is harmless or automatically unacceptable.
Where the package is part of a brownfield modification, connect unresolved interface questions to the project’s management-of-change review so later changes remain visible.
3. Controls, alarms and shutdown interfaces
Bring the relevant control narratives, cause-and-effect information and signal definitions together. The team needs to understand which system initiates a command, which receives it, what feedback exists and where responsibility for the overall function sits.
Useful preparation questions include: Do both documents describe the same signal? Is its purpose stated consistently? Are communication-loss behaviour and reset responsibilities documented? Which assumptions depend on the host system rather than the vendor’s equipment?
If a safety instrumented function crosses the package boundary, refer the question to the responsible functional safety engineering review. A signal label or a vendor statement alone does not establish the integrity of the complete function. Do not invent trip settings, response times or risk-reduction credit to fill gaps in the register.
Worked example: a cooling-water interface
The following is a fictional record showing the level of documentation useful before a workshop. It is not a client case study or a recommendation for any real installation.
- Reference: IF-07, package cooling-water supply.
- Connection: vendor package drawing VP-101 to host utility drawing HU-204.
- Question: the vendor document describes a utility-loss response, but the host control narrative does not identify the corresponding indication.
- Evidence status: clarification required; neither document has been accepted as resolving the interface.
- Owner: project controls lead coordinating with the vendor and operations representative.
- Required output: reconcile the applicable controlled documents and record which scenarios or review decisions depend on the answer.
- Close-out evidence: reviewed document references and the responsible team’s recorded disposition, linked to the study action where applicable.
The register makes the disagreement visible without deciding that a particular protective action is adequate. That decision belongs to the technical assessment, with the actual process conditions and hazards available.
Use the register during and after the workshop
At the opening session, confirm the document revisions and the remaining interface questions. When a scenario depends on missing information, record the dependency and assign a clear action. Avoid silently treating an unknown condition as a confirmed safeguard.
After the workshop, reconcile the interface register with the study action list. Keep the original question, the accepted evidence and the review decision connected. The HAZOP action close-out checklist explains how to preserve that evidence through closure. A changed vendor document may require further assessment under the project’s change process rather than a simple file replacement.
Reference framework and next step
Safe Work Australia’s safety assessment guide addresses hazards, major incidents and control measures for major hazard facilities. Its scope is broader than this package checklist, and applicability depends on the facility and jurisdiction. For a separate international reference, US OSHA’s process safety management standard includes process and equipment information such as P&IDs for covered processes. Neither reference makes this suggested register a compliance certificate.
For a planned package integration, prepare the available vendor and host documents, a first-pass interface list and the unresolved questions. Then discuss the HAZOP scope with Pro Engineers so the study can address the connections as well as the equipment within the package.