istics Required in EMS The characteristics required in an EMS solution are: User-friendly interface: The interface to work with the EMS (EMS client or web client) needs to be an intuitive, task-oriented GUI to allow opera- tions functions to be performed in the shortest possible time with minimal training. Quick launch: This would enable a user working at the NML, SML, or BML to launch any EMS desired (when multiple EMS are involved). Troubleshoot NE: It should be possible for a technician to directly log into any NE from the EMS that manages it for ease in troubleshooting an issue. Single-sign-on is a popular capability that allows the same user id and pass- word to be used when logging into the applications involved in different layers of TMN model that will be discussed in the next chapter. Low-cost operations platform: This would help in minimizing the total cost to own and operate the computing platform on which the EMS runs. Ease of enhancement: New features need to be added to an EMS product and the product might require easy integration and work with another product. Some of the techniques currently adopted in the design of such systems is to make it based on service oriented architecture (SOA), comply to COTS software standards, and SO on. Fundamentals of EMS, NMS and OSS/BSS Context-sensitive help: This reduces the training required for technicians. Context-sensitive help can be associated with any functionality in EMS GUI. With event/fault, a context-sensitive help would involve a quick launch link for information on that fault. Another usual feature in applications is a "?" icon that can be dragged and dropped to any part of the application and a help is launched on how to work on the specific part where the icon is dropped. Access anywhere: This would require a person in any remote location to access the EMS. As already discussed most EMS now provide a web-based interface SO that with secure connection technique the internet can be used to access company intranet and launch the web-based EMS. Effecti