Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

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.

Forecast Start Date

8 replies [Last post]
sam dsoza
User offline. Last seen 5 years 21 weeks ago. Offline
Joined: 20 Jun 2006
Posts: 55
Groups: None

While performing status update is it advisable to adjus the start date of an activity (that has not started) if it does not align with the contractor date by means of adding a constraint or otherwise?

Replies

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

why not add an activity that represents the for some reason ? then you are not guess or trying to remember why that start date has changed. In ALL instances avoid using contsraint dates unless they are contractually listed in the contract. 

Let the avtivities and logic dictate the schedule This is called critical path method scheduling anything else is simply a glorified bar chart. 

Just imagine that your subcontractor informed you that for some reason they will start to work on September 5 instead of September 1 planned in the baseline. Adding Start No Earlier Than constraint is most natural way to enter this in the project schedule.

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

no constrints are typically not used for updating  it is better to revise the logi and or duration so that it reflects reality 

sam dsoza
User offline. Last seen 5 years 21 weeks ago. Offline
Joined: 20 Jun 2006
Posts: 55
Groups: None

Vladimir, If projects follow EVMS methodolgy and if the forecast plan has deviated  from baseline plan to such an extent that earnings do not make much sense then such an instance could necessiate a baseline change without having an impact to the scope. 

By the same token, should the durations on future activities be changed (by virtue of gained effficiencies or prodcut deliveries from contractor) thus impacting start dates of future activities without capturing in a baseline change? 

Sam, the criteria of estimating project model are simple:

  1. It shall reflect the real dependencies and constraints,

  2. It shall be full and include everything that shall be considered in project schedule.

Project is live and so current version of the project schedule may have constraints that did not exist or were different in the project baseline. Corrective actions like changes in assigned resource crews may change expected activity durations and this is normal practice.

Project baseline shall be changed only if project scope was changed.

sam dsoza
User offline. Last seen 5 years 21 weeks ago. Offline
Joined: 20 Jun 2006
Posts: 55
Groups: None

Patrick / Vladimir, Thanks for the response.

I have changed relationships in the forecast P6 file on near term activities which would have impacted start dates of downstream activities in order to align with "current plan" of work being performed. (I may have occassionaly used contraints as well esp in prcurement activites). I feel that is necessary to reflect "reality".  The reasonging being there would be minimal impact to resources on account of changes to near term activities (thus not necessiating a baseline change). 

I would like to hear your thoughts on if the planned duration of activities in the future have been tweaked to get accurate dates without doing a baseline change.

Patrick, all conflicts that you described shall be solved by resource leveling. Adding artificial dependencies is poor practice.

But if activity start is delayed due to the reasons external to project model it is natural to use the constraint or special activity calendar.

Patrick Weaver
User offline. Last seen 5 days 6 hours ago. Offline
Joined: 18 Jan 2001
Posts: 372
Groups: None

The only time it is 'desirable' to change the forecast start date of an activity during a status update is if an unadjusted date after the progress information has been entered is logically incorrect. Reasonable logical changes may reflect physical constraints not adequately included in the schedule (eg, issues around safe working and clear access), or resource limitations (eg, a crawler crane being required to be in two different places at the same time, or one work crew being required to work on 30 different activities on the same day).  Any adjustment should be incorporated by adding logic or editing deficient logic. The reason for these logical changes need to be recorded.  Constraints (ie, imposed dates) should never be used for this purpose. 

This is the difference between statusing (adding and processing progress information) and then updating the statused schedule to produce a sensible plan for the work going forward. Some software will assist with this by implementing a 'retain logic' option but you cannot rely on automatic processes to apply common sense.  For more on this see: https://mosaicprojects.com.au/Resources_Papers_002.html