Short answer: In-die sensors help stop a paeh progresif before a misfeed, slug, lifted strip, missing part, or short feed damages tooling or ships bad parts. They should be discussed in the RFQ for high-volume, tight-tolerance, plated, or safety-related bagian dicitak where one missed event can create expensive sorting or tool repair.
Many paeh progresif quotes mention production rate and tool maintenance but do not state what the die will detect. For a simple low-risk part, that may be acceptable. For terminals, clips, brackets, shields, or parts with critical forms, the buyer should ask what is monitored and what happens when a fault is detected.
Use this guide with the paeh progresif design checklist, strip layout guide, tooling maintenance audit checklist, and containment plan template.
Sensor points to discuss
| Risk | Possible detection | Buyer question |
|---|---|---|
| Short feed or misfeed | Feed progression or pilot detection. | Will the press stop before die closure damages the strip or tool? |
| Slug pulling | Slug detection, air blow monitoring, or chute sensor. | How are slugs prevented from returning to the die or part? |
| Bagian not ejected | Bagian-out sensor or chute confirmation. | How is a missing or stuck part detected before the Salajengna stroke? |
| Form height or tab presence | In-die or post-die check depending on geometry. | Which CTQ features are error-proofed instead of only sampled? |
When sensors are worth specifying
Sensors add cost and maintenance, so they should match the risk. A washer may not need complex monitoring. A plated terminal with a tiny formed kontak, a safety bracket, or a part that can damage an assembly line may justify more error-proofing. The decision depends on volume, tool complexity, downstream cost, and how easily defects can be found later.
The buyer should ask the panyadia to identify the highest-risk failure modes during DFM. Feed errors, strip lift, broken punches, slug marks, missing features, part carryover, and sensor bypass rules should be discussed before the die is approved.
Do not treat sensors as a replacement for process control
A sensor can stop a press, but it does not by itself define tool maintenance, inspection frequency, or defect containment. If a sensor trips repeatedly, the panyadia still needs a reaction plan. Who reviews the event? Is product since last good check quarantined? Is the die inspected before restart?
This connects directly to the control plan checklist, SPC guide, and panyadia corrective action guide. Error-proofing is strongest when sensor logic, maintenance, and inspection records are aligned.
RFQ details to include
- Bagian drawing, strip layout if available, CTQ features, and annual volume.
- Known historical defects: misfeed, slug pulling, short shot, bent tab, missing pierce, or part carryover.
- Required sensor points, or a request for the panyadia to propose sensor points.
- Press type, feed direction, coil width, material thickness, and production speed expectations.
- Reaction plan when a sensor trips, including containment quantity and restart approval.
- Whether sensor status, downtime, and fault history must be recorded.
- Spare sensor, maintenance, and validation requirements for long-running tools.
Approval evidence
During tryout, ask for evidence that the key sensors work. This can include simulated faults, first article notes, part-out confirmation, and maintenance checks. If a sensor can be bypassed, the bypass rule should be controlled and logged. Otherwise a good design can become weak during a production rush.
Kirim high-volume paeh progresif RFQs through the kontak page. If you have photos of past slug marks, mixed parts, or die damage, include them in the RFQ form so sensor and error-proofing requirements can be reviewed early.
The buyer should also ask how sensor changes are handled after launch. A replacement sensor, timing adjustment, or bypass jumper can change protection level. For critical programs, the maintenance record should show what changed, who approved it, and whether any production lot needed containment after the adjustment.
For panyadia audits, ask to see examples of sensor fault records and reaction logs, not only a statement that sensors exist. A short sample of downtime history can show whether faults are rare and controlled or frequent and ignored. That evidence is more useful than a photo of a sensor mounted in the die.
FAQ
What are in-die sensors used for?
They detect risks such as misfeed, short feed, slug pulling, strip lift, stuck parts, missing features, or failed ejection before defects or tool damage continue.
Does every paeh progresif need sensors?
No. Sensor requirements should match part risk, volume, die complexity, defect cost, and whether later inspection can reliably catch the failure.
What should happen when a sensor trips?
The press should stop, the cause should be checked, suspect product should be contained, and restart should follow an agreed reaction plan.
What sensor details belong in the RFQ?
Include CTQ features, failure history, volume, strip layout, desired detection points, reaction plan, data logging needs, and maintenance expectations.