Pega Platform Reviews

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

Pega BPM is a business process management tool that can be used to build enterprise applications.

The solution is operating well overall.

I have been using Pega BPM for approximately two years.

They need to support the solution better, at this time the company does not have enough support.

The implementation is not complex.

I need people who understand this tool and they can implement it. I cannot rely on someone that implements it and leaves. They do not have enough people qualified in the market. If you are not able to operate it, improve it, or do enhancements changes yourself, it will be an issue.

The price is a bit expensive.

I rate Pega BPM a seven 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 primarily use the solution for customer experience. We also use it to create some workflows.

The solution provides us with a very good dashboard.

From a technical point of view, it would be helpful to have some advanced analytics to help with configuration. We have a lot of unwanted features and it would be good to configure it more appropriately so that we are using just exactly what we need.

I've been using the solution for five years.

In terms of stability, occasionally there are a few glitches to contend with. It's fine. It's to be expected. It doesn't affect our work too much.

The solution is scalable. If a person needs to expand the solution for their organization, they can easily do so.

Currently, we have more than 20 people using the solution.

We've never been in touch with technical support, so I can't speak to how they are or what the process is.

We previously used Appian. At the time, there was some product integration and it made sense for us to switch to Pega.

In terms of implementation, the solution's initial setup is a little bit complex. It's not exactly straightforward. The software implementation and deployment, for example, is very complex. In comparison to the on-premises model, the cloud is very quick to deploy. The configuration on the cloud is much more straightforward.

If a person is using an on-premises solution, they will need one person to manage it, but if the cloud is deployed, there's no need for anyone.

We're still in the process of evaluating other solutions. We're comparing other offerings to Pega.

We're partners with Pega.

I'm not sure of the exact release number, but we are using the latest version of the solution.

It's a good idea to get clarity in terms of what future upgrades the solution plans to implement. Then, compare it to the competition. It will give you a good idea of what is possible and what will be possible.

I'd rate the solution eight out of ten overall. It's been quite good and we've been quite satisfied with it.

We use the Pega BPM platform for helping companies establish, expand, or solidify their business process management and workflows.

We do the licensing of the product, and the capabilities of the platform have allowed us to flexible in the type of organizations we work for. Our strengths are in corrections and investigation into the organizational process. We also have our own IT and have existing models that we use for the insurance industry, inventions industry, and others. These models allow us to have a starting point and build out to fit a unique organization's needs. We do a bit of work for the government as well. For the clients, improvements should be an enhancement to business processes, workflow, and efficiency.

A lot of our customers are working with a digital confirmation. The enhanced features in Pega are appealing to our customers as they can use it on designs, digital agility, omnichannel or customer experience. The rapid renew structure allows better implementation over other solutions and aids clients in serving their customers. Because of the features available, we are filling a need we see for our customers. It works with team frameworks and allows them to take proactive decisions with their product lines, data integration, data crunching and some other features that are helpful for customer marketing.

In terms of improvement, we would see a benefit in Pega having better availability on the cloud side. Their presence on the cloud is not as strong as their competitors. Pega and the partners both have needs to enhance their cloud footprint compared to what it is now.

There is room for improvement with RPA as well (Robotic Process Automation) to automatically take action for users. 

The product is also extremely stable. It has a very strong case management base. This holds a lot of complex business to business information and that makes it so implementations and use can be simplified and promptly provided to the customer. The key is that the business department has to understand the product and its purpose in the right manner. I think Pega is one of the most stable applications in the environment of business technology, use, and implementation.

The product is extremely scalable. Scalability comes with two criteria: choosing the number of users and how it will be implemented in the businesses. Some organizations have 40-50 users on Pega and others have more than 1000 users. As far as the scale of use is concerned, there are absolutely no issues. 

The kind of variety and scale that Pega can handle — the different types of business, different types of application, the different types of integration — is absolutely amazing and don't think that any of its competitors come close.

The technical support is extremely good. By technical support, this refers to technical support that we as partners get from Pega. But the support comes in two parts. When we implement Pega, we take ownership of supporting our implementation on multiple levels.

We talk to Pega one-on-one for service requests and we have no reason to complain. That being said there are still some issues here and there, but they are infrequent.

We have been using Pega BPM since our inception based on capabilities. Our expertise has helped us carve out a nice niche with the marketplace.

The Pega BPM is designed in a manner which allows for the product to be implemented by experts and then for control to be handed over to the business users. If the business users are not prepared, the flexibility and ease of use for the business users can't be guaranteed. If the Pega platform is implemented in the right manner, the organization needs to integrate the right skills, the right implementation, and best business practices. 

Unlike other software solutions, Pega is not about having a whole army of developers working to put a solution together. Once the core platform is set, the application can be taken further with even junior developers implementing more controls.

The resources involved in the implementation actually support the organization and the product when implemented well.

As we do the implementations we do not rely on outside teams. We are the outside team with a high level of experience with the product.

Of the business tool available on the market, as of right now, Pega is not the cheapest. But when you choose Pega, it is possible to realize a greater return on investment. The return on your investment is more important. The implementation is a big investment as is the commitment of the organization, but the return is greater.

I would place Pega BPM at around an 8.5 out of 10 because of the cloud and RPA issues. However, Pega is an excellent choice. It is efficient and does what it is supposed to do. It is extremely important to choose the right product and implementation partner. What the customer should be looking for in terms of an implementation partner is the quality of resources that they have, it is not the quantity. 

The Pega resources are classified into solution updates, frequent solution updates and new solution updates. An implementation partner needs to have a core team that brings the solution together. The emphasis is on the people who take the implementation forward.

It is very important to see if the implementation partner has the right interface and the right experience. Organizations themselves need to look at developing a certain amount of internal Pega support. This means choosing a partner or provider willing and able to impart their skills and knowledge. The client has a lot of control on their side. Its good to be able to rely on a strong business implementation partner.

We are primarily using the solution for or our authorization workflow.

The most valuable aspect of the solution is the various workflows.

I haven't been using the solution for that long, so I don't know if there are any features that are lacking.

We need more light retail BPM tools within the Pega system. However, Pega is mostly for big companies.

As our group is pretty small, we may need to look for a different solution that's more geared to smaller sized organizations.

I've only recently begun to use the solution. I've been using it only for the last three or four months.

So far, over the few months we've used it, the solution has proven to be quite scalable.

So far, we've found the solution to be quite scalable.

We haven't reached out to technical support yet. We've been only using the solution for a short time.

The initial setup is straightforward, The installation is not that complicated. One of our team members has deployed it onto the storage.

Our own teams handle maintenance. We have several teams on different projects.

We're constantly evaluating other products. We're looking at others on the market right now.

Most of our use cases are related workflow kinds of tasks like data workflow, user onboarding workflows, etc.

Although the solution might be too big for our purposes, as of now we are continuing with Pega because we don't know of any such tools which have the scalability, as well as the ease of use that this solution provides. That's why we are continuing with it right now.

Although I personally haven't used the solution for very long, I would rate it eight out of ten.

Real-time operational case management and live reporting of key arrival and departure information, including live operational data feeds from both internal and external data sources on web and mobile devices.

Decreased time for plane departures and landing, supported analytical insight for planning of three to six month forecasting, and helped with operational decision planning and support.

Pega Cloud and Pega BPM, because they allowed us to develop and quickly release with confidence using cloud technologies. We limited disruption on core operational systems while proving the business and technology requirements.

Pega Cloud early adoption and use for cross enterprise capability was new to many. The early adoption meant version 2.0 of their cloud service may require refactoring and redesign of some services.

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.