Creating or moving models
|Top Previous Next|
You can create a (project) model by importing/exporting an existing model or by creating a model from an existing object. In the example below, a model is based on a project.
Creating a model from an existing project
Step 1. Go to a folder in the module Project Management.
Step 2. In the section Projects, go to the project.
Step 3. Select the project on which you want to base the model by selecting the correct row.
Step 4. Click Model.
Step 5. Enter the data for the model.
Step 6. Confirm by clicking OK.
Step 7. The model is now displayed under the tab Models, in the section Project models.
Step 8. If the project model should be available for other projects you can either export/import the model or move it to the target location. The difference is that export/import makes a copy of the model and the model is in the original location and the new location. When moving the model, it is only available in the new location.
•Select the model in the Project Models section and click Export; Save the file.
•Go to the Organisational Unit with Project Management, to the tab Models.
•Click in the Project Models section Import, enter the data in the pop-up screen and click OK.
•Select the model in the Project Models section and click Move; a pop-up appears
•Choose the target location and click OK.
It is dependent of the project's starting location (OU and map) which models are available. Below is an overview of which models are available when starting a project. Please
note the difference between an OU and a map!
•All models that are in the map (on tab map > models).
•All models that are in the parent folders (within the OU; on the tab map > models).
•All models that are in the OU tab models.
•All models that are in the parent OUs on the tab models.
This implies that for two locations the models are not available:
•The models that (in the same OU) are in other maps at the same level, i.e. adjacent maps (on the tab map > models).
•The models that are in the folders of parent OUs (on the tab map > models).
Note: This way of working also applies for other types of models.
Note: When making adjustments to a Project Model:
•These adjustments do affect existing projects: property pages, existing automated reports, approvals of products, custom layouts of products, widgets behaviour costs and hours.
•These adjustment do not affect existing projects: staging/planning, linked resource pools, new automated reports.
Note: When roles are assigned to users in a project model, these are not transferred to a project!