What is our primary use case?
We use Fortra's Automate primarily to automate different tasks that different users would otherwise have to do manually, whether running secret queries, pulling files off FTP servers, or uploading files to FTP servers, primarily logistics. You'd be sending and receiving EDI documents, sending inventory files, transferring data to and from customers, and running general reports, whether exception reporting or regular inventory. We're even using it in payroll to set notices when people work overtime. We get reports from the payroll provider. We have automated reports for our transportation business. The solution is the whole company.
How has it helped my organization?
Automate in pre-judge instances was primarily a work multiplier, so it helped alleviate a lot of the work for our customer-facing team members, provided an additional set of services and tools from IT to the business, as well as supporting sales, customer service, and accounting in many ways.
What is most valuable?
Compared to other vendors, it's the scheduling tool because a lot of vendors want to charge you extra for their enterprise-level license to have a scheduling tool built in to give you the ability to set up regular schedules to run and do certain data checks. For example, you can run a report and then query the data. For example, "If there's any data here, send it. If there's no data, then end the task." There are a lot of checks in there, a lot of data readers, OCR readers, SQL query readers, and general data tools. They're very helpful.
What needs improvement?
It would be an improvement if Automate had better stability tools, whether by recommending a certain amount of memory because it can be a memory hog at times, depending upon the type of application or license you run. Fortra does have an enterprise-level automated manager to manage different automated machines running on different servers. We primarily used a desktop version before they discontinued the desktop license. So, going on to the Automate manager, the enterprise manager is a good tool for using it to check the different servers that are running the actual tool. Maybe there are more alerts built into the enterprise tool to check on things like system memory, uptime, or any freezing in the OS versus the application in terms of turning the application from a piece of software into a service or a system running in the background.
For how long have I used the solution?
I've used Fortra's Automate for about 14 years.
What do I think about the stability of the solution?
The software's stability is great, but you have to be very careful about the environment you have it running in because you have to make sure you have this much memory and backend processing because Automate can be resource-intensive. Of course, that depends on how many tasks you run on the application, and the more tasks you run, the more resources it uses.
What do I think about the scalability of the solution?
Only three or four people use the solution, primarily from the IT department. The whole company benefits from the solution.
Automate is extremely scalable, based on your licensing level, of course. But if you have a good software management tool built in a good environment with enough resources, you could scale almost indefinitely depending upon the number of servers and resources you have in your virtual environment. You can scale up, no problem. Just add more memory, more RAM, and more processes. You need to be more strategic about your scheduling of tasks.
How are customer service and support?
I've contacted customer support several times to restore licensing after rebuilding our server and recovering the application. We had to make sure the software was running and things like that. That's usually the primary reason I need to contact them. We need to contact them to upgrade our software because if we don't upgrade it by a certain point, you lose the licensing. If you maintain your upgrades, you maintain your support, and you maintain your licensed updated version, your backups and recovery time are free. But if you stop upgrading the application, you must buy a new license after a certain point. I experienced that myself.
Customer support was very helpful. It was surprisingly quick to get in touch with someone. I've received regular communications, regular emails, updates about the tool, and different plugins available now, but this was when they were called HelpSystems.
How was the initial setup?
I was not involved in the original deployment, but I've been involved with deploying the newer versions. In this case, there was a process with deployment because we had to pull every customer service rep for every account and what type of reports they wanted to customize to SQL and then deploy it, automate, and identify whom the reports need to be sent to. That process was just logistically challenging but not hard in the tool itself. For example, if you set it up for one customer, you can replicate the same task and just change the query, and then run it for another customer and change the folder structure and the to and from emails. You just need to go live once you set it up and test it. As a work multiplier, setting it and forgetting it is really good.
It takes about two weeks to fully deploy the solution because of the number of customers we had and the number of customer service reps, and testing and getting the customer feedback and things like that for every single customer. It took me a couple of hours for each individual, but that's just based on response time with emails and people. But once it was tested, I got the feedback, and it looked good. I just set up the schedule and ran it. It was often running. The sad thing is when you create a tool like that and make it so robust and functional, you have to maintain it. You have to then check on people to say, "Hey, does the customer still want this report? Are they still an active customer?" Because we just have automations going on, and no one's looking at them. Fortra's Automate is one of those things where if you set up too many tasks, you have to manage them. Or if you have a break/fix, like a server goes down and you have to build it back up, you have to make sure you automate your backups, replicate the server, and make sure there's a backup server, make sure you have your contacts to get a backup of license keys and everything else. That hurts because when you have an application that's so important, it hurts you when or if it goes down.
What about the implementation team?
We implemented the solution ourselves. We have a team of four IT people and consider ourselves internal customer service. It's primarily myself and my boss who oversee that project.
What was our ROI?
We've saved about a million dollars, to be honest. Because when you factor in the labor costs we saved and the work multiplication of IT by doing even system-level notifications. We just automate our inventory management system's monitors, SQL queries, and uptime. We used the monitor uptime for our network. If a particular reporting tool is down, it will send an SMS to our phones. We used Automate for cybersecurity, checking our network's access and ensuring file transfers were working. We used it in many different ways that the solution was not readily used for because we were a small IT team at the time, so we used it as a way to multiply our team and provide more services to the company while making IT another kind of profit center because of the different services we're able to provide.
What's my experience with pricing, setup cost, and licensing?
I wish Fortra would retain some lower-tier applications, like the desktop version. The enterprise-level licensing is understandable, especially with the service agreements. However, with the support they're charging, I wish they had more granular support for using the tool or helping me use our training for that location. Most of the support elements are just about break/fix and moving the licenses to different servers. Very little actual direct instruction. However, the tool is self-explanatory and user-friendly, so, in many ways, the help team directs you to the help and written resources already built. They don't have much on-hand support except for break/fix. But there are a lot of resources available.
Once you buy the software, you just pay for the support for backend help.
Which other solutions did I evaluate?
I tried using Automation Anywhere, which is a competing product. But these solutions lock different functions behind different paywalls to get you to the most expensive enterprise tools. We've only tried to deploy a competing product to compare apples to apples. Half of the functionality that we have Automate that we get out of the box, even at a desktop level. Automation Anywhere had none of those functions available from their lowest-tier application. We'd have to go to the enterprise level to get scheduling tools. The aggressiveness of Automate with all the tools and the functionality that comes out of the box makes it not unique in the landscape, with its versatility and embedded tools. Still, with every tier, Automate makes managing a more stable environment easier. And when you do anything piecemeal, it makes it harder. When you go up to Automate's enterprise tier, it feels like you're getting more than just a paywall to unlock different tasks.
What other advice do I have?
Fortra's Automate was deployed before I joined the company, so I have used it since 2008. However, we deployed the customer-facing element in 2012 when customers regularly requested things like inventory reports from customer reps. Instead of running a report from our warehouse management system, we could run an SQL query replicating the same report or drop it in our CSV or Excel file. Essentially, we created a full-customer service to automate regular reports, whether inventory reports, serial number level, item lot level, on-hand or available freight reports, summary transaction reports, or bill of lading reports. We were able to automate a lot of the reports that our customer servers sent to customers. The warehousing company is a third-party logistics company, so we provide many third-party services to our customers, and reporting is one of them. Being able to automate that process and simplify it for the end user, which is our customer service team, is when I realized the benefits of working with Fortra's Automate.'
Fortra's Automate is primarily on-prem, but we use a private hosted environment. Our servers are hosted on a VM platform by a vendor, but they all use an internal Internet network. VPN over the Internet.
We deployed two additional servers in addition to our primary original server, and we upgraded from one to the other to deploy new applications and services to our customer service department.
You do have to run regular backups because sometimes, for whatever reason, the scheduler may lose the schedule for all the tasks. It's a GUI, meaning it's a user front end. You have your schedules, tasks, and everything, but all those tasks are set to certain file types. It has a surface file with all the scheduled information and all the names of the tasks listed, and then you have the individual files with the actual tasks. The application is a user front that manages the schedules and tasks, so it's very user-friendly. And the scheduler runs the VB scripting in the backend. You have to make sure you regularly backup your schedules and your reports to ensure that, if the software stops running and it loses the file, or if there's something corrupted in the application, you can rebuild it, apply the same license you have with them, and then upload your schedule directly. It's really about securing the application for the Windows environment, making sure that whatever Windows update runs, it doesn't destroy the backend grid. It's always good to have good software management regarding backend support.
I have and haven't tried integrating Automate with other solutions I'm currently using because it's running an SQL query in the background. SQL has been the primary tool in which we work with it. If anything goes off or down, SQL will be the primary tool, so you want to ensure your SQL environment stays stable to work with Automate. When SQL works well with it, it's fine. But then, when you have a lot of different third-party tools or competing applications, such as a Microsoft plugin to work with Oracle or different things, Automate has had recent challenges with that. Other than specialized tools, like specialized Java tools, which I've got to update the APIs for. But primarily with Microsoft SQL, it's great and easy to work with. Especially if you're working with Excel files, You need an Excel license installed on the machine in which you're running Excel queries. It can pull CSV data, but if you want to read and write things from Excel, you'll need an Excel application to open it in the background to pull the data. There are some quirks and things you have to have with it to utilize Automate effectively.
I want to increase the usage of automation because every software vendor has its way of doing things. I do want to make sure our team doesn't get too complacent. I'm making sure we have regular maintenance planned while using the software. That's the challenge when the software works too well, and you're lulled into a false sense of security, and if something happens, you're like, "What do we do now? Oh, my god!" You need to ensure you always have a support plan built in, backup and recovery, and structured backups, and ensure those things are working and are alive.
Because Fortra's Automate can run SQL queries, you can automate any SQL-based tasks. Type in the query, customize it, and set it up, and it'll do everything there. It'll pull in data, parse it, write data to SQL directly, and create custom reports. You could do a lot of stuff directly with SQL with Fortra. It's not just the tool itself but the APIs that the solution can work with in different pieces of software. You can upload things and pull them down from websites. There's OCR stuff from PDF. It's great. I like the tool. It's really helpful.
I rate Fortra a strong nine out of ten.
Before choosing Fortra Automate, start with what you're trying to solve. Ultimately, a tool like Automate, unless you have specific problems to solve, you wouldn't know what to do with it. It does so much. If you have a particular problem you're trying to solve, you get an idea about what you're trying to do, whether it's moving, reading, or updating a file, moving, or pulling data. If you're trying to send data, it can do SMTP upload a secure FTP. The solution can do AS2 plugins. It can connect to Oracle SQL, T-SQL, and MS SQL. It could move files on a server, log into your network, and put things in a secure location. The solution is ridiculously helpful. Fortra's Automate is a force multiplier, so if you're one person in an IT team and you have a whole bunch of automated tasks you need to do, this can take care of most of it. Automate is proprietary software that you need certain GUI access for. For the most part, if you can put it in a file, Automate can take care of it.
Which deployment model are you using for this solution?
On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Thank you for taking the time to review Automate! It’s great to see you're enjoying the no-code automation including Automate's drag-and-drop & form-based development features. We're happy to hear you're utilizing both Automate Academy and Fortra's Digital Market Place (formally known as the Bot Store) as additional resources at your disposal. Also, thanks for your feedback on the documentation of errors. I have shared this information with our product team. If you ever find you need any assistance, please do not hesitate to reach out to Support as they are always at your disposal. Thank you again!