Once the 3D model is approved, the project leaves the digital world and steps into the real one.
What used to exist only on a screen is now standing in a factory, wired, piped, assembled, and ready (in theory) to do the job it was designed for.
And this is where things get serious.
Because a beautiful model doesn’t guarantee a compliant, safe, or functional piece of equipment. The FAT is the moment of truth, the place where preparation, discipline, and structure turn a drawing into something you can trust.
This article naturally follows the 3D model review: the design is locked, and now the equipment must prove it can deliver.
How to Conduct an Effective Equipment FAT
Equipment Factory Acceptance Testing (FAT) is one of the most important milestones in a project. It’s where the equipment is proven against specifications before it leaves the vendor’s floor. A well-run FAT builds confidence and removes risk. A poorly run FAT adds no value, burns days of travel, and leaves problems for site installation.
Here’s how to make sure your FAT is worth the effort.
Define a Clear FAT Scope
Start with a protocol that everyone signs off. Spell out exactly what will be tested: functions, performance, GMP and safety requirements, and the acceptance criteria. Just as important—be clear about what is not tested. If a test can only be done after installation, say so. Nothing derails FAT faster than a client expecting a site-level test in a factory environment. Scope definition sets expectations and prevents endless debates.
Complete a Pre-FAT
The vendor must run a pre-FAT before the client ever steps foot in the factory. This is not optional. It’s where calibration is checked, alarms are proven, safety guards verified, and obvious errors fixed. Without pre-FAT, the client becomes the vendor’s quality control team and that is never acceptable. A polished FAT starts with a completed pre-FAT.
Define the Teams and Responsibilities
When FAT starts, everyone should know their job. On the vendor side, the technical team must have the system powered, documents prepared, and technicians available to run the machines. On the client side, process engineers, QA, operators, and EHS need to witness, verify, and raise punch points. One FAT lead coordinates the whole thing making sure the right people are present, tracking progress, and holding sign off authority.
Build the Schedule
FAT without a schedule is chaos. Start with the overall FAT window—what systems, in what order. Break this into system level FATs, so you know when each package (CIP skid, control panel, vessel) will be tested. Then go down to the day-by-day detail: what’s happening each morning and afternoon, which team members need to be on site, which test cases are run, and where contingency time is built in.
Use a Go/No-Go Checklist
Before the client shows up, a go/no-go checklist must be signed off. This checklist is the gate that decides if FAT can even begin. It includes fabrication evidence, approved engineering documents, pre-approved FAT protocol, utilities available, test equipment/components available, and FAT area prepared. It’s far better to reschedule the FAT than to drag the client into a factory where the equipment is not finished and not ready for testing.
Manage the Punch List
Every FAT produces punch points. Log each with a unique ID, description, owner, and due date. Manage them in a shared platform to ensure vendor and client can access without IT issues. Closure is only valid with evidence, updated drawings, photos, or retest results.
Control Document Versions
Never start a FAT unless everyone is looking at the same version of every document. Drawings, P&IDs, software, calibration sheets, FAT protocol, everything must be aligned. The FAT lead should confirm versions at the pre-FAT stage and lock them for use during testing.
Training for FAT, GMP, and Safety
Everyone participating in FAT needs training. GMP training so they know how to fill out FAT protocols in a compliant way. Safety training so they know how to operate equipment, follow energization procedures, and respond in an emergency. And FAT-specific training so operators, QA, and engineers know how to record results and recognize valid outcomes.
Other Best Practices
Strong FATs share a few extra traits. A detailed inspection test plan makes sure no test is missed and all results trace back to the URS. Failure scenarios are tested, not just pass cases, so the system is proven robust. Deviations are logged, investigated, and formally closed. And the FAT report is structured, GMP compliant, and ready to form the basis of qualification documentation.
An effective FAT is not just about turning equipment on and checking a few boxes. It’s about preparation, structure, and discipline. Define the scope so expectations are aligned. Run a pre-FAT so the client is not the vendor’s test team. Define roles and responsibilities, build a layered schedule, and enforce a go/no-go checklist. Manage the punch list with evidence, lock in document versions, and make sure everyone is trained.
Follow these steps, and FAT becomes a milestone that reduces risk and builds confidence. Skip them, and FAT becomes a wasted trip that adds no value to the project.
And once the equipment leaves the factory? That’s another story.
Need some help?
If you need help with conductin an efffective equipment FAT, just drop us a line hello@nodeviation.com
