none
How to modify certain baseline information and not the rest ?

    Question

  • Hello once again.

    So my question is as follows: "How can I rollup the change of baseline start date on certain tasks to their summary tasks and not reset/set new baselines values for the work and cost variance of that certain task ?"

    Now what do I mean ? Well I made the mistake, a while back, of adding new tasks with the option "Create new tasks and set their start dates at the begining of the project" unknowingly set in the Microsoft Project 2010's options. Since I didn't realize this, and I "Set baseline information for selected tasks only" on all the new tasks, well my old and accurate baseline start date for my other summary tasks all changed and went back to the start of the project since I unknowingly had that option set in the Microsoft Project 2010 settings.

    So;
    Mistake #1 - creating new tasks which are in reality starting in the present, but because I had the "New tasks created are set to the project start date" the baseline start of these dates is in the past. This is arguable not a mistake just an oversight on my part.
    Mistake #2 - I then set baseline for selected tasks (the new ones added) which caused all the summary tasks baseline start dates to get tossed in the past at the project's start date.
    Mistake #3 - I didn't realize this because I work with actual start and actual finish in my tracking view, so I never looked at the baseline start dates. I just caught this yesterday and now I'm trying to get help to resolve this.

    Why is this problematic for me ?
    Because I need to have the "accurate" baseline start dates for another project manager since we use that data to project work load in future months.

    How did we try to solve this ?
    In the tracking view, I showed a new column; "Baseline Start" and I modified the baseline start dates of the new tasks. But when I try to "save baseline for selected tasks" obviously all the baseline data is reset. So I lose all my work and cost variance. This is unaccetable for me, and I can't afford to lose this data.

    Hence my original question: How can I change the baseline start date for selected tasks, and then have microsoft project roll up / re-calculate the dates into the summary tasks BUT NOT reset/lose my variance (because I'm working with a lot of ACTUAL data)

     

    Thank you for your time, I look forward to seeing how this is solved.

    DDN

    Tuesday, August 02, 2011 1:42 PM

Answers

  • DDNProcess --

    Thanks for your thorough analysis of the problem, and the issues with the possible solution I posted.  I'm afraid you are back to my original suggestion, which is manually typing the dates you want in the Baseline Start and Baseline Finish fields for the tasks and summary tasks that have incorrect baseline dates.  As you now know, there's really no easy way to correct a Baseline when the original planned dates were wrong.  Hope this helps.


    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    • Marked as answer by DDNProcess Monday, August 08, 2011 1:54 PM
    Wednesday, August 03, 2011 1:26 PM

All replies

  • DDNProcess --

    You cannot update your Baseline by updating only the Baseline Start and Baseline Finish dates, as you already know.  When you update your Baseline, Microsoft Project 2010 captures the current values for Duration, Start, Finish, Cost, and Work, along with a few other minor fields, such as Fixed Cost and Fixed Cost Accrual.  So, that approach simply will not work in your situation.  On the other hand, have you tried manually typing the Baseline Start and Baseline Finish dates for the tasks in question?  Let us know and we will try to help.


    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    • Proposed as answer by John T Purvis Wednesday, August 03, 2011 7:38 PM
    • Unproposed as answer by John T Purvis Wednesday, August 03, 2011 7:39 PM
    Tuesday, August 02, 2011 1:46 PM
  • Well I figured that I could not use the "update baseline for selected tasks" option.

     

    I've tried manually changing the baseline start date on my tasks, but upon changing them - the summary tasks still retains the old baseline start. It does not recalculate it. Is there a way to do this ? Each summary task has about 8 subtasks. And the summary task baseline start is constrained by the new tasks that I added which have erronous baseline start dates. So when I change those erronous tasks and their baseline starts the individual tasks change but the change is not reflected in the summary task's baseline start.

    Tuesday, August 02, 2011 1:49 PM
  • DDNProcess --

    Baseline values do not roll up to their respective summary tasks.  This means you would need to manually change the Start and/or Finish dates for the respective summary tasks.

    It just occurred to me that there might be another method.  Instead of manually typing dates, you might try the following instead:

    1.  Select the tasks AND the summary tasks whose Start and Finish dates you want to update in the Baseline.
    2.  Click the Project ribbon and then click Set Baseline > Set Baseline.
    3.  Select the "Set interim plan" option.
    4.  In the Copy pick list, leave the Scheduled Start/Finish item selected.
    5.  Click the Into pick list and select the Baseline item on the list.
    6.  Choose the "Selected tasks" option (the system does not allow you to select an option in the Roll Up Baselines section).
    7.  Click the OK button.
    8.  Click the Yes button to update the Baseline.

    I tried this method and it seems to work.  This method updates only the Baseline Start and Baseline Finish dates, without impacting Baseline Cost and Baseline Work.  Hope this helps.


    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Tuesday, August 02, 2011 2:52 PM
  • I'll post feedback as soon as I attempt this, thanks.

    Tuesday, August 02, 2011 5:09 PM
  • DDNProcess --

    I will be anxious to hear the results of your testing.  Let us know when you know.  Thanks!


    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Tuesday, August 02, 2011 7:13 PM
  • When you pick the update baseline for selected tasks option it also enables 2 other options below it to either rollup the new baseline information to all the 'up stream' summary tasks or from the subtasks into the selected summary tasks.

     

    Using these options you can, for example, select a few sub tasks and then resave the baseline for those tasks and 'rollup' the new values for baseline fields to the summary tasks that are 'up stream' from the selected tasks.


    Brian Kennemer – DeltaBahn Senior Architect
    Blog | Twitter | LinkedIn
    Tuesday, August 02, 2011 11:14 PM
  • Brian --

    If you re-read the user's original post, the option you propose will not work.  He does not want to roll up the new Cost and Work information; only the Start and Finish dates.


    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Tuesday, August 02, 2011 11:59 PM
  • Damn. :-) I lost that part through the thread. :-)
    Brian Kennemer – DeltaBahn Senior Architect
    Blog | Twitter | LinkedIn
    Wednesday, August 03, 2011 12:03 AM
  • DDNProcess --

    I will be anxious to hear the results of your testing.  Let us know when you know.  Thanks!


    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"


    So I tried your methodology and ran into unexpected results. I will post some sample data and repost it with your methodology so you can see the behaviour.

     

    Wednesday, August 03, 2011 12:28 PM
  • DDNProcess --

    Baseline values do not roll up to their respective summary tasks.  This means you would need to manually change the Start and/or Finish dates for the respective summary tasks.

    It just occurred to me that there might be another method.  Instead of manually typing dates, you might try the following instead:

    1.  Select the tasks AND the summary tasks whose Start and Finish dates you want to update in the Baseline.
    2.  Click the Project ribbon and then click Set Baseline > Set Baseline.
    3.  Select the "Set interim plan" option.
    4.  In the Copy pick list, leave the Scheduled Start/Finish item selected.
    5.  Click the Into pick list and select the Baseline item on the list.
    6.  Choose the "Selected tasks" option (the system does not allow you to select an option in the Roll Up Baselines section).
    7.  Click the OK button.
    8.  Click the Yes button to update the Baseline.

    I tried this method and it seems to work.  This method updates only the Baseline Start and Baseline Finish dates, without impacting Baseline Cost and Baseline Work.  Hope this helps.


    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"


    I have many iterations of this type of structure which need to be corrected. The task text is in french, but I dont think the actual meaning is relevant to me solving this problem. The columns are in english as my MSP2010 client is in english atm. I will show you the break down priot to posting all the columns in attempt to clarify the situation and remove all ambiguity.


    I have a "Fonction 1.7" which has 5 sub categories:

    Task Name
    Fonction 1.7 : Gérer les fonctions de pilotage
       Définir les accès des utilisateurs (TR 1.7.1)
       Définir les tables systèmes (TR 1.7.2)
       Inscrire le domaine des valeurs par table système (TR 1.7.3)
       Définition des ventes dans les stationnements (TR 1.7.4)
       Définir les périphériques (TR 1.7.5)

     

    In one of my sub categories is the following structure:

    Task Name
    Fonction 1.7 : Gérer les fonctions de pilotage
       Définir les accès des utilisateurs (TR 1.7.1)
          Dossier Fonctionnel
          Dossier organique et Database
          Programmation et tests unitaires
          Dossier Anglais
          Dossier des tests
          Exécution des tests

     

    And completely expanded the structure is as follows:

    Task Name
    Fonction 1.7 : Gérer les fonctions de pilotage
       Définir les accès des utilisateurs (TR 1.7.1)
          Dossier Fonctionnel
          Dossier organique et Database
             Dossier Organique
             Database
          Programmation et tests unitaires
          Dossier Anglais
          Dossier des tests
          Exécution des tests


    Now the tasks that are creating problems for me are the "Database" and the "Dossier des tests" these are tasks which I added at a later point in time in my project file, and unknowingly I messed up the baseline start dates as described in my original post. So instead of putting the present date (which is now in the past) they used the entire project files Project Start Date (which is way further in the past).

     

    Wednesday, August 03, 2011 12:37 PM
  • DDNProcess --

    Well, if the using the Save Interim Plan feature doesn't work for you, I guess it's back to entering the baseline dates manually.  :(


    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Wednesday, August 03, 2011 12:38 PM
  • Here is a snapshot of the baseline dates. The start of my project was 26/07/2010. So you can see that after having added the "Dossier des tests" and "Database" since the baseline start dates were set to the project start date of 26-07-2010, the entire summary task basline start changed to 26-07-2010. This is the root of my problem and the problem that I'm trying to correct. I want to change the baseline start dates for "Dossier des tests" and "Database" and have microsoft project roll up the changes into the respective summary tasks so they go back to what they originally were. I assume if I can correct the baseline start and have the data rolled up that the problem will be fixed.

    Task Name Baseline Start
    Fonction 1.7 : Gérer les fonctions de pilotage 26/07/2010
       Définir les accès des utilisateurs (TR 1.7.1) 26/07/2010
          Dossier Fonctionnel 17/11/2010
          Dossier organique et Database 26/07/2010
             Dossier Organique 22/12/2010
             Database 26/07/2010
          Programmation et tests unitaires 17/11/2010
          Dossier Anglais 15/11/2010
          Dossier des tests 26/07/2010
          Exécution des tests 15/11/2010

     

    After you posted your suggestion & methodology on how to solve this, I went ahead and did it. The baseline date did in fact change, but I also had changes in the rest of my data which made me not like this solution.

    Data before applying your solution:

     

    Task Name Baseline Start % Comp. Act. Start Act. Finish Act. Work Remaining Work Baseline Work Work Variance Act. Cost Baseline Cost Cost Variance
    Fonction 1.7 : Gérer les fonctions de pilotage 26/07/2010 100% 02/11/2010 29/07/2011 680.25 hrs 0 hrs 1,004.27 hrs -324.02 hrs $51,133.38 $63,216.83 -$12,083.45
       Définir les accès des utilisateurs (TR 1.7.1) 26/07/2010 100% 15/11/2010 26/07/2011 99.5 hrs 0 hrs 107.7 hrs -8.2 hrs $5,494.00 $5,031.56 $462.43
          Dossier Fonctionnel 17/11/2010 100% 17/11/2010 19/11/2010 23 hrs 0 hrs 6.7 hrs 16.3 hrs $1,842.07 $536.60 $1,305.47
          Dossier organique et Database 26/07/2010 100% 29/11/2010 30/06/2011 18 hrs 0 hrs 7 hrs 11 hrs $1,473.44 $672.00 $801.44
             Dossier Organique 22/12/2010 100% 29/11/2010 30/11/2010 16 hrs 0 hrs 21 hrs -5 hrs $1,281.44 $0.00 $1,281.44
             Database 26/07/2010 100% 30/06/2011 30/06/2011 2 hrs 0 hrs 7 hrs -5 hrs $192.00 $672.00 -$480.00
          Programmation et tests unitaires 17/11/2010 100% 17/11/2010 28/12/2010 35.5 hrs 0 hrs 35 hrs 0.5 hrs $1,295.40 $1,277.15 $18.25
          Dossier Anglais 15/11/2010 100% 15/11/2010 01/04/2011 5 hrs 0 hrs 1 hr 4 hrs $182.50 $0.00 $182.50
          Dossier des tests 26/07/2010 100% 26/07/2011 26/07/2011 1 hr 0 hrs 9 hrs -8 hrs $80.09 $720.81 -$640.72
          Exécution des tests 15/11/2010 100% 01/12/2010 01/04/2011 17 hrs 0 hrs 49 hrs -32 hrs $620.50 $1,788.50 -$1,168.00

     

     

    Applying your suggestion;
    "1. Select the tasks AND the summary tasks whose Start and Finish dates you want to update in the Baseline." 
    I selected the following summary and non summary tasks: 
    Summary task: Fonction 1.7: Gérer les fonctions de pilotage summary
    Summary task: Definir les acces des utilisateurs (TR 1.7.1)
    Summary task: Dossier organique et Database
    Task: Database
    Task: Dossier des tests

    Here is the data after the rest of your suggested solution:

     

    Task Name Baseline Start % Comp. Act. Start Act. Finish Act. Work Remaining Work Baseline Work Work Variance Act. Cost Baseline Cost Cost Variance
    Fonction 1.7 : Gérer les fonctions de pilotage 26/07/2010 100% 02/11/2010 29/07/2011 680.25 hrs 0 hrs 1,007.27 hrs -327.02 hrs $51,133.38 $63,377.55 -$12,244.17
       Définir les accès des utilisateurs (TR 1.7.1) 15/11/2010 100% 15/11/2010 26/07/2011 99.5 hrs 0 hrs 110.7 hrs -11.2 hrs $5,494.00 $5,192.28 $301.71
          Dossier Fonctionnel 17/11/2010 100% 17/11/2010 19/11/2010 23 hrs 0 hrs 6.7 hrs 16.3 hrs $1,842.07 $536.60 $1,305.47
          Dossier organique et Database 29/11/2010 100% 29/11/2010 30/06/2011 18 hrs 0 hrs 18 hrs 0 hrs $1,473.44 $1,473.44 $0.00
             Dossier Organique 22/12/2010 100% 29/11/2010 30/11/2010 16 hrs 0 hrs 21 hrs -5 hrs $1,281.44 $0.00 $1,281.44
             Database 30/06/2011 100% 30/06/2011 30/06/2011 2 hrs 0 hrs 2 hrs 0 hrs $192.00 $192.00 $0.00
          Programmation et tests unitaires 17/11/2010 100% 17/11/2010 28/12/2010 35.5 hrs 0 hrs 35 hrs 0.5 hrs $1,295.40 $1,277.15 $18.25
          Dossier Anglais 15/11/2010 100% 15/11/2010 01/04/2011 5 hrs 0 hrs 1 hr 4 hrs $182.50 $0.00 $182.50
          Dossier des tests 26/07/2011 100% 26/07/2011 26/07/2011 1 hr 0 hrs 1 hr 0 hrs $80.09 $80.09 $0.00
          Exécution des tests 15/11/2010 100% 01/12/2010 01/04/2011 17 hrs 0 hrs 49 hrs -32 hrs $620.50 $1,788.50 -$1,168.00

     


    If you look and compare the tables, there's quite a few things that don't add up and seem to be erronous. For example the baseline start for database changed to 29/07/2011 but the summary task is 28/07/2011.

    Task Name Baseline Start
    Dossier organique et Database 28/07/2011
       Dossier Organique 22/12/2010
       Database 29/07/2011

     

    That's just the first and most obvious example that I saw but if you look at the monetary data, such as the baseline work, work variance and baseline cost they have all changed. Suggesting to me that this methodology is not the solution that I'm hoping for. I found the changes to be easy to see if you look at the cost variance (the last to the right) column.

     

    What are your thoughts?

     


    PS: I apologize in advance for the wall of spam - but I wasnt sure how else to portray what I was seeing.



    • Edited by DDNProcess Wednesday, August 03, 2011 1:53 PM
    Wednesday, August 03, 2011 12:52 PM
  • DDNProcess --

    Thanks for your thorough analysis of the problem, and the issues with the possible solution I posted.  I'm afraid you are back to my original suggestion, which is manually typing the dates you want in the Baseline Start and Baseline Finish fields for the tasks and summary tasks that have incorrect baseline dates.  As you now know, there's really no easy way to correct a Baseline when the original planned dates were wrong.  Hope this helps.


    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    • Marked as answer by DDNProcess Monday, August 08, 2011 1:54 PM
    Wednesday, August 03, 2011 1:26 PM
  • DDNProcess --

    ... As you now know, there's really no easy way to correct a Baseline when the original planned dates were wrong...


    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Bullocks, that's lame !
    I've heard comments from people that they didn't like MSProject because of how it handled baselines... I guess if that's the only solution then this problem is resolved. I'll leave it open for another day or two, see if anyone has an ingenious insight into the matter. Otherwise I'll post your comment as a solution.

    Thanks for your help.

    DDN

    Wednesday, August 03, 2011 1:57 PM
  • Not sure I followed the entire thread, but here's an idea...
     
    1) Create a custom Date field.  Set the Date field to equal the Baseline
    Start and to roll up the way you would like it.
    2) Copy/Paste that back into the Baseline Start?
     
    Pls disregard is this is not at all relevant.
     
     

    Andrew Lavinsky [MVP] Blog: http://azlav.umtblog.com Twitter: @alavinsky
    Wednesday, August 03, 2011 2:08 PM
  • DDN --

    Sure, feel free to leave this topic open for another day or two.  There are some really smart people who participate in this group, and maybe they would have an answer for you.  If not, thanks for your offer to mark the topic as completed.


    Dale A. Howard [MVP]
    VP of Educational Services
    msProjectExperts
    http://www.msprojectexperts.com
    http://www.projectserverexperts.com
    "We write the books on Project Server"

    Wednesday, August 03, 2011 4:30 PM
  • I use a series of macros to retotal baseline information as needed

     

    The macros if used, are to be used in ascending order stating from the lowest level used.

    1.       Baseline Fixed Cost Removal

    a.       This removes any Time Phased Fixed Cost from all tasks

    b.      This is used on rare occasion time phased  Fixed Cost is inadvertently saved in baseline

    2.       Update Baseline Resource Cost

    a.       This updates the time phased assignment cost to a new or correct labor category rates

    b.      NOTE: This was used to change costs from Rate Table A to B without changing time phasing. This is hard coded into macro this will need to be changed based on future need, before macro is used.

    3.       Update Assignment to Task Baseline

    a.       Following a change of Resource Assignment Time Phased Assignment data, the Task Time Phased Task Data, Task and  Assignment data need to be updated

    4.       Update Summary Task Baseline Rollup

    a.       Following an update of Task Data including Time Phased data, needs to be updated to all Summary Tasks at both Task and Time Phased Level

    5.       Update Project Summary Baseline Rollup 

    a.       The Project Summary Task is a special summary task that is needs to be updated at both Task and Time Phased Level

      

    Task Level Data

    Time Phased Data

    Project Summary Task                     5

    Project Summary Task Time Phased Data        5

    Summary Task                                  4

    Summary Task Time Phase Data                       4

    Task                                                                      3

    Task Time Phased Data

    Task Resource Assignment                                  3

    Resource Assignment Time Phased Data         3

              1      2

     

     

     

     

     

     

     


    John Purvis Digital Concepts, Inc. Assigned to CSC ECSS Program

    Wednesday, August 03, 2011 7:41 PM
  • I use a series of macros to retotal baseline information as needed

     

    The macros if used, are to be used in ascending order stating from the lowest level used.

    1.       Baseline Fixed Cost Removal

    a.       This removes any Time Phased Fixed Cost from all tasks

    b.      This is used on rare occasion time phased  Fixed Cost is inadvertently saved in baseline

    2.       Update Baseline Resource Cost

    a.       This updates the time phased assignment cost to a new or correct labor category rates

    b.      NOTE: This was used to change costs from Rate Table A to B without changing time phasing. This is hard coded into macro this will need to be changed based on future need, before macro is used.

    3.       Update Assignment to Task Baseline

    a.       Following a change of Resource Assignment Time Phased Assignment data, the Task Time Phased Task Data, Task and  Assignment data need to be updated

    4.       Update Summary Task Baseline Rollup

    a.       Following an update of Task Data including Time Phased data, needs to be updated to all Summary Tasks at both Task and Time Phased Level

    5.       Update Project Summary Baseline Rollup 

    a.       The Project Summary Task is a special summary task that is needs to be updated at both Task and Time Phased Level

      


    John Purvis Digital Concepts, Inc. Assigned to CSC ECSS Program

     


    Well your macro #4,5 seem to do what I'd be interested in correcting in my own work. Because so far without the aid of a macro fixing stuff - which means it's a pretty tedious task and warranted making a script to do - I'm about to have to go in manually and change all the baseline start dates one by one.

    Are you able to share them? or suggest how I can go about viewing them ?  I'd be interested in seeing if they can solve these issues I'm having and then understand why, and then how to correct them.

    Thursday, August 04, 2011 2:15 PM
  • Not sure I followed the entire thread, but here's an idea...
     
    1) Create a custom Date field.  Set the Date field to equal the Baseline
    Start and to roll up the way you would like it.
    2) Copy/Paste that back into the Baseline Start?
     
    Pls disregard is this is not at all relevant.
     
     

    Andrew Lavinsky [MVP] Blog: http://azlav.umtblog.com Twitter: @alavinsky

    Yeah, thanks for the suggestion Andrew, but this doesn't prevent me from manually changing all the dates either way. So if I'm going to have to do it manually, then I might as well change the baseline start date right away.
    Monday, August 08, 2011 1:53 PM
  • This code is provided with no warrenty, or support.

    Digital Concepts, Inc, is availble to provide contract support if needed.

    Here is Macro 5 code.

    Sub UpdateProjectSummaryBaselineRollup()

    'This updates Project Summary Task Only, run after last
    'This replaces all values by readdition of existing data
    'Prepared by John Purvis, Digital Concepts, Inc.

    On Error Resume Next
    Dim T As Task
    Dim TC As Task
    Dim tcBL As TimeScaleValues
    Dim tBL As TimeScaleValues
    Dim tdBL As TimeScaleValues
    Dim tcdBL As TimeScaleValues
    Dim Counter As Integer
    Dim I As Integer
    Dim Tbw As Single
    Dim SD As Date
    Dim ED As Date


    'Start Date and End Date are extended to ensure baseline information outside of current date range is captured
    SD = DateAdd("d", -60, ActiveProject.ProjectSummaryTask.EarlyStart)
    ED = DateAdd("d", 60, ActiveProject.ProjectSummaryTask.LateFinish)


        Set T = ActiveProject.ProjectSummaryTask

                If (T.Summary = True) Then
                    If T.OutlineLevel = 0 Then
                   
                   
                    Debug.Print T.Name, T.Summary, T.OutlineLevel, T.ID

                    T.BaselineWork = 0
                    T.BaselineCost = 0
                    T.FixedCost = 0
                            
                    Set tBL = T.TimeScaleData(StartDate:=SD, _
                    EndDate:=ED, _
                    Type:=pjTaskTimescaledBaselineWork, TimeScaleUnit:=pjTimescaleDays, Count:=1)

                    Set tdBL = T.TimeScaleData(StartDate:=SD, _
                    EndDate:=ED, _
                    Type:=pjTaskTimescaledBaselineCost, TimeScaleUnit:=pjTimescaleDays, Count:=1)

                    For Counter = 1 To tBL.Count
                    tBL(Counter).Value = 0
                    tdBL(Counter).Value = 0
                    Next Counter
                   
                    For Each TC In T.OutlineChildren 'This finds the outline level 1 tasks that roll up into summary task
                   
                    Debug.Print TC.Name, TC.ID
                   
                    Set tBL = T.TimeScaleData(StartDate:=SD, _
                    EndDate:=ED, _
                    Type:=pjTaskTimescaledBaselineWork, TimeScaleUnit:=pjTimescaleDays, Count:=1)

                    Set tcBL = TC.TimeScaleData(StartDate:=SD, EndDate:=ED, _
                    Type:=pjTaskTimescaledBaselineWork, TimeScaleUnit:=pjTimescaleDays, Count:=1)

                    Set tdBL = T.TimeScaleData(StartDate:=SD, _
                    EndDate:=ED, _
                    Type:=pjTaskTimescaledBaselineCost, TimeScaleUnit:=pjTimescaleDays, Count:=1)

                    Set tcdBL = TC.TimeScaleData(StartDate:=SD, _
                    EndDate:=ED, _
                    Type:=pjTaskTimescaledBaselineCost, TimeScaleUnit:=pjTimescaleDays, Count:=1)
                   
                        For Counter = 1 To tcBL.Count
                         If Not tcBL(Counter).Value = "" Then
                            tBL(Counter).Value = tBL(Counter).Value + tcBL(Counter).Value
                            tdBL(Counter).Value = tdBL(Counter).Value + tcdBL(Counter).Value
                            'tcBL(Counter).Value = 0
                            'Debug.Print fcBL(Counter).Value
                            'fcBL(Counter).Value = 0
                            End If
                          
                        Next Counter

                      T.BaselineWork = T.BaselineWork + TC.BaselineWork
                        T.BaselineCost = T.BaselineCost + TC.BaselineCost
                      
                       'Debug.Print "TC", TC.Name; TC.ID
                        'T.FixedCost = 0
                        'Debug.Print T.FixedCost; T.Name
                   Next TC
                   T.BaselineStart = T.Start
                   T.BaselineFinish = T.Finish
                   T.BaselineDuration = T.Duration
            End If
         End If
         
    Here is Macro 4 Code

         Sub UpdateSummaryTaskBaselineRollup()

    'Re-adds and Uddates Time Phased Baseline data to Summary Tasks
    'Typical use is after a baseline task is moved to a new area of the plan

     

    On Error Resume Next
    Dim T As Task
    Dim TC As Task
    Dim T_cBL As TimeScaleValues 'Task Cost
    Dim T_wBL As TimeScaleValues 'Task Work
    Dim TC_cBL As TimeScaleValues 'Task Child Cost
    Dim TC_wBL As TimeScaleValues 'Task Child Work
    Dim Counter As Integer
    Dim I As Integer
    Dim Tbw As Single
    Dim SD As Date
    Dim ED As Date

    'This assumes a MAX of 15 Levels are in plan, increase is additional levels exist

    For I = 15 To -1 Step -1

        For Each T In ActiveProject.Tasks
            If Not T Is Nothing Then
            'Debug.Print T.Summary, T.ID
               
                If (T.Summary = True) Then
                    SD = DateAdd("d", -60, T.Start)
                    ED = DateAdd("d", 60, T.Finish)

                    If T.OutlineLevel = I Then
                    'Debug.Print T.Name, T.Summary, T.OutlineLevel, T.ID
                    T.BaselineWork = 0
                    T.BaselineCost = 0
                    T.FixedCost = 0
                               
                    Set T_wBL = T.TimeScaleData(StartDate:=SD, EndDate:=ED, _
                                Type:=pjTaskTimescaledBaselineWork, TimeScaleUnit:=pjTimescaleDays, Count:=1)
                               
                    Set T_cBL = T.TimeScaleData(StartDate:=SD, EndDate:=ED, _
                                Type:=pjTaskTimescaledBaselineCost, TimeScaleUnit:=pjTimescaleDays, Count:=1)
                               
                    For Counter = 1 To T_wBL.Count
                    T_wBL(Counter).Value = 0
                    T_cBL(Counter).Value = 0
                    Next Counter
                               
                               
                 
              
                               
                    For Each TC In T.OutlineChildren

                                Set TC_wBL = TC.TimeScaleData(StartDate:=SD, EndDate:=ED, _
                                Type:=pjTaskTimescaledBaselineWork, TimeScaleUnit:=pjTimescaleDays, Count:=1)


                                Set TC_cBL = TC.TimeScaleData(StartDate:=SD, EndDate:=ED, _
                                Type:=pjTaskTimescaledBaselineCost, TimeScaleUnit:=pjTimescaleDays, Count:=1)

                                   For Counter = 1 To T_cBL.Count

                                        If Not TC_wBL(Counter).Value = 0 Then
                                            T_wBL(Counter).Value = T_wBL(Counter).Value + TC_wBL(Counter).Value
                                        End If
                                     
                                        If Not TC_cBL(Counter).Value = 0 Then
                                            T_cBL(Counter).Value = T_cBL(Counter).Value + TC_cBL(Counter).Value
                                        End If

                                    Next Counter


                                End If 'End If TC.ExternalTask = False

                           T.BaselineWork = T.BaselineWork + TC.BaselineWork
                           T.BaselineCost = T.BaselineCost + TC.BaselineCost

                           End If 'End If Not TC Is Nothing

                         Next TC

                    End If 'If T.OutlineLevel = I
                End If 'If (T.Summary = True)
            End If 'If Not T Is Nothing
            
            
        
         Next T
    Next I

    End Sub

     


    John Purvis Digital Concepts, Inc. Assigned to CSC ECSS Program
    Wednesday, August 10, 2011 6:26 PM
  • Hi John,

    I have been reading this with great interest as my issue is that a baseline was saved with incorrect cost rate tables for task assignments.  Now that the PM has realised this, he has updated the rate table in the current schedule and wants to update the costs in the baseline so the variances are correct.  However, the schedule has changed in many places since the baseline so we cannot simply overwrite the original baseline from the current position.

    Would it be possilbe to get the remaining macros too as I believe number 2 and 3, along with the ones you have already provided, would provide the solution? 

    Many thanks for any assistance as I belive this is the first of a number of projects that will have this problem as we have only recently started to use multiple rate tables.

     

    Tuesday, August 16, 2011 9:53 PM
  • This is very possible, I had a similiar rate table change and updated the baseline costs using new rates. This requires a series of macros

    1. Update Resource Rate
    2. Update assignment baseline time phased costs
    3. Update Task time phased ocsts
    4. Update Summary task time phased costs
    5. Update Project Summary time phased costs

    Note as the time phase data is updated you need to also update the task level data.


    John Purvis Digital Concepts, Inc. Assigned to CSC ECSS Program
    Friday, August 26, 2011 4:53 PM
  • Hi John,

    I have a situation here that I need to update baseline cost , because it changed after baseline was saved and project has tasks with progress.

    Also project initial budget change and need to be decreased in 6%.

    Can I have access to your macro 1,2 and 3 ?

    Thank you in advance !

    Sincerely

    Andre L Silva

    Tuesday, April 03, 2012 7:28 PM
  • This is not a perfect solution, but I wrote a macro that does this as well:

    1) Copies Baseline Start/Finish to an Interim Start/Finish fields.

    2) Rebaselines the project (schedule, cost, etc.)

    3) Copies the Interim Start/Finish fields back into the Baseline Start/Finish fields.

    It doesn't handle assignment data or timescaled data, but it keeps your schedule variances while resetting cost.  That's probably good for 90% of the use cases.


    Andrew Lavinsky [MVP] Blog: http://azlav.umtblog.com Twitter: @alavinsky

    Tuesday, April 03, 2012 7:32 PM
  • Contact me by email I can help

    John Purvis

    Digital Concepts, Inc

    jpurvis@dci-america.com

    Tuesday, April 03, 2012 8:12 PM
  • Andrew,

    Thank you for your quick answer

    Can I have access to this scripts ?

    Thank you

    You can reach-me at andre@starinfo.com.br


    • Edited by Andre Ramme Tuesday, April 10, 2012 5:12 PM
    Tuesday, April 10, 2012 5:11 PM
  • Very Informative Thread !!
    Friday, April 13, 2012 11:07 AM
  • Dale you are heaven sent! Thank you so much for your fix. It worked for me and I had a similar issue to that of DDN.

    Thanks a million,

    smlail

    Wednesday, August 06, 2014 2:01 PM
  • smlail --

    You are more than welcome for the help, my friend!  :)


    Dale A. Howard [MVP]

    Wednesday, August 06, 2014 4:41 PM