Examples
Examples
Try the starting example
- Tasks [required working days,zero-based predecessors]; enter JSON
- [[2,[]],[2,[0]]]
- Project start ISO date
- 2026-11-01
- No-work ISO dates; enter JSON
- ["2026-11-02"]
- Interchangeable crews (count)
- 1
- User delay cost (USD/calendar day)
- 100
- Revised task calendar (JSON)
- [[1,1,["2026-11-01","2026-11-03"],"2026-11-04"],[2,1,["2026-11-04","2026-11-05"],"2026-11-06"]]
- Calendar delay versus same task plan with no exclusions (days)
- 1
- Scenario delay cost (USD)
- $100.00
Try another scenario
- Tasks [required working days,zero-based predecessors]; enter JSON
- [[3,[]],[2,[0]]]
- Project start ISO date
- 2026-11-01
- No-work ISO dates; enter JSON
- ["2026-11-02","2026-11-04"]
- Interchangeable crews (count)
- 1
- User delay cost (USD/calendar day)
- 120
- Revised task calendar (JSON)
- [[1,1,["2026-11-01","2026-11-03","2026-11-05"],"2026-11-06"],[2,1,["2026-11-06","2026-11-07"],"2026-11-08"]]
- Calendar delay versus same task plan with no exclusions (days)
- 2
- Scenario delay cost (USD)
- $240.00
Calculation method
Calculation method
Revised task calendar (JSON)
Topological input-order tasks take earliest-free crew; start after predecessors; consume required days excluding listed no-work dates; end date is next calendar day.
Calendar delay versus same task plan with no exclusions (days)
Difference between final revised and no-exclusion finish dates.
Scenario delay cost (USD)
Calendar delay×entered daily delay cost.
Symbols and units
- a
- Tasks [required working days,zero-based predecessors]; enter JSON
- b
- Project start ISO date
- c
- No-work ISO dates; enter JSON
- d
- Interchangeable crews (count)
- e
- User delay cost (USD/calendar day)
Use the units shown. A list keeps the order in which you enter its values. The symbol ^ means “raised to the power of”.
Assumptions & limits
Assumptions & limits
- Work-day task calendar skips exactly user-entered no-work dates; weekends remain working unless listed. Tasks can pause across excluded dates. Supported limits: All numeric inputs and computed intermediates must remain finite. Supported numeric input magnitude is zero or 1e-12 through 1e12 in absolute value; reject values outside this bounded range. All lists/JSON record tables are limited to 100 records unless a stricter bound is stated; reject malformed record arity and wrong member types. Acyclic <=100 tasks, each integer workdays1..30; <=366 excluded dates; crews1..20; all dates valid.
Are these inputs private?
These calculations run in your browser. A shared link contains the values you choose to share. Only questions submitted to the separate AI finder are sent to OpenAI.