Hey Guys & Gals,
Need to pick your brains on a little issue......
I have compiled an integrated schedule of 5 projects in (Optional Client 8.1) clearly showing their interdependencies and Key Interface Milestones so select data can be reported to the board.
Due to the typical (non) availability of each PM, although each project has the same Data Date, in the first instance I copied the Schedule ( and then on this copy I deleted the other projects I didnt need) so I could update & keep the original data intact as I rescheduled to a more current date.
Still with me.....? Good :-)
Now, when I copy this 'standalone' project back into the WBS of the integrated schedule, the calendars are automatically changed to the global default calendar. This changes all the 7 day calendars in my schedule back to the default 5 Day.
Each project should be scheduled on its own Data Date (as clearly stated when scheduling multiple projects simultaneously), but for some reason it isnt maintaining the correct calendars and all my weekend activities are pushed out to the Monday etc.
Does anyone know why it does this? And more imprtant, how to fully maintain each Activites correct calendar?
Scheduling the entire programme just for one specific element isn't aviable option as it would take far too long to update the remaining projects as a result - they will have all been scheduled to the current Data Date but with no update!
I also have 8.3, haven't tried importing as yet but I'm guessing it's no different.
Any help muchos gracias
Walshy
Neil,
Make sure that the default calendar is the same calendar as your activities.
Each project should be scheduled on its own Data Date (as clearly stated when scheduling multiple projects simultaneously
- Each Project should be scheduled on its own Data Date if Individual Simultaneous Opened Projects are created under any EPS node but not on a single WBS.
Hope this will help.
Raymund
Neil,
Thanks for clarifying the issue, I was hooked on a similar problem while importing XER files and then within P6 saving the same version as a Baseline and as a separate project file. We, including regular P6 users, could not figure it out either, you are right in this case it is not an issue with import/export XER files. We solved the issue by brute force, by reassigning calendars and assumed we did something wrong during export/import.
It seems like it might be a BUG.
Good luck,
Rafael
Quick Update.....
I have managed to get the updated project into the WBS structure now by using the 'update existing' option, but for some bizarre reason, the entire project is still set at the old Data Date of 07-Apr-13 and not greyed out, which I would have expected as the newly imported project has a Data Date of 22-May-13!
This is very frustrating as when I schedule, the entire programme is being scheduled from April so I have finish dates prior to actual start dates!
Come on Primavera sort this issue out!!
walshy
Thanks for the info Rafael, but this doesn't really help me at all....especially as you dont really use P6 :-(
It's not the importing / exporting which is the issue, it's the 'dropping in' to the WBS afterwards which causes irregularities.
Hopefully somebody who has had the same issue as me will join in at some point and give their 2 cents worth. Or I will get a solution Mr Paul Harris :-)
I'm not familiiar with Spider Project and don't have access to it either.
Thanks again anyway Raf
Walshy
Probably if you are using Portfolio the best way to avoid conflict is to use a different prefix [unique for each job] for Calendars and Resources. Consider using such prefix for Global as each Job might have his own definition of Global. Even resources common to a portfolio shall be identified using a unique prefix.
To avoid such issues specific to P6 you can learn by looking on the WEB at the NYDTOP requirements for P6.
I use Spider Project and before incorporating a new imported job to a portfolio I can make the changes very easily.
I do not use P6 but at times import/export from/to my clients using other software. I am not proficient with P6, know just enough to understand how best to transfer data to/from it to my software.
I am also interested in understanding the resource loading limitations of P6 as to keep some schedules within the limited functionality of P6. At times extra functionality of Spider can be used for my transfers, one such functionality is the ability to transfer resource dependencies as links, good when P6 resource leveling is so poor that it makes sense to transfer a superior resource leveling from Spider using resource dependencies as links.
Good Luck.
Rafael