A FAT (Factory Acceptance Test) is performed by the vendor prior to shipping equipment to verify it meets specifications. A SAT (Site Acceptance Test) is performed onsite after installation to verify proper installation and interface with other systems. SIT (System Integration Testing) tests the interaction and exchange of data between integrated systems to ensure successful co-existence.
A FAT (Factory Acceptance Test) is performed by the vendor prior to shipping equipment to verify it meets specifications. A SAT (Site Acceptance Test) is performed onsite after installation to verify proper installation and interface with other systems. SIT (System Integration Testing) tests the interaction and exchange of data between integrated systems to ensure successful co-existence.
A FAT (Factory Acceptance Test) is performed by the vendor prior to shipping equipment to verify it meets specifications. A SAT (Site Acceptance Test) is performed onsite after installation to verify proper installation and interface with other systems. SIT (System Integration Testing) tests the interaction and exchange of data between integrated systems to ensure successful co-existence.
A FAT (Factory Acceptance Test) is performed by the vendor prior to shipping equipment to verify it meets specifications. A SAT (Site Acceptance Test) is performed onsite after installation to verify proper installation and interface with other systems. SIT (System Integration Testing) tests the interaction and exchange of data between integrated systems to ensure successful co-existence.
Download as ODT, PDF, TXT or read online from Scribd
Download as odt, pdf, or txt
You are on page 1/ 2
The Difference Between a FAT and a SAT
It’s a question commonly asked in the validation arena, what is the difference between a FAT and a SAT. This article will finally explain what the difference is and how in your next interview you will know exactly why each one is required.
Any project that involves equipment being developed from a third party should have a FAT and SAT incorporated into the system life-cycle. If both the FAT and SAT are performed correctly is will lead to a much easier IQ/OQ process.
What is a FAT
A FAT or Factory Acceptance Test is usually preformed at the vendor prior to shipping to a client. The vendor tests the system in accordance with the clients approved test plans and specifications to show that system is at a point to be installed and tested on site.
It’s an essential aspect of the whole system lifecycle and should be performed by experienced personnel. Time spent doing a proper FAT will lead to fewer problems when the equipment is installed on your site.
On acceptance of a FAT some items to look out for include:
Performed FAT Protocol
Maintenance and User’s manual
Recommended spare parts list
Certificate of compliance
As built technical drawings (electrical, mechanical, pneumatic & process schemes)
Materials certificates/data sheets
Main equipments data sheets
Instruments calibration certificates
Welding Processes qualification
What is a SAT
A SAT is a Site Acceptance Test the system is tested in accordance to client approved test plans and specifications to show the system is installed properly and interfaces with other systems and peripherals in its working environment.
Below is a list of some items that should be considered when performing a SAT:
SIT In the context of software systems and software engineering, system integration testing (SIT) is a testing process that exercises a software system's coexistence with others. With multiple integrated systems, assuming that each have already passed system testing,[1] SIT proceeds to test their required interactions. Following this, the deliverables are passed on to acceptance testing.
Introduction SIT is part of the software testing life cycle for collaborative projects. Usually, a round of SIT precedes the user acceptance test (UAT) round. Software providers usually run a pre-SIT round of tests before consumers run their SIT test cases. For example, if an integrator (company) is providing an enhancement to a customer's existing solution, then they integrate the new application layer and the new database layer with the customer's existing application and database layers. After the integration is complete, users use both the new part (extended part) and old part (pre-existing part) of the integrated application to update data. A process should exist to exchange data imports and exports between the two data layers. This data exchange process should keep both systems up-to-date. The purpose of system integration testing is to ensure all parts of these systems successfully co-exist and exchange data where necessary. There may be more parties in the integration, for example the primary customer (consumer) can have their own customers; there may be also multiple providers.
