Fleet utilization, two ways
Time utilization and dollar utilization side by side, by class, model, branch and age band, with a daily trend so seasonal peaks and the shoulder months either side of them are not averaged away.
Fleet analytics for rental yards
Power BI for Equipment Rental Companies: Utilization, ROI and Idle Days Per Unit
We model your rental software, telematics and ledger into one live view — time and dollar utilization by class, rental revenue and rate yield, return on original equipment cost per unit, dwell between contracts, and branch against branch.
Representative dashboard — sample data
The reporting gap in a rental yard
Your system knows every contract. It will not tell you which units pay for themselves
A rental business is a capital business wearing an operations costume. You buy an asset once, then spend years trying to make it earn back more than it cost to own, maintain and move. Almost every rental platform can print an open-contracts list, an availability screen and an aged receivables report. Very few can answer the question the owner actually asks: across the last twelve months, which serial numbers returned more than they cost, which classes are quietly over-fleeted, and which branch is carrying the ones that sit.
That answer needs three datasets that usually never meet — contracts and assets in the rental software, work orders and parts cost in maintenance, depreciation and overhead in the general ledger. We build the model that joins them and the report that reads it, so utilization, revenue, return and cost land on one page at the grain that matters: the individual unit, rolled up to class, branch and region.
The two numbers a rental yard lives on
Busy is not the same as profitable
Time utilization = rented days ÷ available days · Dollar utilization = rental revenue ÷ original equipment cost — a unit can score well on the first and badly on the second, and only the second pays for the next one.
Try us risk-free for 4 hours
Buy a block of prepaid Flex hours and, if you're unhappy within the first 4 hours, we refund you in full — no questions asked. Hours are deducted only for work you've reviewed and approved, there's no project minimum, and your banked hours never expire.
Views a rental operator uses weekly
Six screens that decide what you buy, move and sell
Each one is tied to a decision — re-fleet, transfer, re-rate, repair or dispose — not a wall of gauges.
ROI per unit against OEC
Lifetime and trailing-twelve-month rental revenue per serial number set against original equipment cost, accumulated maintenance spend and net book value — the payback view that tells you when to hold and when to sell.
Idle and dwell days
How long each unit sits between contracts, split into ready-to-rent idle, awaiting-inspection, down for repair and stranded at the wrong yard — so dead capital is a worklist rather than a feeling.
Branch and depot scorecard
Every location on one comparable base: revenue per available unit, utilization, rate achievement, transfers, re-rent spend and delivery cost — each manager seeing their own yard, head office seeing all of them.
Maintenance against rental income
Parts, labor and outside-vendor cost per unit as a share of the revenue that unit earned, ranked worst first, with repeat-failure models flagged before the next purchase order goes to the same manufacturer.
Rate yield and revenue mix
Achieved rate against book rate by class, customer and term, plus the split between rental, re-rent, delivery, damage waiver, consumables and used-equipment sales — so discounting surfaces before month-end does.
What should a rental fleet dashboard measure?
A rental fleet report earns trust when every measure has one agreed definition and a documented source. We fix those definitions with your team before any visual is drawn — what counts as an available day, whether a unit on a transfer truck is idle, whether delivery income belongs in rate — then implement them as governed DAX measures (opens in new tab) so the same number survives being sliced by branch, class and month.
- Time utilization — rented days over available days, by unit, class, branch and age band, with the availability denominator agreed rather than assumed.
- Dollar utilization — rental revenue over original equipment cost, trailing twelve months and annualized, so capital productivity is comparable across classes of very different value.
- Return per unit — lifetime revenue against OEC, accumulated maintenance and current net book value, with a payback position for every serial number.
- Idle and dwell days — the gap between off-rent and next on-rent, categorized by reason, so you can separate demand problems from yard problems.
- Rate achievement — realized daily, weekly and monthly rate against book rate by customer, class and term, including the effect of long-term contracts on blended yield.
- Maintenance cost ratio — parts, internal labor and outside repair per unit as a percentage of that unit's rental revenue, trended by model and by fleet age.
Why one utilization number is never enough
Most disputes inside a rental business come from two people quoting different utilization figures and both being right. The measures answer different questions, and a fleet decision needs all of them on one page.
| Measure | How it is calculated | Question it answers | Where it misleads on its own |
|---|---|---|---|
| Time utilization | Rented days divided by available days, at unit level | How often is this asset out of the yard? | Treats a deeply discounted long-term contract as a success |
| Dollar utilization | Rental revenue for a period divided by original equipment cost | What is this capital returning against what we paid? | Flatters old, heavily depreciated units bought at a lower cost |
| Rate achievement | Realized rate divided by book or list rate, by contract line | Are we holding price, or buying volume with discount? | Says nothing about whether the unit rented at all |
| Return per unit | Lifetime rental revenue less maintenance, against OEC and net book value | Has this serial number paid for itself yet? | Slow to react — a good recent quarter barely moves it |
The modeling problem nobody warns you about
A rental contract line is a date range, not a transaction on a day. If you drop those rows straight into a report and count them, a machine on a six-month contract appears once and vanishes from every month except the one it started in — so utilization collapses and nobody trusts the report again. We solve it the way it has to be solved: expand contract lines to a daily asset-level fact table, or implement an events-in-progress measure that counts units on rent as of each date. Both sit on a proper star schema (opens in new tab) with a real date table behind the time intelligence functions (opens in new tab), which is what makes trailing-twelve-month dollar utilization and year-over-year comparison a click rather than a rebuild.
The second trap is the asset key. Units get re-numbered, transferred, converted to sales inventory and occasionally re-acquired, and if that key is not stabilized, history detaches from the machine and lifetime return per unit becomes fiction. We reconcile it once, during the build, and document how it is maintained.
Which rental systems do you connect, and how?
We connect the platforms rental businesses actually run rather than insisting on one vendor. What varies is the route in — a reporting database, a documented API, or a scheduled export — and that choice drives refresh cadence more than anything else in the build. Where the platform is Point of Rental, which route is even available depends on whether you run Expert, Elite, Essentials or Syrinx; our Point of Rental Power BI dashboard page compares the three doors out of the system in detail.
| System | What we take from it | Typical route |
|---|---|---|
| Rental management platform (Point of Rental, Wynne RentalMan, Texada, Alert Rental, MCS, InTempo) |
Contracts and contract lines, asset register, rate books, reservations, transfers, off-rent and on-rent events | Reporting database or replica where the vendor allows it; API or scheduled export where it does not |
| Maintenance and service records | Work orders, parts issued, internal labor hours, outside vendor invoices, downtime reason | Same platform where service is integrated, otherwise the standalone maintenance system or ledger |
| Telematics | Engine and run hours, location, movement, fault codes for powered classes | Provider API, or a mixed-fleet feed via the AEMP / ISO 15143-3 telematics standard |
| Accounting ledger (QuickBooks, Sage, Business Central, NetSuite) |
Original equipment cost, depreciation and net book value, branch overhead, disposal proceeds | Native connector or ledger export, joined to the asset key |
| On-premises databases | Any of the above hosted in your own server room | The on-premises data gateway (opens in new tab) with scheduled refresh (opens in new tab) |
Where a vendor only offers exports we say so plainly and design around the cadence that gives — usually an overnight refresh, which is fine for a fleet report. We do not promise real-time where the source cannot supply it.
Multi-branch networks and who sees what
Once a business runs more than two yards, comparison becomes the point of the report and access becomes the constraint. Branch managers should see their own utilization and their own dead units without browsing another region's margin. We implement that with row-level security (opens in new tab) mapped to your existing branch and region hierarchy, so one report serves the whole network and opening a new depot is a row in a table rather than a redevelopment.
The comparison itself needs care. Raw revenue per branch rewards the largest yard, so we normalize to revenue per available unit and to dollar utilization on the fleet each branch actually holds. Re-rent from a competitor gets its own line, because a branch hitting its target on sub-rented machines is telling you about fleet mix, not about selling.
How is this different from the reports already in your rental software?
Fairly: your platform's built-in reports are good at the operational present — what is out, what is due back, who owes money. If that is the whole question, you do not need us. What they rarely do is cross the boundary between systems or reach back far enough to judge a capital decision. Lifetime return per serial number needs maintenance cost from one system, OEC and depreciation from another, and contract history from a third, joined on an asset key all three disagree about. That join, done once and kept clean, is the deliverable — and because it lives in your own Microsoft tenant as a model you own, the next question does not need another vendor request.
What does it cost, and how fast?
You buy prepaid Flex hours that never expire. Starter is 20 hours ($2,500), Growth 40 hours ($4,600) and Power 80 hours ($8,000), with senior hourly work from $100. A first build covering utilization both ways, revenue and rate, idle days and return per unit typically fits inside one block, and most tasks ship within 3–5 business days of your approving the scope estimate.
There is no project minimum. Every request is scoped and priced in hours before work starts, hours deduct only for work you approve, and unused hours stay banked for the next season. See how prepaid Flex hours work, or what a typical custom Power BI dashboard development engagement includes.
Who is this for?
Owners, CFOs and fleet directors at independent rental businesses and regional chains — general tool and equipment rental, aerial and earthmoving fleets, specialty and trench safety, pump and power, portable sanitation, event and party rental. The common thread is a fleet large enough that per-unit economics stop being obvious and a head count too small to justify a full-time analyst. What changes between renting to contractors, to industry or to consumers is the rate structure and the season, not the model — so the same build serves a single yard and a twelve-branch network with only the security roles and the class hierarchy differing.
Dashboards we build for rental fleets
- Time & dollar utilization by class
- Return per unit against OEC
- Idle & dwell day worklists
- Rate achievement vs book rate
- Maintenance cost per revenue dollar
- Branch scorecards with row-level security
3–5
business days, typical
Prepaid
hours, never expire
You
own everything
A first fleet build usually fits inside one Flex block, and hours deduct only for work you approve. See Flex pricing →
How it works
From asset register to a fleet view you act on
- 1
Scope & connect
On a free demo we walk your class hierarchy, branch structure and systems, and agree how an available day, an idle day and a rate are defined. You send the request, we reply with the hours it needs, and once you approve we connect the rental platform, maintenance records and ledger into one reconciled model.
- 2
Build & validate
We stabilize the asset key, expand contracts to a daily grain, and write the DAX for utilization, rate achievement, dwell and return per unit. You check the output against your own fleet reports, serial by serial on a sample, until the numbers are ones you would quote to a lender.
- 3
Launch & hand over
We publish to your workspace, set scheduled refresh and row-level security by branch and region, and train the people who will use it. The report, the model and the credentials are yours at handover, with optional ongoing support from the same block of hours.
Representative perspective
We knew the fleet was busy. What we could not see was that a whole class was busy at a rate that never covered what we paid for it. Putting dollar utilization next to time utilization changed what we bought the following year.Owner, independent equipment rental business
Representative perspective
Idle days used to be an argument between branches. Now every unit that has sat more than a fortnight is on one list with a reason next to it, and the transfers happen without anyone needing a meeting.Fleet director, regional rental chain
Find out which units in your yard actually pay
Book a free demo. We'll map your fleet, branches and systems, then scope the build and tell you the hours it needs before any work begins — and your prepaid hours never expire.
Where this sits next to our other work
Rental sits between several worlds, and the neighbouring pages answer genuinely different questions. If you are a contractor who owns equipment rather than rents it out, the money question is project-level, and Power BI for construction contractors covers that ground instead. If you both rent out fleet and run crews, the two pages are complementary: this one values the asset, that one values the project. Rental businesses that also distribute parts, attachments and consumables, or that move fleet between depots at scale, will find the inventory and logistics half of the picture on Power BI for manufacturing and logistics.
Two adjacent pages cover service delivery rather than asset economics. If your revenue comes from technicians attending jobs rather than machines going out the gate, start at Power BI for HVAC and field service companies, which owns dispatch, work orders and technician productivity. And if your service side runs on Jobber specifically, the Jobber Power BI dashboard page covers getting scheduling and invoicing data out of that platform. Neither of those overlaps with the utilization and return-on-fleet work described here. Businesses whose fleet is tractors and trailers earning by the mile rather than machines earning by the day should start at Power BI for trucking companies, which covers revenue and cost per mile, deadhead and profit per truck.
For the mechanics of how a build is delivered — the model, the DAX, the report layout and the handover — see Power BI dashboard development, and how prepaid Flex hours work for pricing. Every task is scoped before work begins from your block of senior-led hours: no project minimums, no surprise invoices, and hours deducted only for work you approve.
Why it's low-risk
Prepaid hours, you own everything
Every task is scoped and approved before work starts, with hours deducted only for approved work — and at handover the report, model and credentials are yours. Hours never expire, and there's a full refund within your first 4 hours.
FAQ
Questions from rental owners and fleet directors
Time utilization is rented days divided by available days, so it tells you how often a unit is out. Dollar utilization is rental revenue over a period divided by the original equipment cost of that fleet, so it tells you what the capital earned. A unit can be busy and still return badly, which is why we always model both.
Yes, and it is the part most spreadsheets get wrong. A contract line is a date range, not a day, so we expand it to a daily asset-level grain or use an events-in-progress measure pattern. That lets utilization be sliced by any calendar period, branch or class without double counting units on long-term contracts.
We work with the systems rental businesses actually run, including Point of Rental, Wynne RentalMan, Texada, Alert Rental, MCS and InTempo, plus telematics feeds and the accounting ledger. The route depends on what your vendor exposes: a reporting database or replica, a documented API, or scheduled exports where neither is available.
Yes. We apply row-level security so a branch or region manager opens the same report and sees only the assets, contracts and revenue belonging to their locations, while head office sees the whole network. Roles are mapped to your existing branch hierarchy, so adding a depot does not mean rebuilding the report.
You buy prepaid Flex hours that never expire: Starter 20 hours at $2,500, Growth 40 hours at $4,600, Power 80 hours at $8,000, with senior hourly work from $100. A first build covering utilization, revenue and ROI per unit usually fits inside one block, and most tasks ship in 3–5 business days after you approve the scope.
Book a free demo
Get senior Power BI help, on demand
Tell us the task. We scope it, you approve, and a senior consultant delivers — typically in 3–5 business days. Prepaid hours that never expire.
- Prepaid hours from $100/hour — and they never expire
- Senior-led delivery — 20+ years on the Microsoft platform
- Typical 3–5 business day turnaround
- Full refund if you’re unhappy in your first 4 hours
The fastest way to reach us is the form — tell us the task and we'll reply within one business day.