Everything Reliable lubrication management does, in plain language. Search it, or scan straight through.
Every point and every container carries a shape plus a color, so the match reads instantly on the floor.
Shapes and colors are yours to define. A plant with a scheme already painted on the floor keeps using it.
Print tags in sheets from your own printer, each carrying a barcode any standard scanner reads.
A scan resolves to one point, or reports the code as unknown. Partial matches stay out of the answer.
A site can re-tag a shared product to match what is painted on its own floor, while the catalog stays shared.
A plant can carry products its sister sites skip, and those products stay visible in consolidation work.
Plant, area, system, machine, component, point. The tree goes down to the individual bearing housing.
Sump volume, the charge in it, bearing geometry and sampling live on the component, so two points on one gearbox always agree.
Breathers, sight glasses, sampling valves and magnetic plugs recorded where they are fitted, and searchable across the plant.
Fitting a desiccant breather offers the tasks that come with it, for the plant to accept and schedule.
A, B and C ratings that flow into health scoring and into how the schedule ranks work.
Hours and hours-per-day on each machine, for programs that schedule on runtime.
Points sequenced the way the plant is actually walked, with the sequence owned by the planner.
Reordering a forty point route is one drag, on desktop or on a tablet, with arrow keys for accessibility.
One point per screen with quantity, method, machine state and the procedure at hand.
Missed work gathers into its own one-off round, leaving standing routes exactly as the planner built them.
A defined set your plant maintains, so the reasons aggregate into something you can act on.
A skipped or blocked service leaves the due date where it is, keeping compliance figures true.
Points that need the machine down say so on the screen the technician is holding.
Completion, duration and who walked it, for every run.
Work is saved to the device as the round is walked, so a locked phone, a closed tab or a save in a dead zone is picked up where it stopped.
A picture of the machine and of its nameplate sits on the asset, so the typed make, model and serial have the plate behind them.
A leak or a damaged seal is photographed where it is found, and the picture travels with the issue that gets raised.
A camera photo is compressed on the phone before it is stored, so a machine with several of them stays quick to open.
Checklist answers rather than paragraphs, so findings aggregate into counts and trends.
Corporate sets a baseline and each site adds to it.
Temperatures and levels captured as values that trend, alongside the pass or flag state.
A point can name the handful of items it looks at, keeping a focused task focused.
Something worth chasing becomes a tracked defect with an owner and a status.
Write a procedure once and every point doing that job picks it up, so corrections land everywhere at once.
A site procedure takes precedence over the corporate one for the same task.
The record shows which revision was current when the work happened.
A warning sits outside the numbered sequence, where it reads as a warning.
Opened when somebody wants it, which is when a procedure is actually read.
ISO 4406 codes, water, viscosity, TAN, and wear metals held per sample.
Your engineers set the bands, and each component is judged against the set that fits it.
Every parameter charts against its own caution and alarm bands.
Taken, at the lab, and reported, so a sample in flight stays visible.
An exceedance becomes a tracked defect with an owner and a status.
Every thickener and base oil pair screened before a top-up happens, and your own engineering has the last word on any of them.
Published ratings are transcribed from a named chart and cite it, the matrix warns about a pair rather than clearing it, and your plant can record its own ruling.
Minutes of work per day compared with the crew you have, so peaks get leveled early.
Everything needing a shutdown machine gathered for the window when it comes down.
What the program costs, and where it goes.
Product issued against product held, with the coverage behind the figure stated.
Stock levels, reorder points, and the transactions behind them.
Which of these products could be one product, across every plant.
Compliance, oil analysis, deviations, stock and cost, ready to print.
Pick the sections, the scope and the dates, and save the definition.
Every printed page names the plant, the period, who ran it and when.
Report definitions get saved rather than results, so a page always reflects current records.
Who changed what, from and to, kept as an append-only history.
Every table exports, including on the way out the door.
Ask what is due, how the plant is doing, or where to find something, without leaving the page you are on.
Every figure comes straight from the plant records rather than being generated, and the reply links back to where it came from.
The assistant will not set an interval, pick a grade, or rule on whether two products can be mixed - it says so, and points to the tool that decides.
When a figure is easier seen than read, the reply draws it - a health ring, a ranked bar, a short table - beside the words.
A microphone turns speech into the question, for a technician whose hands are not free to type.
Compliance, health and consumption in one reporting currency.
What somebody may change and where they may act stay independent questions.
A Texas mill reads gallons and Fahrenheit while a Quebec site reads liters and Celsius, from the same stored values.
MLT, MLA, or a list your program defines, with expiry dates tracked.
Health weighting, alarm targets, week start and grace periods per site.
Create the plant, build its area, machine and component tree, and add its points and lubricants, all through the screens.
A plant that runs no oil analysis turns the module off, so it leaves the screens and stops counting against the health score, with nothing deleted.
Each company sees its own records, enforced in the database itself.
The demo is a fully stocked mill: real routes, live lab data, and a year of history to dig through.