Capacity is often presented as a commodity table: model name, memory, price. That is useful as far as it goes, but production decisions need more context than a SKU can carry.
A team needs to know where the offer is, how stable it has been, whether it is interruptible, and what the rate means at the moment of launch.
The table is the control
We treat the capacity board as an operational surface, not a catalog page. Sorting and filtering are not decoration; they are the shortest path between a workload’s constraints and an available machine.
That requires a disciplined vocabulary. Rates are integer cents. Reliability has a defined window. Supplier details stay behind the abstraction while the facts a customer can act on stay visible.
Fewer surprises, earlier
- Publish the dimensions that change a launch decision.
- Keep the offer fresh and mark stale information instead of silently presenting it as current.
- Make the next action — configure, reserve, review — part of the same surface.
The right abstraction does not erase complexity. It puts complexity in the place where a decision can use it.