Quick answer
If there is an alarm or suspected release, follow the site emergency plan before contacting technical support. For subsequent equipment review, send the detector and controller identities, exact original indication, timestamps, affected points, recent changes and available maintenance records. Preserve existing evidence through approved channels. Do not assume that a reset, zero adjustment and factory restoration are the same action or appropriate remedies.
Identify the equipment without opening it
Reference the existing asset record instead of rebuilding it during an incident. Provide the detector's asset identifier and enough model/controller information to locate the correct file; flag any replacement or identity mismatch. The maintenance-record checklist covers the full lifecycle record. This brief concerns the condition before a proposed change.
Do not open equipment or enter a hazardous area to complete a support form. The UTAI service policy page provides the established service context; it does not make this checklist an emergency-response channel or authorize repair work.
Preserve the exact indication and sequence
Send the original wording, displayed value and unit together with the timestamp and point label. Include a safe, permitted photograph or existing log where available. State which device produced each item: detector, controller or supervisory display. Avoid paraphrasing every unusual indication as 'sensor fault'.
Manufacturer manuals can assign distinct meanings to warning, fault and over-range states. The Honeywell Sensepoint XCD manual, for example, separates these in its system-status and diagnostic tables. Those codes are not a decoder for a UTAI product.
Explain what changed and what has already been done
Provide a short timeline from the last known normal observation to the current condition. Include recent authorized equipment replacement, maintenance or power events if known. List actions already taken and their observed outcomes, without repeating them to obtain a more convenient result.
If someone recommends 'reset', ask them to identify the exact proposed action and applicable document before work is authorized. Similar everyday words can hide different intended actions. Do not convert an informal request into permission for zero adjustment, configuration changes or restoration of factory settings.
Distinguish a live snapshot from retained history
Ask which evidence is only a current display and which is already retained in an approved log. A later observation cannot reconstruct an unrecorded earlier screen. Do not assume the equipment automatically stores every indication or that a proposed operation preserves or erases particular records; support must confirm that behavior for the actual version.
Use the established private support channel. The following pre-change questions supplement the asset record without requesting passwords, access tokens, raw firmware or unrelated customer information.
- What original indication has been preserved, and what is only remembered?
- Which timestamp belongs to the event rather than the later support request?
- What actions have already changed the observed state?
- What exact action is proposed, and which document governs it?
- What evidence must be retained before authorization, and who owns that decision?
A support response should define the next decision
Ask support to distinguish a confirmed finding from a possible explanation and to identify any missing information. The site should retain responsibility for work authorization and the monitoring arrangements during assessment. A recommendation is not evidence that a repair has been performed or accepted.
After authorized work, request a record of what changed, the relevant verification results and unresolved items. The UTAI maintenance guide covers ongoing records. This page deliberately stops before any reset instructions; collecting evidence must never delay the site's emergency response.