06A212a - OOS - account for resource calendars and leveling delays - Githubissues

AronGahagan / cpt-dev

Code repository for the ClearPlan Toolbar

https://www.ClearPlanConsulting.com

3 stars 1 forks source link

06A212a - OOS - account for resource calendars and leveling delays #304

Closed AronGahagan closed 1 year ago

AronGahagan commented 1 year ago

Request:

Account for resource calendars and leveling delays.

Todo:

[x] assign this issue
[x] label the issue for enhancement or bug
[x] label the issue with codemodule (so fixes can be aggregated and hotfixed together)
[ ] checkout appropriate branch and create topic branch
[ ] design, code and test
[ ] update codemodule x.y.z
[ ] update CurrentVersions.xml manually
[ ] commit changes prefix comment with Issue #XXX -
[ ] merge topic into appropriate branch(es) and push
[ ] delete topic branch

AronGahagan commented 1 year ago

Notes:

Task Leveling Delay affects Task Start Date (for FS; affects Task Finish for FF, etc.)
Assignment Leveling Delay does not affect Task Start date, but does affect time-phased work and Task Finish Date.
Resource Calendar affects Task Start Date if a single resource.
Need to get earliest available work day (and time) on successors with assignments to reset the Target Date used for comparison. Can use oResource.Calendar.Period(dtDate).Working which returns boolean. Then get start (or finish?) time of Calendar.Period(dtDate).Shift1.Start.

AronGahagan commented 1 year ago

Hold on...there is no situation where a leveling delay or a resource calendar alone would cause a successor date to be prior to a predecessor's - that does not happen without a lead, constraint, or actual date. This is a wontfix.