Fault Configuration Accounting Performance Security
AlarmhandlingAutoDiscoveryServiceUsagePerformancemonitoringPreventionAlarmcorrelationNetworkprovisioningServicelevelagreementsReportgenerationAuthenticationAlarmforwardingAuto back upand recoveryBillingDatacollection andcorrelationSystemAccessControlFiltering andFilter managementServiceActivation
LogmanagementSoftwareupgrade todevicesIntrusionrecoveryThresholdbasedreportingInventorymanagementContainmentand Recovery
What are the architectural challenges to be kept in mind while building an EMS? AndSuggest a suitable architecture for building an Element Management System?
In a real world situation, EV's have to cater to different market segments ranging from small ServiceProviders to large ILECs and the EMS requirements of each of these segments are different. Asimple EMS developed for a small Service Provider may not meet the scalability needs of an ILEC,while a full-featured highly available and scalable EMS that is suitable for an ILEC might be overkillfor a smaller Service Provider. Finally developing a new EMS for each segment may not be apractical or a profitable option.When confronted with the above problem, the EV's attempt to solve it by developing a basic EMSinitially and hoping that it could be scaled up to meet the demanding requirements of an ILEC. Thisstrategy definitely makes sense if the EMS is architected properly. From our experience we' venoticed that in many instances it is not the case because the initial development of the EMS is doneat the last moment and in a rushed manner. Therefore the EV's face an uphill task of scaling up theEMS. The key issue in most of these situations is that the EMS was not initially architected to meetthe requirements of large Service Providers. It is therefore essential to choose the correctarchitecture for the EMS so that it could be implemented to meet the requirements of differentsegments effectively.There are a variety of architectures that could be used to build an EMS. Based on our experience,we recommend that the EMS be developed using JEE architecture. Since JEE based applicationscould be extended to n-tiers (if required) to meet the scalability needs of the customer, we believe itis a very good fit for EMS development.The figure below shows a sample application based on JEE architecture (for more indepthinformation on JEE architecture please visit http://java.sun.com/j2ee/appmodel.html) that has fivetiers. Tier 1 is the client tier. Tier 2 is the web tier (WT). Tier 3 is the presentation tier (PT). Tier 4 isthe application tier (OT) and Tier 5 is the data tier (represented in the figure as the database).