During an emergency, you will need to access information regarding your building systems and their status. Maintaining accurate and up-to-date information about the critical systems for your buildings can help first responders (fire fighters, police, and rescue personnel) contain a dangerous situation, prevent further damage, and protect the safety of employees.
Building systems are rarely, if ever, independent entities; rather, they depend on each other to operate. For example, most building systems rely on the building's base electrical service for power; computer systems often need supplemental cooling to operate properly. Mapping these system dependencies will help you quickly determine each system's operational status during an emergency.
Note: System Types, Systems, and System Dependencies can also be entered using the ARCHIBUS Smart Client environment's "Define System and Zones" process. The following instructions are written for Web Central users; Smart Client users can adapt accordingly.
First, establish the system types in your buildings, so that you will be able to categorize your systems.
Next, record your vital building systems information:
- System Code – Enter a unique code for the system.
- System Type – Choose a system type from the validating System Types table.
- Building Code – Choose the building in which this system is located by selecting a building from the validating Buildings table.
- Description – Enter a description for the system.
- Recovery Status – The default is "No Status." Leave this field as is. In the event of an emergency , staff will use this field to update system status.
- Vendor Contact – Enter the name of the vendor or person responsible for the system.
If a system is dependent on other systems, you should document this dependency. A master system is a building system on which other building systems rely.
Note: You can create multiple levels of dependent systems. For example, in the sample HQ data, the electrical system is master to the exhaust system, which, in turn, is master to the network system.
Choose Add New.
Note that you can specify this propagation behavior for each dependent system, not just for the overall master system.
For example, enter System A as the master, System B as a dependent, and System C as a dependent. For System B, enter a value of Yes in the Propagate Status field; for System C, enter No as a value for the Propagate Status field. If System A has a Recovery Status of Offline, then System B automatically inherits the Offline status from System A, but System C does not inherit this status.
If you have floor plan drawings, CAD users at your site can map the areas on each floor that are served by a building system. For information, see Draw Zones .
Copyright © 1984-2019, ARCHIBUS, Inc. All rights reserved. |