WaterfallAllocation
Allocates each period's demand across a set of capacity-limited tiers in priority order: the first tier fills to capacity, the excess spills to the next, and anything left after the last tier lands in an Overflow column. It takes two tables, one listing the tiers with their names and capacities and one holding the demand by period, and returns the demand table's columns plus one allocation column per tier and Overflow.
Inputs
| Input | Accepts | Required |
|---|---|---|
Tiers | Table | Yes |
Demand | Table | Yes |
DemandColumn | Text | Yes |
Outputs
| Output | Produces |
|---|---|
Result | Table |
Settings
Typed in on the node or set by the assistant, not wired.
| Setting | Default | Notes |
|---|---|---|
CapacityColumn | Capacity | Column in the Tiers table holding each tier's per-period capacity. Default Capacity. |
NameColumn | Name | Column in the Tiers table holding each tier's name; these names become the output columns. Default Name. |
RankColumn | — | Optional numeric column that sets fill priority (lowest rank fills first). Leave blank to fill tiers in row order. |
Example
Three plants with monthly capacity (Plant_A 10,000 units, Plant_B 6,000, Plant_C 4,000) in a Plants table with Name and Capacity columns, and a MonthlyDemand table with a Units column. Set the demand column to Units. March's 17,500 units allocate as 10,000 / 6,000 / 1,500 with zero overflow; April's 22,000 fills all three plants and shows 2,000 in Overflow, the demand you cannot serve without more capacity. A stacked BarChart of the tier columns makes the fill order obvious.
Tips
Capacity is per period: the tiers reset every row of the demand table, so this models recurring capacity (production, coverage), not a one-time pool being drawn down. Use RankColumn when priority differs from the row order of the Tiers table.