Avoid creating a schedule in Microsoft Project, importing and updating it in i-lign, then exporting to Microsoft Project and then repeating the process.
Do not use this approach. It is possible, but the way the import and export works would place a number of constraints on the way schedules are prepared and maintained. These constraints include:
-
When a schedule is exported from i-lign to Microsoft Project, you cannot add new resources to the Microsoft Project file, because re-importing the schedule back into i-lign does not provide a facility to select i-lign resource counterparts for the newly added Microsoft Project resources. You will not be able to reimport the file into i-lign unless it has the same resources that were exported from i-lign.
-
When a schedule is exported from i-lign to Microsoft Project, you cannot copy and paste existing tasks and milestones in the Microsoft Project file. During the export from i-lign, i-lign reference numbers are recorded against each task and milestone. Copying and pasting existing tasks and milestones duplicates these 'unique' reference numbers, and you will not be able to reimport the file into i-lign.
There may be additional constraints to the two above.
Recommendation
Use the i-lign Gantt as the master schedule. The original schedule can be created in either Microsoft Project or i-lign, but once imported into i-lign, i-lign should be the master from that point forward. The schedule can still be exported to Microsoft Project to distribute to people who do not have access to i-lign or to perform analysis such as critical path analysis / what if analysis.
