Redwood Business Process Automation - Workload Edition

Unsure. BRG was already using Redwood before I joined the team.

I was not part of the decision making on choosing RunMyJobs, but my understanding on what made RMJ stand out was the fact that it is in the cloud, with no infrastructure support needed on our side, as well as a promise that you could schedule and monitor jobs within ServiceNow. We later found out the ServiceNow promise was not correct and still don't have a direct method as of this writing.

Compared mainly to regular SAP SM37, and also BatchMan... None are able to provide the same array of tools to drive highly complex setups within the batch flow.

When evaluating other products against Redwood Business Process Automation, the largest differentiation was the SaaS-based model. Other solutions were on premises, which would entail server OS licenses, backup/DR overhead, and management at the server and application levels. With Redwood Business Process Automation, the overhead and administration at the server and application levels were removed so the only responsibility is the administration of RunMyJobs.

I have used a variety of scheduling tools over the years. Going all the way back to mainframe schedulers, AS400 schedulers, even some of the more recently developed SAP schedulers. The problem with so many of those other schedulers is that they are either overcomplicated, or too bubble-gummy. The other tools don't seem to give you the flexibility to make those determinations yourself, they tell you "thanks for the payment, now you have to run your jobs the way we say". Redwood gives you the ability to make your tool as simple or as complex as you need it to be. I always prefer to keep it simple but on occasion a particular process may require some added layers of complexity. Not every job you create needs to read like war and peace, so why waste time doing that?

Having evaluated and worked in AutoSys and Control-M, we've found RunMyJobs to be an overall superior product.