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.

Baseline

10 replies [Last post]
bryc ali
User offline. Last seen 1 year 46 weeks ago. Offline
Joined: 3 Nov 2009
Posts: 43

Every tree or two months, my Schedule Variance increase, my planner modify the baseline eachtime two reduce the variance, is it correct to do it? and if it's correct in which case we have to do it please?

Replies

Angelito Estrella
User offline. Last seen 1 year 21 weeks ago. Offline

Provisions in contract allows/force the Contractor to Re-Baseline

ex; when progress consistently drops for say 10% each updating period/month for define/agreed number of months.

Otherwise, Baseline should not be updated.

In updating schedule and keeping its contracted completion period (as in Baseline), work on remaining durations and out of sequence logic.

Changing logics (when necessary) has to be documented and approved by both parties.

Santosh Bhat
User offline. Last seen 13 weeks 4 days ago. Offline
Joined: 15 Apr 2005
Posts: 381

There is no fixed ratio or method, each contract is different, and the contract documentation may provide guidance on what is the mechanism for seeking extentions of time and/or cost recovery - you could in concept use these as the basis for performing a re-baseline, but again the contract should be the document that guides you on this.

As for maintainingg two different schedules - whether they are baseliens, current forecasts isn't important. Typically the reason for having two seperate schedules is to maintain a level of contingency between the internal schedule and the contract/client schedule ,to keep some time up ones sleeve in case of any issues (see here for descriptions on some methods used for this: http://www.austprojplan.com.au/schedule-contingency-methods/).

But consider this scenario, your project is tracking to the internal schedule and physically completed works are showing as 90%, but in order to maintain the contract/client schedule forecast of the contract end date, the same task needs to be showing a value less than 90%. What happens when the client inspects the site, and realises that the contract schedule you've been providing is not representing the true position of the project? then it actually makes the entire schedule questionable.

 

bryc ali
User offline. Last seen 1 year 46 weeks ago. Offline
Joined: 3 Nov 2009
Posts: 43

Thank you for your reply,but when you told me that we must rebasline when the scope varied significantly, could you give me a rate to reforcasting for example when the varition will reach over 5% in term of budget or quantities in the scope ?

Is it correct to have two baselines, one between us and our contractor and another internal for our company if it's correct I think that the forcast of the internal baseline will be more important than the external?

  •  
Santosh Bhat
User offline. Last seen 13 weeks 4 days ago. Offline
Joined: 15 Apr 2005
Posts: 381

When you start playing games of running multple versions of "the truth" eventually all but one of them will fail. I go back to my earlier comment - poor performance is not an excuse to rebaseline.

Valid reasons for changing the baselines are:

1) The scope has varied significantly to warrant a replanning, reforecasting exercise, where significant changes to

  • budgets,
  • milestones,
  • risks/contingencies.
  • delivery methodologies and
  • resources deployed

are deemed acceptable by all parties to the project

2) Where the original baseline has become so detached from the reality of the projects actual position that its not serving its purpose as a measurement tool. But if you're at this point then prior to getting into this pickle, you should've take the steps in (1) above

Alexandre Antonios
User offline. Last seen 4 years 1 week ago. Offline
Joined: 28 Nov 2018
Posts: 12
Groups: None

Hello again,

As I don't have more information about the case, I cannot judge this baseline edit but in theory it should not be changed except if this manipulation is enclosed in the contract itself. It is a matter of bad etiquette (miscordial and mispolite) to change it without the parties' consensus.

You might disagree with such manipulations because they affect Schedule Variance which ultimately affects the different visions about EMV (Earned Value Management). In return, he might have cultural-specific, contract-specific, strategic-specific or industry-specific reasons behind it.

Perhaps Santosh, Anoon or other planners have more insights about it.

Best regards,
AA

bryc ali
User offline. Last seen 1 year 46 weeks ago. Offline
Joined: 3 Nov 2009
Posts: 43

Iunderstand but, when you have the same baselineinternal and for the client,is judicious to revise the base line to reduce de variance between the forcast and progress ?

 

 

Alexandre Antonios
User offline. Last seen 4 years 1 week ago. Offline
Joined: 28 Nov 2018
Posts: 12
Groups: None

Hello Bryc Ali,

You should always have a minimum of two baseline as a contractor:
The internal; the one you use for your own calculations (contractor)
The official; the one you use for the contract agreement on performances and specifications (contractor-owner)

The internal is used from the user's point of view for self-calculation and estimations (you would you use for yourself to benchmark/understand reality behind it).

With the internal baseline, you can 'elastically' operate minor changes (change the baseline) in order to meet the points on the official document (official agreed baseline). With the internal baseline you might justify some 'changes' you made or you might use it as a reference document if somebody manipulated the initial data. 

The official baseline could be changed with "valid reasons" as the agreement allows, in general with a consensus (contractor and owner agree). The official baseline should not be changed (it is unethical and it could lead to unfairness/miscalculations).

I hope this helps,
AA

bryc ali
User offline. Last seen 1 year 46 weeks ago. Offline
Joined: 3 Nov 2009
Posts: 43

I'm a contractor but i have to share my schedule with my client, what do you mean with internal baseline ? 

Santosh Bhat
User offline. Last seen 13 weeks 4 days ago. Offline
Joined: 15 Apr 2005
Posts: 381
Poor performance ( including not meeting baseline schedule dates) should never be a reason for modifying the baseline.
Anoon Iimos
User offline. Last seen 2 years 32 weeks ago. Offline
Joined: 22 Sep 2006
Posts: 1422

It depends on what you are. I mean, if you are a Contractor, then it must be necessary to revise your baseline when needed (regardless how often). You do this in order to control your cash flow. I'm just talking of your internal baseline schedule. For official Baseline (the one that you submit for approval or acceptance), then you cannot simply change it whenever you want to. This one needs "valid reasons" and consensus for whatever changes or variations that may occur.