Illustrative planning scene: Preventive-Maintenance Information Facility Teams Should Record
Illustrative application planning scene; not a customer installation.

A consistent maintenance record helps the service team distinguish a recurring fault from a changed load or installation condition. Record observations and authorised service findings without opening or adjusting live equipment.

Maintain one asset record

Keep make, model, asset reference, rated kVA/kW, installation date, location and service contacts together. Add the approved battery configuration and replacement history. Store current manuals and the agreed service scope where authorised teams can find them.

Record changes and events

Log alarm wording, date and time, operating symptoms, recent load additions and changes to ventilation or access. Record runtime observations with the conditions under which they occurred; an informal observation is not a controlled capacity test.

Keep service findings actionable

Record Information to retain
Visit Date, authorised personnel and agreed work
Findings Alarm history, observations and reviewed configuration
Action Recommendation, owner and next review date
Change Parts/settings changed and supporting service record

Testing, isolation and measurements should follow the authorised procedure. The log is a reporting tool, not a DIY repair checklist.

Prepare for the next service discussion

Send the asset record, alarm history, previous reports, known load changes and site access restrictions. Ask the provider to confirm supported work, visit arrangements and exclusions for the actual model.

Should a facility team open the UPS to complete the log?

No. Use accessible labels, existing documentation and authorised service records.

Is declining runtime always a battery fault?

It can reflect load, battery condition or other configuration and operating changes. Request an assessment rather than assuming a cause.

Request preventive-maintenance scope review.