Project Design
Resume:
[pic] [pic]
KALYAN REDDY MABBU
Email: *************@*****.***
Contact Number 650-***-****
PROFILE SUMMARY:
. Overall 7 years of experience in Designing and developing applications
using Pega Rules Process Commander.
. Good Experience in build and deployment of rules by using PRDBUTIL to
export and to import all the instances from one environment to
another.
. Good exposure to PRPC Reporting features. Hand on experience in
creating the List View and the Summary View Reports.
. Good Experience in creating flows, activities, Rule Resolution,
Decision Rules, SOAP rules and UI related rules etc.
. Good Exposure to Procedural Processing and Declarative Processing by
using the Activities and the Declarative rules.
. Excellent hands on experience in implementing the Activities, Flow
Rules, Flow Actions, Decision rules, Declarative Rules, Privileges,
Access Group and Access Roles, Service level rules, Harness and
Section Rules, Summary Views, Connectors, Services.
. Good Experience in PRPC V6.x features and Hands on experience on PRPC
construction and debugging tools such as Tracer, PLA, Clipboard, DB
Trace and System management Application (SMA).
. Expertise in Full Pega Implementation cycle including Analysis,
Designing, Development, Integration, Testing, and Deployment Phases of
PRPC Applications.
. Good Experience in Developing Webservices by using the SOAP Rules,
Parse Rules, and building the XML Rules.
. PRPC V5 Certified System Architect.
. PRPC V5 Senior Certified System Architect.
. Gathering the Requirements for the enhancements from the business,
Analyzing and Providing a High Level Estimates to the Business.
. Responsible for creating Business Requirement document and get it
approved by the Business folks.
. Prepare High level design and Low level design documents.
. Interaction with business folks to update status on weekly basis.
. Coordinate the team to reach the project deadlines in time.
. Interaction with the business architect and the Technical architect on
daily basis to get the documents approved like High Level Design, Low
Level Design and Code Review Templates etc.
. Involved in Code Reviews and make sure that all the comments are
closed before the unit testing.
. Prepare unit test cases and unit test results.
. Getting and updating the Support Tickets on Daily Basis from the
Service Now Tool.
. Responsible for Fixing the Data Fixes and the Business Support tickets
on the same day itself and get the confirmation from the business.
. Applying the DML Changes in Production on Weekly Release.
. Responsible for applying the Scheduled change or the Maitainance
Change for every quarter.
. I will be the Person to get all the approvals from the Operations and
the Business for all the releases like Scheduled Releases, Emergency
Releases, Weekly Releases, DML Releases and the Maitainance Releases
etc.
. Prepared the Incident Report in case of Production Outages and sending
an email to the User Community Group.
. Closely monitoring all the Nodes with Respect to Production Instances
through SMA and make sure that all the nodes are up and running.
. Working as an onsite coordinator between the Employer and the Business
to get the requirements delivered on time and responsible for avoiding
the slippages.
CERTIFICATIONS
. Completed PRPC V5 Certified System Architect in Dec 2007.
. Completed PRPC V5 Senior Certified System Architect in August 2011.
TECHNICAL SKILLS:
Languages Core Java
Web Technologies HTML, JSP
Distributed JDBC
Technologies
Tools BPM Tool:
PRPC v5.3, PRPC v5.5, PRPC v6.2
RDBMS Tools:
IBM DB2, SQL Server
VERSION CONTROL:
VSS (Visual Source Safe )
Database DB2 v8.1, Oracle 10g, SQL Server
Application Servers IBM Web sphere
PROJECT DETAILS
Client: AIG / Chartis Insurance, New York City, NY Dec 2010 to Till
Date
Project: OMeGA Production Support
Role: Sr. PEGA System Architect
Description :
Omega application has been created by AIG to automate and expedite the
multinational insurance process. Automating the business process as a
workflow, it reduces the paperwork and manual intervention of the people.
Integrating with other applications using service oriented architecture,
OMEGA makes the multinational insurance
process faster and enables other applications to exchange data in real
time. OMEGA is about the policy administration system. The main purpose of
the Production Support Team is to Resolve the Tickets on Daily, Weekly,
Monthly and Quterly based on the Priority of the Tickets. As part of OMeGA
Production Support, Support team will be responsible for the Completing the
New Enhancements requested by the Business Users.
Responsibilities:
. Gathering the Requirements for the enhancements from the business,
Analyzing and Proving a High Level Estimates to the Business.
. Responsible for creating Business Requirement document and get it
approved by the Business folks.
. Prepare High level design and Low level design documents.
. Interaction with business folks to update status on weekly basis.
. Coordinate the team to reach the project deadlines in time.
. Interaction with the business architect and the Technical architect on
daily basis to get the documents approved like High Level Design, Low
Level Design and Code Review Templates etc.
. Involved in Code Reviews and make sure that all the comments are
closed before the unit testing.
. Prepare unit test cases and unit test results.
. Getting the Support Tickets on Daily Basis from the Service Now Tool.
. Responsible for Fixing the Data Fixes and the Business Support tickets
on the same day itself and get the confirmation from the business.
. Applying the DML Changes in Production on Weekly Release.
. Responsible for applying the Scheduled change or the Maitainance
Change for every quarter.
. I will be the Person to get all the approvals from the Operations and
the Business for all the releases like Scheduled Releases, Emergency
Releases, Weekly Releases, DML Releases and the Maitainance Releases
etc.
. Prepared the Incident Report in case of Production Outages and sending
an email to the User Community Group.
. Closely monitoring all the Nodes with Respect to Production Instances
through SMA and make sure that all the nodes are up and running.
. Sending the Extracts to Specific Users on Daily and Weekly basis.
. Good Knowledge on SOAP Protocols which is used to interact with the
external systems to send and receive data.
Environment: PRPC v6.1, v5.3, Oracle 10g, Websphere 6.0
Project: SSO
Role: Sr. PEGA System Architect
Description:
Single Sign On provides users with the ability to logon to multiple
applications without being challenge for repeated authentication. It also
enables the user to use the same User Name and Password across multiple
applications. It also provides the ability to control user access at the
enterprise level and end to end audit sessions for security reporting and
auditing. The main Scope of this Project is as follows:
. User Authentication using Site Minder Single Sign On
. There will be no change to the Application Authorization process that
are handled through those specific applications
. Changes to the User Entitlement screen to create or Update the OMeGA
Bussiness User Profile.
. Managing Data in the LDAP Repository that determines that the User is
Active or Disabled.
Responsibilities:
. Gathering the Requirements from the business, Analyzing and Proving an
High Level Estimates to the Business.
. Responsible for creating the System Requirements Specification
Document and get it approved by the Business Folks.
. Prepare High level design and Low level design documents.
. Interaction with business folks to update status on weekly basis.
. Coordinate the team to reach the project deadlines in time.
. Interaction with the business architect and the Technical architect on
daily basis to get the documents approved like High Level Design, Low
Level Design and Code Review Templates etc.
. Involved in Code Reviews and make sure that all the comments are
closed before the unit testing.
. Prepare unit test cases and unit test results.
Environment: PRPC v5.3, Oracle 10g, Websphere 6.0
Project: DNA
Role: Sr. PEGA System Architect
Description:
Omega is a Multinational Insurance application which creates Multinational
Policies for different clients across the globe.This application keeps
record of all the policies which are created in different countries but the
policies which are issued by AIG Offices (Issuing Office) to different
clients are generated using different systems in different countries. eWS
(eWorld Source) is one of such issuing office for North American Region.
OMeGA will need to be enhanced to support new region structure. OMeGA
covers reporting and issuing office operations (Programs and Requests),
which will need to be transferred from their existing structure into the
new regional structure. As OMeGA handles user management, process flows,
work assignment, transfer and management reports based on current corporate
Region structure, there is a need to update OMeGA, to align with the new
structure. The main Scope of this Project is as follows:
. Create new regional structure for OMeGA
. Migrate existing (historical) transactional data (Program, Request
etc.) to the new regional structure
. Migrate master entities to new regions (for e.g. Users, Workbaskets
etc.)
. Changes to other projects (Web Services, IFRC, SIGMA etc.) arising out
of the Regional Realignment
. Changes to User Management
. Removing Hyperlinks from the user profile
. Removing "Full Profile" button from the user profile
. OMeGA functionality changes
. Report Criteria Page Customization
. Workgroup renaming
. Renaming the OMeGA Role "User" to "Local"
. Ability to associate multiple workbaskets for User with Role "User"
(Local user)
. Edit on Transfer - Transfer Work for IO and RO user should only be
possible if the user has access to the Major line for which the work
was created.
Responsibilities:
. Used the tools PAL and PLA to monitor the Performance of the OMeGA
Reports.
. Increased the Performance of the Reports by creating Indexes for the
OMEGA Database Tables.
. Prepared High level design and Low level design documents.
. Identified the impacted areas and the backend resaver activities needs
to done.
. Coordinate the team to reach the project dead lines in time.
. Interaction with the business architect and the Technical architect on
daily basis to get the documents approved like High Level Design, Low
Level Design and Code Review Templates etc.
. Involved in Code Reviews and make sure that all the comments are
closed before the unit testing.
. Prepare unit test cases and unit test results
. All the documents related to this Project is Stored in a repository
and informed to the business which is used for an audit purpose.
Environment: PRPC v5.3, Oracle 10g, Websphere 6.0
Project: OMeGA Reject Improvements Phase 2
Role: Sr. Developer
Description:
In order to remain competitive in the growing Multinational business
segment, there is a critical need to improve customer facing service
levels. To that end, certain process improvements and enhancements to the
system work flow in the OMeGA system have been identified that will result
in more timely processing of policies, thus saving time, cutting costs and
mitigating the possibility of non-renewal of existing business. In the
current OMeGA workflow environment, one of the main reasons for delays in
issuing policies is the fact that requests from the producing offices for
issuing policies are rejected by the issuing offices due to wrong or
incomplete information.
During the period November 1, 2009 through October 31, 2010 there were
31,713 requests released to issue underlyers. Out of this a total of 8,910
or 30% of the requests were at least rejected once before they were
corrected and a policy could be issued. These rejected requests
represented a gross premium of
$524 million out of the total $2.9 billion in gross premium for all the
requests released during the same one year period. The average time
elapsed from the point the request was rejected to when it was finally
accepted by the issuing office for further processing for policy issuance
was 29 calendar days.
The objective of this project is to make enhancements to the OMeGA system
so as to establish controls surrounding the data / information contained in
the requests in addition to modifying processes that will reduce the number
of requests that are rejected by the issuing offices and develop the
ability to better track the status of the requests and to introduce a new
SLA's as part of this change through the complete OMeGA Application.
Responsibilities:
. Prepare High level design and Low level design documents.
. Interaction with the business architect and the Technical architect on
daily basis to get the documents approved like High Level Design, Low
Level Design and Code Review Templates etc.
. Involved in Code Reviews and make sure that all the comments are
closed before the unit testing.
. Prepare unit test cases and unit test results
. All the documents related to this Project is Stored in a repository
and informed to the business which is used for an audit purpose.
. Prepare release notes for the business users.
. Supported the Business Users during the Warranty Period
. Created the Handbook for OMEGA Users to reduce the number of
Production Support Tickets.
Environment: Pega RULES process commander v5.3, Oracle 10g, Websphere 6.0
Project: OMeGA Reject Improvements
Role: Sr. Developer
Description :
In order to remain competitive in the growing Multinational business
segment, there is a critical need to improve customer facing service
levels. To that end, certain process improvements and enhancements to the
system work flow in the OMeGA system have been identified that will result
in more timely processing of policies, thus saving time, cutting costs and
mitigating the possibility of non-renewal of existing business. In the
current OMeGA workflow environment, one of the main reasons for delays in
issuing policies is the fact that requests from the producing offices for
issuing policies are rejected by the issuing offices due to wrong or
incomplete information.
During the period November 1, 2009 through October 31, 2010 there were
31,713 requests released to issue underlyers. Out of this a total of 8,910
or 30% of the requests were at least rejected once before they were
corrected and a policy could be issued. These rejected requests
represented a gross premium of
$524 million out of the total $2.9 billion in gross premium for all the
requests released during the same one year period. The average time
elapsed from the point the request was rejected to when it was finally
accepted by the issuing office for further processing for policy issuance
was 29 calendar days.
The objective of this project is to make enhancements to the OMeGA system
so as to establish controls surrounding the data / information contained in
the requests in addition to modifying processes that will reduce the number
of requests that are rejected by the issuing offices and develop the
ability to better track the status of the
requests and to introduce a new status called Pending and tracking this
status to reduce the number of Rejected Requests from the Issuing Office.
Responsibilities:
. Gathering the Business Requirements and responsible for Preparing the
Impact Analysis Document and Providing a High Level Estimate for the
same.
. Prepare High level design and Low level design documents.
. Interaction with the business architect and the Technical architect on
daily basis to get the documents approved like High Level Design, Low
Level Design and Code Review Templates etc.
. Involved in Code Reviews and make sure that all the comments are
closed before the unit testing.
. Prepare unit test cases and unit test results
. All the documents related to this Project is Stored in a repository
and informed to the business which is used for an audit purpose.
. Prepare release notes for the business users.
. Supported the Business Users during the Warranty Period and provided
them the user steps whenever required.
. Created the Handbook for OMEGA Users to reduce the number of
Production Support Tickets.
Environment: Pega RULES process commander v5.3, Oracle 10g, Websphere 6.0
Client: ALERE Health, Atlanta, GA Feb, 2010 -
Nov, 2010
Project: Apollo Disease Management
Role: Sr. Developer
Description :
Disease Management is a system of coordinated health care interventions /
communications that teaches individuals how to better manage their chronic
disease condition. Participants enrolled in the Alere DM Programs learn to
take responsibility for managing their chronic condition. The goal of
these programs is to reduce healthcare costs and improve quality of life
for the participant by minimizing or preventing the effects of the disease
from which they suffer.
Responsibilities:
. Analyzed requirements, participated in Design Discussions and prepared
Design documents
. Design and development of the application Enhancements - Worked on
Class Structure Design, activities, decision rules, UI rules, SQL
Connectors, SOAP Services and Connectors.
. Reviewed code to make sure it is efficient.
. Monitored Agents and Log files
. Was completely responsible for all Release management activities that
include Code deployment to QA and UAT, Build verification for
Production deployments, Monitoring Production deployments making sure
the right code is moved to Production and Post deployment activities.
Environment: PRPC v6.3 SP1, Oracle 11g, Microsoft SQL Server 9, Apache
Tomcat/6.0.36, Linux 3.0.34-0.7
Mphasis, Bangalore, India Jan 2006 - Jan
2010
Client: Chartis Insurance
Project: Omega Extension-1
Role: Sr. Developer
Description:
Omega application has been created by AIG to automate and expedite the
multinational insurance process. Automating the business process as a
workflow, it reduces the paperwork and manual intervention of the people.
Integrating with other applications using service oriented architecture,
OMEGA makes the multinational insurance process faster and enables other
applications to exchange data in real time. This project is about the
policy administration system. The main purpose of the project is extending
the web services with in omega. There are existing web services that
interact with the GOAL/D database by using the AIU framework. We are
creating new web services that interact with the Pega Rules database. We
are enhancing the existing application that identify and process the Fast
Track accounts.
Responsibilities:
. Gathering the Business Requirements and responsible for Preparing the
Impact Analysis Document and Providing an High Level Estimate for the
same.
. Prepare High level design and Low level design documents.
. Interaction with the business architect and the Technical architect on
daily basis to get the documents approved like High Level Design, Low
Level Design and Code Review Templates etc.
. Created SOAP Services and the Activities.
. Created the Services to get the Data and to update the Data in the
Database Using the SOAP Services.
. Worked on request and response XML.
. Created and worked on Parse XML rules and Stream XML rules.
. Responsible for creating the Unit Test Cases.
. Created the Resaver Activities to update the New Columns with a
default value in the database.
. Created Hand book for the business users that will describe with
screen references how to run and execute these Webservices without any
issues.
. Prepared and Sent the Production Release Note to the Business User
Community.
Environment: Pega RULES process commander v5.3, Oracle 10g, Websphere 6.0
Client: AIU
Project: AIMA-eAegis, UAT/Production Support
Role: Developer
Description:
Migration of existing client server VB application in to web-enabled driven
by rules engine. The main business of the application is Marine Claims
processing in USA and Canada. AIMA-eAegis has been built using Pega RULES
Process Commander (PRPC) and will interact with AIU GOAL/D.
Responsibilities:
. Worked on the support tickets to resolve the issues
. Unit testing of the modules
. Fixing the application bugs
. Preparing DB Scripts and release notes for month end releases
. Regression testing of the application and modification of automated
test scripts for the rules
Environment: PRPC v5.2, Sybase 12.5, Oracle 9i, IBM Web sphere App Server
6.0, MS Visio 2003.
Client: DBG
Project: CORE Upgrade
Role: Developer
Description :
Analyzed PRPC 5.2 upgrade issues for CORE application in development. The
issues Analyzed and provided solution is Authentication/session timeout.
Analysis of application in PRPC 4.2 vs. PRPC 5.2 in development also done
unit testing for the various scenarios after upgrading in development.
Documentation for Access Groups and Access Roles has been done.
Responsibilities:
. Development and bug fixing Unit testing of the modules
. Fixing the application bugs
. Executing test cases
. Regression testing of the application.
Environment: PRPC v5.2, Apache Tomcat, Oracle, Win 2K and MS Visio 2003.
EDUCATIONAL BACKGROUND
Bachelor of Technology from Anna University, Tamil Nadu, India, Jan 2006
Contact this candidate