Skip to content
All field studies

Field study 01

Two instruments on one machine, moving apart.

Over seven weeks one mount grew quieter and steadier while the mount beside it grew more erratic. Same frame, same work, same shifts. Averaged into one machine reading, the two movements partly cancel. Held as two accounts, they do not.

Period
1 Jun to 21 Jul 2026
Site
Lien Chau Luc
Instruments
2
Operating days
49
Evidence objects
482,111
Proof windows
145

This study reports what was recorded and what follows from it. It does not report an outcome, because there is not one yet. The final section states what these seven weeks cannot establish.

The left mount fell by half. The right never left its band.

LeftRight
0100200300400mg1 Jun15 Jun1 Jul21 Jul19 Junmachine stopped, lime clearedbrief rise on restartRight62 mgLeft129 mg

Hover, or focus the chart and use the arrow keys to read values day by day.

Figure 1  Daily median vibration at each mount, in milli-g.Left falls from 431 on 3 June to the low 120s by mid July. Right stays between 62 and 130 throughout. Breaks in the lines are non-operating days, not missing measurements.

What changed, measured three ways

A level that falls is one observation. A level that falls while its spread narrows and its day-to-day variability collapses is a stronger one, because the three are not obliged to move together. The left mount moved on all three. The right held its level while its spread nearly tripled.

Within-day spread is the interquartile range of window medians on that day. Day-to-day variability is the standard deviation of daily medians across the period.

Three measures, three periods
MountPeriodLevel, mgWithin-day spreadDay-to-day variability
Left1 to 14 Jun259.821.490.3
15 Jun to 4 Jul154.27.914.5
5 to 21 Jul132.77.613.3
Right1 to 14 Jun84.14.110.7
15 Jun to 4 Jul91.913.314.8
5 to 21 Jul84.511.910.9

Three separate things happened. The machine treated them separately.

It is tempting to read this study as one story. It is not. A step in the signal, an operator stopping the machine to clear a drain, and a settled quieter regime are three different events, and the record keeps them apart. So does the machine.

  1. 14 June
    A step in the left mount

    The left mount reads 190.4 one day and 145.1 the next. Nobody notices. No message is sent, no claim is written, nothing is flagged. The reading is simply recorded.

  2. 19 June
    The drain is cleared

    The operator reports lime scale and water overflow and stops the machine. The operating record independently shows a third of a normal day. The machine answers in eight seconds, says the event is outside its vibration sensor, and asks to record it. The confirmation step goes unnoticed, so nothing is written.

  3. 5 July
    The detector fires

    Running over the previous thirty days, the trend detectors register a falling level and a narrowing spread on the left mount, and a widening spread on the right.

  4. 19 July
    It states a position

    Not that the machine improved. That it is no longer treating the left mount as an ongoing rise.

  5. 20 to 21 July
    It goes looking for a cause

    Five weeks after the fact, it locates the step at 14 June and begins asking whether anything was done to the machine around that date. Fifteen claims in two days, each with what would prove it wrong.

The gap between the third row and the last is the point of this system. The step was invisible on the day it happened. It became visible only once there was enough of the machine's own history to see it against.

Five weeks later, it went looking for the cause

On 20 July the machine located the step at 14 June and started asking what had been done to it around that date. Nobody prompted this and nobody had reported anything. Every claim below was written by the machine in those two days, and every one carries the observation that would prove it wrong.

It placed the step at 14 June. The daily record agrees: the left mount reads 190.4 on 14 June and 145.1 on 15 June. The lime event five days later appears in none of these claims.

01
What it claimed

If they dressed or replaced the left grinding wheel around 2026-06-14, that could explain the left step and the later lower, steadier signal on that mount.

What would prove it wrong

They say the left wheel was dressed or replaced around that time, but my left mount does not stay lower and steadier afterward.

02
What it claimed

If a mount, sensor, or readout changed around 2026-06-14, then I expect the left step to line up with that event rather than with a machine-wide change.

What would prove it wrong

No mount, sensor or readout change happened, yet only the left point stepped anyway and the product stayed unchanged.

03
What it claimed

If the glass recipe, thickness, speed, or load changed around 2026-06-14, that change can explain the left-point step-down without needing a fault.

What would prove it wrong

The left point stayed stepped down even though the run conditions did not change around 2026-06-14.

04
What it claimed

The left-zone step matters because it is still current; if it is tied to finish quality, it can affect what ships even while the vibration looks calmer.

What would prove it wrong

If the left product finish and chipping stayed unchanged through and after 2026-06-14, then the signal change is less urgent for output quality.

Where it has landed, for now

I have settled on the declared left mount: its recent vibration is lower and steadier than its earlier window, so I am not treating that as an ongoing rise.

Note what it did not do. It did not call a quieter signal an improvement. It raised the possibility that its own instrument had changed, before anyone asked it to. And it committed in advance to what would make each explanation collapse. None of these has been adjudicated yet.

19 June: the operator wrote, and the record already agreed

At 07:07 the operator sent a message about the machine. Eight seconds later the machine answered. Neither was consulting the operating record, and the operating record had already registered the same event.

Nước tràn, vôi cặn xung quang máy nên hôm nay phải dừng máy nạo vôi cho nước lưu thông lại.

Water overflowing, lime scale around the machine, so today we had to stop the machine and scrape the lime out so the water flows again.

Operator, Lien Chau Luc, 19 June 2026

Operating time recorded, every day of the study

0200400600min1 Jun15 Jun1 Jul21 Jul132 minmachine stopped, lime cleared
Figure 2  Minutes of recorded operation per day.A third of a normal day on 19 June, the day the operator said the machine was stopped. Nobody adjusted the pipeline and nothing told it a stop had happened. The second instrument recorded 122 minutes the same day, agreeing within eight percent.

A third of a normal day, on exactly the day the operator said the machine was stopped. The testimony and the instruments agree and neither was derived from the other. This is what it means for evidence to adjudicate testimony rather than decorate it.

What the machine said back

It offered two possible mechanisms rather than one: the water line blocked by scale, or weak flow at the supply zone. It reasoned to the consequence, degraded cooling and wash-off at the work zone. Then it said the thing that matters most.

Hiện tại, tôi chưa thấy dấu hiệu rung của hai bên đổi theo hướng xấu rõ ràng từ các phiên gần đây, nhưng đây là một thay đổi thực tế bên ngoài cảm biến rung của tôi, nên tôi sẽ cần nhìn thêm sau khi nước lưu thông lại.

I have not seen either side's vibration turn clearly worse in recent sessions, but this is a real change outside my vibration sensor, so I will need to look again once the water is flowing.

Machine reply, 19 June 2026

It declined to explain a plumbing event with a vibration reading it did not have. It then asked permission to record the observation, because an observation enters a machine's permanent record only when the person who witnessed it confirms.

The machine asked to record this as an observation. The confirmation step was new to the site and went unnoticed, so nothing was written and the machine formed no claim about the event. It is not in its memory. That matters for what follows, because everything the machine later concluded about this zone was reached without it.

Two machines, two sites, the same morning

On 21 July both pilot machines sent their operator an account of what they were reading. They share no data with each other and neither was prompted. Both arrived at the same blind spot: the wheel face and the coolant, the part of the work neither of them can feel.

Lien Chau Luc, delivered 21 July

nơi bề mặt đá, nước làm mát, hoặc độ bám cắt đang đổi theo cách làm tôi chạy êm hơn nhưng chưa chắc đã cắt tốt hơn

the wheel surface, the coolant, or the cutting grip is changing in a way that makes me run smoother but not necessarily cut better

Hoang Lan, delivered 21 July

tôi đang phải “làm nhiều hơn cho cùng một việc” so với trước. Nghĩa là tiếng và rung của tôi theo mỗi phút làm việc đang tách ra khỏi mức thô chung

I am having to do more for the same work than before. My sound and vibration per minute of work are separating from the overall level

Neither machine was told what the other was seeing. They reached the same class of explanation from their own separate histories, and both were explicit that it sits outside what they can sense.

And one of them named the water, a month late

On 19 June the Lien Chau Luc operator reported overflow and lime blocking the water flow. The machine asked to record it, the confirmation step went unnoticed, and nothing was written. It is not in the machine's memory. A month later it named a coolant shortage on its own, from the shape of its signal.

chỗ tôi còn để mở lớn nhất vẫn là: đá bên đó có đang bị lì mặt, thiếu nước, hay điều kiện bề mặt đang làm tôi “êm” đi nhưng sản phẩm xấu đi hay không

the biggest thing I still leave open is whether that wheel is glazing over, short of water, or whether surface conditions are making me quieter while the product gets worse

It had nothing to recall, because the account was never written down. It got there from its own record instead.

Neither called quieter better

This is what the study turns on, and both machines wrote it themselves, in Vietnamese, to the people who run them.

chạy êm hơn nhưng chưa chắc đã cắt tốt hơn

running smoother, but not necessarily cutting better

A quieter, steadier signal is exactly what a wheel glazing over produces. So each machine held the reading apart from the conclusion, named what it cannot see through vibration, and asked for the one observation that would settle it.

What each asked for

Lien Chau Luc, delivered 21 July

If the glass edge after the polishing zone starts to dull, burn, or chip while my vibration stays low and even, I will suspect the wheel and coolant more strongly. If the edge stays clean and sharp, I lean away from that.

Hoang Lan, delivered 21 July

If you tell me whether the outfeed polishing cluster has just been replaced, repaired, or re-dressed, or is still the old one, I will reorder the possibilities on that.

Two questions, both decided in advance, both answerable only by a person standing at the machine. Both are still open.

A factory floor drainage channel opened for cleaning. A worker holds a woven collection sack while lime deposit is cleared; a hose runs across concrete caked with white scale.
Plate 1, 19 June 2026Drainage channel opened, lime deposit cleared into a collection bag.

What the system does

Not a feature list. Every line below is something the system did on this machine, in the window this study covers, and the number beside it is a count of rows in its own record.

It kept 482,111 pieces of evidence without being askedVibration and acoustic recording, written to the device before it ever reaches the network, so a lost connection costs transmission and never the record. 49 operating days at this site, unbroken.
It wrote 286 claims, each with its own undoingEvery claim it forms is stored together with the observation that would prove it wrong, written before the answer is known. Not a confidence score. A stated condition under which it would have to admit it was wrong.
It put a date on a change nobody reportedIt found a step in its own left-mount record, placed it at 14 June, and began asking whether anything had been done to the machine around then. The operator had not mentioned it. Neither had we.
It raised the possibility that its own sensor was the problemUnprompted, and alongside the explanations that would have flattered it. A system that cannot suspect its own instrument will eventually mistake a failing sensor for a healthy machine.
It is carrying 16 open questions about itselfRanked by how much each one matters. The top one on this machine is a rise in vibration it could not explain, opened on 17 June and still being asked. A question stays open until someone with the standing to answer it does.
It logged 125 things it could not answerEvery time it is asked something it cannot retrieve, it records the miss. What it does not know is measurable rather than merely absent, and that record decides what it learns next.
It answered an operator in eight seconds, in his languageAnd declined to explain a plumbing event with a vibration reading it did not have. 151 scans at the machine over three months, no account and no training required.
It stayed quiet the rest of the timeNo daily digest, no schedule. It reaches out when its own measurements moved, or when it needs to learn something it cannot observe. Silence is information, not absence.

What we do not publish

This study describes what the system observed and how it reasoned. It does not publish our detection thresholds, tuning constants or gate criteria. Those are the part a competitor would copy and the part a customer never needs. We would rather show you the evidence and let you judge the conclusions.

Operational significance

Lower and steadier vibration does not automatically mean better machine performance. In this case the same signal could represent improved operation, a glazed wheel, changed production conditions, coolant issues, or sensor degradation. MIS preserved these possibilities and identified the human observations required to distinguish them.

That is the difference between a reading and an investigation. A threshold alarm would have stayed silent through all seven weeks, because nothing crossed a limit. What moved was the relationship between one mount and its own past.

What these seven weeks do not establish

Three sites and five months is a field study. It is not a demonstration of effect, and the following are set at the same size as the finding because they carry the same weight.

No time saved has been measuredNo before-baseline exists at any site. We never measured what diagnosis cost these operators previously, so we cannot claim a reduction and will not estimate one.
No prediction has been judgedThe machine records what would prove each claim wrong. The process that adjudicates those claims went live this month and has returned no verdict on any of them.
The cause of the divergence is unsettledFour explanations remain open, including that one instrument's mounting is degrading.
The 19 June stop explains nothingMost of the left mount's decline occurred before it. The stop is visible in the operating record and produced a brief disturbance afterward. It is not the cause of the drift.
One observation never made it into the recordThe machine asked to record the 19 June event and the confirmation step went unnoticed, so it was never written. The event is real, photographed, and visible in the operating record, but it is not in the machine's memory. We are stating that rather than quietly backfilling it, and it is the reason the coolant hypothesis five weeks later counts as independent.

What the operator says

The operator at this site was asked, in July, whether the system had changed anything for him. This is what he said, in his own language, and he has confirmed it reads correctly.

Cái này tiện, giúp tôi theo dõi máy thường xuyên. Giống như có thêm một đôi mắt nữa trông máy giùm mình.

It is useful. It helps me keep watch on the machine regularly. Like having another set of eyes looking after it for me.

Operator, Lien Chau Luc, July 2026

We have not measured what that is worth, and this study does not claim it. It is recorded here because it is what he said.

Where this stands

Observed

A persistent local signal change on one mount, and a separate abnormal operating day.

Reasoned

Several possible explanations, each stored with the evidence that could reject it.

Not yet established

The cause, the effect on product quality, the economic value, and whether any failure was avoided.

The next phase is to close these open questions through documented inspection, intervention, and before-and-after production evidence.

Every figure on this page is a count or an aggregate of rows in a named table, read on 21 July 2026. Counts exclude internal test instruments.

The record is live and continues to accumulate, so these figures are a dated snapshot rather than a running total.

Every machine deserves a memory.

The earlier a machine starts recording, the more its own history can tell you.