1. Monitoring with TWS/Graph
The Best View to TWS
Monitoring with TWS/Graph
HORIZONT
Software for Datacenters
Garmischer Str. 8 D München
Tel ++49(0)89 / 1 1 1 1 1 1 1 1 1 1 1

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
TWS/Graph has an integrated Status Monitor. It can be used to monitor your production:
Monitor the critical path
Monitor Milesstones
Monitor if production is late
Create HTML files with actual status information
Send Alerts ( or WTO to SYSLOG)

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
In addition to the treechart all information is presented in HTML files. Benefits are:
End user needs no host connection
End user needs no special knowledge
End user can access status information from anywhere

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 Message zusammenbauen TWS/Graph Message Jobname
:31:33.88 STC $HASP100 O8CP#14 ON STCINRDR
:31:34.09 STC IEF695I START O8CP#14 WITH JOBNAME O8CP#14
, GROUP STCOPC
:31:34.09 STC $HASP373 O8CP#14 STARTED
:31:34.11 STC IEF403I O8CP#14 - STARTED - TIME=
:31:34.89 STC ICH70001I P390K LAST ACCESS AT 12:21:50
:31:36.50 STC OPG099I HOR60DAY A R IN
:31:36.54 STC OPG099I HOR60DAY HOR60010 W L CPU
:31:38.23 STC
Message zusammenbauen
TWS/Graph Message
Jobname
Application
Monitor- Status (Late)
OPC- Status (waiting)

48. How to use TWS/Graph to avoid delays
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:
Milestones
TWS/Graph and OPC Deadline times

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

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

52. 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. Pros and Cons Simply to use
We think Milestones is the best method to monitor thousands of jobs:
Simply to use
Excellent performance (TWS/Graph must monitor only the milestones, and not the whole stuff)
Milestones must be maintained

54. Using TWS-"Deadlines"
TWS/Graph offers alternatives to monitor the critical path:
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)

55. 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. 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 T A-99

57. Using TWS-"Deadlines"
2. Define an object in the status monitor that points to 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.
The critical job
Specify 99 for all predecessors

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

59. 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. Using TWS-"Deadlines"
5. If you like to see which job missed the deadline, you must select “netplan”…

61. 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. Pros and Cons
In opposite to the “old” method of using milestones this new function has some disadvantages:
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

63. Many thanks for your attention!
TWS/Graph
The Best View to TWS
Many thanks for your attention!
HORIZONT
Software für Rechenzentren
Garmischer Str. 8 D München
Tel ++49(0)89 / 1 1 1 1 1 1 1 1 1 1 1