Erbend ERFOLD setup & safety checklist for sheet-metal folding (OSHA point-of-operation safeguarding): two-gate readiness before production ramp

When you’re commissioning a sheet-metal folding setup, setup speed and safeguarding have to be treated as one system. Use this ERFOLD setup & safety checklist for sheet-metal folding (OSHA point-of-operation safeguarding) as a two-gate pre-ramp method: Gate 1 verifies your ERFOLD receipt steps and machine data dependencies, and Gate 2 verifies that point-of-operation safeguarding behaves correctly during changeover.

Erbend ERFOLD setup & safety checklist for sheet-metal folding (OSHA point-of-operation safeguarding): two-gate method

Gate 1: Data readiness (program and tooling inputs)

• Receipt steps load correctly, with the correct bend type, tool station, beam direction/folding direction, and positions.
• Backgauge and axis references match your real setup so you’re not forced into repeated manual re-entry.

Gate 2: OSHA point-of-operation safeguarding verification (presence sensing and guard coverage)

• Presence-sensing devices protect the operator at the point of operation as intended, including proper safety-distance behavior and correct response when the sensing field is interrupted.
• Any areas not protected by the sensing field are covered by other guarding (guards for all entry areas not protected by the presence-sensing device).

Running Gate 1 and then Gate 2 helps you isolate what’s a programming/data issue versus what’s a safeguarding alignment or guard-coverage issue—especially after staged upgrades.

ERFOLD step/receipt programming checks (bend sequence, bend type, and required data)

In ERFOLD Basic, the receipt/step structure is the backbone of changeover consistency. Erbend describes building a receipt by entering job basics (material type, sheet thickness, length) and then defining an unlimited number of steps. Each step can include the bend type (angle/radius/hemming), tool station, backgauge position, folding angle, upper beam up/down positions, and (where needed) radius-bending and hemming values.

For your checklist, treat each ERFOLD step like a row on a setup sheet: complete, consistent, and aligned to the way the job is actually folded on your machine.

• Receipt header matches the actual job: Confirm material type, sheet thickness, and length match what you’re feeding. If those fields are off, downstream bend behavior and positional data can become inconsistent.
• Step sequence matches your real bend logic: Verify the bend sequence by step (and by side). If the job includes bends on multiple sides, confirm each side’s bend sequence is programmed as its own set so you’re not relying on memory.
• Bend type selection is correct for each step: For every step, confirm the bend type matches what you intend to run (normal bend, radius, hemming). On the ERFOLD side/bend workflow, the control is set up so bend process types can be defined per side.
• Tool station is not left to chance: Confirm the tool station selection is populated correctly on every step. This is a common changeover error point because the “wrong tool/station” can still look plausible on a quick scan.
• Folding direction and upper beam up/down positions make sense: Validate folding angle plus the upper beam up/down position(s) per step—especially on jobs that mix bend directions.
• Radius and hemming values are present when needed: For radius/hemming steps, confirm the required radius/hemming values are actually populated and correspond to the drawings and your tooling approach.

Practical example for your team: If one step is supposed to run a hemming process but the bend type (or hemming-open/closed choice) isn’t correct, you often only discover it after you’ve already cycled—resetting and re-running data. Gate 1 is designed to catch that on the screen before the machine sees material.

Tool, station, and backgauge/axis data sanity check to reduce setup iterations

Programming correctness is necessary, but not sufficient. Setup delays commonly come from axis reference habits and tooling/parameter context not being “fresh” for the job.

Use this manager-focused data sanity checklist before the first real bend run:

• Axis referencing method is documented and followed: Erbend describes referencing all axes at once with one button or referencing each axis individually. Decide which method your shop uses and make sure it’s consistent during changeover.
• Tool menu/database inputs are current for the job: Confirm the tool list/definitions used in ERFOLD match what’s mounted on the machine for this receipt.
• Bending database/auto correction context isn’t stale: If your workflow uses bending database settings for auto angle correction against sheet springback, confirm those assumptions are aligned to the job’s material type/thickness/length.
• Backgauge positions are feasible with your mounted tooling: Even if the step includes a backgauge target, verify it’s reachable within your physical setup (mounted tooling, stops, and real travel) before first run.
• Manual axis movement is used for calibration/tool change—not as a workaround: Use manual control intentionally for the actions it’s meant for (calibration and tool change operations), not as an open-ended substitute for fixing wrong step data.

If you want one “changeover discipline” metric, track how many back-and-forth corrections are needed before the part meets spec. It’s a fast way to see whether tool/station and axis data hygiene is improving.

Up-down folding workflow and handling verification (keeping operators out of pinch-point zones)

On up-down folding architectures, the handling pattern can change the real pinch-point locations operators may approach. Erbend’s DUAL MFA 4225 describes a system designed to reduce manual placement (including a vacuum unit for sheet loading) and it highlights ergonomic advantages of up-down forming.

That doesn’t remove the need for safeguarding validation—so keep ergonomics as an input to your setup risk review.

• Defined hands-free approach points exist: Confirm where operators stand and where hands will be during step changes and the active bend window.
• Assisted handling doesn’t create new hazards: Vacuum loading, transfer tables, pivoting parts, and unloading can introduce pinch zones during transfer/unloading if guarding isn’t verified across the full motion envelope.
• Presence-sensing coverage matches the operator interaction zone: If assisted handling changes where hands go during setup and changeover, your point-of-operation sensing validation has to follow that reality.
• Training covers recovery actions: Ensure operators know what to do when a sensing-field interruption stops the machine, and what not to do inside the hazard area during troubleshooting.

OSHA point-of-operation safeguarding with presence-sensing devices (what to validate in your facility)

OSHA’s presence-sensing device guidance is written for press/press-brake point-of-operation safeguarding. In OSHA’s terminology, these are commonly referred to as light curtains, and they’re designed to stop normal stroking when the operator’s hands are in the point of operation.

Core OSHA checks you can convert into buyer questions

• Behavior when the sensing field is interrupted: Presence-sensing devices are designed to automatically stop the stroke when the sensing field is interrupted, protecting operators and other employees in the area.
• Compatibility constraint: OSHA notes presence-sensing devices cannot be used on machines using full revolution clutches.
• Interlock into the control circuit: The PSD should be integrated so slide motion stops if any part of the operator’s body is within the sensing field at that time.
• Guard coverage for areas not inside the sensing field: Guards must protect all areas of entry to the point of operation that aren’t protected by the presence-sensing device.
• PSD is not used to initiate motion: OSHA notes PSDs can’t be used as a tripping means to initiate slide motion.
• Failure handling behavior: If a failure occurs, normal stopping action should still apply, but the system should prevent the start of the next stroke until the failure is corrected, and the failure should be indicated.

Muting validation during setup (if your process uses it)

OSHA describes that muting/bypassing of the PSD during the upstroke can be permitted for parts ejection, circuit checking, and feeding. In OSHA’s press-brake example, the light curtain is muted when the die is no more than 1/4 inch above the workpiece, allowing stock to bend while the operator moves through the light plane without stopping the slide.

Safety distance validation

OSHA requires that the safety distance from the sensing field to the point of operation must be greater than the distance determined by the safety distance formula.

Oregon OSHA adds a practical view of safety distance as a calculation using maximum approach speed and total stopping time, and it notes stopping time is normally measured using a brake monitor or a portable stop-time measurement device.

How to translate this into Gate 2 tests

• Alignment test: Validate that the sensing field is aligned to the actual hazard zone created by your tooling and part geometry.
• Interruption test: In the correct setup mode, interrupt the sensing field during the conditions where your safeguarding design requires stopping, and confirm the machine responds as intended.
• Muting test: If muting is part of your operation, validate muting behavior in the feeding and ejection scenarios your procedure actually uses.
• Failure handling test: Validate that failures prevent the next stroke until corrected and that failure indication is visible to the operator/team per your commissioning approach.

OSHA’s eTool also includes examples where improperly adjusted light curtains resulted in worker exposure—so treat presence sensing as something you validate again during changeovers, not as “set-and-forget.”

And if you’re planning a safety upgrade cycle, it’s worth noting that industry coverage continues to highlight active press/press-brake guarding evolution—for example, Fabricating & Metalworking reported on the Wintriss Controls Group acquisition of ISB, including expanded press and press brake guarding and light curtain solutions.

Validation tests, operator training, and a practical go/no-go ramp plan

After Gate 1 and Gate 2 checklists are complete, use a go/no-go plan that keeps the ramp controlled.

Gate 1 go/no-go: data readiness

• Load the correct receipt and confirm receipt header fields match the job.
• For each ERFOLD step, verify bend type, tool station, backgauge position, folding angle, and upper beam up/down positions are populated and consistent with your setup expectations.
• Perform a dry run or single-cycle verification in your intended setup mode, without entering the hazard area for “coaching” or re-entry workarounds.

Gate 2 go/no-go: safeguarding verification

• Verify PSD protection behavior by interrupting the sensing field during conditions where stopping is required.
• Validate safety distance and stopping-time assumptions as designed/commissioned for your machine and tooling configuration.
• If muting is used, validate muting behavior in your actual feeding/ejection scenarios.
• Confirm any point-of-operation entry areas not protected by the sensing device are covered by other guarding.

Operator training package to complete before ramp

• How to run the setup mode and single-cycle verification steps safely.
• What to do if the machine stops due to a sensing-field interruption.
• Who owns tool change verification and axis reference confirmation.
• Documentation of signoffs for Gate 1 and Gate 2.

Only then is it appropriate to ramp into production mode—starting with a short first-article run plan and expanding step count/cycle rate after you verify part quality stability.

If you want a second set of eyes on your current ERFOLD changeover workflow, bottlenecks, material flow from load to fold to unload, and whether your safeguarding validation plan matches your real changeover rhythm, reach out through the contact form below. We can review your setup and go/no-go path together.

Sources

• Erbend ERFOLD Basic (Line-by-Line / Step-Based Software)
• OSHA eTool: Presence-Sensing Devices (Presses)
• Oregon OSHA: Machine Safeguarding at the Point of Operation (Guide)