Control-M is used as a job scheduler. Initially, when started, it was more or less used as a batch scheduler. It has evolved over time so much that even the name has been changed to Control-M Workload Automation, which completely justifies its name. It is not just a scheduler anymore; it does many more things than just a scheduler.

Control-M, especially, is quick to the market with all the new products that are coming up, be it the integrations or the capabilities that are emerging. Any new technology that comes up in any stream such as AWS or Azure or GCP is addressed quickly. Control-M is very fast to the market when compared to other schedulers or other vendors where they develop these integrations and the rapid release of these integrations. The target is around three to five integration releases within a month, which is best in the market. The support that is received when a case is raised is really quick and very helpful when compared to others.

The best features of Control-M are highlighted by its GUI, which is a game-changer because it is so user-friendly. Any person who is logging into Control-M for the first time will know what each option or the parameter is. It is so self-explained, eye-catching, and very easy to use. Currently, Control-M is moving away from the thick client to the web client, which also maintains the same user-friendliness. Another key feature is that it keeps up to the market standards with respect to security, compliance, and everything. All the capabilities are available, and it is just a drag and drop of each to create jobs. In this DevOps world, integration with the DevOps pipelines is possible where job creation can be automated as well.

It is very easy to integrate technologies for DataOps and DevOps processes as things change, not only for DevOps processes but for any other tools in the market. There are more than 100 plus integrations that are already built within Control-M where you can just drag and drop to create and have a centralized view of all these jobs, be it ETL jobs, data lake jobs, or ADF jobs. Adding these dependencies and having a centralized view is something that Control-M thrives on. If any issues are faced during this process, the support model and documentation around it are very clear and abstract.

Control-M has helped businesses positively, especially when started as a scheduler without exploring most of the modules that were available. Over the last eight years, the first benefit was that when integrating with a DevOps process to maintain version control, a client had an in-built macro or PowerShell script which was incompatible when the version was upgraded. Standardizing it using the Workflow Change Manager, which promotes jobs between environments, was suggested. Control-M's Application Integrator helps to create custom job types rather than using in-built job types, which helped develop around 150 or 200 jobs with that approach. Control-M also offers a conversion tool that allows conversion of jobs from other tools to Control-M without requiring costly professional services.

There are areas for improvement, especially with the transition from the thick client to the web GUI. While Control-M's main game-changer is its GUI, the current web interface is less user-friendly than the thick client. A Windows client option should be maintained for flexibility, as it caters to users who prefer different interfaces.

Control-M has been used for 15 years.

Control-M as a tool is very stable. However, stability can be affected by how the environment is set up, including network stability, storage, and database factors. Control-M itself is robust, and it would receive a rating of 10.

Control-M is a scalable solution, and its scalability would receive a rating of 10.

When a case is raised, the response that is received is really quick and very helpful when compared to others.

Conversion of jobs from other scheduling tools to Control-M has been done. Jobs have been converted from Dollar Universe and TWS, IWS Maestro as they call it, to Control-M. There is working experience on Maestro and Dollar Universe as well.

Deploying Control-M is straightforward; as long as you know how to deploy it, the first attempt may be more difficult compared to subsequent ones. Documentation and support are readily available, making the overall process easy.

Compared to other vendors, Control-M is quite costly. However, all good things come with a good cost. The features, speed to the market, and quality justify the higher expense. Control-M may need to rethink how to make it more cost-effective because while many clients appreciate the tool and its features, the current economic climate and desire for cost optimization lead some clients to consider other options that may solely meet their scheduling requirements at a lower cost.

Control-M does require maintenance, especially for the VMs in both on-prem and Azure environments, which need to be patched regularly. A separate team handles automated patching, and there is a move away from on-prem to have everything on a single cloud instance.

Maintenance is easy overall; applying patches does not take much time. The technical aspect of upgrading or patching is minimal, but the process around it can take longer. Gathering concurrence from job owners for downtime and executing the patching process usually takes time, even though the actual installation is quick.

Control-M would be recommended if you are looking for a scheduling or workload automation solution and are not overly concerned with cost but want to utilize features to enhance your estate and maintain a centralized view. This review has been given an overall rating of 9.

Control-M manages pretty much everything in our hemisphere, helping us meet our financial regulatory obligations, file transfers, running scripts, PowerShell, and SQL, making it critical to our day-to-day operations.

Control-M supports our DataOps and DevOps initiatives by providing an avenue for our DevOps teams to problem-solve in an easy way, giving them a platform to build on rather than having to start from scratch.

The measurable benefits or improvements we've achieved with Control-M are critical in the finance industry, as it keeps us on target with all regulatory requirements. Without Control-M, I don't know where we'd be, and if we shut it off, the business would probably run for about six hours before we faced serious issues, highlighting its role as a key component to our success.

Control-M has definitely enabled new capabilities and business processes that weren't possible before, allowing us to go to other departments and problem-solve for them, eliminating manual tasks that have been done for years. Departments now benefit from not even needing to look back at whether a task is being done since the information is readily available, providing them more time in their day for productivity and enhancing life for our customers.

Control-M is a great product already, but everything can do with a bit of improvement. Personally, I'd like to see a little bit more color in the web interface, and in terms of its technical ability, the one thing I would be critical about is a bit more user-friendliness with the reports and the way we input information into it.

I've been working with Control-M for three years.

Once we have tested things and gotten them into play, during the three years that I've been working with Control-M, I've encountered only one problem, and BMC's support has been quite good, allowing us to solve that issue quickly and easily.

Once we have tested things and gotten them into play, during the three years that I've been working with Control-M, I've encountered only one problem, and BMC's support has been quite good, allowing us to solve that issue quickly and easily.

The biggest return on investment from using Control-M, from my point of view, is the ease of use and the time it gives our employees back in their day to be more productive.

I would give Control-M a very good rating in building, scheduling, managing, and monitoring workflows. It is pretty easy to use, and we have taken people without any type of formal training and been able to get them into using Control-M fully as a scheduler within weeks, proving its ease of use. In terms of its use for scheduling and building, it provides options, and it comes back to having flexibility, which is appreciated by anyone who has worked in the build area. With all the plug-in options and various job types that you can create, it increases the flexibility and the avenues available for using Control-M as a solution.

I've not had much interaction with licensing. In terms of costs, I think in life you have to pay for what you want, and generally, if you want quality, you've got to pay for it, but in my limited knowledge of pricing outside of Control-M and BMC, I think it is competitive, recognizing there's not a lot out there like Control-M, making it difficult to determine what the price should be as it is a critical piece of work worth its value. I would rate this product an 8.5 out of 10.

Control-M runs all of our payments, batch, and managed file transfers.

Approximately 250 people use Control-M on a daily basis. Their main roles include schedulers who create batch jobs, testers, and administrators and operators.

Control-M enables us to better support our DataOps and DevOps initiatives because we have a release system every month, which allows us to work more effectively and we're automating that system with Control-M.

Control-M orchestrates workloads across several environments. Currently, we use it across five environments.

Control-M handles complex data pipelines and analytics processes by allowing us to integrate with different services. For instance, we use it with our Power BI for our reporting tools, and for pipelines for release functions as well.

We only use on-premise for the creation and automation of data pipelines with Control-M. We don't have the cloud yet.

The main features of Control-M that we appreciate the most are the scheduling and the automation capabilities. When it works, it really works very well for us. Another feature that we appreciate is the file watching service because we interact with many different sections who drop files in various locations. It's great to have that feature to kick off batch when a file becomes available.

Control-M's performance in building, scheduling, managing, and monitoring workflows is amazing. I love Control-M and enjoy working on it. I appreciate how it has automated our workflow because before we had Control-M, it was a manual workflow that was open to user error and took much longer to complete because of the manual checks we had to do before we moved on to our next piece of batch. We've been able to automate it and this has enabled us to triple our workflow.

Having more options with regards to scheduling in Control-M would improve it. There are certain scheduling features that aren't available currently in Control-M, which would be nice to be added.

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

I assess the stability and reliability of Control-M as very reliable because we very rarely have any downtime. The only time we would ever have any downtime is during our reboots, which we need to do failovers for, and those are very brief. When we are actually doing our batch, I don't remember a time we've had any downtime on our production side.

Control-M scales with the growing needs of my company brilliantly. It's been really good for us. We've added so much to it over the last two or three years. We've added more users, more jobs, and all different types of jobs including OS jobs, MFTs, and file watch, and it's been absolutely no problem for us to add. We've probably doubled our amount of jobs in the last two years, so we've had absolutely no problem with it. It's scaling perfectly.

My experience with customer service and technical support has been positive. Anytime we've had a problem, which is very rarely, or we've had a question, it's always been answered very swiftly or I've looked through the community myself. The community is actually really good, and I really appreciate that side of it because I even contribute on that side. I've never had a problem.

We were using an in-house product for running our batch before integrating with Control-M. Control-M enabled us to automate that batch, but it also enabled us to bring in many more things that weren't currently being done by us.

The biggest return on investment for me when using Control-M is the reduced errors, quicker runtimes for our batch, and making the job easier.

I have not considered other solutions while using Control-M.

Control-M's performance has improved our timing and the speed of the releases. It's halved our release speed basically in the last two years.

The measurable benefits and improvements my company has achieved with Control-M include reduced errors, which is the first big one. Before we used the previous in-house software, we would have a lot of manual errors that would have to be changed manually if there was a change in a variable or anything else. Now it's all automated, and the system runs for itself. We've tripled our workflow and we are doing more in less time than we used to previously.

Control-M has enabled new capabilities and business processes that weren't possible before. Our integration with external partners has become easier due to the MFT capability that we weren't doing before. Now we're able to connect through them. These were manual processes done through moving files manually from one server to another, through different partners, but now we're able to integrate it all as one.

Regarding licensing, we handle licensing through endpoints. We've had to increase our endpoints because we're increasing the amount of workflow we have and the amount of jobs that we have. We've had to increase the number of endpoints we've needed. It's very easy to handle the growth and it's easily done.

I haven't used the Control-M Python client, but I've used a small amount of API.

I have not been using Control-M since I've been in my company because I've been in my company since 2009, and we started using it in 2019.

The impact of the migration to Control-M on our business-critical operations has led to fewer errors and fewer failures. Our biggest success story has been the lack of errors. Even when we do have errors, having the outputs available to us allows us to clearly see what the problem is.

I would rate this review ten out of ten.

My main use cases of Control-M involve workload automation, with two key areas being financial reconciliation and supply chain management. In financial reconciliation, a global financial services company pulls data from all its divisions around the world to perform end-of-day, end-of-month, and end-of-quarter reconciliation across a range of technologies, teams, and borders.

In supply chain management, manufacturers with retail stores need to ensure that the right stock is in the right places, which can be complicated. The third main use case relates to integration with SAP, making existing PA environments cheaper and less service-heavy. Those are the three main ones in my customer base.

My customers use Control-M to orchestrate workloads across multiple environments. Control-M orchestration is capable of handling complex data pipelines or analytic processes, which is key for some of our financial services customer use cases and is a relatively core part of their requirements.

My banking customer that moved some capabilities to the cloud uses Control-M for both on-premises and cloud technologies, so that's my awareness regarding the creation and automation of data pipelines across those environments.

The features of Control-M that I find most appealing, and that I've heard customers appreciate, include the file transfer capability, which is very unsexy but fundamentally important. It's what it's all about—extracting data and moving it to different places.

The relationship between Control-M and my clients' DataOps and DevOps initiatives is complex. Most of our customers have their DevOps initiatives somewhat divorced from the Control-M elements. However, this is slowly changing as DevOps starts to incorporate both customer-facing aspects and the internal legacy parts of their business. They are gradually integrating, and that agile way of working is coming closer together.

The measurable benefits or improvements my clients have seen with Control-M relate to compliance, particularly in financial reconciliation. There are significant financial penalties for errors in this area, so it's crucial to develop a robust integration with ITSM systems to ensure that tasks perform as intended and meet the right SLAs.

Control-M can be improved by continuing the trend of being both a mature product and one that is not standing still, as evidenced by the ongoing improvements we've seen. The file transfer piece is particularly popular, and it's essential to keep up with the demands that customers place on it.

I suspect a lot of my customers aren't pushing the boundaries of what Control-M can scale to, but the job scheduler approach allows for immense scalability. Many of our customers are only beginning to explore its capabilities.

I have been selling Control-M for one and a half years.

I don't believe any of my customers have reported issues around the availability of Control-M regarding stability and reliability.

I suspect a lot of my customers aren't pushing the boundaries of what Control-M can scale to, but the job scheduler approach allows for immense scalability. Many of our customers are only beginning to explore its capabilities.

I haven't heard any complaints about BMC's service team support; as far as I know, customers feel comfortable about it. Of course, I can't speak from personal experience.

There is a competitor to Control-M that many of my customers consider; the big one is IBM's IWS. There is some anecdotal evidence of dissatisfaction among customers regarding support since it has moved to HCL. I recently spoke to someone about exactly that scenario.

The overall experience of the migration and deployment process for my customers tends to be a horror show because migrations are critical and touch everything. The biggest challenge people face is unpicking the complexities involved. Thus, it's often hard to simply migrate, especially while maintaining a good relationship with the existing vendor.

On the topic of pricing, setup cost, and licensing for Control-M, everyone moans about it. We work with some customers on optimizing their job structure to deliver proper value for money. This is significant work, as getting value for money is a challenge we constantly address.

The biggest return on investment for users of Control-M in the financial sector can be fairly straightforward: you can easily state how much performing tasks manually would cost in person-hours. By avoiding financial penalties from regulations, the business case essentially writes itself. In manufacturing, it's more complex, as you look at how to minimize manual costs and whether Control-M helps reduce customer churn and ensures stock is in the right location. Extracting this information aids in making the business case.

On the topic of pricing, setup cost, and licensing for Control-M, everyone moans about it. We work with some customers on optimizing their job structure to deliver proper value for money. This is significant work, as getting value for money is a challenge we constantly address.

There is a competitor to Control-M that many of my customers consider; the big one is IBM's IWS. There is some anecdotal evidence of dissatisfaction among customers regarding support since it has moved to HCL. I recently spoke to someone about exactly that scenario.

In my company, zero users interact with Control-M because we don't actively use it; we just sell it. My customer base ranges widely, with some cases having a small batch team of a few dozen users up to hundreds, probably more in rough figures. I wouldn't have huge visibility on that.

I have heard of the Control-M Python client or API very recently. My experience selling the Control-M Python client or API is relatively new to me. It's not entirely new, but it hasn't come up much in my customer base. However, as DevOps and Control-M are becoming better together, I am seeing more of that.

Regarding metrics or data on how my customers perceive Control-M, I don't have any off the top of my head, and I probably would be privileged to know.

My advice to a company considering Control-M is to bring us in to help with the assessment work. Go through a value stream exercise to clarify what you're trying to accomplish and examine the entire end-to-end process. Control-M and workload automation is a solved problem; it's something you should buy rather than build yourself. That would eliminate undifferentiated heavy lifting. Certainly, we can assist clients with automation and value chain assessment, especially beyond the BMC space, which often presents a messy and complex landscape. I would rate this product a 9 out of 10.

My main business use case supported by Control-M is performance data generation, which includes all orchestration jobs and workflow processes.

The feature I appreciate most about Control-M is the capability of scheduling jobs automatically, as the dependency and control runs all tasks automatically by themselves.

I value this feature because it frees up a significant amount of time from my daily work, allowing me to concentrate on other more manual tasks.

Control-M supports my DataOps and DevOps initiatives by automating the entire process through the dependency and successor logic.

The biggest return on investment for me when using Control-M is that it helps me automate the manual tasks of my daily work.

My company has achieved measurable benefits with Control-M through automation, which has improved delivery and reduced the possible manual errors that a human can make.

I think Control-M can be improved because we recently moved to Helix, the cloud control, and the latency of the application is substantial; the job is running in the background, but the UI side is very slow on the front end.

Control-M integrates with new or changing technologies within my DataOps or DevOps stack well; the cloud improvement is positive, but now that AI is a significant topic, it could incorporate more AI features. Although they do have some AI functionality in the cloud applications, it is not particularly useful and intuitive.

If I were to estimate the improvement percentage, I would say around seventy percent.

I have been using Control-M for six years.

After moving to the cloud solution, I believe Control-M is much more stable; we have been using it for around two years, and I do not see any downtime. On the cloud solution, I do not observe any downtime; however, on-premises, sometimes the server is not up and the agent is not running.

In terms of scalability, I believe Control-M works well for the work I am performing, around eight or ten because we are heavily using it for morning tasks, data preparation, and preparations early in the morning for the day.

BMC customer service and technical support typically assist us; we usually speak to the relationship manager to raise any concerns or issues that we find, and so far, we still receive the answers we need, although the response may not be as immediate as we expect.

I would rate the customer service and technical support a seven out of ten.

My company considered switching to other solutions once and attempted to source alternatives, but we ultimately decided to stick with BMC.

The overall experience with the deployment process of Control-M depends on whether we are discussing the application itself or the creation of the job.

I would describe Control-M's performance in building, scheduling, managing, and monitoring workflows as quite good; I have previously used other orchestration tools, and I believe Control-M has much better visualization of workflows in terms of scheduling jobs.

I use Control-M to orchestrate workloads across multiple environments; we have a stream of workflows that connects to AWS, then SQL Server, and our in-house applications and so on, creating a large web of workflows across different kinds of applications.

Control-M handles complex data pipelines and analytics processes mostly through the designer that designs the workflow; we put the complex logic there, and it serves more as a tooling for us to use than Control-M handling all of this.

The creation and automation of data pipelines across on-premises and cloud technologies with Control-M is quite good; so far, I have no complaints with that. Between the on-premises and cloud, we have one less concern about how the application processes on the cloud, but on-premises, we have more freedom in accessing the database and some backend functionality.

My advice for someone or other companies considering Control-M is to check their business requirements and see what Control-M can actually offer because they do have many plugins for different kinds of usage, so it totally depends on what the company wants.

I would rate this review eight out of ten overall.

Control-M is a scheduling tool that I have been using for the last three years. Earlier I used Autosys as a primary scheduling tool. When I started Control-M, it was a new experience because Autosys was over the cloud and we used to log in to the browser. Control-M is specifically for the application where we are using it now. The good thing is that there are so many connectors available.

Although I have one year of Autosys experience, Control-M presents a vast opportunity for us as a developer. Currently, I am in a data warehousing project where all the tools are legacy tools such as Informatica, SalesScript, Control-M, and database. When we are moving to the cloud, Control-M is still valid and relevant. We are transferring our data to the cloud and using Control-M as a scheduler. We are not using native cloud scheduler to date because all the developers here are accustomed to it.

We are almost using around 60 to 70% of the features. Control-M is providing us with so much capability to use during our daily problem-solving.

The good thing is that there are so many connectors available. Control-M provides lots of features, and we are almost using around 60 to 70% of them. Control-M is providing us with so much capability to use during our daily problem-solving.

When I joined this project and was very new to Control-M, there was one problem that even the seniors were facing sometimes. Suppose you are using Informatica; there are lots of Informatica developers in the market or some other tools that are very known to everyone. Even though Control-M is used by lots of people, the documentation in the beginning was very hard to search for on Google. This is why we had to reach out to people who were experienced, and it was a tough job for us because a few functionalities are not properly written in the documentation.

Another area of improvement is related to multiple versions of Control-M being used. In dev, one version exists, and in production, one version exists. In production, the stable version is used. Sometimes when we change over, there are multiple domains in Control-M such as Planning, Monitoring, History, and Forecast Tools. When we hop from one domain to another, sometimes we open a job, and the detail dialog box or detail window is not able to open.

Some features which are hidden are not properly documented in Control-M itself, or maybe documented but not properly given or described with examples. This is a problem. Sometimes we are forced to connect to senior developers who have used it for five to six years or more to learn about it.

I have been using Control-M for the last three years.

There is no maintenance on my end. In the last three years, I have seen two upgrades that were done by the admin team. Control-M is using the new versions, and as a developer, I am using it.

Control-M processes about 10,000 jobs starting every day in our production environment, and adding new jobs is very simple. We don't feel any pressure on Control-M because it is processing multiple jobs in parallel.

Regarding contacting technical support about Control-M, we tried, but at that time, we didn't get any response. We reached out to our client head, described our problem, and received assistance.

As a developer, I created an account in the BMC community to get help support. We post there nearly because sometimes we need solutions very quickly, and we don't have time to connect with the guys in the Control-M help desk.

Earlier I used Autosys as a primary scheduling tool. When I started Control-M, it was a new experience because Autosys was over the cloud.

Regarding the initial installation and setup of Control-M, I still have not installed it. I need to connect with one of my friends who are working in the ops team, as I am in the developer team. We never install Control-M here in this project.

I need to connect with one of my friends working in the ops team, as I am in the developer team. They have the access to install, uninstall, or configure anything.

Regarding pricing, I cannot comment. As a developer, this is not in my hands, and it was decided by the client.

If Control-M is selling their product to new customers who have never used anything, then who will support the new customer? The customer may not have the senior engineer who has used Control-M earlier, so the documentation matters. Control-M can improve this in the way that others have; for example, Databricks, Google Cloud, and Azure have so much documentation.

Whatever we wanted, we have it. Control-M is not executing anything; it is just a scheduler. It schedules an Informatica job, and Informatica is running on its operating system, managing all the logs, and showing us that the job is completed. I have not seen any lagging. This can be answered by the ops team better because as a developer, I own a few applications, and when they start and end, my duty is done. Overall, I would give Control-M a rating of eight out of ten.

I'm not sure about Control-M because it is only for another team member to use. What I can tell you is it is very helpful to use Control-M in the mainframe platform because we can run and schedule many routines at the same time and we can create some scenarios. By these scenarios, we can run a lot of routines. We can build some scenarios and maintain this in the real world in production environment.

Regarding Control-M, what I can mention is I only know about the platform used nowadays for our team, and I believe it is a very archaic model. Probably there is another interface, better solutions and maybe with an interface easier to use on a daily basis. But what we have nowadays is something not so familiar for people that don't have a complete understanding about how to use.

Regarding Control-M, I'm not the one to use it directly, but I know it is a very powerful tool and very dynamic and helps us a lot on a daily basis. I believe the tools to schedule a routine in Control-M are very helpful. On a daily basis, we can use a lot without some problems. It's very easy to use.

It is necessary to take some time to learn Control-M. More or less a month to be familiar with the first steps. As you continue, you will increase your understanding about the feature and probably need more or less six months.

People in the first initial step need more or less one month to be familiar with some commands and start using Control-M tools. To feel comfortable using it on a daily basis without support, it takes more or less six months. This is the appropriate time to be able to use Control-M.

I have used another tool related to Control-M, but it is not so similar. It is something more related about running only individual routines one, two, or three routines at the same time. It is Topaz. It is a tool directly connected to the mainframe as well, but it is more destined to developers to build routines and programs and run these sources. It is not the same, but it is what I use on a daily basis when I need to run routines.

I have never experienced any issues such as lagging or crashing with Control-M.

The scalability of Control-M is adequate. We need to follow some steps to add some routines, but that's acceptable. What I know about this feature is it is reasonable to use when you need to add some new steps, schedule some new routines, or add some files. It is pretty nice and not a big deal to use.

I didn't need to contact the technical support or customer support for Control-M.

I would rate Control-M overall an eight out of ten. I believe you can put my company name as entity data. I'm a software engineer.

My use case for Control-M is orchestration.

The best features of Control-M are that it is easy to use; even a non-technical person can learn it in a couple of days with normal documentation and a few videos. Just two days should be sufficient to pick it up. Users do not need to be technical to use the tool, and it is easy to implement and deploy.

Integrating Control-M with other technologies for DataOps and DevOps is easy; we export the jobs we create in a non-prod environment and, on the runtime, we know what variables need to be replaced, and we replace those variables to deploy to prod since Control-M is just an XML file, which is very easy to search and replace.

Control-M is extensively used in our projects. When we start a project and it becomes an enterprise tool, we are required to use it. If there are any failures, we can tag them with an incident, making it easy for maintenance, monitoring, tracking, and deployment since everything is in one place.

The area that has room for improvement in Control-M is a better dashboard. For example, sometimes we have up to 100 Control-M jobs, and there is no dashboard to know how many jobs are in progress, completed, or waiting for files. That requires us to create an additional dashboard on top of the Control-M metadata.

I've been using Control-M since I started my career in data warehousing in 2011 or 2012 since there are more jobs, more tables, and more data loads in data warehousing.

When it comes to stability, I would rate it as good, an eight out of ten.

The scalability of Control-M is good; we create different servers for different projects instead of putting all jobs on one server, and I would rate scalability as an eight out of ten.

The technical support from Control-M is good; I normally never ask the Control-M team for help as it hasn't gotten stuck for me, however, they are supportive, and I would rate it an eight out of ten.

We have used different orchestration tools, however, I am not aware of the specific tools you mentioned.

The deployment of the solution is easy.

Regarding the duration of deployment, if everything is proper, I don't see a big challenge. Normally, it takes a day if you have the code ready and follow the process and checklist.

The return on investment seen with Control-M is significant; in my experience, we run more than 100 to 150 jobs a day, and to monitor those jobs, one or two people should be enough since it triggers emails for failures and allows us to view logs within Control-M itself.

I'm not sure about the pricing of Control-M. I didn't get involved at the pricing level.

When comparing Control-M with other solutions, I see that everywhere, orchestration tools are simple, and while they come with basic monitoring and alerting functionalities, the decision to use Control-M often comes down to cost, licensing, and maintenance.

My relationship with BMC is good.

I recommend Control-M if there are no other tools available as it is easy to use, with easy maintenance and a centralized monitoring system, alerting system, and incident creation.

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

My use case for Control-M is that it's a job scheduler for some jobs regarding data warehouse jobs and billing tasks for a telecommunication company, mainly monitoring jobs.

The best features of Control-M that I most appreciate are the integration and unification of different systems, such as BMC Remedy, integration with alerting systems, and the unification for the dashboard—something akin to one dashboard to monitor everything, which is very good. It can communicate with different platforms such as cloud, different systems, and OSes. I also appreciate the visualization; when we are designing a tree, a job tree, the option to visualize the dependencies and the mapping is very user-friendly.

Control-M has positively impacted my organization, particularly in the flexibility it offers in scheduling jobs. It has a nice feature called Calendar Integration that integrates with the company calendar to allow for the holidays and special events regarding the organization, not only the public calendar, but specifically for the organization.

There are some areas in Control-M that have room for improvement, particularly some constraints regarding the scripts, such as limitations in how they can be executed and integrated; it's not the normal scripting way in some cases. It's not in all cases, but in some cases, there are limitations and constraints in running the scripts.

Additionally, Control-M requires some hardware resources in terms of system requirements; it consumes some hardware resources.

I have been using Control-M for about five years or more than five years.

The stability of Control-M gets a nine from me; although we faced one issue during this year regarding its stability, nine is good for it.

Scalability for Control-M is good; I would rate it an eight due to the high license cost, but it's scalable.

I would rate the technical support for Control-M a nine.

I have seen a return on investment with Control-M; we have the real-time alert feature. Our administrators get alerts for any job failures or emails for any issues, which saves our business. We also have reporting tools embedded in Control-M to generate daily reports and keep historical data. All of this handles our job, mainly the monitoring and automation for the scheduling. That's why we are using it.

My thoughts on the pricing of Control-M are that the cost of the license is very high. You have to implement some cost-saving measures, such as cleaning up jobs that are not required anymore on a monthly basis, in order to control the license, as the license is very costly.

Additionally, there's a dependency on training; on a yearly basis, or whenever there's a new version, we need to schedule training and an official training from an accredited course center or from BMC itself, which is very costly.

I haven't dealt with other solutions or vendors on the market, but I can say Control-M is better than good when it comes to automation.

There is a good feature about the drag-and-drop; we can easily create and modify jobs with drag-and-drop in the interface, which makes it easier and user-friendly. BMC is a good strategic partner; they are helping us in mapping out our migration strategy, and we have a team from their side that supports us in our job. They know our case and they are specialized in our system, following up on our system.

I recommend Control-M to other users because it's user-friendly, it has a unified dashboard, and it's easy to schedule and use. However, there are certain limitations, especially for larger organizations, to afford the cost of the license and the cost of training. For a small organization, I wouldn't recommend it, as it would be very costly for them.

I would rate Control-M an eight out of ten, considering I have some concerns about the cost and the training, which is also related to cost.