BWTS Vendor Evaluation for Ports and Shipowners
Updated
Vendor evaluation should test each offer against the documented duty and stated assumptions. A scored matrix makes interface, support and evidence gaps visible before award.
Key takeaways
- Compare bids against identical duty and berth data.
- Score evidence and deviations separately from claims.
- Use hydraulic assumptions to compare usable flow.
- Evaluate waste, utilities and access as site interfaces.
- Test support boundaries and spares configuration details.
- Document clarifications and residual constraints before award.
Build the Comparison Basis
Issue the same duty data to each bidder. Include vessel profile, berth constraints and operating windows. Unequal inputs produce an unfair comparison.
Score requirements, evidence and deviations separately. A confident claim is not evidence. Require clarification of every conditional response.
Weight operational fit alongside price. A low initial figure can conceal access or staffing dependencies. Record the rationale for weighting.
Test Hydraulic Credibility
Ask for predicted flow under stated pump and hose conditions. Require pressure-loss assumptions and limits. Compare usable flow rather than nameplate capacity.
Check how the offer handles variable vessel pumps and manifold elevation. A fixed setting may not suit every call. Ask for the proposed operating envelope.
Review start-up, flushing and bypass philosophy. These steps affect berth time and safety. Identify who controls them during service.
Examine Site Interfaces
Compare footprint, lifting, hose routing and traffic segregation against the berth survey. A technically suitable unit may not have safe access. Request marked-up drawings.
Check power, water, drains and communications requirements. Identify temporary works and their owner. Include utility loss in the risk review.
Ask how solids, filter backwash and sediment are contained and handled. Waste responsibility must be explicit. Confirm local lawful routes separately.
Review Evidence Claims
Ask what commissioning records, alarms and logs are supplied. Link each item to an acceptance purpose. Reject vague claims of compliance.
Confirm project-specific flag, port, class, authority, discharge permit and approval requirements. A vendor cannot make them disappear. IMO G5 is guidance, not automatic approval.
Where sampling is proposed, ask for method, custody and laboratory interface. Sea Clean can coordinate with independent ISO 17025 laboratories and authorised parties where required. Interpret results within their method limits.
Assess Support Reality
Compare mobilisation triggers, access assumptions and escalation routes. Ask which tasks need specialist attendance. Separate regional response claims from wider travel arrangements.
Check spares identification, storage needs and maintenance evidence. A support proposal should name configuration dependencies. Avoid assuming interchangeable components.
Sea Clean is PACT Marine's European partner. That relationship is commercial and does not mean Sea Clean is an approving authority or PACT OEM-authorised party. Evaluate responsibilities as stated.
Make a Defensible Decision
Use clarification meetings to resolve high-risk deviations. Document changed assumptions. Do not rely on verbal assurances.
Select against the agreed matrix and acceptance plan. Preserve both technical and commercial reasoning. This supports later change control.
Keep a reserve list of unresolved constraints after award. Assign owners before mobilisation. Revisit it after the first operation.
Frequently asked questions
What is the most important vendor-evaluation input?
A documented operational duty and site survey are fundamental. They let each bidder state comparable assumptions.
Should vendors be ranked by nominal flow?
No. Compare flow under the actual pump, hose, pressure and berth conditions. Nominal values alone can conceal constraints.
Can a vendor guarantee local acceptance?
No such assumption should be made. Applicable flag, port, class, authority, permit and approval requirements require project-specific verification.
What should a clarification log contain?
Record the requirement, bidder response, changed assumption, owner and decision. This makes the final comparison auditable.