Bottleneck Throughput

flowchart LR
START(["START"])
END(["END"])
READ1["#9733; 1 #183; O1 #9733;"]
READ2["2 #183; E1"]
START ==> READ1 ==> READ2 ==> END
classDef default fill:#f2f5f3,stroke:#285c4c,color:#202c29
linkStyle default stroke:#285c4c,stroke-width:4px

flowchart LR
subgraph SO["Ontological"]
direction LR
N1["<b>#9733; 1 #183; O1 #9733; Primary view</b><br/><br/>The limiting required stage bounds sustained flow#59; it does not guarantee that output#46;<br/><br/>In a specified serial flow where each completed unit must pass every required stage#44; sustained throughput cannot exceed the lowest effective stage capacity for the same product mix and horizon#59; demand#44; outages and coordination can make actual output lower#46;<br/><br/>Every completed unit consumes capacity at each mandatory stage#46; Over a sustained interval#44; a stage cannot process more than its effective capacity without depleting previously accumulated inventory or changing the model#46; Finite buffers and variability can reduce realized throughput further#46;<br/><br/>Conditions#58; A process has a specified output measure and operating horizon for evaluating flow constraints#46; The specified serial route requires each output unit to pass every modeled stage in comparable flow units#46; Capacity and output are compared over the same sustained horizon with product mix#44; yield and opening inventory effects accounted for#46;"]
class N1 primary
class N1 ontological
end
style SO fill:#ffffff,stroke:#c5cec8,color:#202c29
subgraph SE["Epistemic"]
direction LR
N0["<b>2 #183; E1</b><br/><br/>Test the limiting#45;stage hypothesis against flow evidence and alternatives#46;<br/><br/>Evaluate a proposed bottleneck against comparable flow#44; capacity#44; queue and idle#45;time observations#44; testing demand#44; starvation#44; blocking and product#45;mix alternatives#59; revise the diagnosis when conditions or constraints shift#46;<br/><br/>High utilization or a queue alone does not establish a system bottleneck#46; Comparing capacity with demand and explaining blocked or starved time distinguishes competing accounts#59; a diagnosis can remain conditional when relevant observations are missing#46;<br/><br/>Conditions#58; A process has a specified output measure and operating horizon for evaluating flow constraints#46; A candidate flow model specifies routes#44; units#44; horizon#44; product mix and the proposed constraint#46; Relevant flow#44; demand#44; capacity and queue or idle#45;time observations are available with stated uncertainty to compare competing explanations#46; Material opening and closing inventory changes#44; yield losses and rework are accounted for or bounded sufficiently to compare capacity and output over the same horizon#46;"]
class N0 epistemic
end
style SE fill:#ffffff,stroke:#c5cec8,color:#202c29
classDef ontological fill:#e6f0fa,stroke:#829fba,color:#202c29
classDef epistemic fill:#f8e8e8,stroke:#bd9195,color:#202c29
classDef decision fill:#e8f2e8,stroke:#91ab8c,color:#202c29
classDef primary stroke:#285c4c,stroke-width:4px
classDef rationale fill:#fff8e8,stroke:#aa9366,stroke-dasharray:5 3,color:#202c29
classDef neutral fill:#f2f2f2,stroke:#929b96,color:#202c29
linkStyle default stroke:#7f8983,color:#202c29