Pega BPM:

Pega BPM offers one suite known as SmartBPM suite. This suite offers the IDE,
engine and management is known as PegaRULES Process Commander (PRPC).Pega
is leader in BPM as well as BRE space.SmartBPM is based on IBM RUP (Rational
Unified Process) methodology.
The following are the BPM Components
Business Process Modeler
Business Process Analysis
Integrated Development Environment (IDE)
Execution engine
Rule Engine
User Portal
Business Activity Monitoring (BAM)
Business Rule Engine allows separating business rules from the application
Sharing business rules across application
Developer & Business user interface
Different rule representations Decision Table
Decision Tree
Score Model
Rule activation and versioning
Authorization and Authentication
Audit trail and rule history
Rule testing framework
Conflict resolution and completeness check

Pega BPM offers SmartBPM suite. Which provides the IDE, engine and management
The Methodology is based on IBM Rational Unified Process.

Rule Engine Architecture

Development Environment
BOM Rules
IT User
Rule Editor
Production Environment
Rule Sets
Business User
Rule Engine
API

Overview Pega SmartBPM Suite

PRPC forms the core of the SmartBPM suite. There are other components available
for advanced features such as Analytics, Content Management.
PegaRULES Process Commander
Process Analyzer
Process Simulator
Enterprise Integration
Case Management
Content Management Integration
Portal Integration
The backbone for all components of SmartBPM suite is PRPC
The following Features are provided by PRPC
Integrated Development Environment (IDE) for all components
Application deployment and Run time environment (Engine)
Application management (change/scale), maintenance
(debug/patch) and administration (configuration)
Base for Pega frameworks (Project Mgmt, Test Mgmt, Industry)

Smart BPM Methodology:

Construction Phase
Inception Phase
Elaboration Phase
Transition Phase
Live

Flows:
Flow rule is an instance of the rule type .Flow is a network of shapes representing
tasks and connectors (directed arrows), each with associated parameters and
values.
Flows are the fundamental rule instances that represent business processes,
identifying who works on a work object in what sequence, what decisions and
processing occur automatically, and many other aspects of the business process
Flow Design Shapes:
The Visio Flow Shell stencil provides the following shapes to represent fundamental
flow elements.
Connector:
Associates a task in the flow with another that may follow the first task. Connector
leaving assignment task may be flow action connectors leaving other task may be
when conditions.
Comment:
Adds explanatory texts anywhere on the flow diagram. Comments do not effect
execution of the flow.

Start:
Identify the start task of the flow.

Assignment:
Represents a pause or potential pause in the flow This signifies that a person or
system must act on a
Work object before the flow can progress.
Decision:
Represents an automated decision. This shape can call a Decision Tree, Decision
Table or a Map Value.
Router:
Identifies an activity that sends newly created assignment to the correct destination
Fork:
Represents a point where the flow chooses one of a few different paths of
processing based on the result of the When rules invoked.
Notify:
Sends correspondence to the specified party when an object reaches an assignment
Assignment Service:
Represents a point in the flow where you pass control to an external system using a
Connect BPEL rule, and pause until an event is raised
Integrator:
Invokes integration services to connect to an external system
Split for Each:

Sends a work object through another flow based on information in the pages of a
PageList or PageGroup property
Split Join:
Breaks the current flow into sub-flows; the sub-flows operate in parallel and later
rejoin
SpinFlowOFF:
Starts a parallel flow; the current flow continues processing. You can indicate if the
parallel flow should run on the current object or a different one

Pega User Roles

The following are the Roles in Pega
Work User Person responsible for processing the work
Work Manager Management of work including task allocation and monitoring
performance (team and resources)
System Architect Design and Develop and Test the PRPC application
System Administrator Administer the PRPC application in terms of resources,
user, systems
Business Architect Takes care of Conception and Elaboration

Pega Slices:
The following are the Pega Slices:
Process

Policy Decisions
User Interface
Integration
Monitor Activities
Case Management
Content Management
Process: Process portal is being used by architects and business analysts to plan
process flow and maps and determining how work will be done.
Policy Decisions:
Decision portal is being used by business analysts and others to capture goals,
mange business rules, review and analyze available dependency
networks
User Interface: User Interface portal is being used by developers and others to
design and manage end user portals, user interface screens, form and
other presentation layers.
Integration: Integration portal is being used by system architects and others to
share Pega systems with other systems and to connect and work with
multiple systems of records.
Monitor Activities: Monitor Activities includes link to monitor work status track
progress and define custom reports on data and rules.

Case and Content Management:

Case and Content Management provides ability to define association of structured
and unstructured content with cases managed and generated by BPM applications.