In one line: To know whether a system can hit a rate, lay out every operation against time, decide which can overlap, and find the chain that sets the cycle. That turns a capacity argument into arithmetic.
Core idea
Marketing promises a rate; engineering has to prove the machine can deliver it. A timing diagram (elapsed time on one axis, operations on the other) shows each step’s duration, which steps must happen in sequence, and which can run concurrently. The longest unavoidable sequential chain, the critical path of a repeating cycle, sets the throughput. Everything else has slack.
How it works
The program’s team exercise models an automated critical-dimension scanning electron microscope, a metrology tool that measures features on semiconductor wafers. Sales says the market needs 80 wafers per hour, or 45 seconds per wafer. The engineering configuration includes:
- a wafer pod and external robot
- a two-wafer load lock with its vacuum pumping
- an internal robot and a wafer pre-aligner
- an X-Y-Z stage that moves, acquires and measures at 10 sites per wafer
- the electron microscope column
Method:
- List every operation from the functional flow (see Functional Flow Block Diagram).
- Estimate each duration from research, data sheets and physics: pump-down time, robot moves, stage settling, image acquisition.
- Mark dependencies: what must finish before what can start?
- Overlap what can overlap. For example, pump the next wafer in the load lock while the current one is being measured.
- Find the repeating bottleneck chain and compare it with 45 seconds.
- Pick at least two more systems engineering methods (such as requirements, risk analysis or trade studies) to support the conclusion, and brief it in ten minutes.
The answer is rarely just “yes” or “no.” Usually it identifies which subsystem must get faster, such as stage settling or pump-down, or which operations must be pipelined to close the gap.
In practice
The same reasoning applies wherever rate matters: test stations, production lines, data pipelines and even meetings. It is also an exercise in leadership, because the team must defend its estimate to an inter-department review where marketing, engineering and management all have stakes in the answer. The course warns against over-engineering it. A few hours of disciplined estimation beats weeks of precise modeling of the wrong thing.
Questions to ask yourself
- What rate has my product or process been promised, and has anyone checked it with a timing diagram?
- Which operations in my process could overlap but currently run in sequence?
- Is our bottleneck a fundamental limit or a design choice?
Connections
- Built from: Functional Flow Block Diagram. Same logic as: Theory of Constraints, Value Stream Mapping.
- Process context: Systems Engineering Process. Defends a: specification.
- Capabilities exercised: Decision Making, Connecting Across Disciplines, Communicating and Advocacy.
Sources
- Course team exercise on timing diagrams for an automated wafer-metrology tool; no public source.
- NASA (2007) Systems Engineering Handbook [1]