The late units is associated with the late dates. The early units are associated with the early dates. Do you understand the forward and backward pass that the schedule algorithm performs when determining dates ?The forward pass begins at the project start date (if the project has not yet started) or a the data date and goes forward in time from the data date and takes into consideration the activity logic, durations, calendars and any hard constraint dates and computes the EARLY start and EARLY finish dates. Based on where you are on your project (as far as progress is concerned) as of the data date this is the EARLIEST that activities can start or finish.The backward pass begins at the project completion date (or the project must finish by date) and backward forward in time and takes into consideration the activity logic, durations, calendars and any hard constraint dates and computes the LATE start and LATE finish dates. Based on where you are on your project (as far as progress is concerned) as of the data date this is the LATEST that activities can start or finish.So think of the late dates as due by dates. In your case the Late dates are earlier in time than the early dates. This means that you are behind schedule and that you will missed the due by dates. In other words you are scheduled LATE DATES to be done by Dec 2015. However due to your lack of progress your project is now projected to be done EARLY DATES on AUG 2016. as far as the units stacking up on the data date if these are LOE activities you will have to assign a resource curve to the resource to get it to distribute the manhours.
The late units is associated
The late units is associated with the late dates. The early units are associated with the early dates. Do you understand the forward and backward pass that the schedule algorithm performs when determining dates ?The forward pass begins at the project start date (if the project has not yet started) or a the data date and goes forward in time from the data date and takes into consideration the activity logic, durations, calendars and any hard constraint dates and computes the EARLY start and EARLY finish dates. Based on where you are on your project (as far as progress is concerned) as of the data date this is the EARLIEST that activities can start or finish.The backward pass begins at the project completion date (or the project must finish by date) and backward forward in time and takes into consideration the activity logic, durations, calendars and any hard constraint dates and computes the LATE start and LATE finish dates. Based on where you are on your project (as far as progress is concerned) as of the data date this is the LATEST that activities can start or finish.So think of the late dates as due by dates. In your case the Late dates are earlier in time than the early dates. This means that you are behind schedule and that you will missed the due by dates. In other words you are scheduled LATE DATES to be done by Dec 2015. However due to your lack of progress your project is now projected to be done EARLY DATES on AUG 2016. as far as the units stacking up on the data date if these are LOE activities you will have to assign a resource curve to the resource to get it to distribute the manhours.