STINTLINE Feature Overview
Usage Tracking and Maintenance
Stintline’s core job is knowing the life of every component on every vehicle: how much of its life each part has used, when it is next due for inspection or rebuild, and the full history of what has been done to it. Usage accrues automatically from the events you record — every session the car runs is credited to every component fitted at the time — so the answer to “how much life is left in that upright?” is always current, without anyone keeping a spreadsheet.
How usage accrues
Each event you record — a test day, qualifying, a race — carries the running done: laps, time and distance (and, where enabled, heat cycles and launch starts). Stintline attributes that running to each component fitted to the vehicle during the event, using the component’s fitment history. Fit a part halfway through the season and it only accrues the events it actually ran; move it to another car and its usage record follows it, not the vehicle.
Life types
Different parts age in different ways, so each component type measures its life in the way that suits the part:
Runtime — life in hours of running. Typical for engines and gearboxes.
Distance — life in kilometres or miles, following your account’s unit setting. Typical for suspension and driveline parts.
Usage count — life in number of uses or events. Typical for parts stressed per event rather than per kilometre.
Heat cycles — life in heat cycles, for parts like tyres and certain fasteners, on accounts with heat-cycle tracking enabled.
Each component type carries a life figure in its chosen units — 25 hours, 10,000 km, 20 uses. A type can also be left without a life figure: its usage is still tracked and displayed, simply against an unlimited life.
One schedule per vehicle model
Life figures, durations and maintenance intervals are defined once, on the vehicle template, and every vehicle built from that template uses the same schedule.
A fleet of identical cars is lifed identically, and a change to the template’s schedule is a change for the whole fleet.
Operations running more than one kind of vehicle use multiple templates, each with its own structure and its own schedule.
Recording maintenance
Maintenance is recorded against the component, from the vehicle you are working on:
Inspect and Rebuild — record the work with a note and an effective date; the matching cycle resets from that point.
Replace — swap the part for a brand-new component (Stintline creates it, capturing its serial number) or a pre-existing component chosen from your stock, with its own accumulated history. The old and new parts are linked in the record, and the outgoing part can be retired in the same action, or returned to stock for reconditioning.
Every action builds the component’s permanent history — what was done, by whom, when, and at what usage point — alongside the automatic entries for installs, removals and transfers. Whole subassemblies are maintained and replaced the same way, as complete units; that is covered on the Subassemblies page.
Inspection and rebuild cycles
On plans with advanced component modelling, component types can also carry an inspection interval and a rebuild interval, in the same units as the life type — inspect every 5 hours, rebuild every 1,000 km.
Recording an inspection or rebuild resets that cycle from the usage point where it happened, and Stintline tracks each component’s progress through its current cycle and reports what is due next: the next inspection, the next rebuild, or — approaching the life limit — replacement.
The time-based override
Some parts have a calendar life as well as a usage life — seals, fluids, safety-critical items with a manufacturer’s shelf life.
For these, a component type can also carry a life duration in months. Each component then has an expiry date, set from the date it entered service, and its life is bounded by both figures: 12 months or 10,000 km, whichever is sooner.
Reports show the expiry date and the time remaining alongside the usage figures.
One percentage, both clocks
Stintline reports each component’s position in its life as a single percentage of life used, taking whichever is further along: the usage fraction or the elapsed-time fraction. A part at 40% of its kilometres but 9 months into a 12-month duration reads 75% used — the calendar is what will retire it, and the number says so.
Every component type has a warning level (80% by default). Component lists and reports flag each part as within life, approaching its limit, or over life, so the parts that need attention surface without being searched for.
Serial numbers and part numbers
Component types carry the manufacturer’s part number and current revision, so your catalogue matches the parts book. Each physical component carries its own serial number — entered when the part is fitted, or generated automatically where your template auto-numbers identifiers — so any individual part can be found, and its full history read, from the number etched on it.
Starting with a used fleet
Vehicles do not need to be new to start tracking in Stintline. Existing components can be pre-loaded with their prior usage, so a part with 3,000 km behind it starts at 3,000 km, not zero — and warnings, cycles and percentages are honest from day one.
For a whole fleet, prior use can be imported in one upload from the manufacturer’s component-tracking file: every vehicle’s figures, including the usage points of each part’s last inspection and rebuild, matched by the manufacturer’s own component names — and the fleet’s vehicles can be created in the same run, complete with chassis numbers and component serial numbers
Who records what, and where parts go
Access control decides who can record maintenance, who can replace and retire parts, and who can only view — down to individual vehicles; see the Access Control page. When a part is removed and returned to stock, its physical whereabouts can be tracked too; see the Inventory Locations page.
Availability
Usage tracking against component life is the heart of every Stintline plan. Time-based expiries and heat-cycle life are available as account options; inspection and rebuild cycles are included on plans with advanced component modelling. Pre-loading prior use is available on plans with the component usage offset feature, and fleet-scale prior-use import is part of onboarding — talk to us when you are ready to move an existing fleet across.
