Share your experience using OPS/MVS Automation Intelligence

We use the auto-purge transaction for some transactions that run very long, and we also use automation to open and close files in CICS as well.

I use OPS_MVS Automation Intelligence mostly for message triggering for alert and alarm, but that is a normal feature that automation systems should do. It works well in alerting, but that is the basic function of automation tools. Everyone in the market can do that, so I don't have much impression of the tool; it is just a normal tool, in my opinion.

My impressions on OPS_MVS Automation Intelligence is that it's quite difficult to use, as it relies mainly on the coding syntax and doesn't provide an easy-to-use GUI. OPS_MVS should have an easy-to-use menu, as the way to create the script is quite difficult, and they should improve this.

I just joined the team about two years ago, but they have used OPS_MVS Automation Intelligence for quite some time, maybe five years.

My team built the customized automation scripts by ourselves, and sometimes we have vendors to help us also, but we never asked the CA team to help us.

For automation products, I used to use IBM System Automation a long time ago, and also MainView Automation, and Control-O. I prefer MainView the most, either MainView Automation or Control-O, as it is very easy to use, while I think IBM System Automation is quite similar to OPS_MVS Automation Intelligence because it relies heavily on the syntax and coding rather than the GUI.

OPS_MVS Automation Intelligence is the automation tool I use. I think OPS_MVS Automation Intelligence is good for creating complex rules because it's coding, but it takes time to learn how to use it. OPS_MVS Automation Intelligence works well if you know the syntax very well and you have experience in creating scripts or REXX syntax; it would be very good and is a good tool, but it takes time to learn, so that is for experienced staff to work with. I would rate the product a six from one to ten. I cannot think of any additional features in the next release of OPS_MVS Automation Intelligence.

We are customers of ServiceNow IT Operations Management, using it for the ticketing systems and user management and change management. Change management and user management are the major use cases for us with ServiceNow IT Operations Management.

We quite rarely use the configuration management part of ServiceNow IT Operations Management, but we sometimes have to. User management and change management are continuously required, and we have to generate tasks for those, but the configuration management part is used quite rarely.

The main and best thing about ServiceNow IT Operations Management is that it helps to organize user management tickets in an organized form. You don't have to go after the work, and you can always see the process where you are and the tasks you have to do on a special day. It's an organized way of managing your own work, especially when it comes to changes. I used Service Manager at my previous employer, but ServiceNow IT Operations Management is much better than that.

The predictive AIOps capability helps to maintain service availability for us with ServiceNow IT Operations Management.

It's a kind of organized way that gives us a schedule to organize our work with ServiceNow IT Operations Management. I can't really tell you an example since I'm so used to it that I can't imagine how we would organize our work in another way, and I appreciate it very much.

We use the centralized dashboard in ServiceNow IT Operations Management.

When it comes to the dashboard of ServiceNow IT Operations Management, I appreciate that I can see everything on the same page. I can organize the most important things, and in my case, change management and user management are the most important. On the dashboard, I can keep these two at the top of the screen and always see new changes or tickets that indicate my intervention, and that's what I really appreciate about the dashboard. We don't have too many incidents in our system, so I focus mainly on new tickets that require my attention, and the dashboard helps me see what to do.

We don't use the orchestration part of ServiceNow IT Operations Management here.

The CMDB part of ServiceNow IT Operations Management is a little bit too complicated, and it is a bit slow at our company. Sometimes, especially when it comes to user management and audits, we need detailed lists about changes and user management from ServiceNow IT Operations Management, and that can take a lot of time. That is the only issue I can list about ServiceNow IT Operations Management.

I have been working here for five years, and this company has used ServiceNow IT Operations Management for quite a long time, more than 10 years.

The technical support for ServiceNow IT Operations Management is good at our company.

Negative

I used Service Manager at my previous employer, but ServiceNow IT Operations Management is much better than that.

I work with ServiceNow IT Operations Management.

I don't really use the real-time analytics aspects of ServiceNow IT Operations Management, but my boss utilizes that part for lists and analytics, especially regarding work and ticket numbers. It is useful mainly for our management.

I am a SWIFT administrator in the company.

I would rate ServiceNow IT Operations Management an eight.