The export and import from P3/SUreTrak to and from MSP may in all but simply structured project be considered a data export and often a project will calculate differently in MSP to P3/SureTrak. This is due to the differences in the way they calculate and some other issues.
There is an article on my web site at www.eh.com.au which explains the process of conversion and problems and pitfalls.
No, that is not the issue. MS Project uses logic and activity durations to schedule tasks. It just always starts from the project start date and not the status date (which does not exist as explained earlier.)
Importing and exporting from MS Project to Primavera products is very difficult but can be done. The two products have many incompatibilities (other than the lack of a status date.) MS Project only lets you have one relationship between any two activities (Primavera lets you have up to four.) Summary and roll-up levels do not transfer simply. The list is long.
In short, do not plan to transfer schedules back and forth on a regular basis. Life is too short for such constant aggravation.
You confusion is understandable. MS Project does not use the concept of a “data date” or date that the status is valid. There is a date line shown on the screen, but it is always today’s date, regardless of when the status of the project was last taken.
MS Project uses a form of CPM that always begins at the beginning of the project and treats actual durations as if they were estimated durations. If you have three activities in a serial logic stream (say A – B – C) and A and C were complete but B was un-started, MS Project will still schedule activity B to occur between activities A and C (ie. in the past.)
To be completely true-full, MS Project 2002 has added the ability to use a status date. This option is not turned-on by default and the number of options and conditions that you have to decide upon if you do intend to use it will almost guarantee you that your settings will be different from someone else who also attempted to do the same thing.
Spider Project is most functional and powerful professional project management software.
The first SP version was launched in 1993 and since then it has been constantly improved. Today is used in 34 countries though most Spider Project customers are in Russia. Spider Project offers numerous unique functional features and is the only PM software that optimizes resource, cost, and material constrained schedules and budgets for projects and portfolios.
The unique features of Spider Project include Quantity Based Scheduling, Conditional Scheduling, Skill Scheduling, Optimal Resource, Cost and Material Leveling, Resource Critical Path Calculation, Cash and Material Flows Calculation and Management, Trend Analysis, Advanced Risk Simulation and Analysis, Calculation of Success Probability Trends, Calculation and Management of required Project Time and Cost Buffers, Application of Corporate Norms, Management of many Parallel Budgets, Multiple WBS and many others.
Spider Project was and is used for management of many large scale programs in Russia, including $51bln construction program for 2014 Winter Olympic Games preparation.
The application areas where Spider Project is successfully used include Aerospace, Banking, Construction, Defense, Energy, Engineering, Infrastructure, Manufacturing, Metallurgy, Mining, Oil & Gas, Railways, Retail, Shipbuilding, Software Development, Telecommunications, Utilities, etc.
P6-Auditor - Display information from Primavera P6 audit tables in a user-friendly format
Unifier-Archiver - Extract and archive important documents and attachments from Primavera Unifier
Unifier-Loader - Load data into and out of Unifier via Excel
PCM-Loader - Import data into Primavera Contract Management with flexible and secure, template-driven Excel spreadsheets
PCM-Archiver - Extract and archive important documents and attachments from Primavera Contract Management
PCM-Unifier Migrator - Automatically transfer live and historical data from Primavera Contract Management to Primavera Unifier with ease
Create Radically Better Construction Schedules with ALICE Technologies
Use the power of AI to create construction schedules that reduce risk while cutting costs and build time. With ALICE, develop the ideal schedule during preconstruction -- or recover projects that are off schedule and over budget.
The export and import from P3/SUreTrak to and from MSP may in all but simply structured project be considered a data export and often a project will calculate differently in MSP to P3/SureTrak. This is due to the differences in the way they calculate and some other issues.
There is an article on my web site at www.eh.com.au which explains the process of conversion and problems and pitfalls.
Regards
Paul E Harris
No, that is not the issue. MS Project uses logic and activity durations to schedule tasks. It just always starts from the project start date and not the status date (which does not exist as explained earlier.)
Importing and exporting from MS Project to Primavera products is very difficult but can be done. The two products have many incompatibilities (other than the lack of a status date.) MS Project only lets you have one relationship between any two activities (Primavera lets you have up to four.) Summary and roll-up levels do not transfer simply. The list is long.
In short, do not plan to transfer schedules back and forth on a regular basis. Life is too short for such constant aggravation.
Is that mean that exporting from MS-Project to P3 or from P3 to MS-Project,will not Keep the Logic of the schedule?
that mean we only exprot Information about the project ,regardless of the Logic of the schedule isnt it???
Ali
===========================================================
Ali,
You confusion is understandable. MS Project does not use the concept of a “data date” or date that the status is valid. There is a date line shown on the screen, but it is always today’s date, regardless of when the status of the project was last taken.
MS Project uses a form of CPM that always begins at the beginning of the project and treats actual durations as if they were estimated durations. If you have three activities in a serial logic stream (say A – B – C) and A and C were complete but B was un-started, MS Project will still schedule activity B to occur between activities A and C (ie. in the past.)
To be completely true-full, MS Project 2002 has added the ability to use a status date. This option is not turned-on by default and the number of options and conditions that you have to decide upon if you do intend to use it will almost guarantee you that your settings will be different from someone else who also attempted to do the same thing.
Good luck!