While importing a project plan from Microsoft® Project to Rational® Project
Conductor,
the project milestones, tasks, dependencies, and so on are correctly
mapped. Similarly, mapping is taken care while exporting the project
from Rational Project
Conductor to
an XML file.
The following table illustrates how project elements in Rational Project
Conductor map
to those in Microsoft Project
2007.
Table 1. Import and export mappingRational Project
Conductor |
Microsoft Project
2007 |
Project |
Project |
Summary task |
Summary task |
Task |
Milestone |
Task |
Task |
Risk |
Summary task (task will be child of summary
task ) |
Defect |
Task |
Issue |
Task |
Assignment - task (no project level assignment) |
Assignment - task |
Resource |
Resource |
Dependency - task |
Dependency - task |
Resource assignment mapping is done on task-level assignments,
but not at the project level. If the rates are assigned to the resources
in Microsoft Project,
the same rates are assigned to the mapped resources in
Rational Project
Conductor.
You can see rates at the project level in the Resources view. Import
and export mapping supports only finish-to-start dependency that is
created among tasks in Microsoft Project. Remaining dependencies available
in Microsoft Project are not imported. Similarly, import and export
of the projects support only As Soon As Possible and Finish No Later
Than constraints. Remaining constraints available in Microsoft Project
are not imported.
A task with multiple assignments in Microsoft Project
is imported as Summary Task with tasks under it. For example, you
have a task created in Microsoft Project
with three assignments Resource1, Resource2, and Resource3. After
importing the task to Rational Project
Conductor,
you will have a Summary Task named T1 with three child tasks, T1_Task1,
T1_Task2, and T3_Task3 created under it. Resource1 will be assigned
to T1_Task1, Resource2 assigned to T2_Task2, and Resource3 assigned
to T3_Task3.