P6 TO P3

Hello everyone,

Can anyone tell me , how to convert a project from P5 to P3..step by step explanation will be helpful

Regards

Justin,

Qatar

I HAVE CONVERTED PROGRAMME FROM P6.1 TO P3.

DURATION IN P6 & P3 FILE IS NOT MATCHING EVEN START & FINISH DATES ARE MATCHING

PLEASE HELP ME OUT.

THANKS IN ADVANCE

AKSHAY..

P6 to P3? you might encounter problems exporting WBS

Hi Emre



If you create a project for a contractor who won’t use P6, export --> contractor will update --> import with the option "update existing project", it should work if both sides are aware of the differences.

But another idea: It seems a bigger project with some budget. Why not grant the subcontractor access to your database? As version 6 MyPrimavera is usable. With a good security concept the contractor has no chance to get to other data and only your admin will be able to read all his data. It’s a question of confidence of course.

I don’t really like if different software is used.

Regards

Dieter

Hi



An addition: If you have to cooperate with a partner, both must use the same software with the same release state. It is reported, that one of the major problems, Airbus Industries had with the A380 was due to develop different parts with the same software, but different release states. Later, when they had to cooperate, it didn’t work --> redevelopment required.

Cheers

Dieter

Hi Benjamin

For contractual reasons only.

Dieter

I would go to P6 in a heart beat, if there were no conversion issues.



But if I follow your logic: why would you, from your professional experience, convert the file ever? You said yourself that the planning\scheduling should be done in one package.



I was not endorsing one strategy over another.

Hi Benjamin

It depends from which information you want to transfer, if reliable or not.

A change to P6 very soon will lead you to take advantage of the additional features. Most companies nowadays want to have an overall reporting, an overall resource-planning etc. So it will depend on your strategy, which software to use - or which combination. Planning and scheduling must be done in one package only. Never do planning in parallel!

It’s difficult, but if you’ll regard P3-related restrictions, I found the export reliable for all basics. But it is a break of structures. In German, we call interfaces by the translation of "cuts" - they always hurt.

If planning is required by contract for a certain package, follow the contract; if just a monthly data-file is required, do the planning in your mainline package and export the monthly file.

My own opinion!

Regards

Dieter

We are going through the same thing with my company with the Army COE. I have been told by a company in Dallas, IMS, that has exclusive rights in Texas to deal Primavera that the backwards conversion from P5\P6 to P3.1 is not reliable. You have a couple of choices once you migrate to P5\P6:



1) Use the converted schedule and correct the conversion errors.

2) Use P3.1 to create the schedule, while maintaining both systems in parallel. There are obvious tradeoffs.

3) Try to talk the "owners" into converting to P5\P6. This migration is inevitable, in my opinion.



This all depends on your client. The Army COE does not make software decisions over night. However, if your client is the COE, I have never found languange in a contract the compels the contractor to use P3.1. In fact, the whole rationale behind using the SDEF file format was to allow their contractor’s to use alternate software, even though P3.1 has been tested to produce a reliabel SDEF compliant data dump.

Please ignore the incomplete last paragraph in my last posting.

Emre,



You said "I have to continue submitting my files using P3.1 according to my contract. If I purchase P5 or P6 and use, will it be efficient to convert P6 file to P3 format when it is required?". And the simplest answer with the information you provided is NO.



If you have to submit your files in one software, why one earth do you want to use another software? This not an upgrade. This is completely new software. As between any two software, all features of one is not supported by the other. Though P3 3.1 and P5/P6 come from the same company, they are different software (not really upgrade).



Three conditions I will start using P5/P6 or any other software for a contract which needs submission in P3, if I were in you place are:

1. My P3 licence is being revoked and replaced by P5 or P6.

1. All my other programmes have to be planned in that new software.

2. For the existing contract where programme have to be submitted in P3 foramt, I do not need to import the project back to P5/P6.











If you only have to submit

And the other thing is that the moment you start using P5 or P6, it is just natural that you start using its features (which are not supported in P3) only to be disappointed that exp

Hi Emre

There are many reasons to change to Primavera Enterprise.

We use P6 as a mainline but still have old p3 licenses for cases as yours.

My opinion: Use P3 for this project it is an excellent tool as well.

The export from P6 to P3 3.1 will work reliable if you’ll regard P3’s restrictions for a project planned and controlled in P6:

- Id-lengths and restrictions

- Only use one hierarchy level

- no roles

....



Have a look into the pdf on the P6 documentation cd: Moving from P3 to P6 (or P5) - a good overview on the differences.



Good luck for your project!

Dieter