Hello,
Currently there are some limitations on the Import functionality that limits the ability to import an entire project plan. Cases where an improved import/export would be beneficial:
The areas that the import function is weak in:
I propose to use the WBS number to assign dependencies and Child/Parent relationships with importing/exporting. This would require the following changes for the import/export functions:
Consider the following structure:
A column for the WBS number would be added. The WBS number would be an abbreviated version that did not include the project digits. Referring to the above structure, for the import/export the WBS would would drop the leading 1 and would become:
During import, the WBS would be used to assign Parent/Child relationships.
For dependencies, additional columns would be added: Predecessor WBS, Predecessor lag, Successor WBS, Successor lag.
Again, the WBS numbers used in these columns would not include any digits for the project number.
One additional change would be to consider any activity that has a duration of 0 to be considered a Milestone.
With these changes it would be much easier to create templates for project plans that will take less time to setup in Projeqtor.
Regards,
Ron
Currently there are some limitations on the Import functionality that limits the ability to import an entire project plan. Cases where an improved import/export would be beneficial:
- Copying a Project plan from one Projeqtor server to another
- Creating templates for project plans that can be easily imported, speeding up the process of creating new plans
- Importing from Microsoft Project
The areas that the import function is weak in:
- Does not import/export dependecies
- Cannot import Child/Parent relationships from Microsoft Project
I propose to use the WBS number to assign dependencies and Child/Parent relationships with importing/exporting. This would require the following changes for the import/export functions:
Consider the following structure:
WBS | Name |
1 | Project One |
1.1 | Activity One |
1.1.1 | Activity One, Child One |
1.1.2 | Activity One, Child Two |
1.2 | Activity Two |
A column for the WBS number would be added. The WBS number would be an abbreviated version that did not include the project digits. Referring to the above structure, for the import/export the WBS would would drop the leading 1 and would become:
WBS | Name |
1 | Activity One |
1.1 | Activity One, Child One |
1.2 | Activity One, Child Two |
2 | Activity Two |
During import, the WBS would be used to assign Parent/Child relationships.
For dependencies, additional columns would be added: Predecessor WBS, Predecessor lag, Successor WBS, Successor lag.
Again, the WBS numbers used in these columns would not include any digits for the project number.
One additional change would be to consider any activity that has a duration of 0 to be considered a Milestone.
With these changes it would be much easier to create templates for project plans that will take less time to setup in Projeqtor.
Regards,
Ron