The Factory Acceptance Test App Built for the Front Line
Sitemate’s Factory Acceptance Test App is powered by Dashpivot, and allows site teams to easily log factory acceptance tests at the job site. Storm, Sitemate’s AI agent, can fill out reports with test results, equipment details, and even photos, then site supervisors can review, edit, and sign off directly on the form via e-signature.
Why Factory Acceptance Test management Is Harder than It Should Be
Slow manual test recording
Inspectors using paper-based forms take a long time to record test results and measurements during factory acceptance tests.
Missing and illegible test records
Paper-based test forms can easily get soiled or damaged. Furthermore, paper forms are easy to lose before results reach the office.
Disputes over equipment performance
Without clear records of test conditions and results, disputes with vendors over underperforming equipment become difficult to resolve.
Cannot preview past test records
Completed paper test forms are usually filed away, which limits visibility on previous tests. This can cause a disconnect between site teams and vendors.
A Smarter Factory Acceptance Test App
AI-assisted test report creation
Storm can help turn user prompts into a complete factory acceptance test report, pre-filled with details that are specific to user input.
Streamlined testing with photo capture
Inspectors can log test results, take photos of any issues, and notify relevant personnel for follow-up, all from their mobile device.
Supervisor review before sign-off
All completed test reports are routed to supervisors for review and approval, which ensures issues are addressed and accountability is not compromised.
Cannot preview past test records
The Factory Acceptance Test App uses a cloud storage system where all completed reports are stored. Looking into past tests can be done with a few taps and clicks.
Understanding Factory Acceptance Test Software
What is a Factory Acceptance Test App?
A Factory Acceptance Test App is a tool that quality and engineering teams use to create factory acceptance test reports, documents that record the testing and verification of equipment at the manufacturer's facility before it is shipped to site. These reports are usually created during the test itself, and cover details on the equipment tested, the test procedures followed, and whether the results meet the required specifications. With a Factory Acceptance Test App, teams can keep a digital record of these tests, as well as any deviations or issues raised during the process.
What does a Factory Acceptance Test App help record?
- General information like project name, manufacturer, and test date
- Equipment description, model, and serial or reference number
- Test procedures and standards followed
- Test results and measurements against required specifications
- Any deviations, defects, or issues identified during testing
- Corrective actions or disposition, such as accept, reject, or retest
- Names and signatures of witnesses and responsible personnel
- Supporting photos and attachments
Why are factory acceptance tests important?
Factory acceptance tests are important because they are a means by which project teams can verify that equipment meets the required specifications before it leaves the manufacturer's facility, and escalate any deviations to engineering or procurement for proper action. These deviations can arise from factors like manufacturing defects, incorrect specifications, or assembly errors. This is especially relevant to industries like construction and industrial or manufacturing plants, where equipment often needs to perform reliably once installed on site. Additionally, these reports serve as a basis for project teams when resolving disputes with manufacturers over equipment that fails to meet the agreed requirements.
-
Feed Storm the factory acceptance test details
Storm can pull insights from user prompts, photos, and voice notes, and use that information to fill a pre-set factory acceptance test report.
-
Data mapping
Storm fills the form with information, such as test criteria, equipment specifications, and pass or fail results, relevant to the user’s input.
-
Review the draft and confirm test results
Engineers should review the generated report to confirm test outcomes and add any required context. This is especially important for equipment with complex specifications or multiple test criteria.
-
Sign-off by quality engineers
All that is left to do is for quality engineers to review the submitted report, add any final notes, and approve it for sign-off. Once approved, the report is sent to the relevant stakeholders or approvers for their review.
See How Sitemate Has Already Helped Companies Like Yours
"Everything is in real-time. No longer do we need to print out forms or take out hard copies."
- Brian Mahon, COO
80%
Time saved on document handling
90%
Faster approvals
Simpler reporting on factory acceptance tests with Flowsite
Flowsite automatically transfers completed factory acceptance test data from Dashpivot into quality dashboards and client reporting systems, removing the need for manual re-entry. Quality and project teams get real-time visibility of test results, so equipment can be reviewed and approved with minimal admin work.
Comparison: Paper Factory Acceptance Test vs Digital Factory Acceptance Test
Most project teams already know paper and spreadsheets aren't cutting it. Here's what changes when you move your method statements to a digital system.
Paper |
||
|---|---|---|
| Test form preparation | Storm uses voice notes, field notes, and other user input to create factory acceptance test forms with pre-filled data that inspectors can use as a guide. | Factory acceptance test forms must be filled out from scratch every time, relying on the inspector's memory of what was checked. |
| Test report format | Consistently get accurate and quality content, neatly formatted within a standard form for all factory acceptance test reports. | Factory acceptance test report quality and completeness vary depending on who is preparing and filling out the form. |
| Versioning | Everyone works from one live version that's always up to date. | Supervisors have to manually update and send out the most recent version of the factory acceptance test form. |
| Recording speed and flexibility | Inspectors can log test results within minutes, straight from a phone or tablet, right on the factory floor. | Recording test results means inspectors need to spend time manually logging and filling up a form by hand. |
| Photo evidence | Photos of equipment, nameplates, or issues can be attached directly to the test report at the time of inspection. | Photos are often taken on a separate device and matched up with the paper report afterward. |
| Punch list and deficiency tracking | Deficiencies can be flagged on the spot, with follow-up actions assigned straight away. | Flagging a deficiency means noting it on paper and following up separately, which can slow down the response. |
| Approvals and sign-off | Once the test is complete and the report is submitted, the appropriate personnel are automatically notified for review and approval. | Getting the approving personnel to sign-off means physically passing on, scanning, or emailing the paperwork. |
| Audit trail | Every submission, edit, and approval is time-stamped as soon as it is made. | Each change or edit must be time-stamped manually, and tracking these changes will require more digging. |
| File-keeping and tracking | Factory acceptance test reports can be sorted and filtered by date, project, equipment, and more in just a few clicks. | Finding a past record means manually sorting through folders, paper files, emails, or spreadsheets. |