FabTime Cycle Time Management Newsletter Abstracts

FabTime Cycle Time Management Newsletter Abstracts - Volume 22 (2 issues, in progress)


10 Recommendations for Fab Cycle Time Improvement (Issue 22.02)

Welcome to Volume 22, Number 2 of the FabTime Cycle Time Management Newsletter. In this issue we have a few links from Jennifer’s LinkedIn, but no other announcements. Our software tip of the month is about using FabTime to identify possible instances of soft dedication in the fab. We have subscriber discussion about WIP Utilization %, sending SMS email to Japanese cell phones, breaking up maintenance events, managing SPC in a shared fab environment, and paying off technical debt.

Our main article was inspired by the many reports we’ve seen and heard lately of fabs facing capacity and cycle time challenges. We’ve spent 20+ years thinking and teaching about ways to improve cycle time for existing fabs. We’ve always closed our cycle time course with a list of our top ten recommendations. Most of these have been covered in past newsletters, but we thought there would be value in a single article that describes all ten. We hope you find these recommendations useful.



On Breaking Up PMs and Other Unavailable Periods (Issue 22.01)

Welcome to Volume 22, Number 1 of the FabTime Cycle Time Management Newsletter. This is the first issue of 2021. In this issue we have an announcement about our new FabTime user interface, a call for papers for the TSIA Joint Symposium, a quick announcement about delivery of sessions of our cycle time management course, and a couple of news links from Jennifer’s LinkedIn.

One of the main topics of our course, downtime, particularly scheduled downtime, is the primary theme of this month’s issue. Our software tip of the month is about using our new Green-to-Green charts (G2G) to identify cases where you might be grouping PMs. In our main article, we discuss why grouping PMs isn’t a good idea for cycle time, and why G2G is a useful metric for monitoring downtime instances. We also have subscriber discussion about dedicating weekends to maintenance events, analyzing failures for time-of-day patterns, and comparing OEE across fabs.