Field fix / guideFAT / SAT DocumentVendor-agnosticQuality & Testingindustrial-automation

FAT Procedure Template — Full Coverage

Shared by TSIMEREZIVO Team · 4 Oct 2026 · 53 views

# Factory Acceptance Test (FAT) Procedure Template Project: ______________ System: ______________ FAT No: FAT-____ Location: ______________ Date: ______________ Rev: __ ## 1. Purpose Verify that the control system hardware and software conform to the functional design specification (FDS) before shipment to site. ## 2. References - FDS: ______________ - P&IDs: ______________ - I/O Schedule rev: ______________ - Cause & Effect diagrams: ______________ - Panel drawings: ______________ ## 3. Attendees | Name | Role | Company | Signature | |---|---|---|---| | | Test lead | | | | | Client witness | | | | | Vendor engineer | | | ## 4. Prerequisites — confirm before starting - [ ] All hardware installed and powered per approved drawings - [ ] Software build frozen — version recorded: ________ - [ ] Point-to-point wiring checks complete (megger + continuity) - [ ] Simulation/test equipment calibrated - [ ] Punch list format agreed - [ ] Previous FAT punch items closed: N/A or verified ## 5. Hardware verification - [ ] Physical inspection vs GA drawing (cable entries, labels, IP rating) - [ ] Power supply voltages within spec at each rail - [ ] CPU diagnostics clean — no faults logged - [ ] Redundancy failover: pull primary CPU/network — bump-free transfer - [ ] I/O card LEDs healthy; channel diagnostics enabled ## 6. I/O channel checks (per I/O schedule) For EACH channel record: forced/simulated value → system value → PASS/FAIL. - [ ] Analog inputs: 0% / 25% / 50% / 75% / 100% injection - [ ] Analog outputs: drive field simulator, measure at terminals - [ ] Digital inputs: contact open/close, including wetted vs dry - [ ] Digital outputs: energise/de-energise, measure at load terminals - [ ] RTD/TC: precision source simulation incl. upscale/downscale burnout ## 7. Functional tests (per FDS / C&E) - [ ] Every cause & effect row exercised — simulate cause, verify effect - [ ] Interlocks and permissives proven both directions - [ ] Sequence logic: step through each phase, verify transitions - [ ] Alarm setpoints, deadbands, and priorities verified on HMI - [ ] Trend and historian capture verified ## 8. Communications - [ ] Each network link broken individually — alarm + failover behaviour - [ ] Third-party links (Modbus/OPC/Profibus): data integrity spot checks - [ ] Cybersecurity: unused ports disabled, password policy verified ## 9. Failure modes - [ ] Power failure → orderly shutdown → restore → recovery - [ ] Air failure / UPS transfer tested where fitted - [ ] Watchdog / CPU fault behaviour ## 10. Punch list | # | Item | Category (A=stop ship / B=site / C=advisory) | Owner | Closed | |---|---|---|---|---| | 1 | | | | | ## 11. Sign-off FAT PASSED / PASSED WITH PUNCH ITEMS / FAILED — circle one. No Cat-A punch items may remain open at shipment.

More like this

Rate, comment, and get full access

Members can download files, rate contributions, and discuss fixes with the engineers who posted them — free.

Join the library