Contract awards get the headlines. Water Finance and Management reported that the San Francisco Public Utilities Commission has awarded the $1 billion Southeast Water Pollution Control Plant "nutrient reduction project" to a joint venture of PCL Construction Inc. and Jacobs Project Management. The report is a contract-level item. It does not describe the commissioning schedule, the acceptance tests, or the documents that will pass to plant staff at closeout, and this article does not assume any of them. What follows is a general account of the records a utility should expect to receive, and when to ask for them, on any retrofit that adds nutrient removal to an existing treatment train.
Why a nutrient retrofit creates a different file
Nitrogen and phosphorus control usually adds process steps rather than replacing the old ones. A biological nitrogen stage may need its own aeration control, dissolved oxygen sensing, and recycle pumping. A chemical phosphorus stage adds feed systems, dosing pumps, storage, and a sensor or analyzer that tells the controller how much to feed. Each addition brings instruments, control loops, and alarm points that did not exist in the prior configuration. Each one needs a calibration record, a setpoint basis, and a documented way to fail safe.
The consequence for records is simple. A plant that gains three new control loops in a retrofit has three new things the operator must be able to explain on the day something drifts. If the file shows only the final installed condition, the staff inherits a plant they cannot reconstruct from paper.
The documents that matter at handover
A commissioning file for a project of this type generally covers several layers. The exact list will depend on the contract, but the following categories are the ones most often missing when plant staff go looking for them later:
First, the as-built process and instrumentation drawings, marked to reflect field changes made during installation rather than the design issued for bid. Second, the control narratives, which describe in plain language what each loop is supposed to do, including what happens on a sensor failure, a pump trip, or a loss of communication. Third, the controller and supervisory software, delivered as a backup with a version identifier and a date, along with a note of who holds the source copy. Fourth, the alarm setpoint list, exported from the system as it stood at acceptance, not as it was typed into a design spreadsheet.
Fifth, instrument calibration sheets and the as-found and as-left values from the initial checks. Sixth, performance test data covering the plant at more than one flow and load, since a nutrient stage that meets its limit at average flow may behave differently during a wet-weather peak. Seventh, operation and maintenance manuals, spare parts lists, and the vendor contact for each major item, with warranty start dates stated. Eighth, a record of training delivered to staff, with attendance and the topics covered.
Staged startup complicates the timeline
Large plants rarely start all at once. Process trains are often commissioned in sequence, and parts of the plant may run under temporary controls or manual operation before the permanent logic is accepted. That approach is sensible for risk, but it creates a file with gaps in time. The utility may hold test data for one train, a temporary control arrangement for another, and no final logic for the third.
A useful practice is to ask, for each stage, which document will carry the operating basis once that stage is accepted, and to note whether any temporary arrangement remains in service. A temporary bypass that was meant to last a few weeks can persist for years if no one records its status. The record should say when a temporary condition ended, or that it did not.
Access and control of the system
The records question overlaps with access. The contractor's engineers usually hold the controller programs, the engineering workstations, and the administrative credentials at the start of commissioning. Ownership of those assets should transfer in writing, with a list of accounts, a record of who changed the passwords, and confirmation that the utility can make a controlled change without the contractor's involvement. A utility that cannot open its own control logic cannot audit it, and cannot prove later that a setpoint change was authorized.
Where the tradeoffs fall
There is a real tension here. Contractors want closeout, and final payment often depends on it. Utilities want to avoid accepting a plant they cannot operate. A common compromise is to tie a portion of final payment to delivery of the closeout package, with a defined list and a review period. Whether a given contract does this is a question for the contract itself, which this article has not reviewed.
The practical advice is to start early. Request a draft document index at the start of commissioning, not at the end. Mark each item as received, received in draft, or outstanding, and review the list at each stage gate. A file assembled this way is less likely to surface as a surprise the first time the plant runs a wet-weather peak with a sensor out of service.