That Day, Another Delivery Date Was Nailed to the Wall by Production
"A-Zhe, how did you run this schedule? This rush order, weren't we supposed to deliver it by Tuesday last week? It's already Thursday, and clients are calling non-stop!" The Production Control team leader stormed into my cubicle, visibly agitated. I looked up to see his face pale with fury, holding a report covered in red marks. To be honest, I've grown accustomed to this situation; it happens almost every one or two months. Every time, it's rush orders cutting in, machines breaking down, then production capacity instantly exploding, and delivery dates simply disappearing into thin air.
Where Exactly Does the Problem Lie?
Frankly, everyone is still using the crude method of Excel spreadsheets! Do you know how many machines we have on our production line? Just the etching machines alone number over a hundred, and each has different process times, mold change times, and maintenance schedules. Not to mention various material constraints, human resource allocations, and those eternally troublesome machine breakdowns. If you're simply calculating "how many pieces can be produced per hour," that's the logic of infinite capacity scheduling, which completely disregards whether machines are available or if there are enough materials.
So the key point is, what we need is "Finite Capacity Scheduling (APS)"! It doesn't just look at capacity, but at "actual bottlenecks." It takes into account:
- Machine Constraints: Is this machine currently available? Or is it running another order?
- Material Constraints: Do we have enough wafers on hand? Are we waiting for an upstream process?
- Labor Constraints: Does the midnight shift only have two people managing three machines?
- Tooling Constraints: Are special fixtures or photomasks currently occupied by another order?
In other words, APS acts like a super-smart superintendent; it considers all limitations and then tells you "when this batch of goods can be shipped at the earliest," rather than "when it can be shipped under ideal circumstances."
How Is It Actually Done?
Our factory later implemented an APS system, and initially, there were various growing pains. But its core logic is actually very simple: it's "scheduling backward from the due date."
- Set Delivery Target: Assume the customer requires this batch of goods to be shipped by Friday at 3 PM.
- Backward Schedule the Last Step: Before shipment is final testing, which requires 8 hours. So, testing must begin by Friday at 7 AM at the latest.
- Backward Schedule the Prior Step: Before testing is grinding, which requires 6 hours. So, grinding must begin by Thursday at 9 PM at the latest.
- Check Resources: At this point, APS will check: is the grinding machine available at Thursday 9 PM? Is there enough labor? If available, it schedules it. If not available—for example, if the grinding machine is occupied by another rush order until Friday 3 AM—then the system will tell you: "Sorry, this batch cannot be delivered by Friday 3 PM; the earliest it can ship is Friday 9 PM."
Of course, this is a simplified example. An actual system would consider hundreds or thousands of work orders, hundreds of machines, and various complex priorities. For instance, our VIP customer orders might have a priority of 100 in the system, while general customer orders might be 50. When two orders compete for the same machine, the system will naturally prioritize the VIP order.
The Most Common Pitfalls
When we first implemented APS, the most common pitfall we encountered was "inaccurate data." I recall one time, the system generated a schedule indicating a certain batch of goods could be delivered two days early. Production control was thrilled and quickly informed the customer. What happened? Just as the goods arrived at the etching machine, it was discovered that the engineer responsible for that machine had incorrectly set its maintenance schedule, making the machine unusable! This batch of goods was consequently delayed by three full days.
Simply put, no matter how powerful an APS system is, it only operates based on the data you feed it. If your:
- Inaccurate Process Times: For example, if it actually takes 3 hours, but you input 2 hours.
- Inaccurate Machine Status: For example, if a machine is broken, but you still set it as available.
- Inaccurate Material Inventory: For example, if the system shows 100 pieces, but there are actually only 50 pieces.
Then the resulting schedule is garbage. The system will give you a seemingly perfect answer, but it's practically impossible to execute. Therefore, whether an APS system can truly be effective largely depends on your data maintenance capabilities.
One Thing You Can Do Today
Check whether your production line's "machine status" data perfectly matches reality.