Description
Expand a booking interval by supplied setup and cleanup buffers.
Project records separate planned effort, recorded time, forecast assumptions, resource buffers and role authority. A probability-weighted impact is one scenario term, and a calendar-day shift is not a business-calendar calculation. Local progress and workload shares need consistent scope and periods before broader interpretation.
Expand a booking interval by supplied setup and cleanup buffers.
When to use this tool
Use Resource Booking Cleanup Buffer when you already have bookingStart, bookingEnd, suppliedSetupBefore, suppliedCleanupAfter and need to expand a booking interval by supplied setup and cleanup buffers.
How to use the tool and how it works
- Enter bookingStart, bookingEnd, suppliedSetupBefore, suppliedCleanupAfter. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read blockedStart, blockedEnd, totalBlockedDuration. Use the output convention below.
Require bookingEnd>=start and nonnegative buffers; blockedStart=start-setup, blockedEnd=end+cleanup and duration=end-start+setup+cleanup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| bookingStart | Booking Start | Required. Finite number. |
| bookingEnd | Booking End | Required. Finite number. |
| suppliedSetupBefore | Supplied Setup Before | Required. Finite number; minimum 0. |
| suppliedCleanupAfter | Supplied Cleanup After | Required. Finite number; minimum 0. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| blockedStart | Blocked Start | Required. Finite number. |
| blockedEnd | Blocked End | Required. Finite number. |
| totalBlockedDuration | Total Blocked Duration | Required. Finite number. |
{
"input": {
"bookingStart": 100,
"bookingEnd": 160,
"suppliedSetupBefore": 10,
"suppliedCleanupAfter": 15
},
"output": {
"blockedStart": 90,
"blockedEnd": 175,
"totalBlockedDuration": 85
}
}Limitations and assumptions
- Time coordinates may be signed; no reservation conflict, actual resource availability, required buffer or safe procedure is checked.
- 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
Reconcile the complete plan, resource calendar, costs and action history for an operational question. Use the actual business calendar or delegated-role documentation when required, rather than treating one supplied offset or Boolean as that full workflow.
References
Similar or alternative tools
- Task Planned Actual Effort Multiplier
Compare actual task hours with a positive planned-hours reference.
- Project Risk Explicit Impact Product
Calculate a supplied probability-weighted project impact.