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)
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.
Spider Project is most functional and powerful professional project management software.
The first SP version was launched in 1993 and since then it has been constantly improved. Today is used in 34 countries though most Spider Project customers are in Russia. Spider Project offers numerous unique functional features and is the only PM software that optimizes resource, cost, and material constrained schedules and budgets for projects and portfolios.
The unique features of Spider Project include Quantity Based Scheduling, Conditional Scheduling, Skill Scheduling, Optimal Resource, Cost and Material Leveling, Resource Critical Path Calculation, Cash and Material Flows Calculation and Management, Trend Analysis, Advanced Risk Simulation and Analysis, Calculation of Success Probability Trends, Calculation and Management of required Project Time and Cost Buffers, Application of Corporate Norms, Management of many Parallel Budgets, Multiple WBS and many others.
Spider Project was and is used for management of many large scale programs in Russia, including $51bln construction program for 2014 Winter Olympic Games preparation.
The application areas where Spider Project is successfully used include Aerospace, Banking, Construction, Defense, Energy, Engineering, Infrastructure, Manufacturing, Metallurgy, Mining, Oil & Gas, Railways, Retail, Shipbuilding, Software Development, Telecommunications, Utilities, etc.
P6-Auditor - Display information from Primavera P6 audit tables in a user-friendly format
Unifier-Archiver - Extract and archive important documents and attachments from Primavera Unifier
Unifier-Loader - Load data into and out of Unifier via Excel
PCM-Loader - Import data into Primavera Contract Management with flexible and secure, template-driven Excel spreadsheets
PCM-Archiver - Extract and archive important documents and attachments from Primavera Contract Management
PCM-Unifier Migrator - Automatically transfer live and historical data from Primavera Contract Management to Primavera Unifier with ease
Create Radically Better Construction Schedules with ALICE Technologies
Use the power of AI to create construction schedules that reduce risk while cutting costs and build time. With ALICE, develop the ideal schedule during preconstruction -- or recover projects that are off schedule and over budget.
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
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.
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