Website Upgrade Incoming - we're working on a new look (and speed!) standby while we finalise the project

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Late units & Early units

1 reply [Last post]
Tanveer Ahmad Niazi
User offline. Last seen 6 years 31 weeks ago. Offline
Joined: 15 Dec 2005
Posts: 151
Groups: GPC Qatar

Hi,

I have been posted to another project site and that is supposed to finish by 31 Dec this year. And have some strange result of man-hour report in the programme. The Remaining Late Units man-hors finishing 19 weeks (Nov 2016) earlier then the Remaining Early Units man-hours at the data date April 2016. The project finish date has projected up to Aug 2016. I couldn’t understand that, if anyone can explain me how / why this happens.

Cheers Tanveer

Replies

Zoltan Palffy
User offline. Last seen 31 weeks 3 days ago. Offline
Joined: 13 Jul 2009
Posts: 3089
Groups: None

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.