| Pros
|
- Multiple project templates can be set up for various project structures and types.
- Default values can be defined in each template.
- Approval process can be run before the import process.
- Work breakdown structure (WBS) can be automatically generated.
- Fields can be set as “Required” so data entry is not overlooked.
- Workflow roles can be set up to assign responsibility for specific fields and route for completion to the next party.
- Projects created with the project template reside in different tables and need to be approved before being inserted into the Project User Flow table.
|
- The
Allow Edit flag on the Manage Project User Flow screen will determine if the field value will be enabled at the lower levels of the project tree. If
Allow Edit is not selected, the user will not have to decide what value to enter and save.
|
- This process copies data exactly from the cloned project.
- It is useful for setting up a small batch of tasks.
- Clone is available on many screens.
|
- This process adds or updates by replicating existing information across multiple projects/levels.
- It adds basic information and up to 40 other project tables.
- It creates top-level and lower-level projects simultaneously.
- It can be done for one or a range of top-level projects.
|
- The input filed is created as a Microsoft Excel file, which is easy to enter and review.
- 37 project tables are available for import.
- This process selects files to load in the proper order, not necessary to remember what dependencies exist (for example, Project Master before Project Modifications; Link Project Labor Categories to Projects before Link Project Labor Category Rates to Projects).
|
| Cons
|
- Project templates must be maintained to ensure no variance from defined setup.
- Setup and maintenance of workflow and roles must be in check to ensure proper routing for project setup.
|
- Every project level must be manually entered one at a time before the next level can be created. Project Level 1 must be entered and saved before Level 2 can be created, and so on.
- It takes longer to set up all project levels.
- Users must go into each individual application to set up (Revenue Info, Billing Info, Mods, and others).
|
- It creates only one record at a time.
- Cloning the top-level task does not copy the lower-level tasks, and each task has to be cloned separately.
- It requires review and edit after creation.
- Dependencies must be taken into account (for example, Link Project Labor Categories to Projects must be cloned before Link Project Labor Category Rates to Projects).
|
- Manual edits may be required in the destination project to clean up data created from the template project.
- This process copies existing template project structure and setup, leaving no room to vary task lengths and other values.
|
- This process requires some technical expertise to understand requirements for editing templates for import.
|