Machine Factory Acceptance Test Checklist
Fill scope, samples, the customer cycle, exceptions, handover and retest in that order. Applicable scope: the record keeps the factory observations for one configuration. Safety certification, warranty and shipment authorisation stay in the referenced agreement.
Factory acceptance record
Identify the unit and the agreed test scope
Agree the procedure, participants and acceptance criteria for the particular configuration before the demonstration. Do not attempt a hazardous fault simulation or bypass a protection device; specialist testing belongs with appropriately qualified personnel and the applicable documented procedure.
Quality checks from configuration to handover — Input to this factory record: the model, options, agreed checks and the configuration revision that each inspection stays linked to.
Record the samples and operating conditions
Identify the products, packaging, ingredients or consumables used in the test and explain whether they represent the intended site supplies.
Observe the complete customer cycle
Define the start and successful end of the customer task. For vending, inspect release, collection and product condition. For service or preparation equipment, record the agreed output and completion indicators.
Trading Card Vending Acceptance Tests — Next record when this factory cycle is a packaged-card release: product condition, a failed transaction and the corrective action stay with the same configuration.
Trace payment and controlled exceptions
Use the agreed payment test arrangement and avoid recording payment-card credentials. Distinguish machine completion from payment-provider status. Include a relevant interruption only through a documented, safe test method agreed with our engineering team.
Review operator access and handover material
Ask our engineering team to demonstrate the routine loading, cleaning and service access included in the agreed scope. Confirm which activities belong to the operator and which require a technician.
Track exceptions before making an acceptance decision
Keep every failed, incomplete or changed test tied to its evidence and owner. Installation and commissioning checks at the destination site are recorded separately from the factory observations.
Site Preparation & Installation Responsibilities — Next record after these factory observations: destination access, utilities, site works and handover checks stay on the installation review, separate from this factory record.
Frequently asked questions
How do you distinguish not tested from not applicable?
Not tested means a product, condition or case that belongs in the agreed scope and was not demonstrated. Mark it unresolved, keep the row, and do not extend a result from a different sample. The acceptance record for a packaged-card release keeps the products not tested with the observations. Not applicable means an exclusion written in the approved test procedure before the demonstration, so the check sits outside the agreed scope for this configuration. The quality record lists the checks actually performed and links each inspection to that configuration revision.
Which records are redone after the configuration changes?
Keep the model, serial number and the hardware, software and option versions on the row for the configuration that was tested. When those versions or the sample change, agree the procedure, participants and acceptance criteria again for the changed configuration, and link the inspection to the new configuration revision. Sample identity, customer-cycle observations, exception cases and retest evidence are recorded again for that configuration. The failed and untested rows on the earlier configuration stay in place. A manual, drawing or training item is recorded when that version has actually been supplied.
Does a factory observation mean the destination installation is complete?
A factory observation records the tested unit during the agreed factory demonstration. Installation and commissioning checks at the destination site are a separate record. That installation review uses the machine's installation drawing and the agreed site scope, including delivery access, utilities, site works and handover checks. Remaining site checks remain listed on the factory exception row until the destination installation file is complete. The handover file lists the checks performed and the installation responsibilities still open before the next delivery stage.