Sample report

What you would receive after a Machine Health Snapshot.

One page per machine. Written in the vibration units and language your maintenance team already uses. The example below is for a fictional pump and every value is simulated.

Machine Health Report

Machine Health Snapshot, 14-day observation

Sample document. Simulated values.

Report RB-SAMPLE-0001
Prepared for: Example Manufacturing Pte Ltd (fictional)
Site: Illustrative plant, Singapore
Prepared by: Robometic

1. Equipment summary and measurement period

MachineCooling-water pump CWP-2, centrifugal, direct coupled to a 15 kW motor
DutyContinuous. Two operating states observed: normal flow (day shift) and reduced flow (night)
Sensing pointsTwo vibration points, motor drive end and pump drive end, and one sound point near the pump casing. Positions photographed and recorded; no sensor moved during the period
Measurement period14 days. Days 1 to 7 learning the machine's normal pattern; days 8 to 14 monitoring against it

2. Normal versus unusual behaviour

Learned normalPump drive end 1.2 to 1.6 mm/s RMS during normal flow, 0.9 to 1.2 mm/s RMS during reduced flow. Motor drive end steady at 0.8 to 1.1 mm/s RMS in both states. Sound signature stable across both states. Levels are in the unit used on the plant contractor's severity charts, so the team can place them against the limits it already applies
Unusual behaviourFrom day 9 a rising trend at the pump drive end, reaching 2.3 mm/s RMS on day 12 during normal flow. Amber notice on day 11 when the level left the learned pattern; the plant's own alarm level was not reached at any point. From day 12 a change in the higher-frequency sound content near the pump casing. Motor drive end unchanged

3. Observations and operating conditions

  • Run log shows no change in product, flow set point or duty cycle during the period. The night-time reduced-flow state recurred as usual.
  • One planned stop on day 9 (filter change, 40 minutes). Levels on restart matched the levels before the stop.
  • Pump bay conditions, from the plant's own records, stayed within their usual range. No coincident changes in nearby equipment were recorded.
  • The next scheduled route reading for this pump was 19 days after the amber notice.
  • Three amber notices in total, all on the pump drive end. All three were labelled by the maintenance team on the same day.

4. Maintenance review

Inspection, day 12Technician reported increased noise at the pump drive-end bearing and slightly raised housing temperature by hand. Lubrication record shows one missed greasing interval
Action takenBearing greased on day 12. Bearing inspection scheduled for the next planned stop. Sensing points left in place
After the actionLevel at the pump drive end fell from 2.3 to 1.9 mm/s RMS within a day, then rose at a slower rate to 2.1 by day 14
Team labelsNotice 1: worth checking. Notice 2: equipment concern (confirmed at inspection). Notice 3: known issue, action already planned

5. Open questions

  • Whether the remaining rise after greasing is the bearing itself or coupling alignment. The sound change points to the bearing; an alignment check and a spectrum at the next reading would settle it.
  • Whether the reduced-flow night state masks part of the trend. The daytime readings carry the finding; the night readings are consistent with it.

6. Suggested next steps

  • Carry out the planned bearing inspection at the next planned stop, within two weeks, with an alignment check at the same time.
  • Keep the two vibration sensing points on this pump for a further 30 days to confirm the outcome of the repair.
  • Decide whether this pump justifies ongoing Machine Health Watch. On this evidence it is a candidate; the other pumps in the bay were not observed and no conclusion is drawn about them.
Sample document with simulated values, prepared to show the format of a Robometic Machine Health Report. Not a measurement of any real machine. Vibration figures are illustrative and are not quoted against any published severity limit. The maintenance team's labels, not the system's notices, decide what counts as a useful alert.

Why one page

A report you can imagine receiving for your own equipment.

At this stage a clear page per machine is more useful than a dashboard with dozens of charts. It records what changed, what the team checked, what was decided and what remains open. The evidence and the decision stay together.