AI in CloudERM, in plain English.

An inspection record is only as good as its photos. Nobody at the office has time to look at every photo of every inspection, so a blurry hour meter or a "rear" photo of the front only turns up weeks later — in the middle of a damage dispute, when it's too late to retake it.

Inspection Analysis is an add-on that reviews each completed inspection within minutes of the crew finishing it (quick passes excepted). Every photo is checked against the question it answers and for quality. Multi-photo sets are checked for coverage. The asset number is looked for in the photos, and the hour-meter photo is read and compared with the reading the crew entered. On an off-rent inspection, the return photos are compared with the dispatch photos and any new damage is outlined on the before-and-after pair, with a confidence level. A comparison the model can't call is marked inconclusive, never clean.

Results land on the inspection's Analysis tab in the web app: an A–F grade and 0–100 score for how well the inspection was documented, with the machine's condition reported separately — so new damage never counts against the crew who found it. The Technician Report averages the findings per inspector, so you can see who documents well and who needs coaching. The model flags; it doesn't bill a customer, change a pass or fail, or edit a record. It is available for both CloudERM and InspectERM.

Setting a new asset's rental rate today is a judgment call: a yard manager looks at age, brand, comparable assets, recent utilization, and the going regional rate, then picks a number. That number may live unchanged for years.

CloudERM's planned rate recommendations will factor in current utilization, asset age, accumulated maintenance cost, and comparable rates across the fleet — then suggest a per-asset daily / weekly / 4-weekly rate. The same recommendation will run for sale price. The operator will see what drove the recommendation — utilization trend, age penalty, maintenance burden — and decide whether to accept it. No black-box pricing; no "the algorithm says so."

Knowing on Monday morning which categories are going to be tight by Friday is the difference between an okay week and a stressful one. Legacy systems leave this to the yard manager's memory — patterns held informally, lost when staff turn over.

Demand prediction is planned to use historical utilization, seasonality, and the current reservation pipeline to forecast which categories will run hot a week and a month out. The manager would see which add-ons to stock; the dispatch team where to rebalance. Each forecast will come with the inputs it used — "loader demand 18% above seasonal baseline because of three large reservations on the books" — so the team can pressure-test the prediction before acting.