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

Covers Systems we installed and systems we did not
Scope Preventive maintenance, consumables, sanitization, calibration coordination
Includes Derouging and repassivation when surface condition demands it
Response Defined commitment for unplanned failures, not best-efforts
Documentation Records written to survive an audit and a staff change
Coverage Nationwide, all 50 states

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.

The six things a process-system service contract has to specify
ElementWhat it must sayWhat goes wrong when it does not
Asset listEvery item covered, by tag number, with its actual configurationDisputes about whether the failed component was in scope.
PM scheduleTasks and intervals tied to the equipment installed, not a generic templateA generic schedule services what is easy and misses what fails.
ConsumablesNamed parts, replacement intervals, and who holds stockA three-day outage waiting on a gasket nobody stocked.
Response commitmentA defined time to respond and to attend, with escalation“We will get someone out” is unenforceable and unplannable.
DocumentationWhat records are produced, in what format, and who keeps themAn audit finding because maintenance evidence cannot be produced.
Change handlingWhat happens when a repair alters a validated systemA 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.

Standards referenced: ASME BPE · ISO 14644-1 · ISO 14644-2

An in-house maintenance team vs a contracted program

Most regulated plants end up running both, and the useful question is which tasks belong on which side of the line rather than which model is better.

Plant staff have advantages no contract reproduces. They are present when something starts behaving oddly, they know which pump has always run warm, and their work lands directly in the plant’s own quality system with no transfer step. Routine tasks, the ones whose value comes from being done on time rather than from specialist skill, are almost always cheaper and better done in house. The limits are narrow and specific: tasks that need qualified welders, calibrated test equipment, passivation chemistry handling, or a procedure written and approved for a one-off intervention. Keeping those capabilities in a team that uses them twice a year is difficult, and qualification lapses quietly between uses.

A contracted program brings the people, procedures and instruments for exactly those tasks, and it brings continuity across sites for a plant that has more than one. What it does not bring by default is presence. A contractor sees the system on scheduled visits, so the drift that happens between them is only visible if the plant records it. That is why the split works best when the in house team owns observation and routine execution, and the contract owns the interventions that need a qualification behind them.

The failure mode to avoid is a boundary nobody wrote down. When both parties assume the other is checking a filter differential or trending a sample result, the item is simply not covered, and that only becomes visible at the first excursion.

What to require from the baseline survey on a system you did not build

Taking over maintenance on an existing system starts with finding out what is actually installed. Insist on a survey deliverable before a schedule is written, and require it to include the following.

  • An as found asset register reconciled to the tags physically on the equipment, with the items that carry no tag listed as such rather than omitted.
  • A configuration check against the current drawings, noting every difference between the pipe in the plant and the pipe on the isometric.
  • Calibration status for every instrument the system depends on, including the ones nobody has calibrated because they were never in the schedule.
  • Measured slope and drainability on the lines that are supposed to drain, with the low points and any liquid held after a drain down recorded.
  • A surface condition assessment with dated photographs at accessible points, so rouge, pitting or discolouration has a starting reference instead of an opinion.
  • An age inventory of elastomers, membranes, resins, lamps and filter elements, with the last replacement date where it can be established and marked unknown where it cannot.
  • A spares audit that checks what is on the shelf against what the installed configuration actually needs, including shelf life on anything rubber.
  • A review of the last few years of excursions, deviations and repeat repairs, read for pattern rather than for individual cause.
  • An obsolescence check on controls, instruments and proprietary parts, naming anything no longer supported so a replacement plan exists before a failure forces one.
  • A defect register ranked by consequence, each entry stating whether the cause looks like design, installation or wear, because those three lead to completely different corrective work.

The register is the part worth paying for. A maintenance schedule written without it services what is easy to reach, and a system with a slope problem gets cleaned repeatedly instead of corrected once.

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.

What does taking over an unfamiliar system involve?

A condition and documentation survey first, because inheriting maintenance without knowing the installed state and what records exist means inheriting problems without their history. The survey usually identifies the first year of worthwhile work on its own.

How are like-for-like spares confirmed as genuinely equivalent?

By checking material, dimensions, surface finish and certification against the original rather than just the part number, because suppliers change specifications. An assumed equivalent that differs in elastomer material is a change presenting itself as maintenance.

What records should a maintenance contract produce?

Work orders with what was done, by whom, when, with what parts, plus calibration certificates, test results and any deviations found. The records have to be in a form the site can hand to an inspector without reformatting them first.

Why does the documentation clause matter more than the day rate?

Because on a regulated system the maintenance record is part of the evidence that the system remained in its qualified state. A cheaper contract that produces records the quality organisation cannot use costs more at the first inspection than it saved all year.

What does a service contract need to say about escalation?

Who is called, in what order, at what point, and who has authority to approve out-of-hours work and expedited parts. Escalation left undefined is the reason responses stall overnight and at weekends.

Should spares be held on site or by the contractor?

Critical spares with long lead times belong on site, because the point of holding them is to remove lead time from an outage. Consumables and common items can sit with the contractor. The list is built from what actually fails and what takes longest to obtain.

What should be agreed about access and permits in a service contract?

Who issues permits, what induction and training the contractor needs, the escort requirement, and the lead time for arranging all of it. Access administration rather than the work itself often determines how quickly a response actually starts.

How is contractor performance measured under a service contract?

Against agreed measures such as completion of scheduled work on time, response achieved, repeat failures and documentation delivered complete. Without measures, a contract renews on familiarity rather than on performance.

What clean utility and cleanroom testing can sit inside a service contract?

Scheduling and supporting particle count, airflow, filter integrity and pressure testing for cleanrooms, plus water, clean steam and compressed air sampling against the site specification. Independent certification is arranged where independence is required.

What clean utility testing belongs in a service contract?

Purified water and Water for Injection sampling against the system's own specification, clean steam quality testing, and compressed air and process gas testing where those contact product. The sampling plan comes from the site's validated programme rather than from a standard schedule.

How is preventive maintenance interval set?

From the equipment manufacturer's recommendation adjusted by the site's own failure history and the criticality of the system. Intervals that never change are usually either wasteful or inadequate, because the history is the information that should be updating them.

What does condition monitoring add?

Vibration, thermography and performance trending catch degradation before failure, which converts an unplanned outage into a planned one. On rotating equipment serving a critical process, that conversion is usually worth more than the monitoring costs.

Can a contract cover multiple sites under one standard?

Yes, and it is the main reason multi-site operators use one contractor. One documentation format and one set of procedures means the corporate quality group reviews one thing rather than reconciling several.

What should a service contract specify about change control?

Which activities are maintenance and which are changes, who notifies whom, what documentation each produces, and how an emergency repair is handled when there is no time for the normal route. The emergency case is the one most contracts leave undefined.

How does a maintenance contract start?

With a survey of the installed systems and their documentation, a scope built from criticality rather than from equipment count, and an agreed record format. The survey usually finds the first year's most valuable work on its own.

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.

Service needed *