The solution has helped us because we have multiple node servers and the workload is distributed between them.

Our firm supports batch processing across many platforms from mainframe to iSeries and open systems. TWS enables consolidation of disparate workloads in a single database, removing the need for engineered interfaces between platforms and enabling simpler job to job dependencies and end to end management and monitoring of workloads.

Provides a robust, full spectrum enterprise-wide WLA platform. I have practical experience with all of the major "Enterprise" WLA products (Control-M, CA-7, and Zeke). None of them have the functionality and ease of use of TWS.

The IBM scheduler allows for easy and seamless execution of the automated tasks in order to ensure data processing.

Improved migration/upgrade features helped us to reduce the time of upgrade.

The tool made it possible to automate the technical workflow within complex business process models, within a heterogeneous network hierarchy, consisting of fault-tolerant distributed agents, managed by (master-)management agents.

The tool made it possible to fully automate actual job-workflows that represent complex end-to-end business process models (BPM’s). Those workflows run on systems that reside in a distributed, heterogeneous, logical agent-network (fault-tolerant, ‘extended’, SAP R/3, SAP BI and even cloud/dynamic (e.g. Salesforce, Microsoft SQL) brooker agents).

This agent-network itself is managed by (master-)management fault-tolerant agents that periodically provide all the agents in the network with a static (predefined) scheduling plan for a certain future period of time, and also house a so called event-processor, that is able to have the master-management agent submit just-in-time defined workload into the actual running BPM, as a result from detected events within the network.

It supports almost all of the different groups in the organisation for automating their tasks, such as finance and accounting, transport department, procurement department and several others as well.

It has over complicated things.

Aside from basic scheduling features and Windows/Unix job types, this product gives us a lot of options to integrate with other systems:

• Custom plug-ins (SAP, DataStage, PeopleSoft, Cognos)
• Database & integration job types (Oracle, MS SQL, Web Services, J2EE)
• File transfer and remote command job types

It is a great way to centralize your enterprise workload to provide better visibility to support groups and better cohesion between applications. Mobile app features are also available to empower users to monitor\manage their workload on the go.

My organization has automated a lot of tasks that were previously being done manually like processing of cheques from multiple banks. This was a three step process wherein a dedicated man resource used to scan the cheques individually, another person then updated a record in the database followed by sending out an email.

All these steps required a lot of time and money and any absence of human resources would result in severe lapses. With the help of Tivoli, all the three tasks were automated into a single jobstream that runs throughout the year without any manual intervention, even taking off days and holidays.

Tivoli Workflow Scheduler provides a centralized tool for all scheduled jobs, including design, monitoring, and support. With thousands of jobs running each day, this would be unmanageable using Windows scheduled tasks, cron jobs, or a home grown scheduler based on Quartz or similar framework.

Job scheduling is an integral part of deploying data warehousing jobs. I was a part of the developer team and while coordinating with the support team who did the actual job scheduling, it was easy for them to coordinate with us on what job to release first, what to cancel, what to release dependencies, etc.

I belong to a part of the delivery module in our organization. We implement TWS in the customer’s environment. It has definitely improved many different processes in our organization.

This product has increased the level of automation with no / minimum downtime and predictable scheduling.

The new servers automatically get monitored with the alerts going to the server administrator or application developers, without the need for someone to submit a request.

The alerts automatically go to a command center, when a server is classified as production in the inventory system. The alerts get automatically suppressed during an approved change.

It gives end users the ability to monitor their jobs/workflows in real time, which helps with MTR when they experience issues.

When there is a holiday or emergency closing, we query the Long-Term Plan to identify what will or will not be running during the closure. Application owners review and sign off of the plan, making everyone aware of the scheduled jobs for that time frame.