The unique identifier for a single vehicle in the fleet system. Every row in a FleetCast export is one MVA — one physical car. FleetCast uses it as the primary key, so a unit appearing twice in a report always means a data problem rather than two cars.

The manufacturer's 17-character Vehicle Identification Number. Used for resale lookups and to match a unit across systems that don't share the MVA number. Rows without both an MVA and a VIN are excluded from FleetCast entirely — they're almost always header fragments or placeholder records.

The four-letter ACRISS-style code describing a vehicle category — ICAR (intermediate), FCAR (full-size), ECAR (economy), CCAR (compact), SFAR (standard SUV), and so on. FleetCast groups almost everything by class: fleet mix, utilization, defleet schedules and acquisition recommendations are all class-level, because that's the unit of decision for both pricing and purchasing.

The operational state of a unit at the moment the file was cut — on rent, ready to rent, awaiting cleaning, in maintenance, at another location, and so on. Status vocabulary varies by operator: FleetCast matches against a known list rather than assuming a fixed set, because the same concept appears as "LOT- READY TO RENT" for one company and something quite different for another.

The manufacturer's model year for the unit. FleetCast uses it as a fallback age signal when Days on Fleet isn't available in your export. It's coarser than a real in-service date — a used purchase looks younger than it actually is on your fleet — so any projection driven by model year alone is flagged as such.

Recorded mileage for the unit. The most reliably populated field across every export format FleetCast reads, which is why mileage-based replacement rules work for every customer while time-based rules depend on Days on Fleet being present.

How long a unit has been in your fleet. Where present, FleetCast uses it both to age units against a replacement policy and to measure your real mileage accrual rate rather than assuming one.

Cumulative days the unit has been on rent. Combined with Days on Fleet it gives per-unit lifetime utilization, which is a fairer measure of a vehicle's contribution than a snapshot of whether it happens to be rented today.

The share of the fleet earning revenue at a given moment or over a period. The headline efficiency measure for a volume operator — though not the whole story for a specialty fleet, where a high-rate unit can be profitable at far lower utilization than a economy unit needs.

Units that are rentable and not currently on rent. This is the true idle count — cars that could be earning and aren't. Distinct from off-road units, which can't earn regardless.

Units unavailable for rent — in maintenance, damaged, awaiting parts or otherwise out of service. Off-road units still cost you every day they sit, but they're an operational problem rather than an allocation one, so FleetCast keeps them separate from idle units.

Units scheduled to return within the next day or two. Together with Available Now these give the near-term supply picture — what you can actually promise a customer this week, rather than what the fleet size implies.

A 14-day view of units scheduled back each day, with a running cumulative total. The cumulative line is a ceiling, not a forecast — it shows the most you could have free if nothing new went out, which is the right way to read it when judging whether to accept a large booking.

What non-earning units cost you per day. Applies your fixed holding cost plus daily-equivalent depreciation to every unit that's available but not on rent. Particularly relevant for specialty fleets, where holding cost per unit is high and acceptable utilization is low — the percentage alone doesn't convey the money involved.

Units scheduled back before the current snapshot that haven't been returned. Flagged prominently because the cost of chasing a late return rises sharply with time — early it's a phone call, late it's a recovery.

Your rules for when a unit leaves the fleet — a mileage limit, an age limit, or both. A unit is due when it reaches either threshold, whichever comes first. These are your numbers; no vehicle feed carries them, so they're set once per company in FleetCast and saved.

Removing a unit from the rental fleet at the end of its hold — sold at auction, returned under a buyback, or moved to a retail channel. Defleeting is the natural counterpart to acquisition: the fleet is a curve, and these are the two ends of it.

A month-by-month projection of which units reach your replacement policy, grouped by location, car class or make and model. Built entirely from units you already own and your own policy — no forecast is involved, which makes it the most defensible number in fleet planning.

How fast your units add miles, expressed per month. Where Days on Fleet is available FleetCast measures this from your own fleet using a median rather than an average, so a handful of outliers can't distort it. Where it isn't, the rate is an assumption you set — and FleetCast states which is in play.

Units approaching or past their replacement threshold, ordered by how close they are. The operational to-do list that sits behind the defleet schedule: the schedule says when, the pipeline says which.

The current depreciated value of a unit on your books. Compared against market resale value, it determines whether defleeting a unit realises a gain or a loss — and therefore whether it's worth accelerating or delaying a disposal.

The capitalised cost of the unit — what it entered the fleet at. With NBV it gives realised depreciation to date, and with hold time it gives depreciation per month, which is the figure that actually drives holding cost.

The number of units a location should hold — demand divided by your target utilization, floored at any facility minimum. Every planning view in FleetCast derives from the same calculation, so the optimization, allocation and acquisition views can never quietly disagree with each other.

The utilization you're aiming to run at — a judgement about the trade-off between idle cost and turning away business, not a number any system can derive for you. Volume operators typically sit in the 75–90% range; specialty and luxury fleets often run far lower by design, because rate per day is several times higher and refusing a booking costs more than idle days.

A per-location floor on fleet size, regardless of what demand suggests. Covers the practical reality that a staffed location can't run on three cars even if the maths says it could — a presence requirement, a contract obligation, or simply a viable lot.

How far a location's fleet sits from its target. A surplus is capital earning less than it could elsewhere; a deficit is demand you can't serve. Both are shown as a signed variance so the direction is immediate.

Your locations plotted geographically, sized by fleet on hand and coloured by surplus or deficit. Designed to answer "where is fleet out of position" at a glance, and it fits both a national footprint and a group of sites inside one metro.

Units that must arrive, by location and month, to hold target fleet as the defleet schedule plays out. Available fleet falls each month as units age out; where it drops below target, the shortfall is the buy. Shown in the month the units must arrive, with an order-by date derived from your lead time.

Weeks between placing an order and units arriving on your lot. Turns "we're short in March" into "order by December," which is the only version of that insight you can act on.

Moving existing units between locations to correct imbalance, rather than buying or selling. FleetCast matches each deficit to the nearest surplus with units to spare, so transfer distance stays down, and prices the move against your own driveaway or transporter costs.

The monthly loss in value per unit. Usually the single largest cost of holding a vehicle, and one no rental feed provides — it comes from your own fleet accounting and is set once per company in FleetCast.

Daily cost charged on every unit whether it rents or not — storage, insurance, registration, floorplan interest. This is what makes an idle unit expensive rather than merely unproductive.

Cost incurred only on days a unit is actually on rent — cleaning, fuel, per-turn maintenance. Deliberately separated from fixed holding cost so idle-unit economics stay honest: a car that isn't renting isn't incurring these.

What it costs to put a new unit on the lot. Multiplied by the defleet schedule it gives the capital requirement of simply maintaining fleet size — often the first number that makes a defleet schedule feel urgent.

How your rate and your competitors' rates for a given arrival date move over time as that date is repeatedly shopped. Shows not just where you sit today but how the market got there — whether you led a move or followed it.

The pickup date being priced. Rate Evolution tracks one arrival date at a time, because a rate only means something in relation to the day it's for — comparing today's price for next Tuesday against today's price for Christmas tells you nothing.

The number of days being priced. Suppliers express this through their own rate codes — D3, W7, M30 and many local variants — where the letter indicates the rate type and the number the length. FleetCast resolves these to a plain day count so a three-day shop is comparable across every location and supplier.

Whether a rate is priced on a daily, weekly or monthly basis. Independent of length: a five-day rental can be priced on a weekly rate, which is exactly why length and rate type have to be read as two facts rather than one.

The operators you measure yourself against at a location. Every company appearing in a shop at that location is collected, so the set can be narrowed or widened after the fact without re-shopping anything.

Where your rate sits against the market — above, below or within it. More actionable than the raw number: being 20% under market on a date that's already selling out is a different problem from being 20% under on a soft date.

The fleet file from your rental system — one row per vehicle with status, class, mileage and location. Export layouts differ substantially between operators, so FleetCast identifies fields by content rather than assuming fixed column positions.

An hourly cut of the entire fleet showing what's on rent, available and off-road right now. Each snapshot replaces the last rather than accumulating — it's a photograph of the present, not a history.

The identifier for a rental location, often an airport code but frequently an operator's own code for a city or neighbourhood site. FleetCast matches units to locations using your own configured codes, which keeps one company's vehicles from appearing in another's reports.

The number of units included in whatever you're currently looking at, after location and any other filters. Shown alongside every fleet metric so a number is never read as company-wide when it's actually one location.