In P3 you need to create a copy of you schdule as a target baseline (Anyway)
and it only allows 2 target plan.
What is the different if you need to create a copy of your current plan to become a baseline (No different what so ever to P3)
And if you decided not to update and continuous keep a baseline copy of last progress - Fine, this feature is only for the one who would like to keep a aduitable history.
I dont understand your issue, can you explain more
Quote
"Why would a scheduler want to convert every update into a baseline? (Only if you wanted to Why Not)
What if there’s a claim or the project conditions change and a mitigation schedule is required? (Already Explained by Kevin)
How would you go back? (You restore your baseline and become a project as its own)
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 (You have to create another project in P3 how does it create more work for you??)
and redundancy in the system that is not required.(Did you backup your monthly progress update in P3?? Is that call keeping the history, how many time you have difficult to find your monthly backup, and how long does it take to restore the backup and try to do a comparsion)
Please advise."
Alex
Member for
22 years 3 months
Member for22 years4 months
Submitted by Kevin Button on Wed, 2007-01-10 17:35
The baseline capabilities of P3eR5 allows you to set as many baselines as you wish. Baselines may be categorised by type, e.g. Original, What if, Previous period etc.
I find this feature invaluable. By saving a baseline at the end of each period update you are creating a full audit trail.
You can also use any baseline that you wish (Up to 3 at once) In addition, baselines can be re-converted to projects and claim digger used to run a comparison.
Member for
22 years 8 monthsRE: Targets VS Baselines
I agree with both David and Kevin,
In P3 you need to create a copy of you schdule as a target baseline (Anyway)
and it only allows 2 target plan.
What is the different if you need to create a copy of your current plan to become a baseline (No different what so ever to P3)
And if you decided not to update and continuous keep a baseline copy of last progress - Fine, this feature is only for the one who would like to keep a aduitable history.
I dont understand your issue, can you explain more
Quote
"Why would a scheduler want to convert every update into a baseline? (Only if you wanted to Why Not)
What if there’s a claim or the project conditions change and a mitigation schedule is required? (Already Explained by Kevin)
How would you go back? (You restore your baseline and become a project as its own)
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 (You have to create another project in P3 how does it create more work for you??)
and redundancy in the system that is not required.(Did you backup your monthly progress update in P3?? Is that call keeping the history, how many time you have difficult to find your monthly backup, and how long does it take to restore the backup and try to do a comparsion)
Please advise."
Alex
Member for
22 years 3 monthsRE: Targets VS Baselines
I agree with David, there are a number of ways to create copies for future comparison:
1. Set a baseline.
2. Copy the project.
3. Backup your project to XER file.
Any of these options can later be used with Claim Digger or some other comparison tool.
Member for
23 years 11 monthsRE: Targets VS Baselines
M C,
The baseline capabilities of P3eR5 allows you to set as many baselines as you wish. Baselines may be categorised by type, e.g. Original, What if, Previous period etc.
I find this feature invaluable. By saving a baseline at the end of each period update you are creating a full audit trail.
You can also use any baseline that you wish (Up to 3 at once) In addition, baselines can be re-converted to projects and claim digger used to run a comparison.
I am not sure what your issue is !!
Regards
Dave