OpCon Reviews

We use it for automating business processes.

We're currently running 900 daily jobs in the system and OpCon allows us to do more because we don't have the human resources to run that many jobs. Now, with a system that can automate things, we are able to add a lot more volume to our day and to increase our job count. It allows our business to process a lot quicker. We can process more in real-time instead of waiting until the next day. It has enabled us to move from traditional batch processing to more real-time processing with a lot of our processes.

We've automated close to 250 tasks. In our IT space, we've automated 100 percent of the jobs that were running manually. We have also automated some tasks in our accounting and our item processing department. The automation on the accounting side drastically changed their jobs. I know because I was involved in working with their teams. And on the item processing team, close to 75 percent of the manual tasks around the core system have been automated.

OpCon has also reduced our data processing times because of the way you can build out workflows. It can run things in sequence. It's not restricted to a linear process, so you can run multiple jobs at once, allowing for multi-threaded jobs. As a result, we have been able to cut our nightly processing job from three hours to two hours.

The most valuable feature is its integration with our core system. There is a very limited number of vendors that integrate with our core system. OpCon allowed us to reassign three part-time people who were running jobs manually. OpCon is running those jobs automatically and those people now work in general IT support, instead of running manual jobs all day. Those people were very receptive to the changes because it was a lot of tedious and error-prone work and they were pretty happy to get it off their plates.

OpCon is also fairly easy to use, as long as you have some kind of process background for understanding workflow. If you understand workflows at a very basic level, you can use OpCon.

The biggest area where there is room for improvement would be integration with their code. They've got a function for embedded scripts and it would be nice if that worked with a code or versioning management system, like GitLab.

Overall, we haven't run into too many roadblocks where we tried doing something and we couldn't do it.

We've been using OpCon for four years.

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.

It scales easily. The only thing you have to be mindful of is licensing, because you pay per task. Other than that, it has handled as many jobs as we've thrown at it. We tried a few thousand in one day. It scales nicely.

It handles all of our critical-to-business processes. It handles all our ACH, our check-processing, our nightly processing, and various other daily tasks. We'd be in rough shape if we didn't have OpCon running.

Our plan is to always increased usage. We have a "continuous improvement" mindset here. If we can implement something in OpCon, we do.

SMA's technical support is excellent. They've always helped us out.

We did not have a previous automation tool. The reason we went with OpCon is that it has an integration with our core system.

The vendor handled most of the setup but it's more complex than other systems. We had some issues with setting up our service users with the domain. There is still some complexity with that — with which users have to run which jobs on which servers — because of permission models. That was the only thing that really was complex about the install. Actually installing the application is very straightforward, but the permissions model behind the service accounts is complex.

The complexity is because they allow you to do things in so many different ways. They didn't want to make an out-of-the-box setting for how you do things. Some of it is left up to the user to figure out the best way to handle things. In our case, we decided to use an Active Directory domain user and it was a little more complicated to do that because of security issues.

The installation itself, to where there was a usable product, took about two hours with their support team. Our experience with them during the initial deployment was very good.

After the initial deployment, it took about 10 minutes to automate our first process.

As for our deployment plan, we had all our manual jobs in a checklist and we ranked them all with a complexity rating. While the OpCon support was on site for our implementation and we had their attention, we worked through the more complex issues. After they left, we picked up the low-hanging fruit.

We have absolutely seen ROI. I don't have any way to measure it, but it's probably the most critical system to our organization, after Active Directory and email.

Yearly, we're paying about $62,000. OpCon has an all-inclusive feature and module license, but you pay per task. We have a 500 daily task count. Recurring tasks only count once. There are only additional costs if you want consulting hours for working on new projects. I think that cost is $250 per hour, a pretty standard consulting rate.

We evaluated one other solution, but I don't recall its name.

My advice would be to definitely involve the business units early in the process and get them all onboard, because you don't want to buy a tool that the business isn't ready for. They should be involved in process mapping.

The biggest lesson I've learned from using OpCon is not really about the tool itself, but more from going through the process and mapping with other departments. There's a lot of room or potential for OpCon, because the users in your company are definitely doing more manual processing than you could ever imagine. It made us realize how much manual work we are doing. It put eyes on that. We became hyper-aware of everything going on and would say, "Oh yeah, let's put that and that in OpCon". That went on nonstop for two years.

It's ongoing. We're still definitely growing the tool. There's always new stuff. Some teams were a little apprehensive at first and now they're more interested in it. When you talk about automation, it's always about someone's fear of being replaced by a machine. That wasn't the case with the core team for the critical pieces. All of those teams were willing to move their stuff because of availability and the criticality of what they were doing. They realized that automating it was a good move.

In our company, OpCon is primarily run by the IT department. The only other team that interfaces with the tool is accounting, and they use the Self Service feature. We have 12 users using OpCon on a regular basis. There are two people in IT who maintain it.

We automate everything we can with our core banking software, including daily and nightly processing and any other recurring IT jobs that can be automated. A lot of our employees access OpCon via its self-service feature. We're a financial institution, so various business units use it, including some people in our mortgage or insurance department. It's mostly used to start processes or run reports on demand and that sort of thing. It's a set-it-and-forget-it solution. 

The most significant benefit is time savings, which translates into money savings. It's hard to quantify how much time we've saved. When we first installed it, we could maybe calculate that, but at this point, we rely on it so much that I have no idea how many person-hours it would take somebody to do these tasks anymore. 

With the processing time freed up, we could focus more on the other business units to implement what they need and work on other special projects. In general, it made us more productive while reducing calls to our IT help desk. The users can do what they need to do without opening a ticket with our IT department or waiting on IT resources to be available. They know they will use the same criteria, so there will be consistency in what they do.

The most valuable feature is the automation in general. We don't have to rely on somebody to manually do the same process over and over again, risking human error. We like the consistency. It's the same way every time. Moreover, it integrates well with our core software.

I'm sure there's plenty that could be improved, but some of the biggest pain points aren't necessarily a fault of OpCon itself. For example, the FICS integration is a little bit clunky. We've had some tickets with their support team, and sometimes they couldn't figure it out, but that probably has more to do with FICS than with OpCon. If there were room for improvement on the SMA side, it would probably be cross-training. They have a person, maybe two, who deals with FICS. Nobody else knows it.

I've been using OpCon for probably four or five years.

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

OpCon is highly scalable. We don't necessarily have a need to scale it beyond what we have now, but it's easy to see it scaling up. However, we don't have any plans to scale up significantly. We'll scale but not a massive amount.

I'd rate SMA support an eight out of 10. We haven't had to contact them much aside from FICS integration and support. If it's a simple issue, they can knock it out without any problem. However, when we've called with more complex problems, we haven't gotten those fully resolved. 

Positive

I think our previous solution was called AutoMate. It wasn't nearly as robust as this, and it relied on on-screen scrapes, etc. It was pretty dissimilar to this, and we retired it as soon as we had this in place. 

The setup was relatively straightforward, but we had someone from SMA on-site, so they walked us through it and showed us how to automate some of our more complex processes. I think the whole setup took two weeks. 

For maintenance, it only takes two or three people in IT. Everybody else has access to it, but we have a core group that maintains it, and then there are around half a dozen to a dozen self-service business users. But from a day-to-day perspective, it's low maintenance. If you're not changing anything, you don't have to do anything. If you're setting up new processes, that takes a little work, but you don't have to babysit the solution.

I'm certain we've seen an ROI. I haven't run the numbers myself, but I'm sure it's probably reduced the number of full-time employees we need by at least one person.

The licensing and pricing model changed this last year, so we're getting used to that. I think it's ultimately going to end up being more expensive. It depends on the scale of the business. It used to be per machine, so we had X number of devices licensed. Now it's not. If we had a lot of machines, the new license might have decreased the cost. Unfortunately, we didn't see the same gains. There wasn't any consolidation of licensing with the shift.

I rate OpCon eight out 10. If you're considering it, I don't think you'll regret it.

We have OpCon in our test environment, we're testing that right now and putting it into production next month.

Our primary use cases are for our core system that does batch processing for our core system, which is Symitar. We have automated about 90% of our daily processing. And we have started to branch out to utilize it more for Self Service where our other business units can automate some of their processing as well.

The fact that if you automate your core processing, in our case, alleviates the need to make sure that if somebody is running late or somebody calls in sick, your jobs are still going to run, they're still going to be on time. It has notifications built-in to let you know if something has failed or has missed the start time. It really keeps your business flowing and with proactivity. That's been the biggest example for my institution. It's the fact that we're a 24-hour shop. There's no downtime. It keeps us running and moving. We're about 90% automated if we look at our core processing. 

The automation of manual tasks has reduced human error by at least 40 hours a week. It's essentially saving another person. 

It has saved our IT team time by automating things a lot less wait time for people waiting for my team to actually run processes or transfer things. There's no delay in between the time when something is supposed to happen and when it happens.

We are able to move forward with business needs. My team is now able to learn, do additional training and other facets of IT. Rather than spending the time blending jobs, transferring, and doing things manually, they're now able to work on other projects within the organization. They're learning more about different areas of how other things function within IT. We become more project-oriented than process-oriented. We're able to identify things within the business that we can automate or that could be changed. We've gone from reactive to proactive

We are at least 80% more productive. 

There are a lot of valuable features. The version that we're currently casting, Self Service, is going to be the most valuable to us. It is going to allow us to open up the doors, broaden our automation capability and help other business units to be able to automate a lot of the little things that they do from day to day. I'm really looking forward to being able to help other areas with their automation needs. Self Service is really key.

OpCon is pretty easy to use. I'm not a programmer, I had no formal training. They offer some basic training courses. They also have a lot of documentation online and their support staff is super helpful. So it's pretty easy as long as you can take the time to familiarize yourself. It's a pretty easy application.

For the Enterprise Manager, the UI is okay. It puts your processing in alphabetical order instead of the actual processing order, but they are building a new UI. They really are on track to make it even more user-friendly. It's like they're listening to some of the common complaints from their customers, or they started to build out what we need or what we are looking for.

We are setting up the Self Service feature right now. That's going to be our biggest list in our organization. We just installed it and went through our training a few weeks ago. My team is building Self Service buttons in our testing environment right now.

Enterprise Manager is a little clunky which I know they're addressing in the solution's manager. 

It's annoying that our processes are listed alphabetically. It should be listed in dependency order or order of processing. That's one thing that drives me crazy. That's my biggest issue.

I have been using OpCon since October of 2010.

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.

They see that there are other competitors out in the market that do what they do. So they want to make sure that they stay relevant and are able to keep up with changing technology. They put a lot of stuff in the new release from 19 to 20. The team has been working really hard to take that stuff into account, like how to future-proof and make this more flexible. I think it's very scalable.

Currently, six of the admin users are me and my team. And we are primary users of OpCon, which means that we are monitoring and setting up. And then we have our Symitar administrative, our core host system administrative who's also involved. We also have our payments team who used to do ACH and draft returns. They are primary users as well.

For deployment, you really only need a couple of people, but I'd like to ensure that my entire team is well trained. You don't necessarily need seven people, if one or two people have a backup is plenty. My team's official title is Computer Operators. They're basically responsible for batch processing and file transfers within the credit union.

Right now 90% of the usage is my team with a small bit with our payments team. So one thing we've been able to do is learn more about the product, go out to our business and see what their needs are. With the new version and the Self Service features, we plan on branching out because Self Service allows business partners not to have to log in to either our core system or the OpCon system, it's through a UI or URL. And so the thought there is that we will be able to branch this out to accounting collections. The payments team has the other items and the card services team as well. There are certain processes in the run in our core and we would like to automate those so that they can just either run automatically or they control when they run them through.

We will start with Symitar and sometimes Symitar will refer us back to SMA. They work really well together and we're able to come to a resolution, but sometimes it's both systems in OpCon and Symitar that have an issue.

SMA support is super helpful. They're a great team.

We also looked at DMC. OpCon has a relationship with Symitar. That was a selling point for us because they have a close relationship and they already have several Symitar clients using OpCon and they came with great reviews. DMC had several other core systems that they were automating but Symitar wasn't the main system. So we just felt more comfortable going with SMA.

The initial setup was pretty straightforward. We had a great team. We had both SMA and Jack Henry, which is our core vendor. They were both on-site. They worked really well together. They were very hands-on in training and had me and my team involved in the whole process.

The deployment took us two weeks. We wanted to implement it in the test first so that we could see how it interacted with our core and our other systems within our network. So that's where we first installed it so that we could do our basic setup and testing. And then once those testing passed, then we set aside some time to set it up in a production environment. Because we obviously didn't just didn't want to gung ho and go back into production.

We use Jack Henry. They are our Symitar, which is our core processor, our integrator.

They told us about SMA because SMA has a relationship with Jack Henry as a core processor. They did a lot of their automation. Jack Henry told us about SMA, which is how I came to bring them on board. Because they had already built a lot of automation for our core processing. They already had a business relationship. 

We currently renewed with one of their new technology bundles. It's around $36,000 annually. We run a query of our SQL in our SQL database to see how many jobs we run. They're charging us per usage and whatever add-ons you want to use with OpCon.

My advice would be to ask a lot of questions. Make sure that you involve your entire staff from beginning to end. OpCon was a really easy experience. Having them on-site, sitting next to you with hands-on experience, you can't beat it. They're not hiding anything. I really appreciated the amount of effort that they put into showing up, training, and following through as well. Whenever something did go wrong, they're always there to support you.

We consider OpCon to be one of our tier-one applications, meaning it's almost as critical and important as our core host system. We haven't done any vendor comparisons in ten years because we're very happy with them. 

Typing matters. A lot of what you enter is manually typed. So watch your spacing, watch your fat fingers and copy and paste or copy schedules wherever possible. And then the other trick is eventually you always have a frequency. Those are the few things that I mess up on that really make my whole deployment delayed because I can't find why it's not working and it's always usually because I have an extra space somewhere or character I didn't need. Watch your typing and have a second set of eyes.

I would rate OpCon a ten out of ten. 

We use it to automate multiple platforms: our mortgage platform, our core platform, and other instances where we're working with third parties to whom we have to move data. It does about 90 percent of our automation. Very rarely do we do anything that's not automated. For example, we do not manually upload anything. It's all done through OpCon.

The biggest improvement is the batch automation. We don't do anything manually anymore; everything is automated. We did have a very highly skilled employee and the job he left for was a job with a bigger credit union to run their OpCon shop. That's how good he became at it. His skill set was at a very high level, where he automated up to 90 percent of what we do. We very rarely have to manually upload.

We've automated about 50 to 60 processes, and that number is growing. We are adding on our mortgage platform to automate that. And that number does not include the OpCon buttons they also use for on-demand stuff.

It has also helped to streamline our operations. We contract out our collection department so they are no longer housed on our system. They're housed on another platform. OpCon is able to not only pull in our data, but it also, on a daily basis, updates that third-party. In addition, if there are any updates coming back, OpCon will check on a daily basis and send it back. That's just a sample of how it automates. 

Another example is how we automate our daily FedLine. The most important job files that we run are our ACH, our Federal postings for credits and debits. We totally automated that where there is no longer any manual intervention. We upload the Fed file; it comes in and OpCon is smart enough to know where to place it and how to run the edits. It's also smart enough to know that there are delay times. Before OpCon, we were posting them the next day, manually, one after the other, because there are four to five that come in and out throughout the day. Because we were able to automate it through OpCon, we can now post them when they actually come in. They are posting throughout the day now. For example, at 12 in the morning there is our major posting, and it's posted right when it should be. Members are actually getting their paychecks or debits and credits right when they should happen. That was a big one which was very member-impactful.

OpCon has also freed up employees to do more meaningful work as a result of automation. They're not having to go into Symitar and run a job. Instead, they can simply run something. They've also found innovative ways to use it as well: "Hey, I have this thing that produces an Excel file. Can OpCon just grab it and send it out to this other vendor for me?" And the answer is, "Sure, that's not a problem." Our employees are thinking outside the box, as far as utilizing it goes. Even though they don't generally know OpCon, they know what it's capable of. In some cases, they're building their own little building blocks of automation themselves.

The main employees who have been freed up are in our accounting, item-processing, and lending departments. In those three departments there are about 15 employees. All depend on OpCon to do something for them. We're not that big of a shop. We have about 100 employees in total.

Our employees expect automation now. Prior to that, it was nice to be able to run something and for them to get their data. It was awesome. Now, as they know that it's a standard process, they're not as excited. They just expect it now. If you would tell them: "Oh, no, you have to manually move this from here to there," they would probably come back and say "Wait a minute, my other thing is automated. Why can't this be?"

If we're counting all the manual intervention, as a percentage, I would say that OpCon has reduced data processing by 90 percent, through automation, the efficiency, and the eliminating of manual errors.

There are a lot of areas that are valuable. Perhaps the most valuable would be the OpCon button that users can select so that instead of having users going into Symitar, they can now just run an OpCon button that works on-demand. That's probably the one that has made the biggest impact. We no longer have users running job processes in Symitar. Everything that they need, we simply have them run on-demand, so there's no access into Symitar. That is one of the most valuable tools we have. Obviously, the batch-automation is a big one, but that button functionality would be the biggest feature.

Usage is a little complex. It's not like you can bring somebody in and they can just use it. They have to be trained. Our main OpCon person left and it's a lot harder for a lot of people. Once you have somebody leave, the next person has to step up and it is a little difficult. As far as complexity goes, it's right up there.

Once you get to know the platform, you do know how to troubleshoot. But there's just so much to learn. If you are properly trained, it is fairly easy to figure out problems and troubleshoot. SMA does offer certification and they also offer consulting hours, which we are using right now.

There is always a percentage of jobs where the batch automation doesn't work or something critical happens within the OpCon server that causes something to stall, and we have to troubleshoot.

Another area for improvement is within the notification and alerts. I'd like to see it get smarter with script-writing within OpCon to make it do more. There is some room for improvement there and that's why we got the consulting hours.

We've been using OpCon for the last five years.

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?"

It's pretty scalable. It can go virtual. They have a lot of options. Right now we are on-prem, but we would definitely look at going off-prem and having it hosted in the future. That's what we'd like, and they do offer that capability. They also offer managed services, which is something we're going to target in the near future, simply because we're a small shop. so they do offer a variety of things that we could definitely take advantage of.

We only have one user using OpCon because the main one left. She is training our other two who are brand-new; they are literally brand-new, even to IT. We are very shorthanded right now. That is why we bought the consulting hours, so that we could get these other two up to speed.

Similarly, only one person is doing maintenance of the solution, which is why we're going to contemplate shifting over to OpCon's managed services. That kind of solution is probably a perfect remedy for a shop like ours. I wouldn't be surprised if, this time next year, we're not even managing it and that they are.

When we had the log problems they weren't very helpful on that. It felt that it wasn't a very helpful solution. From eight to five, they will help. They have some really good people. But if there are really complex problems like the logs, it feels like the front-line support doesn't know, or at least didn't on that one occasion. Thankfully, our network guys figured out the problem. Otherwise, we would have been out of luck. I'd rate technical support at six out of 10.

We didn't have a previous solution. We were doing things manually.

I didn't participate in the setup, but I believe that it was straightforward. OpCon came onsite for training and it seems that soon after my staff got the training they took the ball and ran with it. They got the building blocks in the training and, after that, they caught on fairly well and were able to start automating a lot of the manual processes, one by one.

For the implementation, we had to load the server and we had to have a backup for that OpCon server, which goes out to our Branson site. Any changes to OpCon get passed on. But when OpCon come onsite, they pretty much got everything loaded for us. We were paying them to do that, which is what I would recommend to anybody. It helped us, a company that was brand-new to it, to bring us into it. When they were onsite they handled 90 percent of it.

It wasn't long after the deployment that we automated the first process. Within a week we were already automating some things that we had been manually moving over. And then we road-mapped big ones like the ACH stuff that I mentioned elsewhere. One of our first projects was automating our ACH to the Feds. We had an idea of what we wanted to do once it was implemented.

We have definitely seen a return on investment. The big return on investment was the fact that we lost three OpCon people from our staff and nobody even knew that we had. We went on without skipping a beat. We literally had the worst-case scenario that can happen to an IT staff and we came out smelling like a rose. Everything ran and we were able to continue with a small staff and we did not have to worry about our batch automation.

Yearly, it's around $30,000.

We bought consulting hours for a year at an additional cost. We're getting 85 hours a year for consulting to help us through, for example, with a complex process that we want to get done. Some of those hours might be spent for them to actually come onsite and give one-on-one training to some new people being introduced to OpCon.

We looked at two other vendors. It's been a long time so I don't remember their names. They were enticing because they were definitely a lot lower in cost, but ultimately OpCon had more of a service to provide. OpCon offered more services and more automation. It was a no-brainer after we learned that.

Do your homework. Definitely look at other vendors and consider your staff size. In our case, because we have a small staff, we don't have a lot of programmers. We don't have the luxury of having 10 programmers who can write their own batch scripts. If you're a small shop like us, really do your homework on it because, in the end, if you rely on somebody writing batch scripts to do things and they ultimately leave, you own that. You really need to make sure about your road-mapping. Are your employees going to stay at the credit union? If they are, that that makes a big difference. 

What happened to us was that we lost two valuable OpCon employees within a span of two months who knew how to solve OpCon problems. The third person, who was average but knew it, went down with an ankle injury for a month-and-a-half. We had nobody who knew OpCon for almost two months. The only thing that saved us was that the process was so automated that we didn't have a problem, thank goodness. Everything just ran and we never had an issue.

You have to know your staff; you have to know whether they're content. Are they going to be staying? If you know they're going to leave, you better plan ahead. You don't want to get caught like we did.

But our situation tells you how well OpCon is programmed.

The biggest lesson I have learned from using OpCon is that we have to stay on top of the releases. Every year there are software releases that you have to get done. They are key. But there are also updates, SLAs that come out. We definitely try to keep on top of that because our batch automation is a critical platform. So it's critical that we make sure that everything is up to date. The SQL portion of that is also important. We also use third-party FTP software and that is another thing that we've got to make sure is up to date. It's a definitely a solution with moving parts.

We use it to run all of our batch across seven Unisys mainframes.

It's installed on Windows.

OpCon has streamlined the batch. It's made it quicker. We're processing work a lot more easily now, given the dependencies and frequencies we have. We don't really have to think about checking things. It's all there in the system and done.

When we first brought it in, we saved on people's time. We freed them up to be able to look at the future. We freed up two or three people who used to have to work on it all the time. In terms of batch savings overnight, we've probably saved a good couple of hours per night on batch scheduling.

Auto-scheduling is the most valuable feature. We have the ability to schedule seven days in advance, so we know exactly how we're running every night. If we need to make any changes, we can make changes to the daily schedule and we don't have to worry about changing masters or quarterlies. Changing our master schedule causes us issues. We have another product that doesn't work quite like this and when they have to change the master schedule they have problems. Because we have the ability to auto-build seven days in advance, we only need to change the daily and not the masters.

Believe it or not, there is nothing that we require. Everything we want is there. Everything we need, we get. The support we get, and the management support we get from SMA — we have a monthly review meeting with them — are fantastic.

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

It's fully scalable. We're currently reviewing moving it into our Windows estate, which is huge, and we're possibly looking at moving it into other areas as well. It's fully scalable, obviously with charges. We pay for a set of licenses to run on the Unisys. If we want it to run on other machines, we would have to pay more for the licenses, which is standard for any product.

We run about 2,000 jobs a day, and we are looking at potentially expanding it to 25,000 jobs a day, if our Windows systems move across. We're just about to go into proof of concept on that.

We were using an SMA product, Scheduler, but they stopped supporting that product and then we migrated to their updated product which was OpCon.

The initial setup was easy, as are the updates. It took us about an hour to do it, given the way that it's all written down for you. You can have a resource from them onsite if you want or you just load the software and it goes off and does it all for you. We've done it numerous times and we've never had a problem.

In terms of our deployment strategy, we already had an SMA product called Scheduler. What we did was we took a copy of our database, gave it to SMA, and they migrated it through into OpCon for us. They gave it to us and let us play with it, test it, and make sure it was working okay and then we migrated straight over to it. It was as simple as that. We couldn't find any problems and we migrated straight away. We've never had any problems with it.

SMA is fantastic to work with. They're knowledgeable, they know the products, and they don't try and force anything upon us. They're happy to work with us. They understand our limitations, and they still do to this day.

We've seen a tenfold return on investment. The relationship we have with SMA now is absolutely fantastic. They don't just do batch scheduling. They've come in and offered other services.

We're processing the batch a lot quicker, so our services to members are not down. The money is available and in people's accounts a lot quicker than it used to be. It gives us 100 percent availability. It doesn't fail; we've never had a problem with it. 

It's not expensive. It's a lot cheaper than competitors. Licensing is annual.

There are only additional costs to the standard licensing fees if we go above what we've agreed to. If we were to add a new Unisys mainframe, or if we add a Unix box or a Windows box, then obviously we'd have to pay for licenses. There's nothing else.

You need to be up-front and tell what SMA what you want. There are different licensing models for different setups. There are a lot of options, so it's really a matter of working out exactly what options you require. What works for our organization, Nationwide, may not work for the next company or the company after that. But they have a lot of licensing options available. And if there isn't one that you want, you can make your own with SMA.

There isn't anybody else that does Unisys. There's no other product for running automated batch on Unisys. Obviously, there are other companies in the market that can do Windows and other systems, but no one out there can really run Unisys. And Unisys recommends OpCon anyway.

I, myself, do not use other similar products, but Nationwide does. We use a product called Control-M from BMC. We can't find any advantages of Control-M over OpCon. The drawbacks of Control-M are that it's too expensive and an upgrade takes ages, days, to do.

OpCon is cheaper and the service we get from SMA is absolutely fantastic. The product is always growing. We're seeing it grow. We're seeing the changes, and we're seeing the changes that we're asking for in the product. We don't see that from BMC. That's why we're looking to move Windows from Control-M into OpCon, possibly.

My advice would be to work with SMA. Don't try and do it yourself. Work with SMA until you're comfortable; until you've got the training and the expertise. Work with them until you're comfortable taking it on without one of them there. Do your first install, your first upgrade, with SMA. It's simple, it's as per the manual, as per the training, but you need that little bit of confidence. That's what we've found. We've got that confidence now, and we don't rely on SMA at all to come in to help us.

The biggest lesson I've learned by using the product is trust it. Trust what SMA says. Believe what they say, because what they say is right. The migration is easy and they can do most migrations. Their training is fantastic, their support people are fantastic, and the support is out of this world. We're UK-based, so we have a UK team that looks after us in our daylight hours, and then we have a US-based team, and then we have an on-call US-based team as well, if we have problems. But we've never had to call them out. We've dealt with them, we've had our little questions and niggles, but they've answered everything, every time.

The product is always improving. The new release 19 has a load of new features for us. I've not really looked at it yet, but I think it's become faster, more slick, and a bit more user-friendly. They've taken on a lot of what customers have been saying about it. They've made some behind-the-scenes changes, but they've also made some enhancements to the way information is presented. My system, the Unisys, is quite old, so there's probably not a lot to change in that arena. It's probably more on the Windows and Unix side, which we don't use currently.

We don't really have users as such, because it's a batch scheduling tool. We have about 30 users who have access to it, but only for support purposes. We've got a team called Schedule and Batch which looks after things and check it. My team has access to it, but we very rarely use it and we're not limited on the number of users. The scheduling team is responsible for making sure all the batch work that is scheduled finishes correctly. We also have an ECC team, whose members are like operators. They look after the machines that run all the batches overnight. And then my team is a support team. We support the ECC in scheduling batch, if they have any problems with the product or with any of the batch jobs overnight.

For updates and maintenance of the solution we need just one person, me. My job is platform manager, but I'm also the OpCon subject matter expert as well.

On a scale of one to ten, this product is a 12. But I'll accept making it a ten.

We are using it for automating our core processing system.

Probably 65 to 70 percent of our operations have been automated by OpCon.

It currently runs all of our primary operations throughout the day, as far as we schedule everything through it. Our plan is to continue to automate the remainder of our processes, which are not automated, so we can get as much automated as possible.

The solution has streamlined operations. A good example is our ACH processing. We used to have somebody come in early in the morning to do all of our ACH processing (our incoming items processing). They had to be here early and run all the jobs manually. They did all the processing by hand. Now, it runs automatically at three in the morning. When they come in, all the work's done. They come in later and don't have as much work. It's reduced our workload drastically.

The solution has freed up employees to do more meaningful work as a result of automation. They don't have to sit there and wait for files to download. They don't have to stare at the screen while a process is running. It all runs in the background, doing it for them. When it's ready and prompts them, they know that they're ready to go on with the next part of their job which requires them to do something. A lot of employees love OpCon because it was a very mundane, cumbersome task to sit there and download files, waiting while it was processing. It was not exactly fun and exciting.

It's not so much that we have freed up an employee or gotten rid of an employee. It's just that they have more time to take on more duties. We haven't really had to add employees.

The overall ability to automate all our processing is the most valuable feature so we don't have one scheduler doing this, while another scheduler is doing that, and somebody doing this manually. We are able to automate our processing completely.

About a year and a half.

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.

We've yet to exceed its scalability. OpCon would appear to be able to handle a lot more than what we're doing. We are continuously finding new ways to utilize it.

We have four people in the IT department who are the primary management users of OpCon. However, we also utilize the Self Service portion of it, and the majority of the organization has access to that. There are 20 to 25 users of the Self Service, which allows them to execute jobs without being in the scheduling software. It's actually a web based portal where they can go, and there is a button there they can press to execute whatever job they're trying to execute.

We have had really good results from the technical support. Every time we needed anything, they have been right there. They usually have a really good answer or solution to the problem.

We find it very simple and easy to use. We had a previous product that was a scheduler which was overly complex and extremely difficult to use. We're very pleased with this one.

When we changed our core systems, the new core system supported OpCon. It didn't support our older product. As part of our conversion, we changed over to the OpCon product. This was one of the better things that we did.

One of the things which has really helped us is the time it takes us to build jobs and automate things. For example, if we decide we are going to go out and do a new process tomorrow, our previous system would take a week to 10 days, then require assistance from a third-party support company to get it to work. With this solution, we can do it in a matter of minutes without additional support.

I am coming off of a system that was so cumbersome to use that we couldn't even get it to do basic things without having to involve support all the time. Whereas, we've had to involve support very little with OpCon.

OpCon overcomes limitations of our previous automation tool. Our previous tool didn't work well with anything other than the particular core system that we have. For example, it didn't work well with Microsoft Servers, moving files around, and doing things like file transfers. Whereas, this system does that very well.

The initial setup was fairly complex, but we had great support from OpCon. They came onsite and helped us set everything up. From that aspect, it was very easy because we had them here helping us and working through all the issues. Once we went live with it, they were available again to help us make sure everything was working okay, and that moving forward, everything stayed working.

The deployment of OpCon took about three to four weeks. This deployment was tremendously faster than our previous automation tool, which took almost a year to get in place completely. Even then, we still struggled with issues (with our previous solution).

We did the deployment of the solution at the same time that we were setting up processes and automating it. We went live with OpCon about two months after we'd finished the implementation.

We were in the process of converting, not just our scheduler, but all of our core systems at the same time. So, we were doing everything at once. Our plan and schedule was to get it to work as fast as possible, then move onto the next thing that we had to get working.

It was internal on our part, but staff from SMA came out to help us set it up. They were actually onsite. We sent a person back to their facility for training. Then, after that training was complete, they then came back and helped us complete the onsite part of the installation and configuration.

It has reduced our processing times.

The total cost of ownership is about the same to our previous product. The costs are relatively similar.

The purchasing price was in the $30,000 or $40,000 range, but I don't remember how much of that was licensing or installation and how it was broken out.

We looked at a couple of different solutions. We looked at keeping the product that we had. We look at OpCon. We looked at another solution, but weren't impressed with it at all. It came down to OpCon or trying to figure out if we could interface our existing product with the current system that we had. We determined that wasn't going to be feasible, so we decided to change over to OpCon completely.

One of the problems that we ran into with our existing system, and why we were looking, was the overall technical support. It was very poor. It was a foreign product from Germany, and their technical support was not particularly strong.

Make sure that it fits well with your environment. Understand that it's not simply a single product automation tool. It can automate everything.

We were not utilizing automation as fully as we could. Once we got on the OpCon product, it really made a huge difference in that.

Because there is always room for improvement, I would give it a nine (out of 10).

We use it for batch job automation and batch processing automation.

It has reduced our manual processing times by a good 75 percent. We had over 500 processes a day, since we process jobs for over 40 clients. We were able to automate all that.

OpCon has definitely freed up our resources and allowed us to continue to bring in more clients without adding additional FTEs. Because we are a 24/7 operation, we have 13 employees. We have doubled our client volume without doubling our employees.

As far as streamlining, goes, the scheduling allows us to schedule jobs with different frequencies, and it prevents manual errors and eliminates keystrokes.

All of it is valuable. We've been very successful with it and really reduced our manual keystrokes and manual errors. The greatness of it is the flexibility of the scheduling and the integration of all platforms and processes. We have integrated it with everything from AIX to Microsoft Servers; with pretty much anything that we can.

The product is easy to use and it's simple to automate processes. It's a GUI interface. You don't require any special programming skills to use it.

If there is anything that needs improvement, it would be the file watcher. That could probably be simplified and easier to configure. To configure the file watcher you have to have a good understanding of OpCon. If they could improve the process of how it looks for a file, as well as the configuring, that would help.

Some additional logging-information reporting would also help. They have all the information there but you still have to search around and look back. It's not right there for you, where you click and can get the reporting. You have to know the system and do some additional searches. So reporting is another area that they can build on by simplifying it. 

Another area for our improvement is the upgrade process. We continue to need to bring in SMA OpCon to perform upgrades. If they simplified that and give more direction to the clients for performing upgrades, that would be good.

But other than that, we've been really happy with the product.

We've been using OpCon for over five years.

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.

We have been going from release to release with them and they've continued to add features and improvements. They have also added on products. So I think they are on track. They really have a solid system and I have confidence that they will continue to scale and bring in more features for our automation.

Their technical support is excellent. There have been several times where I have had to reach out to them and they responded immediately. They always have the answers to my questions and come up with solutions. I haven't had an incident where anything was extended over a long period of time. They have definitely been very helpful and knowledgeable.

Autobatch was one of the solutions I used previously. It was a free product that we downloaded, and then someone wrote some scripts. We didn't get to the point of purchasing it. OpCon is more of a high-end product. You get what you pay for. I don't know how we would continue to grow our operation without the help of OpCon.

The limitations in Autobatch which OpCon overcame are due to OpCon's ease-of-use and the configuration. I wouldn't have been able to train my team to start building jobs on the other solution if they didn't have a good technical background. With OpCon, it's much simpler.

The initial setup was straightforward.

When we first started, the deployment took about one week, and that includes training from SMA OpCon as well as Jack Henry Symitar. After that, all the upgrades take about two days.

Many of the other solutions I've used require a lot of scripting and coding. OpCon is more a GUI interface and I was able to get a lot of my team training on this with ease, without sending them to any classes. A lot of my team members can build jobs, from simple to complex, with SMA OpCon, without going to any additional classes.

It's very efficient and straightforward to implement a new job. If I get a request today, I can do it within the hour and have it ready to run. That's how simple it is. I don't need four hours' advanced notice. We started deploying things ourselves immediately after training. They came in and trained us, created some sample jobs for us, and we took the sample jobs and were able to recreate them. We just followed the steps and started applying them. That feature, where we can copy one job to another, is great.

As for our implementation strategy, we have a live system and we had a test system, so we built two systems. We started to build the schedule and the jobs on pre-prod system. Once everything was tested we went live, and we kept the test system for any other testing that we might need to do. Eventually, we got rid of the test system because we were able to do everything on the live system. We're able to test a job — not actually run it, but test it — before we deploy it.

When the SMA technicians came onsite during the initial deployment, our experience with them was good. They were very knowledgeable. They had a good understanding of the system and they gave us very good pointers. They were very efficient and on-schedule. The whole implementation process was seamless and very smooth.

We have definitely seen a return on our investment with OpCon. As I mentioned, we have doubled our client base without needing to increase our workforce. 

We are able to take on additional projects. Our operators are not just running batch jobs, they're monitoring batch jobs and it has allowed us to use them as resources for other things. They have been happy to be assigned to other projects, and they also like to learn more about OpCon. They enjoy building the jobs and doing the automation.

The pricing is over $100,000 for our credit union and I believe it's $89,000 for our clients, in total, annually.

There are additional costs with some of the upgrades. When we need to do upgrades, we will have Professional Services help and we have to pay for that. But the cost is maybe a few hundred dollars. Upgrades usually require two to four hours of their time.

I've used other job schedulers before and the flow of the automation wasn't that efficient, where OpCon's is easy. It's a lot of drag-and-drop. You can copy one schedule to another. You can copy one job to another. It's very easy to use and does not require heavy, intensive knowledge of OpCon.

There wasn't much else out there, at the time, for our core system. OpCon partnered with Jack Henry Symitar, so it was a product that was recommended by the maker of our core system. We didn't really do a search for an automation vendor. We were using one that was out there for free and when the opportunity came for OpCon, with the right pricing for our budget, we took advantage of that. Since then, we've been on OpCon.

What I have learned from using OpCon is that everything is possible within OpCon. Each time we have a new process, that's what we look at first. We try to build everything around the automation.

You will definitely see the efficiency and improvement in your day-to-day operations by using OpCon. My advice would be, during the implementation, to try to build as many sample jobs as possible so that you can reuse them.

OpCon is now managed by my computer operation team. Right now don't share it out to other users. We use it to automate our batch processing for over 40 credit unions that we support. When I say support, that means we do their core processing, their batch processing.

In terms of deployment of upgrades and maintenance of the solution, it's normally just one or two of my team members, or myself, working with SMA's support. They come in and we work with them and we get the upgrade completed and then we go live.

We are an in-house Fiserv Premier bank. This solution allows us to automate a lot of the core processing. 

This is outside a bit of the day-to-day. We recently did a branch acquisition of another bank, though not a full bank. With that, we had to convert all of their ACH transactions. It was a very complicated product that we received from our core provider, Fiserv, for some translation programs. It was very cumbersome to run through the process, convert it out, get output files, etc. Without anyone touching it, I was able to automate the full process from pulling in the files from this other bank, converting everything needed, and posting it to our customer's account 24-hours throughout the day.

We run the ACH process around the Fed window about four times a day: 2:00 am, 10:00 am, 2:00 pm, and 7:00 pm. We are not staffed all those hours. If someone were to actually run through all those steps, it would take maybe 15 minutes per each file.  This is if someone were to manually do it. So, that adds up. The main thing is we can let it run at two in the morning without staff.  It of course ran in less than 10 minutes, since it was automated. 

The product allows our full-time employees to be repurposed, not eliminated. We turn ourselves from operators who used do everything to reacting or being proactive. 

We have a night operator whose whole evening was just initiating, running everything, and watching it. My predecessor and I have been doing a staggered approach, taking these tasks out of the night operator's hands and putting them into OpCon. This still gives her the control where she can initiate via the Self Service portal. Now, we're hitting that phase where I can start to let it run on its own. She's become more reactive with the handful of things that she's still doing.

Our night operator loves it. Granted, she is one of those people who is always up for change and improving things. The way that she used to run things in the IBM mainframe was more isolated. She would see the output as a whole: That process A and process B were running, but she didn't actually know the details. With OpCon, she likes to have it up to watch it (not that you have to have someone watch it closely). She uses OpCon because it is easier for her to troubleshoot if something were to come up by seeing where things are at, what step it is on, and observing colors change.

The team members' reaction to the change has all been positive. Everyone has a different feel for it, but everyone sees the positive. I do my best to put a positive spin on it. It's not so much taking anything away from anyone. It's just converting it into OpCon, running it, then determining, "Is intervention needed? Can it run on its own?" 

Anything that is file movement related is awesome. Whether you are outsourced or an on-prem in-house bank (like us), you're not just fully in-house anymore. There are so many different third-parties that you work with now. With the amount of files going back and forth between end users or simply from the core to different vendors, this is the best part about the solution, streamlining and letting it run. Whether that's constantly throughout the day, certain times of the day or month, or a specific 16th day of the month, that's probably the most helpful because there is no operator that you have to wait on. We can just push it through a traditional FTP or SMTP.

It's very helpful, as we can move quite a few files all at the same time from a server level instead of having someone at their workstation downloading a 100 files. E.g., I created a process with our recent branch acquisition that we did early last year, where files were moving between the acquiring bank (us) and the selling bank. I put on our Self Service portal buttons for execution, that said, "As file's become available..." Then, my conversion team could have access without waiting on me to pull in stuff. If they knew that the selling bank put out some large conversion files, they can go out and simply hit a button. It would go out, grab it, and in a matter of minutes, be available to them on our public shared drive versus trying to pull that down via a secure site. 

The solution is what you want out of it. It's not something you can just quickly grab, try, run, and play with. You have to get the knowledge and train yourself. It was easy for me, but I also took the time to throw myself into it. There is a learning curve to a certain extent. You have to learn the rules. There are so many different ways that you can do things in it. If you were to survey five of my peers and me, I'm sure we all work on it differently. There is no one outcome of it. This is not to say that you can't pick it up out-of-the-box, but the way SMA trains you is on their standards of using it. You have to know the concepts of it, the different terms, and how you apply things. If you are using Windows, patch scripts, or mainframe things, it's not always an apples to apples thing. There's a bit of different translation into the product.

There is a current way to help hone in on detail that you are trying to visually show. For example, they have an add-in product (Vision) that we haven't purchased. The way the add-in product works is taking tagged data and categorizing it into a tiled report view.  It's actually live and constantly updating.  I like the visual / workflow side of OpCon, since I take the time to make it viewable from a visual standpoint.  Right now, I have a hard time if I want to translate what I'm doing to show folks who aren't users an overview. While I know SMA has an option for this, it's just more data. How can I show everything without my CIO needing to login to OpCcon and having me showing him the flowchart? A different way to report visually for other people to see processes would be my only improvement.

I would like to see more connectors to other various things. However, this has more to do with other vendors holding back with their applications.

Custom Templates for common jobs.  I do a lot of copying and pasting for jobs, that it would be easier if I could have my own templates.  Also Custom Documentation, that could flood to multiple job types vs. similar documentation on the same job being typed up.

A little over two years now.

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. 

70 percent of our manual day-to-day processes have been automated by OpCon. 30 percent of the overall daily and nightly processing take more time to do. Taking individual processes that were standalone and putting them in was one thing, but then taking and tying them altogether is that 30 percent. Basically, if you're taking the human element out of it, you have to build it so you are comfortable with it and can rely on it. That is where the time comes into it. I'm very thorough. I go through it and make sure I can cover common outcomes. For example, "Is this going to make sense? What if this happened?" You build in all this stuff so the way you rely on it, you do not have to worry about it. Whereas, with that human element, they know what to do and where to jump around. Someone who is seasoned will know how to make decisions along the way, and you have to sort of program some of that in. This doesn't apply for everything, but in some cases, it does. 

To get it expanded out to that additional 30 percent, it will probably be done in the next year with everything that is going on. Though, I would love to have it done in the next couple of months, but when an acquisition comes in, that is the priority.

I like going out throughout the entire bank and finding behind the scenes processes that other people are doing which we could help with. If it's just file movements, taking data that they are manipulating, moving things around, or simply just triggering a process, that is the fun side of my job. To sit down, look at a process, take it, and if I can, free up a quarter of someone's day by automating it, that is fun. Working with other departments in the bank, getting to learn a bit about their areas is a fun learning opportunity. Their tasks don't have to be automated either, it can be streamlined by giving them Self Service buttons. It is about making the task more efficient for the user.

The more things that are new and introduced in our environment, they go right into OpCon. It's more understanding, "How do does OpCon help us do that?" and, "Is there a tie in for it?" 

The scalability is huge.

I am the primary who maintains it. There are also two other individuals who are in a similar role to me: my immediate supervisor and another colleague. They both have access. My supervisor just relies on me to train him as needed, then the other colleague is able to jump in and interpret a lot of my stuff. However, we're divided. He's in charge of this and I am in charge of that, but we do cross-train. Beyond that, there is a night operator. She is Tier 1 support. She can help react to job failures and work on smaller things. If it's above her, then she defers it to me.

There are three different departments who use the Self Service besides us. They don't use the automation side of it, though. They use the Self Service to run a process or generate something. This is mainly our accounting department. They are very tied into it, but they don't see the automation side of it. They just know that they need to push a button and things happens. Also, our item processing area and the conversion team use the Self Service.

You have to put the effort into the training and learning. SMA is big on free training. They do monthly training down at their headquarter office. As long as you own the product, the only thing you pay for is your employees' travel expenses. The training is free. They are willing to train people and give them the knowledge. That way, you are equipped to do what you need to do. Then, obviously, they're available for support and assistance from there, but it's only for what you need above and beyond on that.

The technical support is good. I don't use it that often because they're very good about training you. It's more if I have a question, or something small comes up, then I can open a case. Otherwise, I have what they call blocks of hours. E.g., if I'm scratching my head or trying to think through how do I want to develop something? Then, I tap into my block of hours with a dedicated specialist who is assigned for our bank. It all depends on what's going on. If it's something brand new or different that I'm doing, then I'll touch base with them and run it by them. Otherwise, the block of support hours is mainly for upgrades and stuff like that.

Before, we did use file transfer stuff, which was a bunch of "if" and "then" statements. We were executing with that. But, that was very limited to what the application could do. Whereas, OpCon is a whole different game changer of what you can do from an enterprise level.

As a bank, there used to be a lot of full-time employees who would just run checklists all day doing manual steps. Whereas, with this product, we can automate the full day to a certain extent. There is still some intervention or items that are more user driven. Instead of our operators running the day-to-day, they just initiate certain phases of it. Then, we rely heavily on the Self Service portal and building out that stuff for our operators to use. They very much enjoy that.

Prior to OpCon, the organization used a lot of scripting in its own server. A big selling point for OpCon was its automation on an enterprise level. Converting everything to OpCon moved everything to one place. 

The nice thing at Frandsen is management sees the need and results of all the automation. They took an investment with my predecessor buying the product and we continue to see great results.

I was not here for this bank's initial setup, but I was previously involved with the setup of OpCon at another bank.

I've worked at five different banks and each bank operates differently in the way they have things locked down or how things are completed for projects. The setup was pretty straightforward. You just get the database and application up and running, and then, the mainframe agent up and running, which is especially important for a bank,. 

The database and mainframe side of the setup are always sort of tricky no matter what application you're working with, but it was pretty straightforward. It was up and running, then we trained and helped start to set up things for how we wanted to move forward. So, I thought it was good.

The deployment took about a day, but the bank that I worked for was very locked down when, e.g., trying to get things to open up and the right resources from SQL DBA. But, the actual application on the mainframe side, that's a no-brainer and seamless.

It took a couple weeks to deploy our first process because you have to test and get comfortable with it. We only automated a couple core things at the time because the main focus of getting OpCon in the bank was that they wanted a very cumbersome process streamlined.

At my current organization, I know that deploying the first process took them a couple months because they wanted to a lot of testing before they implemented it.

My implementation strategy is going for the easy stuff first to get a feel for it. Then, I can quickly turn things around on a small scale. Afterwards, I will graduate to that larger scale. With each implementation that I did, I evolved myself and how I wanted to do it, what I learned, etc. Because the other bank versus this bank were on two different mainframes, I had to translate a bit and think through things differently. I like doing the smaller things first, but now that I'm two and a half years into it overall, I can chew off the big things right away too. I'm not afraid of them, and they're fun, exciting, and more thrilling than the easier stuff.

We deployed it ourselves.

To deploy OpCon, you just need someone who is fluent on SQL DBA. SMA tells you there are two different approaches: If you want a whole group of people to help or if you want a train the trainer approach. 

When you take the human element out of it, someone is not interrupted nor are they delayed. They are not hung up on another thing that they are already working on. That's the nice thing about OpCon. We have the time to react to things and are not holding things up. So, if you add up those 10 minutes 15 times a day for our processes, that's quite a bit, especially for the repetitive stuff. It's easy to automate it, then it just does what you need it to do. It just runs. 

This has overall reduced our data processing times in our environment by approximately 50 percent. The nice thing is we can spread work out. If you need to have employees onsite for the ACH processing, someone has to come in early, then probably stay a bit late on that end of the shift. Now, we're spreading it out. With the ACH, if you're doing it with just an employee, then you're only doing it during working hours. Now, we can run things over a 24-hour span, spreading it out. 

There are different add-ons, like the Self Service or Vision model. It all depends on what agents you have in your environment. We have a mainframe and Windows, and while I think SQL is free, SAP or anything beyond that has different connectors that might need a license.

At my previous company, we did not look at other solutions because we knew SMA was the most well-known within our industry. 

At my current bank, they did look at HelpSystems. It was between HelpSystems or SMA OpCon. Ultimately, they went with OpCon.

Take your time. Think about it. Once you start to create different concepts and learn them, come up with naming conventions, your own rules, and go by them. This way, everything is similar. It's easier for me to train my operators if it all looks the same.

Ease of use depends on how you set it up. It is there, but it all depends on what you want to do with it and how much time you want to put into it. If you just want to move some files around and keep things looking the same, it is easy to use. But, if you want to do some tricky stuff, you have to put some time into it, making it look clean and understandable for you and everyone else. You also have to document a bit, but that is sort of case by case.

I come up with rules, trends, conventions, prefixes, etc. that I'll find sometimes six months later. Then, I'm like, "Ah, I like this a lot better. I'm going to set this as my own standard going forward." I am evolving myself and constantly making it easier for me to use.

The solution expands my creativity when looking at processes.

I would rate the solution a nine (out of 10). It is in its own league. OpCon makes my job so much easier. SMA is a great company and partner.