We use it for IT workflow automation. We have three main categories: billing, reporting, and analytics. We automate the entire workflow, end-to-end, including the file movement from our managed file-transfer solution to our NAS storage point and then kick off the downstream workflows. Most of them are ETL-based in Informatica. And the loads are done to a database and/or storage with output. It's the entire workflow.

We host it on-prem.

It is our enterprise scheduler; we're migrating everything to it. We'll only have Stonebranch as the enterprise scheduler controlling all of our jobs when we get to the end of our project. So it's being used extensively. We'll be somewhere north of 450 jobs when have completed the project and we will increase usage. As more workflows come online, Stonebranch is the platform we will use to automate them.

We have 35,000 jobs that are running in SAP at different times of the day and at different frequencies. All those have been configured in Stonebranch Universal Automation Center.

Basically, it is a workload automation that we are using to run our various SAP application jobs. The background jobs are scheduled from third-party tools. We used to trigger from AutoSys. This is a replacement product for AutoSys.

Our primary use case is automating the workload for the company. It's used quite extensively. We run over 500,000 jobs a week with it.

We started off with replacing mainframe batch scheduling for some of our distributed applications, and then it grew into not just batch but workflows and file transfers.

The volumes that we throw at it are in excess of 15 million tasks per month.

We use Stonebranch to manage and migrate automated tasks. 

It handles all of our scheduling. All our batch workload runs through it. We use MOVEit for our file process transfers, so we don't use Stonebranch for that. 

We have MOVEit integrated with our scheduling, so we run commands to MOVEit from scheduling.

We're running about 46,000 tasks per day.

Two people are using this solution in my company.

It's deployed on a private cloud.

The primary use case is that we are now at the point where we are creating workflows and it is allowing us to shorten the time it takes for tasks to go through multiple machines. We wanted something that would give us better visibility.

Automate batch processing jobs that used to run on cron and had very ambiguous logging. It really helped us automated many manual jobs as well that were time-consuming and tedious.

I am a consultant. Stonebranch was used for retail businesses.

We use it for enterprise scheduling and workload automation. For the most part, it runs our internal mainframe batch jobs and does file transfer processes in and outside the company.

I am a part of a production support team, and we automate most of our work using this. It reduces all the manual work.

Scheduling Unix and Wintel batches. Full package - finance, backups, transfers. Three environments.  

We are currently converting a segment of our distributed batch scheduling requirements from another vendor. The new model will give each application the ability to build, maintain and monitor their own batch flows.

Originally purchased as a replacement for CA7/11, now used for full-blown enterprise automation. We utilize agents on Linux, Windows, iSeries, and zSeries machines.

Scheduling Linux and Windows tasks from a 3rd party scheduler running on IBM z System. Integrating mainframe workload with distributed ones.

Centralized scheduling and file transfers running on a couple of hundred agents (Windows/Unix/Linux).

We use UAC on a daily basis to serve our internal customers. My team uses UAC to create workflows based on business requirements, creating patching campaigns and provide support. 

We are scheduling applications and tasks for our internal customers.

• We are using Stonebranch to automate our MDM solution with all inbound and outbound systems. 
• We also use it for scheduling jobs or process to extract data from our business app to data warehouse solutions.
  

Using Universal Agent as a distributed agent (like extended agents), managed with IBM Workload Scheduler for z/OS.

We had no enterprise solution in place for our application. This was meant to support Linux and Windows.

Universal Agent is used as a distributed scheduling agent with IBM Workload Scheduler for z/OS. It's used in different environments (development, production) for scheduling jobs on open systems.

FileTransfers and batch automation in Java environments. Implement daily checks on database tables with SQL tasks.

We primarily use the solution for our clients.