Control-M Reviews

We use it as a scheduling tool. We use it for infrastructure backups and running scheduled tasks, but nothing in regards to data analytics.

It is an infrastructure process behind the scenes: custom backups and custom file migrations.

We leverage Control-M for backups. That would be a critical process that we have integrated. This allows teams that rely on the backups to have a single pane of glass through the dashboard to determine if their backup is successful. It allows email alerts or triggers, if something fails or we need to do manual intervention.

My organization has been able to script scheduled jobs in Control-M to potentially replace legacy products that are at end of life or end of service. The previous backup applications that were being used for specific files, folders, or applications were no longer being supported, therefore being able to use Control-M to replace that has been very valuable.

We rely on Control-M for automation. Anything that would have been a manual effort previously or legacy, Control-M has been able to replace.

The scheduler allows you to pretty much run anything from anywhere. It is very convenient. The sensor reporting that the scheduler gives you can monitor hundreds of jobs that could potentially be running in a given hour.

All the scheduled tasks are available in a dashboard or workflow view that different teams leverage. This is important and great. Having the ability to have a dashboard or workflow allows for easier troubleshooting. We also have alerting set up through email triggers, which are very helpful.

We leverage it for file transfer. We don't necessarily have application workflows dependent on those, but we do have Control-M for the migration of files. The visibility of a successful transfer is very useful, e.g., the ability to report on that or view whether that job succeeded or failed in the dashboard. You have an alert that would trigger on a failure. So, failure is automated. The Control-M job could retry that file migration a number of times based on logic that you have programmed into the job, and having to avoid manual intervention is useful.

The alerts are helpful and can contribute to faster issue resolution in the event of an issue.

The infrastructure updates could use improvement. Some of the previous updates that we have run to get to version nineteen were troublesome. So, a more seamless upgrade path for the infrastructure components would be useful. I don't know if they have replaced that in version 20 or if version 20 has an easier path, but I would like to see the upgrade from one version to the next version be a little smoother.

I have been using it for about five years.

The platform has been great. I don't think we have had any downtime besides our upgrade process.

The scheduling process has been able to handle almost everything that we have asked it to do. It seems to be able to run pretty much anything from anywhere within our environment.

This solution was a new integration/installation done before my involvement.

The application was a part of the infrastructure when I joined. We have been able to add automations for components that were otherwise manual. 

The upgrades are a bit complex. The last time we did an upgrade, it took several hours.

The upgrade was planned. We ran into an issue, then we had to reach out to support. They were quick to respond, but the resolution did take several hours. They did a good job. The issue was resolved in a timely manner during our upgrade window. Their service was an eight or nine out of 10, as far as issue resolution. To be a 10 out of 10, I would like something prescheduled. If we could have had support personnel available for the upgrade procedure, it would have been helpful. So, it was just the time element.

The product is helpful for its automation components.

It is worth evaluating.

Control-M is mainly an infrastructure tool that we use for scheduled tasks. The IT teams and most of the operations teams are the ones who use it. I would estimate about 10 people, but the management of the application is centralized.

The big lesson learnt: Reach out to support when using the product and do something that you could reimagine.

We don't have any data analytics in Control-M.

We don't have developer integration with Control-M at this point.

Control-M is doing a fantastic job for what we use it for. The product is a nine out of 10.

Control-M is the primary tool used in our department as an interface between desk jobs and SAP. I create and monitor the jobs in Control-M and that ties into SAP.

At this point, we are using it as a batch scheduler, which is primarily used for SAP. We use it for everything financial, like payroll, because SAP is our primary ERP.

Our system administrator uses Control-M when he is scheduling batch jobs. 

Our SAP jobs are fairly critical, because there are a lot of collections from a financial aspect coming through on a daily basis. From that regard, Control-M is fairly critical for us. We need to know when and if jobs fail since that has an impact on the collection of money.

We used to have multiple shifts of people sitting there and monitoring our jobs until the introduction of Control-M. So, with Control-M, we have been able to reduce the human capital, in regards to shift workers. Therefore, we are saving money from a cost perspective, in this regard, by about 25%. We have had a 50% reduction in staff. The ability to monitor and be notified, when our jobs have on time completion or fail, has had a big impact on the company.

It is more about the notification tools and its ability interface with SAP. It has the ability to notify people about jobs and schedule based on prerequisites, because this is not something that we can actually do within SAP. For example, if one job is dependent on another job completing, SAP doesn't have this capability. This is why we went with Control-M. 

It is very simple to use. I have only been in this position for four years, but it was really easy for me to pick up and monitor Control-M.

In the client, it provides a unified view for me. I can alter the view that I want to see jobs and conditions. This is nice to have. The fact that you can see everything in one space is very important, especially these days where everything is about data and monitoring as well as because we are working from home on a global basis. So, in real-time, I can monitor jobs, failures, or anything that might be stuck. The real-time monitoring and the ability to see everything in one place is important for us because we operate 24/7.

I use the mobile and web interface. I started off with the desktop client, and there are some slight differences in the interface between the mobile, web interface, and desktop client. This is a nice feature, because when I am on the road or going for a walk, then I have my mobile with me and I can get notifications if I need to run anything. Then, I can just log on from there.

All the modules within Control-M can interface with SAP.

Everybody's biggest gripe is the reporting capability option. It is a gripe because there is a lot of information in Control-M, but the solution doesn't have a good reporting tool to extract that information. Now, if you want all that information, you need to rely on another third-party BI tool to extract the information out of Control-M.

Two or three years ago, I was at a seminar where they said that they were looking at improving the reporting. However, from that time until now, there hasn't been much of a change in the reporting capabilities. Especially in today's day and age, where accessing data has become very important, this is something that they should be looking at.

We are using Commvault as our backup application. Currently, there is no integration between Control-M and Commvault. 

I have been in my position as an operator for four years. The company has had Control-M for over 20 years. 

Over the last three upgrades, Control-M has improved quite a bit. When I joined our department, Control-M didn't have a good reputation because it was always falling over. All our issues were addressed by Control-M with their upgrades. 

In the latest version, we find it has been extremely stable. We haven't had many failures as far as the program is concerned.

Generally, we don't interact directly with BMC because we have a service provider that we use, Blue Turtle. So, we interact with Control-M via Blue Turtle for any queries that we are having.

The initial setup was done before I joined the company.

We have a system administrator who applies our Control-M updates.

Control-M has helped us improve Service Level Operations performance. It helped us from the monitoring perspective. Now, we are able to control real-time monitoring and real-time notification of any failures that would occur within the system. Because we run it 24/7, we have notifications for any failures that have been setup. They will come through on our mobiles, and in that regard, Control-M has helped us.

Unfortunately, I can't compare it to anything else.

It just works. Control-M is very good. You only need to look at something else when an application gives you problems. However, in our environment, it is stable and just works. We haven't even bothered looking at anything else.

I can highly recommend it. It is very easy to learn. It is very stable. It has multiple interfaces, e.g., you can use it on your desktop, access it via the web interface, or access it on a mobile. The support that you get is actually quite good. It is a tool that I highly recommend. For what we require it to do, it does exactly that and more.

We have a system administrator, a chief scheduler, who is my supervisor, and two operators, including me. The four of us are power users who have scheduling capabilities in Control-M. We have different people on our BI team. Overall, 10 people have various levels of access.

We have tried Control-M as part of your DevOps automation toolchains. We are only getting into DevOps now as a company. We are still playing around with it. Currently, we are still fairly separate as far as DevOps is concerned. My department is basically the middleman between dev and operations. Whatever dev wants, we will create those jobs and test them. Once they want to send them into production, they let us know, and it then goes to operations. We are the center for those types of things.

Because we went into lockdown and the financial impact of the lockdown, projects were placed on hold. This year, they were& still on hold. Probably sometime next year, we will be starting on those projects again.

I would rate Control-M as eight out of 10 because the reporting needs improvement.

We primarily use Control-M for financial services. We do file transfers, payroll, HR, and other related tasks.

The top three processes that we have automated with Control-M are payroll, HR reports, and time reports. This automation gives HR, and the business in general, a clearer picture of what is happening as far as the payroll timesheets go, including who's punching in and punching out. Essentially, it improves transparency.

Control-M provides us with a unified view where we can define and monitor applications, and this is very important to us, especially in the audit process. We have auditors and they request certain information; using Control-M, we can log in and create the report according to the parameters they're asking for. It makes life much easier.

Our developers use the web-based interface to monitor their jobs. They do not have access to do anything else but they can tell if their jobs have run, or not.

Our developers leverage the “as-code” interfaces and it makes it very easy to roll out new applications and application updates. Everything is automated as far as transferring files in and out to certain people. This is helpful because it doesn't have to be done manually. It also generates reports automatically for us. Control-M jobs produce the reports so we don't have to create them every day.

We just started using Control-M to streamline our data and analytics projects. So far, it has given us some actionable insights. The streamlining has improved our business service delivery because we can tell if something is running behind, and why. We know if there's an issue before anybody notices.

Control-M has improved our data transfers because it is much easier to do encryption back and forth when sending files.

This product has helped us to achieve faster issue resolution. I estimate that issues are now normally resolved within 10 minutes. It's very quick.

Control-M has helped us to improve service-level operations performance. We have a critical job stream and because we're an institution, we have to have certain data out at a certain time for the federal reserve. If we can detect when something is running behind, and why, then we can notify them ahead of time so that they know the reports are going to be late. It helps them on their end, too. This way, they don't have to call and ask us where their report is.

The most valuable feature is the reporting function. It allows us to pull up reports for specific information that the end-users are looking for.

The planning and monitoring features in Control-M 20 help us because we can forecast to assist with network maintenance. For example, if we have something major going on with the network and there is going to be downtime, we can do a forecast to see what's going to be running at that particular time and adjust things accordingly.

I would like to see more audit report templates added, and perhaps more customizability in terms of reporting.

I have been using Control-M for 15 years.

Control-M is very stable and we've had no major issues with it.

Scalability is not a problem. It absolutely extends with our needs and the jobs that it needs to run in. At this time, it is running payroll reports and other payroll jobs. We are looking at expanding this to other applications in the future, although there is nothing definite yet.

Technical support is very responsive and we have never had any issues with them. Generally, if we have a problem or question, we can open a ticket with BMC and we usually get a response back within an hour, or no later than two hours.

I would rate their support a ten out of ten.

We work with BMC for upgrades and support. We are part of the AMIGO program.

We have absolutely seen a return on investment with Control-M. It is centralized and it's made everything easier for the business end, in particular for getting their reports on time. 

The pricing of Control-M is reasonable. 

The developers in our organization are responsible for creating the scripts. There are 20 of them and they monitor their jobs. With respect to operations including creating, running, modifying, and killing the jobs, there is a group of six staff in charge of that. This group also creates the schedule and the calendars, so essentially, they take care of the day-to-day administration.

My advice for anybody who is considering Control-M is that if they have questions then BMC is great to talk to, but there is also a BMC community and if they have questions or want to know how it's running or working for other organizations, they can post and generally get a response back. There are user groups specifically within Control-M.

I would rate this solution a ten out of ten.

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.

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%.

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.

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. 

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

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.

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.

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.

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.

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.

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.

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.

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

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

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.

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.

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.

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. 

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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. 

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

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

10 to 20 people are administering it.

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. 

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

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.

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

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.

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.

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.

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.

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.

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.

I have been using it for almost 12 years.

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.

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. 

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.

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. 

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.

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

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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.