Getting startedWorked example: primary air fan
Worked example

Investigate a primary air fan

In a cement burner simulation, a dust build-up scenario changed the vibration of the primary-air fan. The planner’s question was whether the evidence justified a field inspection. The following observations come from the Ultron demo run of 8 November 2026.

Customer guide · Updated 14 November 2026

#In the demo

In the demoWhat the reviewer could establish
Select the scenarioIn Simulation, select the PA-fan impeller dust build-up case. Open Home, Burner and Diagnosis. The fault card identified mechanical vibration at the impeller and listed dust build-up as the likely cause.
Inspect the measurementsDiagnostic Analysis showed drive-end vibration at 3.35 mm/s RMS against a normal value of 2.15 mm/s RMS. The trend was rising by about 0.4 mm/s per week. The configured high alert was 4.5 mm/s RMS.
Interpret the forecastThe reading was 1.15 mm/s below the high alert. At the displayed rate, that gap corresponds to roughly 2.9 weeks. This projection depends on continuation of the trend and does not establish when the fan will fail.
Request verificationSelecting “Request vibration analysis from the PM cell” produced REQ-013. In the PM cell the request retained the asset, suspected cause, priority and projected alarm.
Track the handoffStarting REQ-013 moved it to In progress. The report form exposed measurement positions, speed, load, spectrum, finding and recommendation. The recorded test ended before a field report was submitted.

#What a plant would add

The technician would collect measurements under the site’s approved procedures and record speed, load and sensor position. The reliability engineer would compare the observations with the suspected cause and document a confirmed, rejected or inconclusive finding. If the plant requires an ERP work order, an authorised user would verify the ERP record and link its identifier to the request.