Item: ActiveBatch Workload Automation
Rating: 7
Author: Bas Verschuren

Use Cases and Deployment Scope

We use ActiveBatch Workload Automation for our IT processes and systems. Before we needed to make different complex scripts, eg powershell. Now thanks to ActiveBatch Workload Automation it is centralized in one software application.

Pros and Cons

schedule jobs
consolidation of the different object and processes
expand the base line of the different jobs

still need some scripting code
some objects could be better intuitive
learning scale

Most Important Features

scheduling Jobs
make it easy to expand the UI
The number of predefined objects

Return on Investment

make a directly visible if something went wrong
not to worry when execute scheduled jobs
negative point is that only large businesses can benefits, I believe.

Alternatives Considered

I only have used this software, so I can't judge other software. I wasn't involved in decision making.

Key Insights

Do you think ActiveBatch Workload Automation delivers good value for the price?

Yes

Are you happy with ActiveBatch Workload Automation's feature set?

Yes

Did ActiveBatch Workload Automation live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of ActiveBatch Workload Automation go as expected?

I wasn't involved with the implementation phase

Would you buy ActiveBatch Workload Automation again?

Yes

Other Software Used

Microsoft SQL Server, TOPdesk, Azure DevOps Server (formerly Team Foundation Server)

Likelihood to Recommend

ActiveBatch Workload Automation is best in large IT landscapes with a lot of business processes but less so in smaller organisations I believe. I think it is too complex for IT department that uses less than 50 objects. Because then the profit doesn't weighed the learning time.

ActiveBatch Workload Automation Reduces Scheduling Time

Overall Satisfaction with ActiveBatch Workload Automation