Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Date Difference between MSP and P6

3 replies [Last post]
Ron Beechey
User offline. Last seen 4 years 21 weeks ago. Offline
Joined: 13 Apr 2016
Posts: 28
Groups: None

I have an activity for 22.5 days in P6 and MSP.   Both have calendars that are 6X10 with Sunday non working.   In P6 I get the dates 3/27/20 to 4/16/20 and in MSP 3/27/2020 to 4/24/2020.  

There is a need to use the MSP plan as an overall roadmap and the detailed P6 file to feed it.  

Anone have any ideas??????

Have a missed setting something in the setting in either product

Replies

Zoltan Palffy
User offline. Last seen 20 weeks 4 days ago. Offline
Joined: 13 Jul 2009
Posts: 3089
Groups: None

it all has to do with hours, calendars and durations

why are you using factions of a day as a planning unit.

Usually frations of day are hours and are generally used for a very granular schedule like in an outage schedule  

Sterling Gallagher
User offline. Last seen 1 year 24 weeks ago. Offline
Joined: 4 Oct 2019
Posts: 14
Groups: None

Hi Ron

How are you transferring the data from MSP to P6?  Try using XerTransfer to import between MSP and P6 and see what you get.  XerTransfer is an add in to Microsoft Project and you can open an XER file in Microsoft Project and save a Microsoft Project file as and XER file for import back into P6.  XerTransfer will translate your calendars correctly between both platforms so if you still get the same issue after using it you can rule your calendar out as the issue.  You can download a trial copy from here https://xertransfer.com/ .  

As far as the date variance it could be any number of things and its hard to comment without seeing your file.  Other than your calendar (most likely the culpret), the other thing to check is that your MSP file has been statused properly and there isnt any retained logic in MSP that P6 accounts for when you F9.

Happy to have a look at your file and provide comment if your interested.  You can email me at scheduling@optusnet.com.au if you are interested.

 

Kind Regards

Sterling Gallagher

 

Tom Boyle
User offline. Last seen 3 weeks 6 days ago. Offline
Joined: 28 Nov 2006
Posts: 304
Groups: None

Hi Ron,

It looks like you’ve missed something in both tools, or there’s something else you haven’t told us.

  1. As you’ve described it, if the activity starts at the beginning of the day on Friday 27Mar’20, then it should end at noon on Wednesday 22Apr’20.  That’s 225 hours (22.5 days at 10 hrs/day) working from 07:00 to 18:00 (with an hour off at midday) each Monday through Saturday.
  2. The P6 dates are incorrect.  They are exactly what you get if you fail to change Hours/Day from 8.0 to 10.0 in the Time Periods dialog of your 6dx10h calendar specification – then enter 22.5 days as the activity duration.  (P6 takes that 22.5 “days” as 22.5 x8 = 180 hours duration.)
  3. The MSP dates are also incorrect, but there is no easy explanation for what you’ve got.  Possibilities:
  • In the project’s scheduling options, you’ve set the hours/day definition to a higher number like 11 instead of 10.  Then entering “22.5 days” gets stored as 247.5 hours instead of 225 hours.
  • Your 6dx10h calendar specification includes around 20 hours of unintended non-working time between the start and finish dates of the activity.  Verify that the workweek shifts for each day are exactly as intended.  Also check for unintended calendar and workweek exceptions.
  • Seems unlikely, but certain combinations of resource assignments can also seem to change the effective calendar of tasks that are not fixed-duration.

Good luck, tom