Try our new research platform with insights from 80,000+ expert users
Control-M Administrator at Cognizant
Real User
User-friendly GUI, responsive support, and the BIM feature helps us meet our SLAs
Pros and Cons
  • "BIM is helpful because we do not miss any SLAs, as we get to know the issue well in advance. It is the topmost service that has helped us provide better solutions for the business."
  • "The reporting functionality needs a lot of work. We have faced problems with different versions where we run the right report, but it gives us blank entries. Then, when we run the same report again, it gives the correct data."

What is our primary use case?

Our organization has multiple projects that use Control-M, and I support the banking domain. In the past, I have worked on projects for retail organizations and medical companies.

We have approximately 150 applications in our current project. These include Loanpower, erwin, and OpenLink.

How has it helped my organization?

With the use of Control-M, our SLAs are met more often. If there is an issue, we identify it in advance, before the problem occurs.

Control-M helps us in terms of automation because it has various scripts in different formats. We can run a Python program or a shell script, and these allow us to automate almost everything.

This product helps to secure our business because we can restrict users.

We have automated several critical processes with Control-M. One is used during patching, where we log in and type one command that will stop and start the services on all of the servers that we have. We have approximately 10 servers in production and five in non-production, so it's a lot of work to restart all of the servers. We also have automation that performs a health check. It runs every day at a scheduled time and will delete all jobs in production that are older than five days. Similarly, we have jobs that check to ensure certain conditions are being met and will check the various alerts that can occur.

Automating these processes has improved our business because every morning, we have to send a status update to show that the components are working. This is something that we used to do manually. We would log into CCM and check everything. Now, we have automated that using a script, wherein it sends the status email automatically to whichever business users request it. It has helped to reduce a lot of manual activity.

Control-M has definitely helped us to resolve issues faster. I estimate that the improvement is between 60% and 70%.

Our service-level operations performance has improved by 80% with the use of Control-M.

What is most valuable?

The GUI is very user-friendly. It provides us with a single view and we have everything in the same UI. This is very important because we don't spend a lot of time switching tabs or opening Control-M for different purposes. We have a single GUI open and it saves a lot of time.

Two really helpful features are Forecast and Business Impact Manager (BIM).

BIM is helpful because we do not miss any SLAs, as we get to know the issue well in advance. It is the topmost service that has helped us provide better solutions for the business.

Forecast is useful in terms of patching, etc, because whenever we are looking for downtime or any team is looking for downtime, it's easy for us to use Forecast to find it.

Self-service is helpful and our business users appreciate it because they don't have to have Control-M installed on their machine. They can log in using the web portal.

What needs improvement?

The reporting functionality needs a lot of work. We have faced problems with different versions where we run the right report, but it gives us blank entries. Then, when we run the same report again, it gives the correct data. We have spoken with Customer Care and some of the issues are fixed in the latest version, 9.20.

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

For how long have I used the solution?

I have been using Control-M for 11 years and my company has been using it for longer than that.

What do I think about the stability of the solution?

This is a pretty stable solution. We have not had any downtime.

A couple of times, the agent has gone down unexpectedly. However, in terms of the EM and server, it's pretty stable.

What do I think about the scalability of the solution?

Our organization is pretty big, with approximately 250,000 employees, and we have multiple projects that use Control-M. We have approximately 150 applications in our current project, and there are about 175 employees that are actively using Control-M. That is across three different countries.

It is easy to scale. It can handle a lot of job flows and it's easy to create multiple jobs to run at the same time. We are expanding in terms of jobs for the same application because they have a lot of upgrades going on at the application level. 

We are not planning to expand the number of applications in our project as of now. We do have requests, but it's a slow process. We can add perhaps five or six applications a year.

Overall, we have no problems in terms of scalability. 

How are customer service and support?

When we can't find a solution to an issue, we reach out to BMC customer support and they respond almost immediately. Overall, the technical support team is very good and I would rate them a nine or ten out of ten.

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

We did not migrate to Control-M from a competing solution. Some of our clients, although not my current project, migrated to Control-M from different products. The reasons for changing products are the additional features available in Control-M, as well as the ease of use. Also, some people are more confident in the security that Control-M provides, compared to other tools on the market.

Personally, I started my career with Control-M and have been using it ever since.

In the company, we have a couple of clients who use IBM Tivoli Workload Scheduler (TWS), AutoSys, and Stonebranch. However, the majority of our clients use Control-M. The choice of solution stems from requirements and input from the client.

One of the reasons that some clients are not using Control-M is because of the cost. For a client with 5,000 or more jobs, they definitely implement Control-M. However, if they are running only 200 or 300 jobs in a small environment, there are other native tools available.

How was the initial setup?

I was not part of the implementation at my company but I have implemented several Control-M projects. The initial setup is straightforward.

First, we download the files from the BMC site and then start the installation. This involves running the setup files and if there is any error, you have knowledge base articles and you also have AMIGO support if you enroll in it.

The deployment can be completed in a day or two, including the Enterprise Manager (EM), servers, and agents. There are also conversion tools that are available to assist with creating jobs.

Our implementation strategy began with installing the Enterprise Manager first, and then the server, and then the agents. We would raise a support ticket so that whenever we had any issues, we could reach out to them.

I did not look at the interactive guides or videos that Control-M provides for reducing time to full productivity. I had all of the documentation handy but I did not refer to any of the videos.

What about the implementation team?

Our in-house team is responsible for deployment.

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

Control-M is priced accordingly for larger environments. It is expensive for smaller environments with only a few hundred jobs running.

There are two different types of licenses available. The first is based on the number of jobs that we run per day, and the other is based on the number of agents that we install. My current project has a contract for five years. During the first two years, we are allowed to run any number of jobs using any number of agents. However, in the last three years, we have to stick to whatever is defined in the contract.

In past versions, BIM and Forecast were separate components that were available at an additional cost. Since version 9, however, everything is included and there are no costs in addition to the standard licensing fees.

Which other solutions did I evaluate?

For my current project, the client has always used Control-M.

What other advice do I have?

The latest version of Control-M is 9.20 but we are working with 9.18 because our client has certain servers where the OS is not compatible with 9.20. It is running on Linux machines and at this point, our client hasn't given us approval for the OS upgrade.

Our business users don't typically use Control-M. They have access to it but only use it when a critical chain is stuck and they want to check it themselves. They can use self-service for this, although most of the time, they don't.

An example of why they would use self-service is when a critical batch has failed and is stuck for a long time, and they want to see the approximate time that it will be completed. Also, during an audit, they can use self-service to see which users have certain access, such as production access or write permissions.

The Control-M users in our company have different roles. We have administrators, and we have people who specialize in migration. We also have people who look into scheduling and we have a team that just takes care of monitoring.

The number of people that we require for the day-to-day administration depends on the size of the project. In my current project, we have approximately 8,000 jobs actively running. We have approximately 17,000 configured. In our L1 team, we have eleven people, and we have eight members for each of our L2 and L3 teams.

We do not use the Control-M integrated file transfer capability in our workflows, although we do use the File Watcher feature. We have a tool from Axway called SecureTransport, where they handle the file transfer, but we can define this as part of a Control-M job.

The biggest lesson that I have learned from using Control-M is that anything can be automated. You can control various applications and it is simple to schedule jobs for products like SAP and databases.

My advice for anybody who is considering Control-M is that it has a wide variety of features compared to other tools. It is flexible, easy to use, and the web portal makes it simple for business users or application teams to access it without having to install it on a Windows server or a Citrix platform. 

I would rate this solution a 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. The reviewer's company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Subject Matter Expert at a consumer goods company with 10,001+ employees
Real User
Workflow dependencies work well, and automated audit reporting helps out sort out issues quickly
Pros and Cons
  • "Workload Archiving is a very good feature for us. It helps with our customer requirements in terms of reporting and auditing... Previously, when we didn't have any archive server, we managed the data in Control-M with man-made scripts, and we would pull the data for the last 365 days, or three or four months back. Since we installed the archiving, we have been able to pull the data, anytime and anywhere, with just one click."
  • "With the current version update, I'm not sure why we needed a separate database upgrade. Why not put it all in one package? Previously, you could do it either via a manual upgrade or an in-place upgrade but it wasn't separate."

What is our primary use case?

I am working with a beauty products company and we are dealing with supply chain issues. Most of the jobs in Control-M are through SAP.

Right now we have it deployed on-prem, but we are planning to move to the cloud very soon. We are using Control-M Workload Archiving, Control-M Enterprise Manager, Control-M servers, agents, APIs, REST APIs, and Control-M Forecast. We use all the services Control-M provides except Control-M Workload Change Manager.

How has it helped my organization?

Since moving to Control-M we have seen a lot of reductions in the manpower needed. For notification, ticketing, and integration, we have different teams. We have Azure teams and some Windows teams. Previously, they were using and managing their own scripts and manually running them. After the migration to Control-M, there were no limitations. Where there are different protocols we can use the APIs and integrate things with Control-M. There are no worries about integrations with Control-M. In UC4 there were lots of limitations because we needed the same protocols to integrate things. With Control-M, there are no such limitations.

In our current environment, there are three sets of applications. The first, an online application, is dependent on some 45 files that have to be generated on Saturday. Our middleware job is supposed to run once all the 45 files have been generated by SAP jobs. There are sequences running through Control-M: First are the SAP jobs that generate the files in a certain location. Once those files are there, the sequence initiates the middleware that moves the files to the proper IT server. All these process flow dependencies go through Control-M very easily.

We have also automated daily audit reports through the solution's reporting facility. Through scripting, we get an alert when anything happens in the Control-M environment. An issue might occur with the agent, the process, or the Control-M server. We have everything reported via email. We can easily see what happened on a given day and sort out any issues.

As a result of using Control-M we have also seen an improvement in Service Level Operations performance. We have some monitoring tools in Control-M and our service SLAs have definitely improved. We have a ticketing system integrated with it and we can easily monitor the SLAs for tickets generated through Control-M. If the person responsible for a ticket will not handle it in the right amount of time, the ticket will pop up with a message saying it's in danger of breaching the SLA. Our service levels are much higher with Control-M, when compared to other tools.

What is most valuable?

Control-M Workload Archiving is a very good feature for us. It helps with our customer requirements in terms of reporting and auditing. We have internal audits every quarter, and every six months we have external audits. During these audits, the auditors get historical data through Control-M. Previously, when we didn't have any archive server, we managed the data in Control-M with man-made scripts, and we would pull the data for the last 365 days, or three or four months back. Since we installed the archiving, we have been able to pull the data, anytime and anywhere, with just one click.

Control-M gives us a unified view where we can easily define, orchestrate, and monitor all our application workflows and data pipelines. We are mostly using SAP and other business warehouse jobs, and we can easily see the systems through Control-M. It gives us a very good view of geographical data. If I go through the Web Services to show things to my customers, they are very satisfied with the Control-M views. They can check historical data and they can see the current view. They can easily pull these up. We are satisfied with the fact that, with one click, we can see all the applications within one view.

Our line-of-business personnel use Control-M’s web interface to support their business initiatives. One of our big applications is our JG application, where a user needs a data pipeline and Power BI jobs with refreshed data. Instead of the user having to send a request to our Control-M team, they can use the Web Services directly to check their data. If they're using an iPad or a desktop, they can easily check on it themselves. They're not dependent on the Control-M team directly. We educate users on how to check things and how to pull the reports. It is very easy to use. Also, we don't have 24/7 support within our company. Suppose a user needs something at midnight. They don't have to wait for the Control-M admin team to give them the report. They can directly pull the details.

What needs improvement?

With the current version update, I'm not sure why we needed a separate database upgrade. Why not put it all in one package? Previously, you could do it either via a manual upgrade or an in-place upgrade but it wasn't separate. But for the current version, we needed to upgrade the database separately. It meant doubling our tasks to do the upgrade. That is something that needs to be improved.

For how long have I used the solution?

I've been using Control-M for the last 17 years. My specialization is in Control-M and I'm very happy and very comfortable with it.

What do I think about the stability of the solution?

I would rate its stability highly, compared to other tools in the market right now, such as UC4, and AutoSys. In the past, I have worked with many banks. All these financial companies are using Control-M, and there is a reason: It's due to the stability.

What do I think about the scalability of the solution?

I would give the scalability a nine out of 10.

In our environment right now, out of 20,000 jobs in Control-M, 15,000 are SAP. We are planning to expand our usage of Control-M to Power BI, Business Warehouse, PeopleSoft, and Azure. Those are in our pipeline right now.

We have about 25,000 users of Control-M on different projects, in the U.S., Japan, India, and Asia Pacific. Some are monitoring programs through Control-M, some are only doing scheduling. Some are responsible for designing, others for the implementation before the licensing. And once this transition team is done, the operations team comes into the picture for monitoring. We have a separate team for integration, as well.

The number of people we require for day-to-day administration of Control-M depends on the job size and the user requirements. We work in an offshore and onsite model. We have a key administrator over the 20,000 jobs, seven schedulers, and nine people on the monitoring team, and that work is done 24/7. The schedulers and admin work 24/5.

How are customer service and technical support?

In a case where we fail to understand an issue by collecting data on our own through our audit reports, we open a case with BMC. BMC always gives us a fast resolution. Their support is very good.

How was the initial setup?

The setup of the current version of Control-M, overall, is very easy. The upgrade is in-place. With one click the agent upgrades, the server upgrades. The only point, as I mentioned, with upgrading, is that we needed a separate database update. When we upgrade our Control-M server, the database server should be upgraded at the same time.

The initial implementation in my current environment was in 2006. When we took over we just upgraded it. After that, we implemented two more Control-M Servers in this environment, as a PoC.

The amount of time required to implement it depends on the environment we are working with. In this environment, we have two production servers, four QA servers, and two testing servers. We have eight Control-M servers, three Control-M Enterprise Manager servers, and more than 400 agents. It depends on the change process. In our change process, we first need to upgrade our QA and test environments. Once that is done, we can go for the production environment the next day. After that, over the next seven days, we update our Control-M agents. Some of the upgrades require downtime. In four to five hours, we could easily update everything, but it's dependent on the downtime and the customer requirements.

When we upgraded to version 20, first we implemented it in our QA environment and we tested the new version in our test environment for three to four months. Once we see there are no bugs, we implement it in our production environment. We've seen a lot of bugs and BMC has had to produce some patches that we have had to apply in our environment. That is why we approach it the way we do in a QA environment, and wait for three months, and then go to production.

When we moved to Control-M, we used the Control-M Conversion Tool. It's a very important tool. It gives us an idea of where we stand. If I'm going to move an old environment to a new environment, it helps us with any errors so that we can rectify them.

What about the implementation team?

Back in 2016, when I was working with version 7, I opened a case with BMC and they helped me to upgrade everything. It was a very good experience. They dedicated a resource to us. We gave them our implementation plan, they reviewed it, and they suggested how to remediate some missing steps. We followed their approach and, at the time of cut-over, they assigned a dedicated resource. If there was an issue, we could open a ticket and they would come online and sort it out. The BMC Assisted MIGration Offering (AMIGO) is a very good program.

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

You must accept that BMC licensing can be very confusing. No one can easily understand how they calculate things, whether it is user-based, job-based, or server-based. The calculation is quite tough. How BMC calculates licensing is not easily available anywhere. It's a very tough part for the client at times.

But BMC is a market leader, so users don't easily go for different vendors. If there's an option to go with Control-M, they will always choose BMC. But for people who find the licensing challenging, they will go with a different vendor.

For us, the licensing part is managed by a team in the U.S. But what I deal with is that we have to manage our Control-M jobs to a maximum of 30,000, because we have 30,000 licenses. We have 20,000 with fraud detection and 10,000 in non-fraud. There is a BMC utility that can guide you and alert you if the forecast is for an increase beyond the licensing. It will notify us: "Hey, you have a license for 20,000 and the Control-M forecast shows you might need to increase that number in the coming days." So we do some cleanup, some internal housekeeping to remove things and remain under the threshold. Those are some of the things we do as administrators. We try to manage under whatever licensing we have. Through the BMC reporting tool, we can see our peak number of users in a month. BMC charges if you go over a certain peak.

Control-M is very robust. There is no harm to the customer if you choose Control-M every time. But when it comes to licensing, it's very expensive, and sometimes users think twice.

Which other solutions did I evaluate?

Previously we were using UC4 for more than 20,000 jobs. But our customers were not very comfortable with the user interface in UC4. Certain things were not appropriate in that tool. Since our decision to migrate to Control-M, our customers have been very satisfied.

Integration is very easy. When I'm thinking about integrating Control-M with anything I'm not worried about it. I know Control-M will definitely have a way to integrate easily. I have used UC4, AutoSys, and Dollar Universe. But when the requirements include integration, I always think of Control-M, because I know the integration will be very easy. I will never go for any of those other tools.

What other advice do I have?

Control-M is very critical for anyone who is using 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. 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 2025
Learn what your peers think about Control-M. Get advice and tips from experienced pros sharing their opinions. Updated: July 2025.
861,524 professionals have used our research since 2012.
reviewer1899735 - PeerSpot reviewer
IT - VP at a financial services firm with 10,001+ employees
Real User
We have a better picture of our auditability
Pros and Cons
  • "We have a better picture of our auditability. When someone comes to us, and asks for sources, "How did the deltas occur?" We can provide answers quickly, or at least quicker than what we used to. We are actually sure of the information that we provide, where before it was like, "Hmm, I think it comes from over there. Let me double check, but it gets really convoluted over here and I think that is where it comes from." Now, if it is within the Control-M environment, it has a straightforward answer that we can provide with confidence."
  • "The community and the networking that goes on within that community need improvement. We want to be able to reach out to an SME, and say, "Hey, we are doing it this way. Does that make sense?" Ideally, they come back. and say, "Yes, it does make sense to do it that way. However, if you want to do it this way, then it is a little more efficient." We understand that one solution framework doesn't fit everybody. Depending on the breadth of the data and how broad it is, you may have different models for one over the other."

What is our primary use case?

It is controlling our workflows, ingesting data, and then putting it up into our database platforms. In turn, those are consumed by our internal clients.

We do integrate Control-M Python Client and cloud data service integrations with some of our cloud providers. We have pipelines going out to the public cloud and some pipelines that are internal.

We have public and private cloud channels as well as on-prem. The expectation for most large financial institutions is that we will get 99.9% to the public cloud eventually. We want everything to be in OpEx as opposed to CapEx. We don't want data centers. We just want access to our data and to be able to turn it into information, which in turn, turns it into actionable items. Ideally, we would love to not support any on-prem or hybrid solutions, having everything be public.

How has it helped my organization?

Control-M has improved our visibility and streamlining. We have better clarity into data flows. We can resolve issues faster by not trying to reverse engineer what pipeline the infraction may have come through. We are not completely there yet, but we have better clarity and visibility. 

We have a better picture of our auditability. When someone comes to us, and asks for sources, "How did the deltas occur?" We can provide answers quickly, or at least quicker than what we used to. We are actually sure of the information that we provide, where before it was like, "Hmm, I think it comes from over there. Let me double check, but it gets really convoluted over here and I think that is where it comes from." Now, if it is within the Control-M environment, it has a straightforward answer that we can provide with confidence.

The speed of our audit preparation process is faster. When questions come in about flow, data, or sources, we don't have to try to reverse engineer anything anymore. We are able to go straight to Control-M and find out what the flow is or what happened. The visibility is there. We see the endpoint on this, such as, "What is the reverse flow on it? Where did it come in? Where did that data flow come from?" So, it is not a spaghetti mess anymore. This makes auditability easier. We are able to provide answers more quickly, which in turn, makes the audit process quicker.

Control-M has improved our business service delivery speed. It is more reliable and has increased the release schedules. We are also working on testing standards, and it has shortened the window of getting things to us. It has shortened the window, not to market, but basically getting them live. 

Control-M is critical to our business. If the support ends, we are at risk in some of our critical flows. We have redundancy around it that has been purposely built. We do that with all of our solutions. That way, we are not tied into one specific vendor, then if something happens tomorrow, we don't have a fire drill. We have things in place, but to a certain extent, there is heavy reliance on this solution.

What is most valuable?

The most valuable feature is the Self Service tool. They have metrics in place almost all across the pipeline, which is really nice. 

What needs improvement?

We are not yet really a power user of it. You can take as many training classes as you need, but it is not until you are working with a subject-matter expert (SME) on it that you can find out how you can really make this tool sing. My engineers know how to work Control-M. However, if I ask them, "Oh, is this the most efficient way of doing it?" They may not be able to say, "Yes." It is doing what we want it to do. That is nice and okay, but is it the most efficient, effective way? So, we are not there yet.

For how long have I used the solution?

I have been using it for about four years.

What do I think about the stability of the solution?

The platform is good. We haven't had any major outages. The stability is there.

What do I think about the scalability of the solution?

We really haven't pushed it to any of its limits. No scalability concerns have come up for what we are doing.

If you came to me, saying, "Hey, I was looking at Control-M, but it has some issues." I am going to sit there, and go, "Tell me what the issue is." Right now, we are not using the far reaches of whatever cloud providers are out there. Control-M does well with the major providers.

How are customer service and support?

The community is not as robust as some of our other tools that were replaced. The problem was the other tools that we were using didn't do everything that Control-M is now able to do, like monitoring and the entire pipeline flow.

The community and the networking that goes on within that community need improvement. We want to be able to reach out to an SME, and say, "Hey, we are doing it this way. Does that make sense?" Ideally, they come back. and say, "Yes, it does make sense to do it that way. However, if you want to do it this way, then it is a little more efficient." We understand that one solution framework doesn't fit everybody. Depending on the breadth of the data and how broad it is, you may have different models for one over the other.

I would rate the technical support as seven or eight out of 10.

How would you rate customer service and support?

Positive

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

We had a patchwork set of solutions in place that were getting the job done. The problem with that was we had a lot of SMEs within certain verticals. Therefore, there wasn't one overall picture. Every time we went from one step to another step, we had to start talking to another person to figure out what was going on. So, we were trying to bring everything together under one solution with Control-M.

We are able to have a better picture of our data consumption, e.g., what files or data is brought in. Previously, we would ingest data at different points. The question that would always come back to us would be, "Where did this data come from?" Then, we would always have to reverse engineer and have some documentation on it, but the documentation would be outdated. Someone would change the pipeline and forget to change the documentation. With Control-M, we can see everything in one location. To a certain extent, it is not documentation.

I am an engineer by trade. I have been doing this for over 30 years. I know that it is nice that someone puts together a document describing the environment, but as soon as that document is saved that document is outdated.

We don't throw another tool into the toolbox just because it is a nice pretty tool. We try to figure out what the benefits are. Ideally, in our world, we try to reduce the number of tools because I don't need 50 different screwdrivers in my tool kit. I make sure that I have a flathead and a Phillips, but I don't need 50 screwdrivers. Here, we brought in this solution and it replaced some existing solutions. Now, my engineers don't need to know X number of products. They only need to know half of X number of products.

What about the implementation team?

The tool was vetted by another group before making it available to the organization and putting it into our toolbox. Then, when it was available, we looked to leverage it.

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

One of the restrictions that we had was with some of the licensing, and not having any insight on the financials part of the product. I don't know what the licensing on the product is, but we don't have an unlimited enterprise license. So, there might be a limitation on either the cost of the licensing or the number of seats.

What other advice do I have?

There is always a learning curve any time you are using a new product. Our engineers who are using Control-M are kind of happy with it. There really are no negatives on its learning curve. I am always weary with new products since it is another thing that someone needs to learn, but now there are other products that we don't use because of Control-M. What I would not be open to is bringing in another product, where we need our engineers to know how to work it and make it efficient as well as support other products already in our environment. So, I like that we can get rid of three or four products and replace them with a single product. As long as the learning curve is not too steep, that is an advantage to me.

We are looking into using Control-M to deliver analytics for complex data. So, the solution is doing either machine learning or complex analytics on top of the data flow. While we do some analytics, it is not to the extent that we really want to.

I would rate this solution as a high seven or low eight (out of 10).

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
Sr. Automation Engineer at a computer software company with 1,001-5,000 employees
Real User
Saves time, offers great auditing capabilities, and has good automation
Pros and Cons
  • "It has certainly helped speed things up."
  • "They can improve their interface."

What is our primary use case?

I've been with the same company for 22 years. The use case started out truly as a batch processing solution. That was what we originally got it for back in the day to help us automate what was being done manually or being done through homegrown tools or scripts, et cetera. The use cases evolved through the years. Now, we use it to orchestrate workflows that are touching traditional data centers and that are going out to the cloud and bringing it back.

From one spot, we have a single pane of glass. Like many companies, our systems are getting more complex and more diverse, with cloud and edge computing, containerization, et cetera. However, we have one place where we can go and look and see what's going on. If something happens, we can check what happened and where it happened. Today, we're dependent upon a lot of services and cloud technology that sometimes we don't know the ins and outs of.

A big challenge is to make sure that we have certain things run daily or on a periodic basis. That really was the driving use case. We had a lot of manual tasks going on and if someone, for example, left on vacation, something may not get done for two or three days, a week or two weeks. This solution takes all that away.

The main use case was to get away from having to stare at a system or a screen, and just let things run, let the workflows flow, and only be notified if there's something wrong. That was really a big driving use case.

How has it helped my organization?

It freed up people to work on exciting work instead of mundane work. No one has to sit around and stare at that screen all day long. No one has to reinvent the wheel for the 50th or 500th time to do tasks like maybe put a file out into an S3 bucket or out into an HDFS Hadoop file store since it's already there. It's already done for them. They just drag, drop, click and they're done. It's freed people up and they can do the exciting work that is really what we should be doing anyway. No one wants to be doing boring work.

What is most valuable?

I am a big proponent of an automation API and Jobs-as-Code. That is Control-M in the DevOps world. It opens up the tool to a traditional operations tool. Developers can jump right in there now, giving them that ownership, and integrating the existing DevOps tools that they have. That is a huge feature that I just love. 

There's an application integrator. It doesn't matter if you're trying to integrate with on-premises, off-premises, API, container, or serverless functions, it's easy for you to design. You just design that integration and then it's available instantly, and that's a huge time saver. 

It's rather easy to create, integrate and automate data pipelines with Control-M. I can give a broad answer. It can be as easy as drag and drop, or it can be as complex as designing the integrations. If you use customization, you can access a data lake that your organization developed. For the typical user out there, the difference is on a scale of one to five, with one being easy and five being hard, you're probably looking at a two and a half. For most people, it's very easy. It's getting easier as it's all web-based nowadays. Alternatively, it can be all code-based.

I have not explored Python Client too much. I've tinkered with it and that's been the limit of my exploration. Now, with the integrations like AWS, we've made extensive use of it, and it is very easy for anybody to do. Python Client has a lot of great possibilities, especially in the data science arena, however, sadly we have not had an opportunity as of yet to play with it.

The Control-M interface for creating, monitoring, and ensuring delivery of files as parts of your data pipeline has gotten better. It is not perfect. That said, it’s come a long way over the years. Nowadays, most of it is web-driven. A lot of it can be API driven if you so wish. There's still probably some future work to be done there, however, for the average user that's coming in, starting to use it for the first time, they're going to need a little training and handholding at the beginning for maybe the first week or so. Then you can start setting them free to go out and use it on their own.

The orchestration of our data pipelines and workflows has been able to give a single point of view too. Management doesn’t care about the bits and pieces. A workflow or a data pipeline could have 100 or 1,000 components behind it, and management does not care about that. Management cares whether the SLA has been met or not. They want that easy-to-see red light or green light. We can provide them with that. The solution drives self-service and it helps. A manager doesn't have to call somebody in IT and wait around for an answer.

They can immediately get that information for themselves, consume it and be able to understand that, "Hey, you know what, this data pipeline over here, we're going to be 15 minutes off our SLA for today." Then, they can start asking why. I like parts of Control-M like Batch SLA Impact, is they can start doing some of that analysis themselves, for example, “this late due to the fact that maybe the system was down for maintenance for two hours last night." That's really beneficial in today's business world.

The automation of Control-M has sped up everything. We can integrate directly into existing pipelines and the DevOps teams can get anything integrated with their Jenkins deployments. They don't have to wait for traditional operation functions. This is all built-in. It validates and checks. In some cases, it automatically deploys the agents and deploys the configurations. That's something that years ago you'd have to wait for. The speed of delivery has vastly improved.

Nowadays, auditing is as simple as running a report. If this falls under an auditable category, we can just hit a button and the report is done. Control-M audits everything, even if it is not under the regulatory or audit spotlight. Every process, every movement, and every change is logged by the system. If there's ever a question, you’ll be able to find a why and a when. There’s an audit trail.

It certainly helped speed processes up. I can eliminate what I call the manual gaps between certain features. I don't have to send an email to somebody to say, "Hey, guess what? That file's ready. Now you can run process X, Y, Z." The system just says "Hey, the file is there, let's go." It's eliminated those gaps between parts of the workflow. It also helped optimize the infrastructure needed as it's like a Tetris Puzzle. I have these ten different workflows that I'm trying to run and before I may have had ten dedicated systems for them. Now I know that I don't need that.

We use this model all the time. We can run those ten processes on three systems and be just fine. That saves money. The solution is not only speedy, but it also saves money.

They are doing a great job with continuing to drive the open-source model of it. Five years ago, if you looked for Control-M anywhere, you would not have found it. Today, that model has changed. They're actively publishing on GitHub.

You can download for free an entire container and run Control-M at home if you want to tinker with it. That was unheard of a few years ago. You can type a query in Google and start to see all sorts of documentation that is now available to the public. The major strides that they have made there are pretty darn good.

What needs improvement?

If you want to take it and ramp it up to doing some very heavy-duty integrations, you can find yourself at first dealing with a difficult integration. However, once you get that integration going for maybe a month or so, the next person after you will have less difficulty. That's the power. 

They can improve their interface. They're going through huge modernization efforts and they're getting there. They're probably 75% there, however, there's still another 25% to go.

For how long have I used the solution?

I've been using the solution for 22 years.

What do I think about the stability of the solution?

Since it supports business, it has to be stable. It's very stable. We have not had major outages or anything. That's always a good thing, however, like with any solution, its stability is going to depend on how you deploy it and what safeguards you put in place, including high availability and disaster recovery, et cetera. All the hooks for that are in the product, however, it's up to you to decide how you're going to use those hooks.

What do I think about the scalability of the solution?

It's highly scalable. You can run five things in it today and easily scale up to run 1,005 things tomorrow. In terms of scalability, there are no issues there.

How are customer service and support?

Technical support tends to be very helpful.

How would you rate customer service and support?

Positive

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

I used to work for an insurance company and I used Computer Associates. It was called CA-7 and CA-11, which are similar tools.

We tried to use Computer Associates before this, but it didn't support the systems we needed and the integration was next to impossible.

How was the initial setup?

I was involved in the deployment and initial setup of the solution right from the beginning.

We had jobs and workflows running within the first day. That was pretty good. We don't use the Helix model, however, there is a Helix model you can purchase, in which everything's hosted by BMC. You can be up and running literally in hours which is reasonable. There's a learning curve, however, if you do not get some value out of it within two days, you're probably doing something wrong.

At the time, there were only two of us deploying the solution. Today there are only three of us.

It's business-wide. Everything from data to marketing, to finance, even though it probably wouldn't make sense to anybody else, it touches everything. It's deployed across Windows, Linux, containers, VM, cloud, et cetera.

If anybody has a use case or wants to learn more about it, we'll show them. Anybody in our organization can get basic access and can tinker around in an alpha test environment. This includes non-technical people. We have non-IT people that use it.

If they can self-service and maybe design some parts themselves, that's a huge win right there. We have a very open model of deployment.

There are occasional patching and vulnerabilities that come out. Most of the patching nowadays can be automated if you're using the Helix-based solution. A lot of that is handled by BMC.

What about the implementation team?

We did not use an integrator, reseller, or consultant for the deployment.

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

I can't speak to the exact licensing costs. 

Which other solutions did I evaluate?

Every few years we go through a reevaluation. We'll go through and look at what's on the market and what companies have come up with or released new versions. We'll go through and we'll say, "Okay, let's compare these, what do we need and what are all the tools offered out there?" We do that roughly every five years and it keeps us on our toes.

The biggest difference as of late is the API and Jobs-as-code. Control-M is light years ahead of others. It is light years ahead of the competitors and what they're offering. Other competitors are starting to get APIs, however, only BMC is working with Job-as-code and is in the lead. To my knowledge, they're really one of the only ones who can define your entire workflow as code.

What other advice do I have?

Control-M is pretty critical to our business as it runs many different business processes every day, and if it wasn't there, we would probably hire many more people, be a lot slower, and be more prone to error.

We use a hybrid deployment. We have parts in the traditional data center. We have parts in the cloud. We sometimes have parts that live on containers. They only exist for two minutes. It is very much a hybrid mix of goodies with our deployment.

I'd advise potential new users to examine it today and not think about what it did ten years ago. Control-M is an old product. It has been around since we all used mainframes, however, just because something's been around for a long time, doesn't mean it's a piece of junk or doesn't work with modern technologies. It has adapted and grown with the times. Control-M did cloud-based work before many of us were even talking about the cloud. It's hard to get rid of negative perceptions sometimes, however, the best thing for people to do is to head out to the internet, look it up, and go out to GitHub.

If you have a technical team, send them out to GitHub. You can download everything in an image or in a container and try it yourself. It doesn't cost you a nickel. 

I'd rate the solution nine out of ten.

The biggest advice I can give is to try it out. Don't only believe what the PowerPoints tell you. There's no excuse that you can't have a deployment running clearly within hours. Be willing to think about how it can solve problems in new ways. Sometimes we try to find a new tool as we have a square problem and we get upset as all the tools we're looking at only have round solutions. Sometimes the reason that it only has round solutions is due to the fact that that's the proper way to solve the problem. You have got to be willing to break down whatever you're trying to do, whatever workflow you're trying to automate or integrate, and take it in pieces.

If all you want to do is save yourself a lot of money, use Cron, and use Windows Task Scheduler. However, if you want to take your business to the next level and start to get to the point where you can automate to remediate and audit, that's where tools like Control-M come into play.

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
Chris Wahl - PeerSpot reviewer
Operations Engineer at West Bend Mutual Insurance Company
Real User
Saves us thousands of hours, is widely applicable, user-friendly, and features top-notch reporting
Pros and Cons
  • "The reporting is top-notch. I haven't found any other applications on the market that can replicate what Control-M offers. The alerting is very good, and I think their service monitoring is the best in the industry."
  • "The stability could be improved. I ran into an issue with a recent Control-M patch. The environment would become unstable if security ports were scanned. This is an area they need to improve on, but ultimately it's a relatively small improvement."

What is our primary use case?

We use the solution in Western Mutual Insurance Group's environment for the daily scheduling of around 11,000 jobs. Our number of end-users is in the hundreds, across 18 to 20 teams. We have three different physical locations as a company. Since COVID, we are a partially remote workforce as well, so we have multiple locations.

It's essential that the solution orchestrates our workflows. Regarding processes like file transfers and data workflows, we want one source for that. We want one area where we can check and see how things are progressing, and Control-M is invaluable. Everyone has access in our environment to Control-M, and we all use it heavily. We utilize a ton of plugins in our environment. We started the transition into servers and are seeing what our license allows in that area. We try to take advantage of everything we can.

We use Control-M to replace a lot of our manual logging of job data. It's been very valuable in terms of logs that can output alerts.

I just did an audit earlier this year, and it was a swift process using the product. It took me less than a few hours, and without the solution, it would potentially take a couple of days to a week.

We essentially have a nightly batch cycle. We process data overnight, so it's available for end-users during the day. Using manual execution, instead of Control-M, this nightly batch cycle would transition into a weekly or monthly batch cycle instead.

How has it helped my organization?

I recently took over as admin of Control-M about a year ago. Since then, the question has been how we can further utilize Control-M in our environment. We haven't yet found the limits of what Control-M can do. We're finding better ways to apply it every day. From the old days when we manually scheduled jobs to the current paradigm of using an automation tool. This made the process much more manageable.

We define Control-M internally as a "critical business application." I would say that if Control-M were not available, the impact would be catastrophic to our business.

What is most valuable?

The reporting is top-notch. I haven't found any other applications on the market that can replicate what Control-M offers. The alerting is very good, and I think their service monitoring is the best in the industry. 

The solution is a key part of our system and I have not seen any significant limitations with it. It's very reliable and performs as advertised.

We're just starting our data pipeline journey. Compared to other products in the market, I believe Control-M's is the easiest to use. Theirs came out ahead in terms of ease of use every time. I rate them very highly in that area. We're primarily an Azure corporation. We found that the solution's built-in integrations with Azure are straightforward to use.

We actively build out methods of alerting, for instance, when workflows in Control-M don't complete, as this impacts our end-users and our managers that support the teams attempting to provide data for the end-users. I think Control-M has a ton of built-in integrations that make alerting when that data is unavailable more visible to end-users. I think that's been very useful in our environment.

What needs improvement?

The stability could be improved. I ran into an issue with a recent Control-M patch. The environment would become unstable if security ports were scanned. This is an area they need to improve on, but ultimately it's a relatively small improvement.

For how long have I used the solution?

We have been using the solution for around seven years. 

What do I think about the stability of the solution?

One patch had some issues, but the fix pack was very helpful. Other than that, we haven't had any stability issues with this product. So I'd rate it very highly.

What do I think about the scalability of the solution?

The scalability is excellent, we're looking into options in Azure for scaling up and down in our environment, and Control-M has been essential in accommodating that.

How are customer service and support?

Technical support would be a 10. They're always available. They've been very helpful with any questions I have. There are multiple means of contacting them, and they've always been responsive. The technical account partner, Jake, has been very helpful. The account rep, Chris, has also been very responsive.

How would you rate customer service and support?

Positive

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

Control-M in our environment predates my time. I believe the company first implemented the solution around 15 years ago.

How was the initial setup?

The initial setup was before my time. We started off as a mainframe exclusive influence of Control-M, and then we transitioned to distributed servers from there. I am a team of one.

What was our ROI?

The solution's automation has improved our business service delivery speed. Our big push this year has been toil reduction and automation of manual tasks that ultimately take time away from our engineers. Control-M is factored into probably north of 80% of those reductions with its ability to automate tasks. So far this year, we're at about 4,000 hours of toil reduced. I would say Control-M has played a factor in 3000 of those hours.

What other advice do I have?

I would rate this solution a ten out of ten. Control-M is critical to our business.

There are other solutions like Control-M out on the market, but in every recent market evaluation, Control-M has always come out on top. I think they are becoming more cloud-native as they progress with their Control-M Web Services. They're more reliable than the others on the market right now. 

I would advise anyone to start with a trial version of this product. I think they'll be very impressed with it. 

We don't use Python to a significant degree at all in our environment. We have been looking into that, but nothing solid yet. We don't use AWS but are looking to get into it in 2024.

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
Balabrahmam Chakka - PeerSpot reviewer
Integration Administrator at Sainsbury's Supermarkets Ltd
Real User
Reduced the number of jobs that we run daily
Pros and Cons
  • "Control-M has helped us resolve issues 70% to 80% faster. It provides us with alerts instead of having someone go to that particular server and check the logs to determine where the issue is. We can simply click on the alert information, then everything is in front of us. This provides us with time savings, human effort savings, and process savings."
  • "Control-M reporting isn't that good. It is very limited. We would like the ability to create our own reports as well as the ability to publish dashboards in the cloud, which would help us. Improved reporting will help us determine statuses and get the answers that we need. However, I personally think BMC is not focusing on the reporting. I have even visited the BMC office in India, and asked, "Why haven't you improved the reporting?""

What is our primary use case?

I work for the second largest chain of supermarkets in the UK. We are running about 90% of our jobs through Control-M. This applies for jobs and scripts on-premises and in the cloud.

When we used Control-M version 7, we were just doing scheduling. When we moved to Control-M version 9 six months ago, we started using the cloud plugins, like AWS.

How has it helped my organization?

Control-M is business-critical for our operations. It does all our monitoring and tracking.

Our command center people watch the Control-M job status and alerts. Since the pandemic started, and we are working from home, we have been providing them with Self Service. We started this two or three months back. Now, they can watch the jobs and alerts through their mobile and iPads instead of logging into their laptops.

We set up a file transfer mechanism because this will be easier for Control-M to track end-to-end.

We use Control-M as part of our DevOps automation toolchains. We have a four-person team for Control-M. We help the DevOps team create new jobs. We assign a dedicated resource to understand their requirements and how they can be integrated with other jobs. Because Control-M works end-to-end, it is critical for our DevOps daily jobs.

We use Control-M to streamline our data and analytics projects. Control-M has helped improve our data transfers. If there are no security concerns, the data can directly link to downstream systems. We use Control-M to watch all the transfers of files to their targets.

What is most valuable?

All our Control-M alerts go to our internal automation.

It has two-way integration. We now have a ServiceNow integration. 

What needs improvement?

Control-M reporting isn't that good. It is very limited. We would like the ability to create our own reports as well as the ability to publish dashboards in the cloud, which would help us. Improved reporting will help us determine statuses and get the answers that we need. However, I personally think BMC is not focusing on the reporting. I have even visited the BMC office in India, and asked, "Why haven't you improved the reporting?"

There are some latency issues with jobs between on-premises and the cloud. BMC is helping a lot to check the imports and exports from version 7 to version 9, including the EM server and the mainframe.

Control-M could improve agentless connectivity a little more. We are using it almost 100% with agents, but when we start using agentless, Sainsbury's Bank has different security mechanisms and we cannot install Control-M. For example, the agentless connection fluctuates a lot, which triggers alerts.

For how long have I used the solution?

I have worked with Control-M for almost 10 years, since 2010.

What do I think about the stability of the solution?

The stability is very good. 

What do I think about the scalability of the solution?

The scalability of the latest version is a drastic improvement compared to version 7.

How are customer service and technical support?

We are getting good help from them. When I use Support Central, I can also see tickets that have been created by my colleagues.

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

We currently have IBM TWS as a job scheduler, but they don't automate their ticketing. Whereas, Control-M has automatic ticketing. 

We are using TWS for mainframe data. We are looking to start moving all our TWS jobs to Control-M now that Control-M is in the cloud. We are looking at moving these jobs around September or October, then we will have 200,000 jobs daily in Control-M.

How was the initial setup?

We are trying to import from Control-M version 7 to Control-M version 9, but have experienced a major problem with its new features (database-related stuff). We are slowly fixing this as we go, with the help of BMC. Right now, we are doing this process step-by-step, but we can't upgrade everything to the latest version. We can only move everything to Control-M version 9.5.

Initially, we were first-timers doing the cloud. We had so many trials and errors. For importing, we created virtual machines in AWS and set up a lot of automation. However, we needed a static IP address for Control-M. So, we had to start from scratch to create new virtual machines with static IP addresses.

We are currently importing step-by-step. We still have two mainframe servers that we need to do and should be done by the end of August.

What was our ROI?

We have 70,000 jobs running daily. Control-M has reduced the number of jobs that we are running daily. We used to have more than 500,000 jobs running daily. This is very important to us.

Control-M has helped us resolve issues 70% to 80% faster. It provides us with alerts instead of having someone go to that particular server and check the logs to determine where the issue is. We can simply click on the alert information, then everything is in front of us. This provides us with time savings, human effort savings, and process savings.

Which other solutions did I evaluate?

You can't compare other tools to Control-M, because Control-M is further ahead of any other tool.

What other advice do I have?

Once a year, as part of our disaster recovery, we restart Control-M and see what happens. Next, we will run those jobs through Control-M. Then, we will show management, "This is what happens if you use Control-M and if you don't use Control-M."

There are some areas of our business where we don't have Control-M. When we start doing those areas through Control-M, it will be an end-to-end solution.

We don't use Control-M for file transfers. We have proposed using Control-M for file transfer with version 9, which is in the cloud.

In the future, we will give control to the DevOps team through BMC AMI Change Manager. They will create the jobs, then send them to our BMC Control-M team for review, testing, and promotion to production. However, adopting this will take some time.

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

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)
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
DevOps Expert at Saint-Gobain ADFORS CZ s.r.o.
Real User
With workflow capabilities, a successful job can call another job, while a failed job is restarted and we are notified
Pros and Cons
  • "The unified view where you can define, orchestrate, and monitor applications, workflows, and data pipelines is important because we have more than one team working on Control-M. We have a support team, a job-creation team, and a SAP team. We can all work together on it. It avoids anyone from working on his part and not using the latest modifications."
  • "I would like to have a web version of Control-M to replace the client. Currently, our support and jobs-creation teams are using the client and that needs to be installed on a PC. It's very heavy, consuming a lot of resources compared to the web portal. I know that they're trying to improve the client with the latest version, but for me, there hasn't been enough improvement yet."

What is our primary use case?

We started to use Control-M in 2019 with the MFT (Managed File Transfer) module. Last year, we also started to use Control-M for SAP jobs.

How has it helped my organization?

Our transfer processes with MFT from Control-M, are quicker and safer now because we have implemented a lot of rules. For example, it helps balance jobs. Also, there are workflow capabilities, so that if a job succeeds it can call another job. And in case of failure, it can restart the job and warn us by email or by a Teams message. That kind of warning for the support team means we can address problems before the business complains. These are benefits we did not have before Control-M. Improvements to data transfers via Control-M are on the order of 80 percent.

Issue resolution, with Control-M in place, is about 90 percent faster, because most of the issues are resolved without intervention. It has also helped improve Service Level Operations performance by between 80 and 90 percent.

In terms of automating critical processes with Control-M, it's not only for transfer jobs but we have some applications that need to be restarted every week for performance reasons. Instead of having someone connecting on Sunday to do that, we can do it automatically with Control-M. These are OS jobs and it's very critical for us to restart them.

The kinds of things that Control-M is allowing us to do now that we couldn't do with our homemade solution are in terms of physical operations, the monitoring through the dashboard, and the reporting. With our previous solution we didn't have any reporting, but now we can export reports to PDF and share them with the business. We also have Control-M/Forecast to plan the maintenance of our system and to know which systems and jobs will be impacted during a maintenance period.

What is most valuable?

The most valuable feature of Control-M is the collaboration. We can all work together on it and have a better view of things with the dashboard, and that's true even for business users. The unified view where you can define, orchestrate, and monitor applications, workflows, and data pipelines is important because we have more than one team working on Control-M. We have a support team, a job-creation team, and a SAP team. We can all work together on it. It avoids anyone from working on his part and not using the latest modifications. In case there is an issue, we know who made the mistake, and we can also roll back the mistake. That is very good.

Our line-of-business personnel use Control-M's web interface. We have tried the mobile application, but we haven't used it enough. The web interface is very good. Previously, a business user would ask us, "What about my file?" Now that we have Control-M, they are up to date on it. The self-service portal is very helpful because it gives them a view of the latest version of the interface and they can consult it without having to ask us every morning about a given operation.

What needs improvement?

I would like to have a web version of Control-M to replace the client. Currently, our support and jobs-creation teams are using the client and that needs to be installed on a PC. It's very heavy, consuming a lot of resources compared to the web portal. I know that they're trying to improve the client with the latest version, but for me, there hasn't been enough improvement yet. I think their roadmap shows that there will not be a new version next year, due to the crisis. I think the next major version will only come out in two years.

For how long have I used the solution?

I've been using Control-M for two years.

What do I think about the stability of the solution?

It's very stable. In the last year, there have only been two issues. One was our fault, due to our configuration. The other was because of the Control-M application. We had to call support to get them to solve it. But overall, it's a very stable application.

What do I think about the scalability of the solution?

The scalability of Control-M is very good.

We plan to expand the jobs Control-M is running, including operating system jobs, and then maybe database jobs such as SQL Server and Oracle. Currently, we have more than 2,100 jobs and we are planning to have 30,000 within two years.

In terms of the number of our employees who are using Control-M, we have about 40 admin users, including on some support teams, our SAP team, and our job-creation team. On the business side, we may have about 15 users. For day-to-day administration of Control-M we need three to five people.

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

We started with Control-M to replace our file exchange solution, which was a homemade solution. Our needs were growing and growing and our solution was not enough to support them.

How was the initial setup?

For the MFT part, the initial deployment took about four months because we had to convert all our jobs and all our scripts to Control-M. It was not easy because we had a homemade solution, so there was no conversion tool for it. That meant we had to do it manually, with some scripting on our side.

In terms of our deployment strategy, for SAP we started with one SAP system from among the many we have. We started with a complex one, which was Redwood. The version of Redwood we had was not supported by the Control-M importing tool. Again, we had to do it on our side without a conversion tool.

What about the implementation team?

I was the project leader for the implementation of Control-M in our organization. We brought in an external company to help us install the solution. Our experience with that company, to be honest, was not good. We have now changed to a better one. We now work with Ogchee.

We have had a person from Ogchee working with us, full-time, for a few months. He is here to help us and to support the application. But we also worked before with BMC support, and it was okay.

What was our ROI?

We have definitely seen return on our investment with Control-M. The benefits are very good.

Which other solutions did I evaluate?

We did not really look at other options because we had some good information from an external partner about Control-M and that is why we went directly to Control-M.

What other advice do I have?

Don't hesitate to use Control-M, because there are a lot of benefits for your everyday work, especially the collaboration, scalability, and the visibility from the tool.

I would rate Control-M a nine out of 10. The one missing point is because the client is not that mature.

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
Sr. Automation Engineer at a computer software company with 1,001-5,000 employees
Real User
Our developers use the automation API and Jobs-as-Code to kick off jobs without having to write something manually
Pros and Cons
  • "It provides a unified view where you can orchestrate and monitor all your application workloads and data pipelines. That's very important because with cloud, software as a service, edge computing, traditional data center, and legacy apps, there are all these environments. If you don't have that single pane of glass or that one place to look at, you're going to invest a lot of time and resources into tracking things down when they go wrong."
  • "They really need to work on improving the web interface, as there are still a lot of bugs... In general, they need to do a lot of work on shoring up their testing and quality assurance. A lot of bugs seem to make it into the product."

What is our primary use case?

The business services that Control-M supports for our organization include everything from finances, marketing, data analysis, big data, data lakes—pretty much everything.

We have it on-prem and we also use it in the cloud. We still have most of our components in the data center right now.

How has it helped my organization?

When it comes to data analytics, Control-M helps make sure that as we're ingesting data and running it, that the workflows are kicking off in the correct order, and that we're actually getting the data. It's also making sure we return data to the appropriate business units or partners. It definitely streamlines our data analytics. It has sped things up because we don't have to wait on humans anymore to kick things off.

Our line-of-business personnel use Control-M's web interfaces and it gives them a view, a red-light/green-light dashboard. They can see if things are behind or ahead. It helps them keep track of the stuff that's important to them without having to call other people or put in tickets.

In addition, the use of Control-M as part of our DevOps automation toolchains and leveraging of its “as-code” interfaces for developers has considerably sped up our ability to roll out new applications and application updates. It's also allowed our developers, even when they have one-off projects, to easily use the automation API and Jobs-as-Code to kick those off without having to write that kind of function by hand or find another tool. It has been a big part of our DevOps process.

We have also automated critical processes with Control-M. The top-three are 

  1. a number of financial processes
  2. data ingestion
  3. and what we call partner management. 

Those automations mean we get things done consistently and on time. It also lets us know if we're not going to meet our deadlines and enables us to be proactive instead of reactive.

By using Control-M 20’s Role-Based Administration feature, we have been able to decentralize teams to manage their own application workflow orchestration environments. That's important because it frees up resources. People can get things done more quickly without having to stop what they're doing. And it allows them to focus, instead of constantly being pulled in a thousand directions or having to call in different people for help. It helps eliminate tickets or requests to a Control-M administrator, and that frees up our operations personnel to focus on what's more important for the business. Instead of watching for and answering tickets, they're actually able to be proactive and look for potential bottlenecks or to help people enhance their processes.

Another benefit comes from using Control-M 20's Centralized Connection Profiles. Being able to store all connection profiles in a central database helps with efficiencies, with DevOps initiatives, and it helps with ownership.

The extended capabilities of version 20, especially the web interface, help because we don't have to deploy clients or maintain the clients. It lets pretty much anybody who wants to use it just fire up a web browser and use it. That's the biggest capability of version 20, for us.

Overall, Control-M lets us spot problems more quickly. And in terms of Service Level Operations performance, it helps because we now can be proactive instead of reactive. If we know that we're not going to meet an SLA, we can meet ahead of time instead of having to wait and see.

What is most valuable?

Among the most valuable features are

  • the measuring and monitoring of the SLAs, the service level agreements—they code in recovery actions for when things go wrong
  • the single pane of glass enables us to see everything, all the processes, in one place
  • the ability to integrate with all sorts of different platforms and services.

It provides a unified view where you can orchestrate and monitor all your application workloads and data pipelines. That's very important because with cloud, software as a service, edge computing, traditional data center, and legacy apps, there are all these environments. If you don't have that single pane of glass or that one place to look at, you're going to invest a lot of time and resources into tracking things down when they go wrong. You really need that single pane of glass to show you what's going on across all your disparate systems, in one location.

We also have Control-M for internal and external file transfers. It's really just a part of our normal, everyday procedures. It makes sure that they happen. It makes sure that we got the files. It makes sure that data has flowed back to the appropriate departments.

What needs improvement?

They really need to work on improving the web interface, as there are still a lot of bugs. 

Also, the new Helix Control-M version doesn't seem quite ready for prime time for many of us. 

In general, they need to do a lot of work on shoring up their testing and quality assurance. A lot of bugs seem to make it into the product.

For how long have I used the solution?

I've been using Control-M for about 21 years.

What do I think about the stability of the solution?

It's a highly stable product. It has to be—it runs your business. It's very mature in that arena.

What do I think about the scalability of the solution?

It's highly scalable, so as your enterprise grows it's very easy to continue adding in agents or to expand out your management platform, with little or no downtime.

We use Control-M for financial applications across the spectrum, including marketing, data analytics, data analysis, and partner management. We continue to grow and as new things come online we're adding them in.

They do a really good job in terms of how they expand the product and keep up with the times. It's very cloud-centric, but at the same time, it can also handle legacy-type stuff. Overall, they've done a very good job on that.

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

What we had previously were all home-grown solutions. We switched to Control-M to get a grip on our environment, to have the single pane of glass to enable us to monitor and manage everything from one location. And the big thing that Control-M allows us to do now that we could not do previously is to orchestrate workflows across all types of disparate systems.

How was the initial setup?

The initial setup was straightforward. It was easy to get going, easy to install, easy to create workflows consistently. There wasn't a huge learning curve. We learned as we went, but it was pretty easy to learn the product.

Our deployment took about a month.

The integrated guides and how-to videos in the solution’s web interface, for helping get to full productivity with the solution, are very helpful. People watch them. They need to be a little more in-depth and they need more of them, but what they have is a good start.

We have about 120 people in our company who are actively using Control-M. They range from developers to operations personnel, financial analysts, marketing analysts, and data scientists. We have a team of three for day-to-day administration of Control-M but they do more than just Control-M.

What about the implementation team?

We worked with a partner to deploy Control-M. Our experience with them was very good.

What was our ROI?

We have definitely seen return on our investment in Control-M, many times over.

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

It's an expensive product, there's no doubt about it. It's one of those solutions where you're paying upfront to reap the benefits down the road. You're going to spend a lot of money upfront, but the benefits you're going to get out of it are going to quickly pay for it. That's something people don't understand sometimes.

Which other solutions did I evaluate?

We looked at a few others including IBM's Tivoli and Computer Associates.

The biggest difference is that Control-M is a more mature and growing product. The other ones were very stale. They just didn't seem to be keeping up with the times. Also, Control-M requires a lot less administration than the other products did, and Control-M was a lot easier to learn than the others. The others had a very high learning curve.

What other advice do I have?

Look at Control-M from a high level, not only down to the details. See how it can benefit your company. Most companies have data centers, they use cloud, they use software as a service—they use a mixture. But even if you're 100 percent cloud, Control-M can still benefit you because it is going to give you that vision that you've never had before of what is going on in the company. And it's going to present it to you in a way that business owners and business management can understand. It's also going to allow you to do some amazing things with automation around the automation API and Jobs-as-Code. So instead of having all these siloed systems, it is really going to help you get many things under that one roof.

My biggest advice to anybody looking into this product, or any product like this is, is to do your due diligence and get your training. It's very important to have some sort of education on this going into it. That training could be formal training or it could be help from a Control-M partner for your implementation. You can get the easy stuff out of the product on day one, but to get to the things that are really going to save money and make you say, "Wow," that takes some knowledge.

The biggest thing I have learned from using Control-M is that you never know what you can automate until you try.

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