Skip to content

Main content

Capacity Buffer Share Tool

Expose signed capacity overcommitment after an explicit reserve.

Loading tool…

Description

Subtract committed from positive capacity for uncommitted, then subtract reserved for freeAfterReserve.

Capacity accounting compares available supply with commitments, reservations, or demand. Negative residuals can expose overload while zero capacity requires a distinct undefined utilization state.

Subtract committed from positive capacity for uncommitted, then subtract reserved for freeAfterReserve.

When to use this tool

Use Capacity Buffer Share when you need a transparent resource or workload capacity term.

How to use the tool and how it works

  1. Enter capacity, committed, reserved. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read uncommitted, freeAfterReserve, bufferShare. Use the output convention below.

Subtract committed from positive capacity for uncommitted, then subtract reserved for freeAfterReserve. Divide that free amount by capacity for bufferShare.1

Input fieldMeaning and unitsAccepted input
capacityCapacityRequired. Finite number; strictly above 0.
committedCommittedRequired. Finite number; minimum 0.
reservedReservedRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
uncommittedUncommittedRequired. Finite number.
freeAfterReserveFree After ReserveRequired. Finite number.
bufferShareBuffer ShareRequired. Finite number.
json
{
  "input": {
    "capacity": 100,
    "committed": 70,
    "reserved": 10
  },
  "output": {
    "uncommitted": 30,
    "freeAfterReserve": 20,
    "bufferShare": 0.2
  }
}

Limitations and assumptions

  • Commitments and reserves are nonnegative but may exceed capacity, producing negative free capacity and share.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Validate calendars, skill constraints, and concurrent demand with the actual resource plan.

References

  1. Calculation and input contract: management/capacity-buffer-share — tool.io

Similar or alternative tools