#DicasOZmap | Backbone design and design element exchange
OZmap allows you to separate your projects into parent project and child project, helping you to document your backbone more efficiently and avoiding duplication of elements.
O parent project this is the main project, where the central part of your network is, since the child projects will be their derivations. The great advantage of documenting in this way is that elements present in the parent project will be shown in the project areas in common with its children, but the opposite will not be true, and elements of a child project will not appear in its parent, thus allowing you do the individual documentation for certain regions keeping elements that connect them.
To designate a project as a parent, simply go to your child's data and select its name in the “Parent project” field.
If the project you want to assign isn't appearing there, it's worth checking if it doesn't already have a parent project for it. That way it won't appear, because OZmap doesn't allow the existence of a “Grandfather Project”.
As soon as your projects are linked, the elements of the main project will already be appearing in the corresponding areas in the secondary projects and, in special cases, it is possible to visualize boxes in reverse, from the child to the parent, just by right clicking on the box you want and select the option “Share box with parent project”.
Once shared, the box will have a blue triangle in your drawing, similar to the image below, helping to identify it. The triangle facing up indicates that the box is being previewed in its source project and a downward facing triangle that is being previewed in the parent project.
When opening this box, it will also be possible to identify its origin by name, which will indicate in parentheses the project to which it belongs.
The connection made between projects is also very useful to carry out the action of transfer of items from one project to another. Counting on a parent and child link between the project where the element is and the destination project, it is possible to select the option “Switch to a parent/child project”, for that just open the element in its source project and click with right click on it, looking for the indicated option, as shown in the image below:
This can be done with all elements such as boxes, cables, clients, among others.
You can also change elements in batch, for that, the first step is to generate an area report (to learn how to do this operation, click here).
Next, you can decide whether you want to transfer all equipment from that region or just a certain category. In the first option, just go to the “Change project” button on the “General” tab of your report.
And then select the target project.
To change specific elements, you can go to their respective report page and select which ones will or will not be transferred, following the same process immediately afterwards.
When transferring cables and boxes separately, we recommend that when transferring from parent to child, the boxes are changed first, then the cables, and from son to parent, the cables are changed first, then the boxes. Doing the process in a different order can lead to the automatic creation of boxes at the ends of the cables, as the original boxes will have remained in a project that the other does not have access to.
It is also interesting to note that the link between projects cannot be broken while an element of the parent project is connected to the child or vice versa, the connection needs to be removed so that both projects can lose their inheritance.
For more information about Backbone, click here.
Now that you've learned how to connect your projects, how about optimizing your backbone documentation?