The relationship between a pharmaceutical manufacturer and its equipment OEM is one of the most important — and one of the most consistently mishandled — vendor relationships in a GMP facility. Get it right and the OEM is a strategic asset. Get it wrong and you spend years paying premium service rates for work that isn't quite what you needed and documentation that doesn't quite meet your QMS.
Here's what we've learned about getting the most from Glatt, Ohara, ACG, Vector, Thomas, and other major pharma OEMs.
What OEMs are great at
Three things, primarily.
Equipment-specific engineering knowledge. Nobody knows a Glatt GPCG better than Glatt. The factory technicians have seen failure modes you'll never see, know which subassemblies tend to drift, and can tell you in five minutes whether the symptom you're describing is normal aging or a real problem.
Parts and assemblies. Genuine OEM parts, current revisions, immediate availability for common consumables. The aftermarket exists, but for anything safety-critical or process-critical, OEM is the right answer.
Equipment-level service. Major overhauls, controller replacements, retrofits, capability upgrades. Anything that touches the equipment's design envelope should involve the OEM — both because they know what changes are safe and because OEM sign-off matters when you submit changes through your change control.
Where OEMs typically fall short
Not in capability — in scope mismatch.
Calibration scope. An OEM service visit typically calibrates the instruments they're trained to calibrate, using the procedures and tolerances in the equipment manual. That's often a subset of what your QMS requires you to calibrate, at intervals and tolerances that may be tighter than the OEM's. Their calibration certificates almost never include the as-found data your impact assessments need.
GMP documentation format. OEM service reports are designed to communicate what was done to the equipment, not to drop into your QMS as audit-defensible records. Signatures, traceability statements, NIST references, deviation handling — all of these vary by OEM and rarely match your internal expectations out of the box.
Scheduling flexibility. OEMs route their technicians across multi-state regions. The visit window for routine service is typically "this week or next." That's fine for major work; it's painful for the kind of rapid response calibration sometimes needs.
Pricing structure. OEM rates are appropriate for OEM-level work. Paying OEM rates for instrument calibration that a qualified third party could perform at half the cost is one of the most common cost leaks we see in calibration programs.
The pattern we see at well-run pharma sites: OEM handles major service, retrofits, and equipment-level engineering. A qualified calibration partner handles routine instrument calibration with documentation formatted to match the site QMS. Both are vendor-managed under the same calibration program.
How to structure the relationship
The mismatch isn't a bug in the OEM model — it's the OEM doing what OEMs do. Your job is to define scope clearly so each party does what they're actually good at.
- Define what the OEM owns. Major service, retrofits, capability upgrades, parts. Equipment-level engineering work. PLC software updates the OEM has to sign off on. Annual or scheduled engineering inspections if your contract calls for them.
- Define what someone else owns. Routine instrument calibration. Day-to-day troubleshooting. Site-defined modifications that don't change the OEM design envelope.
- Define how the documentation flows. OEM reports come into your QMS through a controlled receiving process. Your calibration program owns the calibration records of record. There should never be a question about which document is authoritative.
Specific recommendations by OEM
| OEM | Where they shine | Where to supplement |
|---|---|---|
| Glatt | GPCG, WST, fluid bed engineering, controller upgrades | Routine sensor calibration, GMP-format documentation |
| O'Hara | Tablet coater design, Labcoat/Fastcoat support, retrofit work | Per-instrument calibration with as-found data |
| ACG | FBC fluid bed engineering, integration support | Site-formatted calibration certificates |
| Vector / Freund | FLO-COATER engineering, parts | Routine calibration scheduling flexibility |
| Thomas Engineering | Accela-Cota expertise, coater performance tuning | Cost-effective recurring calibration |
The handoff between OEM and calibration partner
The most common failure mode in this relationship is the handoff — OEM does service, calibration partner does the next scheduled calibration, and the records don't reconcile. Either the OEM reports a calibration that the calibration program doesn't have a record of, or the calibration partner finds an instrument adjusted from where the OEM left it without any documented event in between.
Three things prevent that:
- Every OEM service event triggers a notification into your calibration program management system. Even if the OEM didn't calibrate anything, your program needs to know they were there.
- Any OEM calibration of a process-critical instrument is treated as a calibration event in your program of record — documented, with as-found data wherever obtainable, and reconciled against the prior calibration history.
- The next scheduled calibration after an OEM event includes an explicit check against the OEM report. Discrepancies are documented, not silently corrected.
Key Takeaways
- OEMs are the right answer for equipment-level engineering, major service, parts, and retrofits — they know their equipment better than anyone
- OEMs are typically the wrong answer for routine instrument calibration — scope, documentation format, and pricing rarely match what a calibration program needs
- Define cleanly which work belongs to the OEM and which belongs to a calibration partner; both should be managed under one program
- The handoff between OEM service and routine calibration is where records most often go wrong — build the reconciliation into your program from day one