How it works

Log a sample, get it scored the moment it lands

Each sample keeps its time, its value and who captured it, tied to the lot and the characteristic. Its statistic is stored with it, so the lot view and the history read the same points.

  • Capture sequence Station selected Reading taken Scored against baseline Logged and flagged

Capture

Log each reading at the line

Log the reading right at the line, tied to the lot that’s running. Every point is stored, not just the ones that trip a flag, so if a value starts drifting on second shift, it’s on record before anyone asks.

  • Entered at the line, tied to the lot and the characteristic
  • Time, value, and who captured it, kept with the point
  • Every statistic persisted, so the history is there later
  • Weld cycle time z 3.4
  • Flagged 30m ago

Outliers

Catch outliers at three sigma

Every point you log is scored against the recent mean and spread. Anything past three sigma is flagged, and the flag carries its z score so you can see how far out the reading landed.

  • Three sigma by default, sensitivity set per characteristic
  • The flag shows the value, the mean, and the z score
  • Thin data holds the flag back until there is enough
  • Weld current, Weld Line 1Mean 12.0 A
  • Run of 8, one side

Trend rule

Catch drift before it goes out of limits

Eight points on one side of the mean read as drift. You get the flag while every reading is still inside three sigma, with the run length shown, so you can see the trend build before it becomes an outlier.

  • A run test on which side of the mean the points fall
  • Raised while the numbers still look acceptable
  • Run length shown, so the shift can see it building
  • Bore diameter by lot 12.01 L01 11.98 L02 12.03 L03 12.00 L04

Lots

Open the chart for a lot or a characteristic's history

Open the chart for the lot that’s running, or go back through the full history behind one characteristic. Any commentary the shift left on the run stays beside the points it explains.

  • Chart view per characteristic, updating as samples land
  • Lot view for what one lot actually did
  • Run commentary kept beside the points it explains
  • Weld cycle time, last 124.92 s

Checks and chart

Get two checks and one chart. Keep your Cpk package.

You get two tests and one chart. Xbar-R charts, Cp and Cpk aren’t included, so keep the package you use for those.

  • No Xbar-R, Xbar-S, p or c chart families
  • Flags score each reading against the recent mean and spread
  • No Cp or Cpk capability indices
  • Weld cycle breach, waiting call
  • Investigation Enginecase opened
  • Auditor: same flag on lot check

Flag review

Review the flag, then make the call

A flag is a starting point, recorded with the point that raised it. What it means for the lot is your quality process’s call. That call might open a case in the Investigation Engine, or line up with what the Auditor sees on a lot check.

  • The flag is recorded with the point that raised it
  • The Investigation Engine picks it up when it becomes a case
  • The Quality (Auditor) reads the same detection on a lot check

What the line sees when a reading drifts

    • Weld cycle timeLot L-2291, T. Nakamura, 14:20 4.72 s
    • Inside limits, logged
    • Point 212 on record

    Every reading gets logged as it happens.

    You log the reading at the line, against the lot that's running. The point is captured whether or not it trips a flag, so second-shift drift is already on record.

    How capture works
    • Weld cycle time, last 84.92 s
    • 8 points, one side

    Drift flagged before it breaks three sigma.

    Eight readings landing on one side of the mean count as drift. The flag comes while every point still sits inside three sigma, so the shift sees the trend building early.

    How drift detection works

FAQ

Ask what shifted before your lot closed.

30 minutes on your samples and how the SPC Engine scores them against the recent mean.