{"id":8763,"date":"2026-08-26T08:23:42","date_gmt":"2026-08-26T06:23:42","guid":{"rendered":"https:\/\/www.taktiq.de\/?p=8763"},"modified":"2026-08-26T08:23:54","modified_gmt":"2026-08-26T06:23:54","slug":"why-cycle-time-alone-does-not-ensure-stable-assembly","status":"publish","type":"post","link":"https:\/\/www.taktiq.de\/en\/blog\/why-cycle-time-alone-does-not-ensure-stable-assembly\/","title":{"rendered":"Why Cycle Time Alone Does Not Ensure Stable Assembly"},"content":{"rendered":"\n
<\/div>\n\n

In assembly, cycle time is often considered the key metric that determines the line\u2019s rhythm. It specifies the interval at which a product must leave the line in order to meet customer demand within the available production time. However, this does not necessarily mean that a line is running stably. This article explains why that is the case and what really determines stability. <\/p>\n\n

How the Cycle Time Is Derived From Customer Demand<\/h2>\n\n

The cycle time is calculated by dividing the available production time by the customer demand quantity:<\/p>\n\n

\"\"<\/figure>\n\n

It is crucial that both figures cover the same reference period. If demand is specified per shift, the available production time per shift is also taken into account, that is, the gross shift time minus all scheduled interruptions, such as breaks or planned downtime. <\/p>\n\n

Given 450 minutes of net shift time and a demand of 150 products per shift, the result is:<\/p>\n\n

t<\/mi>T<\/mi><\/mrow><\/msub>=<\/mo>450<\/mn> <\/mtext><\/mtext>min<\/mi><\/mrow><\/mrow>150<\/mn> <\/mtext><\/mtext>pcs<\/mi><\/mrow><\/mrow><\/mfrac>=<\/mo>3<\/mn> <\/mtext><\/mtext>min<\/mi><\/mrow><\/mtext>pcs<\/mi><\/mrow><\/mfrac><\/mrow>t_\\mathrm{T} = \\frac{450\\ \\mathrm{min}}{150\\ \\mathrm{pcs}} = 3\\ \\frac{\\mathrm{min}}{\\mathrm{pcs}}<\/annotation><\/semantics><\/math><\/div>\n\n

This means that a finished product must leave the line every three minutes. The cycle time thus describes the target rhythm of the entire system and the basic assembly time available at each station. <\/p>\n\n

In practice, however, this time can rarely be filled 100 percent with assembly work. Distribution times, organizational non-productive time, or customer-specific requirements reduce the portion that can actually be utilized, which is represented by the usable cycle time ratio. The effectively usable cycle time of a workplace is calculated from the cycle time, the usable cycle time ratio, and the reciprocal of the relevant order portion: <\/p>\n\n

t<\/mi><\/mtext>eff<\/mi><\/mrow><\/msub>=<\/mo>t<\/mi>\u00d7<\/mo>\u03b7<\/mi>\u00d7<\/mo>1<\/mn>a<\/mi><\/mfrac><\/mrow>t_\\mathrm{eff} = t \\times \\eta \\times \\frac{1}{a}<\/annotation><\/semantics><\/math><\/div>\n\n

A workplace with a cycle time of 120 seconds, a utilization rate of 95 percent, and only 50 percent of relevant orders would thus yield the following calculation:<\/p>\n\n

120<\/mn><\/mspace>s<\/mtext>\u00d7<\/mo>0,95<\/mn>\u00d7<\/mo>1<\/mn>0,5<\/mn><\/mfrac>=<\/mo>228<\/mn><\/mspace>s<\/mtext><\/mrow>120\\,\\text{s} \\times 0{,}95 \\times \\frac{1}{0{,}5} = 228\\,\\text{s}<\/annotation><\/semantics><\/math><\/div>\n\n

Because there is no work to be done at this station in half of the cycles, more schedulable capacity is available for each relevant order. Whether this capacity can actually be utilized on the product depends on the specific line and work organization. <\/p>\n\n

Cycle time should be distinguished from the actual processing time: it is the actual time required for a work cycle at a station, which varies depending on the variant, the worker, or material availability. Cycle time sets the framework, while the actual processing time shows the extent to which the actual processing utilizes that framework. <\/p>\n\n

Whether a line operates smoothly therefore depends on how the work is distributed within that framework.<\/p>\n\n

Why the Average Gives a Misleading Picture of Utilization<\/h2>\n\n

In an idealized assembly process, every product would be identical and every station would operate with consistent utilization. In production lines with many variants, this is never the case. One variant may require a great deal of effort at one station, yet hardly any at another. As a result, capacity utilization fluctuates from order to order. This fluctuation is called time spread, and it encompasses the entire distribution of times, not just the minimum and maximum. What matters is not only how high the maximum utilization is, but also how often each level of workload occurs. <\/p>\n\n

\"\"<\/figure>\n\n

This is precisely where a common misconception lies. The average utilization of a workplace may be below its available capacity, yet the line may still operate erratically. This is because products do not move through the line as an average, but as specific orders in a specific sequence. If several time-intensive variants arrive one after another at a workplace that is already heavily loaded, delays occur, even though the average remains unremarkable. <\/p>\n\n

This fluctuation results in two effects. If too little work is assigned to a station, idle time results, which goes to waste as unused capacity. If more work is assigned than can be handled within the cycle time, the cycle time is exceeded. The \u201ctime spread ratio\u201d serves as a key metric for evaluating such overruns. It quantifies the extent and frequency with which orders exceed a workplace\u2019s available capacity, thereby serving as a direct indicator of time spread. <\/p>\n\n

\n
\n\n\t
\n\t\t
\n\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\tDr. Nils Hellmuth<\/span>\n\t\t\t\t\t\t\t\tAcademic Collaboration Manager<\/span>\n\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"TAKTIQ\"\n\t\t\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t\t\t\t\t\t<\/cite>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t<\/span><\/a>\n\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t<\/div>\n\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

\u201eWith a cycle time of 180 seconds, variant A takes 130 seconds, variant B takes 175 seconds, and variant C takes 220 seconds. On average, the three options take about 175 seconds, which is below the cycle time. Variant A still results in 50 seconds of idle time, and Variant C exceeds the cycle time by 40 seconds. \u201c<\/p>\n\t\t\t\t<\/div>\n\t\t\t<\/div>\n\t\t<\/blockquote>\n\t<\/div>\n\n<\/div>\n<\/div>\n\n

Idle times and time spread ratio are thus two sides of the same coin. The greater the time spread, the greater the tension between peak workloads and unused capacity. A single outlier can usually be accommodated through organizational measures. If such deviations occur regularly, the work distribution no longer matches the actual variant mix. This is precisely where line balancing comes into play. <\/p>\n\n

Line Balancing for Stable Lines With a Fixed Cycle Time<\/h2>\n\n

Line balancing assigns tasks to workplaces on the line and determines which worker performs which tasks at which station<\/a>. A task is the smallest meaningful unit of work that can be scheduled: a completed task with a planned standard time that specifies how long a worker needs to complete it. This standard time can be determined using established time-management methods; TAKTIQ supports MTM and MODAPTS, and will support REFA in the future. <\/p>\n\n

Several tasks together form an order, that is, a single product to be manufactured in a quantity of 1. Depending on the model and variant, an order contains different tasks, the sum of which determines the assembly effort required for the product. In high-variety production lines, line balancing must therefore do more than simply distribute work evenly: it must take into account time spread, idle times, time spread ratio, and the frequency of individual variants. <\/p>\n\n

An obvious solution is max line balancing. In this approach, the line is designed so that even the most time-consuming variant fits within the cycle. This provides reliability, but comes at the cost of idle time, since all the less time-consuming variants leave capacity unused. <\/p>\n\n

Mixed line balancing, on the other hand, considers the actual distribution of work loads across the variant mix. Instead of designing each station for the worst-case scenario, it distributes the work loads in such a way that idle times are reduced and the time spread ratio remains manageable. What matters then is no longer whether a single variant temporarily exceeds capacity, but whether this load can be planned and managed within the overall system so that the line runs stably and efficiently given the actual order mix. <\/p>\n\n

The transition from max line balancing to mixed line balancing is the key lever<\/a>. It only becomes effective when combined with other mechanisms. <\/p>\n\n

The first is intentionally limited drift. Drift occurs when a worker cannot complete an order entirely within the scheduled cycle time and finishes a part of the work in the following cycle. Station boundaries are not viewed as rigid in this context, but are controlled through a defined drift limit. This limit determines how far into the next station an order may be processed before planned drift turns into a drift limit violation. Drift is therefore not automatically a bad thing, nor is it synonymous with overload; rather, it is a planned tool for accommodating time-intensive variants, as long as it remains controlled and is balanced out over other cycles. <\/p>\n\n

\"\"<\/figure>\n\n

The second mechanism is sequencing. It determines the order in which products move through the line. If several complex variants follow one another in quick succession, this creates peaks in workload. If, on the other hand, variants with high and low labor content are strategically combined, the time spread can be reduced over the order sequence. Sequencing rules systematically limit such peaks: For example, they specify how often a complex variant may appear within a defined order sequence (density rules) or which variants should not follow one another directly (neighborhood rules). Our article on sequencing rules explains<\/a> how these rules work in detail. <\/p>\n\n

Another concept is the Vario Cycle. While the classic cycle is based on equal time intervals between products, the Vario Cycle uses variable cycle times: Products requiring more work are allotted more time, while those requiring less work are allotted correspondingly less. This relaxes the rigid output logic. Especially when a fixed cycle leads to excessive idle time, significant time spread ratio, or a constant need for support, the Vario cycle can be an interesting alternative, depending on the line\u2019s logic. <\/p>\n\n

\n
\n\n\t
\n\t\t
\n\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\tDr. Nils Hellmuth<\/span>\n\t\t\t\t\t\t\t\tAcademic Collaboration Manager<\/span>\n\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"TAKTIQ\"\n\t\t\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t\t\t\t\t\t<\/cite>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t<\/span><\/a>\n\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t<\/span><\/a>\n\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t<\/div>\n\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

\u201eIn the end, it’s not just the cycle time that counts. It sets the time frame within which the work at each station must be completed, but whether a line runs smoothly depends on line balancing. \u201c<\/p>\n\t\t\t\t<\/div>\n\t\t\t<\/div>\n\t\t<\/blockquote>\n\t<\/div>\n\n<\/div>\n<\/div>\n\n

Frequently Asked Questions About Production Planning<\/h3>\n\n
\n\n\t\n\t
\n\n\t\t \n\t\t
\n\t\t\t