t if a disaster materializes, including roles and responsibilities of personnel. Operational implications during disasters: Networks need to be resilient to handle operations during disasters when parts of the network may be affected or are completely out of service. Enough planning and thought should be given to ensure resiliency of networks in such scenarios and to develop the ability to provide full or impaired functionality to customers during disaster impacted times. These could include the ability to do intelligent routing, selective service prioritization, and choosing reliability over high performance. Ability to support georedundancy in the product: Geographic redundancy is the ability to seamlessly switch functionality from one or more parts of the network to other redundant parts of the network SO end users of the system face minimal to no impact in functionality. Although this is a complex feature that depends on the complexity of the network and different types of nodes being deployed, when planned and implemented well, georedundancy could be a killer feature in highlighting the advantages of the product over other rivals. Early warning systems: Network roadmaps could be adjusted to accommodate features of an early warning system as required by customer or business inputs in accordance with standards. Backup and restore: In the event of disaster, how would parts of the network become operational again? What information needs to be saved by the system to be able to re-create the necessary service? Would the system be robust enough to recover operations and also allow for the restored system to be controlled via configuration and input to selectively recover operations? Roadmaps could incorporate features that support required functionality, ensuring support for backup and restore at the levels required by the network. Redundancies at different levels: Power redundancy: How does the network use power? What sources of power are used? How long will the system operate if there is a power failure? Should i