Factory Acceptance Test Fat Procedure Example Document

What the FAT Procedure Document Actually Needs to Cover

A Factory Acceptance Test procedure is just a structured checklist of every test the equipment must pass before it leaves the manufacturer's door. The document itself is usually 5 to 15 pages, sometimes more for complex systems. It walks the tester through each check, records the result, and builds the audit trail that the buyer's team will actually review during acceptance. Most people think the value is in the testing. It isn't. The value is in the paperwork. A well-structured FAT procedure document with an attached example sheet is what gets the equipment signed off on time and prevents the buyer from finding a gap three weeks after installation. I have seen projects stall for days because someone forgot to include a pressure relief valve pop test in the procedure and the client refused to acknowledge the unit as complete.

Standard Sections You Will See in a Real FAT Procedure Document

1. Document Header and Revision Control

Every proper document starts with a header block. Document number, revision number, date, title, equipment tag, and manufacturer details. The revision control table logs each change with a short description. This seems basic but it is where most people cut corners. When you hand a FAT procedure to a client, the first thing they look at is whether revisions are tracked. If they are not, they assume the rest of the document is equally sloppy. This section states what the test covers and what it does not cover. Be specific. "This procedure applies to the acceptance testing of Centrifugal Pump P-101A/B manufactured by XYZ Corp, model 250CD, serial numbers 4401 through 4410." Include exclusions too. If hydrostatic testing is being handled by a separate procedure, say so. Ambiguity here causes arguments at the factory gate. List the codes and standards that govern the tests. API 610 for centrifugal pumps. ASME B31.3 for piping. ISO 10816 for vibration. IEC 60034 for motors. If the client has company-specific standards, reference those as well. Do not guess at standards. Look them up. I once had a procedure reference the wrong edition of API 610 and the client's inspector flagged it before we ran a single test. That wasted half a morning.

This is the most practical section of the document. It covers what must be true before any test begins. Mechanical completion status, calibration certificates for all instruments, safety briefings, PPE requirements, personnel roles, and available utilities. Include a sign-off table where the contractor, manufacturer, and client each initial that the prerequisites are met. Never skip this. It shifts the conversation from "we weren't ready" to "we confirmed readiness and still had issues." I had a situation where a pump was tested without the vibration pickup mounts being installed because the procedure did not call them out as a prerequisite. The vibration readings came back noisy and inconclusive. We had to stop the test, remove the pump from the skid, install the mounts, and restart everything. Two days lost. The fix was simple: adding a pre-test checklist with photos of required equipment setup.

5. Test Procedures with Step-by-Step Instructions

Each test gets its own subsection with numbered steps. This is the core of the document. The steps must be written so that a competent technician can execute them without asking clarifying questions. Vague steps like "run the pump and check for abnormalities" are useless. Replace them with "Start pump P-101A. Monitor bearing housing temperature for 30 minutes. Record values at 5-minute intervals. Acceptance criterion: temperature rise shall not exceed 40 degrees Celsius above ambient." Specific numbers, specific intervals, specific acceptance criteria. Every test needs a pass or fail threshold. These come from the project specifications, the equipment datasheets, and the applicable standards. Pull the exact values. Do not round them off. If the specification says vibration must be below 2.8 mm/s RMS, write 2.8, not "under 3" or "within acceptable limits." The client will find the difference and use it to delay acceptance. Include blank tables for recording actual measurements during each test. Column headers should include: parameter name, design value, acceptance limit, measured value, units, instrument ID, and result (pass/fail). Pre-formatting these tables saves time on the day of testing and ensures nothing gets forgotten. I always add a column for "remarks" because there is always something to note. A pressure transducer that drifted slightly during a long test. A temperature reading that spiked briefly and then stabilized. These details matter when someone reviews the document six months later.

Tests do not always pass. The document should include a section explaining how deviations are documented. A deviation form number, who authorizes it, how it is classified (minor or major), and the process for retest. Most contracts require all major deviations to be resolved before acceptance. Write that down clearly. The final page is the signature block. Manufacturer representative, client representative, independent inspector if applicable, and date. Sometimes you need a section for photographic evidence reference numbers. Keep it clean. One page is enough. Start with the project specifications. Those documents dictate the tests, the criteria, and the standards. Extract every requirement into a traceability matrix. This matrix maps each specification clause to the corresponding test in your procedure. The client will ask for this matrix. Having it ready makes you look organized and saves three hours of scrambling.

Use a template that has worked for similar equipment. Do not start from a blank page every time. Modify the existing template to match the new equipment and project requirements. This approach cuts drafting time significantly and reduces the chance of omitting a required test. I keep a library of templates for pumps, heat exchangers, compressors, and control panels. For a typical centrifugal pump FAT, the draft takes about 4 hours including review. From scratch, it would take me 8 or 9. Include a sample completed test record in the appendix. This shows the client exactly how data will be recorded and gives them confidence that the testing process is controlled. A blank procedure looks theoretical. A completed example looks practical.

Common Mistakes That Make FAT Procedures Unusable

Writing acceptance criteria that conflict with the project specifications. This happens when someone copies a generic procedure and forgets to update the limits. Always cross-check every criterion against the approved datasheet. Forgetting to include instrument calibration traceability. Every measuring device used during the test must have a current calibration certificate on file. State this requirement in the procedure. I had a client reject a temperature reading because the thermocouple's calibration had expired by one week. They were within their rights. The procedure should have explicitly required calibration verification before each test. Omitting safety interlock tests. These are easy to skip because they are not exciting, but they are critical. A pressure relief valve that fails to pop at the set pressure is a serious defect. Include it. Include motor rotation verification. Include electrical insulation resistance testing if the motor is part of the scope. These take five minutes on the day of testing but prevent major problems later.

Making the procedure too long. A 40-page FAT procedure for a single pump is unnecessary. The reader will skip sections. Keep it under 15 pages whenever possible. Use appendices for supporting documents like calibration certificates and drawings.

Factory Acceptance Test Fat Procedure Example Document

If you need a starting point, search for industry-standard templates from organizations like ASME, API, or ISO. Many engineering consultancies publish sample FAT procedures for specific equipment types. The one I rely on most is a custom template built from the API 610 FAT guidelines combined with a few of my own modifications. It covers all the standard tests for centrifugal pumps and includes the traceability matrix and deviation form as integrated sections. Downloadable versions exist on several engineering resource sites and from professional associations. Look for documents that include blank data tables with the proper columns rather than just text descriptions. The tables are the part that saves time during actual testing.

Advanced Nuance: The Hidden Bottleneck in FAT Procedures

Most people focus on the test steps. The real bottleneck is coordination. A FAT procedure is only as good as the schedule around it. You need the client's inspector present for every critical test. If the inspector is scheduled for Tuesday but the mechanical completion is delayed until Wednesday, the entire FAT timeline shifts. Include a coordination schedule in the procedure appendix that lists each test, its estimated duration, and the required attendees. This forces everyone to think through logistics before the testing day arrives. Another thing beginners miss: the difference between a witness test and a hold point. A witness test means the client watches it happen. A hold point means work cannot proceed until the client has approved the result. Mixing these up causes confusion on site. I once had a contractor treat a hold point as a witness test. The client's inspector showed up late, saw the pump running, and assumed everything was fine. The vibration reading was off-spec but the test had already finished. The client refused to sign. We had to remove the pump, investigate, and retest. Six days. If the procedure had clearly marked the vibration test as a hold point, the contractor would have stopped and waited.

Final Practical Notes

Print the procedure on the day of testing. Digital copies on tablets are fine as backup, but paper is what people actually write on. Bring three copies: one for the manufacturer, one for the client, and one for your own records. Label each copy with the equipment tag and serial number. Do not start testing until every prerequisite box is checked and signed. Rushing into tests without confirming calibration status, safety conditions, and utility availability is the fastest way to waste a full day. I have seen it happen. It is not fun to watch. The FAT procedure document is not a bureaucratic hurdle. It is the single most important tool for ensuring the equipment you built actually works and that the client accepts it without unnecessary friction. Treat it with the same care you treat the equipment itself.