The stability has been very good.

The downside is that when something does go wrong, most times it's a networking issue, which tends to get lost in the mix. OpCon will say, "Unable to communicate," and now we have to try and track which part of it has failed. Is it the agent that has failed? Is it the Enterprise Manager that has failed? Is it the network backbone that has failed? Or is it the SQL Server that has failed? A way in which OpCon could be improved is to better analyze things when a failure is occurring to point us in a better direction without our having to check all the different paths.

We didn't have any problems for the first few weeks. When we got to a big volume of jobs, we started to have some response delay. We called SMA's French support and U.S. support to analyze our problem. SMA's solution was that there was a difficulty with the large history. We hadn't deleted and had too many days in history. We had to purge some history and close some days. Today, we do that regularly and it's okay for us now. We have a good response time from the product.

I would rate the stability high, with our situation. They've got a lot of baked-in support with Symitar and they're very much a VIP partner in how we run our business.

In terms of reliability, it has performed exceptionally well. Rarely do we encounter issues—perhaps once or twice in a calendar year, and these are often minor and resolved with a simple reboot.

The stability is amazing. Because everything is on-prem, we control the network environment from OpCon to other servers within our networking environment. As far as the product goes, there has only been one time in the 11 years that we've been using it when the product has gone down. It was due to our networking going down, so it wasn't even the product. It was an internal issue.

Deployment and maintenance really only needs one person. OpCon is that user-friendly. With the right support, one person should be able to build, maintain, and administrate it. This is actually my primary role.

I haven't experienced any issues with stability.

We haven't had any issues with its stability or performance. It has been perfectly stable so far.

The software remains stable, effectively monitors servers, and executes jobs, and I can't recall the last instance of it encountering any significant issues. It's highly stable and reliable for the range of tasks it handles. Considering the volume of processes we run each month, the occurrences of failures or issues requiring attention are typically job-based or related to user errors from other departments. I would rate it ten out of ten.

I would rate the stability of OpCon ten out of ten.

They've gone through some changes recently with the owner, but I know that they're on the right track. I feel that they're very stable.

Thus far we have only had a few minor problems, all of which the vendor addressed quickly. We have not encountered any major problems. The product is very stable and reliable.

OpCon has been completely stable.

The stability is near perfect. I won't say it is perfect, but I've never had a database error (knock on wood), corruption, or system loss that wasn't due to something else, like a power failure. The software has always operated. It always returns appropriate messages. It's very reliable.

The director of IT and a data center analyst are the ones who manage it overall. We write the jobs. We do the initial QA, essentially maintaining the system directly.

We only have it running in a single instance, but they do support a failover cluster. It is supported to run in a high-availability mode. I wouldn't see any problems with the application's stability. We've never had issues. We run it on a virtual machine.

OpCon is stable. We've only had issues with problems we probably should've known how to prevent, so the solution itself is stable.

The stability, on a scale of one to 10, is about a seven. We are having some issues with logs. We did reach out to OpCon, but they didn't have a solution for that, so we're having to manually handle that on a daily basis. That was a little disappointing. I'm hoping that one day they will have a list-serve where we can reach out to other OpCon shops. That way, we can reach out to other OpCon users who have a high level of OpCon skills and say, "Hey, we ran into this problem. How did you guys figure your way out of it?"

The stability is fantastic. It's 100 percent. We've never had a problem with the product from day one.

Very rarely do we experience anything that would make me question OpCon's stability. 

OpCon is a very stable enterprise. We have had very few downtime issues.

It's rock solid. We've never had any issues with it.

There are four of us who do the deployment and maintenance of the system, but that is not full-time. We work on all the systems.

We are planning on upgrading to version 19 in January.

It has been a very solid system for us. We really haven't experienced a long period of downtime. And when there were issues, SMA support was able to come in and resolve them immediately.

There hasn't been a problem with the whole system, but there were certain releases that created problems. We got a temporary workaround from SMA. But it was nothing major or something that kept us down or made us divert to manual processing.

The stability is good. The only time we've ever had an issue was simply due to internal system issues. For example, we recently had something where our SQL Server had connection issue.  All systems were down. I've never (knock on wood) had an issue with any of the agents or application itself. 

Stability has been great over the years. We had a bit of a hiccup this last year with it. We are still trying to work through that. Prior to the latest release, it was great. We didn't have any problems with it. We have had a little issue going on now that we need to handle.

My boss and a couple other people are involved in OpCon's administration. We have a couple other employees who work with it too. 

It's extremely stable.

OpCon is really reliable. We take a lot of value from OpCon. It has improved our everyday jobs by a lot.

There are two people needed for OpCon's maintenance because we want a full backup when one of us is not in the office.

Stability is an area for improvement. We just went to the new release. You have an agent that runs on the MCP, and you have an agent that runs on each Windows environment. You have SAM which is the manager of all of them, and it has to communicate with all of them.

There are FTP agents that run on the MCP and they are there so that we can transfer a file from the MCP to the Windows environment or vice versa. Sometimes, and nobody has been able to figure out why, it just goes down, and all of my jobs that need it are hanging or failing. It happens about once a week. They have not been able to resolve whatever the problem is. If we see that the job failed, we have to restart it. If it happens in the middle of the night, we're not going to know about it until the next morning. It would be very helpful if they could figure out what in the world is happening with that FTP client that's on the MCP.

Also, every now and again, the schedule builder, which builds out your schedule for the next day or however many days you're building it out for, fails. It has something to do with our virus protection. Because their customer service is so good, we're working with them and trying to figure out what the actual problem is, to get a resolution to that. They know about it and have been trying to figure it out, but it's been years and it's just one of those difficult things to troubleshoot.

We've never had an issue with the stability of the platform. For example the platform/server itself has never been the point of failure. The only issues we've experienced is when the in-house human created configurations were done with errors. Even when errors are identified, the system produces an error output that helps determine the point of failure, so it can be resolved. 

The stability has been very good.

The stability of this solution is awesome. It's the only product I've ever seen that you can actually build to fix itself if it has a problem. You'll build something and, if you find an issue, you can say, "Hey, if this happens again, do this to correct it."

It is very stable. It is rarely offline or not functioning because of some internal error. This happens once in a great while, so I would call it very stable.

It can be deployed and maintained by as little as one person or a fraction of an FTE. It's not a full-time job taking care of it, not at the scale of our company.

If you set your schedule right, you do not have to think about it until a failure occurs. The stability is good. The failure occurs mostly because the file that is being expected is not yet ready from the Core side or from the vendor side. 

The stability of OpCon is 100% stable.

In the time that I've worked on it, I've had one problem where the transaction log locked up. That was seven years ago. It was a while ago. It's solid. You have to do your due diligence with your typical maintenance and paying attention to things, but it's a solid product.

The stability is really good. It stays up. It is functional 99.9 percent of the time. Usually if there is an issue, it's on the server back-end or the SQL database.

OpCon requires three people for deployment and maintenance.

The solution is very stable. We have had no outages that I recall.

Overall the stability has been great.

We've had a few issues but they're not because the system isn't stable. They have been more a case of known issues, but, until something broke, we weren't notified that we should fix things. That was a little frustrating. They knew it was happening, but they didn't tell us, "Hey, this is happening. You should do this before it breaks."

One issue had to do with pulling a file, because you can't use wildcards for file names all the time. SMA had a different FTP solution that they gave us, one that one of their programmers wrote. We're using it, but it's outside of the core OpCon system. Since we got it, things have been good. It just would have been nice if we could have done it all within OpCon instead of having to have a separate process.

It is a very stable product.

The stability is very good. We don't ever seem to have any issues or major problems with OpCon. It's always been quite good.

We have currently been looking to upgrade to version 19. So, we are testing that.

The stability is excellent.

The solution is not that stable, so I would rate it a four out of ten.

OpCon has been rock-solid. It works day in and day out and is very robust. It runs on Windows Servers, but it is a very high-availability, robust scheduler automation engine.

In two years, we've had one OpCon database issue that woke people up overnight. It halted production and SMA had a fix for it pretty quickly. That's one time in two years.

The stability is really good.

OpCon has been incredibly stable. We haven't had any issues with the core OpCon system. It has not died.

OpCon is relatively stable once running. We will give it credit there where it is due. 

It is very stable. They have a great foundation. 

However, to increase stability, they will need to create more online learning. So, somebody who lives in San Antonio (in my case) doesn't have to drive to Houston.

OpCon takes six individuals to operate and maintain it.

The stability gets better all the time. Where we've had problems with stability, it's been partly our fault. We run it on a VMware server but we haven't recognized that the workload has increased and haven't increased the capacity of the server it's running on. It's because of things like that that OpCon has had the odd issue. But in general, the product in and of itself is pretty reliable.

It's a very stable product.

The only time we have to be careful of is if we have an extended power outage. We've learned that we have to bring our SQL database server up before we bring OpCon online. That's true for several other systems that we run. But otherwise, OpCon tends to work as expected.

It's a stable solution.

We require one person and a backup for deploying and maintaining the solution.

The stability of OpCon as a solution is excellent. We never have any issues with its stability.

The solution is very stable. I haven't seen any stability issues with the product to date. They tell you what exactly what is to be expected. They provide documentation of updates and what you should do and what you shouldn't do. I feel that as long as I follow the guidance from them, I won't have any stability issues.

We have had it go down one time, which was not related to the system itself. The server went down, which was an issue on our end. That is not OpCon's fault. Now, the only issue with this, which is OpCon related, was that it didn't send any errors except for one alert, one time. Then, because the server was down, it was unable to send us anything ongoing.

If there was some way that we could set up monitoring on a separate server that would look for specifically OpCon related tasks, then that would be more helpful. But, as for the stability of the system, we have never had it go down that was its own fault.

This solution is very stable and you can trust the software.

It's definitely been pretty stable for us. We run things 24 hours a day, so sometimes we run into issues related to putting server patches on it. We have to find a time to stop everything to load Windows patches and the like.