Pega Platform Reviews

Our use case of this solution is for clinical case management. I'm the senior vice president of the company and we are customers and end users of Pega BPM. 

The solution has assisted us by automating our workflow. It supports the process management of medication therapy engagements with patients. 

We appreciate that this solution supports the size and scale that we need.

This is a very expensive product and there is a lack of availability of the Pega skill sets, the resources. 

I've been using this solution for 10 years. 

The solution is stable. 

The solution is scalable, we have around 1,000 users and don't have any plans to increase that number. 

We deployed ourselves and I don't recall any issues. The solution is not maintenance heavy and we have a few people responsible for upkeep. 

Licensing costs are very high. 

It's important to check all options and ascertain that this is the appropriate solution for you. There are other features that products like Camunda provide,   but as you need to scale and get more sophisticated in your process management, Pega becomes a better option.

I rate this solution eight out of 10. 

We have two different projects right now using Pega BPM. In one we are doing a migration of applications regarding claims, and the process requires orchestration between different providers that this company needs to organize the work. When you have a claim and you need a repair for something, we need to organize the work that we send to the provider. One, for example, is doing water claims. Another one could be about car claims. These are our main processes right now for Pega BPM. 

The other project is regarding onboarding customers in a bank. We use Pega to orchestrate the different aspects we need to complete the onboarding for our customer.

One project is on-premise and another one is on cloud, but we started using the Pega cloud and right now we are migrating to Azure Cloud,

Yes it has improved the KPIs. For example, in the insurance project, the time required to complete the project with Appian was around a month and now with Pega it is around two weeks. We still have a lot that is manual, but we reduced the time of the process.

The best part of Pega, for me, is that they let you reuse a lot of the aspects in the product.

The main problem with Pega is that it is quite complex, so it is very difficult for the developer to learn. Sometimes it is like a black box where you can't develop other things. When you try to modify something on the product it is quite difficult. Also, when new people try to learn how to develop in Pega, it is quite difficult to learn, and it's a big product. I think that is the problem.

Maybe they could try to make an easier implementation. I don't know how. Maybe with more information on the Pega platform, in the Pega academy, or modifying the application to make it easier to implement. 

I started using Pega BPM 11 years ago.

Pega BPM is stable.

Pega BPM is more scalable than Appian. We can have more processes running, more data in the server, and the performance is better.

Both of our projects are in production right now, but in one of them the customer will require around 3,000 users. With the other project it will be around 300 people.

Right now, there are two or three people running this kind of project, so we will need more people for that.

The plan for Pega in both projects is to continue for around five years more - so we have a lot of work there.

We don't have too many problems. It's true that we have more ticket service requests with Pega, but they answer quickly, so I think that is good.

In one of our projects, we previously used an application called .NET by Microsoft and the solution was so slow. Well, I think it was created 20 years ago so the modification on that application was too slow because the code is much longer and you have to read more lines of code so it was not easy to modify the processes on that application. It was for that reason that we tended towards Pega, looking for more agility on the modifications and giving control to the business people to modify different business rules for themselves.

The initial setup is complex.

When you are doing a project in Pega, it is more complex than the processes that you are normally going to implement. When the product is complex to learn it's more complex to develop.

The deployment time is not too much. It is about the same as with Appian when you have the configuration down, no more than one or two hours.

Normally when we use Pega we are thinking about a more global application that you can use in different countries or for different areas.

It requires a Pega architect from the company.

The pricing with Pega BPM is a huge problem because it is quite expensive for the Spanish customers. It is higher than other BPMs.

My advice to anyone considering Pega BPM is that they have to think about that they want to do on it because not everything is possible. It is similar to Appian, so really think what you want do you in Pega. If you are thinking about moving an application towards innovation on Pega, it's not a big solution to do it. If you're thinking about something more, it's a good product. Don't spend money on that because Pega is more expensive than other products.

The main lessons regarding Pega are that you need people who know how to use it because it is a complex product. If you create the application from the beginning, you are going to need a lead system architect to do it, because if you don't do it correctly, the use and the good points that Pega has could be an issue for you. The main point here is that you need people who know Pega really well in your team.

As a product I have to say that I think Pega BPM is the best right now, and the only problem that we have with Pega is the people. So if I focus only on the product, on a scale of one to ten, I have to say Pega is a nine.

The product is so good. The only problem is that the people who work on it need more knowledge.

For an upcoming project, my manager told us to look at all the different capabilities between the Pega, Appian, and the Camunda. We don't know the use case yet. We need to know the use case, however, at this point, we are just exploring different tools, BPM tools.

The integration is good. It can be capable of different integrations. 

There is a Pega Decision Hub, which is just a text-based analytical site. Based upon the text-based analytics and it can decide and trigger a case.

There are a lot of new features in Pega that are great.

I like case management in Pega. For the case management applications, so it's really fast to develop and it can scale and be extended based upon the business requirements.

The initial setup is pretty straightforward. 

The documentation and training available are great.

Pega is coming out with Pega Express, which is kind of a low-code development platform. The business rules can be built in a Pega Express Portal, which is more specifically built for business users and not technical users. That way, even non-technical people are able to build their own business processes easily.

The local development approach is good in Pega, however, cost-wise, it's getting expensive. That needs to be addressed.  

With Camunda, containerization is the most helpful feature. It can containerize and it can have its own deployment process. Pega may be adding that feature in a future release, however, right now, that's lacking and needs to be addressed.

I'd like to see Pega support microservices architecture, which it doesn't do right now.

We have been using the solution for more than six years.

The scalability is excellent. It can scale as much as you need it to. It's one of the great aspects of the product.

I've never directly contacted technical support. I can't speak to how helpful or responsive they are. We have our own internal team that can troubleshoot.  

That said, we used to connect with Pega on issues and it's my understanding that support tickets can be addressed very quickly. Support-wise it's very extensive. 

I also trained in Appian. 

The initial setup is straightforward. There is no complexity. There is documentation around the installation process and upgrade process as well. Pega will also provide you with good training materials in the Pega Express Portal, which is helpful for teams who are planning for new developments. That way, they can learn easily and understand everything.

It's a great product, Pega, however, cost-wise, it is a little expensive compared to other BPM tools. That's where I feel that they can improve.

Now, we are exploring other software, like Camunda. We just want to see the different designs or decide which tool is better for our application.

We are a customer and an end-user.

We have been using Pega for more than six years, and at this point, we also want to just explore the other BPM tools. It's kind of for considering cost efficiency also. We are looking at the cost of the development effort or the scalability of the tool. While I like Pega, I'm just exploring the other BPM tools with respect to Pega.

While it depends on the application you are using, if you're planning for an enterprise application that can interact with different applications, Pega would be a good option.

Sometimes if you have a smaller workflow, for example, if you're just introducing a smaller workflow in an existing application and you just want to leverage only that workflow-related feature, you don't need Pega. You can just have any workflow tool, like Camunda or Appian. Cost-wise, Pega may cost you more.

If you're planning to leverage all the features in Pega, like case management and low-code, no-code and RPA, robotic process automation, and other high level or case management, if you are planning to leverage all these different kinds of features that are available in Pega, just go with Pega. And if you're just planning to leverage only a kind of workflow, you don't need to go with Pega. You can just go with other BP flows or BPM process models like Camunda. 

There are a lot of features that you can explore in fault tolerance and error handling, exception handling, et cetera. There are other items as well if you're in the development stage, and something like Page will likely be helpful. I don't know of other tools that will support anything to that extent.

There are still some limitations in the solution. I'd rate it at an eight out of ten, as there are still some improvements that can be made. 

The solution is basically a quoting application. When insurance brokers or internal users have to call or do insurance quotes for commercial insurance, we use Pega. The insurance we cover is for outdoor coverage and for a casualty to property, as well as casualty insurance.

The solution's case management is its most valuable aspect. 

It's basically an open architecture based software, which means the main aim of the software is to provide a low-code application development environment. It has several authoring tools on the UI flow and makes sure that you can put in a lot of gadgets and create the screen very quickly using those gadgets.

Right now, it has a pretty good feature set. It has case management and BPM workflow as well as robotic automation. It has decisioning. It has chat and virtual assistant support, and we just implement it on the cloud, therefore it's a pretty robust feature set.

They use something called a unique model-based architecture. During development, where the database and the UI, everything comes from one single piece of architecture. Due to that sometimes the enterprise architecture teams do not like it due to the fact that it forces them to use just one piece of architecture. If these could be more modularized, then it can be easily deployable in different kinds of scenarios in organizations, it would be much better.

However, they are kind of tightly coupled and it's difficult to separate everything out. Still, I would say it is an improvement to consider for the future. Id they could decouple the various components so that it gives flexibility to enterprise architects to deploy what is most needed as part of their enterprise architecture strategy, rather than getting kind of, looking at the only way the product handles, it would be a stronger product.

They are currently spending some time on improving the product with respect to machine learning, especially related to robotic automation. They probably could be a little more adept on that area would help.

It's very difficult to change many things unless somebody puts in the time to figure everything out. However, Pega could learn from all the customer service calls they get and categorize them in order to do an automatic form-based or customer service based response. If they could set it up to everything automatically, then that would save a lot of time and headaches for companies and help them troubleshoot and work through issues faster.

We've been using the solution for almost ten years. We haven't used in the last 12 months too much, however.

We have found a few issues on the solution and we work closely with technical support to help fix them. While it is largely stable, we do find we need to keep up with problems and work closely with Pega directly to address and fix them when they arise.

In terms of scalability, provided you throw hardware at it and you do a proper production implementation approach and alignment strategy, it's scalable. 

You can go up to 2000 to 3000 users pretty easily. It's just that you need to throw a lot of hardware at it and make sure that you manage and create the web servers required. You need to create various pieces such as database servers and things like that, to make sure that you get the performance you need for those 2000, 3000 users.

The solution is being used continuously. I'm not sure about the increase in the usage, but at least it's serving the purpose as needed for the brokers.

It's a complex piece of software. For that reason, we did find some issues and I was kind of instrumental in working with Pega on their global support model. We had weekly calls to review. They have a process to track issues that are unique. Sometimes it's handled by their support network, and sometimes the issue is taken up to be dealt with by working on the next version. For us, triage calls are made every week.

The initial setup is never straightforward. It's always complex. Organizations deploying the solution will need a Pega admin and experts. It's not like anybody can just walk in and install it onto a PC. It needs a lot more performance concentrations and much more integration considerations. Therefore, it's a little complex.

In terms of deployment times, on-premise, it takes a little more time, and I would say it would take maybe about a month. However, now, cloud implementations are pretty quick and go much faster.

In terms of maintenance, we do need someone from the company to help us manage the solution.

We did solicit outside assistance for the implementation. We actually used both the Pega professional services in the beginning for a short time and then a subsequent implementation was done by an integrator.

There are multiple models. They have enterprise licenses for each server, for the product version. If you're doing it on-premise they also have per user basis on their cloud. 

It depends on what your specific need is. Those vary from customer to customer, depending on the number of users and the volume of business and things like that. There's no, set price, or a specific quote and everybody just follows it. It's more they work out the enterprise licensing agreements or per user basis with respect to each client.

I joined the company when those decisions were already made. I wasn't part of that decision. However, in a lot of places where I've consulted as a digital transformation consultant, we did definitely compare Pega with competition such as Appian and other BPM, and even Salesforce and other workflow systems as well.

We're just customers. We don't have a business relationship with Pega.

Pega BPM is definitely one of the topmost BPM packages out there. It hits all the right notes for a containerized implementation. The only thing you need to be careful is that you definitely need experts to help you along the way, in both the design and the requirements capture. They have an excellent requirements capture tool as well. However, if somebody needs to be trained on that, you need the help of experts, both on the software architecture as well as business architecture as well as the Pega admin. Eventually, these kinds of positions will either require a company to staff up or they will need to work with a system integrator. 

Most of the companies work with system integrators due to the fact that Pega professional services are definitely very expensive. Organizations will work with a company life Cognizant or Accenture or others to really help them out along the way.

I'd rate the solution nine out of ten.

The latest releases of PegaRULES are scalable, advanced, and can be easily integrated into your environment.

PegaRULES should provide a more drag-and-drop interface to make it a low-code, no-code product.

I have been using PegaRULES for about a couple of years.

PegaRULES is a stable solution.

PegaRULES is a scalable solution.

The solution's technical support is good, but getting professional support is a bit expensive.

Positive

The solution’s initial setup was easy.

The solution's overall deployment plan was for around a couple of weeks.

PegaRULES is a good product, but its pricing is a bit on the premium side, especially for professionals. Licensing-wise, PegaRULES is at par with market rates.

Overall, I rate PegaRULES a nine out of ten.

The company has a strategic partnership with Pega. I was the general sales manager. 

This is a customizable product. It's low code and can be restored quickly if needed. 

The solution is expensive and it put many of our customers off. After a while, the company was no longer prepared to work directly with customers which created problems. 

I recently stopped using this solution because I changed jobs but I had used it for 18 months. 

The product is stable. 

The technical support is very good. 

Positive

We helped our customers implement this solution because the company had its own in-house dedicated team. 

This product is quite expensive. 

This product is suitable for pretty much any size of organization. I rate this solution eight out of 10. 

I mainly use Pega BPM to look at conversations and try to create a better experience for the customer.

Pega BPM's most valuable feature is the use of CDX to solve problems.

In the next release, Pega should include process mining.

I've been working with Pega BPM for three years.

Pega BPM is stable - I haven't seen any glitches because of usage or anything like that.

Pega BPM is scalable.

Pega's technical support could be better.

Neutral

The initial setup was complex.

It was easy to learn, adapt, and go through Pega BPM's low code builders. I would give Pega BPM a rating of nine out of ten.

Pega is an Intelligent Automation Platform that has evolved from a BPM perspective. This allows teams using this solution to address complexities without having deep knowledge in a specific development area.

One of the areas of this solution that could be improved would be to improve the low code features of the application itself. We would also like to use the same platform to build any application, even if it is not necessarily defined as a functionality needed by a BPM.

The RPA tool within this solution needs further enhancement to compete with other RPA tools in the market. They are focusing more on the overall platform rather than working on the RPA. Document AI tools could be an added functionality, for example. Alternatively, customers will need to purchase another RPA tool to complement the whole solution if they have very advanced RPA needs across their business.

I have used this solution for one year. 

This is a stable solution. 

This is a scalable solution. 

The technical support is good.

The initial setup was not that complex but also was not that simple.

We often recommend this solution to our customers. It is a wonderful solution. There are not many professionals working with this tool which is important to note.

If the core need of a customer is for BPM and automation, this is a suitable solution. If their needs exceed a BPM solution, such as modernizing different kinds of applications, there may be other suitable solutions. 

This is a good solution from a technical perspective and is based on a very reliable and scalable platform.

I would rate this solution a nine out of ten.