I am in the transition phase amongst P3 to P3e/c V5. While tring to assign targets to my projects I noticed that I have to convert the Targets into baselines. Dis anybody run into the same predicament?
I posted the following on Primavera help:
"Why is it now that I have to convert my Target projects for comparison into baselines? I am only allowed to have One Baseline as per my contract requirements. If after I convert the Target into a baseline, I do not want it to be a baseline, then how do I undo this action?
This is not convenient and it goes against scheduling principles. Why call targets, baselines? I do not get the concept
**** Entered By: MMAGEE @ 2007-01-08 07:28 ****
Dear Myrelie,
The baseline functionality has been improved a great deal for version 5.0. It is called a baseline as when using the current project it allows a ’snapshot’ of the project at anytime for comparison in the future, this fits the baseline functionality perfectly.
If you do not wish to convert a project to a baseline you can copy this project then convert the copy to a baseline (please note changes to the project will not be reflected in the baseline).
If you wish to restore the baseline to a project you can simply use the ’Restore’ option from Project -> Maintain Baselines option.
Some of new features in 5.0 are the ’Update Baseline’ functionality. This enables you to update the baseline (such as add new activities/ information) without having to restore the baseline as required in previous versions.
I hope this answers your questions. If there is any more information you require, please let me know.
Regards,
Mark
Solution ID: prim29823
Solution Title: What Project Details are updated when updating a baseline
**** Entered By: OCPCust @ 2007-01-08 09:04 ****
I strongly believe that the Nomenclature of Baseline shall be "reserved" for the schedule prepared as per contract requirements that represents the scope of work, cost as well as the duration of the project as the contractor plans to carry the work at time of contract award after if it is approved by the owner. The fact that the new primavera converts every potential target into a baseline presents a problem since a scheduler can loose track of which one is the real Baseline to the project.
Why would a scheduler want to convert every update into a baseline? What if there’s a claim or the project conditions change and a mitigation schedule is required? How would you go back? I think by having a "Baseline" (AS noted on the P3e/cV5) and and having to create another copy of the project creates a lot of unnecessary work and redundancy in the system that is not required.
Please advise."
Can you give me any feedback on how you coped with this issue? It is very inconvenient for me to have 20 or 30 baselines. any help is appreciated
I posted the following on Primavera help:
"Why is it now that I have to convert my Target projects for comparison into baselines? I am only allowed to have One Baseline as per my contract requirements. If after I convert the Target into a baseline, I do not want it to be a baseline, then how do I undo this action?
This is not convenient and it goes against scheduling principles. Why call targets, baselines? I do not get the concept
**** Entered By: MMAGEE @ 2007-01-08 07:28 ****
Dear Myrelie,
The baseline functionality has been improved a great deal for version 5.0. It is called a baseline as when using the current project it allows a ’snapshot’ of the project at anytime for comparison in the future, this fits the baseline functionality perfectly.
If you do not wish to convert a project to a baseline you can copy this project then convert the copy to a baseline (please note changes to the project will not be reflected in the baseline).
If you wish to restore the baseline to a project you can simply use the ’Restore’ option from Project -> Maintain Baselines option.
Some of new features in 5.0 are the ’Update Baseline’ functionality. This enables you to update the baseline (such as add new activities/ information) without having to restore the baseline as required in previous versions.
I hope this answers your questions. If there is any more information you require, please let me know.
Regards,
Mark
Solution ID: prim29823
Solution Title: What Project Details are updated when updating a baseline
**** Entered By: OCPCust @ 2007-01-08 09:04 ****
I strongly believe that the Nomenclature of Baseline shall be "reserved" for the schedule prepared as per contract requirements that represents the scope of work, cost as well as the duration of the project as the contractor plans to carry the work at time of contract award after if it is approved by the owner. The fact that the new primavera converts every potential target into a baseline presents a problem since a scheduler can loose track of which one is the real Baseline to the project.
Why would a scheduler want to convert every update into a baseline? What if there’s a claim or the project conditions change and a mitigation schedule is required? How would you go back? I think by having a "Baseline" (AS noted on the P3e/cV5) and and having to create another copy of the project creates a lot of unnecessary work and redundancy in the system that is not required.
Please advise."
Can you give me any feedback on how you coped with this issue? It is very inconvenient for me to have 20 or 30 baselines. any help is appreciated