I was recently contacted by a client who was finding imported projects were not calculating the project costs correctly and had different values to the original project in the database that it was exported from.
Aim
The aim of this paper is to explain why a project that is imported into P6 may have different costs to the original project that it was exported from.
When a resource is assigned to an activity and the default setting have not been changed then:
Earn 25% commission when your network purchase Uplyrn courses or subscribe to our annual membership. It’s the best thing ever. Next to learning, of course.
I carried out the following test with both XER and XML files:
Note: This is not what I would expect to happen!
The obvious solution is to not change resource Unit Rates when exporting project but this is not always feasible.
Another option is before exporting a project is to copy the resource Unit Rate assigned to activities using a Resource Assignments Global Change into in a Resource UDF which may be Global Changed back into the Resource Assignment after importing the project.
Other resource types and P6 software versions may calculate differently but this paper may assist you if you are experiencing issues.
If you want to learn more about Planning and Control with Microsoft Project, please check out my online course here.
Leave your thoughts here...
All Comments
Reply