Scheduling Wire Harness Assembly With Overlapping Operations

A wire harness shop wins its lead time in the overlap between cutting and assembly, and the schedule has to model that overlap explicitly rather than assuming each step waits for the one before it to finish. EDGEBIC by User Solutions lets a downstream step start once a defined transfer batch of leads is ready, routes crimp work only to certified operators, and counts harness boards as real finite positions rather than unlimited bench space.

Harness and cable assembly sits between electronics and fabrication. The routing is long, the volumes are moderate, and most of the calendar is spent waiting for a batch that is already mostly done.

The Waiting Is the Lead Time

Take a 900-lead harness. Cut and strip runs four days. Crimp runs two. Board assembly runs three. Test and pack runs one. Scheduled strictly in sequence that is ten days, and for most of the first four days the assembly bench is empty while leads pile up in a bin.

The floor already knows better. Assemblers start pulling leads as soon as a decent stack exists. The plan simply never said so, which means the promised date was three days later than the shop could actually deliver.

Lot streaming makes that overlap explicit. Set a transfer batch on the cut step, say 150 leads, and the successor is allowed to start once that batch is ready. The rest of the leads keep flowing behind it. See what is lot streaming for the concept and lot streaming overlap walkthrough for the mechanics with numbers.

If the leads need staging or kitting between operations, add a transfer delay so the schedule carries that lag instead of pretending the handoff is instant. The related electronics pattern is covered in lot streaming for electronics.

Boards Are Finite, Even When They Look Like Bench Space

A harness board is a physical fixture. You have six of them, or twenty, and a build occupies one for its whole duration. A scheduler that models the assembly area as a pool of labor hours will happily start ten concurrent builds against six boards.

Model the board area as a work center whose units are the real number of boards. Each build consumes one unit for its duration, and the engine will not place more concurrent builds than positions exist. When a build cannot claim a board on its planned day, it moves to the next opening and the date says so. That single change usually explains most of the gap between the plan and what the floor actually manages.

If some boards can only run some assemblies, split them into a work center group whose members are the boards that can take the job, and bind the routing step to the group. The engine expands the group at schedule time and picks the member that finishes soonest.

Crimp Certification Is a Real Constraint

Crimp quality is inspected, and in aerospace and defense harness work the operator has to be signed off on the tool and terminal. Treating every set of hands as interchangeable is how a plan promises work that legally cannot be done on the shift it was placed in.

Model the certification as a skill, assign it to the operators who hold it, and require it on the crimp step. The scheduler places that step only in a shift where someone with the skill is rostered. If the certified crimper is out for a week, take them off the roster and reschedule: the crimp steps move to days that are covered, and any harness that can no longer make its build date is flagged. Completed work is never moved by that reschedule. Yesterday's finished harnesses stay recorded exactly as logged. The pattern is the same one described in operator certifications for welding shops.

You can also pin a specific build to a specific operator when a customer requires it, and that pin survives every later reschedule.

Cure, Potting, and Overmold

Overmold, potting, and epoxy steps do not consume labor while they cure, but they do consume calendar. Queue time on the step handles that: it is a shift-aware buffer placed after the operation and before the successor may start, so an overnight cure lands as real elapsed time. If the cure runs as a fixed daily oven cycle instead, model the oven as a one-job-per-day work center so it takes one load per unit per day.

Either way the downstream step lands on the correct morning and the ship date includes the cure rather than quietly deleting it.

A Worked Order

A 900-lead harness with a transfer batch of 150 on the cut step.

Ten sequential days become five. No new machines, no overtime, one field on one routing step. The gain is real because the waiting was never real work.

Tracking What Actually Happened

Operators log start, stop, and completed quantity at a shop floor station. Those actuals feed the plan, so a cut step running slower than standard pushes only the work that has not started. The plan you print in the morning and the plan the floor is running stay the same document. Partial completions carry forward correctly, which matters on a four-day cut step that spans a weekend: see how partial completions carry forward.

Heritage in Defense and Electrical Assembly

User Solutions has built finite capacity scheduling since 1991, more than 35 years, including work for the US Navy, GE, BAE Systems, and Cummins across 33 locations. The lineage behind EDGEBIC, including the RMDB heritage, handled the Nimitz refit at more than 26,000 tasks, an environment where certification and sequence both had to be right. Harness work for regulated customers is the same shape at a smaller scale.

Where to Start

Pick your longest harness. Put a transfer batch on the cut step, set your board count as real units, add the one or two crimp certifications that actually gate work, and reschedule. Compare the new promised date to the old one before you change anything else.

For background, what is production scheduling is the plain-language start. The industry fit guide maps neighboring sectors and EDGEBIC is the product hub. Ready to find the waiting in your longest routing? Contact US for a demo.