Menu
Standard Work Combination Table: Sequencing Manual, Machine, and Walk Time

Standard Work Combination Table: Sequencing Manual, Machine, and Walk Time

Learn how to build a standard work combination table, mapping manual, machine, and walk time against takt, with a worked example and column-by-column guidance.
Standard Work Combination Table: Sequencing Manual, Machine, and Walk Time

A standard work combination table is the Toyota Production System document that plots each operator step against time, distinguishing manual work, automatic (machine) time, and walking, so you can see whether a single worker's cycle fits inside takt.

It is one of the three core standardized work forms, sitting alongside the process capacity sheet and the standardized work chart. Where a simple time study lists tasks, the combination table layers three different kinds of time onto one timeline and lines them up against the takt bar.

That visual overlap is what exposes waiting, overburden, and dangerous overlaps between a person and a running machine.

What the table actually captures

The purpose of the combination table is to answer one question: can one operator complete a full cycle, on foot, across the assigned machines, within the takt time? To do that it separates three time categories that most stopwatch studies blur together.

  • Manual time: the hands-on work an operator performs, such as loading a part, clamping, deburring, or inspecting. The operator is actively doing something.
  • Machine (auto) time: the interval a machine runs on its own after the operator presses start. The operator is free during this window and can walk to the next station.
  • Walk time: the seconds spent moving between machines or positions. Walking adds nothing to the product, so it is a prime target once the sequence is stable. A spaghetti diagram is the natural companion for attacking it.

Manual and walk time are drawn as solid or continuous lines; machine auto time is drawn as a dashed line running in parallel, because the operator has already moved on. The moment the two lines separate is where the operator gets free hands, and that is where the next task should begin.

The columns, and how to fill each one

A standard layout carries one row per work element and a set of fixed columns. Fill them in this order:

  1. Step number and description: break the cycle into discrete elements at natural stopping points (part touches down, button pressed, gauge reads). Keep elements small enough to time cleanly.
  2. Manual time: record the observed hands-on seconds for the element, taken as the repeatable low time across several cycles, not the fastest freak result.
  3. Auto time: enter the machine's own run time for elements that involve a machine cycle. Leave it blank for purely manual steps.
  4. Walk time: the seconds to reach the position where the next element happens.
  5. Time graph: the right-hand plotting area where each element is drawn to scale, manual and walk as solid, auto as dashed, so the cumulative cycle builds left to right against a vertical takt line.

The takt line is the whole point of the graph. Takt equals available production time divided by customer demand. If your cumulative operator line crosses the takt line, the cell cannot keep up and the sequence must change. Standardized work like this is a prerequisite for stable overall equipment effectiveness, because you cannot improve a cycle you have not first made repeatable.

A worked example

Assume available time of 27,000 seconds per shift (7.5 hours after breaks) and demand of 450 units. Takt time is 27,000 divided by 450, which equals 60 seconds per unit. One operator tends two machines, M1 and M2.

  • Element 1: load M1, manual 8s.
  • Element 2: start M1, then walk to M2, walk 3s. M1 auto time is 40s, running in the background.
  • Element 3: unload finished part from M2, manual 6s.
  • Element 4: load M2, manual 9s.
  • Element 5: start M2, walk back to M1, walk 4s. M2 auto time is 35s.
  • Element 6: unload M1 (its 40s auto has finished during elements 3 to 5), manual 7s.

Operator hands-on plus walking equals 8 + 3 + 6 + 9 + 4 + 7, which is 37 seconds . That comfortably fits inside the 60-second takt, so one operator can run both machines with 23 seconds of margin per cycle.

The dashed auto lines confirm neither machine finishes late: M1's 40s starts after element 1 and ends before element 6, and M2's 35s starts after element 4 with room to spare.

If demand rose and takt fell to 35 seconds, the 37-second operator cycle would break the takt line, and you would rebalance, shorten walk paths, or add a second operator.

Reading the results and rebalancing

Once plotted, the table makes three failure modes obvious. First, operator overburden : the solid line crosses takt, meaning the person physically cannot finish in time. Second, operator waiting : a long dashed auto line with no manual work stacked against it means the operator stands idle watching a machine.

Third, a person-and-machine collision , where the manual line overlaps an auto line on the same machine, a safety red flag that the operator is reaching into a running cycle.

Rebalancing usually means resequencing elements so the operator does useful work during someone else's auto time, trimming walk distance, or shifting an element to an adjacent operator. This is disciplined kaizen, and it pairs naturally with a broader value stream mapping effort and the improvement rhythm of the PDCA cycle .

When you standardize the winning sequence, you also feed the theory of constraints conversation by revealing which station is truly pacing the line.

Common mistakes when building one

  • Timing to the average instead of the repeatable low. Standardized work should reflect a reliably achievable time, not a best-case sprint or a padded average.
  • Ignoring walk time. Teams often log manual and auto time but treat walking as free. On multi-machine cells, walking can be a fifth of the cycle.
  • Forgetting the auto line runs in parallel. If you add machine time to operator time as if it were sequential, you will conclude a feasible cell is impossible.
  • Building it once and framing it. The table is a living baseline. Any layout, tooling, or demand change resets takt and invalidates the old sequence.

Where Fabrico fits

A combination table is only as honest as the time data behind it. Fabrico is the real-time data foundation that keeps those numbers current instead of frozen in a stopwatch study from last quarter.

Its real-time OEE and production monitoring captures actual machine cycle and run times on the floor, and its computer vision can read machines with no PLC, so even older equipment reports its real auto time.

When you rebalance a cell, Fabrico shows whether the new sequence actually holds up against live output rather than a whiteboard assumption.

On the maintenance side, machine auto times only stay stable if the equipment does. Fabrico's field-ready CMMS handles work orders, assets, preventive scheduling, and spare parts, so a drifting cycle time can be traced to a maintenance cause and fixed at the root.

For the underlying concepts, our guides on what a CMMS is and autonomous maintenance give operators the context to keep standardized work standing. Fabrico is EU-built with EU data residency.

Frequently Asked Questions

How is a standard work combination table different from a standardized work chart?

The combination table is a time-based graph: it plots manual, auto, and walk time against takt to prove a cycle fits. The standardized work chart is a layout-based diagram, drawn on the cell floor plan, showing the operator's walk path, standard work-in-process, and safety or quality checkpoints. You typically build the combination table first to confirm timing, then draw the chart to document the physical movement.

Do I need machine auto time if the process is entirely manual?

No. If no machine runs on its own during the cycle, the auto column stays empty and the table simply sequences manual and walk time against takt. The auto line matters when an operator tends machines that run unattended, because that free window is exactly what lets one person cover several stations.

How often should the table be updated?

Revisit it whenever takt changes (demand shifts or available time changes), whenever the cell layout or tooling changes, and whenever a kaizen alters the sequence. Treat it as a baseline that improvement moves forward, not a document you complete once. Live monitoring makes these triggers visible rather than something you discover weeks later.

Ready to build combination tables on real machine times instead of stale stopwatch data? Book a Fabrico demo and see how live OEE and CMMS data keep your standardized work honest.

Latest from our blog

Define Your Reliability Roadmap
Validate Your Potential ROI: Book a Live Demo
Define Your Reliability Roadmap
By clicking the Accept button, you are giving your consent to the use of cookies when accessing this website and utilizing our services. To learn more about how cookies are used and managed, please refer to our Privacy Policy and Cookies Declaration