ActiveBatch Workload Automation

ActiveBatch Workload Automation

About TrustRadius Scoring
Score 7.9 out of 100
ActiveBatch Workload Automation


What is ActiveBatch Workload Automation?

ActiveBatch from Advanced Systems Concepts in New Jersey is IT workload automation software.
Read more

Recent Reviews

Read all reviews

Popular Features

View all 6 features
  • Analysis and visualization (10)
  • Logging (10)
  • Alerts and notifications (11)
  • Central monitoring (11)

Reviewer Pros & Cons

View all pros & cons

Video Reviews

Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of ActiveBatch Workload Automation, and make your voice heard!

Return to navigation


View all pricing

What is ActiveBatch Workload Automation?

ActiveBatch from Advanced Systems Concepts in New Jersey is IT workload automation software.

Entry-level set up fee?

  • Setup fee optional


  • Free Trial
  • Free/Freemium Version
  • Premium Consulting / Integration Services

Would you like us to let the vendor know that you want pricing?

6 people want pricing too

Alternatives Pricing

What is Lumen Cloud Application Manager?

Lumen Cloud Application Manager (formerly AppFog from CenturyLink) is a cloud-agnostic application and infrastructure management platform with integrated Managed Services. The centralized platform manages workloads across on-premises and third-party cloud environments, allowing for greater scaling…

What is Oracle Autonomous Transaction Processing?

Oracle offers the Autonomous Transaction Processing, supporting database self-repair and maintenance with machine learning to eliminate human labor, human error, and manual tuning.

Return to navigation

Product Demos

Demand More from Your IT Automation
ActiveBatch Self-Service Portal for Business Users
Redefine Your IT Automation Strategy with ActiveBatch
Return to navigation

Features Scorecard

Workload Automation

Return to navigation

Product Details

What is ActiveBatch Workload Automation?

Advanced Systems Concepts, Inc. (ASCI) offers its Enterprise Job Scheduling and Workload Automation Solution, ActiveBatch.

ActiveBatch coordinates and consolidates silos of automation within a single framework. The goal is to give businesses the IT agility they need and reduce the time expended on managing and supporting multiple automation tools and silos. ActiveBatch provides users with advanced job scheduling and workload automation capabilities for reliable and adaptable integration with an array of applications, databases, platforms, and technologies. IT organizations can reduce their dependency on custom scripting with the ActiveBatch Integrated Jobs Library, which features hundreds of pre-built, proven, drag-and-drop integrations for commonly-scripted actions and functions in a multitude of different automation areas including workload, business and IT processes, managed file transfer, big data, and more.

ActiveBatch Workload Automation Features

Workload Automation Features

  • Supported: Multi-platform scheduling
  • Supported: Central monitoring
  • Supported: Logging
  • Supported: Alerts and notifications
  • Supported: Analysis and visualization
  • Supported: Application integration

ActiveBatch Workload Automation Videos

Find out how ActiveBatch can simplify your IT complexity with an industry leading job scheduling and workload automation solution! Most organizations have between 3 and 8 different automation tools in place. This results in an increased cost of IT Operations, siloed processes...
 Show More
The pace of business is accelerating. Business teams need real-time information faster than ever before. ActiveBatch Self-Service Portal empowers business users to take on daily and ad hoc processes with a business user-friendly, web-based interface for desktop or tablet brows...
 Show More
IT and business processes are scattered across multiple environments, and the systems being managed have increased tenfold. How can you address this complexity in a world where IT budgets are static and finding people with the right skills is a growing problem? The answer is a...
 Show More

ActiveBatch Workload Automation Downloadables

ActiveBatch Workload Automation Integrations

ActiveBatch Workload Automation Competitors

  • CA Workload Automation (AutoSys)
  • Automic (CA) Workload Automation
  • BMC Control-M
  • Cisco Workload Automation

ActiveBatch Workload Automation Technical Details

Deployment TypesOn-premise
Operating SystemsWindows, Linux, Mac, UNIX, Mac OS, IBM z/OS, Hyper-V, VMware, and more
Mobile ApplicationApple iOS, Android, Windows Phone, Blackberry, Mobile Web

Frequently Asked Questions

ActiveBatch from Advanced Systems Concepts in New Jersey is IT workload automation software.

Reviewers rate Analysis and visualization highest, with a score of 8.9.

The most common users of ActiveBatch Workload Automation are from Mid-sized Companies (51-1,000 employees).
Return to navigation


View all alternatives
Return to navigation

Reviews and Ratings




(1-11 of 11)
Companies can't remove reviews or game the system. Here's why
Score 7 out of 10
Vetted Review
Verified User
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.
  • 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
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.
Steve Schneider | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
ActiveBatch Workload Automation runs all of our nightly processes, creates server reports, verifies services are up and restarts them if not. Monitors mission critical servers and SAN units for space issues, encrypts and FTP's files to clients, sends out strategic notifications to clients and monitors SLA's. We use ActiveBatch Workload Automation for almost everything we do. It's an incredible piece of software.
  • ActiveBatch Workload Automation executes our nightly processes and then monitors every process through all of the stages then notifies the client sending them technical information about the job run.
  • ActiveBatch Workload Automation monitors our SAN and mission critical servers for space issues. When we get an alert from ActiveBatch Workload Automation we know it's legitimate.
  • ActiveBatch Workload Automation logs everything! If a job fails we know that we will have all the information we will need to troubleshoot the issue.
  • We have some jobs with 100's of steps and it doesn't even phase our Job Scheduler. It is an amazing application.
  • There could be a more robust user community to share idea's. There is one but I think it could be much better.
  • It's a very complicated application so it's not super easy to pick right up and start using it. We made some mistakes in the beginning that we feel we should have had a better understanding before we started using it. That's our fault.
ActiveBatch Workload Automation is a super robust application, it is suitable for almost anything, it has so many extensions into different applications such as VMware, Amazon EC2, Azure, Power Shell and many others. If it's digital, ActiveBatch Workload Automation can probably create an automated process solution.
Score 10 out of 10
Vetted Review
Verified User
We use ActiveBatch to run our DW Informatica workflows, daily tableau reports, analytics jobs, and ICEDQ rules. This allows us to minimize downtime/errors when coordinating data loads, reporting, data quality, and analysis jobs. We can also easily scheduled prod to test data refreshes which helps our team and others with development and testing priorities.
  • Makes scheduling easy to understand, follow, and rerun jobs when necessary.
  • Allows for cross-team coordination of scheduled tasks which reduces errors.
  • Makes stopping jobs easy when needed for server/database downtime.
  • Scripting enables us to easily change email addresses for failed job alerts.
  • Nested plans/jobs make creating and changing dependencies simple.
  • On RARE occasions, have seen scheduling properties changed that don't take effect.
  • Simpler to understand/more robust reporting options would be nice to have.
  • Maybe I'm missing something, but why doesn't the Instances view show completion time? Just execution time and duration.
I can only speak for our environment, but it has allowed us to get away from the unfriendly Informatica PowerCenter workflow schedule. And coordination of Informatica/Tableau/ICEDQ has been a BIG help to us. We have not tried to drill down to the Informatica session-level of detail, just stayed with running workflows. The session-level logic seemed complicated.
Score 9 out of 10
Vetted Review
Verified User
ActiveBatch [Workload Automation] jobs are developed by two departments, but those jobs are for (or affect) many departments across the whole organization.

We are consistently looking for repetitive tasks that are currently taking up employees time, but which can be automated. By building automation scripts, significant time savings are achieved, and employees are freed to work on tasks which are not repetitive - and thus scriptable.

ActiveBatch has been an excellent tool for this type of automation, as the job scripts are easy to develop quickly, and logging and alerting are strongly incorporated for when things don't go as expected.
  • File management - moving, archiving, and folder cleanup are a drag-and-drop breeze. The visual representation of file management steps includes date/time filtering, file/folder/both specification, and recursion all in an easy and intuitive unit.
  • FTP/SFTP/FTPS - while one must still write the FTP scripts, the interface simplifies much of the infrastructure, allowing the developer to encapsulate the script text in a graphical package that is easy and intuitive.
  • PowerShell integration - for anything that isn't easy in ActiveBatch's GUI, simply drop in a PowerShell step and write the task in PoSh - anything returned from PoSh can then be used by the following steps.
  • String handling / parsing. I find myself using PowerShell to do a fair amount of text parsing (particularly if manipulations are needed) - not necessarily a bad thing, but certainly a place where ActiveBatch could be improved.
  • Debugging - or lack of it! With no stepping debugger, it can be a longer process than many other programming / scripting environments: rather than simply stepping through and observing state changes, I find myself inserting logging steps to excess, then having to clean them up once the error is found.
  • The perennial - Documentation! While a near-universal complaint for *any* software, ActiveBatch's developer documentation is somewhat spotty - just where I need detail, I find summary-level info. There is lots of documentation (as there should be for a tool with such a wide range of applications), but it is in mixed formats (some PDF, some CHM), and the descriptions of specific fields within job steps is often little more than I can get in a tool-tip in the GUI. Allowable ranges, expected formats for string data, and similar helpful details are inconsistent.
  • The KnowledgeBase at ASCI's web site often has examples which answer the questions I have, but not always - and not always under the search terms one would think to use.
Any place one can find a task that is performed repeatedly - either on a schedule, or in response to a triggering state (i.e. a file being created in a specific folder) - that task is at least a good candidate for ActiveBatch [Workload] Automation to be used. Repeating FTP jobs, regular SQL tasks or maintenance, regular file system maintenance - all can likely be taken out of the hands of employees, freeing up time for less repetitive tasks.

ActiveBatch [Workload Automation] is not appropriate for any task which requires flexible judgment - it isn't an AI engine.

ActiveBatch [Workload Automation] also requires at least two servers - a manager ("Scheduler") and at least one worker ("Agent") - thus it is not a good choice for a very small company without those resources available. It is also somewhat costly - not in terms of value, but possibly beyond the reasonable budget of a small company or non-profit with thin profit margins where the investment may outweigh the return.
Score 10 out of 10
Vetted Review
Verified User
ActiveBatch [Workload Automation] is used by our department to fulfill company wide needs. The main use is to control and monitor overnight processing to ensure that all processes are run successfully without need of manual intervention. We also use ActiveBatch [Workload Automation] for internal system maintenance tasks and any other processes that originally required frequent, repetitive manual intervention.
  • ActiveBatch [Workload Automation] is great for simplifying complex tasks so that users of multiple technical skill levels can create and monitor automated tasks.
  • The support team is amazing and will respond with solutions and answers to questions or issues very quickly.
  • ActiveBatch [Workload Automation] does a great job of adding new features and enhancements to the product based on customer feedback.
  • ActiveBatch [Workload Automation] can be a little overwhelming for new users due to its many features and options.
ActiveBatch [Workload Automation] works great for any type of repeatable task, and has several methods of initiating jobs that can be applicable for any environment. In our experience we have yet to find a scenario that needed automation that could not be accomplished via ActiveBatch [Workload Automation]. However, if the number of automated job needs is small, or if they are very simple jobs then ActiveBatch [Workload Automation] might be overkill in those types of situations.
Mark McCully | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
ActiveBatch is used across our Enterprise for scheduling of automated scripts, batch jobs, data transfers, data extraction and several other important services that would otherwise have to be run manually. ActiveBatch has been a reliable tool to save our Operations team from having to work late hours to run these types of tasks manually and risk human error.
  • Enterprise Scheduled Tasks
  • Working in multiple environments and operating systems
  • Security and permissions
  • Technical support
  • Logging
  • Cost
ActiveBatch is a great Enterprise Scheduling tool. It is relatively easy to use and setup. Our Administrators like it because it is robust and works across multiple domains and environments seamlessly. All of the service and user accounts used for the scheduled tasks can be encrypted and secured as well. I would say ActiveBatch is less appropriate for smaller companies that may not need to pay as much for a tool to run automated services, scripts or batch jobs.
We have been pretty happy with ActiveBatch support so far. Luckily, we have not had any major issues with it - so we haven't logged a lot of support tickets. The response time to tickets is about average and the level of expertise of the support engineers seems about average as well. Our sales team has been helpful in getting faster responses when necessary as well.
Score 1 out of 10
Vetted Review
Verified User
We used ActiveBatch to manage many of our automated database reports. It was used system-wide, but for our department only my colleague and I used it. It was supposed to be a replacement for Windows task scheduler, but it barely worked as intended. We had to hack many of our scheduled jobs to use batch scripts since the built-in Powershell or command line options did not work.
  • Everything in one place
  • Easily manage multiple machines and their scripts
  • Supposed to allow for more in-depth schedule 'chaining', e.g. when this job ends it kicks off another
  • Almost none of the advertised functionality worked in any form
  • Hacks to get it to work included calling a batch script via a scheduled task instead of just saving the code directly in AB - running that way did nothing
  • Notifications of job activity either didn't work or just absolutely spammed you
  • User accounts didn't work, our team had to share the one that barely worked
If it did the things it says it can, it would be an incredibly powerful and essential tool. Being able to manage all of our scripts in one place, as well as which machines they run against and their schedules would have been amazing. The builder was also easy to use for setting things up; again if they actually did anything once set up.
My colleague contacted them directly, I only know hearsay on this but it was not good.
Ron Zermeno | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
ActiveBatch is used by our organization to automate redundant tasks, both internally and externally. Many of our departments have 'jobs' they've created, to run processes that would normally occur during working hours. With ActiveBatch, these processes can now be set to 'trigger' at scheduled times throughout the day and throughout the night. This saves from having one person being assigned with running and managing the individual tasks. And since the jobs are scheduled, the processes can run during the weekends and holidays, saving employees time and the company money.
  • Easy to automate mundane tasks. Take all those batch files spread across your environment and put them in one application for management.
  • Good support site and knowledge base. If you run into issues, the support is quick to respond and assist with a resolution or advice.
  • Additional 'extensions' (plug-ins) are available, to aid ActiveBatch with interfacing with other platforms (AWS, Sharepoint, IBM and VMWare).
  • The manual could provide more examples of how to create certain jobs, otherwise you will need to check the site or call support to aid with creation.
  • Dashboard presentation could be worked on, to help present an overview for management.
It's great for basic tasks or tasks that need to run in a certain sequence. Especially import/export jobs, where the next step can only work when the previous job has completed. It does have some issues where a tasks may run into an error (file location not available) and may not always prevent itself from continuing to run the job.
Score 8 out of 10
Vetted Review
Verified User
We are using ActiveBatch across multiple departments. Our collections team is using it to gather customer payment history from a Microsoft SQL database. Our billing application runs through ActiveBatch and feeds the billing data to the data warehouse. Through ActiveBatch, our business unit's reports are made available, or they receive ActiveBatch alerts indicating an error occurred in the data generation and details about the error.
  • ActiveBatch does Microsoft SQL jobs well, providing centralized configurations.
  • The scheduling options and flexibility is very good in ActiveBatch.
  • The ability to restrict ActiveBatch users to specific areas of the application is easy to manage.
  • The Oracle connectivity and error detection is challenging and doesn't always work for us.
  • The UI for administration is overwhelming as first and could be simplified.
ActiveBatch is an excellent tool to distribute to multiple teams across the organization, allowing developers, application support, business units as well as mangers to create the tasks they need and maintain their configurations, without having to wait on a central point of support.
Score 8 out of 10
Vetted Review
Verified User
It was and still is being managed and integrated into other internal systems by the whole IT DevOps team, but forms a critical layer that services our entire organization in providing automated linkage between my former company's systems and those of their clients. On any given week the company would have literally hundreds of file import/export transactions that need to happen on a single day, every day, every month, or some complex combination of days at different hours of the day and night and consistently ActiveBatch delivered. It allowed for the efficient design and redesign of import/export jobs (such as being able to reuse schedule objects, allow for the partial execution of nodes for a particular job to help with testing, and effortlessly change parameters from testing to development deployments), logging of transaction errors, and ability to work with the wide variety of file processing tools that we would use internally (ETL, SSIS packages, .NET code, etc.) It's relatively intuitive design allows for it to be used and managed by people with even a bare minimum of IT experience, without sacrificing power and reliability.
  • One good feature I already mentioned is that once you create a configuration object (such as a schedule object), you can reuse it as much as needed. This minimizes errors in scheduling because there's less opportunity to make a configuration error with future similar jobs that would follow the same schedule, makes it more efficient to schedule those new jobs, and makes it efficient to make scheduling changes--change the scheduling object once and all the related jobs' schedules are automatically changed.
  • Partial path execution is a good strength, especially for testing/debugging. I can have a decently sized tree of process nodes for a given job, but I can easily deactivate the nodes I do not want to include in my testing.
  • Being able to define test and production jobs in separate environments and easily change the settings of one without affecting the other is another strength. Often I would have a job set up in a test environment and after testing it, it would get ported to a very similar production environment with only having to change 3-4 parameter settings. And then I could easily deactivate the test job while still keeping it all set up in the event of needing it for future enhancement/troubleshooting.
  • While I like being able to reuse scheduling objects and the like, more work needs to be done to help one not reinvent the same scheduling object without realizing it and to then find scheduling objects that have similar schedules even if they are worded slightly differently than what I'm expecting. It needs to be "smarter". It was easy to accumulate a pool of scheduling objects that while named differently, had exactly the same schedule. It was also hard to sift through to find the little differences between similarly named scheduling objects.
  • The logger had a clean enough interface but it could be more legible and offer contextual help to describe the messages one is reading. I remember trying to read black text on a medium gray background with Courier size 10-11 font. Not so easy to read quickly and to parse through the relevant parts. I think some selective color coding would be good and links to message definitions or any form of further information would be nice. Maybe the ability to export the log file to various formats would also be helpful.
  • I don't remember a dashboard that at a glance on the top level would highlight what jobs failed completely and which jobs might have warnings or non-critical errors. I got emails because I defined to get them. Maybe again if there was a way to color-code the type of error would be good nice-to-have.
I used to work in a company that only used SQL Server Agent to handle imports and exports of ETL data. ActiveBatch is far more powerful and easy to use, so I definitely would recommend it. I would think of three questions: (1) Do you handle a large volume of exports and imports in a given week? (2) Do you need a lot of configurable options, such as with scheduling? (3) Do you utilize a variety of ETL processing tools (such as GlobalScape EFT and Microsoft SSIS) but want one tool to work with them all? If yes to those questions, then ActiveBatch would well fit the bill for you then.
Ruben Santiago | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
ActiveBatch usage in the company has expended extensively from its v4 days when it hosted just 6 jobs. Now, with over two thousand jobs and dozens of workflows, it touches and does processes for just about every department within the company; claims, sales, I.T., finance, H.R., and now the mainframe. It allowed us to set standards for how users write jobs and security of the systems. With the addition of the web server component, end-users can access the system via the web GUI instead of providing them server console access. In training the users, we set forth policies for how to write/use code/elements of the system so that others, not familiar with the system, can quickly identify where issues are and target their efforts in those jobs. After our security audit, use of the ActiveBatch increased since it hooks into our encryption software....well, it hooks into a lot of applications specific to our needs. With any workflow, comes a different set of requirements, and ActiveBatch has allowed us to meet or exceed every one of them.
  • Interaction with other third party software. Interacts with encryption software, various 'partner designated' sftp software, file manipulation software, etc.
  • Variety of options for users based on experience in accomplishing the same things as 'coders'. Someone like me wouldn't need to use the Jobs Library too much but users who are not comfortable with code can accomplish the same tasks using the drag/drop functionality of the pre-built jobs library.
  • Security. Allows the admins to secure every single element of the system; plans, jobs, accounts, etc.
  • Easy to use by the end-users.
  • Lack of continued development for the non-jobs step library items.
  • Updates sometimes 'break' previously working functionality; the email trigger comes to mind.
  • Lack of development of what can trigger jobs/processes.
I found it suited for just about anything. Currently ActiveBatch sits on a Windows environment, but it can hit the Linux servers by calling WinSCP or Putty to perform actions on the Linux servers.
Return to navigation