H O RIZONT Software for Datacenters

1. TWS/Graph The Best View to TWS Monitoring with TWS/Graph HORIZONT Software for Datacenters Garmischer Str. 8 D- 80339 München Tel ++49(0)89 / 540 162 - 0www.horizont-it.com

2. Monitoring Production? Is it possible to monitor a complete production? Technically yes, but…

3. Monitoring Production? The problem: A complete production is too big for graphical monitoring!

4. Monitoring Production with TWS/Graph! The solution: Monitor the critical path, and not the complete production!

5. TWS/Graph Status Monitor • Monitor the critical path • Monitor Milesstones • Monitor if production is late • Create HTML files with actual status information • Send Alerts (Email or WTO to SYSLOG) TWS/Graph has an integrated Status Monitor. It can be used to monitor your production:

6. Identify Critical Jobs As a first step you must know what you like to monitor, and how to group these jobs logically, e.g. by functionality, by owner, by department etc.

7. Define Structure After you've made a decision what you like to monitor, you must define a structure

8. Define Structure • Now this empty structure must be filled up with objects: • Groups • Applications • Operations

9. Define Structure Use the right mouse to insert objects into the empty structure

10. Define Structure Top Level, e.g. the OPC subsystem

11. Define Structure Next Level, e.g. Operations

12. Define Structure Do you want to get a list of all jobs that are in error?

13. Define Structure Or do you want a list with all jobs that are started?

14. Define Structure Or do you like to monitor all jobs that are defined in OPC to be monitored? (available with TWSz 8.1)

15. Starting the Monitor Start

16. Starting the Monitor Refresh all 5 minutes Write status information to HTML

17. Status Monitor is up and running No job is in error Jobs are active Some critical jobs are done, some others are still waiting After the refresh the colors are changed, every colour has a special meaning

18. Status Monitor is up and running Job(s) in error Job(s) are active

19. Status Monitor is up and running All netplans can be loaded directly from the monitor, here are the active Job(s)

20. Complex Monitoring e.g. for special jobs ...and jobs for several departments The structure should be defined in a way that allows to monitor all interesting elements from one screen: The Focal Point

21. Define more Jobs/Applications

22. Define more Jobs/Applications

23. Define more Jobs/Applications

24. Define more Jobs/Applications

25. Define more Jobs/Applications

26. Define more Jobs/Applications

27. Define more Jobs/Applications

28. Define more Jobs/Applications

29. Starting the Monitor Start

30. Starting the Monitor

31. Status Monitor is up and running Jobs are waiting Some Jobs are in error, other jobs are active, other jobs are waiting Not planned

32. Status Monitor is up and running

33. Status Monitor is up and running

34. Status Monitor is up and running This display can be used on a big screen for the operators

35. HTML Output • End user needs no host connection • End user needs no special knowledge • End user can access status information from anywhere In addition to the treechart all information is presented in HTML files. Benefits are:

36. HTML Output The HTML files can be used to publish TWS status information via Intranet

37. HTML Output

38. HTML Output

39. HTML Output Detailed job information

40. How to monitor late jobs

41. How to monitor late jobs The jobs is „late“, if it is not complete until 18:00 Selection criteria: One or more jobs (generic selection)

42. How to monitor late jobs These job(s) are „late“, if they are not complete until 18:00. 06:00 (=IA) + 12:00 Std. = 18:00 Selection criteria

43. “Late” Monitor is up and running

44. “Late” Monitor is up and running Job (and superior levels) are „late“ The superior Level is still red, because ERROR has higher priority than LATE

45. Alerts After every refresh any program can be called from TWS/Graph.

46. Alerts Create Message Send Email TWS/Graph has an integrated REXX interface. Parameters like the jobname or the status can be passed as a parameter to a program

47. WTO - Output Syslog 03213 18:31:33.88 STC04191 00000081 $HASP100 O8CP#14 ON STCINRDR 03213 18:31:34.09 STC04191 00000290 IEF695I START O8CP#14 WITH JOBNAME O8CP#14 , GROUP STCOPC 03213 18:31:34.09 STC04191 00000090 $HASP373 O8CP#14 STARTED 03213 18:31:34.11 STC04191 00000081 IEF403I O8CP#14 - STARTED - TIME=13.31.34 03213 18:31:34.89 STC04191 00000081 ICH70001I P390K LAST ACCESS AT 12:21:50 03213 18:31:36.50 STC04191 00000090 OPG099I HOR60DAY A R IN 03213 18:31:36.54 STC04191 00000090 OPG099I HOR60DAY HOR60010 W L CPU 03213 18:31:38.23 STC04191 00000290 - - Message zusammenbauen TWS/Graph Message Jobname Monitor- Status (Late) Application OPC- Status (waiting)

48. How to use TWS/Graph to avoid delays • Milestones • TWS/Graph and OPC Deadline times TWS/Graph can be used to find out if production will be in time, or if there are delays. There are some basic techniques to do that:

49. Milestones Probably the best way to monitor the Critical Path is to insert milestones and to monitor them with TWS/Graph

50. Milestones Now the same application with milestones (yellow symbols)PS: We used the TWS/Graph function ”Search for redundant links” to clean up the application