Graphics used to generate Fire Brigade Maps must contain:
The parent fire object –whose function or object model you select when running the tool.
All the child objects of this parent object. Child objects that are missing in the graphic will not appear in the corresponding map. For example, if you select a function or object model of an automatic zone (whose child objects are detectors) in the tool, you must place both the parent zone and the detectors in the graphics. As a result, the child objects (detectors) will appear in the fire brigade maps of the parent objects, the zones, which will instead not appear. Other objects present on the graphics are not considered for the fire brigade maps. NOTES: - If a graphic contains the parent object with no child objects, then the resulting map includes the parent object. - This function can work for any parent-child object pair, but not for grandparent/grandchild objects, or anyway across more than one relationship step in System Browser. For instance, it works for zone/detectors and section/zones, but not for section/detectors. - The parent-child structure of the generated maps depends on the graphics, which may not exactly correspond to the Management View. For example, if a parent object and its children are split in multiple graphics, then you get multiple corresponding maps with the split sets of child objects.
In complex graphics, the child objects may appear in different depths. In this case, the fire brigade maps generator creates a PDF file with as many corresponding maps as necessary to display all depths with child objects. Note that all such depths must properly display the graphical layers with all graphical information required by the fire brigade map.
If a fire object of the selected function or object model is present in multiple graphics, then the tool generates the corresponding multiple fire brigade maps in the same PDF file.
To get specific access routes in each fire brigade map, you can create dedicated access route layers and associate them to the corresponding fire objects using the Coverage Area Reference property of a bounding rectangle around the object symbols. For more information, see Access Route Layers via Coverage Areas.
