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.

Extra time put in developing schedules

2 replies [Last post]
John Reeves
User offline. Last seen 1 week 1 day ago. Offline
Joined: 10 May 2013
Posts: 108
Groups: None

Is it just me, or do others put in quite a bit of extra time for Baseline P6 Schedule & other P6 Schedule Submittals.  Never had a position where you get overtime, I think maybe I figured if I was more efficient maybe I could have go it done in regular hours - but that is BS, it takes longer than most people would assume or estimate.  I would say now, after too many all-nighters, I always go for less line items, but often the spec forces high, even un-necessary detail.  Any rules you live by to avoid this?  I've tried scheduling the scheduling but then that takes time away from the scheduling.  I thought I was doing ok on my last Airport schedule, then the wind changed the day before, runway usage changed, and it had to be re-sequenced with no warning - always something.


Rafael Davila
User offline. Last seen 59 min 48 sec ago. Offline
Joined: 1 Mar 2004
Posts: 4978

There is a misconception among some schedulers that to track activity progress long duration activities must be divided into many segments.  This is a common cause for excessive number of activities to be updated.

If the activity is a duration type such as concrete curing then by reporting elapsed duration then progress is correctly assessed.   But progress of most activities is related to physical volume of work.  If the activity is productivity type then by reporting production then progress is correctly assessed.  Remaining duration will be calculated taking into consideration activity production rate and remaining volume of work.

Activity durations shall be dictated by what it takes for a better schedule:

  • most of the time contiguous work is the way to go,
  • at times activity splitting creates undesired results when resource leveling spread apart activity segments that must be performed contiguous,
  • at times splitting the activity is necessary to get lower duration schedules when considering resource leveling.

Unfortunately this is not well understood by many of those who claim they have the absolute knowledge and embed it into the infamous “Best Practices” that prohibit what otherwise would be BETTER than "Best Practice”.

Only a few among available CPM software provides for production type activities as Spider Project does, for decades it has been embedded in linear scheduling models.  Not surprisingly in linear scheduling model many activities are of long duration.

Linear Scheduling Method

Linear schedules can be modeled using SS+lag and FF+lag between overlapped activities activities, even if your software does not provide for productivity type activities.

Zoltan Palffy
User offline. Last seen 18 hours 1 min ago. Offline
Joined: 13 Jul 2009
Posts: 2842
Groups: None

consider the alternative no work at all.