1. Sourcing Operations Management Architecture Monitoring that works!

2. 1.Monitoring Overview 2.The Sourcing Business 3.Demonstration 4.The OMA Advantage 5.Next Steps 6.Questions Agenda

3. Monitoring Overview

4. Why Monitor? Visibility (The Truth) MeasurementCorrelation Notification Actively know environment is working Actively know when its not! Continuous visibility Fault awareness before the end user No finger pointing! Half the time to resolve problems Diagnosis is MUCH simpler See only the problem, not the noise! Always in touch! Information to manage Sweat the assets! If you can see it, you can do something about it. Its what you cant see that will kill you!

5. Why Monitoring Systems don't work –High upfront investment –Availability (and accessibility) of in- house skills to implement and support the solution –Technical complexity –Heavy resource impact on device and network –Ability to rapidly deliver value –Lack of tool flexibility –Never-ending configuration, maintenance and administration Gartner

6. How do we fit in OMA (Single Pane of Glass) ESM EM

7. How we fit in OMA – What we use to collect data and produce outputs PROCESSPROCESS APPSAPPS We will instrument and hook to applications in every way that we can Trusted performance and capacity advisor. Go to guys for performance problems What we deliver: Problem identification Mission critical (apps+infr) alerting Our Historic deliverables Planning advice Integrate into your operation Problem, Change, Capacity, Incident Review, Review Weekly Baseline Incident Monthly Baseline Problem Incident Administration Capacity

8. The Sourcing Schema - Leading Indicators ExchangeWhat we Monitor Exchange CountersQueues (6), Connectors (6), Mail (3), Info (9), Messages (12) Log Files (Critical Errors) (2003) ESENT, Information Store, System Attendant, Routing Engine (10) Operating SystemDisks (10), Memory (6), Services (16), CPU (5) HardwareTemp (2), Fan (3), PSU(1), Disks(15) Total Counters:104 (100 Average number of counters) Out of a possible 10 000 counters (Exchange has 1 700) 10 000 Counters x 100 Servers = 1 000 000 100 Counters x 100 Servers = 10 000 We alert on <10% of these. 99.99% of the action with < 1% of the footprint! We poll every 2 minutes 100 Tests x 100 Servers / 2 = 5 000 tests / min = 7.2 million tests / day. Imagine making it more complicated The law of diminishing utility 1 st 10 tests = 50% utility 2 nd 10 tests = 25% utility 3 rd 10 tests = 12.5% utility Etc The 101th test = 0.01% utility = 99.99% utility.

9. The Sourcing Schema - Leading Indicators ExchangeWhat we Monitor Exchange CountersQueues (6), Connectors (6), Mail (3), Info (9), Messages (12) Log Files (Critical Errors) (2003) ESENT, Information Store, System Attendant, Routing Engine (10) Operating SystemDisks (10), Memory (6), Services (16), CPU (5) HardwareTemp (2), Fan (3), PSU(1), Disks(15) Total Counters:104 (100 Average number of counters) Out of a possible 10 000 counters (Exchange has 1 700) 10 000 Counters x 100 Servers = 1 000 000 100 Counters x 100 Servers = 10 000 We alert on <10% of these. 99.99% of the action with < 1% of the footprint! We poll every 2 minutes 100 Tests x 100 Servers / 2 = 5 000 tests / min = 7.2 million tests / day. Imagine making it more complicated The law of diminishing utility 1 st 10 tests = 50% utility 2 nd 10 tests = 25% utility 3 rd 10 tests = 12.5% utility Etc The 101th test = 0.01% utility = 99.99% utility. Top 10 (50%)Next 10 (75%)Next 10 System uptimeCritical error logsOther services System tempVirus services% Processor time Disk SpaceOther key Exchange servicesDisk array status MTA servicesPSU & statusMemory hard page faults Queues/storeMemory available SMTP queue Next 10Next 10Next 10 Fan statusOther memory testsNon critical logs Processor cache statusTop processorsNic errors Mail flow indicatorsOther CPU tests Other exchange counters

10. OMA Horizontal vs. Vertical Mom/SCom BotzView 10 000 tests 96 tests We are not going to configure your Netbotz, - use the Netbotz tool. We will tell you that your data centre is overheating, every time, only when it is. We will tell the correct person, even if you changed the configuration. If you want 10 000 tests, get SCom If you Want 96 tests that cover the 99.99%, get OMA!

11. Q How does our solution work (technical)? PE Secure Comms Monitored Device Are you there? How much? A DB Web 132 No correlation required No name translation required No test differentiation required No Contextual knowledge required Completely Rules based

12. Sourcing Solution Fully integrated end-to-end solution Significantly lower resource impact on IT environment than traditional ESM solutions Quick deployment ensures quick business benefit Go-to-show in less than six weeks Instantaneous value Low noise 24x7 multichannel notification engine Business Model Automation as a philosophy Source code owned and developed internally South African solution designed for South African environments Rand based pricing model Software-as-a-Service (SaaS) delivery model –It must work No Deployment, Licensing, Upgrade or Maintenance fees –Software is Free and Evergreen The Sourcing Solution and Business Model

13. Our current Client portfolio

14. System Inputs Technology Areas Operating Systems Active Directory QOS NBAR NAS & SAN Radio LANs Wan Jet BizTalk Desktops Application Response Message Queues Assets Log & Text Files Databases Database Tables

15. System Outputs Availability, Capacity, Performance, Diagnostics Single Pane of Glass IncidentsTechnology Agnostic diagnosis Technology Agnostic Reporting

16. Multi-Functional Dashboard (IT Management View)

17. Multi-Functional Dashboard (Executive View)

18. Function Based Dashboard

19. Graphing and Trending of Performance Counters

20. Router Dashboard

21. Protocol Analysis

22. Application Response Monitoring DNSNetworkTrafficUser Exp

23. User Experience

24. Application and End User Response Monitoring

25. Branch Ready

26. OMA Attendant

27. SLA & Availability Reporting

28. Application Monitoring

29. Log File Parsing

31. Backup Monitoring

32. Database Table Monitoring PE Secure Comms

33. Instrumentation Counters Custom Application Code

34. Application Monitoring

35. User Experience

36. Reporting Engine

37. Incidents

39. Availability