As you note, the MSP interim baseline will only save start/ finish dates. Relationships and constraints will be taken into account when the dates are saved, but as you note, if subsequently changed will not be readily visible. However, it is still useful to give a "visual" indication of progress against interim target schedule.
P3 does enable all of the data to be compared, although the price for this is having to retain all the target programmes.
Having used both MSP and P3, I must admit a preference to P3 as it requires a much more "structured" manner of working as opposed to MSP.
Member for
22 years 10 months
Member for22 years10 months
Submitted by Ronald Winter on Wed, 2003-05-14 10:51
About those 10 saved, interm baseline schedules; are you saving just the dates or are you also saving the relationship, constraint, cost, and resource information as it existed at the time that the interm scheduled was saved?
Without this information, all you have is a nice barchart that proves nothing. Dates are meaningless unless you can show that conditions producing those dates were the same.
Member for
22 years 11 months
Member for22 years11 months
Submitted by Tony McClennon on Wed, 2003-05-14 07:27
Ref MSP Baselines, in MSP2000 it is possible to create up to 10 baselines in the same programme file by using the Tools Tracking Baseline facility, then using the "Save Interim Plan" option. The various Start/Finish date titles can be customised to ensure no confusion arises when trying to save information.
I have used this method to save 6 different baseline plans from various stages of a project. By formatting the bars within the Gantt chart area, it is possible to set up comparisons between the current programme and any of the Interim Plan dates.
Thank you very much for the comments ref MSP versus P3. I suspect the same comments would be made for Open Plan. Can anybody confirm this please? I have always felt the absence of a proper "Timenow" function is MSP is very limiting. Have this been fixed in MSP 2002?
Any comments on how P3, Open Plan compare with Artemis Views?
I feel this discussion is very useful. Hope other Planning Planet members think so.
Member for
22 years 10 months
Member for22 years10 months
Submitted by Ronald Winter on Fri, 2003-05-09 11:06
- P3 you can have 2 baseline whereas in MSP you have only 1.
- P3 can handle more complex data compared to MSP.
- P3 doesnot restrict you for relationships, you can use FS, SS, SF and FF and combination of all, but try the combination in MSP simply not possible.
- P3 is also fairly easy to use as is MSP. Now, the connectivity with Excel, Access and oracle is excellent. People find MSP easy because of its connectivity with other MSoffice products.
I note the comments vs P3. Has anybody got similar comparative experience of Open Plan (OPP and OPD) versus MSP. I suspect similar comments to that registered for P3, but that is not the same as knowing.
Also any comments of Artemis Views versus MSP.
thank you
Member for
22 years 11 months
Member for22 years11 months
Submitted by chu chong keong on Tue, 2002-11-26 11:34
I have been a user of MSP for over 5 years and is currently swithcing to P3. MSP was much easier to handle since I was already familar with MS Office. But the switch to P3 was really tough for me, as I continued with the mindset of MSP.But alas, its easier now with alot of patience and of course with the help of 1 book written by Leslie Feigenbaum. I am the type who like to do self study and working in a small construction companies where the bosses do not believe in sending the staff for training. Having known P3 for 6 months, I feel that P3 is much more "exciting, intelligent, mature, illustrative, dynamic and informative". Whats more in my country, P3 seems to be the elite and in planner/scheduler vacancies, knowledge of P3 is a must.
Im not sure If anyone has done a write up of sort comparing P3 and MS Project.
I have been a user of both products for 7 years now and below are some of my personal view on the matter.
1. Both are effective scheduling softwares.
2. MS Project is more user friendly in terms of data inputing especially entering resource data.
3. P3 is more powerful in terms of transferring data and in organizing data. It gives you a wide latitude in terms of reporting features.
4. Depending on the extent of Project Management consciousness in your company, I believe P3 is suited to a company which is very mature. But for not so extensive and not so complex projects, MSP can do the job as well.
Each has its advatages and disadvantages. MS project is relatively easy to use unlike P3 and older versions were relatively cheep, especially when compared to the cost of P3 and the maintenance contract. However I am lead to believe that Microsoft is changing its licensing and the enterprise version of MS Project 2002 will be much more expensive.
Member for
22 years 11 monthsRE: MS PRoject Vs Primavera
Ronald,
As you note, the MSP interim baseline will only save start/ finish dates. Relationships and constraints will be taken into account when the dates are saved, but as you note, if subsequently changed will not be readily visible. However, it is still useful to give a "visual" indication of progress against interim target schedule.
P3 does enable all of the data to be compared, although the price for this is having to retain all the target programmes.
Having used both MSP and P3, I must admit a preference to P3 as it requires a much more "structured" manner of working as opposed to MSP.
Member for
22 years 10 monthsRE: MS PRoject Vs Primavera
Tony,
About those 10 saved, interm baseline schedules; are you saving just the dates or are you also saving the relationship, constraint, cost, and resource information as it existed at the time that the interm scheduled was saved?
Without this information, all you have is a nice barchart that proves nothing. Dates are meaningless unless you can show that conditions producing those dates were the same.
Member for
22 years 11 monthsRE: MS PRoject Vs Primavera
Ref MSP Baselines, in MSP2000 it is possible to create up to 10 baselines in the same programme file by using the Tools Tracking Baseline facility, then using the "Save Interim Plan" option. The various Start/Finish date titles can be customised to ensure no confusion arises when trying to save information.
I have used this method to save 6 different baseline plans from various stages of a project. By formatting the bars within the Gantt chart area, it is possible to set up comparisons between the current programme and any of the Interim Plan dates.
Hope this helps.
Member for
24 years 1 monthRE: MS PRoject Vs Primavera
Thank you very much for the comments ref MSP versus P3. I suspect the same comments would be made for Open Plan. Can anybody confirm this please? I have always felt the absence of a proper "Timenow" function is MSP is very limiting. Have this been fixed in MSP 2002?
Any comments on how P3, Open Plan compare with Artemis Views?
I feel this discussion is very useful. Hope other Planning Planet members think so.
Member for
22 years 10 monthsMS PRoject Vs Primavera
Imtiyaz, you are mostly correct about Baseline Schedules.
In P3, you can have as many Baseline Schedules as you wish. You can only report against two at the same time.
More importantly for a Scheduler, MS Project does not have a real data date (or status date.) Without this, all data measurements are meaningless.
Member for
22 years 6 monthsRE: MS PRoject Vs Primavera
Major difference between P3 and MSP are;
- P3 you can have 2 baseline whereas in MSP you have only 1.
- P3 can handle more complex data compared to MSP.
- P3 doesnot restrict you for relationships, you can use FS, SS, SF and FF and combination of all, but try the combination in MSP simply not possible.
- P3 is also fairly easy to use as is MSP. Now, the connectivity with Excel, Access and oracle is excellent. People find MSP easy because of its connectivity with other MSoffice products.
Member for
24 years 1 monthRE: MS PRoject Vs Primavera
I note the comments vs P3. Has anybody got similar comparative experience of Open Plan (OPP and OPD) versus MSP. I suspect similar comments to that registered for P3, but that is not the same as knowing.
Also any comments of Artemis Views versus MSP.
thank you
Member for
22 years 11 monthsRE: MS PRoject Vs Primavera
I have been a user of MSP for over 5 years and is currently swithcing to P3. MSP was much easier to handle since I was already familar with MS Office. But the switch to P3 was really tough for me, as I continued with the mindset of MSP.But alas, its easier now with alot of patience and of course with the help of 1 book written by Leslie Feigenbaum. I am the type who like to do self study and working in a small construction companies where the bosses do not believe in sending the staff for training. Having known P3 for 6 months, I feel that P3 is much more "exciting, intelligent, mature, illustrative, dynamic and informative". Whats more in my country, P3 seems to be the elite and in planner/scheduler vacancies, knowledge of P3 is a must.
Member for
16 years 9 monthsRE: MS PRoject Vs Primavera
Im not sure If anyone has done a write up of sort comparing P3 and MS Project.
I have been a user of both products for 7 years now and below are some of my personal view on the matter.
1. Both are effective scheduling softwares.
2. MS Project is more user friendly in terms of data inputing especially entering resource data.
3. P3 is more powerful in terms of transferring data and in organizing data. It gives you a wide latitude in terms of reporting features.
4. Depending on the extent of Project Management consciousness in your company, I believe P3 is suited to a company which is very mature. But for not so extensive and not so complex projects, MSP can do the job as well.
Just this for now.
Se
Member for
24 years 6 monthsRE: MS PRoject Vs Primavera
Each has its advatages and disadvantages. MS project is relatively easy to use unlike P3 and older versions were relatively cheep, especially when compared to the cost of P3 and the maintenance contract. However I am lead to believe that Microsoft is changing its licensing and the enterprise version of MS Project 2002 will be much more expensive.