ISO 15243 · ISO 10825 · multi-tenant · exportable

Read the damage.
Name the cause.

A photograph of a returned gearbox part becomes a standards-linked failure record: the damage mode, the severity, the mechanism that caused it, and the batch it came from. The model suggests. The inspector decides. Every confirmation becomes training data.

ISO failure modes
13

ISO failure modes

Cause mechanisms
8

Cause mechanisms

Severity grades
5

Severity grades

Outer raceway5.1 fatigue · 5.4 electrical erosionRolling element5.5 plastic deformationInner raceway5.2 wear · 5.3 corrosionBore and land5.6 fracture and crackingFIG. 1 · ROLLING BEARING · ISO 15243
live
select
ISO 15243CH 1/3
6 MODES

Rolling-bearing damage classes

Core objectives

Three things the system is built to do

Witness is not a general defect detector. It is scoped to rotating equipment, to two published standards, and to the decision an inspector actually has to make.

  1. 01

    Make a failure traceable

    A returned part usually arrives with a photograph and nothing else. Witness turns that photograph into a record that cites a clause of a published standard, so the finding survives a warranty dispute.

  2. 02

    Separate what from why

    The damage mode says what the surface shows. The attribution says why it got there. The same pit can mean end of life or a contaminant dent that seeded it early, and the batch-level action differs.

  3. 03

    Turn inspection into data

    Every confirmed or corrected record is a (model, human) pair. The workspace accumulates a labelled set that belongs to the plant, and exports on demand as JSON.

Workflow

Photograph in, reviewed finding out

Each stage does one job and hands off. Nothing decides for itself past the confidence gate. That gate is the single place the system chooses whether a person is needed.

01Photographbench camera02IntakeEXIF · pHash03AnomalyPatchCore04ISO modeforced choiceGateconfidenceFiles automaticallyInspector reviewsInsightfleet cubeSCHEMATIC · PHOTOGRAPH TO FINDING
0.82gate threshold

Score above the threshold files itself. Below it queues for a person.

  1. 1

    Enrol

    Upload known-good reference photographs for each part family. This set defines what normal looks like for this workspace, not for the industry.

  2. 2

    Intake

    The photograph is read for EXIF, scored for provenance, and hashed. A perceptual hash catches the same part submitted twice.

  3. 3

    Detect

    Stage one asks one question: is this part abnormal against the reference set? A PatchCore-style memory bank answers it, and returns a heat map.

  4. 4

    Classify

    Stage two asks a second question: which ISO mode is it? The choice is forced. The model must pick from the standard's own list, never invent a label.

  5. 5

    Decide

    A confidence gate splits the traffic. High confidence files itself. Low confidence queues for an inspector, whose call is the authoritative one.

The loop does not stop at the finding. A confirmed record links back to the batch that produced the part, so a repeated mode across one supplier becomes a fleet signal rather than a pile of separate complaints.

What it knows

Two part families, two published standards

Bearings and gears fail in different ways, and each has its own catalogue. Witness carries the standard's own numbering, so a finding traces back to the document rather than to a label somebody invented.

Outer raceway5.1 fatigue · 5.4 electrical erosionRolling element5.5 plastic deformationInner raceway5.2 wear · 5.3 corrosionBore and land5.6 fracture and crackingFIG. 1 · ROLLING BEARING · ISO 15243

Rolling bearings · ISO 15243

Six primary damage classes, from rolling-contact fatigue to fracture and cracking. 6 modes carry clause numbers such as 5.1 and 5.6.

Tooth flankscuffing · contact fatigueTooth rootcracks · tooth fractureMesh contact linewear · plastic deformationFIG. 2 · SPUR MESH · ISO 10825

Gear teeth · ISO 10825

7 wear and damage classes covering the flank, the root and the mesh: wear, scuffing, contact fatigue, cracks and tooth fracture.

The third axis: attribution

A mode describes the surface. An attribution names the mechanism that put it there. Witness records both, because the fleet action depends on the second one.

  • Operating duty
  • Lubrication
  • Contamination
  • Mounting / alignment
  • Overload
  • Electrical
  • Corrosion
  • Handling

Inside the part it reads

SHEET
03
Bearing assembly
REV B
SCALE NTS
1Outer racehardened ring2Cageball spacing3Rolling element9 off4Inner raceshaft fitFIG. 3 · EXPLODED ASSEMBLY · DEEP-GROOVE BALL BEARING

Reference geometry

FIG. 4-AFastener
Thread
M12 × 1.75
Grade
10.9
Head
hex, 19 A/F
Torque
86 N·m
FIG. 4-BShaft seat
Diameter
Ø 20 h6
Fit
k5 interference
Ra
0.4 µm
Runout
0.010 mm
FIG. 4-CPreload spring
Free length
84 mm
Rate
12 N/mm
Wire
Ø 2.5 mm
Ends
closed, ground
FIG. 4-DHousing flange
Bolt circle
Ø 68 mm
Holes
6 × Ø 9
Pilot
Ø 36 H7
Material
EN-GJL-250

Severity · ISA-101 discipline

Five grades, each tied to an action

Severity never rides on colour alone. Every grade pairs a hue with a filling-disc glyph and a numeral, so the signal survives colour-vision deficiency, a greyscale print, and a washed-out bench display.

  1. 0

    Serviceable

    Return to service

  2. 1

    Monitor

    Re-inspect at next interval

  3. 2

    Plan repair

    Schedule rework

  4. 3

    Remove from service

    Pull the part

  5. 4

    Safety-critical

    Quarantine batch, escalate

Features

What you get once records start accumulating

The first finding is useful. The hundredth is where the system earns its place: patterns across suppliers, batches and duty cycles become visible.

Traceable

Every record cites a clause

Bearings map to ISO 15243 damage classes and gears to ISO 10825, 13 modes carrying the standard's own numbering, so a finding traces back to the document.

Isolated

One workspace cannot read another

Postgres row-level security scopes every row to the signed-in tenant. Reference sets, findings and batches belong to the workspace that made them.

Honest

The gate is visible

Confidence is shown, not hidden. A record that the model was unsure about is marked unconfirmed until a person confirms or corrects it.

Provenanced

Findings link to batches

A part carries a batch code and a supplier. Link enough findings and a repeated mode stops being an anecdote and becomes a warranty case.

Analytic

The fleet cube

Insights aggregates on three axes at once: ISO mode against severity against attribution, so a lubrication problem separates from a design problem.

Portable

The labels are yours

Confirmed records export as JSON, with the model's suggestion and the human call side by side. That pairing is what trains the next model.

Start with one photograph

Open the console and walk the loop end to end: enrol a reference set, score a part, accept or correct the ISO mode, then watch the finding appear in the fleet cube against its batch.