Redwood RunMyJobs Reviews

Redwood Workload Automation is a software application that assists businesses in automating and streamlining their business operations. 

It allows businesses to plan and handle tasks, workflows, and applications across multiple systems, platforms, and environments. 

Redwood Workload Automation can increase efficiency, reduce errors, and free up resources for more strategic projects by automating repetitive tasks and workflows.

The scope of the Redwood Workload Automation use case may vary based on the organization's specific needs. Some businesses will use it to automate a single process or application, whereas others will use it to automate multiple processes across multiple systems and platforms.

My job requires me to handle 24+ applications at the same time. It entails constant monitoring, file processing and transfer, and complicated workflows. 

The main reason for using Redwood Workload Automation Software in my work environment is the use of automated and optimized business processes across multiple systems. 

It simplifies complicated workflows and task scheduling. Redwood software improves operational frequency while decreasing downtime. It aided my company in meeting SLA (Service Level Agreement) and compliance standards. It also offers alert capabilities to avoid errors and complex circumstances, which increases the efficiency of my company. 

Redwood Software also provided automation solutions for SAP and Oracle applications, which was beneficial to me because our work setting relied on these technologies.

One of Redwood Software's features that I liked was its event-driven automation, which allows IT teams to respond to real-time events, alerts, and notifications from numerous systems. The program also includes built-in analytics and reporting capabilities, allowing users to gain insights into task performance, workload optimization, and resource utilization.

We can simply integrate the existing IT infrastructure, including databases, applications, and platforms, using Redwood Software without any extra development or coding.

Redwood automation software could be made more user-friendly and intuitive, making chores and automation processes easier for users to complete. This could be accomplished with improvements to the user interface, instructions, and user training.

Allowing users to customize workflows and automate a wider variety of tasks could make the software more flexible. This could be accomplished by providing more pre-built automation components as well as making custom components easier to build.

Apart from this, Redwood is doing really great, and it's highly recommended 

We use this for scheduling SAP batch jobs.

The jobs can be scheduled as per the requirements.

We can easily import jobs from SAP ECC systems.

As it has pre-defined options and it helps in managing the jobs.

We can connect to many third-party systems.

There won't be a memory outage issue, as it uses its own server/ECC memory only.

Without any interruptions, Redwood can connect to N number of third-party systems/legacy systems. There won't be any interruption to the job.

With an easy search option, we can get details about jobs.

We can schedule a batch job for all third-party systems and help to schedule jobs as per the regional/country time.

The alerting mechanism prevents business impact, and we have no need to log in to the SAP system and monitor batch jobs. Whenever any job fails/is long-running we immediately get an email notification and we can take necessary action.

It offers easy scheduling of jobs daily/weekly/monthly.

There are many filters we can use to check the job status. There is also a customized filter option which helps to get the reports as needed. 

As this contains almost all the time zones, we can schedule jobs as per the regional/country time.

The best part of the tool is the submit frame & time window where we can schedule jobs as per the requirements.

We can schedule a batch job for all third-party systems.

This tool supports all browsers.

As it includes alerting mechanisms, it helps to avoid some business impact.

Without any interruptions, Redwood can connect to N number of third-party/legacy systems. Once the job is scheduled, there won't be any interruption to the job.

We need the automatic creation of incidents for failed jobs.

In the dashboard, it could show the total count of jobs in a system, for example,  how many are in running/scheduled/held/event wait states.

In reports, if we have pre-defined reports such as killed/completed jobs of that particular month, it would be easy for auditing purposes.

If there's a direct export option, it would be great. Every time we need to run a report to export the data.

Submit frame/time window could have more pre-defined options, which will help us to schedule the job easily.

It's been a year of using this tool.

We did not use a different solution previously.

It is cost effective.

License renewal is a very easy process.

We did not evaluate other options.

It's used for all of our SAP applications. We have ERP, CRM, and data warehousing. It's used for our PeopleSoft, and it's used for some of the other corporate internal applications. Informatica Data Warehousing uses it.

I don't build jobs. I'm part of the team that did the version and the infrastructure part of it. Our teams go through the process definition and the chain definition for the most part, and I believe they do not use the visual process editor.

In terms of deployment, the core of it is SaaS, and you still have some internal servers. It's never 100% SaaS.

Going to a SaaS solution has eliminated some of the down times that we needed to install some of our patches. For our agent servers, we're able to create redundant servers so that we can take one down at a time and not involve any downtime. So far, the various upgrades that we received had extremely short outage durations of one or two minutes. The ability to stay up-to-date and current, both from a security standpoint and from an application enhancement standpoint or bug fixes, has been fabulous as compared to an on-prem solution, which would take a long project to upgrade. That's probably been the biggest benefit. Moving to a SaaS solution has a lot of advantages. When you're running factories and projects 24 hours a day and seven days a week, uptime is very important, and you try to minimize any downtime, even planned downtime.

It has dramatically reduced the time and effort that our organization spends on deployment, updates, and maintenance. With our other application, it would be a six-month project to do a major upgrade. So far, with the upgrades that have been done by Redwood, the downtime is only for a few minutes. There is a gigantic difference.

We're pretty heavy into SAP. They have a good SAP interface where we're able to create and utilize jobs even from SAP, which gives us some additional features. It's about the same on the other applications that are simply running command-type batch jobs, but the SAP interface gives us a lot of flexibility. Some of it's similar to what we already had, but it has a positive impact on us.

It's a very powerful tool. It has a lot of flexibility for how you can define jobs and build them. There are different ways in which you can construct jobs depending on your specific needs and requirements. It has a lot of features for different ways that you can build jobs, which is great for power users but a bit confusing for newcomers because there are a lot of different options. 

It lacks some of the common reporting features. I'm a bit surprised that there aren't some standard reports to be able to extract any data on usage. They've described to us that customers have different reporting needs, so they let them develop those, but reporting is a common need. It would be helpful to have it as part of the solution.

One of our business groups has used Redwood SAP BPA for at least 10 years before I started working with it, and then the rest of our teams moved over from AutoSys to Redwood over the last year and a half.

It has been pretty stable. Performance-wise, we've had to work on it a bit simply because of our volume. That's more with database performance. We haven't had any problems with any jobs because of any bandwidth performance.

So far, it's been good. It scales. As we did the conversion, we did probably eight different deployments or eight different sub-projects to bring various applications live. That part of it scaled very well, with the exception of some of the performance of the database tuning, which took some time, but part of it had to do with the high volume of jobs that we run.

It's deployed across a broad list of applications, across multiple data centers. Its users include business people, developers, and schedulers for jobs. There are hundreds of people who use it.

I have contacted them. I would rate them an eight out of ten at this point.

Positive

Over the last year and a half, we've migrated from AutoSys to Redwood. We switched because of their roadmap and their commitment to keeping the product fresh by patching on a regular basis and providing regular updates. Looking at other competitors, there was also the cost-benefit.

The future of AutoSys was unclear. It was a product that we had used for almost 25 years, but the roadmap was unclear on whether that was going to be a viable product going forward. It put us onto a SaaS product that is definitely more stable and gives us a roadmap into the future for enterprise-wide job scheduling.

Redwood is a little more complex than the AutoSys application we used before. It creates some challenges from the standpoint that there's a two-step process. You build a job and then you schedule the process to run. You build a process definition or a chain definition, whereas, in AutoSys, you do it basically in one step. That part has been a little bit more difficult, but it has given us a lot more flexibility, specifically in terms of the ability to write some very complex calendaring that we couldn't quite do before for the scheduling portion of it.

It was complex. We had a high number of jobs, and we had a percentage of jobs that were very complex in terms of how they were built. Also, we were moving from a system that had been in place for over 20 years. So, you don't always have experts around who understood why it was done that way, but the conversion pretty much brought everything over the way it was executed before.

We spent a year. Part of that was the volume of jobs that we have and the number of teams involved. We've got multiple job scheduling teams by application. We don't have one central team, which made it more difficult from a conversion standpoint. There were a lot of people to train.

As a job scheduling tool, Redwood has reduced the footprint for what's needed. There are still process servers that are required to be inside in order to communicate with SAP and keep the communication inside, which is good from a security standpoint, but the core application is in the cloud. So, we're not responsible for patching the database or patching the core components of the application. This means our upgrades have become very simple because it's a small agent that gets updated during any software release. So, the actual upgrade process is just a few minutes of downtime, which has been a huge benefit. Server-wise, we probably have the same number of internal servers because there are some gateway servers that are utilized, and we've duplicated them and made them redundant so that we can take down and patch them one at a time to minimize any downtime and failover capabilities. Our net is probably similar, but the planned downtime is significantly or exponentially less.

Being hosted on SaaS has reduced the patching requirements that are needed. Any of the connectivity and vulnerability requirements are pretty much handled by the application now, so we don't have to deal with that internally. When you move to a SaaS solution, you're at the wind of the internet, if you will, for final connectivity, but it's not quite as important in job scheduling because your jobs, once they fire off and run, continue to run on the application servers if there is any outage. So, it's not like other applications that are more chatty or require a persistent connection.

We used the Redwood migration team. Our experience with them was good. They are sharp people, and they know their product very well. Alex Borders was the most helpful. He was our lead for the conversion. He had a huge wealth of knowledge.

From our side, there were two of us who worked on it from a standpoint. I worked on it from the technical side, and the other person worked on it from the governance side in terms of whatever we had to change internally process-wise, but each application had its own teams involved in it. So, there were hundreds of people involved in it. Most of it was from the testing and training standpoint for the job support and job processing teams, basically our developers and schedulers.

We're not even a full year into running it yet, so it's a little hard to provide any input about the ROI.

It initially surprised me because we went from an application that was priced by connection to agents/the number of agents to an application that was priced based on the number of job executions. At that time, many of the products we looked at were also priced on job execution. That seems to be more common in the business or in the vendors that provide solutions out there, but that was probably our biggest difference.

An evaluation of other products was done, but we had already used the SAP version of Redwood. So, we were already familiar with its capability. The fact that we already had people who were familiar with supporting it weighed pretty heavily into it.

It's important to do a PoC, take some of your complicated processes, and ensure that your expectations are met.

For the people I work with, the time freed up from using this solution is about the same because we were already using an Enterprise job scheduler. It's probably the same workload. Similarly, the reduction in service interruptions and process failures is the same, but we've drastically cut down our planned downtime. 

I would rate it a nine out of ten.

Redwood RunMyJobs is mainly used to make job schedules happen automatically. I've used it for important tasks, and it's been really helpful. It's a dependable and efficient platform for automating important work processes. 

You can also use it to automatically back up your organization's data every day. It shows how well your organization is doing and tells you if something important doesn't work. Redwood RunMyJobs has saved me a lot of time and effort because it does my job schedules automatically. 

I would recommend it to anyone who needs a good tool for getting work done on time. One great thing about it is that it's good at handling errors and can work with other systems. It's easy to set up if you know a bit about it, and it's user-friendly. It helps you get more done.

Redwood RunMyJobs made my organization work better. It saves us a lot of time and money by doing jobs automatically. It also reduces the mistakes that people make. 

The tool is really good at keeping our data safe when it's being used. We can connect it to other systems and programs easily. It also tells us how well our work is going and helps us find and fix mistakes. 

Redwood RunMyJobs is a tool we can trust. Redwood makes things happen automatically and smoothly. It helps make the process of creating and using software easier, so we can deliver it faster. This means we can keep testing and using it all the time. This saves time, makes our software better, and lets us control how we build it.

This solution is like a reliable alarm system. 

It sends alerts right on time, telling everyone when a task is about to fail because it's taking too long or when it's stuck unexpectedly for a while. 

It also lets everyone know when a job is successfully done, making it easy to keep track of our work. It's a super useful tool for doing repetitive tasks, and it saves a ton of time while making sure mistakes are rare. 

When we need to stop all scheduled tasks, especially during updates or downtime, we can pause them easily.

It would be nice if Redwood RunMyJobs could work on different systems. 

The support team is helpful, however, they could be even better at reaching out to users who need help. 

If the reporting options were more flexible, it would make the product better. 

Also, if the way it looks and works is easier for people who don't know much about tech, that would be good. 

Redwood provides an advanced form of scheduler that supports multiple applications and workflows by automating the process. This makes room for innovation that helps users to innovate rather than perform a repeated process. 

This being a SaaS automation tool, we benefit from integrating with other technologies across the enterprise and consolidating workflows across different environments. 

It helps us overcome limitations and gaps in complex processes that function between various resources. Process flows can be created and managed well. 

The cloud, data, and file management capabilities are remarkable.

The file transfer, cloud, and data can now be managed well.

Jobs can be scheduled, integrated, and automated without much effort.

There is an opportunity for innovation.

This product is simple and easy to use.

Redwood unifies the process by being user-friendly which makes work simple and easy to navigate across. It patches the gap in complex processes that function between resources. The solution scales and integrates with different technologies. It helps people overcome monotonous and repeated processes by providing the opportunity to innovate and think out of the box. 

It is uniquely designed for maximum benefit and scalability.

Redwood unifies the process by being user-friendly which makes work simple and easy to navigate across.

The product helps people overcome monotonous and repeated processes of work by providing the opportunity to innovate and think out of the box.

I like the following features:

• File transfers, cloud, and data can be managed well
• Jobs can be scheduled, integrated, and automated without much effort
• There is always an opportunity for innovation 
• Simple and easy to use

There is nothing much that the product should improve on except for adding new features. They should provide an easy-to-go-through document for beginners to understand and use the solution hassle-free. 

The product can improve customer service. 

Apart from these, it has impactful and unique features that stand out from any other application used. They are helpful in bringing people out of their comfort zone as they have room for innovation. 

Redwood is primarily used for DevOps automation in our business for agile, functional application delivery. 

It helps in creating logical workflows from the data center to the cloud with automation. Redwood easily manages and coordinates complex processes and automates their interdependencies without manual intervention which is an impressive feature. 

Every step is fully logged and auditable at a process level, without manual intervention. It can visually combine workflow steps into the process chains.

Redwood has helped in automating the scheduled tasks and jobs. 

We can create and test micro-workflows to find defects sooner. Redwood helps in eliminating repetitive and time-consuming manual steps for better productivity. 

The tool is very compatible with multiple CI/CD tools. Every step is fully logged and auditable at a process level, without manual intervention. It can visually combine workflow steps into the process chains. 

It enforces consistent business and IT service standards across the enterprise without extra manual effort.

Redwood Software has many excellent features, including, automating any number of tasks without lagging, and provides multi-tier environments like development, test, and production. 

It has an event-driven automation feature for accurate, complete data and faster results. 

Built-in SLA monitoring allows you to meet your SLA targets and get early warnings for deadline breaches. 

We can create and test micro-workflows to find defects sooner. 

Redwood helps in eliminating repetitive and time-consuming manual steps for better productivity. The tool is very compatible with multiple CI/CD tools.

Redwood Software has a high price tag, especially for small and medium-sized businesses that might not have the funds to engage in a complete automation system. 

The initial setup of the software is quite challenging. There are some difficulties faced during dependencies set up under jobs. 

The customer support and documentation part can be improved for much better response and understanding. A course could be provided on the tool in the market about the importance and usage. 

Apart from the above, Redwood is doing great at its automation and is highly recommended

 I've used the solution for two years.

We did not previously use a different solution.

We did not previously evaluate other options.

RunMyJobs has been used in our security project. 

We have a security monitoring tool that would trigger alerts for the pre-defined conditions, and RunMyJobs would send a request to the integrated ITSM. That way, automatically incidents are created with the data populated from the triggered alert. The associate can then investigate the triggered alert and report incidents.  

This has reduced the manual work for associates and has provided more time and concentrate on the critical business task.

This solution has cut down on the manual work the associates need to perform to create incidents for the triggered alerts and as well as eliminate the scope of error and also provides associates more time to concentrate on investigation and also other critical business tasks.

The associates are also able to get the status of the process through the dashboard which has most of the critical data needed to know on the process. This is faster and more efficient as it is integrated for incidents. It allows the team to meet the SLA defined by the customer.

RunMyJobs can be easily integrated with other software to perform automation. Our team was able to integrate it with the ITSM tool as well as security monitoring tools to make the incident creation process automatically feasible. 

Rather than going through a number of documentation and support calls, an individual can easily implement the tool and also provide knowledge transfer to the team members. 

The dashboard provided can be made more visually appealing and could include more critical data that would help associates in one glance get the required information.

There can be more pre-built integration setups that can be used based on the changing business requirements. Due to the lack of this, we are forced to integrate adapters. Not all third-party tools are easily integrated into the Redwood RunMyJobs for automation purposes. 

I've used the solution for less than a year.

This is a good automation tool to implement if a company wants something to perform repetitive tasks that need to be done on a daily, monthly, or quarterly basis. 

It's a very scalable product and can take on large workloads.

We did not use any tool previous to this.

We are able to cut down the time it takes to manually handle tasks.

I'd advise others to have a detailed call with support to understand the integration.

We looked into Tidal Workload Automation.

Primary uses include:

1. Scheduling and automating IT operations tasks, such as database backups, server maintenance, and software upgrades.
2. Automating financial processes, such as accounts payable and accounts receivable, to reduce errors and improve efficiency.
3. Managing and automating supply chain processes, such as inventory management and order processing, to improve supply chain visibility and reduce lead times.
4. Automating HR processes, such as employee onboarding, benefits enrollment, and performance reviews.
5. Automating marketing and sales processes, such as lead generation, customer relationship management, and email campaigns.
6. This solution was deployed as a SaaS model in a hybrid cloud. 

The solution has helped our organization by offering:

Increased productivity. With automation in place, employees can focus on more strategic tasks that require human expertise, increasing overall productivity. 

Reduced errors. Automating tasks with Redwood Software - Workload Automation Edition can reduce the risk of human error, improving the accuracy of critical business processes.

Scalability. Redwood Software - Workload Automation Edition can scale to support growing business needs, enabling organizations to handle increasing workloads without adding additional resources.

Redwood's error-handling capabilities enable users to define how the system should respond to errors or exceptions during task execution. This feature enables users to minimize the impact of errors and ensure that critical business processes are not disrupted.

Redwood's task scheduling feature allows users to define when and how often a particular task should be executed. This feature enables users to optimize resource utilization and ensure that critical business processes are executed on time.

The following area could be improved:

Machine Learning and AI Capabilities. Adding machine learning and AI capabilities would enable Redwood to automate more complex business processes and tasks. For example, users could leverage machine learning to automatically classify documents, extract data from unstructured sources, and make intelligent decisions based on real-time data

Reporting and Analytics. Adding more robust reporting and analytics capabilities would enable users to better understand how their business processes are performing and identify areas for improvement. This could include providing pre-built dashboards and reports, as well as the ability to create custom reports and visualizations.

I've used the solution for 1.5 years.