Commissioning Testing After BWTS Installation
Updated
Post-installation testing checks that the installed system works within its agreed scope. It must distinguish functional commissioning from a full D-2 compliance validation.
Key takeaways
- Define whether testing is functional, contractual or regulatory before mobilisation.
- Verify installed details against drawings before wet commissioning.
- Test operating range and alarms, not just start and stop.
- MEPC.325(75) testing is indicative and not full D-2 validation.
- Keep contractual and regulatory acceptance routes distinct.
- Retain a performance baseline for later service diagnosis.
Choose the Test Purpose
State whether testing releases the asset for operation or closes installation defects. That decision determines the test matrix. It also determines who can sign results.
Map drawings against installed pipework and cable routes. Mark deviations before water is introduced. Unrecorded field changes create later troubleshooting risk.
Set pass criteria for each control, instrument and mechanical item. Avoid a single vague system-pass statement. Identify the action for a failed criterion.
Check Installation Details
Confirm valve orientation, tags and accessible isolations. Verify drains cannot discharge into an unsafe area. Inspect supports before pressurising hoses or pipework.
Check sensor location against the intended process condition. A sensor in a stagnant leg cannot represent operating flow. Record calibration status and expiry.
Verify electrical supply, emergency stop and control communications. Test loss-and-return behaviour. Confirm that restart authority is clear.
Run Practical Tests
Flush in the sequence specified for the installation. Capture debris or abnormal pressure changes. Do not conceal flushing problems by increasing flow.
Test the expected operating range, including a low-flow condition. Compare measured values with the accepted hydraulic basis. Investigate unstable pressure before handover.
Simulate credible alarms and confirm safe responses. Include loss of power, abnormal pressure and communications failure. Record operator actions as well as system response.
Handle Commissioning Sampling
Specify why a sample is required before choosing containers or laboratories. Define the sample point and timing around the process. Preserve the custody trail to the report recipient.
MEPC.325(75) commissioning testing is indicative only. It is not a full D-2 compliance validation. Do not describe an indicative test as universal compliance evidence.
Sea Clean can coordinate independent ISO 17025 laboratories and authorised parties where required. Laboratory availability and transport can affect the schedule. Confirm holding-time requirements early.
Manage Acceptance
Put contractual acceptance and regulatory acceptance in separate columns. They can require different documents. One does not automatically satisfy the other.
Verify applicable flag, port, class, authority, discharge permit and approval requirements for the particular operation. Conditions can differ by vessel and location. Keep correspondence with the project record.
PACT's public material describes treatment concepts, but project suitability requires assessment. Confirm hydraulics, utilities and local acceptance. Do not rely on a published flow range alone.
Close and Monitor
Issue a punch list with severity and release conditions. Distinguish defects that prevent service from documentation tasks. Re-test corrected critical items.
Create a baseline of pressures, alarms and control settings. It makes later degradation easier to identify. Store it with the as-built record.
Schedule an early operating review after handover. Compare actual throughput with the commissioning basis. Amend procedures where berth conditions differ.
Frequently asked questions
Is a commissioning test a D-2 certificate?
No. Indicative commissioning testing under MEPC.325(75) is not a full D-2 compliance validation. The applicable acceptance route must be confirmed for the project.
What records matter after installation?
Keep as-built drawings, test sheets, calibration status, alarm results and punch-list closure. These records explain what configuration was actually tested.
Should sampling delay start-up?
It depends on the agreed acceptance plan. Plan laboratory logistics and sample timing early so required evidence is not improvised.
Who resolves a failed test?
The project acceptance plan should allocate this responsibility. A defect owner, retest method and release condition should be recorded.