SKIP TO CONTENT
1 / 25
Day1
Rate · % of plan90%
Days lost · plant0.0
Days lost · you0.0
Share of planned production rate achieved · as the line ranDashed line · planned rate 100%
100%50%0%
Day 1Day 8Day 15Day 22Day 30
The same line, the same month, twice

Same person, same month, same readings. The only thing that changed was what was on the board when the call was made.

  • What did not stop. With spiderAI™ the line ran through day twenty. Fourteen concerns, seven of them on one supply, and three months of repair history, weighed together, said nothing justified stopping the line.
  • What got ranked. The fourteen concerns went on the board one to fourteen, by what each one costs the line. Four were worked on the first shift. Ten ran on with a job card each.
  • What got named on day one. The three silent machines got an owner each and an answer due before shift end. Missing data stopped counting as health.
  • Who made the calls. The area head and the site head, both months. spiderAI™ writes the board and the decision rule. The person still decides, and with the board in order the same person decides better.
Source · the sintering use case · plant and machines from the iHz™ walkthrough
What this page does not claim ▾

The plant is illustrative. Its equipment names, register identities, areas and panels are the fictitious ones the iHz™ walkthrough uses, and no machine here names a real one. The month is real: the steel line shows it run at plan with spiderAI™, and the days lost in that month are not measured, so none are stated. Which register name carried each concern in the source month is placed by area for the story. Your months are simulated by two plain rules, marked where they apply.