BMC AMI Ops Reviews

BMC AMI Ops is our main tool for monitoring and managing the z/OS mainframe environment day-to-day. We primarily use it to monitor system performance, identify issues or abnormal activity, and check the status of mainframe resources. It helps us quickly identify potential problems before they affect applications or users.

Recently, we used BMC AMI Ops to investigate a performance issue on the mainframe. We noticed unusual resource usage and used the monitoring views to identify which system resources were contributing. This helped the support team narrow down the cause quickly and take corrective action before it had a wider impact.

BMC AMI Ops is mainly part of our regular mainframe monitoring. It gives us a quick view of system health and helps the team identify performance or resource issues during day-to-day operations.

BMC AMI Ops has mainly helped us improve the visibility and responsiveness of our mainframe. The team can monitor system health and resource usage, which makes it easier to notice unusual activity and investigate issues before they become larger operational problems. It also improved troubleshooting because the support team has more information available when a performance issue occurs. Instead of spending as much time collecting information from different places, we can use the monitoring views and alerts to narrow down the affected area and start the investigation. Overall, it has helped make our operations more stable and reduced the time spent on identifying the initial cause of some issues.

We have not tracked a specific percentage reduction in downtime, but we have seen an improvement in how quickly the team can respond to issues. When there is a sudden CPU or resource-related issue, the monitoring information and alerts help us identify the affected area much faster than relying only on manual checks. The main benefit is the reduction in the initial investigation. The team can see the current system condition, identify the abnormal activity, and start troubleshooting with the available information. Thus, it helps us resolve issues more efficiently and reduce the risk of performance problems affecting end users.

The monitoring and real-time visibility are the features I found most useful in BMC AMI Ops. We can quickly check CPU and system resource usage, identify unusual activity, and drill into issues when there is a performance problem. The alerts and different monitoring views also make day-to-day troubleshooting very easy.

The alerts in BMC AMI Ops help the team notice abnormal resource usage or performance issues early, instead of waiting for a user to report a problem. The real-time views give us the current system status, which is useful when investigating an issue. The troubleshooting tools are generally easy to use once you are familiar with the different views. Although, new users may need some time to get comfortable with the interface.

BMC AMI Ops provides good visibility across different aspects of the mainframe environment, rather than requiring us to rely on separate monitoring tools for everything. The different monitoring views make it easier to move from higher-level system information to more detailed information when investigating a problem. I also find the historical information useful for troubleshooting recurring performance issues. We can compare what is happening currently with the activity and use that information during analysis. There is a learning curve for users who are new to the product, but once the team becomes familiar with the monitoring options, it becomes a useful part of operations.

BMC AMI Ops is useful for monitoring, but the interface can take some time for new users to understand. I would prefer to see a more modern and intuitive UI with simpler navigation. The product could also make troubleshooting easier by providing more consolidated information. Better dashboards and more customizable alerts would help the team focus on the most important issues without having to move to multiple screens. Improved documentation and more guided workflows for common troubleshooting scenarios would also be helpful for new users.

Another important improvement would be making the product easier for new team members to learn. Some of the monitoring options and views take time to understand, especially when troubleshooting an unfamiliar issue. A more simplified dashboard, clearer navigation, and better guidance around alerts would make the day-to-day experience smoother. It would also be useful to have more flexibility in customization, so each team can focus on the metrics and alerts that are most relevant to their environment.

I have been using BMC AMI Ops for one year.

BMC AMI Ops is stable.

BMC AMI Ops has handled our existing mainframe monitoring requirements well as the workload and system activities change. We have not experienced major scalability issues in our environment. This is useful because we can monitor the system resources and workload from the same environment as activity increases. For a larger or more complex environment, proper configuration and tuning would still be important to maintain good monitoring performance as the environment grows.

We have reached out to the BMC support team when we needed help with the product configurations. Overall, the support experience has been satisfactory. The support team was helpful in understanding the issue and guiding us through the troubleshooting process. For more complex mainframe-related issues, the resolution can sometimes require additional investigation and back-and-forth communication. However, having BMC support available is useful when the internal team needs assistance with configuration or troubleshooting.

We did not make a direct switch from another comparable solution, so I would not want to make a comparison based on assumption. BMC AMI Ops is part of our existing mainframe monitoring. We use it for performance visibility and troubleshooting.

The initial setup requires some planning around the environment and licensing requirements. I don't have the exact licensing cost available to provide. From an implementation perspective, the main effort was getting the monitoring configuration fine-tuned with our existing mainframe environment rather than basic installation itself.

We have not measured a specific financial ROI or headcount reduction from BMC AMI Ops, so I would not put an exact amount on it. The main benefit is time saved during monitoring. For example, when there is an unusual CPU or resource utilization issue, the team can use the monitoring information to quickly identify the affected area instead of spending as much time on manual investigation. The value for us is mainly in faster issue identification, more efficient troubleshooting, and better visibility into the mainframe.

The pricing and licensing are more suitable for organizations that require a base for enterprise-level mainframe.

We looked at the available options for mainframe monitoring before selecting BMC AMI Ops, comparing them based on the monitoring coverage, performance visibility, alerting, and how well they fit in our existing OS infrastructure. The main consideration was having a solution that would provide detailed system monitoring and support day-to-day troubleshooting without requiring major changes to our existing environment. BMC AMI Ops fit our operational requirements.

I would recommend first defining what you need to monitor and which mainframe resources are most important to your team. BMC AMI Ops provides a lot of monitoring information. Spending some time on the initial configuration and learning the different views will make the product much easier to use. I would also suggest starting with the key alerts and performance views that the operation team actually needs, rather than trying to configure everything. Once the team becomes comfortable with the product's monitoring features, it can become a useful part of regular monitoring. My overall review rating for BMC AMI Ops is ten out of ten.

We usually use BMC AMI Ops to automate tasks as described, and there are a couple of batch files running in the tool itself which we monitor for the health of the servers that are being assigned to the agents in BMC AMI Ops.

We can take one example of a job that is being done on BMC AMI Ops, which is a file transfer job. Before file transfer happens, there is one job called file watcher that watches the file at a specific location on the server. Once the file is received at the path, it gives commands to the next job, which is a file FTP job to transfer that file. Once successful transfer is done, it removes the source file and marks the job as completed.

The file watcher and file transfer combination is really helpful to accomplish our tasks. As an SME, we do not know when we are going to receive a file from our offshore clients, so we need to have it monitored to a certain window or time accordingly to process the further steps.

There is a job feature called Azure jobs that we were not aware of earlier. It supports cloud pipelines jobs directly integrated with BMC AMI Ops. We are under exploration of that and have experimented with the jobs to run Azure pipelines, which is almost on the verge of successful completion. It is a new feature, and there are a couple of areas we have not explored yet, but as of now, Azure pipeline is helpful.

There are three different sections in BMC AMI Ops: define mode, monitoring mode, and others. In the monitoring section, there are varieties of things to be monitored on the dashboard itself. You can customize it and get all the information on one panel, which is usually helpful because you can see everything at one glance, reducing the time and allowing you to take action accordingly.

If you are going to check all of the monitoring sections individually, it usually takes around five minutes to check one section, so it would take around fifteen minutes total. However, using it on one dashboard and checking all of the monitoring sections at once lets us save up to half an hour, compared to checking ten monitoring tasks manually.

We usually use automation in day-to-day executions. For example, we have tasks where files are delivered by offshore teams to us, and we can read the files, check for errors, and execute SQL queries to check for the desired output, confirming whether it is successful. If it is not, it presents the error indicating that it is not the desired output we expect. Automation is used daily and helps streamline our processes significantly.

Cost is monitored by the number of job executions, which helps us understand what is really required. Previously, using automation tools, we ran all jobs across all environments, such as dev, test, and production. However, after learning from IR management that we pay for every job execution, we collaborated with SMEs to rectify unnecessary executions and streamline our operations according to necessity.

BMC AMI Ops has been in use at our company for more than a year.

We were previously using CA workload automation tool before BMC AMI Ops. There were certain limitations with that tool, and we have been using BMC AMI Ops since a year or more than that. It has broader features, helps streamline our processes smoothly, and it has zero downtime while upgrading and better notification, which is really helpful for us.

Earlier we only had notifications on the failure of completions, but with BMC AMI Ops, we have a couple of features in the notification part that allow us to add the group and assign a couple of team members to that group, and it triggers the notifications accordingly. For example, if a job is getting failed or stuck somewhere during execution and takes longer than expected, it triggers the notifications. We have notification categories, such as notifying within BMC AMI Ops window and email notifications, and these features usually help us.

We have used a BMC AMI Ops AI feature called jet, which usually helps in the monitoring mode, but not in the defined mode. There are certain limitations, and with the help of AI, we can give commands or prompts to get things executed, which has been really helpful so far.

The accuracy and reliability in the monitoring mode of BMC AMI Ops are quite good.

BMC AMI Ops provides a better experience in operations. In terms of system health visibility, we can have the monitoring section in one dashboard, which is quite good and handy for reviewing all of the monitoring aspects in the system and subsystems.

It reduces the time and minimizes the chance of human error that occurs when we monitor things manually. If we correctly prompt the AI and give the right command, it executes the tasks as we want, which has usually been helpful for us.

It is really hard to say if there are any improvement areas or not, but every software has improvement areas that should be found out. As of now, I do not have anything in mind, so it would be difficult to specify. I do not have any small improvements or wishes for future updates at this time.

There are a couple of features in BMC AMI Ops, and it has plenty of features, but it is really difficult to understand as a new BMC AMI Ops user. We should go through a couple of training sessions to understand the various features available in the define mode, monitoring mode, agent mode, and all of these aspects. It is a bit difficult to track everything, but there are always certain improvement areas in software.

I have been working with BMC AMI Ops since twenty twenty four.

BMC AMI Ops is stable as of now.

BMC AMI Ops is scalable. If we encounter any limitations, we contact BMC AMI Ops support team. They provide solutions, and if they do not have one, they contact the development team to address our scaling needs.

Customer support is good, but sometimes we receive less interactive solutions, so we occasionally do not get the answers we need. We need to have a couple of conversations and often receive solutions later.

I previously used a different solution before BMC AMI Ops.

We were using CA workload automation tool and I previously shared certain limitations of that tool which was on premises and caused larger downtimes during upgrades. In contrast, BMC AMI Ops is cloud-based and helps us integrate wherever we want in the cloud, which is significantly helpful.

BMC AMI Ops has plenty of features, but it is really difficult to understand as a new BMC AMI Ops user. We should go through a couple of training sessions to understand the various features available in the define mode, monitoring mode, agent mode, and all of these aspects. It is a bit difficult to track everything, but there are always certain improvement areas in software.

It is quite helpful, and I would suggest others use BMC AMI Ops. Use all the features carefully because it has a large amount of functionalities that can help ease tasks and enable error-free execution of automations.

BMC AMI Ops is quite good, and while we have used the tool so far, I can suggest others use it to automate tasks. I would rate this solution an eight overall.

My main use case for BMC AMI Ops is monitoring my systems with the proper health checkup to ensure everything is up and running. Apart from this, we have a lot of service request monitoring and KPI monitoring for our customers. Being in the telecom sector, monitoring is a priority for us, so we use this tool as a monitoring solution.

One specific example of how I use BMC AMI Ops for monitoring occurred when we noticed that a production batch job is taking longer than expected. With this BMC tool, we monitored the system, the job, and the resource-related parameters while the job was running. We checked the CPU, memory health, job status, and the trends of when it got completed and when it was long-running. I also checked any resource consumption during that time.

The main use case remains day-to-day production monitoring of the mainframe environment, focusing on health checkups, job resource utilization, alerts, and important systems that need monitoring. We work in shifts, maintaining vigilance over alerts on a single dashboard, rather than logging databases. If any anomaly occurs, it triggers an alert based on conditions we have integrated, which is how we use it in our daily operations.

BMC AMI Ops provides real-time monitoring, including alert and event management, allowing for quick investigation of system conditions. This real-time capability is incredibly useful as it helps ensure our production is up and running, quickly identifying resource consumption issues. Even non-technical staff can check on system conditions through one dashboard rather than logging into servers and reviewing logs. If the system reboots, we can identify what is happening, which aids in reducing downtime.

The alert event management feature is quick in helping identify issues, thanks to predefined thresholds we have in the system. For example, if CPU usage exceeds 80%, it triggers an alert. This helps us check system health promptly, and if an issue arises, we take corrective action. We assess the severity of alerts and investigate the issues based on job information and current status to understand the impact and root causes.

Additionally, I want to mention the feature of drilling down into system-level issues, which aids in checking historical data. If a job fails, we can compare its current status with previous trends to see how it is running now. While analyzing this, we can also perform automation — for example, if an event is triggered, we can automatically kill processes that consume unnecessary resources.

I want to see improvements primarily around user experience and ease of troubleshooting for complex issues with multiple alerts. Having a more consolidated view related to event jobs and system resources would be beneficial. Additionally, more intelligent alert correlation would be useful to connect alerts occurring simultaneously. I also believe that incorporating AI integrations would help significantly, facilitating quicker identification of issues.

For operational purposes, I see several areas for further improvement. First, enhancing automation around operational tasks can reduce manual intervention and enable teams to respond faster. Secondly, allowing for dashboard customization can improve investigations by providing distinct dashboards for different teams with tailored metrics, fostering flexibility and ease of use for the end users.

I have been using BMC AMI Ops for my day-to-day operations for the last two years.

I have not experienced downtime or reliability issues with BMC AMI Ops; I have not seen any signs of problems on the BMC side for the entire time I have been using it.

While BMC AMI Ops handles workloads effectively, it struggles under very high workloads, occasionally providing inaccurate information, suggesting that this is an area for improvement.

I have had an excellent experience with BMC AMI Ops customer support, easily rating them ten out of ten. They respond quickly when I need assistance with features or tools.

I saw BMC AMI Ops being used in the production environment when I joined, but in comparison to other tools like Grafana, BMC offers more comprehensive features. The advent of AI offers unique capabilities that were lacking in other solutions.

Using BMC AMI Ops has led to operational time savings as it automates monitoring efforts, decreasing the need for manual processes and allowing the team to operate with fewer staff members, streamlining our operations.

I evaluated Grafana before choosing BMC AMI Ops, but I found Grafana had limitations that made setup and implementation more cumbersome compared to BMC's more straightforward production monitoring setup.

My advice for those considering BMC AMI Ops is to recognize it as a leading monitoring solution compared to others. Implementing it carefully, particularly regarding alerts, automation, and integrations, is crucial for effective performance. I rate this product overall as an eight out of ten.

My main use case for BMC AMI Ops is to monitor the health and performance of our maintenance to keep the system running optimally. It helps us detect issues, monitor system resources, and ensure critical business applications run smoothly.

I can provide a specific example of how I have used BMC AMI Ops in my day-to-day work. Recently, we noticed CPU utilization was much higher than normal during peak business hours. Because of BMC AMI Ops, we received an immediate alert and identified that our workload was utilizing maximum CPU. We resolved the issue before any users were impacted.

To monitor everything effectively, I need to keep an eye on my CPU and any utilization patterns.

BMC AMI Ops offers excellent features including real-time monitoring, performance dashboard, and intelligent alerts, plus the automation capabilities we are using. It is easily accessible with visibility across multiple systems.

I rely most heavily on the performance dashboard and real-time monitoring. The real-time monitoring and alerts keep us informed about problems immediately rather than waiting for users to report issues.

BMC AMI Ops has impacted my organization very positively, primarily in terms of timing. Our manpower previously was required to investigate issues, which took considerable time just to identify the problem. Now we identify issues very early and solve them immediately.

The positive outcomes include mainly reduced downtime and improved efficiency of our manpower. Earlier, when users reported high-priority issues, we had to spend extensive time investigating, resulting in system downtime. Now everything is much easier with BMC AMI Ops.

Regarding BMC AMI Ops's AI capabilities, I believe its governance and security are very strong. We are currently handling almost eighty percent of our projects with it, and it is very stable with enterprise-level performance, including strong role-based access and monitoring capability.

BMC AMI Ops is very reliable. The monitoring data is accurate, and the alerts are very specific and timely.

BMC AMI Ops can be improved by offering a more modern user interface and better dashboard customization. While we can customize the current interface, it could be more robust. Additionally, more cloud integration is necessary.

I have been using BMC AMI Ops for the last year.

BMC AMI Ops is very stable.

Its scalability is very strong. Currently, we are using it for one to three systems, and it remains very stable and scalable.

The customer support is very good. Previously, we faced an issue and contacted the team, and they were very helpful.

I see a return on investment based on time. It reduces time requirements by almost fifty to sixty percent.

My experience with pricing, setup cost, and licensing is that the pricing is quite reasonable, making it accessible for new firms looking to get started with it.

I would rate my experience with using BMC AMI Ops for monitoring the health of my whole system as very effective, providing a unified view across all mainframe systems. This allows us to detect issues faster and more accurately, thus reducing the time spent by manpower trying to find problems while shifting between different monitoring tools.

We are using the observability and AIOps-driven early detection feature in BMC AMI Ops, which helps us detect any abnormal activities in the integrated systems, and it is very helpful.

We have not yet used the integrated monitoring, automation, and OpenTelemetry features in BMC AMI Ops.

In my experience, BMC AMI Ops has helped improve mean time to detection. I can provide a recent example. Earlier, it took considerable time to identify errors, but during peak business hours, we faced an issue with CPU usage that was blocking somewhere. We managed to solve it without any downtime or affecting users.

We have not tested any other tools.

We have not evaluated any other options before choosing BMC AMI Ops.

My advice for others considering BMC AMI Ops is that if you are a new startup looking for data security and securing your CPUs to gain visibility, this tool is very reliable and worth implementing.

I would rate my overall experience with BMC AMI Ops as a nine out of ten.

BMC AMI Ops serves as our primary alert monitoring tool for the mainframe server for all the consoles, connecting all the consoles together. It helps us identify all the issues running on our server, sends us alerts, and provides automated alerts, making it very helpful for us to find out the issues running on the server without any delay.

We have eight LPARs in our system and we have automated all of them with the help of BMC AMI Ops. If there is any job failure in any of the environments, this tool catches that and sends it to Splunk, then it forwards to our ITSM tool, creating an incident and sending us alerts directly to our email box, allowing us to react very quickly without any delay.

Generally, we are using BMC AMI Ops as a monitoring tool. I am also doing administration work for this tool, providing access, creating all the consoles, and establishing all the connections with the mainframe to the MainView.

BMC AMI Ops offers us accurate and timely monitoring of our servers.

In our multiple environments, it is not possible for us to monitor all the LPARs at the same time on a single screen, so BMC AMI Ops helps to automate. If any alert comes on any of the servers, it sends us the alert, which is very useful and allows us to avoid continuously watching all the servers.

BMC AMI Ops has positively impacted our organization by allowing us to respond to alerts on time, as previously we were unable to work on all alerts in time and would miss many alerts due to multiple servers, leading to SLA breaches. After using this tool, we get all the issues in a timely manner and are able to act on them promptly.

Currently, I am working on the upgradation part of BMC AMI Ops, having received new updates in the past few months. I find it useful, as I have seen changes in the GUI structure and multiple features have been added. I am still exploring its functionalities; earlier, we had many security policies to navigate, but those have improved in this newer version.

Currently, for the automation part, while BMC AMI Ops helps alert us when issues arise, we are also using Splunk as an additional tool for automation. Any alerts from MainView get sent to Splunk, which then sends them to ITSM. A feature that allows alerts to come directly from MainView to ITSM would be extremely beneficial.

I have been using BMC AMI Ops for approximately four years.

BMC AMI Ops is stable, and it works well.

BMC AMI Ops' scalability allows us to connect multiple servers to MainView Ops; we currently have eight and plan to add more, finding no performance issues, and adding more space is easily manageable.

BMC customer support for AMI Ops is responsive; whenever we encounter an issue, we simply email BMC support and open a case, and they assist us based on our needs.

Previously, we only relied on TN3270 consoles, requiring constant human monitoring without automation. We switched to BMC AMI Ops because it offers more automation, which aids in issue detection, thus providing more flexibility and efficiency.

We initially required a larger team to monitor multiple servers, but with BMC AMI Ops, we have reduced our team size due to its automation capabilities. It saves us time as our alerts are handled automatically, allowing us to respond promptly and avoid SLA breaches as we no longer miss alerts.

Pricing, setup costs, and licensing decisions are managed by our management team, so I am not directly involved and do not have detailed knowledge about those aspects.

Before choosing BMC AMI Ops, we evaluated mainframe automation options that utilized JCL and COBOL. While those options were tricky and time-consuming, BMC AMI Ops presents a GUI-based solution without such limitations, making it much easier to use.

Regarding the AI capabilities of BMC AMI Ops, since we use it only within our internal organization and do not provide access outside, we have not faced security issues. However, companies interacting with the outside world need to be careful about maintaining server certificates to prevent data theft.

When it comes to accuracy and reliability in output, BMC AMI Ops works very well; any issues, misses, or glitches are easily identified.

BMC AMI Ops provides a unified operations experience that is very helpful for gaining visibility into the system health across mainframe systems and subsystems, giving us an easy way to check system health and utilization from a centralized dashboard.

I am not certain if I am using the AIOps-driven early detection feature specifically; we are in the process of upgrading to a new version, so I am not familiar with all terms. However, we use AIOps detection to monitor the servers to identify any issues.

BMC AMI Ops monitoring assists the TOC monitoring team in overseeing the system, while the automation feature is very useful for managing alerts according to our established protocols; we use CCS servers and automation viewer consoles effectively.

Regarding MSU consumption, the data is generated by the storage team where they run jobs; we do not utilize BMC AMI Ops for this specific feature. Consumption metrics are sourced directly from our TSO mainframe sessions.

When the TOC needs to monitor all servers, they utilize OpenTelemetry integration, which helps them get expected outputs regarding alerts and server issues, providing visibility into what is running correctly or incorrectly.

For organizations with multiple servers facing monitoring challenges and alert misses, I recommend BMC AMI Ops as it would be useful for identifying issues and resolving them in a timely manner without requiring a large team.

BMC AMI Ops is very useful for us now due to our heavy workload and multiple servers; it effectively addresses our challenges. I would rate this product a nine out of ten.

I have been using BMC AMI Ops for one and a half years.

My main use case for BMC AMI Ops is mostly for automation, specifically different kinds of job automation. Depending on the conditions that match, there are scripts that need to be run. With the help of this tool, we run multiple scripts when the conditions are satisfied.

An example of how I use BMC AMI Ops for automation is that my job is not focused on scheduling or creating any job. My job is very limited to rerunning, restarting, and troubleshooting jobs. Although I have never automated any job, I have exposure to automating a small job. For instance, if the conditions are satisfied, we need to run a particular script, and there, we can use BMC AMI Ops.

I don't have anything else to add about my main use case or any other ways BMC AMI Ops helps me in my role because my role is very limited.

Regarding BMC AMI Ops's AI capabilities, I haven't used the AI feature extensively. However, I was impressed by what I saw at a BMC roadshow concerning how the AI works. I don't have much interaction with BMC AI so far, so I can't comment much on that.

Since I don't have much interaction with the AI in my day-to-day work with BMC AMI Ops, I prefer not to comment on its accuracy and reliability of output.

In my opinion, the best features BMC AMI Ops offers are all the features, as I like them overall. The most important feature is when there is a job that is waiting for some input or prerequisite. We don't have to dig manually a lot; we can just click an option on the job page to find out why the job is waiting, what it is waiting for, and what the prerequisites are.

I use that feature to check job prerequisites or troubleshoot issues quite often, and it does save me a lot of time compared to manual digging. If that feature is not there, I will have to check the neighbors, the successor job, the predecessor jobs, and then check each job and the entire flow. Instead of all that digging, I can simply click on that particular option to get the exact answer I need, regarding why the job is waiting and what needs to be done.

Another feature I rely on often is the viewpoint feature, where we can apply multiple filters and generate reports about various jobs, such as specific folders, applications, sub-applications, and sub-folders. These filters help us get the exact results we want on our dashboard, allowing us to manage the jobs that require our focus. The viewpoint feature is very important.

BMC AMI Ops has positively impacted my organization in multiple ways, especially in automation, as we do not have to manually run or search for or run scripts. When the conditions match, we can simply schedule the jobs, and it will run that script automatically. Without this feature, we would have to keep human resources available to monitor jobs 24/7, matching conditions and running scripts. This automation has helped us significantly.

I can't say how BMC AMI Ops can be improved because my role is very limited, and I have not explored the entire tool in my organization yet, so I can't comment on that.

Regarding needed improvements, by default, when we open a viewpoint, we don't see the jobs in a linear way. If all jobs could be displayed in the correct flow by default, it would be better. For example, Job 1 should run first, then Job 2, and so on. Sometimes, I find Job 1 somewhere down, Job 3 somewhere up, and Job 4 somewhere else. The jobs should be arranged sequentially by default; this could be improved.

BMC AMI Ops is very stable. Whenever there is maintenance work, the tools admin takes good care of it, so there is not much impact on downtimes. Therefore, I would say it's a very stable tool.

Regarding the scalability of BMC AMI Ops, I can say that it is scalable. My organization is a bank, and at the end of every month, some delays occur in the jobs due to a lack of CPU resources. The company is not ready to increase CPU capacity because only at the end of the month are those resources in high demand. I have not worked on scalability much as I'm only responsible for the jobs, but I see the tools admin doing some work behind the scenes to manage resources when more jobs need to be run.

I can't share specific metrics about return on investment, as I'm not the correct person for this query. However, I can say that after deploying this tool, we have saved costs and reduced the need for employees, leading to less manual work.

My advice for others looking into using BMC AMI Ops is to get certified from BMC while using this product. It will really make your life easy and help your organization, especially in the banking and BFSI sectors. Since I am BMC certified, I emphasize the importance of getting good training to effectively use this tool in day-to-day operations. I give this review a rating of 8 out of 10.

BMC AMI Ops is primarily used for IBM systems to detect soft failures and alert when anything goes wrong in the system.

BMC AMI Ops is configured to flag when CPU threshold goes above 90%, which flags multiple such patterns and allows us to avoid outages many hours before they actually occur.

BMC AMI Ops is deployed across multiple systems, including IBM z/OS, IBM DB2, and other mainframe systems. It has been deployed centrally, enabling monitoring of multiple machines and performing auto-remediation if something goes down.

The best feature of BMC AMI Ops is its AI/ML-based correlation, which creates alerts that help improve MTTR and can work in complex environments. The closed-loop automation is also very useful.

The AI/ML-based correlation makes the biggest difference for my team because it is useful due to the complexities involved in events coming from different sources and applications, including IBM z/OS and DB2. This helps us quickly troubleshoot environments and avoid outages proactively.

Other features of BMC AMI Ops that stand out include capacity optimization, which allows us to review the capacity of our systems, and auto-ticketing within ITSM systems that integrate with ServiceNow and BMC Helix.

BMC AMI Ops has positively impacted our organization in numerous ways. We deploy it for our customers, allowing us to deliver services in a timely manner, improve our SLAs, and enhance our overall customer experience.

The AI capabilities of BMC AMI Ops can be improved, along with the performance, look and feel, and the user interface, which still appears to be on the legacy side.

BMC AMI Ops has a longer learning curve, so a simplified experience for those configuring and using the platform would help. Improved documentation and more training and enablement from BMC would also be beneficial.

Regarding BMC AMI Ops's AI capabilities, governance and security are improving, but there is still significant work needed to raise the AI guardrails, as a substantial amount of data is at stake for our customers, and we do not want the AI to malfunction.

When considering BMC AMI Ops's AI capabilities, it is important to note that it is not a true AI, but a machine learning-based model that includes features like automated baselining and machine learning-based correlation.

I have been using BMC AMI Ops for around ten years.

BMC AMI Ops is stable.

BMC AMI Ops has a very scalable architecture.

We struggle with customer support due to a lack of expertise, but it can be improved. I would rate customer support as a three out of ten.

Before choosing BMC AMI Ops, we evaluated other options, notably the IBM native capabilities. However, we decided that BMC AMI Ops was better for various reasons and went ahead with it.

We have seen a return on investment, improving productivity by five percent year-on-year.

My experience with BMC AMI Ops pricing, setup cost, and licensing is that it is always expensive. Our customers constantly look for alternate options because BMC AMI Ops is a very costly product.

We have utilized the AIOps-powered detection in our mainframe operations, which has been effective in highlighting issues that matter and helps us improve our SLAs and customer experience.

BMC AMI Ops is a great product, but it comes with a huge price tag. Companies should develop their own delivery and support capabilities, as finding those from BMC is challenging.

We are using the observability and AIOps-driven early detection feature in BMC AMI Ops, which has helped us improve proactive resolution way before outages actually occur, enabling us to detect issues.

I have utilized the integrated monitoring, automation, and OpenTelemetry features in BMC AMI Ops, which have greatly improved our incident response consistency. We have been using these features for eight years, and they help us improve our MTTR for our customers.

Visibility into cost and capacity awareness due to BMC AMI Ops's capacity optimization capabilities gives us a real-time view of the underlying capacity, informing our decisions regarding mainframe usage and MSU consumption.

I have used the expanded GenAI assistance feature in BMC AMI Ops UX. It is at a very experimental and early stage, and while we have not completely utilized it, I find it very helpful from what we have seen.

I would rate this product an eight out of ten overall.

The automation capabilities have reduced the majority of the work that our team used to do manually, as manual processes consume a lot of time and are prone to human error. When it comes to automation, we see the performance has been raised, and clients are also satisfied with the performance. We do not have much downtime or any critical issues that are highlighted which impact the business. Automation has really changed and is a game changer for us.

BMC AMI Ops has had a major impact because we are using it for one of our major clients. The alerting system gives us precise alerts, and based on that we try to fix issues before they lead to a business impact. The client is happy when there is no business impact, which is a really positive thing. The improvements we have seen include a reduction in the FTEs or headcount needed for operations work because of automation, and that has really helped us for cost savings.

The monitoring and integrated monitoring and automation system have improved incident response by providing us with a unified view of the health system and data across the environment. It helps us with real-time monitoring and automated alerts, enabling early detection for the team to effortlessly fix issues before they escalate. Manual efforts have been reduced, allowing us to respond to incidents consistently.

Overall, I find it is well designed, but only two points less because, as I mentioned, a few false alerts still require our resources to investigate other issues, and the graphical representations, UIs, reports, and other aspects need some improvements, indicating a scope for improvement. Graphical representation helps us with better analysis for our business analysts, so that would be an improvement.

I use BMC AMI Ops to maintain its usability for the main team so that the main team can use the product to install it for various clients. BMC AMI Ops is a product that is given to us by a vendor, and we run a couple of jobs called JCL, which is a language in mainframes. Mainframes are a really old kind of technology. In mainframes, we use all these vendor products to help our clients manage their own system.

BMC AMI Ops offers an analysis of the mainframe system. It has automation, AI features, and can keep track of storage, providing a whole analysis of the mainframe system.

I prefer automation the most out of automation, AI features, and storage tracking. I think AI is only going to get bigger as we evolve with technology, and AI is only going to help us grow.

BMC AMI Ops has improved outcomes for my team, and it has definitely improved outcomes for the clients that we serve. The real reason we maintain these products is for our clients.

The client was able to use BMC AMI Ops to track their usage of the system. The client was able to automate a lot of the processes in their system, and that helped them.

I would like to see more AI in BMC AMI Ops, such as an AI feature that lets you keep track of storage in some way, perhaps some kind of automatic disk cleanup.

I have been working here since January of 2026. It has been about a month since I started using BMC AMI Ops.

BMC AMI Ops customer support is pretty good, but I have not had any experience with it. I would rate the customer support of BMC AMI Ops an eight on a scale of one to ten.

I am not aware if we previously used a different solution because I actually just started this January of 2026.

I do not deal with the pricing, setup cost, and licensing for BMC AMI Ops. I am not a salesperson.

The implementation team is something that the client chooses regarding BMC AMI Ops. If the client wants a specific software vendor package, we give it to them.

I would not know if there has been a return on investment because I am not a sales person.

I do not deal with the pricing, setup cost, and licensing for BMC AMI Ops. I am not a salesperson.

I am not aware if we previously used a different solution because I actually just started this January of 2026.

I would not really know how BMC AMI Ops's observability and AI Ops-driven early detection feature has helped in identifying abnormal behavior early because I think the main team really uses the features. I am just aware of the features.

Only the main team would know the real usage of the integrated monitoring, automation, and open telemetry features in BMC AMI Ops. I only know the features.

I assume BMC AMI Ops has helped in improving mean time to detection, MTTD because the main team usually says that it was implemented well.

I do not really know other companies and how they use BMC AMI Ops, but I am sure it is a great product.

I liked this interview because I got to see how AI works. I would appreciate a short poem or haiku that will summarize my review. My overall review rating for BMC AMI Ops is eight.

My main use case for BMC AMI Ops is for monitoring and small adjustments in the mainframe environment, where I use the tool to monitor the status and health, the depth of MQ queues, and to enable and disable transactions in CICS, among other things. I have created several screens and views that are very interesting and important for monitoring the health of the mainframe environment as a whole.

The best features that BMC AMI Ops offers, in my opinion, are the ability to issue commands in several CICS at the same time and the ability to create views and screens that reflect the performance and general state of the systems and their applications in the environment as a whole. When I have a Sysplex with several CICS, sometimes dozens of CICS, and I need to stop a transaction or start a connection, through BMC AMI Ops I can do this with a single command on one screen, instead of opening CICS by CICS to issue the command inside each one. Issuing commands on several systems at the same time makes day-to-day work much easier because it saves many minutes every time I have to issue a command in more than one CICS at the same time.

BMC AMI Ops has had a positive impact on my organization because the ability to create views and screens, where I bring together applications and their functions on a single screen, makes monitoring and spotting possible problems that are happening much easier. Thus, my response is much faster and more proactive. By looking at the screens and views, I get a real-time notion of whether a queue is filling up too quickly in MQ or if there are transactions in a CICS that should be active but are not, all of which is reflected in the user experience. If the application is down for a long time, the user is impacted.

Regarding BMC AMI Ops, I appreciate the way it is today; since I am a mainframe professional, I appreciate its style and layout. However, I understand that newer generations might prefer a layout more similar to a web page in appearance. I think the only thing I would like to add is that new users may feel intimidated by the black MainView screen on the mainframe. If it were possible to have a more user-friendly and more up-to-date layout, perhaps people would find it easier to accept using BMC AMI Ops.

I give it a nine because the tool is very complete and very good, but I think it could be a bit more explanatory when I need to create new views and screens; there is some documentation missing. I have documentation, but it is in a language that is not very intuitive.

I have been using BMC AMI Ops for six years.

BMC AMI Ops is quite stable.

The scalability of BMC AMI Ops is not an area I am involved in, but I hear from the people who are involved that it has good scalability.

Regarding BMC AMI Ops customer support, this is also not an area I get involved in; this part usually stays with my support team.

When I joined this company, BMC was already installed, but I know that before they used Omegamon.

BMC AMI Ops is deployed locally in my organization.

I have not used the built-in automation and OpenTelemetry features in BMC AMI Ops yet, as that part is handled by another part of my team.

I have not obtained data on return on investment since, as a member of the production team, I do not have data on values and finances; however, I believe that using BMC AMI Ops makes day-to-day production much easier.

My experience with pricing, setup costs, and licensing is not an area I am part of.

I do use the observability and early detection features with AIOps in BMC AMI Ops, and this is the main reason I use BMC AMI Ops in my environment. Through the views and screens I create, I monitor various system elements on a single screen. It is possible to create thresholds and other alarms when parameters are not within what is acceptable for production, making it very easy to identify and try to act on the root of that problem.

Regarding cost and capacity visibility, this is not an area where I, as a production analyst, have access to the cost issue. However, I believe that BMC AMI Ops has proven to be interesting, so much so that the company has continued using it for many years.

My advice to others who are thinking about using BMC AMI Ops is that it is worth investing in BMC AMI Ops; it is a complete, good tool, not difficult to configure and use, and it helps a lot. I have given this review a rating of nine out of ten.