Factory Acceptance Test (FAT) / Site Acceptance Test (SAT)

FAT/SAT for <insert system name>
Project Number: Doc No:
Issue Date: <Date> Revision No:
Project Title:
Project
Description:
Factory Acceptance Test (FAT)/

Site Acceptance Test (SAT)
(This document should be a FAT or SAT please delete all references to the non-relevant one i.e. if
a FAT is being performed, delete all references to SAT)
for
<insert system name>
Custom Software
Doc Ref: SP-GEN-06 Factory Acceptance Testing/Site Acceptance Testing Page 1 of 17
Confidential
Revision No. Reason for Revision Date
00 Issued for Approval <insert date>
Custom Software
Confidential
TABLE OF CONTENTS
1 APPROVALS 4
1.1 PRE-APPROVALS....................................................................................................................................4
1.2 POST-EXECUTION APPROVAL...............................................................................................................4
1.3 AUTHORISED SIGNATURE LOG.............................................................................................................5
2 INTRODUCTION 6
2.1 PURPOSE.................................................................................................................................................6
2.2 SYSTEM DESCRIPTION...........................................................................................................................6
2.3 SCOPE.....................................................................................................................................................6
2.4 HOW TO COMPLETE THIS DOCUMENT.................................................................................................6
3 PRE-REQUISITES 9
3.1 DOCUMENTS REQUIRED FOR FAT/SAT...............................................................................................9

3.2 DEFINITIONS..........................................................................................................................................9
4 OPERATIONAL FUNCTIONAL CHECKS 10
5 RESULTS AND DEFECT MANAGEMENT 13
5.1 RESULTS LOG......................................................................................................................................13

5.2 DEFECT LOG........................................................................................................................................13
5.1 DEFECT FORM.....................................................................................................................................13
6 SUMMARY REPORT 14
6.1 CONCLUSION........................................................................................................................................14
6.2 COMMENTS..........................................................................................................................................14
7 LIST OF APPENDICES 15
7.1 RESULT LOG........................................................................................................................................16

7.2 DEFECT LOG........................................................................................................................................17
7.3 DEFECT FORM.....................................................................................................................................18
Custom Software
Confidential
1 APPROVALS
1.1 Pre-Approvals
<delete or add as appropriate>
Function Name Signature Date
Author / Creator
(Supplier)
Project Manager
System Owner
Quality
1.2 Post-Execution Approval
<delete or add as appropriate>
Function Name Signature Date
Author / Creator
(Supplier)
Project Manager
System Owner
Quality
Custom Software
Confidential
1.3 Authorised Signature Log
The following table is to be filled by any personnel involved in the execution and/or the
recording of test results during the SAT/FAT
Name (Print) Department/Organization Signature Initial / Date
Custom Software
Confidential
2 INTRODUCTION
2.1 Purpose
The purpose of this document is to ensure that <insert system name> is in compliance with
the requirements of <insert client name> prior to implementation at <insert site name>.
Performance/ Compliance will be recorded on the attached document; any defects will be
discussed/ accepted and/ or corrected prior to factory/site acceptance of the system.
The scope of supply for <insert system name> shall include but is not limited to requirements
outlined in <insert details of specifications such as Functional Spec, etc> and therefore final
payment is reliant on complete fulfilment of the scope along with observing any and all
requirements detailed elsewhere in this document.
2.2 System Description
<Briefly describe system including hardware, software, database, external devices, interfaces
and interface software as appropriate>
2.3 Scope
The scope of this Site Acceptance Testing (SAT) / Factory Acceptance Testing (FAT) is:
 <Briefly describe scope of testing>
2.4 How to Complete this Document
 Each test shall have the following details as a minimum:

o Test Objective
o Test Execution Procedure
o Acceptance Criteria
o Pass/ Fail
o Verified by/Date
Custom Software
Confidential
 Tests detailed in this protocol must be fully completed to provide all required data for
the testing of the system. Entries must be made only in Blue ink. Opaque liquefied
corrections are not permitted. Entries must be made at the time the observations
are made. Mistakes and/or corrections made must be crossed by a single pen
stroke, initialled and dated. The preferred date format is: dd/mm/yy, e.g. 22/06/11.
 The individual making the entries must initial and date the entry in the appropriate
box. If more than one individual makes entries in this protocol, each individual
will sign and date the entry in the box provided.
 All entries must be neat and legible. If the information is not applicable, N/A may be
used with an explanatory comment.
 All test results must be recorded directly into the protocol and recorded indelibly.
 Any corrections should be recorded directly onto the test results sheet, initialled and
dated.
 Short hand notation should be avoided.
 Spaces / Sections must not be left blank. Insert N/A, initialled and dated and where
required an explanatory comment provided.
 A Pass/Fail result must be determined upon completion of each check. A check will
fail if it does not comply with the acceptance criteria or the check is not verified.
All results must be filled out in the “Results Log”. Any exceptions noted during
testing should be referenced in the “Results Log” and documented in the “Defects
Log”. For each defect identified a “Defect Form” shall be completed.
 When all exceptions have been signed off, the SAT Lead who, if satisfied that the
equipment has passed the SAT satisfactorily, shall then complete the post-
approval page of this plan.
Custom Software
Confidential
3 PRE-REQUISITES
3.1 Documents required for FAT/SAT
SP-GEN-06 Development of a Factory / Site Acceptance Test (FAT/SAT)

<Reference all documents used in the FAT/SAT ensuring that they are the latest, approved
versions>
3.2 Definitions
<define all terminology used that may not be obvious to the reader>
Custom Software
Confidential
4 OPERATIONAL FUNCTIONAL CHECKS
Table 1 details the required functional tests for the FAT/SAT

<add or delete lines as appropriate>
Table 1: Functional Test Check List
FAT/SAT URS Reference Test Title

Reference Section
Number
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
4.9
4.10
4.11
4.12
4.13
4.14
4.15
Custom Software
Confidential
<Complete the below form for each test requirement>
Test Reference Number 4.1

Test Details
Test Objective
Acceptance Criteria
Step Procedure Expected Results Actual Results Pass/Fail Initial &

Date
1.
2.
3.
Custom Software
Confidential
4.
5.
6.
Overall Test Results:
Comments/Observations
Test Executed By: Signed: Date:

(Print Name)
Test Reviewed By: Signed: Date:
(Print Name)
Custom Software
Confidential
5 RESULTS AND DEFECT MANAGEMENT
Each test performed is to be recorded in the result log as below. All information listed must
be recorded. See Appendix 1 for the Result log.
5.1 Results Log
Results of each test completed during FAT/SAT are summarised on the Results Log (refer to
Section 7.1 Results Log)
For each result logged as a fail an item is also entered in the Defect Log.
5.2 Defect Log
Defects are logged in the Defect Log (refer to Section 7.2 Defect Log). A corresponding
Defect Form (refer to Section 7.3 Defect Form) is created for each logged defect in order to
track the changes/ deviations required solving the defect. The Defect Log should be reviewed
at the end of FAT/SAT execution.
An action must be agreed between the <insert client name> FAT/SAT Lead and Customer
Software representative as to the resolution of the defect.
5.1 Defect Form

A Defect Form must be filled out for each defect identified during FAT/SAT execution.
Custom Software
Confidential
6 SUMMARY REPORT
6.1 Conclusion
 The tests and checks detailed in this FAT/SAT have been completed and the
results documented.
 All results have been recorded in the result log and have been resolved. See
Appendix 1.
 All defects have been recorded in the defect log and have been resolved. See
section 7.2.
6.2 Comments
These comments result from a determination of the findings of the FAT/SAT. These should
include whether all of the FAT/SAT objectives have been met and a recommendation stating
whether <insert client name> considers <insert system name> ready for acceptance.
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
Completed by: ________________________ Date: _____________
Custom Software
Confidential
7 LIST OF APPENDICES
Record a list of any supporting additional documents used to support this FAT/SAT
execution at <insert client name> and append them to this protocol. Each appended document
should be signed, dated and the project number recorded once verified as correct.
Appendix Document Number of

Reference Pages
Comments:
Completed by: _______________________________ Date: _______________
Custom Software
Confidential
7.1 Result Log
Results of each test completed during FAT/SAT are summarised below
FAT/SAT Test Description Result Verified By: Defect

Reference (Pass/Fail) (Initial & Date) Reference (If
Number applicable)
<copy test descriptions from section 4 before printing out document>
7.2 Defect Log
Defects are logged below; a FAT/SAT Defect Form is to be attached for each defect tracking the changes/ deviations required solving the defect.
<fill out a FAT/SAT Defect Form each defect listed below>
Defect FAT/SAT Defect Description Re-test Closed Verified By:

Number Reference (Yes/No) (Yes/No) (initial & date)
Number
Custom Software
Confidential
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Custom Software
Confidential
7.3 Defect Form
<copy as required>
FAT/SAT Document Number & Revision

Defect Number
FAT/SAT Reference Number
Defect Description
Proposed Action to close out Defect
<Customer> Approval for Proposed Action

<Print Name> <Sign> <Date>
Customer Software Approval for Proposed Action
Description of Action taken to resolve defect
Retest
Is retest required? Yes No
If retest is required attach appropriate results.

Defect Resolved <insert date>
Approved By < Customer>:
Approved By Custom Software
Custom Software
Confidential

Factory Acceptance Test (FAT) / Site Acceptance Test (SAT)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Factory Acceptance Test (FAT) / Site Acceptance Test (SAT)

Uploaded by

Copyright:

Available Formats

FAT/SAT for <insert system name>

Project Number: Doc No:

Issue Date: <Date> Revision No: