EPC Engineering

“Based on available data” is working harder in your spec than four words should. It shows up in EPC documentation constantly, and it’s technically accurate every time — the data you had was the data you used. That’s also the problem. The phrase is a hedge, not a finding. It tells the reader the design basis reflects whatever characterization window happened to be available, not the conditions the system will face over its actual life. Conservative sizing. Self-cleaning capabl

Every steady-state filtration spec carries the same flaw: the influent data behind it was never meant to describe the plant’s worst day. That’s not a knock on the data. A few weeks of grab samples, maybe a full season if the budget allowed it, averaged into a single total suspended solids (TSS) number for the design basis; that’s what everyone works with. Nobody hands an EPC a year of hourly readings from a really challenging month of operations. Averaged data is what’s avail

The specification a plant runs on is written by people who will never operate it, and the gap between those two vantage points is where most filtration disappointment lives. That is not a criticism of EPC teams. It is the structure of the job. The engineer writing the design basis works from characterization data, datasheets, and design conditions — an honest but partial picture of a stream that will behave in ways no sample window fully captured. The operator, eighteen month