Primavera Project Planner Professional

No such animal.

Daniel

We need to establish the software packages we are dealing with, as Primavera Project Planner Professional 4.1 is not an official Primavera Systems product name. The following are the names that Primavera Systems use:

• Primavera® IT Project Office (formerly Primavera TeamPlay®)
• Primavera® IT Operations Management (formerly Primavera Evolve®)
• Primavera® Engineering & Construction (formerly P3e/c™ for Construction)
• Expedition® Professional
• Primavera® Contractor
• Primavera Project Planner® (P3®)
• PrimeContract®
• SureTrak® Project Manager
• Primavera® Maintenance & Turnaround (formerly Primavera Enterprise®)
• Expedition® Professional
• Primavera® New Product Development (formerly Primavera TeamPlay®)
• Primavera® Professional Services (formerly Primavera Evolve®)

Please could you confim whichtwo packages we are dealing with.

Paul E Harris
Eastwood Harris Pty Ltd, Melbourne, Australia
Planning and Scheduling Book Publishers, Training & Consulting
www.eh.com.au

Paul,
Thanks for highlighting.

Yes I was mistaken. Its P3e/c and P3 I’m juggling with. I will check the P3e/c forum category on the grouses...:)

Daniel

Daniel

There are several methods of integrating schedules from two different organizations.

1. The best option I feel is when the two companies are on the same computer network and both to the same software and schedule in the same database. Both P3 (the older Primavera product) and P3e (the newer product) will allow this.
2. The next option is to have them on the same software and one company operates on a checked out or exported copy of a subproject and therefore has the same codes, calendars and resources. It may then be updated and checked back into the master project.
3. The two companies may run on different packages and manually linked by having a set of milestones that are common to both schedules. When the schedule with the driving milestones, typically the designer with the availability of design packages as driving milestones, then these milestones are duplicated in the contractors schedule and an appropriate constraint applied to hold them in place.
4. Summary tasks from one schedule may be manually transferred from one schedule to another to give a complete picture.
5. There are some other tools such as inter project relationships in P3 or using Primavera Contractor (a low cost cut down version of P3e that is limited to 750 activities) that could be able to be used with P3e/c. But to use one of these options in your situation someone will have to change products.
6. Ultimately the option to avoid is regularly importing from a product supporting one file format to a product supporting another file format. This is because usually the two packages calculate differently and there is normally a clean up after importat.

Paul E Harris
Eastwood Harris Pty Ltd, Melbourne, Australia
Planning and Scheduling Book Publishers, Training & Consulting
www.eh.com.au