The bottom line: In die-driven manufacturing, a machine running at 100% OEE with the wrong die is still a quality problem. ProAlert tracks production targets and scrap thresholds at the cavity level... so your OEE metrics always reflect what tooling is actually in the press, not just that the press is running.

The Die vs. Machine Disconnect

Generic OEE platforms track performance at the machine level. For stamping and molding operations, machine-level metrics hide the actual quality and efficiency story.

Machine OEE is a blended average that masks tooling-specific problems.

A 16-cavity die running at 94% quality looks acceptable in a machine-level OEE system. But if cavity 7 is responsible for 80% of the rejects, you'll never see it unless your quality system attributes scrap to the specific cavity that produced it.
Production targets vary by die, not by machine.

The same press running a high-cavity die produces dramatically more parts per minute than when running a prototype single-cavity die. If OEE targets don't change when the die changes, every run compares actual output against the wrong benchmark.
Scrap thresholds should follow the tooling, not the machine.

Acceptable scrap rates differ between a production die running automotive components and a prototype die doing first-article runs. A machine-level threshold that works for one is wrong for the other... leading to either missed quality signals or constant false alarms.
Die changeover cost is invisible in most OEE systems.

Die changeover time is captured as downtime in generic OEE systems, but the cost attributed to each die change... tooling setup labor, line downtime cost, and changeover frequency... is never analyzed at the die level. You can't optimize what you can't see.

Die Scheduling and Run Management

ProAlert schedules production at the tooling level, not just at the machine and product level. Operators select the active die at run start... which drives the correct OEE targets and cavity attribution for the entire run.

Capability	How It Works
Die-Driven Scheduling UI	Production schedule entries include die and tooling assignment alongside machine and product. Supervisors schedule by tooling, not just by output. Scheduling UI accessible from web and mobile.
Die/Tool Selection on Production Start	Operators select the active die or tooling at the EdgeSense touchscreen or mobile app before starting a run. Selection drives OEE performance targets, scrap thresholds, and cavity attribution for the full run duration.
DieRun CRUD and Finalization	Each die run is a first-class record: created at run start, updated continuously as cycles accumulate, and finalized at run end. Finalized runs are immutable records for tooling history and ROI (Return on Investment) analysis.
Die Changeover Cost Analysis	Changeover time and labor cost recorded per die change event. Reports show changeover frequency, average duration, and cost per die... enabling data-driven decisions on tooling investment and changeover optimization (SMED).
Tooling Product Type	Tooling-driven product types are classified separately from standard products in scheduling and OEE calculation. Prototype runs, first-article runs, and production runs each carry different threshold configurations.
Die-Grouped Mobile Guidance	Mobile app displays production guidance grouped by active die, including cavity layout, acceptable ranges, and operator instructions. Technicians on the floor see tooling-specific information, not generic machine procedure. The play button on a scheduled die run either activates the run or names the documents blocking it.
The Die Record Itself	A die asset carries a tooling card: the presses it is linked to, its cavity sets, its condition, its meters, and a hit count derived over a date range. Die and tooling images fall back to the CMMS asset photo where no dedicated die photo exists.
Changeovers Raise Themselves	Finalizing a shift raises the changeover work orders its adjacent die runs imply, named by the registered CMMS identity: "Changeover: X to Y". Run positions are counted from one, so a description reads "run 1" and matches the schedule rather than being off by one against it.
Co-Products on One Die	A die producing several products updates the live count for every co-product per cycle, scaled by the summed cavities and preserving scrap, so a progressive die's output is attributed rather than averaged.

Cavity-Level Scrap Control

Every scrap entry is attributed to the specific die cavity that produced it. Thresholds are configured at the cavity level. Violations trigger instant notification and enter an approval queue.

Cavity Scrap Threshold Monitoring

Scrap thresholds configured per die cavity. When a specific cavity exceeds its acceptable reject rate, the alert fires at the cavity level... not as an undifferentiated machine-level scrap event. Cavity 7 failures are tracked separately from Cavity 12 failures.

Cavity and Source Attribution

Every scrap entry records the originating die cavity. Pareto analysis of scrap by cavity reveals which tooling positions are contributing disproportionately to reject counts. Targeted corrective action at the cavity level instead of rebuilding the entire die.

Instant Scrap Email Notifications

Email notification fires the moment cavity scrap exceeds the configured threshold... not at the end of the shift, not in the next morning's report. Quality teams can respond to an emerging cavity problem while the die is still in the press.

Scrap Threshold Approval Queue

Scrap events above threshold are placed in a supervisor approval queue. The run can continue only after a supervisor reviews the violation and approves continuation or initiates a die pull. Approval actions are logged with timestamp and supervisor identity for audit purposes.

Violation Approval Workflow: Every threshold violation generates a structured approval record: cavity ID, scrap count, threshold value, time of violation, and the supervisor's disposition (Approve Continue, Pull Die, or Reduce Run). Corrective action notes are attached to the violation record. The complete history is available for quality audits and die repair analysis.

ProAlert defect heatmap for a four cavity door panel insulator die, showing the die plate with defect counts drawn over each cavity pocket and a By Cavity breakdown reading LH Rear 34, RH Front 9, LH Front 7 and RH Rear 5 out of 55 total defects — **Fifty-five rejects on one die in a fortnight, and thirty-four of them came out of the same pocket.** The grid is drawn over the tool itself, so the hot corner is a place a toolmaker can walk to: LH Rear, bottom left, 62% of everything the die scrapped. At the machine level all of this is one scrap figure against one press, with nothing in it to act on. The breakdown on the right says what kind of reject as well as where... LH Rear took 20 of the die's 24 die-cut-short and 9 of its 12 web wrinkles, which is the signature of a worn pocket rather than a bad batch of felt.

Kanban and Tooling Source Tracking

Kanban Workflow

Visual Kanban board for die and tooling work-in-process management. Track die status across stages: In Storage, Staged, In Press, In Maintenance, and Awaiting Repair. Every die has a current state visible to scheduling and maintenance teams.

Diagram Editor with GPS Markers

Visual floor layout editor with GPS (Global Positioning System) coordinate markers for die storage locations and press assignments. Maintenance teams can locate a specific die in the die room without calling the tool crib.

CMMS Photo Fallback

Die and tooling records display the dedicated die photo when available. When no dedicated die photo exists, the system automatically falls back to the CMMS asset photo for the associated machine. No broken image placeholders.

ProAlert die record for DIE-DP-2401, a four cavity steel rule die, showing the press it runs on, a hit count of 5,958 over ten production runs in the last fortnight, wear at 82,400 of 100,000 cycles, its maintenance dates, its cavity set and the die plate photo — **The tool's own record, with the press it runs on and the wear that decides when it comes out.** 5,958 hits since August 24, counted from the ten production runs the die actually ran rather than typed in by a toolmaker, and 82,400 of 100,000 cycles of wear on an amber bar. Last PM August 2, next due September 27, and a link straight to FL1-PRESS-002 and to the cavity heatmap above. The plate on the right is the CMMS fallback doing its job: this die carries no dedicated photo of its own, so the record draws the asset photo instead of leaving a hole.

How Die-Driven OEE Calculation Works

In die-driven mode, ProAlert's OEE engine substitutes die-level targets and thresholds for the generic machine-level defaults at the moment the operator selects the active die.

OEE Component	Standard Mode	Die-Driven Mode
Availability	Machine downtime vs. planned run time	Same calculation, but changeover time is attributed to the specific die change event rather than generic unplanned downtime
Performance	Actual cycles vs. machine's rated cycle target	Actual cycles vs. the cycle target configured for the specific die... a 16-cavity die has a different PPH (Parts Per Hour) target than a 4-cavity die on the same press
Quality	Good parts vs. total parts at machine level	Good parts vs. total parts with cavity attribution... Quality score reflects the per-cavity scrap configuration, and cavity-level violations are visible within the composite Quality metric
Composite OEE	Availability x Performance x Quality at machine level	Same formula, but all three inputs use die-level configurations. OEE for the run reflects the actual tooling in the press at every moment of the shift

Generic OEE vs. Die-Driven OEE

Generic Machine-Level OEE

OEE targets fixed to the machine regardless of tooling in the press
Scrap tracked at machine level... no cavity attribution
Die changeover treated as generic unplanned downtime
No die scheduling... schedule is product and machine only
No cavity-level scrap thresholds or approval workflows
Die storage location and status managed in separate spreadsheet

ProAlert Die-Driven Manufacturing

OEE targets adjust automatically when the operator selects the active die
Every scrap unit attributed to the specific cavity that produced it
Die changeover time and cost tracked at the die change event level
Schedule entries include die and tooling assignment alongside machine
Per-cavity thresholds trigger instant email and approval queue
Kanban board shows every die's current state from storage to press

See cavity-level scrap control and die-driven OEE in a live demo.

Book a 30-minute demo... we'll walk through die selection, cavity threshold configuration, and the scrap approval workflow on actual stamping line data.

Schedule a Demo