Scheduling Transformer and Coil Winding Around the Impregnation Cycle

A transformer plant's throughput is set by its impregnation vessels, and any schedule that models those vessels as daily hours instead of daily loads will promise two or three times the units the plant can produce. EDGEBIC by User Solutions treats the vessel as a one-job-per-day work center, pools the winding machines that can take the same coil, and times core and coil work to the tank build that consumes it.

Coil winding is the visible work. The vessel is the constraint. Getting the second one right is what makes the plan match the floor.

The Vessel Sets the Ceiling

Vacuum pressure impregnation is a batch process. Load, draw down, fill, hold, drain, cure. Whether the cycle is eight hours or fourteen, the vessel is committed and often stays committed for the balance of the day once the load is set.

A scheduler that sees sixteen daily hours will pack three loads into one vessel. The floor does one. Flag the vessel as a one-job-per-day work center and each vessel unit accepts a single load per day. Two vessels means two slots a day, roughly forty a month, and that is the plant's real ceiling. Most shops have never written that number down.

Once the ceiling is in the plan, upstream work is timed to feed a slot and downstream work is timed off one. The oversold weeks show up months ahead rather than at the end of the month. The same batch modeling pattern appears in heat treating furnace scheduling.

For a one-off Saturday cycle, use a daily capacity override on that single work center and date instead of changing the permanent calendar.

Pooling the Winders

Winding machines are rarely identical but often overlapping. Three machines can take a given coil, one runs it faster, one can also take the large units. The routing usually names one, so jobs queue on it while the others sit.

Bind the winding step to a work center group containing the machines that can genuinely take the work. At schedule time the engine expands the group, compares each member's projected finish against live load, and places the job on the one that gets it done first. Members carry their own efficiency factor, so a faster machine is modeled as faster rather than averaged. Jobs already running stay on the machine running them.

Where a large unit physically requires one specific machine, leave that step bound to it and pool only the interchangeable work. The general behavior is described in routing a job to a backup machine when the primary is full, and a neighboring winding-shop pattern in coiler pools for spring manufacturing.

Core and Coil as a Feed

Core stacking, coil winding, and assembly of the core and coil set have to be complete before tanking begins. Scheduled as an independent order, that work finishes whenever it finishes and the tank bay waits.

Model core and coil as a sub-assembly feeding the tanking step. The engine schedules it to complete before the parent build starts, and when it cannot, the parent moves rather than opening a tank for parts that are not ready. See how a sub-assembly feeds its parent job and, for larger structures, building a multi-level assembly routing.

Add queue time where a step genuinely has to sit, for example a bake or a cool-down. Queue time is a shift-aware buffer placed after the operation and before the successor may start, so a twelve-hour bake lands as twelve real hours on the calendar.

Backward From the Promised Date

Transformer orders carry hard dates: a substation outage window, a project milestone, a utility delivery slot. Forward scheduling from now says when a unit could finish. Backward scheduling from the promised date says when winding has to start and whether the vessel has a slot.

Schedule backward and the units that fit are confirmed, while the ones that do not are flagged with the step that could not be placed. On a vessel-constrained plant that step is almost always impregnation, which tells you precisely where to spend. See forward versus backward scheduling.

A Worked Month

Two vessels, one cycle each per day, 20 working days.

The plant is oversold by four vessel loads and nothing else is close. That is a specific, actionable answer: add four weekend cycles, or move four units into next month, or fund a third vessel. Without the one-job-per-day rule the plan would have shown the vessel at 55 percent utilization and pointed at nothing.

Tracking Actual Cycles

Operators log start, stop, and quantity at a shop floor station. Impregnation cycles that consistently run longer than standard show up in the logged data, which is what you use to correct the standard. Completed operations are never moved by a reschedule, so replanning mid-month leaves the record of what already cured exactly as logged while the rest of the month reflows.

Heritage in Electrical Equipment Manufacturing

User Solutions has built finite capacity scheduling since 1991, more than 35 years, for manufacturers of heavy electrical and mechanical equipment: US Navy, GE, BAE Systems, and Cummins across 33 locations. The lineage behind EDGEBIC, including the RMDB heritage, drove GE Railcar on-time delivery from 30 percent to 90 percent in an environment of long builds and batch-constrained processes. A transformer plant with two vessels and forty promises a month is that same constraint problem.

Where to Start

Flag your vessels as one job per day, pool your interchangeable winders, link core and coil as a feed to tanking, and schedule the next quarter backward from the promised dates. The count of flagged units in month one is your real capacity gap, and it will be a smaller and more specific number than the one currently being argued about.

For fundamentals, what is production scheduling is the plain-language start and why the bottleneck sets the pace covers the constraint logic. The industry fit guide maps neighboring sectors and EDGEBIC is the product hub. Ready to write down your real monthly ceiling? Contact US for a demo.