Control-M Reviews

We have been using it in the institute to manage all the student data and post-study processes.

We have been using Control-M in our IT department to maintain server backups and database updates and schedule regular updates. Furthermore, it is being used in our library system to automate periodic updates of library catalogs. Control-M also automates email notifications for event announcements and fee structures.

The best feature is that we can automate everything. Moreover, we can access all the features through one dashboard, which is beneficial. 

We have been using Control-M for managing simple automation tasks. It will be very effective in managing other types of tasks. Control-M has the potential and can be very useful in managing business aspects.

The licensing cost can be improved. Although it provides good value, it could be better. The pricing model should be optimized.

Its initial setup is a bit complex. They could provide more documentation and tutorials to make the initial setup easier to understand. Enhancing the documentation could simplify the setup process.

We have been using it for more than one and a half years.

The tasks we have been handling are straightforward automation tasks. Considering that, I would rate it a ten out of ten.

It is scalable. I would rate it a nine out of ten for scalability.

We have 50 to 60 users.

Technical support has improved. In the past, they were not as supportive, but they are better now. Based on recent experiences, I would rate them an eight out of ten.

Positive

This is the first solution that we have used.

The initial setup and configuration are a bit challenging. There is a bit of a learning curve for some people. It takes a few days.

At the time, there were not many recommendations or resources to understand and deploy it properly, so it took us a couple of weeks to understand and deploy. It has been simplified over the last eight to ten months.

We implemented it in-house.

It has reduced the total cost of ownership by 30% to 40%. 

It has saved a lot of time for our employees and staff members. For a small task, there have been about 40% to 50% time savings.

It is a little bit expensive.

Our relationship with BMC is more transformative. We consider BMC as a strategic partner and trusted advisor.

I would definitely recommend Control-M to every institute because it is extremely helpful to manage every task without any manual error. I would suggest trying Control-M at least once. It is also recommended to start with the documentation and familiarize oneself with basic concepts before integrating it into the business aspect. 

Overall, I would rate it an eight out of ten.

Control-M is a job scheduler. You can schedule FTP jobs or use scripts within Control-M. You can also execute commands when necessary to schedule, or you can just run a script that is hosted on a server. Based on the schedule, you can orchestrate or automate jobs. You can set dependencies between jobs. You can correlate and create a sequence of your jobs and execute them in the order you wish. You can set the variables and options that you like. You can set the prerequisites and post-job activities after the completion, such as reports analysis, emails, etc.

Helix Control-M is critical for us. If we do not have a job scheduler like this, we will have to have people running 366 different jobs on a daily basis and 24 hours a day. These are the jobs that we run from midnight to midnight every single day on a scheduled basis.

I do not use Helix Control-M's Python client or Airflow. I am using the web client. I do not create jobs. I give my users access to create their own jobs. I just maintain the agents and keep the administration going. When they have questions, they come up to me and ask. We just use the web interface to go into the planning mode and create our jobs, folders, dependencies, etc.

Control-M has helped to give business users visibility and control over their jobs. Both Control-M and Helix Control-M allow me to give users control over their own set of jobs. They can log in and orchestrate their jobs as they want. They can also troubleshoot them on their own. It makes that easy. I just have to be hands-off and stand by in case they need assistance, but once the tool is deployed and every agent is up and running, it is easy. The people who have the jobs running or the job scheduled know about their own jobs. They know their own demands. They have control over the decision of when they are going to run it and how they are going to run it. It makes it very simple, and it helps.

You can set up your users and define whether they have admin privileges or they can just affect a set of jobs.

The fact that it is all centralized in the web browser makes it easily accessible from everywhere. All my users are IT people. They do different things. They do databases. They do informatics. They do development and things of that nature. To business users, such as board members of the company, we can give them reports on, for example, how the business closed and how much profits were there, or if all the transactions were submitted to the bank on time. If not, what were they missing? We can provide all things of that nature. We can pull it all up in a report and then schedule it on a daily basis or weekly basis. It is simple.

There have been cost savings with Helix Control-M. The license that the company was paying for Control-M, including support, was three grand more expensive than Helix Control-M. With Control-M, we also had to have an administrator dedicated to maintaining Control-M on-premises. That cost of having a person dedicated to doing just Control-M jobs is gone after we moved to the cloud. We are not only getting more money in savings; we are also making a better distribution and use of our time. By not having a dedicated person, we are saving a couple of grand. We are saving on the license and, of course, resources. We do not have to have dedicated resources such as servers. We do it virtually. We do not need to have resources reserved for the server and database. I just have to deploy the agent, which can run multiple instances in my cluster. They can share resources, which is another saving there.

In Helix Control-M, we have the automation API that allows us to customize and do integrations easily in any script, such as Java or Python. It is all integrated within the integration API.

Every year, they add another set of automation or compatibility with different applications. They are capable of integrating with Informatica, AWS, etc. You can schedule queries directly from Control-M on databases without having a server or agent. You can do scan jobs or queries directly. Every other month, they are doing releases, and they have tons of new integrations, which makes it compatible with more and more applications around the cloud.

They have a department that handles requests for enhancements. I talked to Control-M guys back in October or November when they had a gathering here in Atlanta. We talked about not being able to go back in history in Helix Control-M for more than two weeks. We submitted a request for enhancement. They told us that they are working on it, and they are thinking of expanding that to 30 days. We would like to see it expand to 90 days, but they are working on it. In Control-M, we were able to go back 180 days, but that was on-prem. The storage of that data was on our own servers. We know that storage is money, and we do not expect them to store that much of the data, but at least 30 to 60 days seem proper.

Community Loans of America has been using Control-M since version 6. It has been at least 10 years.

I have not had any downtime with Helix Control-M. All the upgrades are scheduled, and they give us a time window when they think they are going to schedule them, and we adjust. I have not seen anybody notice it. The jobs get held before the update, and they start automatically after the update. If anybody noticed it, that was because I had to tell them that a maintenance window was coming up and to be aware of it.

I contacted their support a couple of times to ask them about an error that I did not understand. They have three guys who are pretty handy. When you ask questions, you, of course, have to wait at least 24 hours for someone to respond. They are pretty fast. Most of my queries were responded to within the same day, which is great. I would, for sure, rate their support a solid 10 out of 10.

Positive

We were just using Control-M. We did not have any other scheduler. We migrated from Control-M to Helix Control-M. 

Control-M is on-premises, and it requires a dedicated administrator. Control-M has three major pieces. It has a Control-M server. It has a main agent, and it has a database. If you have HA, you will have the same things at a secondary location, so you will have to manage the cluster and make sure that all the pieces are working together. If, for some reason, one side fails, HA tries to recover in the second location. The management or the administration side of things is a challenge. It requires a dedicated person. Our main Control-M guy left us six years ago. Every time we had an issue with Control-M, it took us three or four hours to put it back where it should be. By migrating to Helix Control-M, our biggest success was getting away from the administration. Having Helix Control-M, which is a cloud product, allows us to use all the advantages of the job scheduler without handling the administration of our own servers.

If I compare Helix Control-M with what I had to do on Control-M on-prem, the process is very similar. The calendar has changed though. There was an advantage with Control-M that you could specify when was your new day load. Our new day load was every day at 9 AM in the morning. With Helix Control-M, we have to have only midnight as a new load because of the change of the date. It was a big challenge because we had to reorchestrate all the jobs to suit the new day load being moved from 9 AM to midnight. 

Essentially, scheduling a job or creating a new job requires the same effort in both applications. The advantage of Helix Control-M is that I do not depend on a single agent to pull FTP profiles. All of them are centralized. It does not matter which agent I am using. I have access to the whole list. In Control-M, FTP profiles had to be added to the agents that were being used. Helix Control-M has made it easy to orchestrate data pipelines in production because now, I do not have to worry about the whole backend of Control-M. I am sure that it is up to date, and I can log in reliably, load jobs, and orchestrate them as I need.

I once tried to migrate Control-M to something else called RunMyJobs. Compared to RunMyJobs, I would definitely go for Helix Control-M.

In terms of our environment, we are a mixed shop. The majority of our products are on-prem. We have a Nutanix cluster in our data center, and that is where we host the majority of our things. We have maybe one or two devices on AWS. For Azure, I know that we have a license because it comes with our enterprise Microsoft 365 license, but I do not recall having any hosting there.

For migration, they have a migration tool that makes it very easy. You can run this migration tool, and it will export all your current jobs in a JSON file. It will try to import them on the tenant in the cloud on Helix Control-M. We faced a few challenges here and there because at the time we did it, some features were missing in Helix Control-M or were not supported, but they were supported in Control-M. We used to have dual endpoint profiles for the MSP file transfer or the ASP. FTP jobs have profiles where the server address, user password, or key gets stored. In Control-M, you could have a single profile with two endpoints. You could have Host A and Host B in a single profile. That was not supported with Helix Control-M at the time we decided to migrate, so we had the challenge of converting all those dual endpoint profiles into single endpoint profiles to be able to be imported. I know for a fact now that it is no longer an issue because they now allow you to create dual endpoint profiles in Helix Control-M, but it was a challenge at the time.

Fixing things here and there and making it compatible took about six months. Those six months were not just because of how hard it was to migrate. It was a combination of the challenges of migration and other tasks that we have not been doing because we could not afford to have a person dedicated entirely only to Control-M. Effectively, the time dedicated exclusively to the migration was two and a half months, but the migration was distributed in a six-month calendar because of other duties and tasks that I had to perform.

We got help from VPMA. VPMA is our reseller. We purchased a license of Control-M through VPMA, and they have support and all that. We get help from them. They helped us to run the Orchestrator or the migration tool from BMC. They told us where the odd points were, and then we went to do it on our own. We came back and reviewed them again and kept fixing them.

Overall, we had three people. We had one person from VPMA, and then there was me and one of my technicians to assist me.

It is not bad. The company can afford it, and it pays for itself. We have those jobs running automatically.

I would rate Helix Control-M a 10 out of 10. I like Helix Control-M. 

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

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

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

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

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

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

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

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

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

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

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

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

We have been using the solution for around seven years. 

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

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

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

Positive

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The stability is very good. 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

We predominantly use Control-M SAP R3 jobs. That's our primary batch job load with external vendors and internally on our AWS instance. That's our batch load alongside a few custom integrations. They are not public applications. It's all in-house applications. We have integrations and API integrations for the API hubs, which speak to multiple other applications within our next case.

It isn't the only point of failure, but Control-M handles our business-critical, priority-one applications. We have other options. Control-M runs the SAP side for all batches. The time needed to realize the benefits depends on the scale and complexity. 

One use case was in health care and involved shipment orders. With Control-M controlling the workflow, we could effectively monitor it and forecast any delays. This enabled us to deliver critical products in under four hours across hospitals in the network. 

We can apply the same standards and run the same set of jobs across environments. Once they are tested in the non-production environment, we can move them seamlessly to the production environment. 

We have a nightly process of batch reports. Before Control-M, we spent around 12 hours manually scheduling reports in SAP. After streamlining the process, we reduced manual work to nine and a half hours. The business could update all the processes before midnight.

While it doesn't totally free up IT personnel, it provides visibility into self-service tools where business users can see their pipelines or job streams. It would be read-only access for the business side, but to take action on the job, they still need to contact the IT team. 

Control-M doesn't facilitate collaboration between business and IT users, but It provides a better user experience. Both parties can see what they are talking about, so there's no black zone for any of the parties. Before Control-M, the functional team had a particular nomenclature to relate what they had seen on Control-M. With the self-service tool, they can simply relay the job name. The collaboration starts there, and it builds over with a lot of other parameters.

Control-M provides a centralized view of our enterprise workload. As the owner, I can access my dashboard and see the status of jobs across the enterprise. It is strong at integrating with different applications and creating a pipeline of dependencies across applications on different operating systems. 

When it comes to developments where we have to move across regions or environments, it seamlessly integrates and adapts to different regions. Regarding integration with the DevOps pipeline, it allows us to use a JSON file and promote it across environments easily. 

We use Control-M to deploy workflows for DataOps and DevOps initiatives. It allows us to quickly test workflows or configuration changes without much manual effort. We add the JSON file for the conversation parameters and let the system handle the schedule. Integrating other DevOps tools within the journey gives us the management perspective and approval of multiple pipelines.

I'm currently working on the SaaS version, but I've also worked on the on-prem versions before. There is a handful of features that haven't been added to the SaaS version, and the BMC knows that. It's a matter of time before they prioritize the missing pieces and bring them into the SaaS version. 

I started using Control-M back in 2018.

Control-M has the best stability in the market. They claim 99.99 percent availability. It's hardly four hours of downtime throughout the year.

Control-M is infinitely scalable. We only need to add agents. BMC will take care of it if you need anything on the SaaS side, but we can handle the rest using our agent architecture.

I rate BMC support 10 out of 10. They are stringent about their SLA timelines. They respond on time, and if it's a priority one, they will call immediately. 

Positive

We previously used the SAP Scheduler and adopted Dollar Universe. All our local manual efforts ran in  Windows Scheduler.

It was a greenfield approach, and I was there from day one as a consultant. Deploying Control-M can be easy or difficult, depending on what the business needs. It takes a while to understand the infrastructure setup our business needs and the number of jobs we need to run through this application. 

It took a while to understand the infrastructure setup we require. We had to understand the number of jobs running through this application and how business-critical they are. The documentation BMC provides is top-notch and covers every step we must follow. 

Migrating to Control-M is a bit tricky in terms of preparing the data and having the right tool to convert required parameters into a Control-M-ready job. Control-M has a feature called AMIGO that helps us migrate from the existing source.  Converting a job and loading it into our Control-M format isn't straightforward. We must do some prerecorded checks and setups before. 

There is some maintenance in the form of updating agents and deploying patches on the SAP application. Since it's a SaaS application, BMC handles most of the maintenance on the server side. 

The license model is based on the number of jobs we run on the SaaS application or the number of executions, unlike the on-premise model options. If we have a handful of jobs, it's always good to consider Control-M, but if it's a large number of jobs, Control-M might not be a great option. 

Control-M enables us to consolidate our jobs, and it helps us have a uniform approach and schedule. It helps to have the audit logs available. The scheduler space is nice in terms of control. 

We attempted to leverage ActiveBatch by Redwood and a few other options, but Control-M had all the features we needed. It gives us a 360-degree view of our implementation across silos. The architectural requirements also vary depending on the criticality of the applications. 

Control-M allows us to customize the job templates for any application we need, which covers all our future plans. Its integration speed is excellent because it has templates for every application. 

I rate Control-M 10 out of 10. New users will be fine if they follow the Control-M documentation. There's also a book you can buy on Amazon called "Batch Scheduling" that comprehensively covers batch operations and how BMC has evolved over time. 

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.

We are using it for job scheduling, shift scheduling, etc. It is pretty much orchestrating all the job shifts for the IT team or core team.

We specialize in security, which means 24/7 your system or team needs to be ready for anything or anybody in the world, independent of even time differences. If you are managing your client's services from Europe, or anywhere else in the world, Control-M makes it easier to do scheduling, saving people time.

Since we have different satellite offices in Toronto and Ottawa, we use different role accessibility in different locations. That is why we are using it on-premise. However, in the next six months or so, we are planning to go to a hybrid cloud environment on Control-M since we are adding two or more satellite offices. We think that it will be more manageable if we implement it in a hybrid cloud environment.

The solution is innovative. Specifically for the overseas and time differences, you can feel the efficiency of Batch Impact Manager on jobs, batch processing, and impact management. It works the best on these kinds of issues. It saves us time and money, which is important. We save a lot using Control-M.

The most important thing is it is easy to manage conversions and stuff. It is easy to convert different systems, like AWS, which saves time.

We are working with vendors, partners, and clients to manage GDPR and data privacy. This solution is good with data privacy because BMC is GDPR compliant. That is very important, especially for overseas clients and businesses.

Overall, Control-M is quite critical for our business. I would rate this as nine out of 10.

• The monitoring
• Workflows
• Production
• Scheduling the shifts
• Timeframes for specific roles and management

Time differences are important because we have some overseas clients. That is why we are using Batch Impact Manager for the Control-M, which is very helpful for us. It detects potential blocks in advance, delays, and errors. That helps us to optimize the scheduling, then the batch workload processing as well. 

It is pretty easy to create, integrate, and automate data pipelines. It is user-friendly, not rocket science. That is what I like about the Control-M, and specifically Batch Impact Manager. You will need some orientation and need to know what you are doing if you are integrating your system, and this solution makes it easier.

We use Control-M Python Client and cloud data service integrations with GCP, which is pretty hassle-free. There aren't any problems or compliance issues. It is pretty easy to retrieve the data, do conversions, etc. They are on-time, and there is not much of a delay. 

The engineers on our team say that it is pretty easy to build, test and promote data workflows with the data coding language integrated into Control-M through the Control-M automation API. The ease of integration is eight out of 10. Python is the main language that our database managers and data engineers are using along with some other languages. 

The Control-M interface is user-friendly and easy to use. Orientation-wise, it is easy for data engineers to adapt.

Ingesting and processing data from different platforms can be a challenge. Control-M does allow integration for this with other systems to make this easier. For example, we integrate Control-M with an in-house system to do this.

I am unsure if Control-M is compliant with Microsoft Azure environment integrations. We have some clients in Azure environments. Specifically, in Canada, government agencies and nonprofits mostly use Microsoft Azure.

I have been using it for almost a year and a half.

The stability is very good. My impressions of the stability are very positive.

I would rate the scalability as nine out of 10.

The technical support is near perfect. I would rate them as nine and a half out of 10.

Positive

We were previously using an in-house solution, but we weren't improving it much, which is why we switched to Control-M.

Control-M creates cost-efficiencies, saves time on scheduling and data efficiency, and provides better data management. We use the managed services as well because we partner with some clients at MSPs and MSSPs. This solution is also good for their environment because it is easy to access, retrieve, and work with actionable data as well as all the procedures and processes. It is good and works. I would rate it as eight out of 10. 

The total cost of ownership is impacted by the Control-M pricing as well as the overall cost of the procedures and daily batch processing. We can easily see that at the end of the year, in terms of big time and money savings.

The pricing and licensing could be better. However, when I compare Control-M pricing with JAMS, Control-M is still better priced than JAMS enterprise.

We also evaluated JAMS Scheduler, which is also a workload automation solution. The pricing for Control-M was better and has good predictive maintenance that is better than JAMS. Control-M is also more integrated with Google for different solutions.

Control-M is better for the cloud. Specifically, the hybrid cloud is the best. On-premise is still okay, but it depends. Its hybrid cloud environment works better and is optimized in a better way to save money and time. Its implementation is easy from the cloud GCP and AWS. Microsoft Azure is not there yet, but otherwise, it is perfect.

I would rate the solution as nine out of 10.

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

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

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

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

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

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

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

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

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

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

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

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

Among the most valuable features are

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

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

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

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

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

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

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

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

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

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

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

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

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

Our deployment took about a month.

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

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

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

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

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

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

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

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

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

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