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

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

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

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

5. HORIZONT 5 TWS/Graph 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. HORIZONT 6 TWS/Graph 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. HORIZONT 7 TWS/Graph Define Structure After you've made a decision what you like to monitor, you must define a structure

8. HORIZONT 8 TWS/Graph Define Structure Now this empty structure must be filled up with objects: Groups Applications Operations

9. HORIZONT 9 TWS/Graph Define Structure Use the right mouse to insert objects into the empty structure

10. HORIZONT 10 TWS/Graph Define Structure Top Level, e.g. the OPC subsystem

11. HORIZONT 11 TWS/Graph Define Structure Next Level, e.g. Operations

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

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

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

15. HORIZONT 15 TWS/Graph Starting the Monitor Start

16. HORIZONT 16 TWS/Graph Starting the Monitor Refresh all 5 minutes Write status information to HTML

17. HORIZONT 17 TWS/Graph 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. HORIZONT 18 TWS/Graph Status Monitor is up and running Job(s) in error Job(s) are active

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

20. HORIZONT 20 TWS/Graph 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. HORIZONT 21 TWS/Graph Define more Jobs/Applications

22. HORIZONT 22 TWS/Graph Define more Jobs/Applications

23. HORIZONT 23 TWS/Graph Define more Jobs/Applications

24. HORIZONT 24 TWS/Graph Define more Jobs/Applications

25. HORIZONT 25 TWS/Graph Define more Jobs/Applications

26. HORIZONT 26 TWS/Graph Define more Jobs/Applications

27. HORIZONT 27 TWS/Graph Define more Jobs/Applications

28. HORIZONT 28 TWS/Graph Define more Jobs/Applications

29. HORIZONT 29 TWS/Graph Starting the Monitor Start

30. HORIZONT 30 TWS/Graph Starting the Monitor

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

32. HORIZONT 32 TWS/Graph Status Monitor is up and running

33. HORIZONT 33 TWS/Graph Status Monitor is up and running

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

35. HORIZONT 35 TWS/Graph 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. HORIZONT 36 TWS/Graph HTML Output The HTML files can be used to publish TWS status information via Intranet

37. HORIZONT 37 TWS/Graph HTML Output

38. HORIZONT 38 TWS/Graph HTML Output

39. HORIZONT 39 TWS/Graph HTML Output Detailed job information

40. HORIZONT 40 TWS/Graph How to monitor late jobs

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

42. HORIZONT 42 TWS/Graph 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. HORIZONT 43 TWS/Graph “Late” Monitor is up and running

44. HORIZONT 44 TWS/Graph “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. HORIZONT 45 TWS/Graph Alerts After every refresh any program can be called from TWS/Graph.

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

47. HORIZONT 47 TWS/Graph WTO - Output Message zusammenbauen 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 - - TWS/Graph Message Syslog Application Jobname OPC- Status (waiting) Monitor- Status (Late)

48. HORIZONT 48 TWS/Graph 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. HORIZONT 49 TWS/Graph Milestones Probably the best way to monitor the Critical Path is to insert milestones and to monitor them with TWS/Graph

50. HORIZONT 50 TWS/Graph 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

51. HORIZONT 51 TWS/Graph Milestones The status monitor of TWS/graph needs one object for every milestone

52. HORIZONT 52 TWS/Graph Milestones The monitor signalises if a milestone is late. In this case the daily production was delayed right after the start at 10:00

53. HORIZONT 53 TWS/Graph Pros and Cons +Simply to use +Excellent performance (TWS/Graph must monitor only the milestones, and not the whole stuff) -Milestones must be maintained We think Milestones is the best method to monitor thousands of jobs:

54. HORIZONT 54 TWS/Graph Using TWS-"Deadlines" TWS/Graph allows to check automatically all predecessors of a critical job (e.g. the online start). If one preceding job exceeds its deadline, the status LATE is shown. To do this you must specify '00:00' in the 'late time' field and 'Operation Deadline' in the 'late time origin' field. As long as you have coded deadline times, the monitor produces late alerts for these if they are in your monitored critical path. And if there is a known delay to the start of batch by, say 2 hours, you only need to change the 'late time' field to '02:00' for one monitored job (last one in the critical path) TWS/Graph offers alternatives to monitor the critical path:

55. HORIZONT 55 TWS/Graph What are TWS Deadlines? The deadlines we are using in our function are the operation deadlines. They have to be specified in the application descriptions of TWS.

56. HORIZONT 56 TWS/Graph Using TWS-"Deadlines" 1. Find out the last job in your critical path, e.g. the online system. In our example the last job is T82030050A-99

57. HORIZONT 57 TWS/Graph Using TWS-"Deadlines" The critical job The late time must be specified as an offset to the deadline. If you specify 00:10, and the deadline in TWS is 12:30, the job will be late if it is not complete until 12:40. Specify 99 for all predecessors 2. Define an object in the status monitor that points to the critical job

58. HORIZONT 58 TWS/Graph Using TWS-"Deadlines" 3. After having started the monitor, TWS/Graph checks automatically all predecessors of the critical job.

59. HORIZONT 59 TWS/Graph Using TWS-"Deadlines" 4. The status monitor shows LATE if any preceding job missed the deadline (remember: the deadline has to be specified in the application description of TWS)

60. HORIZONT 60 TWS/Graph Using TWS-"Deadlines" 5. If you like to see which job missed the deadline, you must select “netplan”…

61. HORIZONT 61 TWS/Graph Using TWS-"Deadlines" 6. TWS/Graph shows the netplan with all predecessors of the critical job, all jobs that missed the deadline are marked (here pink).

62. HORIZONT 62 TWS/Graph Pros and Cons -Operation deadlines must be maintained in TWS. -Poor performance (TWS/Graph must locate and analyse all predecessors) +In case of delays the monitor can be adjusted easily, only the ‘late’ time must be modified in the status monitor In opposite to the “old” method of using milestones this new function has some disadvantages:

63. HORIZONT 63 TWS/Graph HORIZONT Software für Rechenzentren Garmischer Str. 8 D- 80339 München Tel ++49(0)89 / 540 162 - 0 www.horizont-it.com TWS/Graph Many thanks for your attention! The Best View to TWS