Control-M Reviews

We use Control-M for ACS and Azure services as it has inbuilt cloud integration. We have a product that works on government databases where we use data scraping and then integrate it with Azure and OpenAI. This integration allows us to process data and get insights. We also use AWS services to save the processed data in the AS.

Control-M is a bit faster compared to other solutions. The job and coding are easier. Also, my DevOps and Ops teams work collaboratively with it, enhancing its efficiency. The workflow is much easier compared to the ACS services we were using. Automation is more advanced, deployment is fast, and version control has been simplified.

They should have a proper integration method that clearly defines the workflow. Additionally, there should be an automation system for developers to set it up more easily and quickly. My Ops team faces certain problems that need addressing.

I have been using Control-M for four to five months.

The downtime is higher compared to AWS. Indexing and databasing are more challenging, and the endpoint sometimes gets reset automatically. The accuracy rate is about 80% to 85%.

As we hire new interns and DevOps partners to scale our business, Control-M scales well with the enterprise's growth. As the workload on Control-M increases, its scalability is much higher. Its cost is very low.

I never had direct communication with technical support because solutions are available on the web. We didn't have a one-on-one conversation, but the support is adequate through online resources.

Neutral

We migrated from AWS to Control-M. It was more cost-effective and capable compared to AWS services. We were a startup with limited resources.

The setup was manageable with certain experienced DevOps staff, making it easy to deploy on the local server.

There was an built-in DevOps team that found Control-M more cost-effective and capable than AWS services.

New users should have a comprehensive understanding of how BMC and Control-M operate. Good coding skills are essential, as well as utilizing open-source codes. Monitoring should be done by someone knowledgeable about the system. I would rate Control-M a seven out of ten.

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.

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.

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

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.

I have been using it for about four years.

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

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.

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.

Positive

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.

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.

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.

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

We primarily use the solution for automation, orchestrating and automating the workloads, and being able to schedule tasks. Prior to Control-M, we were manually running jobs or there was either a scheduled task on Windows, getting Task Scheduler, or we'd have a script laid out that someone would have to run through manually on a daily basis. 

We learned about Control-M and felt that it could take over that process and have it automated, while also providing some monitoring and notifications so that if something did fail, we could easily be notified and keep track of it.

It provides a holistic view of jobs that are scheduled to run. We haven't done full production on it yet. Hopefully, we'll be in production by July or August this year. That said, so far from what we can see, it's going to free up some time for certain staff that has been running these tasks manually overnight. Now, if someone gets notified of an issue, then they can address the issue. In the long run, it'll free up some time and resources to focus on other tasks. 

I like the interface, including how I can see everything and how I can put the jobs together. Depending on the experience, I can either use the GUI or I can use the command line to create jobs based on JSON scripts. It provides that flexibility for someone who has no experience of using Control-M as well as with someone who's a full-blown developer that can get very complex with creating these jobs. Generally, it provides a good interface for everyone with different levels of experience.

Control-M doesn't really process data as far as I can tell. It orchestrates other scripts. From what I understand, Control-M doesn't really ingest or analyze any data. It's a tool to help with the processing of data on different platforms. I can tell it to run a script on one server, to send the data over to another SQL server, or a different platform, Power BI for example, and run a script on Power BI so that it can ingest the data when it gets there and do what it needs to do. Once that's finished, I can send it to another platform to put a dashboard together based on when that data is available.

Once one understands the process of how it functions, it's pretty simple and straightforward to create, integrate, and automate the pipelines. There is a learning curve to understand how it all works, all the components, and all the requirements for parameters and different options. However, it's pretty simple once someone has a basic understanding of how it all works.

The Control-M interface is good for creating, monitoring, and ensuring the delivery of files as part of our data pipeline. There's a wealth of information in both the full client, as well as the web interface that they have. Both are very easy to use and provide all the necessary material to understand how to do various tasks. The help feature is very useful and informative and everything is very easy to understand.

It’s great that Control-M orchestrates all our workflows, including file transfers, applications, data sources, data pipelines, and infrastructure with plugins. There are a lot of plugins and we haven't used all of them yet. Primarily, we've only used the file transfer plugin, the Azure file service, and Azure functions. Primarily, the developers have used that to put the various tasks and workloads in place. While we haven't fully utilized everything in Control-M yet, we're learning how to use the various functionalities and transitioning from our legacy scripts and data sources. 

Some of the documentation could use some improvement, however, it gets you from point A to point B pretty quickly to get the solution in place.

I've been using the solution for almost a year. 

It seems stable. I haven't rolled the solution out to a very large environment yet. The solution we're working on right now seems to be working fine. All the issues we've seen have to do with us figuring out connectivity between Control-M and the cloud services, however, I haven't had any experiences with issues around stability with Control-M.

Right now, it's a small deployment and we have it in four environments. We have it in our dev, QA, UAT, and production environments. Right now, there are two application teams that are using Control-M, however, we have another two or three teams that are looking to get onboarded.

It's pretty scalable. I haven't done a deep dive look into it the scalability, and we haven't identified a need yet to scale out. It seems pretty scalable, yet I'm not sure as I can't speak from personal experience. I don't have experience with it yet.

It was a challenge to get the direction on how Control-M should be implemented. As we learned about new requirements from the customer, implementing those with help from the engineers at BMC was hard. The third-party contractors were one issue, however, when I escalated it to our customer representative, he was able to get me in touch with a dedicated BMC engineer and she was able to give me the information I needed and provided the context and direction on the best approaches. I wasn't able to use the third-party engineer that was assigned to us, however, the internal resource was a great partnership to help move this along.

Neutral

We were using Microsoft and internal tools. We used the basic Windows tools that were built in.

We went with this product to centralize the deployment and to centralize the management of all of the workloads.

Some of the installation components were really complex. I'm more on the infrastructure-based side of Control-M, I deploy it and then get it ready for functional use so that the application developers, script developers, and workload developers could easily access it. It took me three weeks to figure out the requirements for getting the SSL certificates as the documentation wasn't really clear on what those requirements were. Once we figured it out, it was simple, however, the support staff couldn't give me the right information to understand what was required.

It seemed like there was a gap in expectations on what was required for certificates. In terms of the installation overall, it wasn't clear what each variable or what each configuration point was referring to until we were well versed with how everything functioned. Then we were able to say, "Oh, this is what that field meant and this is what was required here." However, during the installation process, there was very limited information on what was being asked at each configuration point.

In terms of strategy, there was a challenge with the customer. I was the third or fourth resource that was brought onto the project. The first three people that handled it, internally and externally, had trouble figuring out what the expectations were. I was handed the baton at the last moment. I had to tie up loose ends and try to get this up and running for the CIO before he started to send up red flags to BMC.

We had an integrator, however, setting up the timing with the integrator was a challenge. What I got from my company and the general expectations weren't clear. When I did get clarification, I wasn't able to get ahold of the contractor since he required a week or two weeks lead time. We then ran behind based on the lack of information I got. Setting up time and requirements was a challenge.

I'm also a contractor working for a customer. Being a third party, trying to work with another third party with minimal information from the client, was just a challenge all around.

There was another team handling the pricing. I'm not sure of the exact costs. 

Our customer chose this solution. 

We do not use the Control-M Python client and cloud data service integrations with AWS and GCP and we do not use Control-M to deliver analytics for complex data pipelines yet.

We haven't gone into production yet, so we haven't rolled this out to all our customers. We're still testing the features and we'll be starting the UAT in two to three weeks.

Right now, we're still in the early stages of rolling everything out. We've gone through the testing in our development environment and in QA to make sure things are good. Now, we're testing performance in UAT internally, and then we'll have customer validation within a few weeks before we go into production.

The solution will play a very critical role in day-to-day operations. However, it'll be at least two months before it becomes critical. Right now, it's still being implemented and evaluated.

It is pretty flexible on various cloud solutions, working with different cloud technologies and platforms. I would say potential users should take a look at it. It does provide a lot of flexibility, especially with the application and integration component that they have. The developers seem to really be able to get what they need out of the AI or the application into an integrated product or feature set.

Before installing Control-M, have a sit down with the Control-M solutions engineer and make sure you share with them all of the details of what you'd like to accomplish before deploying the solution. My client just said, "We want this" and they didn't give us the details about what they were looking for. We ended up having to redesign a few features, as those items were not clarified as part of the installation. When I was brought on board, the customer didn't mention they wanted HA, so that came later. At that point, we had to reinstall and add more servers.

The person who signed the contract was focused on MFTE, which is the enterprise file transfer tool or managed file transfer tool. However, later, the architecture team decided not to use that and go with another tool. Due to that decision, the client could have gone with a SaaS solution instead of the on-premises solution to Control-M and saved a lot of time, money, and hassle on deploying the on-premises infrastructure. So my advice to others is to make sure that the needs and the functional usage of the tool are identified clearly before purchasing or implementing the tool.

I'd rate this tool ten out of ten. It does what it says it does. 

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.

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.

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.

We use it to schedule nightly batch jobs. We also have jobs that run during the day on a cyclic basis to provide up-to-date, real-time information for the company.

I'm also pretty much focused on keeping things going. I'm the only scheduler at the company. We have about 4000 jobs in the daily schedule with around 42,000 iterations of jobs.

Everything that we schedule is run through Control-M. It supplies and provides what is needed, whether it is nighttime processing or cyclic job streams that are needed for the company to do what it needs to do.

The whole Control-M scheduling package is valuable. 

The most important features are that it is easy to use and graphical, since I'm a graphical person. This allows me to see it on the screen. I've used other scheduling tools, and the information wasn't there. Being able to see the jobs that connect to another job is real important to me.

It can do anything that I need. We do real-time jobs. We also do jobs that have to run at certain times. I have not been presented with a scheduling need that I was not able to do. It is very flexible and dynamic.

I learned it intuitively, and it's easy to use. I speak to operators who sometimes have limited technical knowledge and they are able to pick it up with my help. They're able to pick it up pretty easily and do the functions that they need to do. 

I'm not sure how the solution fits together with our business modernization initiatives, as there are things outside of my area, even though Control-M is the scheduling tool of the company. They may use other things, e.g., Big Data.

It always works. There is never a problem with Control-M. If there is a problem it is either with the server Control-M runs on or a scheduling error that was made. 

Control-M is always running and never breaking. I always tease server people about rebooting, since my application is always running.

We were on version 6 and went to version 8 about four years ago. Everything worked just like it used to, but it was more streamlined. When we went to version 9 last year, it was even more streamlined. Things just looked more up-to-date, and it was more web-based. 

Sometimes, I don't think of what can happen next, but I see the new version, and think, "Oh wow, that was a great idea!"

We keep growing in number of jobs. We have more jobs every year, and it is never a problem. Everything still runs like it is supposed to. It works quite well, and there is never an issue with the job count getting bigger.

Compared to large companies, we are small as far as our Control-M footprint.

The technical support is great. On their website, they have a knowledge base, where a lot of times, I find the answer to my problem. If not, whether it is a question or technical problem, I open a case online, and I get responses very quickly. If it is a high level problem, I will get a call back right away. They have follow-the-sun support, so I always have access to someone to talk to. If production is down, I will get someone on the phone right away, and I've never had a problem. They always answer my questions, which is very helpful. They never say, "Hey, you could have looked this up over here." They give me great answers back, which have helped quite a bit.

When I got there, we had Robot Schedule. With this solution, I couldn't see the job connecting, which was sort of frustrating. It was like, "Hey, where does this one go?" 

I know Robot Schedule has advanced. However, we had Robot Schedule and Control-M, and we migrated off of Robot Schedule and moved everything to Control-M. and I was part of that process. I just felt so much better after we phased off Robot Schedule.

The upgrade process is great. They have a whole department with their AMIGO program, where you can have someone walk you through it. We have upgraded to 9.18. When we go to 9.19, it will be real quick. It should be almost hands off from what I understand, and that is what I am attending this BMC event to find out about: the upgrade process. When we did the last one, it was real easy. I understand it will be even easier going forward, so I'm happy with that.

This product saves hours in a day based on my experience working here versus other companies with manual operations.

The solution has helped reduce IT operations costs. Years ago, I would get many calls in operations. I get zero calls now. I may get an email or two about a question operations has, but everything runs. It doesn't break and works like it is supposed to.

I have been exposed to a little bit looking online. We talked to someone through our rep. They were looking at Control-M and some other source scheduler. They went with the other scheduler for some reason. I looked at it online, and thought "Wow, this looks really weird."

Do your due diligence. Look around at what is out there. However, I would 100 percent be behind Control-M. It's a great company. Their support is good. The product is great. It's a good investment. It will keep growing and cover any needs that we have. This product can do everything I need and can help me do anything I need to do to schedule for real time information, supplying things, and batch jobs at night.

We are automating more things. I sometimes hear an application team say, "We are running this manually, and we want to make it automated." I will make a few jobs to save them from doing what they are doing manually and automate it. I am always looking for more things to automate.

The people who are in development of this product seem like they are very forward thinking, and always thinking, "What can we do next?" I think that is great.

We use Control-M to monitor jobs on the endpoints. We monitor throughout the day to see which jobs fail. It helps resolve issues with the programmers. They know if they want to rerun, force complete, or hold a job. We work hand in hand with the programmers who have the final say on what they want to do with a particular job that requires action. Control-M is deployed across multiple locations, but I can't estimate the number of users.

Control-M is a critical part of our operations. We rely on it to do our jobs daily. It helps us automate things that come from the JCL side where you would normally have to do everything manually. It's a little quicker and more automated on the BMC side, which makes things smoother for the end-users. 

The solution allows you to relay your issues to management, who in turn, can communicate them to our customers and programmers. It maintains a dialogue between all parties. It's had an overall positive impact on our process execution. 

We can set up automated email notifications to the programmers or the whole team for a particular job. It helps save time because we're not consistently looking at the job to see if it has ended or failed.

The Control-M interface makes delivering files in our data pipeline a little easier. The integration is so much more seamless, so the transition is a smoother experience.

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

The stability is fairly good. We haven't had any serious issues. 

The response time could be faster when you need a person to answer your questions. There are situations where availability becomes crucial. 

I wasn't involved in the deployment. Maintenance is handled by our unit team. They do updates and patching almost weekly.

I rate Control-M an eight out of ten. It comes down to preference and what you need. There are multiple platforms out there, but I've only used this software.  I recommend doing some research and seeking out a lot of opinions. Talk to other folks who worked with other solutions to get a grip and a better understanding.