Understand the interface decision

A stopped fan does not immediately produce the same thermal condition at every load or ambient temperature. Conversely, waiting for a high-temperature trip may not provide the intended protection if a critical location is not measured. The design needs documented coverage of the cooling failure.

Electrical reliability also depends on the installation environment and supporting functions. Review these matters within the accepted design and maintenance responsibilities. The checks below are planning and evidence requirements, rather than instructions to modify energized equipment.

Put these inputs in the review record

Use a project-specific worksheet to capture the following information. For each entry, name the document, revision and person responsible for resolving any uncertainty.

• Cooling-system design and the fan-failure detection method. Identify the exact configuration and the supporting document.
• Permitted output under reduced or unavailable forced cooling. Keep the design assumptions visible in the project record.
• Temperature limits and sensor coverage credited for protection. Name the responsible reviewer and resolve any missing information.
• Alarm, shutdown and restart conditions after cooling is restored. State how this entry will be verified during acceptance.

Define the acceptance boundary

Accept the response against the equipment manufacturer’s instructions and relevant validation. Do not disable a fan alarm merely because the converter remains operational at light load. The allowed degraded condition must be explicitly defined.

The test record should identify ambient conditions, loading and whether the fault was simulated or physically introduced. Keep diagnostic verification separate from evidence that the full thermal response remains within the approved envelope.