What is our primary use case?
Rocket Zeke is batch software. It's an essential component of the solution I provide to my client. I work for a Canadian insurance company and most of the information they manage is in a mainframe. All the batch jobs go to Rocket Zeke.
Many teams are involved in getting this to work. Teams are dedicated to batch processing 24 hours a day, and there are support teams. There's also a lot of engagement with other groups that use the product. Including those that use the agent, we probably have 500 users. Around 400 are end-users. The others are part of the staff needed to keep the solution working.
How has it helped my organization?
Rocket Zeke is a reliable solution that gets a lot done quickly because batch processing usually occurs at night. Rocket Zeke finishes all the insurance processing overnight so it's available the following day when the company needs it. Its direct impact is behind the scenes. The client sells insurance, and Rocket Zeke ensures they have all the necessary information, like records and reports, in time.
What is most valuable?
Two features are valuable. One is Rocket Zeke's ability to integrate with the mainframe, which is the main processor using the agent. It works on any computer, so users don't have to wait. They can use their laptop or any other way to connect and securely access all the necessary information. The other valuable feature is automation, which is an integral part of batch processing.
What needs improvement?
I work a lot with the support side when there are issues. I see a lot of confusion about the various licenses. The licensing model is somewhat complicated. The product license has to be installed. Sometimes, when a license is expiring and I need a new one, it's hard to understand where those licenses are in the guest support portal. I've discussed this with ASG, and they've acknowledged that it's too complicated.
It has had an impact. It's not that the product doesn't work, but we get messages from the user worried that the product will run out of support and their whole operation will be affected.
For how long have I used the solution?
I've been using Rocket Zeke for five years.
What do I think about the stability of the solution?
It's rare to find a totally stable product, and we've had some issues where the product had errors. When that happens, we must stop everything and turn it over again. Generally, it is highly stable, which is necessary because we can't have downtime with a product like this.
What do I think about the scalability of the solution?
Rocket Zeke is highly scalable. It fully leverages the mainframe while enabling connectivity with other platforms. The company is constantly growing, and we've had no problems getting Rocket Zeke to handle more information. Scalability is a strong point.
How are customer service and support?
I rate ASG support an eight out of ten. They respond quickly 90 to 95 percent of the time and provide excellent support. However, some issues take a long time to resolve. Some support requests for information take months. They say they're working on something but don't give an ETA. Sometimes we have to wait weeks or months for a solution. That's only five to ten percent of cases.
How would you rate customer service and support?
How was the initial setup?
Rocket Zeke is deployed on-premises. We have a massive mainframe where everything is deployed. It is deployed in stages: test, alpha, and production. It also takes some time to deploy a new version or fixes. It's crucial that we take time to ensure it works correctly because I've seen other solutions damage a complex product. We need to be careful to avoid issues during deployment. It's a step-by-step process to make sure everything's working properly.
Everything is centralized because the mainframe is located in one computer center, but Rocket Zeke can connect to agents installed on other computers, so there's connectivity to different locations.
Deployment involves multiple departments and teams because of how widely the product is used. Many parts of the company take advantage of this product. It is used in every aspect of the insurance process, and some administrative departments use batch processing. Regular maintenance is essential. I'm primarily responsible for maintenance, but I have a team of people who do part of the work.
What's my experience with pricing, setup cost, and licensing?
I don't make purchasing decisions, but the decision-makers tell me they don't switch to other solutions because this one has the price they need. Pricing is part of their decision to stick with this product.
What other advice do I have?
I rate Rocket Zeke an eight out of ten. Rocket Zeke has many features that other solutions lack. It's a more open product. Some other products only allow you to process everything on the mainframe. Rocket Zeke has more flexibility and connectivity. This is essential because it allows end-users to work with the product without understanding how to use the mainframe.
My advice to prospective users is to spend time working with the experts to understand if this product fits their needs. It's a far-reaching product with many capabilities, but you need to learn how to take advantage of all the features.
