Paul Industries holds service and maintenance contracts on high-purity water systems, CIP/SIP skids, cleanrooms, process piping, autoclaves, chillers and process equipment, including systems we did not install. A contract covers scheduled preventive maintenance, consumable replacement, sanitization support, calibration coordination, derouging and repassivation, and a defined response commitment when something fails. Most plants split installation and maintenance across different vendors and lose the system knowledge in the gap.
Request a quote or call 201-450-8280
What a process-system service contract should actually contain
Most maintenance agreements in this industry are one page of generalities and a day rate. That is not a contract, it is an intention. A contract that protects a regulated plant needs six things written down, and if any of them is missing you will discover it at the worst possible moment.
| Element | What it must say | What goes wrong when it does not |
|---|---|---|
| Asset list | Every item covered, by tag number, with its actual configuration | Disputes about whether the failed component was in scope. |
| PM schedule | Tasks and intervals tied to the equipment installed, not a generic template | A generic schedule services what is easy and misses what fails. |
| Consumables | Named parts, replacement intervals, and who holds stock | A three-day outage waiting on a gasket nobody stocked. |
| Response commitment | A defined time to respond and to attend, with escalation | “We will get someone out” is unenforceable and unplannable. |
| Documentation | What records are produced, in what format, and who keeps them | An audit finding because maintenance evidence cannot be produced. |
| Change handling | What happens when a repair alters a validated system | A like-for-like repair quietly becomes an unmanaged change. |
Why the documentation clause matters more than the day rate
In a regulated plant, maintenance is not just an engineering activity, it is evidence. An inspector asking why a water system drifted out of specification will want to see what was done to it, when, by whom and with what parts. If your contractor keeps those records in a van and a phone, you do not have a maintenance history, you have anecdotes.
The related failure is the knowledge gap. When installation and maintenance sit with different companies, nobody owns the question of why the system behaves the way it does. The installer knows the design intent and leaves. The maintenance vendor knows the failure history and never saw the design. Six years later a recurring microbial excursion gets treated as a cleaning problem when it is a slope problem, because the two halves of the story were never in the same place.
What we cover
- Preventive maintenance Scheduled tasks matched to your installed equipment, with records written for audit rather than for invoicing.
- Water system support Sanitization support, membrane, resin, filter and UV lamp replacement, and sampling coordination.
- Derouging and repassivation On hot loops this is a maintenance certainty rather than an incident, and it belongs in the plan.
- Emergency response Defined response for unplanned failures, including out-of-hours where the contract calls for it.
- Shutdown and turnaround work The work that can only happen with the plant down, planned and staged so the window is not wasted.
Why Paul Industries
We build these systems, which means we maintain them knowing why they were designed the way they were. On systems we did not install we start by understanding the design intent rather than by replacing parts, because most recurring faults in sanitary systems are design or installation artefacts rather than component failures. And because we self-perform the piping, welding and passivation, a repair that turns into a modification does not need a second contractor and a second mobilization.
Frequently asked questions
Will you maintain a system another contractor installed?
Yes, and it is a large share of this work. We start with a survey: what is actually installed, how it is configured, what the documentation says and where the existing records are. That survey frequently surfaces the reason a system has been troublesome, because recurring faults in sanitary systems are far more often design or installation artefacts than component failures. Only then do we propose a maintenance scope.
What does a service contract typically cost?
It scales with the asset list, the response commitment and how much consumable stock is held for you. A contract covering scheduled maintenance on a single water system is a very different number from one covering water, CIP, autoclaves and chillers with an out-of-hours response commitment. What we will not do is quote a day rate and call it a contract, because the day rate is the least important number in the agreement.
How fast can you respond when a system goes down?
That is a contract term rather than a general claim, and it should be written as a defined time to respond and a defined time to attend, with an escalation path. The honest constraint is travel: a plant two hours from a crew base gets a different commitment than one six hours away. We would rather write a response time we can meet every time than a headline number we meet when convenient.
Does routine maintenance count as a change to a validated system?
Like-for-like replacement generally does not, provided it is genuinely like-for-like and documented. The risk is drift: a gasket in a different material, a pump with a slightly different impeller, a valve from another manufacturer because the original had a lead time. Each is defensible alone and collectively they can invalidate the qualification argument. The contract should say who decides when a repair has become a change.
What records will we receive?
Work performed, date, who performed it, parts fitted with their identification, measurements taken and anything found that was not on the schedule. That last category matters most, because the observation that a surface is starting to rouge or a valve is passing slightly is what lets you plan work instead of reacting to a failure. Records are handed over in a form you can put in front of an inspector.
Do you hold spares for our system?
Where the contract calls for it, yes, and it is usually worth doing for the small number of parts whose absence stops production. The analysis is simple: for each consumable, how long is the lead time and what does an hour of downtime cost. Gaskets, seals, filter elements and UV lamps are cheap to stock and expensive to wait for. Large items are usually better handled by planning than by stocking.
Can maintenance be scheduled around production?
It has to be, in practice. Most of what we do on live plants happens in planned windows, during a shutdown or between campaigns, and the planning matters more than the work. The scope that needs the system drained, cooled and released is grouped into a single outage rather than spread across several, because each return to service costs testing time before the system can be used again.
What is usually missing from an existing maintenance contract?
Three things, repeatedly. A real asset list, so scope disputes are inevitable. A documentation clause, so there is no maintenance evidence when an inspector asks. And any provision for derouging or repassivation, which on a hot high-purity loop is not an unexpected event but a scheduled certainty that nobody budgeted for until the surface failed.
Do you cover cleanroom recertification?
Yes, and it is worth putting on the same schedule as the rest of the plant. Recertification to ISO 14644-2 needs the room in a defined state, so it competes for the same production downtime as water system sanitization and piping work. Planning them together usually costs one outage instead of three, which is the single largest saving available on a maintenance program.
How do we start a maintenance contract with you?
Use the form on this page or call 201-450-8280. The useful starting point is a list of the systems you want covered and any documentation you already hold, including original qualification packages if they exist. For systems we did not install we will normally propose a survey first, because writing a maintenance scope without knowing what is actually installed produces the generic contract this page argues against.
Need a service contract that holds up in an audit?
Tell us what systems you run and who maintains them now. Call 201-450-8280 or use the form below.