Automic Workload Automation Previous Solutions

VpChiefT7306
VP, Chief Technology & Digital officer
We had a few solutions. Most of them were code reading oriented, but it wasn't the platform. We didn't have any other platforms. We had tested another platform in that time, a very big one, which is not really relevant to this discussion, because I don't have anything bad to say about them, only from the point that they were too robotic for us. I think that Automic came with a very good approach in the delivery level. It's important, because when you're working at the delivery level, you can see the ROI that you will receive from the implementation. It's a very good product and has a very good delivery level. Especially the guys that designed the solution over here are focused on the issues in the top 10 painful issues that we had, while resolving them during a very fast implementation. It gave us the boost to go with the digital area, the application area, and the business strategy area. View full review »
Vinit Choudahry
Technical Consultant at a tech services company with 10,001+ employees
I have been an admin on other tools as well. I was a contributor to and implemented BMC Control-M. View full review »
SrProduc3570
Sr Production Control Analyst at a logistics company with 10,001+ employees
When I started, we were already on this product, but I do know that they were using a competing product before and they felt that this product had more of what they wanted. So they converted from the competing product to this product. When the company chose this product, it was actually pre-CA, and then CA acquired the product. But for the most part, they've kept it what it was. While it has a new owner, it's still the same product. View full review »
Ruairi Brennan
IT Manager at ESB
This was before my time. I suppose we had an operations function that was shift-based. We would have a team that worked around the clock, and they would be performing the batch functions manually. Then, when Automic came in, we could operate 24/7 because Automic was doing the automation, but we only needed a team 9 to 5, Monday to Friday, in the office. This cut down on the need for a rolling shift. However, this is probably going back about 10 years ago. View full review »
Christine Bauder
Assistant Director of Production Services
We ran our Finance, HCM, and CIW processes through Unicenter. I don't believe that Unicenter was very user-friendly and they found it difficult to integrate with other applications. We ran the Student Information System batch on the mainframe using CA7 as the batch scheduler. We switched from Unicenter to Automic and from the mainframe to Automic, mainly because Automic can integrate easily with any other application or service. When we got off of the mainframe and moved the student side to PeopleSoft, it only made sense to use Automic as the batch scheduler. View full review »
ITSpeciac65b
IT Specialist Automation Service Coordinator at a financial services firm with 1,001-5,000 employees
We were previously doing manual work. There was an initiative coming from the senior management to automate more things, which is how this came about. When I joined the project, this product was already selected. I had no real say about the product. I had to learn it, because I was given CA Automic Workload Automation, and told this is what you are going to implement. View full review »
Mohamed Elazzouzi
Production Systems Engineer at a comms service provider with 1,001-5,000 employees
I used Dollar U. There are really big differences. Dollar U has decentralized methods and tools. ONE Automation has centralized tools. It is really strong and really easy to use ONE Automation. For example, for organizing, for creating applications and clients, for manipulating the agents, for the servers, it's really easy. You just put the agent in the server application with the LI and it directly connects with the Automation Engine Server. It's amazing. View full review »
Jared Kessans
Lead Systems Administrator at Great American Insurance
For the open system side, I don't believe we were using anything previously. Probably anything that they would have been using would have been Microsoft Task Scheduler or a Unix cron. But we were not using anything that I know of at the time. We did have CA-7 on the mainframe, which we still actually use on a limited basis, but that is being sunsetted. So we were not using anything really. View full review »
Axel Lambrecht
Systems Engineer at Merck KGaA
Initial reason was the projects which from SAP R2 to R3. That was the reason why they looked for a different scheduling system. Meanwhile, we are controlling nearly all SAP systems that we have, so it has a three digit number. In this area, no one has any idea of using a different tool for it. The another direction where we hope that we can move into other directions, but without the necessary management, it can't. View full review »
VInce Sola
Manager, Application Administration at a leisure / travel company with 1,001-5,000 employees
We did not have a previous solution. View full review »
Hubert Rossle
System Specialist at a tech services company
About 15 years ago, we had CA-7 from CA. Then, we changed to the UC4 Automic. Now, we are back to CA. View full review »
Aicke Sandrock
Engineering Job Scheduling at IT S Care
It was 13 years ago, we previously used Control-M and switched to UC4. This was a management decision. View full review »
SystemsE0ad0
Systems Engineer at a retailer with 10,001+ employees
The company previously used AutoSys. To my understanding, they switched for cost reasons. View full review »
Ali Imran
Head of Branchless Banking at a financial services firm with 5,001-10,000 employees
Automic has been a Greenfield project. We were the first implementation and a number of banks went with this solution after us. View full review »
Uc4Admindd71
UC4 Administrator at a financial services firm
When I came to the company, they were already using Automic. They had been using it for a long time. View full review »
Martin Mertens
Manager of Global Process Automation at Adidas Group
Our old solution was not able to deliver a real end-to-end automation. It was embedded in SAP. An excellent product for SAP so far, but it is not able to be scalable for the end-to-end. This was the reason why we did research at our company to do an end-to-end product assessment. In the end, the decision was to made to go with Automic. View full review »
Eric Gauthier
Senior System Engineer at BECU
When I joined my company, we were using an application from AppWorks. I was part of the decision process to do the beta with One Automation when UC4 bought them, and then became Automic. I was also part of the decision to stay with the platform and to continue to renew each year. View full review »
Mladen Stankovic
Systems engineer at a comms service provider with 5,001-10,000 employees
This is our first job management solution. My managers made the decision to buy it. The important criteria when selecting a vendor to work with are * Good support * A good product. Good support is very important for us. View full review »
Alan Soucy
SCM
We switched over 20 years ago. View full review »
UnixAdmiff01
Unix Administrator at a manufacturing company with 1,001-5,000 employees
We actually have an older product AppWorks 6.0 that we currently use, and we are transitioning from AppWorks to Automation several months from now. We are currently in the developmental stage. The current solution we have is not supported, which is why we are switching. View full review »
Alain Feyereisen
Application Operating Service Manager at a financial services firm with 201-500 employees
In the beginning, we used a banking solution which was running on one platform. It was AS/400 at the time. We were changing the banking platform so it moved to a new platform. The old scheduler did not exist for the new platform. Additionally, the new banking solution needed an adapter, so we also needed a solution which could interact with this banking solution. We had more satellite systems, so we also had to handle the planning between different systems and the old scheduler, which was one platform based and it could not handle it. That was the initiative to choose a new scheduler. View full review »
Adrian Northage
Automic Admin at IT Service Solutions Service Delivery
We bought this back in 2004. We were upgrading all of our systems to SAP systems, and we wanted a scheduler. We did not want to use the SAP scheduler, so we were recommended UC4 (as it was at the time). That is why we brought it in. It was for our SAP system, but we use it on all applications now. View full review »
MichaelJones
Lead Production Control Specialist at SAIF Corporation
We have a lot of legacy systems and we're implementing new systems and applications to take over the old things. We're an insurance company so we have claims, and policies, and AP, and financials, and payroll. Old systems get old, and as we're implementing new systems, AppWorks or Automic now, just fits. It's just the best there is, so, it was a no-brainer. We had such success with AppWorks. And then we went to this big RFI to figure out what we were going to change to because we didn't want to upgrade AppWorks anymore. But the success that we had with AppWorks - and then when Automic bought it - it was like a no-brainer. We would just go with them. View full review »
ArchiveA93e0
Archive And Research And Development Lead at a manufacturing company with 10,001+ employees
The older version wasn't performing as well because we pretty much maxed out what it could handle with our thousands of jobs we run a day. So, the Automation solution was brought to us and we said, "Well, this thing could supposedly handle it," so we've gone to it, and so far so good. View full review »
SeniorPrd2b5
Senior Programmer at a manufacturing company with 1,001-5,000 employees
We were replacing AutoSys. We saw Automic as a better version of it, which it definitely has been. We replaced that an existing solution because it was no longer fit for its purpose. View full review »
Michael K.
Systems Administrator at a financial services firm
We were previously using CA-7. View full review »
Associated2d
Associate Director at Pbb Deutsche
We had a couple of solutions in place starting from Windows, Unix crontab, and other batch controlling software (like Control-M, Redwood, etc.). Batches interact with all applications, so the batch structure is more complex and using different tools was not a solution. Therefore, we needed to have one single workflow as a solution for us, and we made the decision to have one tool in place. Then, we did an evaluation, and the winner was CA. View full review »
SeniorSy2f47
Senior Systems Engineer at a non-tech company with 11-50 employees
In the past, we had CA-7. CA built this mainframe schedule. Then, we have canceled the contract to CA, and decided to go with UC4. Now, UC4 is a part of CA, and now we have a contract with CA again. View full review »
Hartwig Esch
Administrator at VW Financial Services
We had a previous solution. It was Control-M. We switched because there were some issues around the costs. Automic's costs were lower. View full review »
Yalin Yuksel
System Specialist at Türkiye İş Bankası
We were not previously using another product. However, we did have our own automation solution (scripting). Before Automic, there was no automation product. View full review »
Achim Henkman
Service Management at Siemens Industry
We did not have a previous solution, just something we built in-house. We have been using this solution for 20 years. View full review »
Norbert Bollinger
Production Services at a government with 1,001-5,000 employees
We were not previously using another solution. View full review »
Roman Rauchwarter
Systems Analyst at a tech services company with 1-10 employees
We used just shell scripts and crontab. View full review »

Sign Up with Email