Architecture of PEGA ……. Part 1
Before we get started with PEGA Architecture let's first understand a bit around BPM. This article mainly focuses of key components of BPM rather than PEGA. It is important to understand BPM before understanding Architecture of PEGA. If are already familiar with these skip to next article which focuses more on PEGA architecture.
As you all know BPM stands for Business Process Management. The immediate question that comes to mind is what a Business Process is?
Wikipedia defines (http://en.wikipedia.org/wiki/Business_process as follows, which is quite easy to understand
A business process or business method is a collection of related, structured activities or tasks that produce a specific service or product (serve a particular goal) for a particular customer or customers. It often can be visualized with a flowchart as a sequence of activities with interleaving decision points or with a Process Matrix as a sequence of activities with relevance rules based on the data in the process.
Let’s see easier definition of BPM
BPM is the general term for the services and tools that support explicit process management (such as process analysis, definition, execution, monitoring and administration), including support for human and application-level interaction.
In other words a BPM can be treated as a set combination of
BPM = P2P + A2A + P2A
(P2P – Person to Person, A2A – Application to Application, P2A – Person to Application).
When we define a BPM the set of component that completes the BPM architecture. Although most of the components are self explanatory below listed with few one liner description
• Workflow: A workflow is a depiction of a sequence of operations, declared as work of a person, work of a simple or complex mechanism, work of a group of persons, work of an organization of staff, or machines.
• Portal: Portal is a web system that provides the functions and features to authenticate and identify the users and provide them with an easy, intuitive, personalized and user-customizable web-interface for facilitating access to information and services that are of primary relevance and interests to the users.
• Operational Data Analysis : Operational business intelligence (BI) is a system of reports, metrics, and dashboards designed to drive decisions that optimize a company’s performance in the present.
• Integration: In the BPM context – Integration means linking all the various layers of BPMS architecture seamlessly as well as with other systems that form part of Business process domain .
• Document Management: In information systems, Document management consists of Digitizing, Indexing, Archiving , Retrieving and Managing documents.
• Identity Management: In information systems, identity management is the management of the identity life cycle of entities (subjects or objects)
• Rules: A business rules engine (BRE) is a software component that allows non-programmers to add or change business logic in a business process management (BPM) system. More @ http://dotnetclr.blogspot.com/2011/12/my-journey-to-pega-starts-from-here.html
• Process Repository: In the BPM context – Process Repository is the collection of Process models – Design time, completed and run time . Typically they are stored as XML models compliant to standards like BPMN.
• Process services :
• Monitoring (Business Activity Monitoring BAM ) :
• Lifecycle Management :
• Security :
• Event Management :
• Process Documentation :
Next in Part -2 we are going to see what all are PEGA offerings (PEGA offers smartBPM) and how each of the aforementioned components aligns with PEGA smartBPM.
