Example sketch
Maintenance scheduling for rental equipment
“We rent out construction machinery, and which unit is due for maintenance and when sits in a spreadsheet nobody has maintained for months.”
This sketch is an example. We wrote the sentence; the concept was generated by an AI and edited by us; our renderer draws it.
ConceptMaintenance
Maintenance Clock
Knows when every rental unit is next due for service, and schedules it between two rentals.
How we understood your problem
Maintenance depends on two figures the spreadsheet never combines: the calendar and operating hours. Because equipment is constantly out on site, a due service is only noticed when the unit comes back or breaks down, exactly when it should be earning rent.
Who it's for
- Workshop managerSees due maintenance and schedules it into the gaps between rentals.
- Rental deskSees at booking time whether a unit falls due for service during the rental period.
- MechanicTicks off maintenance steps and logs the meter reading.
Interface
Data model
| Entity | Field | Type |
|---|---|---|
| Equipment Type | name | Text |
| interval_months | Number | |
| interval_hours | Number | |
| Equipment | asset_number | Text |
| type | Reference | |
| operating_hours | Number | |
| blocked | Yes/No | |
| Rental Period | equipment | Reference |
| start_date | Date | |
| end_date | Date | |
| Service | equipment | Reference |
| due_on | Date | |
| completed_on | Date | |
| meter_reading | Number | |
| cost | Amount | |
| Service Step | service | Reference |
| text | Text | |
| done | Yes/No |
| From | Cardinality | To | Relation |
|---|---|---|---|
| Equipment Type | 1:n | Equipment | sets the interval for |
| Equipment | 1:n | Rental Period | is out during |
| Equipment | 1:n | Service | requires |
| Service | 1:n | Service Step | consists of |
Market value
What this problem would be worth on the market: how the product could be offered if it were sold. Not our price, and not an offer.
Billed per unit per unit
-
Up to 50 units
3 €
per month · per unit
- Most likely fit
Up to 250 units
2 €
per month · per unit
Value is created per unit monitored, not per person in the workshop.
Roadmap
-
Stage 1
Inventory
All units captured with intervals; the list of due maintenance is accurate.
-
Stage 2
Scheduling
Maintenance sits in the calendar between rentals; returns supply meter readings.
-
Stage 3
Blocking
Overdue units are blocked from rental; the history is complete.
Core features
- Intervals per equipment typeBy months, by operating hours, or by whichever comes first.
- Maintenance calendarDue services are visible between rental periods.
- Meter reading at returnOne field at return keeps the hour count accurate.
- Block when overdueAn overdue unit can no longer be booked out.
- Maintenance historyComplete per unit, as evidence for resale or in a damage claim.
Deliberately left out
- No rental management: bookings come from the existing system; only the periods matter here.
- No telematics at first: manual meter readings suffice as long as returns are logged.
- No spare parts inventory: that would be a separate product.
What the AI does
Estimates from past hours when a unit will reach its hour-based interval.
What the AI explicitly does not doThe estimate never shifts a deadline. Blocking follows fixed rules, not forecasts.
Integrations
- Rental software (periods)
- Calendar
- Label printing
Three questions we would ask you first
-
Does the rental software expose periods, via an interface or at least an export?
-
Which units even have an hour meter, and who reads it today?
-
May the system actually block a unit, or should it only warn at first?
A sketch, not an offer. Generated by an AI, rendered by us.