Pega Platform

Pega Platform has introduced the low code feature, using app studio seasonal and professional developer can develop application easily and quickly. The initial application can be build by Business analyst and product owner who has less knowledge of Pega Platform, further application can be enhanced/extended by professional developer. We can develop end to end application and promote to higher environment. Easily we can perform parallel development using branch.

Suited for:
CRM and automated tool.
Data modeling

Telecom sector and banking sector. I had worked on these sectors and it is well suited. In these two sectors business complexity is high and changes need to done very quickly.

Pega [RPA] is good to address a specific business function requirement with not too many bots or automation processes. It takes time and effort to set it up. Though once done, it is very easy to configure and use. One should also run a POC to verify if this product meets the scalability requirements.

Good for customer service to use instead of DOS like black screens, but bad for trying to train customer service (no sandbox environment, at least for us) since they can’t “completely” perform a task prior to going to a live environment. The knowledge is fairly good, except you can’t search the body of an article which is weird.

I think Pega is an excellent platform for any transactional, repeatable task that is currently managed manually by agents needing to be automated.

Pega may be very helpful if your company wants to move beyond just marketing automation and into integrating marketing with all internal processes. In our company we see marketing as more than just branding and advertising, but really as a way to facilitate great customer experiences. Pega works well if you share this vision. If you're only looking for a platform to run your advertising and campaigns than Pega may be too much for you.

Well suited for handling customer queries via service requests (which are called cases). These cases can be viewed/ worked upon at multiple stages by multiple teams before resolutions in Pega Platform.

It is not suited for centralized bot deployments. If several bots need to be deployed, then it will be difficult to manage and control. Programmers have to create custom code components to collect log files, health files, etc. On the other hand, it is best suited for an application which takes a random time to load, works in Windows MDI, or in parallel programming.

Pega Platform will specifically come in handy and will be very useful if your business needs are to be dealing with a lot of data collection, in considerably large data completion forms. It is less appropriate in fulfilling some complex business needs like invoking APIs that are hosted by an external server. Or if the business needs to have a lot of mobile development.

I am using Pega to automate our desktop or web application. This is the perfect platform to scale the work on demand. The average developer can extend the functionality.

If you need a good CRM for your customer service team to track customers interactions and you like to manage it without coding, it is a perfect option. It is very good for any case with multiple steps. For example, a bank, health insurance company, or auto insurance quote application.

Simple and powerful platform to build Workflows with SLAs, Access Control and Correspondences and what not... :)

Pega is perfect to implement Process Management for any kind of company, by using each process as a case type, they all can be managed in one single system. This eliminates the need to maintain several systems in parallel.

Pega RPA is well suited for situations where you want to design a single UI that will allow agents to work in one place rather than having to manipulate data in many different environments, over and over again. For example, if you have SAP, Siebel and Salesforce, you can create a UI that allows your agent to work within that single UI vs. having to Alt Tab between all three applications.

Pega is great for corporate web apps when a certain work flow or process can be improved through automation or a more stream lined process. It can handle forms and documents really well, integrates well with many different services (including other Pega apps), can handle very complex work flows and logic to basic things like user permissions and notifications. I would say it is less suited for small business needs. I would also say it is not that great at handling media or very interactive screens such as video (something I have personally never seen done).

We had a business request where the user wanted the functionality to be ready in 2 weeks. We were able to deliver that functionality with the help of Pega. Pega did it well!

A business friendly toolkit for defining applications. Unlike traditional BPM tools, there are much less complicated, technical syntax to handle in modelling processes and hardly any hard-coded programming. A well-trained business user can be trusted to create a business application from the PegaSystems BPM framework if desired.

Less time, robust code situations, good performance.

Build a Banking Application where customers can check for loan, insurance status based on the loan numbers provided. Customers register with bank, login to the portal and search for the loan status. Create a portal for applying loan / insurance claim which is routed to manager for approval upon successful background verification. Once approved, email customers for notification. Invalid applications go to false claims table for rejection. Also create a portal for banking payments to other banks for existing customers via NEFT/IMPS

Process intensive systems can best use Pega. If there is a process, there can be Pega :)

Pega plaform is well suited for large enterprise application development. Pega provides powerful capabilities in implementing security. It is used in Banking, healthcare and Insurance domains. So many banks all over the world are using Pega to develop their applications.Healthcare and insurance corporations also benefit similarly.
Developing attractive UIs is difficult in Pega.

CRM Sales Automation Appeals and Grievances

Pega is well Suited for

• Building business process applications which have assignments, routing and escalations.
• Best suited for customer care applications.

Less suited for

• applications which have the system of records in some other system (ie) For claims application the claims details has to be in pega, if the info has to be fetched from some other system it makes the application slow.

It is very well suited for the workflow process and implementing business process across companies. It is not well suited for transaction-based processing.