Project Manager at a energy/utilities company with 10,001+ employees
Real User
Limitless scalability, good support, and it has improved our incident resolution time
Pros and Cons
  • "The integration with ServiceNow is good. When a job ends and there are problems with it, we automatically open an incident in this platform, and the number of the incident is forwarded to Control-M. This means that we have a record of it with the log of the job."
  • "Integration with some applications and platforms is complex and requires development. We have done some integration with the application integrator, but it was more like a manual solution. This is an area that can be improved."

What is our primary use case?

I am a project manager and am responsible for the Control-M infrastructure.

Control-M is the only batch infrastructure that we have, so we run all of our batch activity on the platform. We are using the web interface, for example, the workload change manager and application integration. There is not a particular sector but rather, we run all of our batch jobs on this tool.

How has it helped my organization?

Control-M provides us with a unified view of our workflows, which is important to us because our processes are standardized. We have set up a company that is used mainly for scheduling, which is also involved in creating flows and monitoring them. As such, standardization from the point of view of the user is important. Effective standardization facilitates our work. 

We have automated many processes with ServiceNow, including some that are critical. For example, if we need to stop 100 instances, we can open a ticket in ServiceNow and it automatically creates the job flow in Control-M that sends the command to stop the instances.

The integration with our incident management platform has meant that we have been able to achieve faster issue resolution. The reason is that we have eliminated the manual phase of opening an incident. It was very time-consuming and it is not easy to calculate how much time we have saved, but I estimate that our process is 70% faster.

Control-M has helped us to improve the performance of our service-level operations by approximately 60%.

What is most valuable?

The integration with ServiceNow is good. When a job ends and there are problems with it, we automatically open an incident in this platform, and the number of the incident is forwarded to Control-M. This means that we have a record of it with the log of the job. This is a feature that reduces manual work. It is not officially included in Control-M; rather, it was developed for us by BMC.

The web interface supports us well because we have done some customization for each area of our company, and the client can see all of the jobs that they are interested in seeing. One can watch their flow on a phone or tablet. For example, we have integration with WeLink and our clients can see the flow of the billing workflow.

We use Control-M as part of our DevOps automation, and for our company, this is very important because it reduces the amount of work that has to be done. We are a very big company and we have millions of jobs scheduled. The more that we can automate, the better it is for us.

What needs improvement?

Integration with some applications and platforms is complex and requires development. We have done some integration with the application integrator, but it was more like a manual solution. This is an area that can be improved. 

Buyer's Guide
Control-M
July 2024
Learn what your peers think about Control-M. Get advice and tips from experienced pros sharing their opinions. Updated: July 2024.
792,905 professionals have used our research since 2012.

For how long have I used the solution?

I began working with Control-M approximately 20 years ago.

What do I think about the stability of the solution?

In past versions, there were issues with stability and it was a negative experience for us. However, in the version we have now, stability has improved. At this point, the product is good and stable.

What do I think about the scalability of the solution?

Scalability-wise, there are no limitations. We have between 500 and 600 users including our DevOps team, applications teams, and others. For example, some people work on solving problems, others handle scheduling, and some only use it for viewing or monitoring the workflows.

How are customer service and support?

We have a strong collaboration with BMC and we are constantly in contact with them.

The support is good and we are satisfied with it. In general, the responses are fast and the solutions that they provide are good.

Which solution did I use previously and why did I switch?

In the past, we migrated from IBM's Tivoli Workload Scheduler (TWS). We did not use the Control-M migration tool at the time because it had not yet been developed. We completed the migration manually.

The reason that we switched to Control-M is that we stopped using the mainframe.

How was the initial setup?

There was no particular problem for us in regards to the implementation process, as we had BMC to assist us. We have a very large environment and our migration took between twelve and eighteen months. We have thousands of agents and many Control-M environments.

We did not follow a particular implementation strategy.

What about the implementation team?

For implementing and setting up Control-M, we collaborate strongly with the BMC team.

We have approximately 20 people of varied roles in charge of the day-to-day administration.

What was our ROI?

My impression is that we have seen a return on investment from using Control-M. As it is our only solution for batch processing, it helps us to centralize all of the batches that we have. This, along with the standardization of workflows, are the most valuable features of this product.

What's my experience with pricing, setup cost, and licensing?

The licensing is managed by the commercial section of our organization.

Which other solutions did I evaluate?

We evaluated several options and we found that Control-M was the most complete solution.

What other advice do I have?

We use Control-M to integrate file transfers within our workflows, although we don't use the managed file transfer capability that comes with it. We are currently analyzing it and we are deciding whether to use it or not. At this time, we use other programs for our file transfers. Our analysis will show whether we can migrate the process to this new feature.

Overall, Control-M is a good product. We do have small requests that we give to BMC, although they are very specific. The product covers a good percentage of our needs, as-is.

This is a product that we will continue to use and I can recommend it to others. I expect that in the near future, we will migrate to the most recent version, 9.20, and that we will use some of the newer features that it offers. That said, there is always something that can be done to make a product better.

I would rate this solution a nine out of ten.

Which deployment model are you using for this solution?

Public Cloud
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.
PeerSpot user
Senior Associate at a tech services company with 10,001+ employees
Real User
Our application team has visibility on what jobs are running and what jobs are failing
Pros and Cons
  • "It has a very good GUI. We can search for a job very easily. The web interface, user account creation, and access control are very good. From an access control point of view, we can provide access to as many users as we want. A second group of users can be given a certain number of features, according to the requirements. The web interface is very easy for end users to login and use. A lot of features have been added, e.g., adding jobs. They can add jobs to their stuff, whatever they want, then get it validated by the scheduling team and work it into production."
  • "A lot of businesses are using ServiceNow, which is another tool. I would like there to be some integration with ServiceNow or other third-party tools as well as have easily available integrations. Right now, we need to write scripts. Apart from that, if there were some integrations with an ITSM tool, then that would be good. Because at the end of the day, most of our clients are using different ITSM tools. I know that BMC Remedy is easy to integrate with Control-M. However, if there was availability for Jira as well as other ITSM and DevOps tools, that would be a good improvement."

What is our primary use case?

We are mainly scheduling jobs on Linux Windows, SAP, and DataStage environments; a few other application integrations, like Micro Focus, and third-party applications, like Web API.

We are using it for banking and financial services.

How has it helped my organization?

We use Control-M as part of our DevOps automation toolchains and leverage its “as-code” interfaces for developers on a few JSON-based script applications. This is in the testing phase, but in production for one or two applications, and rolling out new applications and application updates is much faster. Earlier, we had to go through a lot of processes. We had to raise a change request and work through various approvals, then the scheduling team would do it and there would be a lot of failures. Now, they are directly creating those jobs and submitting them. It is coming in automatically because it is running in Control-M.

Multiple critical processes have been automated. Here are two of those processes:

  1. Our critical banking application for end users, especially to check their bank data, e.g., how much is in their account, how much money they have withdrawn, etc. 
  2. It is used for ATM withdrawals and runtime data, e.g., SMSes go out with how much has been debited or credited in their account.

Automating these processes provides more visibility to our application team. They can see critical jobs failing and immediately taking action in Batch Impact Manager (BIM) with the help of our team.

What is most valuable?

The most beneficial features are the Forecast option and Archiving feature, as well as the integration option with other applications and tools to the API. When it comes to the API integration with any third-party tool, we can integrate using the application integrator tool and API interface with web APIs, which is the best part. Control-M has its own Forecast solution. Therefore, we can forecast how many jobs are going to run, on which day, and at what time. Another benefit is the tool's Archiving feature. So, we had a lot of requirements, like when an application or end user team would say that they want to see the log or output of the job from two or three months before. So, the archive solution is very helpful because we can keep at least a year's worth of data for our environment.

It has a very good GUI. We can search for a job very easily. The web interface, user account creation, and access control are very good. From an access control point of view, we can provide access to as many users as we want. A second group of users can be given a certain number of features, according to the requirements. The web interface is very easy for end users to login and use. A lot of features have been added, e.g., adding jobs. They can add jobs to their stuff, whatever they want, then get it validated by the scheduling team and work it into production.

What needs improvement?

A lot of businesses are using ServiceNow, which is another tool. I would like there to be some integration with ServiceNow or other third-party tools as well as have easily available integrations. Right now, we need to write scripts. Apart from that, if there were some integrations with an ITSM tool, then that would be good. Because at the end of the day, most of our clients are using different ITSM tools. I know that BMC Remedy is easy to integrate with Control-M. However, if there was availability for Jira as well as other ITSM and DevOps tools, that would be a good improvement.

For how long have I used the solution?

I have been using it for almost 12 years.

What do I think about the stability of the solution?

It is very stable. If we are using agents, it runs without any issues. I have sometimes found issues when we are running it with an agentless solution. However, with the agent, it does not have many issues. It will have an issue once or twice a year.

What do I think about the scalability of the solution?

It is a very scalable solution. 

Almost all our end user application teams are using it. 

For day-to-day administration, we have two people. For scheduling, we have four people. 

How are customer service and technical support?

The integrated guides and how-to videos in the solution’s web interface is a good approach. There are a lot of documents and webinars. Also, the support is very good. We receive good responses very quickly.

I would rate the technical support as nine out of 10.

Which solution did I use previously and why did I switch?

We migrated from Tidal Automation. In Tidal Automation, various options are not there. So, jobs are running mostly using an admin account. When all jobs are running using an admin account, that is a risk. However, in Control-M, we have various options. We can use an admin account as well as a separate account, like a user account, to run jobs. Whereas, these features were missing in our previous tool. 

We switched from Tidal to Control-M because the application team wanted more control. There is a web-based solution for Tidal, but all the data is shown there. For example, if there are 10 applications, then the web applications team can see all 10 applications, though they might only want one application. Even if the backup team wants to view just their backup jobs, they see all the applications that are working. However, in Control-M, we can control whatever applications that we want, limiting what can be seen by each team. 

How was the initial setup?

The initial setup was easy. BMC provided all the documentation before starting. They did it in the development environment and targeted various applications. They showed us what they were doing before they implemented it. So, we were coordinating with them.

Deployment took three months.

What about the implementation team?

I was involved during the initial setup. It was done by BMC's professional services team and I was part of the support.

What was our ROI?

It is a good investment. I think we are paying the same amount of money for Control-M that we were paying for Tidal and not getting as many features.

Control-M has helped us achieve faster issue resolution. It is 60% to 70% faster than what was happening before.

Service Level Operations have improved in the sense that fewer team members are required as compared to before. So, we had a bigger team, and that has been reduced because of Control-M's latest features, like development. Therefore, a lot of things are now being done by the application team instead of having a separate scheduling team, which has now been reduced. The application team is currently being trained to handle more things on their own. They also have visibility on what jobs are running and what jobs are failing.

What's my experience with pricing, setup cost, and licensing?

In our environment, pricing depends on the total number of maximum jobs that can run, which is fine. Therefore, if the number of jobs increases, then the licensing fees will increase.

Which other solutions did I evaluate?

I have hands-on experience with Redwood and ActiveBatch solutions. If there are a lot of Windows requirements with Windows jobs, then definitely ActiveBatch is the best solution. If we see there are a lot of SAP-based requirements, then Redwood is the best solution and either Redwood RunMyJob or Redwood CPS work for this. If we see Unix or any other application with jobs, then Control M is the best solution.

What other advice do I have?

While we do use Control-M to streamline our data, we don't use it much to view our data and analytics project since there are various third-party applications of the bank where jobs are running. The major work that we do is creating and adding those jobs to the tool.

We are not using file transfer at all because we are a US-based financial company. They have a lot of restrictions for file transfer between third-parties, so Control-M is not used for file transfers.

It is one of the best scheduling tools in the market for batch job automation and DevOps.

I would rate Control-M as nine out of 10.

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. The reviewer's company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Buyer's Guide
Control-M
July 2024
Learn what your peers think about Control-M. Get advice and tips from experienced pros sharing their opinions. Updated: July 2024.
792,905 professionals have used our research since 2012.
Operations Support Analyst at a retailer with 5,001-10,000 employees
Real User
Speeds up ticket resolution for opening and assigning a ticket
Pros and Cons
  • "Control-M provides us with a unified view, where we can easily define, orchestrate, and monitor all our application workflows and data pipelines. It also provides the ability to filter. So, if I don't want to see everything, I can also narrow it down or open ViewPoint. This is very important since we have thousands of jobs to monitor. If we did not have this ability, it would be very difficult to see what is going on."
  • "Control-M reporting is a bit of a pain point right now. Control-M doesn't have robust reporting. I would like to see better reporting options. I would like to be able to pull charts or statistics that look nicer. Right now, we can pull some data, but it is kind of choppy. It would be nicer to have enterprise-level reporting that you can present to managers."

What is our primary use case?

It provides enterprise scheduling for a lot of things, e.g., supply chain, payroll, reporting, sales and marketing, and web services, which is our online store and ordering.

We are currently running jobs on Control-M for databases, web apps, proprietary applications, Workday, Oracle, WebSphere, Kafka, and Informatica stuff on Unix and Linux. It is flexible. I haven't had any problems with compatibility.

It used to be on-prem, but now it is in a different data center in a different city. So, it is a VM.

How has it helped my organization?

We use the GUI, but there is a web interface that some users are using on the business side. Those users can easily check on their job flows on the web interface, so they can see whether their job has completed or it is waiting for something. It can check the status and  history of what happened, for example, the previous day.

What is most valuable?

The scheduling is quite easy to use and pretty robust.

Control-M provides us with a unified view, where we can easily define, orchestrate, and monitor all our application workflows and data pipelines. It also provides the ability to filter. So, if I don't want to see everything, I can also narrow it down or open ViewPoint. This is very important since we have thousands of jobs to monitor. If we did not have this ability, it would be very difficult to see what is going on.

It is easy to use, and you can set things up very quickly. We can copy jobs, making copies of the existing configurations and setup. 

What needs improvement?

Control-M reporting is a bit of a pain point right now. Control-M doesn't have robust reporting. I would like to see better reporting options. I would like to be able to pull charts or statistics that look nicer. Right now, we can pull some data, but it is kind of choppy. It would be nicer to have enterprise-level reporting that you can present to managers.

For how long have I used the solution?

I have been using Control-M for at least 12 years.

What do I think about the stability of the solution?

I haven't seen any significant issues with Control-M in several years, e.g., we haven't had to call support. So, it has been very stable.

It runs all the time. We are running thousands of jobs with little issue, especially when I compare it to some of the other systems that we use for other things. It has been very stable.

One to two people are needed for day-to-day administration. I usually do it myself.

What do I think about the scalability of the solution?

I haven't seen any problems with scalability in terms of performance or stability. 

There are at least 50 people using Control-M. Some of them would be architects, senior programmer analysts, database administrators, Unix administrators, software engineers, and team leads.

How are customer service and technical support?

I had an issue one time at my previous company. There was some issue with the database. We worked with Level 2 support to fix it. Other than that, there is not too much to talk about really in terms of problems. 

The integrated guides and how-to videos are very good in the solution’s web interface for reducing the time to full productivity with Control-M. BMC puts out a lot of webinars and videos on their YouTube channel. Sometimes I do use those. I go in and watch the video or webinar to see what is new or how to do things, which is very valuable.

Which solution did I use previously and why did I switch?

We migrated from CA Unicenter, which was out of service and quite clunky. That system didn't have a graphical user interface; it was command line-based. It had a console, so it was very difficult to see what was going on. It was also difficult to troubleshoot. It took a long time to find information or set things up. Therefore, management decided to move to Control-M, especially since I had experience with it. It has been much easier to use and work with than CA Unicenter.

CA didn't have File Watchers. It had another way of achieving that outcome, but it was very cumbersome and not always reliable. It was also difficult to troubleshoot. 

There is a lot of logic in Control-M that you can do. For example, after a job completes, there are actions you can do. There are actions before the job completes or before it starts. There are actions you can do afterwards. There was some logic that you can add to the job, and we just didn't have it with CA.

The calendars are also a lot easier to work with using Control-M. The CA calendars were just terrible. In Control-M, we have a lot less calendars, about 20 calendars, compared to 80 or 100 in CA.

It is faster to implement things like new jobs or projects with Control-M. Whereas, in the past, certain things would be executed manually, like scripts and workflows. It is very easy to use. I can set up jobs and workflows quickly, which helps developers to test.

How was the initial setup?

It is very easy to set up a PoC. If someone just wants to do a quick test, it is very easy to do. Assuming that everything is in place, it is quite easy to test or set up cyclic jobs.

We did the setup twice. The first time was a migration from another system, which was not BMC. That took three months, which was still pretty fast, and it was very successful. The second time was an upgrade to version 19, and that took about two months, and it was also quite successful. From my perspective, the solution was very good as far as upgrades go. We didn't have any major issues, before or after the upgrade.

What about the implementation team?

We had a vendor help us out, but overall it was very smooth and a success. We used Control-M’s Conversion Tool when migrating from CA Unicenter to Control-M and the vendor helped us. Using the Conversion Tool was very important because it speeded up the process. It took all the information from one system and transferred it over, which saved us a lot of time. So, we spent more time on the verification. We spent less time on the setup and spent more time just verifying the setup to make sure everything was correct. It was a time saver for us.

My experience with BMC during our initial deployments and upgrades was very good. I got quick responses with good information. The people that I dealt with were knowledgeable and helped to resolve the problems. So, my experience was very positive. I would rate them as 10 out of 10. I never had any issues.

What was our ROI?

Control-M has helped us achieve three times faster issue resolution. We have it integrated with ServiceNow, so it tickets automatically. Whereas, in the past, we used to do it manually. We had operators opening tickets, so it speeds up ticket resolution for opening and assigning a ticket. Also, Control-M captures some errors. Sometimes, this helps to troubleshoot any problems. You can set up alerts for jobs that run too long, etc. So, it has a lot of features that we use.

Control-M helped us double or triple our Service Level Operations performance.

Which other solutions did I evaluate?

CA sent us a proposal and IBM also sent one for Tivoli Workload Scheduler. We saw their presentations and packages, then did some research. We thought Control-M was the best solution based on experience and feedback from others. I had experience on Control-M already. I had been working on it for several years and had a positive experience. The other thing was just ease of use. Tivoli and Unicenter just do not seem as polished. They didn't look as easy to use, especially Tivoli. I think we heard that Tivoli was very clunky and not easy to use.

It was mostly my experience with it. Control-M was easy to use, very stable with no issues, and easy to configure and maintain. Whereas, CA was not as easy to use nor polished. CA also always keeps on buying other companies and incorporating things, so the experience is not as smooth. With Tivoli, we just heard that it was terrible to use and lacked a good interface. We had another Tivoli product from IBM for backups, and it was just terrible.

What other advice do I have?

Give Control-M a chance. If somebody is considering the solution, they should install a demo on their system and use it. It is very easy to use. It has a lot of options and features. BMC is pretty good when it comes to upgrades and implementing new features, so there is always stuff coming in. There are a lot of new options that we haven't even tried.

Of course, you should compare all your options, but Control-M is a good choice. It is probably the best.

In the future, we will probably use Control-M as part of our DevOps automation toolchains and leverage its “as-code” interfaces for developers.

I would rate it as nine out of 10. The reporting is something I would like to see improved. Other than that, there is not much I dislike about it. I work with it every day. I have been working with it for the last dozen years or so. It is an excellent product. It just needs more reporting.

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.
PeerSpot user
SAP Solution Manager and Control-M Admin at a wholesaler/distributor with 10,001+ employees
Real User
Integrates with all our applications, and saves a lot of time and monitoring effort
Pros and Cons
  • "It is an enterprise tool that integrates with all the applications in our organization. It has made our life easier because we don't need to wake up at midnight and do monitoring, etc. It does everything. It also sends precautionary alerts. If a job or activity is running for more than the specified time, it alerts the application team. So, our teams do not need to sit in front of a laptop or any open application to watch the jobs. They can do their other regular activities while Control-M takes care of all the jobs. It notifies them when there is job completion, delay, and error."
  • "We have some plug-ins like BOBJ, and we need a little improvement there. Other than that, it has been pretty good. I haven't seen any issues."

What is our primary use case?

It is an enterprise tool, and it is a critical one. It is used for scheduling all of our enterprise jobs and monitoring them. We have both cloud and on-premise applications, but Control-M is installed only on-premises. We have high availability as well as load balancing servers in the cloud as well as on-premises.

How has it helped my organization?

It is critical for our business. Control-M directly affects our business because all our jobs are integrated into it. Without it, it is very difficult for us to do the monitoring. There is application-level dependency. We have SAP, Logility, and other third-party applications, and then we also have retail applications. We have different types of jobs. SAP handles only SAP-related or ERP-related jobs. In retail, we have stored procedures, and BI has HANA procedures. If Control-M is not there, it would be difficult for application teams to sit in front of the application and wait for a job to finish and then trigger another one. We are a global company, and we have jobs running round the clock. It saves almost half of our time in a day.

It is good in terms of data transfer. We are using the Managed File Transfer plug-in. It is pretty good, and it has good features. In one place, we can see what files have been processed or what jobs have been deleted or failed. We can see everything on the dashboard. If I have to search for a particular file that is missing, I can go there and check. 

It can orchestrate all our workflows, including file transfers, applications, data sources, data pipelines, and infrastructure with a rich library of plug-ins. This functionality is critical from the application point of view.

It has had a positive effect on our organization when creating actionable data. It is pretty good. It is a critical application for us. All our jobs and integration activities are monitored and scheduled through Control-M. We have multiple projects running, and teams are continuously doing the testing in the Control-M. This is the application where they can do all the testing for high-load jobs and other things. It is a critical application for all project teams.

What is most valuable?

Cost-wise, it is good. It is an enterprise tool that integrates with all the applications in our organization. It has made our life easier because we don't need to wake up at midnight and do monitoring, etc. It does everything. It also sends precautionary alerts. If a job or activity is running for more than the specified time, it alerts the application team. So, our teams do not need to sit in front of a laptop or any open application to watch the jobs. They can do their other regular activities while Control-M takes care of all the jobs. It notifies them when there is job completion, delay, and error.

When we migrated to the SAP ERP application, a lot of jobs got created. We had to do all the things manually and monitor round the clock. Control-M has made our life easier. We can now concentrate on our applications and other tasks.

Since we have got this product in our company, our life has become easier. We don't require much L1 and L2 monitoring and support. We don't have L1 support when it comes to the Control-M application. We do have an L2 team application support, but it is minimal.

What needs improvement?

We have some plug-ins like BOBJ, and we need a little improvement there. Other than that, it has been pretty good. I haven't seen any issues.

For how long have I used the solution?

We have been using this solution since 2016.

What do I think about the stability of the solution?

It has been good so far, and I haven't seen many issues in terms of performance.

What do I think about the scalability of the solution?

Its scalability is good. We have more than 100 end-users of this solution.

How are customer service and support?

I would rate them an eight out of ten.

How would you rate customer service and support?

Positive

How was the initial setup?

I was not there when it was purchased and installed. It was already there when I came here. At that time, it was version 8. From 2017 onwards, I've been doing all the upgrades. Currently, we are on version 9.20.

What about the implementation team?

It is updated in-house. Usually, we submit the AMIGO report to BMC for the initial validation. Once they validate and confirm, we do the upgrade. They know what our environment is like, and if there are any issues at the time of upgrade, they easily find out the cause. We also have support from a third party called VPMA. We can take their help as well for critical issues.

In terms of maintenance, there are OS-level updates every month, which are taken care of by the IT team. Application-wise, we do patch fixes when a particular plug-in needs patching.

What's my experience with pricing, setup cost, and licensing?

Cost-wise, it is good. 

What other advice do I have?

I would definitely recommend this solution. Control-M is the place to go if you want to have workflow automation in place. I have previously also worked with the Remedy tool in another organization, and I found it good.

It is pretty good in terms of creating, integrating, and automating data pipelines. If you have all the information, it is a straightforward activity. If it is new functionality, then before integrating Control-M with a third-party application, you need to do some work in terms of configuration.

It is easy to ingest and process data from different platforms. Its setup takes some time, but once the setup is done, it is pretty easy.

We don't use Control-M to deliver analytics for complex data pipelines. We do have analytics, but we have an SAP analytic application called BOBJ BI. We do have a job set up for that. It runs from Control-M, but analytics are shown in the SAP application.

Our cloud usage is not much. From the S3 bucket, we are using the file transfer part from the application perspective, but there is not much integration with cloud applications. We only have the MFT plug-in to communicate with AWS S3. Other than that, there is not much interaction with the cloud from the Control-M application side.

I would rate it a nine out of ten. It has been good so far. I haven't seen any issue. It is easy to use. I still have a lot to learn about this solution.

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.
PeerSpot user
IT Operations Specialist at a retailer with 5,001-10,000 employees
Real User
It's very easy and seamless to get important files transferred in a secure manner
Pros and Cons
  • "The most valuable features are the Advanced File Transfer and the manage file transfer. They make transferring files securely seamless. It's very easy to set up, get deployed, and have it transferred to and from vendors. As long as we can get our firewall rules implemented at a decent time, it's very easy and seamless to get important files transferred in a secure manner."
  • "We've also had a few database bugs within our organization. I think we are migrating to OpenJDK rather than just regular Java and that has since shown some issues with our Control-M instance, timing out and causing our jobs to stop running. We are still working with BMC to fine-tune that and get that resolved."

How has it helped my organization?

Overall, we have a great visual of all of our key business processes, and it gives us a secure way of transferring everything in and out of the business so that if anything were to be intercepted, it would be secure and not compromised.

We transfer financial files between Google cloud. We use it for the I series. We have a lot of automated jobs, around 3,000 jobs per day, that we load that range between just regular commands for our planning allocations, finance, or data warehouse along with Google cloud. We're starting to implement a lot of that, but a lot of it has been automated and it allows us to process everything in a timely manner.

We are in the process of implementing the managed file transfer which gives us the dashboard, but we are still fine-tuning that. Overall, it does give us a great picture and helps everything. If there's something delayed, it gives us the opportunity to send out a notification to a team to say that their process is delayed. We get tickets created and have everything sorted in a timely manner.

We use Control-M's web. It makes it very easy for us to show them what they need to see and what they don't need to see. They mainly can just view the tasks that they have, but it's pretty divvied up permission-wise.

Control-M integrates file transfers within our application workflows. It has made everything a lot quicker. We've been able to get files transferred to vendors and we've been able to retrieve files from vendors rapidly and securely.

It also streamlines our data and analytics project. Mainly developers will create either different types of processes that we will implement within Control-M to make it automated and that definitely, I would imagine, helps streamline and format certain projects and reports that we send out to executives that helps out a lot. I don't know the exact extent of it, but I would imagine that it has helped our business service delivery. 

It has helped to achieve faster issue resolution. With the shouts and notifications that we get, we're able to create tickets as soon as a problem surfaces. So as soon as we do get a job failure, we get an email notification that prompts us to create a ticket, page out the team, and get it resolved in a matter of our terms of our SLA.

What is most valuable?

The most valuable features are the Advanced File Transfer and the managed file transfer. They make transferring files securely seamless. It's very easy to set up, get deployed, and have it transferred to and from vendors. As long as we can get our firewall rules implemented at a decent time, it's very easy and seamless to get important files transferred in a secure manner.

Control-M has automated critical processes. We run a lot of our backups through Control-M, daily sales reporting, and warehouse initiatives with shipping and planning. There are a bunch of finance processes that go through here that are time-critical. It's made everything more streamlined and secure and it comes through much quicker than doing it manually.

What needs improvement?

We have had a few small bugs with the configuration of the different types of jobs where it is the order of operations if it's doing a statement, we've noticed that if you try and do a little bit of both, it may cause one of them not to work. 

We've also had a few database bugs within our organization. I think we are migrating to OpenJDK rather than just regular Java and that has since shown some issues with our Control-M instance, timing out and causing our jobs to stop running. We are still working with BMC to fine-tune that and get that resolved.

I believe the file transfer process does everything that it needs to do. I don't believe that there's anything that would need to be changed there with all the features that it has, it's pretty robust. But overall I don't really see many changes that we would need.

For how long have I used the solution?

I have been using Control-M for three to four years. 

What do I think about the stability of the solution?

Other than the database connections that we've had and as of, I believe when we upgraded or moved away from Java using OpenJDK, it's been hit or miss. I know that we've had a few instances where our jobs just stopped processing, but we're not sure if that's related to the application itself or if that's something in our environment, but overall I am personally okay with the way that it runs.

What do I think about the scalability of the solution?

We run it on windows as well as Linux, and we are still trying to work on getting it to our DR site. But, I believe we are able to process quite a bit through there.

We use it for our I series AS 400. We also use it for Google Cloud, Cognos, ADP, many custom applications that we run as well, but we do a lot of I series.

I do not plan to expand it to other applications in the future.

My department consists of eight people, and we are mainly data center analysts. I'm their manager. We also have developers with a select few developers that are able to get in and view it, but they cannot actually create anything. They can just view and see what is running.

Between five to 10 users are responsible for the day-to-day administration of Control-M.

How are customer service and technical support?

I've never used Control-M before, prior to being here and all I had to use were the help guides from the web, as well as the user interface that we have. The help administration guide has been the only way that we are able to get questions resolved and to go through support.

Their support is hit or miss. We have had successful sessions with them. And then we have other ones where there are fingers being pointed and it doesn't really solve anything. We have a rep that my manager goes through, but we seem to usually get issues resolved in a timely manner.

What was our ROI?

We have seen ROI. We were able to have fewer people manually running tasks. We're able to put them right into here and we're able to scale and move a lot of file transfers through here.

What's my experience with pricing, setup cost, and licensing?

It is a little bit expensive. I believe that however we are set up, it might be per job that we load or the highest number of jobs that are loaded monthly and I believe it is quite expensive.

What other advice do I have?

My advice would be to try and utilize as many features as you can. Don't get overly creative with things because that can just confuse other people. If there are other users getting in there, you want to definitely have a standard workflow on how jobs should be created, organized, and make sure that you keep track of what's being changed so that if something were to fail it's easily trackable.

It's a very robust application and there is a lot that can be sent to it and sent out of it and you do not want it to get into the wrong hands because you can do quite a bit with it.

I would rate Control-M an eight out of ten. 

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.
PeerSpot user
Systems Engineer at Shiftmovers
Real User
Top 5
Enables us to manage and orchestrate workflows across the enterprise
Pros and Cons
  • "Switching to Control-M has helped reduce the total cost of ownership by 60%."
  • "The licensing could be less expensive for small-scale businesses."

What is our primary use case?

I have the new Control-M. I use it for one-time workflows, across the enterprise, and one-time application performance of the deployment.

How has it helped my organization?

It allowed the organization to meet operational standards. It ensures we implement the set project and have it aligned with our daily programs. It provides insights into changes for better performance. 

What is most valuable?

The user interface has been excellent. It gives the full overview of the tender performance of data across the workflow. It gives insights on the performance and the degree to which the application has been performing for the given period of time

The reporting, the dashboards, and the support are all helpful.

There's robust support for compliance and governance and ensures we meet the set company policies and our security. It ensures we're following international guidelines on privacy.

The solution helps us better our performance. There aren't issues when we need to plug new solutions and out of our DevOps toolchain. 

It's helped us reduce our CPU  consumption. The price has come down and the workflow nature has significantly changed. It's excellent. We've been able to save a lot of money after switching from Broadcom. 

The solution has helped modernize our business. Our workflow capabilities have changed and the monitoring process has been simplified. Data can be monitored efficiently from the set of a project to the end, across the data system. 

The system has really simplified the workflows, and we can easily deliver the data outcomes, enhance efficient data workflows, and offer the full performance report based on the load of the workloads that run across the entire flow system.

There's proven stability in monitoring.

We've used Control-M to manage and orchestrate workflows across the enterprise, including Microsoft Azure.

Control-M helped make it simpler to create, integrate, and automate data pipelines across the infrastructure. It's not complex.

We can schedule several events and get the best outcome based on the targeted performance.

The solution helped consolidate job scheduler tools in our organization. Each department target has a unique report based on the set workflows that is multifactor for various outcomes. It's also helped consolidate job schedulers.

Switching to Control-M has helped reduce the total cost of ownership by 60%.

What needs improvement?

The licensing could be less expensive for small-scale businesses. They need to work on a model that's fair to companies of all sizes. They could charge, for example, based on performance. 

For how long have I used the solution?

I've been using the solution for the past six months.

What do I think about the stability of the solution?

This is the most stable solution I've come across. I'd rate the solution's stability eight out of ten.

What do I think about the scalability of the solution?

The scalability is excellent. I'd rate scalability nine out of ten.

We have eight users on the product currently. 

How are customer service and support?

Technical support responds quickly.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

We migrated from Broadcom CA. It took around four days. 

How was the initial setup?

The initial setup is not complex. The customer support team can assist to help set the system efficiently and integrate it with other working systems in the organization. The deployment itself took three days. We had four people involved in the process. 

I haven't experienced any maintenance tasks, however, the solution can require some occasional maintenance. It does update from time to time to ensure the platform continues to run efficiently.

What about the implementation team?

We had a consultant help with the implementation. We worked with the vendor. They ensured the deployment process was smooth. They ensured the integrations worked efficiently.

What was our ROI?

We've seen a 30% ROI so far.

What's my experience with pricing, setup cost, and licensing?

The pricing and licensing are cost-efficient. 

What other advice do I have?

I'm a customer.

I'd recommend this solution to others based on its performance and operational capacity. It can improve data management and workflow configuration. 

I'd rate the solution nine out of ten.

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.
Flag as inappropriate
PeerSpot user
Richard Meyer - PeerSpot reviewer
System Engineer at a healthcare company with 10,001+ employees
Real User
Gives business users visibility into and control over their jobs, freeing up IT personnel
Pros and Cons
  • "It gives us the ability to have end-to-end workflows, no matter where they're running."
  • "The stability of Control-M has Not been great. A big thing we've been trying to work on with BMC is observability. Modern applications should be observable and resilient, but we're finding that sometimes Control-M is not very resilient and many times Control-M is not very observable."

What is our primary use case?

The major use cases we have are batch processing and MFT. We are heavy users of the MFT plugin.

How has it helped my organization?

One of the benefits of Control-M is that it's helping to give business users visibility into and control over their jobs, and freeing up IT personnel to focus on other operations. Here, I'm mainly thinking of MFT. Our MFT end-users did not have access to our prior MFT tools at all, so they couldn't see the jobs. They would just request a job be built and then we would publish job reports so that they could see what was out there. Now, in Control-M, we're able to give them job-control access. We still lock down the building of file transfer jobs, but they now have the ability to see a job and see how it's built. They can run a job and hold a job if they need to.

But even for some of the batch jobs, we've written some orderable services that are allowing them to run jobs on-demand, jobs that they used to have to log in to a server and go through a menu to do. Our business users definitely have much higher capabilities in our product now.

And while we are primarily on virtual servers, we are in the process of standing up some agents in the cloud. We have our first agent in AWS up and we're getting ready to do some testing on it. That's pretty critical. There's a really big push within our organization to move into cloud. A lot of our next-gen apps that are going to be replacing the current ones are being built in the cloud. We have that first agent out there, but I assume there are going to be many more to follow as these new applications are stood up in the public cloud. Today we're on-prem, but I definitely envision us moving the entire Control-M stack to the cloud. Eventually, it will be in the cloud and we'll just have a couple of agents on-prem, versus being on-prem and having just a couple of agents in the cloud.

Control-M has also helped to make it easier to create, integrate, and automate data pipelines across on-premises and cloud technologies. It's due to the ability to orchestrate between workflows that are running in the cloud and workflows that are running on-prem. It gives us the ability to have end-to-end workflows, no matter where they're running.

What is most valuable?

The automation is one of the most valuable features.

What needs improvement?

New plugins could be tested better. We've had a lot of problems with the MFT plugin. We've been working through a lot of issues with BMC on it.

The functionality that has existed for long periods is very stable. But the problems with the MFT plugin specifically, and problems we've had with MFT in general, have unfortunately caused the entire stack to be affected enough that our end-users couldn't even log in to the application. 

I wish we would have known better about how MFT impacts the application as a whole, and I wish they would have done more load testing around that. That seems to be where most of our issues have been. The issues have been so bad sometimes that the entire app goes down, not just MFT.

For how long have I used the solution?

I've been using Control-M for about two and a half years.

What do I think about the stability of the solution?

The stability of Control-M has Not been great. A big thing we've been trying to work on with BMC is observability. Modern applications should be observable and resilient, but we're finding that sometimes Control-M is not very resilient and many times Control-M is not very observable. We're working with BMC to try and figure out how we can externally monitor this application. 

We are using Dynatrace because of the problems we've had with Control-M. If we stood up Control-M and never had any problems, we probably wouldn't be too worried about being able to observe the processes and the queues and the communication between processes. But because we've had so many problems, it has forced us to dig in. We can't wait for a problem to happen and wait for a week for support to tell us how to fix it. We can't do that in a production environment. We have to know before a problem happens so that we can be proactive and not reactive. That's been a big struggle that we're continuing to work with BMC on.

What do I think about the scalability of the solution?

It's pretty scalable. You can stand up a ton of agents and you can stand up a ton of servers, if you need scheduling servers. Scheduling and agents are definitely very scalable.

There isn't the ability to really scale the EM (Enterprise Manager) a ton, although the GUI can be scaled somewhat. I don't know how much of a need there is to be able to scale the EM. We don't seem to have issues on the EM side, for the most part.

We're definitely having issues with the gateway between the EM and the scheduling server, but BMC is telling us that it's because we're running too many file transfers on the scheduling server. They say that if we stand up more scheduling servers, that should resolve that issue. We'll see if it does, if we still have any issues after we spread the load of MFT, not only over more agents, but also over more schedulers. If we still have issues after that, I think that would mean you're pretty limited in how you can scale your EM. That is the one thing about which I'm not sure how well it scales.

How are customer service and support?

Technical support is very back-and-forth. That's one of my gripes about the support. We open a case, they ask us for logs, we upload logs, and they come back and ask us for something else. 

At times, there isn't a lot of what I would call working together with them. We do now, but that's because we had a ton of support cases piling up and we started escalating with their internal leadership. Now, there are weekly meetings between our leadership and their leadership and our account managers, as well as weekly meetings with the support team and the dev team, to talk through our cases and any updates on them.

It took a lot of pushing from our end to get them to work with us. Otherwise, they just asked for logs and then we were waiting for a couple of days for them to look through all the logs and get back to us. We can't be doing that, especially if the issue is a production problem. We can't just upload logs every time we open a case and wait around for two weeks to get an answer.

Another gripe is that they're very siloed in what they know. Something that I've been asking for for a long time, from BMC, is somebody who can take a look at our environment as a whole, and not just in pieces. Every time we open a case with support, they want to assign it to a specific area. If it's a problem with the agent, then an agent person will look at it. If it's a problem with the EM, then an EM person will look at it. But nobody is looking at the environment as a whole. That's an issue because a lot of our problems, as I've mentioned, with MFT, are impacting the entire environment. It's not just one component. It's the entire environment and how those components relate and how they communicate that have been impacted. Nobody has really looked at the environment as a whole, in support. I think it would benefit BMC to have more experts on the entire application and not have everybody so siloed.

How would you rate customer service and support?

Neutral

How was the initial setup?

The initial setup was a little complex, due to some of the requirements. It requires that you have C shell as it doesn't work with the regular BASH shell. There are some old mainframe requirements that have carried through the product, even though we don't run it on mainframes. For example, the user that you use to run it has to be under seven characters long. We had to modify the account we use because the name was too long.

We're still really trying to get our environment squared away. We started two and a half years ago, but we've got a laundry list of applications that we're migrating out of and we've only completed one of those migrations. We're having to modify our architecture now because of the load that we are running. I'm working with professional services at BMC to review our existing architecture so that they can give us a BMC-supported design recommendation.

One of the competitors we are migrating from is Broadcom/CA. Broadcom bought a couple of products. They own both AutoSys and Automic, and we are migrating out of both of those solutions. AutoSys has been pretty straightforward to migrate into Control-M because the job configuration is pretty simple. However, the Automic workflows are very complex. They utilize certain features that only Automic offers, things that we can't replicate in Control-M. That is causing a lot of issues and has caused us to put that project on hold for the time being, until we can work through some of the problems that are being presented. We've been migrating Broadcom for at least a year now.

Some applications are pretty straightforward. MOVEit is an example of one that's a pretty straightforward conversion. However, another tool we have, Diplomat MFT, has a backup file structure that is not what the conversion tool was expecting. We ended up writing a custom Python script to do that conversion for us. The ease of migration really depends on what application you're migrating out of. It could be very complex or very easy.

The migration process is a very high concern. We selected Control-M due to the ability to migrate everything into it and have everything in one tool. If we can't get our migrations completed, then Control-M will just be another tool on top of all the other ones that we have to support.

What about the implementation team?

We used VPMA for the deployment. Our experience with them went pretty well. They're definitely very knowledgeable about the product

I don't know that they, or really, as I said earlier, even BMC had all the knowledge around how MFT could impact the application as a whole, back when we originally bought this. MFT was very new back then. VPMA did their best and guided us as much as they could, but I just don't think the plugin for MFT, specifically, was very mature yet. There were probably a lot of unknowns there.

We had a pre-sales team from BMC that helped us in the very beginning, before we worked with VPMA. They were nice, but I wouldn't say they were very knowledgeable. They had a very surface-level knowledge of the application. They didn't know anything that was deep. They would have to find out for us and get back to us.

What was our ROI?

It's not my realm, but I would assume Control-M has not helped us realize any savings on renewal costs after switching from Broadcom. The cost of an agent is significantly higher for Control-M than it is for Automic or AutoSys.

What's my experience with pricing, setup cost, and licensing?

We are paying way more for Control-M than we've paid for any of our other scheduling tools. We have an inside joke that Control-M is sold as the "Bentley" of schedulers, but we feel that we got a "Pontiac" because it's falling apart half of the time.

BMC has two licensing models. One is where you pay by job execution and the other is where you pay by endpoints. I'm sure the specifics vary depending on the customer, but we opted to go with endpoint licensing. I'm not sure if that was the best decision, knowing what we know now.

With endpoint licensing, we pay per server. That means it behooves us to run as many jobs as we can on each of those servers. But we're very much finding that even if we make those servers very large and give them a ton of resources, they're still not able to perform because Control-M doesn't scale very well vertically. If you make the agent bigger, if you double the CPU and RAM, that doesn't necessarily mean you can run twice as many jobs. It's going to choke in other areas. 

We will see if we end up switching our licensing model. I think the endpoint licensing model we chose is quite a bit more expensive than an equivalent model where we would pay per execution. We would definitely have to change a lot about our environment if we were to change our licensing model from endpoint to execution, because today we give all of our end-users the ability to run jobs on-demand. If we were to change our licensing model to be based on executions, we would probably want to restrict that a little. 

The way you license is a very large consideration when moving to Control-M.

What other advice do I have?

We really haven't taken advantage of some of the features that Control-M offers yet. The main thing I'm thinking of is SLA management. We haven't implemented that yet on a lot of our business-critical workflows because we just lifted and shifted everything into Control-M from the old app. As of today, things are pretty much equal until we are able to implement some of those additional features.

There are capabilities that Control-M offers that are good and I can see it being a very good product. BMC, as a company, has some maturing it needs to do in a lot of its processes. They have a very good sales team, but a lot of things after that can use some work.

We definitely haven't bailed on it, but I've heard a little bit, back and forth, from people at BMC that they might not be too upset if they lost us as a customer because we've been having so many problems. We've been on them about helping us get this environment corrected and functioning as we expect it to. But in a year from now, it's possible we could be in a really good place. I'm excited to see where it all goes.

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.
PeerSpot user
Ramesh Subudhi - PeerSpot reviewer
Analyst at a financial services firm with 10,001+ employees
Real User
Our batch jobs are automated, so we can check our dependencies with minimal manual intervention
Pros and Cons
  • "Our data transfers have improved using Control-M processes, e.g., our monthly batches. When we used to do things manually, like copying files and reports, we used to take three to four days to complete a batch. However, with the automated file transfers and report sharing, we have been able to complete a batch within two and a half days and our reports are on time to users. So, 30% to 40% of the execution time has been saved."
  • "After we complete FTP jobs, those FTP jobs will be cleared from the Control-M schedule after the noon refresh. So, I struggle to find out where those jobs are saved. Then, we need to request execution of the FTP jobs again. If there could be an option to show the logs, which have been previously completed, that would help us. I can find all other job logs from the server side, but FTP job logs. Maybe I am missing the feature, or if it is not there, it could be added."

What is our primary use case?

Most of my work goes through Control-M, e.g., all my development work. When it goes to production, it moves to batches. This will be either daily or monthly batches.

There are many applications running in Control-M, e.g., a quantitative risk management ALM application.

Most of our production jobs at the organization level are fixed through Control-M, running as either mainframe jobs, Informatica jobs, or QRM software-related jobs. Also, file sharing through FTP jobs and dependency setups between different software patches all run through Control-M.

How has it helped my organization?

We use file transfer jobs in our workflows. For example, if I want to share reports to end users in the production shared area, where specific users have access, Control-M makes this very easy as soon as a job is complete. The FTP job copies the report to a defined shared area, triggering an email to the user with a link. As soon as users are notified through email, they can open the email and click on the shared link to view the reports.

We have automated critical processes with Control-M. Our report deliveries are now automated. We automated our batch jobs and can check our dependencies through Control-M with minimal manual intervention. This has saved a lot of time and manual mistakes. For example, we used to copy old reports and send them via email, then users would come back to us, saying, "These are not this month's reports. These are old reports." After automating these reports with Control-M, there were no errors at all.

What is most valuable?

Multiple software can be collaborated through Control-M, then we can seamlessly monitor when it goes into production after a scheduled daily or monthly deployment. Even though we don't have any privileges to change these jobs, we can monitor them with read access and see how they are being executed. We can also verify their dependencies and see the logs. If there are any failures, we can get the logs from Control-M and fix them in the development environment, in the cases that are required to be done as soon as possible. It provides a complete picture about how the batches are running in production.

We have a lot of things that need to be considered. Everything needs to be done one after another in Control-M, where it provides us a pictorial representation of job dependencies, and even a person without technical knowledge can understand it by looking at the pictorial representation of jobs. So, we can provide the exact time when it can start. Then, we can update the users about the expected time for the job's completion. In case of any delays, we can understand them, then provide a new ETA to the users. Without Control-M, it would be difficult to provide these estimates.

We are using the web interface. We are not going through the mobile because we are a bank. Everything we do is through our laptops, not through a mobile. The web interface supports our business initiatives well. Whenever we want to see the updates, we need to connect to Control-M. We know what needs to be monitored and verify them depending on what their dependencies are. If the batch is still running, we can understand the historical information, then calculate and provide an ETA to users.

What needs improvement?

After we complete FTP jobs, those FTP jobs will be cleared from the Control-M schedule after the noon refresh. So, I struggle to find out where those jobs are saved. Then, we need to request execution of the FTP jobs again. If there could be an option to show the logs, which have been previously completed, that would help us. I can find all other job logs from the server side, but FTP job logs. Maybe I am missing the feature, or if it is not there, it could be added.

When integrating different projects through Control-M, sometimes dependencies cannot be identified. 

For how long have I used the solution?

I have been using Control-M for almost six years.

What do I think about the stability of the solution?

I have never faced any issues with stability. It is very good.

10 to 20 people are administering it.

What do I think about the scalability of the solution?

I have never faced any issues with its scalability.

500 to 600 people are actively using Control-M. These are business analysts, team leads, managers, developers, and senior developers. Anyone who is touching the development and production would have access. 

How are customer service and technical support?

Whenever we have issues, they are resolved through our organization's admin.

Which solution did I use previously and why did I switch?

With the integrated file transfer feature, most things are automated. Previously:

  • We used to copy the report, then send manual emails. However, with this feature, we are able to complete tasks with minimal monitoring because they are automated. Users are automatically notified as soon as the reports are complete. 
  • We used to work during the daytime and after business hours. We were forced to open and view that the reports were there. Or, we waited until the next day to copy the reports, sharing and sending them by email. With this feature, we are less bothered. We can wait until the morning of the next day. We just go into the office and see if the reports have been shared already, seeing that everything is okay. So, during the night, some reports are generated and emailed to the users. 

The integrated file transfer feature has saved us a lot of time and manual effort, approximately two to three hours a day. Also, users are notified as soon as the reports are complete, where they used to wait until the next morning. They can just verify their email using the office provider mobile. Then, they connect to their laptops and get the reports. So, if they need the reports and are waiting for them, then they are not required to wait until the next morning to receive them, saving about 10 hours of their time.

How was the initial setup?

I was not involved with the initial setup. That was before my time.

What was our ROI?

Our data transfers have improved using Control-M processes, e.g., our monthly batches. When we used to do things manually, like copying files and reports, we used to take three to four days to complete a batch. However, with the automated file transfers and report sharing, we have been able to complete a batch within two and a half days and our reports are on time to users. So, 30% to 40% of the execution time has been saved.

Control-M has helped us achieve faster issue resolution. Whenever we come across any data-related errors, instead of going into the process, we just get the Control-M log. Nearly 50% of our issues are resolved by looking at the Control-M logs. 

Control-M has helped us to improve Service Level Operations performance by 30%, because we no longer need to manually copy reports and receive email notifications. So, the process has improved a lot.

What other advice do I have?

Organizations looking for seamless integration with different applications can move forward with Control-M. In my experience, Control-M provides a good solution. It also integrates with different applications and software.

At this point, we are not using the solution's streamlining for data and analytics projects.

I would rate it as eight out of 10.

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.
PeerSpot user
Buyer's Guide
Download our free Control-M Report and get advice and tips from experienced pros sharing their opinions.
Updated: July 2024
Buyer's Guide
Download our free Control-M Report and get advice and tips from experienced pros sharing their opinions.