Occasionally you might want to forward parts of a project to a third party for further processing. In this case, you can define partial projects that you "cut" out of the overall project (Using Visum: Exporting a partial project). These partial projects can be edited as independent projects and later be integrated into the overall project again. PTV Visum ensures that the newly created objects are integrated properly.
In order to avoid having to load numerous modifications, during partial project export, you can raise modifications for the base version that are always used in the "cut out" part of the project. During the integration process, the merging of these modifications will be taken into account.
Should you later wish to integrate the subproject into the overall project once again, do not change the base version, the exported modifications or the modifications integrated into the base version of the subproject. During the "Export partial project..." process, you can lock these objects in the overall project to ensure trouble-free integration. In addition, you may also lock objects in the exported partial project to avoid unintended changes to the base data.
If you are working on an extensive project, you can assign the creation of modifications in particular to several users. The prerequisite is that the project database of the scenario management is administered in SQL server (Using Visum: Creating a project for scenario management). The modifications edited by several users are then locked for editing by other users. This also applies to modifications or scenarios depending on the modifications used. The Multi-user mode tab provides an overview of all locked objects. The depicted approach ensures that scenarios and modifications are kept consistent. We recommend the use of the multi-user mode if several users want to work on one project. With the conversion functions provided, you can convert your project back to a standard SQLite database without multi-user mode at any time.
|
Note: If several users are working on creating model transfer files, they might use the same code for a new network object, although the content of their objects differs. PTV Visum will recognize these code conflicts when you use the model transfer files in scenario management. So, if the same code has been assigned twice, one of the objects is automatically assigned a new, unique code. |
