QMS software that catches a bad reading before the lot ships.

Quality management software (QMS) for the plant floor. Operators log checks on forms, the Auditor sweeps readings every 15 minutes, and each problem becomes a case.

Book a demo All solutions
  • Fill weight outside range, Line 3, medium
  • Hold lot L-2210? Open hold Dismiss

Some of the people we've built with

  • Fill weight, Line 3 form v6Every numeric field watched
  • Flags this week 4

A reading slips out of range overnight. The chart is in a binder, and the lot has already shipped.

Catch the bad reading before the lot ships.

Old way

checks are paper or spreadsheets, and nobody reads the trend until the audit.

New way

operators fill in forms at the line, and every numeric field is watched, including ones nobody thought to chart.

  • An outlier opens a hold inside the authority you set, and anything outside waits for a person. A drifting form field notifies a person.

The Modules behind the quality record

How a quality check becomes a closed case

Each Module does one job, in this order.

1 It connects

  • Paper checks
  • Spreadsheets

2 What runs, and what it does

  1. Form BuilderBuilds the checks your operators fill in, with fields that show only when they apply and every form version kept.
  2. AuditorSweeps readings every 15 minutes, flags outliers and proposes a hold. A form field that drifts notifies a person.
  3. Authority MatrixSets which holds the Auditor may open alone and which need a person.
  4. Approval QueueHolds that need a person wait here, oldest first.
  5. Investigation EngineTurns an issue into a case with its causes, countermeasures, evidence and lesson.
  6. Notification CenterRings the bell for the right person when a hold or a flag needs them.

3 What you get

  • Hold released by R. Singh 14:20Decision on record

In customer plants, downtime fell 86% and shorts went from 50 a month to 12.

Real plants, real numbers, first in manufacturing.

  • less downtimeacross seven production facilities 86%
  • customer shorts a monthwithin six months 50 to 12
  • longer planning horizonin a customer deployment 50%
  • facilities on one installationrun by one customer 19
Where these numbers come from

These numbers come from customer deployments, first in manufacturing. We don’t name customers without asking them first. If you want to talk to a customer, ask us and we’ll ask them.

  • Case CS-0042 Issue raised Causes found Countermeasure in progress
  • Lesson learned: seal temperatureWritten on the case before it closed

Log the nonconformance, find the cause, keep the lesson

A nonconformance becomes one case. The causes, the fix and the lesson stay together and stay findable. mode40 was started by people who ran plants before they wrote any software.

  • Raise the defect where it happened, tied to the record it came from
  • Fishbone causes, target conditions and countermeasures on the same case
  • Attach photos, reports and records as evidence
  • Record the lesson on the case, and every change to it is logged
  • Access is set per screen: dashboard, records, schedule, holds and root cause

Related use cases and systems

FAQ

Bring your last nonconformance.

30 minutes on one real issue: the check, the hold and the investigation. We'll show you how it runs from first report to lesson.

Book a demo See the Investigation Engine