On-prem deployment · Ready to ship · Validated with an automaker

Aletha / Tightening

See the defect behind the "OK"

From Greek Alḗtheia, "unconcealment" —— bringing the hidden truth to light

Aletha surfaces the False OK that rule-based systems miss — false tightening, thread stripping and cross-threading that pass the torque-angle window yet deviate in curve shape — and turns those findings into concrete production-operations improvements.

Vendor-neutral
Per-instance models · 6-D ontology
Unsupervised · cold-start
Agent diagnosis
Scroll
01
Act I The invisible defect

A passing reading
is not a sound joint

The controller only checks the end-point torque-angle window. Inside that window, false tightening, thread stripping and cross-threading land within spec and pass as OK — yet the shape of the whole torque-angle curve has already gone wrong. This False OK is an invisible process-quality risk.

A fixed window sees
only the end point
Aletha reads the whole curve

That is how it catches the "looks fine, actually bad" False OK from the curve shape — exactly what Aletha does.

OK / Suspect / NOK shape comparison (illustrative)

Amber = suspect (fluctuation / stick-slip), red = NOK; all three head for the Final target.

Case — out-of-sequence tightening

Illustrative · red = anomaly (out-of-sequence) · green = OK

A normal tightening has three clear stages — rundown → snug → elastic region. When the sequence is wrong it stalls before the elastic region, with repeated false snugging, taking several times the rotation to reach target torque — the final torque still passes, yet Aletha catches it from the shape. Curves are illustrative, axes are relative.

02
Act II From signal to action

Not just an anomaly-detection engine
a lean lever for quality production

It turns every False OK into a structured, traceable result pinned to the exact process instance — an event + root-cause label + evidence curve. How much value that unlocks depends on the customer’s own management.

Full closed loop · real deployment

4-step loop · from AI detection to improvement

STAGE 01DetectAlethaAI DETECT STAGE 02Remote reviewAlethaREMOTE REVIEW STAGE 03On-site checkProcess eng.ON-SITE CHECK STAGE 04ImprovementProcess eng.IMPROVE ↺ improvements flow back to monitoring
FEEDBACK LOOP
Engineers’ improvements and their outcomes flow back into Aletha as reusable detection know-how; the next occurrence of the same anomaly is recognized automatically, with no review from scratch.

In practice with customers

01

ICA · containment + operator training

Confirmed anomalies trigger quarantine / re-check; high-frequency anomaly points become operator-training material to correct technique.

02

PCA · permanent corrective action

Root causes feed process-parameter changes (tightening strategy / PSET, mating face, error-proofing) to eliminate the issue at source.

03

People / team performance

Anomalies are attributed by station / shift / team and folded into quality KPIs, making accountability measurable.

04

Process-design feedback

Anomaly patterns flow back to process / product design, driving improvements in structure, fastening scheme and target torque.

05

Supplier quality feedback

Anomalies tied to a fastener / incoming-material batch → feed back to the supplier and lock down the batch.

06

Standard-parameter maintenance

Real normal curves maintain the “standard-parameter library”, curbing mis-edits and parameter drift.

07

Traceability & recall narrowing

Detection pinned to the process instance + logged events shrink the recall scope to the minimum when issues arise.

More use cases

These are only the validated starting points. The structured results the engine produces are open-ended — we look forward to operationally mature customers who turn data into action incubating more of their own use cases on Aletha.

03
Act III The moat

What sets us apart

There are data / quality tools from tightening-tool vendors, and domestic platforms too. Each has its strengths — but no single one holds all four below.

01

Vendor-neutral · no hardware lock-in

Ingests curves from any brand of tightening system / MES — one platform across every tightening tool in the plant.

02

Per-instance models · 6-D ontology

Across six dimensions — plant × shop × line × model × equipment × process — every process instance gets its own model → a tighter normal baseline → extremely low false-positive and miss rates.

03

Unsupervised · cold-start, out of the box

No labeling, no rule-writing — point it at historical normal curves and it builds models automatically; new models / process upgrades are covered automatically, no manual reconfiguration.

04

Ontology-ready · Agent diagnosis

Detection results + expert annotations accumulate in an ontology knowledge base; the on-prem Agent does more than detect — it offers causes and recommendations (diagnosis).

04
Act IV Fast deployment

Seamless go-live
no sensors, no line stoppage

Aletha connects directly to the tightening data you already have — no new hardware, no line changes, no downtime. After a one-time data integration, modeling, calibration, detection and event logging run fully automatically.

1

Data integration (service)

We connect your existing tightening data / platform

2

Pull historyauto

Take existing normal curves

3

Unsupervised modelingauto

One model per instance

4

Threshold calibrationauto

Shadow-mode trial run

5

Event loopauto

Anomalies auto-logged, fed back to the knowledge base

Plugs into your existing systems, adding the layer they can’t see
Existing on-site systemWhat it manages on the lineWhere it stopsWhat Aletha adds on top
Tightening controllerReal-time OK / NOKOnly checks the torque-angle window; in-window shape anomalies slip throughIn-window False OK
Tightening data platform / quality softwareCurve capture, SPC / reportsSees statistics and trends; locked to its own tools, granularity up to 3-DVendor-neutral intake, per-instance detection in 6-D
SPC / control chartsProcess distribution and driftDoesn’t read single-curve shape; needs manual rulesSingle-curve, rule-free shape detection
MES / quality traceabilityRecord, trace, reportRecords data; doesn’t detect anomalies itselfLogs detection as events, feeds back to traceability
Get started

Start with one pilot
Turning Data into Value

01

Pick a pilot

One line, a few critical safety tightening points.

02

On-site demo

Run detection on your own historical data.

03

Shadow run → go live

No downtime; close the loop in a few weeks.