Description
Divide effort by available hours times utilization for durationDays.
Capacity accounting compares available supply with commitments, reservations, or demand. Negative residuals can expose overload while zero capacity requires a distinct undefined utilization state.
Divide effort by available hours times utilization for durationDays.
When to use this tool
Use Task Effort Duration Utilization Crosswalk when you need a transparent resource or workload capacity term.
How to use the tool and how it works
- Enter effortHours, availableHoursPerDay, utilizationFraction. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read durationDays. Use the output convention below.
Require nonnegative effortHours, positive availableHoursPerDay, and utilizationFraction in (0, 1]. Divide effort by available hours times utilization for durationDays.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| effortHours | Effort Hours | Required. Finite number; minimum 0. |
| availableHoursPerDay | Available Hours Per Day | Required. Finite number; strictly above 0. |
| utilizationFraction | Utilization Fraction | Required. Finite number; maximum 1; strictly above 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| durationDays | Duration Days | Required. Finite number. |
{
"input": {
"effortHours": 12,
"availableHoursPerDay": 8,
"utilizationFraction": 0.5
},
"output": {
"durationDays": 3
}
} Limitations and assumptions
- This is a constant-capacity effort model, not a working-calendar schedule; dependencies, interruptions, multiple workers, and uncertainty are omitted.
- 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
Similar or alternative tools
- Workload Allocation Over Capacity
Return positive excess above capacity and allocated/capacity as utilizationFraction.
- Project Buffer Task Share
Return buffer/(buffer+task) as bufferShareOfCombined and buffer/task as bufferToTaskRatio.