IndustriesManufacturing
The work order says it was fixed. The next shift says it’s back.
AOI connects shift handoffs, operator messages, technician notes, and work orders into one equipment history, so a problem that keeps returning shows up as one problem instead of a string of separate fixes. It works alongside your CMMS, not in place of it.
What led up to it
Day 1 · 05:50Night shift handoff
Case packer on Line 2 jammed twice overnight. Cleared both, ran fine after.
Day 1 · 09:20Line 2 operator
Packer jamming on the 12-count again. Slowed the infeed to keep it running.
What the work order records
CMMS · WO-4471
ClosedLine 2 · Case packer
Adjust flap guide
- Opened
- Day 1 · 10:05
- Closed
- Day 1 · 14:30
16 days later
Whether it came back
Day 17 · 06:05Night shift handoff
Line 2 packer jamming on the 12-count again. Ran slow most of the shift.
Day 17 · 08:40Line 2 operator
Same jam as before. Cartons coming out of the glue station skewed.
“A work order can tell you what was repaired. The surrounding conversation often tells you what led up to it, what operators noticed, and whether the problem came back.”
Where a line’s history actually lives
Most plants keep more than one record of the same week. Each is written by different people, for a different reason, in a different place.
| Source | Who writes it | What it tends to hold |
|---|---|---|
| Shift handoffs | Outgoing lead or supervisor | What ran, what didn’t, and what the next shift should watch. |
| Operator messages | Line operators | The first mention of a noise, a jam, or a workaround. |
| Technician notes | Maintenance technicians | What was found, what was adjusted, and what wasn’t checked. |
| Work orders | Planners and technicians | The task, the asset, and when the work was closed. |
| Maintenance channels | The maintenance team | Triage, parts, and who is picking it up. |
| CMMS records | The system of record | Asset history, preventive maintenance, and completed work. |
- Shift handoffs
- Outgoing lead or supervisor
- What ran, what didn’t, and what the next shift should watch.
- Operator messages
- Line operators
- The first mention of a noise, a jam, or a workaround.
- Technician notes
- Maintenance technicians
- What was found, what was adjusted, and what wasn’t checked.
- Work orders
- Planners and technicians
- The task, the asset, and when the work was closed.
- Maintenance channels
- The maintenance team
- Triage, parts, and who is picking it up.
- CMMS records
- The system of record
- Asset history, preventive maintenance, and completed work.
Your CMMS stays the system of record. AOI adds the history around it. It does not replace it.
One case packer. Seventeen days. Seven records.
Read in order, this is one problem. Filed where each entry was written, it is seven separate records in four places, with unrelated traffic in between.
Line 2 · Case packer
Illustrative example. Not customer data.
Day 1
05:50Shift handoff · Night to day01
Case packer on Line 2 jammed twice overnight. Cleared both, ran fine after.
09:20Operator message · Line 2 channel02
Packer jamming on the 12-count again. Slowed the infeed to keep it running.
10:05CMMS · WO-4471
Opened03Line 2 case packer: adjust flap guide.
13:55Technician note · Maintenance04
Flap guide was out about 3 mm. Adjusted, tested 20 cycles. Glue pattern looked uneven, didn’t check.
14:30CMMS · WO-4471
Closed05Work complete.
Day 6
+5 days
11:10Maintenance channel
Line 4 changeover parts arrived. Staging them by the cage.
Day 11
+5 days
18:00Shift handoff · Day to night
Line 2 ran clean. Filler down 20 minutes for a sensor, back up.
Day 17
+6 days
06:05Shift handoff · Night to day06
Line 2 packer jamming on the 12-count again. Ran slow most of the shift.
08:40Operator message · Line 2 channel07
Same jam as before. Cartons coming out of the glue station skewed.
Day 11 mentions Line 2, but the filler, not the packer. Mentioning the same line is not enough to connect two records.
What AOI reconstructs
The same seven records as one equipment history: in order, grouped into episodes, with the work order in its place and every line traced to where it was written.
AOI / Histories / H-2207
IllustrativeLine 2 · Case packer
Recurring jam on the 12‑count
Status
Reported
D1 05:50
Workaround
D1 09:20
WO opened
D1 10:05
WO closed
D1 14:30
Reported again
D17 06:05
Episode 1 · Day 1
Jams overnight and on day shift. Infeed slowed as a workaround. Flap guide adjusted under WO-4471, which closed the same afternoon.
16 days after WO-4471 closed
Episode 2 · Day 17
The same jam on the same format, and a new detail: cartons skewed out of the glue station.
How the AOI demo works · Illustrative
The same two stages, on a packing line.
The interactive AOI demo works in two stages: first it turns each record into a structured event, then it connects related events into one history. Here are the same two stages applied to the case packer above.
01Structured events
One record, structured
As written
Day 17 · 08:40Operator message · Line 2 channel07
Same jam as before. Cartons coming out of the glue station skewed.
Case packer on Line 2 jamming again. Cartons leaving the glue station skewed.
- Entity
- Case packer
- Area
- Line 2
- Date
- Day 17 · 08:40
- Source
- Operator message
- Explicitly stated“Cartons coming out of the glue station skewed.”
- InferredThe case packer, and a repeat: posted in the Line 2 channel as “same jam as before”.
- UncertainWhether the glue station has anything to do with the jams.
Source kept · Operator message · Day 17 · 08:40
02Operational memory
Related events, one history
Entity history
Line 2 · Case packer
- Recurring
- 7 events
- 2 episodes
- 4 sources
Episode 1 · Day 15 events
- 01Shift handoff
- 02Operator message
- 03Work order
- 04Technician note
- 05Work order
Quiet 16 days, then activity resumed
Episode 2 · Day 172 events
- 06Shift handoff
- 07Operator message
Linked by entity and timing · each event keeps its source
Manufacturing demo · In development
A synthetic plant to explore, in development.
We are building a synthetic manufacturing environment for this page: shift handoffs, work orders, and technician notes you can follow from the first record to the reconstructed history. Until it is ready, the main AOI demo shows the same mechanics in a synthetic lab setting.
All demo information is synthetic.
What the records state, and what they don’t.
- Explicitly stated
The case packer jammed on both days.
Written in four records, two in each episode.
- Inferred
The Day 17 jams are the same issue as Day 1.
Same asset, same format, same symptom, 16 days apart.
- Uncertain
Whether the glue station is involved.
Mentioned twice. Never checked.
That last line is where your team starts. AOI puts it in front of them with the records attached. It doesn’t decide it for them.
What would your line history show?
We’re looking for a small number of manufacturers to test AOI against real shift, maintenance, and work order history.