Description
Use min(delayDays, totalFloat) for consumedFloat, max(0, totalFloat - delayDays) for remainingFloat, and the reverse excess for unabsorbedDelay.
Schedule differences use a common time coordinate and may preserve negative slack or lead times. A scalar lag or float term does not recalculate a full dependency network.
Use min(delayDays, totalFloat) for consumedFloat, max(0, totalFloat - delayDays) for remainingFloat, and the reverse excess for unabsorbedDelay.
When to use this tool
Use Milestone Delay Float Consumption when you need one explicit scheduling or delay-budget component.
How to use the tool and how it works
- Enter delayDays, totalFloat. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read consumedFloat, remainingFloat, unabsorbedDelay. Use the output convention below.
Use min(delayDays, totalFloat) for consumedFloat, max(0, totalFloat - delayDays) for remainingFloat, and the reverse excess for unabsorbedDelay.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| delayDays | Delay Days | Required. Finite number; minimum 0. |
| totalFloat | Total Float | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| consumedFloat | Consumed Float | Required. Finite number. |
| remainingFloat | Remaining Float | Required. Finite number. |
| unabsorbedDelay | Unabsorbed Delay | Required. Finite number. |
{
"input": {
"delayDays": 3,
"totalFloat": 5
},
"output": {
"consumedFloat": 3,
"remainingFloat": 2,
"unabsorbedDelay": 0
}
}Limitations and assumptions
- This is one delay against a supplied float allowance; network dependencies, calendars, and concurrent delays are not recalculated.
- 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
Use a complete dependency plan and working calendar to assess critical paths, resource constraints, and completion forecasts.
References
Similar or alternative tools
- Work Item Slack To Promised Date
Subtract forecastFinish from promisedAt for signed slack.
- Critical Ratio Remaining Work Days
Divide signed daysToDue by positive remainingWorkDays for criticalRatio and subtract remaining work from days to due for slackDays.