OPEN BETAFree while in beta - no subscription is charged.What beta means for your data

WheelHub.iO
Transparency

Your numbers come from your readings

WheelHub shows what your CALIPRI readings say. Every profile, classification, trend and forecast is worked out from the exports you upload, so the results are only as good as those readings and how each upload was matched to your fleet.

WheelHub is in beta

WheelHub is in open beta. It works, people are using it on real fleets, and it still has bugs. Some of those bugs will show up in the numbers.

Most fixes go out without you noticing. Now and then a fix changes how data is stored. When that happens, the only clean way forward may be to clear your organisation's data and ask you to upload your exports again. We don't expect this often, but it can happen. If it does, we'll tell you as soon as we know, along with why and what to re-upload.

So while we're in beta, don't treat WheelHub as your only copy of anything. Keep your original CALIPRI exports and your own maintenance records.

What the numbers are

WheelHub shows you what your measurements say. It doesn't tell you what to do about them.

Every profile, classification, trend and forecast comes from the exports you upload. A reading taken badly, an upload filed against the wrong set, or a re-profile that was never recorded will all show up on the charts, and the charts will be wrong in the same way. A forecast is a projection from past readings. It knows nothing the readings don't.

Whether a wheel gets turned, swapped or left alone is your decision, made against your own maintenance standards. WheelHub is one input to that decision. It doesn't replace the inspection or the engineer who signs it off.

What accuracy depends on

Three things WheelHub relies on and can't check for you.

The readings

WheelHub analyses the measurements in your CALIPRI export. It doesn't take them. A probe out of calibration, poor contact on the wheel, the wrong measurement plan or a slip in the field all carry straight through to the profiles, classifications and trends. We can show you what was measured, but not how well.

Matching uploads to the fleet

Each upload is matched to an existing train set. If a file goes to the wrong set, or a wheel lands in the wrong position, its history and forecast describe the wrong wheel. The match shown at upload is our best proposal, and you confirm it.

The wheel's history

A wheel's trend only holds together if its re-profiles, replacements and position swaps are recorded. Miss one and the readings before and after it get treated as one continuous run, which throws off the wear rate and the forecast.

What that means for you

  • Check the measurement plan and the reading quality before relying on a classification.
  • Check that each upload is matched to the right set and wheel positions before you commit it.
  • Record re-profiles, replacements and position swaps, so trends and forecasts stay continuous.
  • Use classifications, trends and forecasts as one input to your maintenance decisions. They don't replace inspection or your maintenance standards.

Disclaimer

WheelHub presents and analyses measurements to support your wheel-maintenance decisions. It doesn't measure wheels, certify measurements, or replace inspection, engineering judgement or your regulatory obligations. Everything it shows is worked out from the data you upload and the matches you confirm. Check against your source records before acting on it.

Found a problem?

Email support@wheelhub.io. We can open your organisation's data, but we can't see what you were looking at. The more exact you are, the faster we'll find it.

Please send:

  • The page linkCopied from the address bar, so we open the same screen you had.
  • What you expected and what you gotNumbers help most. For example: "Sd shows 24.1 here, the CALIPRI export says 28.3."
  • The set and wheel positionIf it's about one wheel.
  • The export file nameAnd roughly when you uploaded it.
  • A screenshotIf it's about how something looks.
  • The XML file itselfIf your organisation allows you to share it. It's optional, but if an upload failed or was rejected we may never have received it, and the original file is usually the quickest way to the bug.

We'll only look at your data to chase down the problem you reported. We'll write back with what we found, whether it was our bug or something in the data, and what we changed.