Pega Platform Reviews

Our customer base is varied, ranging from insurance to banking to government. In the insurance domain Pega is used for things like policy, as middleman management, policy administration and claims administration. In the banking realm, it's used across multiple areas from CRM systems, customer service, sales automation, and things like loan origination, payment investigations and payment arrangement management. In the government sector, it's used particularly as a case management software to manage processes.

Most of our customers are enterprise businesses, we are partners of Pega and our company functions as a system integrator. I am co-founder and Chief Technology Officer. 

One of the valuable things in the solution is that Pega offers a unique environment where its entire architecture is very unified, meaning it's used free across multiple areas. In other products, say IBM, and other solutions, the products range across several solutions and include separate components for analytics, separate components for the UI and a separate component for business roles. Pega, on the other hand, is one unified architecture and that is very valuable. The second thing is that Pega is model driven architecture so building something up on it from models is very quick. 

From a room for improvement point of view, what I've seen is that many customers want solutions that directly meet their requirements so while Pega has somewhat vertical solutions on Pega customer service and sales automation, industry and customer experts expect more out-of-box solutions to be readily available on Pega.

It is the same for additional features - the customer expects more business solutions to be directly available on Pega. For example, when I say business solutions, Pega could have a business solution on customer service, a business solution on sales automation. Pega may not have a proper business solution for LOS, or Loan Origination System. These are common business solutions which could be made available in the solution, it would be very good if they could focus on the direct business solutions which customers expect over here.

I've been using this solution since 2003, so 17 or 18 years. 

As enterprise customers are using it, you can tell it's stable. It's one solution which we've basically used and worked both on-prem as well as on cloud and it's one of the other unique value aspects of Pega, that the same solution can work on cloud as well as on-prem. 

From a scalability perspective, it's scalable. In terms of high volume, we have some applications based out of Vietnam which have millions of cases, so in terms of the number of cases, it's highly scalable. We have other customers who also have a high volume of users. 

Because I've been working with Pega since 2003, I can see the improvements that have been made in terms of how they go about establishing contact with customers. These days, it's pretty easy and accessible.

Initial setup is quite straightforward. Deployment time is based on the actual size of the project. On average, it can take anywhere from three to five months to build. Usually, the team servicing from our side is around five to seven people and from the client side it's usually a project manager and a couple of others. 

PegaRules is a very powerful rule engine. It's a very powerful platform to build any sort of solution onto. Where a customer makes mistakes is when they underestimate the business expertise of a partner, so they really need to ensure that initial implementation is right. It is very important to understand who is implementing it on the ground. If they don't understand the business requirements and the required business outcome of management, it can be awkward, and not in line with expectations.

The main thing I have realized is that understanding the business problem and understanding the required outcome for the customer is very important. One of the biggest business areas is to focus on understanding problems and the kind of business outcome the customer requires. It's really about understanding the big picture. 

I would rate this product a nine out of 10. There is always room for improvement, but I've seen many customers getting very good value out of this solution.

In terms of features that I have found most valuable, there are lots of new things in Appian BPM, maybe six in this newer version. Earlier, what we needed to do if we wanted to deploy some code into the other environment was to upload it into the environment, take a patch from the other environment, patch it, and import it. Nowadays it is easier. There is a new feature in the Admin Console where I just need to click on that environment, pick a patch, and just select the environment. Then I see whether it is queuing in the scheduled environment or going for production. I select the environment and I can directly deploy that patch. This is a very good feature of the current version.

There is a very well implemented UI side - the front-end visibility. There is a new progress bar that allows you to see your progress. There is a very impressive UI design that they've embedded into the BPM tool.

In terms of areas that need to be improved, I would say the timeout. This is because sometimes when we are patching some data from the database, we are getting added as a timeout. I would like to build a solution for that or to improve that feature, because by doing so the process will be trimmed. Sometimes it gets stuck just due to taking so much time for the user in the back-end data from the database. I think all the other features are very good.

Additionally, I'd like to select the availabilities. I'm using the earlier version now because it is on-premise implementation. If I go on the newer PGi for a couple of days, the latest version, then I will able to see what other additional features we need to have in the BPM tool.

I've been working on Appian BPM tools for about three years.

I do not have an issue with stability. I'm completely fine with that.

It is definitely scalable and I know that is a very good feature of the Pega BPM and Appian BPM.

I have never contacted support. 

But we have one help ticket raised, so technically I do support the production.

I like Appian BPM. In Appian BPM I need to code for the components. If it's a bigger program, depending on the sizing, I read about using Pega BPM for that. But I'm working as an Appian Lead and working on Appian BPM tools for about three years.

About a year ago, I was working as a DOS developer and then I moved to Appian BPM and Pega BPM. I get feedback from the users. Based on the data from the POC, I present that to the user and if there is any implement I'll do it on the same day and avail it to the user. If they're okay with it, then I can go ahead and create the application and develop it for the solution.

Working as a DOS developer I'm coming from a different place. I came to know about this BPM tool from the website and learned that it has very good features. So that's the main attraction to BPM tools.

The initial setup is not complex, it is easy. For the first time user, we do have the trial version of it. Nowadays, as you are aware, we have data in the Cloud where it is like MySQL. It will take under 30 minutes. Not more than that.

We are working in Agile. So there is a sprint of two weeks. After each and every sprint we have to be looking forward to the after-sprint plans. So the solution has been deployed after each and every sprint to the queue and on the decided date, to the production.

I used a number of integrators for my current project that was as a re-seller. I don't have experience with implementing. On my current project, I do integrate with the re-seller that does business with Appian. We are just consulting for the solution at our end with an integrator at Appian by using the data authentication.

I would definitely let people know about it. Let me give you a scenario. Let's say there is a banking system. Generally, people come to the bank, fill out the form, and submit it. Then a record will be created in the system. So what happens by using the Pega BPM is that we can clearly identify the flow - how you do it by using the different user input tasks. This is appealing to the user, to the customers, to everyone. Definitely I would like to get a return on that and let them know that if they use this BPM tool, more than any other technology tool, it has the most complete set of tools for the system.

On a scale of one to ten, I'd rate it an eight. This is because it is easier to use than any other product and it is more secure. All of our software was developed in Java and as we know Java is a secure language. 

There are many more features. It is easy to use, easy to understand, easy to implement and easy to enhance and we can do it as a Cloud. Also, it is very user-friendly. Nowadays, it's on Cloud so we can access it from anywhere. There is no location per se or any system requirement.

Pega BPM can be deployed on-premise and in the cloud.

All the scalability issues are addressed with Pega BPM because you can create enterprise-grade solutions with the architecture it has.

Pega BPM has a use case in every sector and area, such as manufacturing, insurance, vendor suppliers, and vendor collaboration hubs.

The most valuable feature of Pega BPM is its architecture.

Pega BPM could improve the UI, it is poorly designed to have a good UX experience.

I have been using Pega BPM for approximately six years.

Pega BPM is stable.

Pega BPM is enterprise-grade and scalable.

The support from Pega BPM is very good.

Using Pega BPM on the cloud is simple. Within five minutes you can have your own Pega BPM instance.

The licensing model from Pega BPM is too complex and is more expensive than other solutions, such as SAP. The overall price of the solution depends on the use case.

My advice to those before purchasing is the UI capability is not good and the cost of the implementation generally is higher in the implementation.

I rate Pega BPM

They use it for marketing and case management. It is also used for workflow process automation and market intelligence, using the solution’s AI capabilities.

The case management functionality of this solution has been most valuable.

There is a scarcity of resources who have worked with this solution before.

I have been using this solution for eight years.

This is a stable solution.

This is a scalable solution.

I would rate the customer service for this solution a four out of five.

Positive

The initial setup for this solution is not that complex.

The enterprise product has the best features as a cloud product. It is the market leader in the BPM space.

I would rate this solution a nine out of ten.

We are a strategy consultancy for someone who is looking for a Low-code No-code platform for the utilization of digitized service processes. We can determine if Pega BPM is the right fit for them because it can be deployed on the Cloud,on-premise, Kubernetes, and Dockers. We are in discussions with customers with many other solutions, such as OutSystems and Mendix. From a strategic point of view. We're not going to implement only one service tomorrow.

We mostly use European providers. We do not use hyper scalers because of privacy concerns, such as Google, Microsoft, and Amazon.

We use Pega BPM for simple service management processes. We are a consultancy that works for the government. We look at public services and how public services can be supported. These new types of workflow technologies where you to have end-to-end case management. They can be used for public services processes that are created on these platforms.

Pega BPM could improve the artificial intelligence capabilities because they are always valuable and case management for all types of industries is important. Additionally, the reporting performance management capabilities could be better because you want to have insights into how your processes are working, such as Cloud protection. The whole range can be better. However, the platforms are improving every year, they are on the right track.

In the next release of Pega BPM, they should add more ways to do the customer interaction fields in the portals.

I have been using Pega BPM for more than one year.

Pega BPM is scalable. If you have larger data models, for example, thousands and millions of transactions, they have their limits. Larger data models need to be improved. It's not only technically scalable, for instance, if one organization develops a solution built on ServiceNow or Pega BPM, how can you transfer the solution to the next organization that has the same platform. They have a marketplace on most of the platforms where third-party vendors can show their services. For a public organization, if you develop a small application, the next town could use it the same way. How to transfer easily from one to another one. It might not be a relevant case for private companies because you are in competition. There's no need to give away knowledge. However, in the public domain, it's a different case but it's very special, nothing in general.

The technical support of Pega BPM is very good.

If you work with any of those platforms such as Pega BPM, Mendix, OutSystems, or ServiceNow, they have different sweet spots. You should always think about what you really want to accomplish. What do you want to do with those platforms, you have to choose between Pega BPM or ServiceNow. You have to decide what is the right provider, and it is not one-fits-all. 

The platforms are used to be faster. You have citizen developers who can build faster solutions but in the end, if you have no governance, no strict rules on how to use it there can be problems. For example, to put out a fire somewhere, you can do it in 10,000 different ways. If you don't have strict rules, how to do it, you might end up with a crazy solution that you can't manage over time, such as the maintainability of those solutions or of the platform ecosystem in general.  You need strict governance or rules of what to do and how to do it. Otherwise, it will be like a crazy zoo of different solutions and you don't know what it is, how they work, or why they work. If everyone is able to use a solution but they are not using it in the same way it can be improper and this is why governance and rules need to be applied.

I rate Pega BPM a seven out of ten.

Pega BPM is good, it is not the worst solution you can find on the market. However, it depends on what you're looking for. It has to meet the use case that you are looking to solve. Other solutions, such as OutSystems and Mendix, they're more open-minded, you can do whatever you want to do, but they don't have strong case management. In my industry, it's more or less, very simple service processes.

I've been using Pega BPM for insurance underwriting, claims management, and pricing.

What we like about Pega BPM is their case management feature which we find powerful. We also like its workflow capability.

The licensing model of Pega BPM is tricky, especially for first-time customers, so it's something that they could improve.

The technical support team for this solution could be faster in resolving tickets.

I've been using Pega BPM for five years.

We are satisfied with the stability of this solution.

We have been able to use Pega BPM in different lines of businesses for the past few years, so we find it scalable.

We faced some issues so we had to contact technical support. We raised the ticket and it was resolved. It took a week, but it was resolved.

We implemented Pega BPM with the help of a consultant.

This solution's licensing model needs to be improved.

It's a yearly subscription, but there are no extra costs apart from the standard licensing fee.

I'm using one of the latest versions of Pega BPM: version 8.

It was the IT side, with the help of a consultant, who handled the installation of this solution, so I didn't have much visibility into whether it was easy or complex. It was done over a period of seven to 15 days.

The number of end users using Pega BPM in our organization is 35 to 40.

Deployment of this solution did not take many people: just two people, but for maintenance, we have three people, so deployment and maintenance requires a total of five people. All of them are engineers.

We use Pega BPM almost on a daily basis. We currently don't have any plans of increasing its usage.

I'm recommending this solution to other people, particularly if it is a good use case for them.

Pega BPM is the first business process management software we were able to try. We had an old tool we were using, but it was not a BPM software. 

My rating for Pega BPM is eight out of ten.

The most valuable feature is the ease of deployment.

We would like to have a better ability to customize PegaRULES.

In Pega, it is very important to have good overall system performance. As such, the performance should be improved.

Better automation would be helpful because I would like to see all of the manual intervention removed.

I have about five years of experience giving applications support for PegaRULES.

We cannot say that any application is fully stable, as it depends on the particular requirements. For example, if we have application automation then we need to make it scalable, but nothing is 100% perfect.

This is a scalable product. We have perhaps 50,000 users across our clients who use it.

I do not generally contact technical support. Instead, our core idea is to determine the issues and resolve them ourselves.

It is easy to install PegaRULES. There are no major issues because we have the proper guidelines for release and configuration. The length of time needed for deployment depends on the requirements for each client.

We have a complete in-house team that performs the implementation and deployment for our customers. This includes creating new rules and definitions, determining which policies are required, managing the system, giving support, and release management. 

We are planning to move our system to the cloud within the next six months, so this is something that we are preparing for.

The suitability of this solution depends on the organization, but in general, I definitely recommend PegaRULES. When assessing the appropriateness of this product for a client, I would first study their requirements.

I would rate this solution an eight out of ten.

We are using Pega for developing our workflow applications.

It's a good tool for workflow automation.

It's stable and secure.

In regards to the integration, more APIs may be required.

It needs more integration with other platforms.

I have been using Pega BPM for six months.

It is stable, and it is a distributed architecture.

We have approximately 1,000 users, but it can scale up to approximately 15,000.

It's a scalable product.

We have not contacted technical support.

Previously, we did not use another solution. It was all manually done.

The initial setup is straightforward, nothing complex.

It took two or three days to deploy. We are still new to the system.

We completed the implementation ourselves.

We have a complete team of administrators and application administrators who maintain this solution.

It's a user-based license where, as you scale the numbers of users, the price increases.

They also price base on the number of cases you have. 

They have varieties of pricing models.

Currently, we are working on the deployment models. 

We have not yet started on how to do automation of deployment. I think it's there, but we have not explored it yet.

We have in-house applications that we want to implement automation for. We will be using this software to automate those products.

I would recommend Pega BPM.

I would rate this solution a nine out of ten.