User talk:Gabbynizri

Critical Situation Management

Use of the phrase ‘Critical Situation Management’ (CSM) has been typically reserved for managing security emergencies or natural disasters at the national level, or for managing other life and property threatening situations.

Ayehu proposes the use of CSM as a business’ capability to sustain key business functions when normal operations at any scale have been disrupted. According to this concept, CSM is a new niche of the network availability market. CSM offers a complete, automated and proactive solution for downtime pain by providing accurate information along with the necessary resources to the right people, and achieving effective and well-timed event resolution. At the same time, and without compromising the downtime solution it entails, CSM is set to ensure the on-going uptime business operations, serving as an insurance policy for protecting the entire revenue stream of a business. A CSM system can be depicted as a virtual situation room to keep a business resilient. Whether in its downtime or uptime capacity, CSM monitors the status of events critical to core functionality of the business, coordinates between them and the business resources, and achieves optimal resolution. Harnessing a CSM system’s full potential can improve a business’s financial performance and enhance its uptime operations while safguarding it from potential outages and degradations. The EyeShare EyeShare, Ayehu’s flagship product, is the first end-to-end Critical Situation Management Solution.

EyeShare CSM Methodology

EyeShare CSM methodology incorporates four core processes which can be depicted as follows:
 * Event profiling and real time analysis - monitoring the status of events critical to core functionality of the business
 * Solution building –matching events and classifying them into an appropriate profile
 * Communication - coordinating between events and business resources
 * Resolution – achieving optimal resolution

EyeShare accompanies the process throughout, repeating operations of core processes as necessary, until a complete incident resolution is achieved. The process begins when data collectors intercept input events from external sources including notification systems, logs, and CMDB via multiple communication modules (web services, email, SMS, voice). The events are aggregated, normalized, correlated and integrated, and then stored in EyeShare data warehouse (DWH) and classified into event profiles, that correlate between specific inputs and possible incidents.

EyeShare extracts the data gathered in the DWH using data mining, data manipulation methods.. Advanced filtering and correlation algorithms discover patterns of events, analyze real-time events, and correlate between past and present events. Using pre-configured rules, authorizations, escalation procedures and methods of communication,

EyeShare initiates a procedure for avoiding or resolving the incident. In some cases, EyeShare initiates an automated solution, while in others, it creates an incident profile, correlating between events, people and communication channels. Where relevant and where available, required information for resolving the incident is provided along with the notification, either from

EyeShare’s DWH or from third-party sources. Following a typical incident process, the first designated responder is notified by the appropriate communication channel. Where relevant and available, information from EyeShare’s database or from third-party asset management systems is provided along with the notification. A recommended course of action may also be provided. In any case, if the first responder does not reply within the preconfigured period of time, the incident is escalated according to preset rules and further notifications are sent. Throughout the process, EyeShare tracks response patterns and learns how to better manage similar incidents in the future. For example, EyeShare may note that System Administrator X almost never responds to e-mail and will thus automatically route that person’s notifications through SMS.

EyeShare’s automated methodology recaps itslef, as required, to realize an optimal resolution.

A tag has been placed on Critical Situation Management, requesting that it be speedily deleted from Wikipedia. This has been done under the criteria for speedy deletion, because the article seems to be blatant advertising which only promotes a company, product, group, service or person and would need to be fundamentally rewritten in order to become an encyclopedia article. Please read the general criteria for speedy deletion, particularly item 11, as well as the guidelines on spam.

If you can indicate why the subject of this article is not blatant advertising, you may contest the tagging. To do this, please add  on the top of the page and leave a note on the article's talk page explaining your position. Please do not remove the speedy deletion tag yourself, but don't hesitate to add information to the article that would help make it encyclopedic, as well as adding any citations from reliable sources to ensure that the article will be verifiable. Feel free to leave a note on my talk page if you have any questions about this. ~ Danelo 17:10, 10 August 2007 (UTC)


 * Hi Gabbynizri. Just to let you know, when you place the tag on a page to contest its speedy deletion, please keep the speedy deletion noticed on the page as well (i.e. do not delete it). I re-added the tag to the Critical Situation Management page. Thanks. ~ Danelo 21:23, 10 August 2007 (UTC)