On this page
The factory and customer site answer different questions
At a factory, a qualified team may be able to demonstrate the built equipment against an agreed test setup. The U.S. site can add customer utilities, interfaces, upstream/downstream equipment and operating conditions that were not reproduced there. The actual product and project determine the safe test plan.
Endress+Hauser’s published commissioning offering includes engineering documentation and factory/site acceptance testing. That is an example of separately planned testing services, not a universal standard or proof of any project’s performance.
Nine completed checks do not make twelve complete
Fictional example: a project plan contains twelve agreed checks. Nine are completed at the factory; three require interfaces available only at the customer site. Those three remain open. A broad factory-test pass statement does not supply their missing results.
Record each check’s status and the evidence behind it. If a factory check was not run or failed, give that its actual status rather than placing it in the same category as an agreed site-only check.
| Requirement/check | Before shipment | At the installed site |
|---|---|---|
| Function reproduced in the approved factory setup | Record the actual result and test conditions. | Confirm whether the installation changes the basis of that result. |
| Customer interface absent at the factory | Record the agreed deferral and dependency. | Run the appropriate authorised check when the interface is available. |
| Exception or unrun check | Keep the issue and decision visible. | Resolve under the agreed technical/project process. |
Fund the people, equipment and customer preparation
Test materials, measurement equipment, travel, software versions, customer availability and follow-up work belong in the project plan. Ask who can approve technical readiness and who records an exception. The commercial payment or contractual acceptance event is a separate question for the actual agreement.
A customer signature does not itself establish that every technical result exists. Equally, this guide does not decide what a signature does under the contract.
Give the service team the result, not only the label
Before handover, management should provide the approved configuration, test results, unresolved items, agreed next actions and the customer/technical contacts entitled to decide. That gives the later service team a record of what was demonstrated and what still needs work.
Use that evidence to narrow or postpone the handover if important dependencies remain unresolved. Qualified personnel must decide the actual safe testing and return-to-use process.
Scope
- Original technical-project preparation framework using a supplier-described service offering. No FAT/SAT standard, safe test procedure, payment right, contractual acceptance or product approval is established.
Next step
Keep the detailed technical test matrix with the project records. Use Launch dependencies to assign the remaining site checks, required resources and technical handover decision.
Sources & review notes
Endress+Hauser
Passage, dates and research notes
company-guidance · Project documentation and engineering assistance; advertised Factory and Site Acceptance Tests
Read the service body, including documentation and FAT/SAT offerings. This is a supplier-described offering, not proof of performance, a universal test standard or an endorsement. ELN’s factory/site matrix is original.
Bookmark this guide or mark it as read.
Progress privacy
Saving is off by default. Without it, progress lasts only on this page. If you turn it on, this browser profile stores public content IDs and the progress you record. Anyone sharing the profile could see them. No plan inputs or contact details are included. Reset or export in learning settings.
This is a reading aid, not evidence of disclosure delivery, expertise or legal approval.