twork. This func- tionality cannot be specified as an essential feature of inventory management as separate solutions exist and are usually used to handle network maintenance and restoration. We have discussed network provisioning, planning the network, and also map- ping the network design to inventory. It would be good to have a short discussion on network design. There are several network design creation modules that can deliver network designs with different configurations to choose from, SO that the service provider can make an optimal selection based on the service provider's requirements. Since the network design has to represent the configuration of all the elements in the network, the designs are mostly graphical with capabilities to drill down on OSS/BSS Functions specific equipment and get details on its suggested configuration. The planning performed prior to network design helps the service provider to make appropriate change in configuration for a smooth provisioning and good network performance after deployment. Event or rule-based network design is usually used for network design. Event driven systems can be programmed to the dynamic of taking corrective actions to fault scenarios. This intelligence is specified as a rule. It is also common to do logical modeling whereby elements that can be grouped are considered one logical entity based on the services that are provided or executed on these elements. This makes it easier to define configurations, where attribute values are set on the logical collection rather than on individual elements that make up the collection. Network templates make design much faster and easier by offering the ability to define and maintain rules governing the ordering, design, and provisioning of various logical network systems. These templates have default values for configuration that can be reused without defining the value each time a new design has to be created, which is similar to a previous setup. The network design module can be used not just for setting the conf