Framework Explanations: Mapping the Stock and Flow Structure of Systems

Derived from an academic source (private repository).
MIT System Dynamics Group faculty. (2013). Mapping the Stock and Flow Structure of Systems (Assignment 3, 15.871 Introduction to System Dynamics). MIT Sloan School of Management.

Advanced Structural Mapping in System Dynamics

This resource details the fundamental frameworks and structures used to analyze complex systems, as outlined by the MIT System Dynamics Group (2013).

---

1. Stock and Flow Framework

Purpose

The primary lens for understanding system architecture, this framework distinguishes between the accumulated state of a system and the rates that change those states over time.

Components

• Stocks (Accumulations): Represented by rectangles; these hold the state of the system and provide it with memory (e.g., inventory, employees).
• Flows (Rates): Represented by "valves" on arrows; these indicate the speed at which stocks increase or decrease (e.g., production rate, attrition rate).
• Clouds (Sources/Sinks): Represent the boundaries where the model begins or ends.
• Information Links: Thin arrows that transfer data from stocks or constants to flows without transferring physical material.

How it Operates

Stocks integrate the net difference between inflows and outflows over time. A stock only reaches equilibrium when the sum of its inflows exactly matches the sum of its outflows ($Inflow - Outflow = 0$). In social systems, these concepts apply to "soft" variables like employee experience or customer trust as well as physical objects.

Textual Diagram Description

[Source/Cloud] ➔ ➔ [Inflow Valve] ➔ ➔ [[ STOCK BOX ]] ➔ ➔ [Outflow Valve] ➔ ➔ [Sink/Cloud]
(Note: Information links may loop back from the Stock to the Inflow or Outflow valves based on system rules).

---

2. Challenging the Clouds (Boundary Selection)

Purpose

A methodology used by modelers to critically evaluate the scope and boundaries of a system model.

Components

• The "Cloud": An icon representing an infinite source or sink of material outside the model's concern.
• Feedback Loops: Mechanisms that might connect a sink back to a source.
• System Boundaries: The conceptual perimeter defining what is endogenous (internal) versus exogenous (external).

How it Operates

The modeler "challenges" every cloud by asking if the source or sink is truly unlimited. If the outflow of a process impacts the availability of its future inflow (e.g., a "sink" of unhappy customers eventually reduces the "source" of new leads), the cloud must be replaced with a stock or a feedback link to accurately reflect the system's constraints.

Textual Diagram Description

A cloud icon with a question mark over it, pointing an arrow toward a flow valve:
? Cloud ? ➔ [Inflow] ➔ [[ Stock ]]

---

3. The TQM / PDCA Improvement Cycle

Purpose

A goal-seeking model derived from the Plan-Do-Check-Act (Deming) cycle, used to simulate how organizations identify and eliminate defects or process inefficiencies.

Components

• Actual State: The current level of defects or performance.
• Target/Goal: The desired performance level.
• Gap: The difference between the actual and desired state.
• Improvement Rate: The speed at which corrective actions reduce the gap.

How it Operates

This is a Balancing Loop. The system compares its current stock (e.g., Defect Density) against a goal. This comparison creates a perceived "gap," which triggers an improvement rate (the flow). As the improvement rate increases, the stock of defects decreases, eventually closing the gap and slowing the improvement efforts.

Textual Diagram Description

[Goal] ➔ (info) ➔ (Gap Calculation) ➔ (info) ➔ [Elimination Rate Valve] ➔ ➔ (Outflow from stock)
[[ Stock of Defects ]] ➔ (info) ➔ (Gap Calculation)

---

4. Multi-Stage Product Development Model

Purpose

To map the "pipeline" of knowledge work, demonstrating how delays and rework affect the time-to-market in engineering or product design.

Components

• Backlog/Concept Stock: Ideas or tasks waiting to be processed.
• Work-in-Process (WIP) Stocks: Tasks currently being engineered.
• Completion Flow: The rate at which tasks move from one stage to the next.
• Downstream Stocks: Finished designs or launched products.

How it Operates

This model functions as a series of connected stocks and flows. Each stage acts as a "buffer." Even if work starts immediately at the beginning of the chain, the physical structure of the pipeline ensures that the final stock reflects a delay, as each unit must pass through every intermediate accumulation.

Textual Diagram Description

[Idea Stock] ➔ [Development Flow] ➔ [[ Prototype Stock ]] ➔ [Launch Flow] ➔ [[ Marketed Product Stock ]]

---

Source

Full APA-7 Citation: MIT System Dynamics Group faculty. (2013). Mapping the Stock and Flow Structure of Systems (Assignment 3, 15.871 Introduction to System Dynamics). MIT Sloan School of Management.

Journal/Repository: MIT OpenCourseWare
Authors: MIT System Dynamics Group faculty
Year: 2013