We are currently implementing Contractor with one of our contractors as they are using MS Project and it was causing unneccesary additional work for us with fortnightly updates. We exported the contractors work from the main schedule (we use P3e), tidied it up and exported it to them to import in to their Contractor. This way we are both working off the same schedule. They can then do their own updates and send it to us for us to import in to the main schedule. As they have more than 750 activities we suggested that they break their schedule down (ie Stage 1, Stage 2) and create individual projects per stage. It is limiting with only 750 activities and this was the best solution.
Member for
20 years 10 months
Member for20 years10 months
Submitted by Tomasz Wiatr on Fri, 2005-01-28 09:46
We have not problem with effects of comparision P3 vs. PE because PE is simply successor of P3 (PE is better P3, meybe too heavy, but better). Your opinion in the aspect of missinformation about novelty of "programme management" features in PE are not right assumption, of course. Old P3 was able to control all projects in organisation too - in Concentric PM suite, i.e. with SureTraksPM on sites and with "one" P3 in the "headquarter"! Today schedulers use P3 like a standalone system, but P3 is concentric PM engine "for all projects" in organisation, like a PE (simmilar purpose) :-)
"Problem" in this sub-group of forum is comparison of FULL PE (specially Pe/c) and RESTRICTED Primavera Contractor because this comparison is worst than P3 vs. ST, because ST has not any restriction in the number of tasks, and other too. This kind of restrictions we know only from educational version of P3 (200 tasks), and working model (demo) of P3 (40 tasks). It is our "problem", not power of Pe/c engine but "deadlock" on the engine of Primavera Contractor! Primavera Contractor is the same branch (AEC) with Pe/c so we want to love Primavera "Light", but this is difficult love :-(
Good Luck
Tomek
Member for
21 years 6 months
Member for21 years6 months
Submitted by Martin Tinsley on Fri, 2005-01-28 08:33
I am not familiar with the 750 task limited product but if you are an experienced planner and understand your business well, you must have a handle on the magnitude of your projects prior to purchasing the software.
I think also that it is fair to say that P3 and P3e are very different products in that P3 is very much rooted in the construction industry for on off large projects whereas P3e lends itself to a programme of many concurrent projects. P3 needed tidying up at some stage as there are some messy areas, for me the worst being the Auto Cost Rules. The Worst mistake Primavera may have made is that many construction companies who are already using p3 without any problems, take the line if it aint broken, dont fix it and thus the take up of P3e might not be that fast.
Ultimately there isnt a mainstream product that can compete with Primavera for organisations that want to seriously and successfully get to grips with planning projects.
Member for
20 years 10 months
Member for20 years10 months
Submitted by Tomasz Wiatr on Thu, 2005-01-27 13:44
In other part of this forum I have written question related with comparrision of Pe/c vs. Primavera Contractor (redirected here by moderator - thanks) and I see that situation is not good :-(
Restriction of "max 750 tasks per project" it is not friendly restriction. Meybe number 750 is not small but it is bad condition for all "friends" of Primavera on the world! Comparision of Pe/c vs. Primavera Contractor is worst than comparision of P3 vs. ST, specially that ST have better graphics than P3 (even). But new Contractor is "sad joke", specially this ... last 50 tasks. Worst is only 699 tasks per projects :-(
Congratulations to Ahmad Rashidi with him list of features. I am waiting for it fom Primavera, but I have it here on the our Planet :-) I must to rethink the buing of Contractor accurately. I am unhappy with it.
I think Primavera made a fatal mistake having try to map a product line same as Surtrack and P3. With Primavera Contractor and P3e. And try to compete with MSP
However, I guess what you get is what you paid for. Unless Primavera plan to downgrade their P3e $ line to a more attractive pricing model, the growth of users for P3e will be slow.
I do find P3e is very powerful and getting better and better in each version. Still their price is far too dear for a small firm. To tackle that market and still maintain the big corporate users is a very difficult task.
I guess you cannot please two women at the same time.
Member for
21 years 4 months
Member for21 years4 months
Submitted by ahmad rashidi on Tue, 2004-09-21 22:00
Member for
20 years 11 monthsRE: Primavera Contractor 4.1
We are currently implementing Contractor with one of our contractors as they are using MS Project and it was causing unneccesary additional work for us with fortnightly updates. We exported the contractors work from the main schedule (we use P3e), tidied it up and exported it to them to import in to their Contractor. This way we are both working off the same schedule. They can then do their own updates and send it to us for us to import in to the main schedule. As they have more than 750 activities we suggested that they break their schedule down (ie Stage 1, Stage 2) and create individual projects per stage. It is limiting with only 750 activities and this was the best solution.
Member for
20 years 10 monthsRE: Primavera Contractor 4.1
Dear Martin,
We have not problem with effects of comparision P3 vs. PE because PE is simply successor of P3 (PE is better P3, meybe too heavy, but better). Your opinion in the aspect of missinformation about novelty of "programme management" features in PE are not right assumption, of course. Old P3 was able to control all projects in organisation too - in Concentric PM suite, i.e. with SureTraksPM on sites and with "one" P3 in the "headquarter"! Today schedulers use P3 like a standalone system, but P3 is concentric PM engine "for all projects" in organisation, like a PE (simmilar purpose) :-)
"Problem" in this sub-group of forum is comparison of FULL PE (specially Pe/c) and RESTRICTED Primavera Contractor because this comparison is worst than P3 vs. ST, because ST has not any restriction in the number of tasks, and other too. This kind of restrictions we know only from educational version of P3 (200 tasks), and working model (demo) of P3 (40 tasks). It is our "problem", not power of Pe/c engine but "deadlock" on the engine of Primavera Contractor! Primavera Contractor is the same branch (AEC) with Pe/c so we want to love Primavera "Light", but this is difficult love :-(
Good Luck
Tomek
Member for
21 years 6 monthsRE: Primavera Contractor 4.1
I dont agree at all with you guys!
I am not familiar with the 750 task limited product but if you are an experienced planner and understand your business well, you must have a handle on the magnitude of your projects prior to purchasing the software.
I think also that it is fair to say that P3 and P3e are very different products in that P3 is very much rooted in the construction industry for on off large projects whereas P3e lends itself to a programme of many concurrent projects. P3 needed tidying up at some stage as there are some messy areas, for me the worst being the Auto Cost Rules. The Worst mistake Primavera may have made is that many construction companies who are already using p3 without any problems, take the line if it aint broken, dont fix it and thus the take up of P3e might not be that fast.
Ultimately there isnt a mainstream product that can compete with Primavera for organisations that want to seriously and successfully get to grips with planning projects.
Member for
20 years 10 monthsRE: Primavera Contractor 4.1
Hi everyone,
In other part of this forum I have written question related with comparrision of Pe/c vs. Primavera Contractor (redirected here by moderator - thanks) and I see that situation is not good :-(
Restriction of "max 750 tasks per project" it is not friendly restriction. Meybe number 750 is not small but it is bad condition for all "friends" of Primavera on the world! Comparision of Pe/c vs. Primavera Contractor is worst than comparision of P3 vs. ST, specially that ST have better graphics than P3 (even). But new Contractor is "sad joke", specially this ... last 50 tasks. Worst is only 699 tasks per projects :-(
Congratulations to Ahmad Rashidi with him list of features. I am waiting for it fom Primavera, but I have it here on the our Planet :-) I must to rethink the buing of Contractor accurately. I am unhappy with it.
Tomek from Poland
fanatic of UK-Pertmaster and US-Primavera
Member for
21 yearsRE: Primavera Contractor 4.1
hi all,
my first post! :)
i agree on the fatal mistake part, i have my reservations on the reliability of p3e or p3ec compared to p3.
cheers.
Lili
Member for
23 years 8 monthsRE: Primavera Contractor 4.1
As a start on enterprise, seems this Primavera Contarctor 4.1 is better, not much investment but have similiar enterprise environment.
I think there is some improvement to user on the interface but not much benefit on overall picture on enterprise.
Member for
22 years 8 monthsRE: Primavera Contractor 4.1
I think Primavera made a fatal mistake having try to map a product line same as Surtrack and P3. With Primavera Contractor and P3e. And try to compete with MSP
However, I guess what you get is what you paid for. Unless Primavera plan to downgrade their P3e $ line to a more attractive pricing model, the growth of users for P3e will be slow.
I do find P3e is very powerful and getting better and better in each version. Still their price is far too dear for a small firm. To tackle that market and still maintain the big corporate users is a very difficult task.
I guess you cannot please two women at the same time.
Member for
21 years 4 monthsRE: Primavera Contractor 4.1
Exactly! I have tried to import a RM10mil worth of project with 1051 activities and guess what!?...
1. Maximum activities per project: 750 only.
2. Only 1 project can be opened at a time.
3. No project group/member structure. I was hoping it works like P3 3.1.
4. Have Send Project feature. It works. Nice.
5. Export to MSP in MPX only even though I have MSP 2002 on my PC.
6. No Web publishing wizards.
7. No Risks, Issues, Thresholds, WPs & Docs, Tracking Layouts. etc.
8.Import/Export to EC 4.0 no problem!
Happy venturing guys!
Rashidi.
Member for
21 years 8 monthsRE: Primavera Contractor 4.1
Not me, and most probably I will never venture even to try a software that is limited to 750 activities per project.
Although our projects on average are about 400 to 600 activities I would advise not to invest time and risk finding yourself short in the long run.
This is certainly a downgrade if compared to Suretrak, not to mention P3, Open Plan, Artemis, Spider .....