SYNC CLOCKS / Practical resources
Clock System Acceptance Test Checklist
Plan synchronized clock acceptance with a blank checklist for references, display checks, agreed tolerances, results, exceptions and handover records.
In this guide
What should be agreed before testing begins?
Agree the equipment, locations, operating conditions and acceptance limits before collecting results. A useful acceptance record shows what was tested and against which requirement, rather than treating a group of clocks that looks correct at one moment as proof of the complete installation.
List the installed models, firmware where available, time source, distribution method and responsible parties. Separate factory checks from site checks. Record whether every location must be tested or an agreed sampling plan applies. The quantity and duration of observations should follow the project requirement, not an arbitrary universal rule.
The clock system specification template helps define requirements before quotation. This checklist addresses the later task of recording installation verification and handover.
Are you checking a display or an electronic timing output?
Identify the measurement point explicitly because a visible wall-clock reading, a server output and an electronic event timestamp are not interchangeable results. The test method must resolve the agreed error at the point that matters to the customer.
For a display check, record the displayed information, local time zone, observation method and reference. For an electronic output, identify the interface, measuring equipment and relevant configuration. Do not infer microsecond performance from a photograph of a display, or treat server performance as measured performance at the end of a network.
Which reference and measurement method fit the tolerance?
Select a reference and method whose limitations are understood and suitable for the agreed acceptance criterion. Record resolution, uncertainty where established, reference identity and observation conditions so another reviewer can understand what the result does and does not demonstrate.
A browser time display may help with an ordinary time-of-day observation, but it should not be used to claim traceability or precision calibration. NIST states that time.gov is a time-of-day service rather than a basis for establishing traceability. Formal traceability requires documented links to a reference and measurement uncertainty, not merely a familiar source name.
If the proposed method cannot distinguish passing from failing at the required limit, resolve that issue before testing. Do not add extra decimal places to a visual observation to make it appear more precise.
What should each location record?
Use one consistent record for each tested location or agreed group, keeping the requirement beside the observed result. Leave an unavailable result blank or mark it as not tested; do not turn missing evidence into a pass.
| Record field | Information to enter |
|---|---|
| Location and equipment | Building, floor, position, model and identifier |
| Configuration | Time source, distribution method, firmware if known |
| Requirement | Agreed tolerance and measurement point |
| Method | Reference, instrument or observation method, resolution and uncertainty where established |
| Conditions | Date, time zone, operating state and relevant network conditions |
| Result | Observed value, units and evidence reference |
| Disposition | Pass, fail or not tested against the agreed criterion |
| Follow-up | Issue, responsible person, retest result and date |
Keep photographs and logs associated with the relevant record. A photograph can establish installed location or visible state, but its evidential value depends on what it actually shows.
How should interruption and recovery tests be handled?
Perform interruption tests only under an approved method and maintenance window, with the responsible staff controlling the action. Reference loss, network loss, server power loss and clock power loss are different conditions and should have separate requirements and records if they form part of acceptance.
This checklist does not instruct operators to disconnect production equipment. Record the approved test condition, start and end times, expected behavior, actual observations and recovery result. Include the point at which the installation is returned to normal service. A device continuing to display time is not, by itself, evidence that its accuracy remained within the required limit.
What belongs in the handover pack?
The handover pack should connect the agreed requirements to the installed configuration, test results and unresolved issues. It should also identify who will maintain the system and where the applicable operating documents can be found.
- Final equipment and location list with configuration references.
- Reference and distribution diagram matching the installed arrangement.
- Completed acceptance records, evidence files and retest history.
- Open exceptions with responsibilities and agreed next steps.
- Applicable manuals, maintenance contacts and change-control arrangements.
Keep credentials in approved secure storage, not in a public checklist or general enquiry attachment. Use the download center for available product documents and contact HC Electronics to clarify documentation for the proposed configuration. Record actual acceptance decisions only after the responsible parties review the completed evidence.
Discuss your clock system requirements
Send your clock locations, quantities, available infrastructure and required timing performance to HC Electronics.