 be mapped to specific events to handle scenarios the same way it would be done by a network professional. Event management solutions display event records and take corrective actions for specific events. A network operator uses a sequence of events to identify a particular problem. Similarly, the event management system needs to collect and correlate events to identify the event pattern that maps to a predefined problem. Event management solutions collect data from multiple network elements. These events are filtered and the event is checked against specific event pat- terns for match. If the events can lead to a pattern, then such events are stored in a repository for reference. For example, if three SLA jeopardy events on the same service raises an e-mail to the operator, then each SLA jeopardy event or the event count needs to be stored. 43. Network design: These solutions help to develop a design model of new ele- ments to be included in a network and to design network configurations that are needed to support new services. First the network and its elements are modeled and simulated before assigning the design to appropriate systems that support the implementation. Network design will include physical design, logical design, and soft- ware design. For example, multiple call servers need to be placed in a rack. The physical design will detail what shelf and slot each of the servers will be placed. The logical design would segregate the servers into call processing servers and management servers to detail the interactions. Software design will drill down into the software packages and features that should be avail- able on the servers. 44 Network domain management: These applications provide interfaces to hide vendor specific implementations. Using domain management applica- tion, legacy functionalities are exposed as standard interfaces compliant to Fundamentals of EMS, NMS and OSS/BSS standards like MTNM, OSS/J, and MTOSI, following standard data models like SID and CIM. The net result is an in-domain activ