OpCon Reviews

OpCon has primarily been used to automate our backend IBM and Windows processing. Largely, this involves file transfers, IBM i job submissions, Powershell scripts, and SQL queries. 

We use OpCon to build workflows of related processes to ensure that things are run in the correct sequence. Logic is in place to ensure errors are handled appropriately, and often automatically. OpCon's Solution Manager is also used to empower other users to initiate processes, where previously tech involvement was needed. 

OpCon is the glue that joins numerous processes and various systems into a single cohesive and centralized experience. 

In my department, OpCon has largely removed the human error from our nightly processing. Clicking or launching the wrong program is a thing of the past, now that OpCon has taken over the processing. When employee turnover occurs, items that have been handled by OpCon are no longer a concern, due to the fact that the process will continue to function as expected. 

Error handling and reporting have also been a great benefit. Often when things in our environment break, OpCon will generate a notification to us of the diagnosed problem. We also heavily use OpCon's IBM Message Management system to identify messages displayed on our i Series and respond appropriately. This ensures critical messages are seen as well as tracked when required. 

Self-service has also been a great benefit to us. We're able to build processes within OpCon and give the end-user the ability to initiate them with inputs. Where previously this couldn't be done due to the security concerns of giving the end user that capability, now we can grant a batch user used by OpCon those permissions. This enables us to keep tight control over permissions, but grant some extended functionality through Solution Manager. 

The self-service is great as it enables users to initiate processes within OpCon without giving them access to more functionality than required. It relieves stress off the technology department, as more users are able to facilitate their own processes without a call to tech.

IBM LSAM has a very robust set of tools to monitor and run the various processes on an IBM i mainframe. It has the functionality to mimic operator input and capture data off of the screen for evaluation. The two most heavily used features of the LSAM in our environment are the Message Management and Scan Spoolfile functions. These allow us to capture information from message logs as well as spool files and launch further processing through the LSAM or OpCon itself. 

The smart email allows us to retrieve emails from a specified account and triggers further processing. Again, it allows another avenue for external users to initiate processes without needing to contact us. 

The script repository enables us to hold "scripts" that can be run on various machines - Windows in our case. It supports versioning and documentation.

The end code response allows us to evaluate how a process finished, set the termination/end code appropriately, and then trigger further processing based on how it ended. 

It's a pricey product. The new license model gave us access to a lot of functionality that we're not likely to use any time soon. The cost of the product is now also determined by the number of jobs you run through the software. There are pros and cons to this method, but now I have to evaluate if a simple function is worth the cost to automate before doing so. 

More functionality within self-service would be greatly appreciated. We're needing to look at other solutions in conjunction with OpCon as the number of user inputs available within self-service doesn't always meet our needs. If self-service could be improved to pull information from OpCon to "pre-fill" inputs, that would also create a much more seamless and powerful experience. 

It would also be fantastic if we could create our own job subtypes. There are quite a few that come with the software, but being able to create your own would mean you could standardize how parameters are provided to executable programs/scripts. 

I've used the solution for more than 4 years.

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

It's very scalable, especially given the new license model which allows installation on "unlimited" Windows machines. However, detailed knowledge of the product may be required to make use of it properly. It takes time and experience to make great use of the software. 

Usually, this is a positive experience, however, occasionally I feel like we're getting the run-around or being offered solutions that don't appear to be applicable to the issue. Very rarely is an issue not resolved within a week. 

We did not look at anything else of this caliber. We made heavy use of Windows Task Scheduler and the IBM Job Scheduler. The process worked, but everything was scattered and we really needed a centralized point of contact for all our automation.

SMA was onsite to implement the software initially. Largely, this was straightforward and any bugs or issues that came up we were able to work through shortly after SMA left. 

We had an internal team that worked with our implementation team from SMA to set up the product. SMA was incredibly knowledgeable of the OpCon ins and outs. Particularly the IBM contact with SMA was extremely impressive in their ability to provide robust solutions and bug fixes to problems in a very quick manner (often within a few hours of reporting the issue). 

In our environment, OpCon is much more expensive than it used to be a year ago. Licensing changes no longer allow us to automate to our heart's content in our "small" environment. Now, the cost to automate needs to be evaluated as new items are put into the software because it's likely you will be charged for them. 

Getting a good handle as to what SMA charges can also be helpful so that new processes can be created in a way that incurs a smaller expense. As an example, using a single script to accomplish what multiple jobs could do otherwise. 

Yes. We looked at Help Systems Robot.

Overall, OpCon has been an amazing addition to our automation toolbelt. While current prices sting a little, given past pricing, it has been well worth the cost and peace of mind. 

We primarily use OpCon to manage daily activities, generate reports, and handle FTP jobs for our full-service credit union.

OpCon improves our daily operations by automating many manual functions. OpCon's ability to run jobs in our host system allows us to create simple, effective automation that requires minimal employee interaction - thus helping improve our efficiency and reducing errors. We also use it for many other systems and also to trigger various scripts such as PowerShell and Python.

The automation of manual tasks using OpCon has reduced human error. In any place that we implement OpCon Automation, it removes the ability for inputting something incorrectly, and/or it will throw out an error. If we are asking for input, if they put it in incorrectly, it doesn't then attempt to run the process. It stops and says, "You did this wrong." We have that ability to kind of put those parameters in there as opposed to entering something incorrectly and then not finding out about it until the next day like, "Oh shoot, we updated a parameter and we missed a zero." OpCon definitely gives us a better feel for that. We have on my self-service alone probably 40 jobs in here. Then in our daily list running, we have over a hundred schedules running different things on a day-to-day basis. So I don't know how I can quantify how much it's reduced but it's over 50%.

OpCon has saved time for our IT team overall. In just over the years that we've done it, we keep adding new things to it. As an example, we're getting better at writing scripts that we can then execute with OpCon to alert us to various things that might be happening either in a host system or something like that. Thereby that then reduces research time to try to figure out when something went wrong. You can get a little bit deeper into it if you start using the advanced failure criteria where you can then have it so that you can say, "Hey, if you see this exit code, do this." Doing a little job output parsing, finding some different ways to push out notifications that let us know that something's gone wrong well in advance of a department coming back to us and saying, "Hey, this report didn't print the way we wanted." Or, "This process seems to be off." It definitely reduces the time that we spend looking into these projects or into these problems.

With IT time freed up, our organization has been able to move forward with other business needs. The company is learning that the ability to automate some of these things is freeing up time. Even if we're doing short-term stuff, for example with the PPP loans, the loans that financial institutions were giving out to businesses during the pandemic to help out. There's a ton of work and paperwork that goes along with that. I've been working with them to help them build some automation so that to flag loans on particular loans for particular reasons, or to pull data to send to our main house, to send out letters. That's a small example of what we're working on there.

OpCon increased our organization's overall productivity. It's hard to quantify it from my position in a company of 758 people. I don't have the statistics for all the other departments.

Last year, we added a second environment and the OpCon Deploy product. This has allowed us to build a testing environment. This has been a great addition for us as we can work through our workflows without disrupting our production environment. 

Our users use the self-service features. We have a number of them set up and their self-services are actually called Solution Manager. My accounting group uses it and my payments group probably uses it the heaviest. A lot of times we use it for daily postings, either GL postings or we have various different payroll postings that the payments group has to process based on some accounting groups that we work with and things like that, that have to be done a little bit separately than the regular payroll postings that we do. That's just the tip of the iceberg, I do have it set up for a few other groups just to do things like upload or actually transfer files via FTP to other vendors. It's a one-step process where they've created a file and that file needs to be consumed in some way, either via our host system or sent out to a vendor.

The self-service feature reduces the complexity of the technical aspects of workload automation. We've been using OpCon since 2012. Being able to give somebody a self-service button that they can press to consume a file to run a process within our host system was a huge advantage. Before, somebody had to go into the host system, run a particular batch job, manually type some things in that could also then be typed in incorrectly and create problems. It's taken a lot of steps away from what used to be a very manual process. People in other departments are not always technically minded like we are in IT, it helps them to focus on what their job is as opposed to having to do their job and then understand how to run this whole major IT process.

The self-service feature definitely increased our user's productivity. I can remember when we had an eight-page checklist that we had to go down each item and run each of these, "Step one, do this. Step two, do that." And when we brought OpCon and that clearly reduced all of that daily having to go through a checklist. We actually had one person in IT, and their job for the day was to run the checklist. Once we went to OpCon automation, whether self-service or just fully automating some things, it reduced that checklist to basically nothing at this point.

Upgrading to newer versions remains complex. I am not sure if this can be streamlined however, as when the enterprise needs to be updated, typically, all associated agents throughout the environment also need to be updated. Also, all agents, connectors, etc. all need to be on the same version for compatibility. Good documentation of your environment as it grows is very important.

We've been using OpCon since 2012.

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

Due to the fact that OpCon works with Windows and UNIX commands, it can be expanded into many areas along with embedding PowerShell scripts, etc. We continue to find new ways to utilize OpCon.

I have worked closely with many technicians at SMA and all have been excellent and committed to finding solutions that work.

OpCon is an expensive and complex solution that will take time to learn. However, once it is in place, it removes many manual processes throughout the organization. It would be best to start small with the some of the main functions first and then build up from there.  

We do not currently use OpCon's Vision features. Mainly because I've been doing it for so long and I learned through the older enterprise manager, that's where I spend most of my time. I do know that SMA has made a point of really moving the operational side of OpCon to their URL and more into the Solution Manager, which would then force us to really start using the Vision more.

It's like any other enterprise system, as they grow and we move things more to a more visual GUI type interface, then you kind of have to just grow with however the vendor grows. I'm looking at Vision like, "Do I really look at this? No." I don't even know if this is connected. We're not really set up for Vision yet so it's probably a while. It's down the road before we start using this.

We manage all the tasks run on the IBM.

We have automated 95 percent of our processes since deploying this solution. 

We use it to process our entire nightly update when we are running our updates for our DDA savings, CDs, and loans. It runs everything in order. We set up dependencies, where one job can't start before another. So, it's good for making sure that things stay in a good order and run the way that they should run.

The solution has freed up at least one employee to do more meaningful work as a result of the automation. We only have five FTEs in our group.

We can view what is going on with the system. We have better control of when things are run and how they are running their statuses. It just gives us a complete overview.

It allows us to organize everything into a process flow throughout the day for our different tasks that we have to run. So, it keeps everything organized. It is easy to monitor and adjust, if we need to.

Automating tasks is pretty easy for the most part, though you can get more complicated. For most of our tasks, it's relatively simple.

There is a learning curve. We had to go to class, learn, and take their training classes, then come back. We got assistance from OpCon as well to convert our processes on the Unisys machine over to the IBM. Now, when we add new products, it's pretty straightforward to write a new process and schedule it, then run it at a set time of day.

I have been using this solution since December 2016.

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.

We run with a very slim staff for our group. We only have one employee, at most times, who monitors and oversees things.

Its scalability is pretty good. We are a lot smaller shop than a lot of OpCon clients, but we don't have any problems adding additional jobs. It doesn't seem to slow anything down.

There are two or three main users who write processes or jobs. I manage the computer operations and my assistant manager will write some schedules. We have another IT person whose function is to try and make automation processes better throughout the company, and he uses OpCon. It also has a Self Service feature where you can push out particular jobs to users throughout the company. E.g., if they want to start a job, they can do it on their own without contacting the IT department. So, it's a web GUI front-end. They have a button if they want to create a certain report, then they can at their workstation.

The technical support is good. They will work with us and get issues resolved pretty quickly.

We were on a Unisys machine and used their workflow language to write automated jobs. But, it's sort of apples and oranges comparing the solutions, as they are pretty different.

We had a process in place before we switched to the IBM and were on Unisys, when we used to be on a different tool. It wasn't as consistent and would get things out of order, not running properly. Switching to OpCon, employees have found other things to fix their time on.

It is a lot easier to schedule things with OpCon than with our previous solution. We have jobs which run every 15 or 30 minutes, and it's easy to schedule those. You can use it to check and make sure other things are not running at the same time. 

OpCon was much easier and quicker to set up than our previous solution because we could set up schedules and copy them over, using them for other functions easily. Overall, it was 50 percent easier.

We were still running things on the Unisys system on a daily basis. So, we would copy our files over to the OpCon system, then run them through a simulated update just like we had on Unisys and compare the results.

We did use some of the OpCon consultants for the deployment. The main consultant who helped us was George Loose.

It took three to four months to get everything fully converted over. That is partially on the people who were in charge of doing the switch over. They were also in charge of running the daily operations on the Unisys machine and their time was not fully vested in the switch over.

In reference to the deployment being loaded, I wrote a process the week after I came back from the class. It didn't take too long.

1. We are running with less full-time employees. 
2. The daily processes are running smoothly. We don't find a lot of issues, so we have more time to devote to other tasks other than just keeping the system going.

This solution is slightly more expensive than our previous solution. Right now, we are paying about $40,000 a year. However, we think it's well worth the cost to keep things automated, reducing our staff.

The decision was made before I moved into this department.

It can get as complicated as we want to try to get it. We use it pretty extensively to run things on other machines and processes on other servers other than the IBM. So, we use the solution pretty well. It's fairly easy to use and straightforward.

Our data processing times are dependent on the IBM running. We switched to IBM at the same time that we went to OpCon.

OpCon is used fully on the IBM. We may increase usage in the future, as we always look for more automation opportunities as they come up. However, right now, it's just as we add new products or applications, then we'll add new schedules for those.

I would give the solution a 10 (out of 10).

We use it for automating with our core system, Symitar. We've automated some 100 processes with it. Of what we can automate, about half is now automated.

Before OpCon, it was a person's job to just manually run a bunch of things, like file transfers. And someone had to set up nightly processing within our system. Now, nobody has to do those things, and nobody forgets to do them. It just does them. It has improved our efficiency. We don't have to log in and download files and transfer them.

We haven't freed up a full person's job using it, but there are a good handful of people for whom it has freed up about half of their time. And those employees love it. A lot of tasks are based on certain times, and they're no longer stuck doing those things at those times. We don't have to have anybody coming in early anymore. They can focus on the processing part of their jobs instead of the file moving and downloading.

The solution has also reduced our data processing times by about 20 percent. We're still in the building process. We have a lot more to go.

For us, the integration with Symitar is the main reason we got it. But we're also able to automate everything. We don't have to do things manually anymore. It takes out that human error.

I don't really think anything needs to be improved within the functionality. The only struggle I had, when I first started using it, is that it depends a lot on the command line and I didn't have that experience. So more built-in, basic commands or more education on commands would be good.

We've been using OpCon for two years.

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.

SMA's technical support is great. They've been very helpful. What has been a little difficult because is the time difference. They are in America but they're two hours ahead of us. Sometimes things happen at the end of our processing day and their tech support is closed. But other than that, it's been great. Their online system is good and when we call it's good.

There is on-call support, but they make it very clear that unless processing has stopped, there's a fee for that level of support.

We had MOVEit before. The time to implement that solution, versus OpCon, was about equal. But OpCon can do much more than the other one could. In terms of automating processes, they are similar. MOVEit did not depend so much on command lines, so it was a little more straightforward when we wanted to work with dates or file names. But it didn't integrate with Symitar. For us, that was the huge part.

OpCon's TCO is a lot more but we didn't have support with the other solution.

The initial setup was complex. There's so much it can do. But we had a lot of support from SMA, so we got what we needed. That complexity goes back, in large part, to the command-line issue. The simple things, like downloading a file and saving it, are really easy. But if you want to do more stuff, it takes a little while to get through that and to understand how it works.

SMA came onsite for the initial week and set it all up. We went live right away with several things at that point.

Our implementation strategy for OpCon was to get the nightly processing stuff set up. That was the most important initial goal. Then we made a list of all the things that were run by people manually and we went down that list.

Our experience with the SMA techs was great. They were onsite and that was helpful. They're very knowledgeable. They explained everything and they gave us best practices.

We have seen ROI in terms of people being able to work more efficiently, which helps with the cost of employees.

We just switched to task-based pricing, instead of annual agent pricing. There are the licensing fees and a maintenance fee. And we have costs for maintaining servers, our main server and our DR server.

We didn't really evaluate other options because OpCon is endorsed by Jack Henry. We were able to talk to other Symitar clients to get their experiences. OpCon was the logical choice.

The biggest lesson I have learned from using OpCon is that we do a lot of things manually that we don't need to be doing manually. Also, as we're automating people's processes, we're able to analyze what they're doing and find a more efficient, better way to do things.

My advice would be to learn about the command line. Also, start early on making a list of all of the things you want to automate and write out the steps for each process. That's been taking a lot of time: Trying to get people to explain the different steps they do and then trying to figure out the best way to set that up in OpCon. Starting on those things early will help speed up the implementation.

There are about 10 people using OpCon's Enterprise Manager and the Self Service, in our company. There will be more. We're slowly expanding. Among the users are our systems analyst, our system administrator, and some of our accounting, operations, and compliance people use it. We also have a network specialist who uses it for file cleanup on different servers.

We have three people involved in maintaining the solution and each has a role. Some of us create, some of us upgrade it, as needed, and some of us monitor it daily. We don't have our developers using it. They develop something and then we usually incorporate it for them.

Our usage of OpCon is still pretty moderate. We have a lot of plans to increase it. It's just a matter of time. It touches all departments, but we want to utilize it more within each department.

I would rate the solution an eight out of 10. It's pretty good but I don't think it's miraculous. It's definitely better than our old solution and I'm pretty happy with it.

We use it throughout the enterprise, company-wide.

Utilizing OpCon has enabled us to achieve almost 98 percent automation throughout the enterprise. We have over 15,000 jobs in OpCon.

The solution has also streamlined operations. We were utilizing six people to do our processing and sustain our environment prior to using OpCon, and now we are only utilizing one person for that. And that person, who is currently working primarily on OpCon, has been freed up to do other work, other scripting. He's also able to do additional admin work within the IT environment.

OpCon has taken employees out of day-to-day, manual operations and given them an opportunity to grow in other areas of IT. They have been dispersed throughout our IT department in various other functions and roles where we needed additional staff, including our client services PC area, our server support area, and some of the other admin work areas. They no longer have to do repeatable, menial tasks just running batch operations.

In addition, nightly processing would take about 10 hours prior to OpCon. Now that we're running on OpCon, it takes two.

• The most valuable features are its integration into Windows, into VM, and into AIX, as well as SQL.
• The job automation and ability to run scripting are also important for us.
• It's relatively easy to use and utilize. If you have knowledge and understanding of network technologies, it makes it much simpler.

We have not explored the possibility, but one of the areas for improvement would be more integration into Active Directory, to where it could do the creation of user accounts and the additional work to integrate third-party systems into payroll systems.

We've been using OpCon for almost eight years.

It is a very stable product.

So far it's been scalable in our environment. We haven't had any issues with the scalability of the product.

We have plans to increase the Self Service capability and to integrate it into additional business units. As far as some of the other environments go within our infrastructure, we do have plans to add automation to our document imaging system and any other new or auxiliary products that we purchase.

The technical support staff is knowledgeable about their product. We have had a turnaround time of less than four hours in most instances where we've had to call in for support. But the product in and of itself is very stable so we have not had a lot of technical support calls. Contacting them has been more for when we've had to implement new products or new services and we were making modifications.

We did utilize another job scheduler prior to OpCon called JFS, which was not robust enough to do everything that we needed done. That's why we opted to look at the OpCon solution as a replacement. JFS was more tedious in terms of implementation. It was not robust enough to do individual calendar scheduling, nor did it have the ability to do a lot of these single transfers or to initiate any scripting for SQL or AIX. It was very limited.

With JFS it did not take long to implement automations; a couple of hours to automate a process and to be able to add jobs to it. It's just that it was very tedious and we had to consistently manipulate the schedules to fit our needs because it did not have a calendar system like OpCon does to be able to manipulate jobs and do schedules by date.

Overall, JFS was not scalable. It didn't meet our needs. It required a lot of manual intervention. We had outgrown that product very quickly. We had been on that product less than four years before we decided that it just was not good enough to sustain our environment. Currently, our environment has over 240 servers and there was no way we could have managed that with the old schedule.

The initial setup was pretty straightforward. The SMA group came out onsite to assist with the implementation. It was done in two phases, upon our request, because we didn't have the man-hours to be able to do it all in one shot. They came out and did some initial training with us and then we asked them to come back four weeks later. Upon their return, because of the training we received, we were able to tackle a lot of the automated processes and they helped us with the more complex schedules.

The deployment itself took a couple of hours.

The implementation strategy for us was to tackle the nightly process first, and the second item was to tackle all FTPs. The third was to tackle the complex scripting for all other SQL or AIX. The last step was to do Self Service.

We reached our return on investment from the first year that we purchased the initial product, simply because of the number of man-hours saved. We were paying $200,000 in personnel costs to sustain our operations environment. We removed that from our budget as far as salary is concerned, from the operations area, because we didn't need as many personnel to run operations on once we implemented the product. We ended up adding new roles to take on new initiatives and we were able to expand our IT area into other things.

Our annual maintenance costs are $45,000. The initial cost is separate.

Initially, we purchased just the standard OpCon solution. We upgraded to the OpCon elite solution, the enterprise edition. That did include some Self Service licensing. But if we want to expand to more Self Service licenses, we will have to purchase them. We may look at that in the near future.

I don't recall which other options we looked at. We did attend an educational conference where this product was offered and we decided to explore its capabilities. Because we had a job scheduler in place prior to purchasing OpCon, we didn't weigh it against many other products. We looked at some of the features that it had and the robustness of the product and we liked the presentation that we were given, as well as the possibility for expansion. That's why we took it on as a job scheduler.

Step back and look at your enterprise and purchase enough licensing to cover all of your servers. When we first went into the product, we only purchased the minimal, standard licensing. It was just the 10 licenses. Fewer than six months after the purchase of the product, we had already used up all the licensing that we had purchased. If we had really taken a look at our overall infrastructure and seen the number of servers that we had, and taken into account the utilization of this product — because it's so robust it can be used for many things — we could have made a better decision on the purchase and gotten an enterprise version of it instead of just the standard.

I have about 15 users of the product. Three of them are operators, about five of them are in the development realm, and the rest are batch users who initiate schedules using the Self Service feature. For deployment and maintenance of OpCon we require two people. They do monthly security patching, which is normal maintenance, as well as yearly upgrades.

The biggest lesson I've learned in using OpCon is that you get your money's worth. The robustness, scalability, and expandability of the product are things that every company should invest in. OpCon is a very good product.

We use OpCon for scheduling batch jobs on the Unisys mainframe. It controls all of the batch work. Therefore, if we want to rerun a job or add a new job in, It is used for controlling this Unisys batch work.

It allows batch work to run as smoothly and efficiently as possible.

If we are talking about a one-off job, it takes roughly five minutes to set that up, which is very quick.

Results are pretty much instantaneous. It depends what frequency you put on the job. It could be a job that will not run for another couple of hours. But, if you set up a job and want it to run straightaway, it will do it straightaway.

OpCon has streamlined operations. 

Going back 20 odd years ago, everything used to be controlled manually before. Now, it's just a flow of jobs. You kick one off, then there are just dependencies, one after the other. These jobs just follow those dependencies and do it all automatically, instead of somebody having to sit there and do it manually.

From when it was first deployed, the solution freed up around 100 or so employees to do more meaningful work as a result of the automation.

It reduced data processing times when it was first deployed. Back then, it probably saved a good six or seven hours on a daily basis. The amount time has shrunk since then, but that is not due to OpCon. It is more due to reduced processing times on the Unisys mainframe.

It is very simple and easy to use, but that might be because I've been using it for a long time.

The things that we use most often are:

• NIST view
• Job Master
• The quick search option.

The way to view a schedule is called perch view, and that's not always the greatest. It can be quite slow.

Any issues we did have with earlier releases have since been addressed in later releases.

We are looking at something called Solution Manager which comes with it, because we don't use that currently. This shows more performance and is an easier way to access them. You can also set trends and do more analyzing.

I have been using it for 12 to 13 years.

The company has probably had it for about 20 years.

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 scalability is quite good. The amount that we have on it doesn't ever cause any issues. I am not too sure how much more it could cope with, but I imagine it's a lot more.

We have approximately 50 scheduled jobs running various different processes. It varies between 20 and 100. Because it's a big organization, these automated process are not a massive part of the organization: Approximately 15 to 20 percent. I don't see this figure going up since a lot of stuff tends to be moving into cloud-based stuff.

Our use of OpCon needs improvement because I don't think we use it to its full capabilities.

There is a team of us who do the maintenance. There are mainly three people on the team with another hundred other people using it for view only purposes, such as viewing data results and what times certain jobs finish. They don't have access to make any amendments.

The technical support is very good. I think we have a designated person who we contact if we ever have any sort of issues, etc. Their response time is fairly quick (within 24 hours).

The initial setup is pretty straightforward. They give you some good user guides and information on how to do it.

If we are upgrading, it probably takes about two to three hours. We start the automation process within this two to three hour time slot. It is pretty quick.

When deploying a new version, we have to do a lot of testing. We have DR boxes which we do our testing on first. That's what we're currently doing it at the moment. Then, we have to run it through our change management to make sure all of the various other areas in the department are happy.

SMA is pretty helpful, if we do ever have any questions. They are pretty quick to respond.

For upgrades, three or four are required. There are three of us on our side involved in upgrading it. Then, there is one person from SMA to help, if need be.

Compared to other solutions that we have in the organization, OpCon is a lot quicker to deploy. For example, Control-M takes almost double the time to deploy.

We use OpCon for Unisys and Control M for more server-based jobs.

it's definitely an application worth considering and looking into. It is a pretty good tool. I don't really have too many issues with it.

My biggest lesson since using it has been to learn how to upgrade it. This is part of the process, as I've gone from the scheduling side of it, where no one else scheduled jobs to the next step of learning how to upgrade it.

I would rate it an eight (out of 10). The product is always available and easy to use. I like the overall general feel and view of it.

Job automation is the primary use of this solution. Processing reports, running batch jobs, processing ACH, and all other daily operations are things we have automated using OpCon. 

Without this automation, I am not sure how possible it would be for the company to finish the nightly processing by doing it manually. Working 8 hours a day is not enough for us to complete our daily process. 

In addition, we are using OpCon for testing our Dev and QA environment.                                            

OpCon is automating everything for us. I cannot imagine working without OpCon to process our daily operations. 

With OpCon, we can still do other operational tasks, troubleshooting, projects, research, etc. Without OpCon, we will be up and working until the wee hours of the morning. We are only checking our OpCon if there is a failure. Without a failure notification, we are confident that OpCon is doing its job for the company in order to process our day-to-day operations.

Self-service is one of the features I like the most. The self-service feature allows us to give control to the users to execute the job we have set up for them. This eliminated the requests, either through a ticketing system or email, to run a specific schedule for the department. 

With a simple click of a button in self-service, the department or the user can complete his/her job. Users are loving this feature, too. They are liking the option that they have control over their process.        

I would like to see OpCon being accessible using a mobile app. This will increase the convenience for the administrator. Imagine it is a weekend and you are on call. A failure email was received. You will then need to grab your laptop, connect to VPN, and access the application to find out what is going on. If you are somewhere else, you will need to bring your laptop with you all the time. If the job can be fixed with few clicks, a mobile app will help the administrators to fix the job right away even if you do not have your laptop with you. 

I have been using OpCon Enterprise Manager since I joined the IT team last 2012. Even before I joined the team, the company was using OpCon Enterprise Manager.

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.

Any organization size can be managed by OpCon. Whether you have one product, one staging area, and one QA or multiple staging and multiple QAs, you can easily connect them and push anything into production with few simple clicks. 

I do not have anything negative to say about their customer service or technical support. So far, all of them are so helpful. They will even send a follow-up email before closing the ticket. 

This is my first job scheduler/job automation application.

When I started here, the OpCon was in production already. I am not sure about the complexity of the setup.

When I started here, the OpCon was in production already. I am not sure how the application got installed. 

I do not have the numbers, but definitely, our ROI for having OpCon is high. To give an example, we are only two personnel on a team. We can manage the daily operations, attend to any system issues, do projects, and manage the core system ourselves.

Their setup cost, pricing, and licensing are fair. SMA Technologies will not charge you too much. I have the experience that SMA tailored the licensing for us according to our average yearly usage. 

If you want to increase your daily efficiencies, consider OpCon. Give them a try and you will notice the difference from Day 1. Ther support is outstanding. You can call them 24/7/365. They value their SLAs. SMA staff are very friendly. 

We primarily use JHA SYMITAR Episys (Currently running through EASE). Our Episys server is now hosted at Symitar and they run most of our OpCon schedules, and we run a version of OpCon in-house and connect to the Episys server at Symitar through OpCon "Ease Connector". We've used Episys Batch/On-Demand in-house job scheduling (2014-2019) and Episys Batch/On-Demand Ease Connector job scheduling (2019-present). We also use OpCon to schedule non-related Episys jobs, such as file transfers to/from vendors. Everything is automated.   

It has eliminated the need for a full-time Operator. All Batch jobs are automatically scheduled. We do not have IT Operators overseeing Batch jobs. All FTP's are done through OpCon also. We have OpCon set to notify the team by email if any job fails, or notify front office staff when a job is completed. Some jobs are scheduled with the OpCon feature "File Watcher" and will run a job when a file is present in a Network folder - eliminating the need for intervention by staff. If files are not present when they should be, OpCon can be set to let you know a schedule is past normal run time.

On-Demand access allows the front office to run jobs on their own, making it unnecessary to contact IT when they need on-demand reports run.

We get email notifications for failed jobs, jobs completed, schedules past run time, etc.

File Watcher can run jobs when files are made available in a folder. 

We would like to keep a previous version of a job/schedule just like UC4 used to do. 

We would like a display of the created date, created by, and last modified date, as well as modified by.

I've used the solution for 7 years, since September 2014, and I have used 5 OpCon in-house and 2 OpCon EASE Connectors.

The stability is excellent.

The scalability is excellent.

Technical support is excellent.

The setup is a little complex. We couldn't have done it on our own. You must work with SMA to get set up and have training, but once you become familiar with it you should be good to go. The only time we consult them now is when we are upgrading to a new version. The instructions have never allowed us to do it on our own.

We have an in-house team for the in-house version.

We needed the Symitar OpCon team to work with us when we switched to Symitar Ease and to document all the schedules/jobs. 

We could not work efficiently without OpCon. It eliminates the need for full-time operators.