Resume

Sign in

Project Architect

Location:
Basking Ridge, New Jersey, United States
Posted:
September 12, 2018

Contact this candidate

Resume:

Mail Id: ac60yn@r.postjobfree.com

Phone: 813-***-****

Technical PRPC Lead Architect having More than 15 years of experience in Information Technology and extensive experience in enterprise application architecture design using PegaRULES Process Commander, worked broadly in various domains experience with Health Care, Insurance, Financial, retail banking and Automobiles, also worked on large multi-release Pega projects for several Fortune customers in delivering BPM and BRE applications that automate the processes using different Pega Framework and knowledge for policy administration from Insurance sector. I have worked in designing the rating computation BRE application in Financial Services and excellent System designer & team player with good interpersonal and problem solving skills. Having experience on Control-M job scheduler to schedule, Order and Run the jobs for various system monitoring and played production Lead role.

Technical Skills

PegaRULES(PRPC 7.X,6.X,5.X,4.X)

CC Framework

HealthCare Framework

CPM Framework

Project Management

Unix Scripting

Java/J2EE

JavaScript

SQL Server

Oracle/DB2

BRE Architecture Design

Release Management

Product Configuration

Test Management Framework

Control-M Job Scheduler

Apache James

Experience

Organization

Designation

Duration

Cognizant Technology US corps

PEGA Lead Architect

Feb 2011 – Till Date

Virtusa Corporation

Senior Consultant

May 2008- Jan 2011

Satyam Computer Services Ltd

Associate

Feb 2005 - Apr 2008

Fortune System Pvt Ltd.

Programmer

Aug 2002 - Jan 2005

Education

Bachelor of Engineering (B.E Computer Science), Madras University,Chennai, India, -2002

High School- Sri Ramakrishna BHEL Higher Secondary School,Ranipet,India -1998

Achievements & Certifications

Pega Certified Senior System Architect (CSSA 7.x)

Pega Certified System Architect V4 and V5, Pegasytems Inc.

Certificate of Appreciation Q3 FY09.

GIP Certified Professional.

Appreciation for Hot Doc,CFDB & ADAM first Integration Deployment.

Awarded First Class for the Bachelor’s Degree.

Awarded Master in Engineering Drawing.

Trained JPMC Tools and Technology.

BMC Control-M Workload Automation 8.0.

Trained in ECG Gateway File transfer with working experience

Geneos Active console.

Trained in Dynatrace and DCRUM with working experience.

Wily System Monitoring.

Trained ITSM Change ticket manager.

Experience at Cognizant Technology

VDE- Voluntary Disenrollment(CVS Caremark, New Jersey, US)

Technical Lead and Development (Oct 2017 to till date)

Business Problem: Voluntary disenrollment (VDE) requests from members are processed manually, with multiple touch points. Voluntary disenrollment’s accounted 86% of total SSIC disenrollment volume and required 100% manual review. Multiple systems (MedForce, Valencia, PeopleSafe, Facets, and MARx) are independently referenced for processing these disenrollment requests. Manual processing exposes us to inconsistency and inaccuracy in decision making and request processing. In some cases, incorrect correspondences are triggered to members, members are not disenrolled timely, and are not disenrolled with correct disenrollment date. Current configuration also requires us to contact the members multiple times to obtain all the required information to process the disenrollment requests. The proposed state shall automate and integrate the processing/handling of voluntary disenrollment and cancellation requests from members and to reduce labor hours by at least 50%, increase compliance and reduce internal review labor and cost, Improve member experience and Enable Tier 1 users to process greater percentage of volume.

Environment: PegaRULES Process Commander(PRPC) 7.1.8, Linux 2.6, and IBM WebSphere 8,MDS (SQL Server 12.0.5), Pegarules & SOR (DB2 10.05)

Project Role: Technical Lead and Development

Capture Actual business requirement for VDE system flow and create the Design Documents.

Review Technical Solution Document and provide recommendation to business as well as Development team.

Code and create the flow as per the design.

Create External service to load or retrieve the data from FACETs/MDS/SOR system and validate end-to-end system behavior in VDE.

Project communications, including facilitating team meetings and developing and distributing the project status reports.

PHYCON- Physician Contracting (United Health Group,New Jersey, US)

Technical Lead Architect and Development (Feb 2016 to Sep 2017)

Business Problem: The goal of phycon was to modernize the process for validating and applying provider demographics and provider contract changes to our sources of truth provider databases and claims systems such as NDB, FACETS, etc.. Phycon was intended to replace a series of lotus notes databases and an Oracle on demand solution called UNO that could no longer be supported.

Environment: PegaRULES Process Commander (PRPC) 6.2 SP2,PRPC 7.1.9, Linux 2.6, Oracle 11g and IBM WebSphere 7

Project Role: Technical Lead Architect

Work with business to get the Actual requirement and Design the system.

Schedule and prepare Client playback session.

Review Technical Solution Document and provide recommendation.

Prepare and review High level Migration Strategies document.

Create Deployment plan, review and Implement.

Review Performance result and provide the recommendation.

Coordinating external integration team and apply the changes.

Performance analysis and fine tuning the application.

Provide the business a feasible solution for the long term goals.

Involve in designing the application, participate in design discussions & review, and provide design solutions to business problems.

Developing and managing detailed schedules, including tracking and managing the dependencies across the various work-streams rolling-up into the project.

Project communications, including facilitating team meetings and developing and distributing the project status reports.

Concourse-Case Management (Maryland, US)

Technical Lead Architect (May 2014 to Sep 2016)

Business Problem: Case Management can be viewed as the central hub with spoke relationships to other interfacing systems. Case Management is the central work stream within the Emerald Program, with the other work streams being leveraged by the case management function. The other work steams are called Enrollment, Provider, CHI, Transport and Claims. The system is having a user-friendly overall dashboard and intuitive workflows for the various process /services that will guide the case manager thru the steps. The system built to have a strong notification /alert sent to the team for task tracking and case scoring based on the data points ranked by importance. Case management application has and automating much of the emails handling/sending/receiving. The system has an easy to read accumulator of benefit paid from the clients.

Environment: PegaRULES Process Commander (PRPC) 7.1.6, Linux 2.6, MS SQL Server 10.5 and Jboss 5.1

Project Role: Technical Lead Architect & Production Support Lead

Work with business to get the Actual requirement and Design the system.

Schedule and prepare Client playback session.

Review Technical Solution Document and provide recommendation.

Understand system architecture and various Integration.

Prepare and review High level Migration Strategies document.

Create Deployment plan, review and Implement.

Review Performance result and provide the recommendation.

Coordinating external integration team and apply the changes.

Designing FAX send/Receive approach and implement.

Implement Risk management security log tracker.

UnitedHealth Group-IEMT(Incentive Error Management Tool, Florida, US)

System Architect (Jan 2014 to Apr-2014)

Business Problem: This project proposes to provide a central repository and access tools for the logging of the success/failure and follow up activities surrounding controls points (both automated and manual), as well as tools for reporting for internal and external consumption. Included will be functionality for identifying and managing exceptions (and groups of exceptions), so that root causes and issues over time can be identified. It also tracks the Error/Issues/Exception for various clients for their Incentives /Rewards and generates the reports .The Report will be used for Incentive Process improvement on the other applications. There are some external systems like eHP,FACETs .. etc which maintains the Incentive Payment process and its issue/Exception treated as a Controls .Each Control defined as Issue/Exceptions. Current process is that Incentive QA Team use the Shared points to create controls/Upload the file to the share points and reports will be generated manually. The IEMT solves the above issue and improved client satisfaction and retention.

Environment: PegaRULES Process Commander (PRPC) 6.2 SP2,, Linux, Oracle 11g and IBM WebSphere

Project Role: System Architect.

Work with business to get the Actual requirement and Design the system.

Schedule and prepare Client playback session.

Review Technical Solution Document and provide recommendation.

Understand system architecture and various external Integration.

Prepare and review High level Migration Strategies document.

Create Deployment plan,review and Implement

Review Performance result and provide the recommendation.

JP Morgan Chase-Service Action Manager-TechRefresh (SAM), Florida, US

System Architect & Production Support Lead (Apr 2012 to Dec 2013)

Business Problem: JPMC want to create the new infrastructure to cut down the Operational cost for SAM in terms of hardware, software and maintenance cost. It was the plan to move the existing SAM application from the old environment to the new TechRefresh environment. The new environments build from the scratch and moved the SAM application on top of it. I got tremendous opportunities to work with various team to setup the environment. The server was build individually for Dev, QA, UAT, Training and Prod/DR. Initially, I started with Development and once the complete testing is done then the similar setup propagated across all regions. Once the Prod/DR server was made then I moved to Production support Lead role.

Environment: PegaRULES Process Commander (PRPC), CPM, Linux, Oracle, Weblogic, Wily, Geneos, NDM and Control-M

Project Role: Technical Lead Architect & Production Support Lead with the following responsibilities:

Review Technical Solution Document and provide recommendation.

Understand system architecture and various external Integration.

Prepare and review High level Migration Strategies document.

Create Deployment plan,review and Implement

Create and deploy new control-M jobs and schedule it.

Check and verify the Production health using Wily and Geneos.

Involve and work with Production support activities Like Work on the Application Ticket, Schedule Release Plan and Participate DR Test

Review Performance result and provide the recommendation.

JP Morgan Chase-Service Action Manager (SAM), Florida, US

System Architect (February 2011 to Mar 2012)

Business Problem: JPMC want to handle the client bank account inquiry and maintenance request through a guided process .It involves creating the case and assign those cases to different channel of people. The case Records each client interaction and stored in the system. The inquiry received from the client by various channel like Phone, email, mail and fax which is processed by different set of agents. The processed data shared across different group of people for reporting purpose. The application integrate with many external systems like WCRM, eSouce, IVR, ISB and Service Portal to retrieve various client information before the case get processed.

Environment: PegaRULES Process Commander (PRPC), CPM,Solaris, Oracle,Weblogic,Wily,NDM and Control-M

Project Role: System Architect with the following responsibilities:

Understand system architecture and various external Integration

Understand the client requirement and prepare the estimate

Prepare and review High level and detailed system design document

Develop Approach & Recommendation document for new client requirement

Review Design plan and update

Create Deployment plan,review and Implement

Create and deploy new control-M jobs and schedule it.

Check and verify the Production health

Review Performance result and provide the recommendation.

Experience at Virtusa

AIG-PRPC Environment Consolidation, New Jersey, US

System Architect (December 2010 to February 2011)

Business Problem: AIG Chartis Has Upwards Of 80+ PRPC Environments Consisting Of Up To 5 Instances/Servers Per Environment. Support and Maintenance are challenging as well as costs are high and growing. The objectives are to determine if PRPC Environments can be consolidated to reduce the costs also determine an approach And Roadmap for consolidation on two environments

Environment: PegaRULES Process Commander (PRPC), UDB,Oracle & Websphere

Project Role: System Architect with the following responsibilities:

Review & Evaluate PRPC Environments For Opportunity To Consolidate

Provide High Level PRPC Environment & Architecture Design Principles

Provide High Level Roadmap For PRC Environment Consolidation

Develop Approach & Recommendation For Consolidation On Two Environments

Estimate and Schedule Development plan and review.

TENET – Billing Editor Studio (BES), Texas, US

System Architect (September 2009 to November 2010)

Business Problem: Patient Financial Services (PFS) currently follows a paper process to update the edit formulas used by the Claims Clearinghouses to process Tenet claims. Edits generally arise from updates in CMS regulations, and must be implemented in a timely manner. The current process involves a paper request form that is routed through several approvals and then forwarded to an outside vendor for implementation.

In the past, communication has been lost between the approvals within Tenet and coordination between vendors and PFS. By creating an automated workflow for the edit approval process, Tenet will begin to eliminate the miscommunications, provide a current status of each edit, and integrate the approval process with Perot development team implementation.

The Billing Editor Studio project will allow facility and corporate employees to create a request for a clearinghouse edit via an online request form. The request form will be systematically routed to the appropriate users for approval, development, and implementation. Users will have the ability to check the status of completed and processing requests and manage their approval tasks online. Billing Editor Studio project will be available to users through the eTenet web portal utilizing single sign-on with eTenet user IDs and passwords

Environment: PegaRULES Process Commander (PRPC), Java, SQL Server & Websphere

Project Role: System Architect with the following responsibilities:

Focused on BES Enterprise architecture design

Understand client requirements and delivery.

Indentify different point of System Integration and provide better Integration approach

Preparing System Design and Create process flows using PegaRULES Process Commander

Deployment of rules into different environments like QA, UAT

Estimate and Schedule Development plan and review.

Providing technical support and Code Review using Pega Guard rails

TENET-PEGA, CC Framework,Texas, US

Tech Lead (September 2008 – August 2009)

Business Problem: The architecture is designed to provide loose coupling between the application processes and the Enterprise connectivity functionality. Tenet BPM applications running under PegaRULES Process Commander (PRPC), will be interfacing with Tenet’s enterprise applications, sending and receiving information. The main business functionality was auditing the individual hospital entities, create the exception and provide the remediation plan. Future applications may require sharing information beyond Tenet enterprise applications to, for example, industry sites or government agencies.

Environment: PRPC 5.3 Sp2, Java, SQL Server 2005, IBM Web sphere 6.1

Project Role: Tech Lead with the following responsibilities:

Primarily focused on the architecture and design of the CFDB Enterprise Integration.

Responsible for testing connectivity to and from the external system.

Responsible for understanding client requirements and delivery.

Responsible for identifying the individual team task and monitoring them.

Responsible for code review and provide the quality delivery to the client.

JPMC-CLS

Integration Architect (July 2008 to August 2008)

Business Problem: Hot Docs is an external application used for the assembling of loan documents. With Assemble Documents, the system interfaces to Hot Docs by writing the required Doc fields to a row in a common database. The user then logs into Hot Docs and continues with document generation. Pega will save a record to an Oracle database. The record will be picked up by Hot Docs to generate the Answer File. Hot Docs integration runs by using Data Model (Table layout).

Environment: PRPC 5.3 Sp2, Java, Oracle, IBM Web sphere

Project Role: Integration Architect with the following responsibilities:

Primarily focused on the architecture and understanding the existing whole system

Responsible for understanding client requirements and delivery

Involved in customizations of the existing CC framework functionality

NASCO, WSTI (Web Service Test Interface)

Tech Lead (May 2008 to July 2008)

Business Problem: The objective of this project is to produce a simple way of use, maintain, browser based tool for testing NASCO Web Services. Authorized users should be able to access the tool, select a Web Service from a list of available NASCO Web Services, provide the required input parameters and after submission or the request, receive back the appropriate web service response. Authorized NASCO Administrators should be able to maintain easily by including the ability to add new, fully functional, and services without requiring technical assistance.

Environment: PRPC, Java, DB2, IBM Web sphere

Project Role: Tech Lead with the following responsibilities:

Primarily focused on the architecture and design of the whole system

Responsible for understanding client requirements and delivery

Involved in external services integration and end-to-end security for the application (including SOAP)

Responsible for identifying individual team task and monitoring.

NASCO, 834 Run In Review (RIR)

Tech Lead (May 2008 to July 2008)

Business Problem: The scope of the project includes designing an application to run 834 records in review mode; make the Run in Review process complimentary to the existing 834 file process and make any updates necessary to the existing 834 Companion Guide documentation.

Environment: PRPC, Java, DB2, IBM Web sphere

Project Role: Tech Lead with the following responsibilities:

Primarily focused on the architecture and design of the whole system

Responsible for understanding client requirements and delivery

Involved in external services integration and end-to-end security for the application

Experience Prior to Virtusa

Ford, Warranty Strategic Initiative (WSI)

System Architect (February 2008 to April 2008)

Business Problem: Create Business Rule Engine (BRE) for maintain and manage the Claims Adjudication process over automobile industries.

Environment: PRPC, Java/J2EE, DB2, Mainframe and IBM Websphere

Project Role: PRPC System Architect with the following responsibilities:

Responsible for understanding client requirements and delivery

Responsible for preparing design and Creation of process Flows using PegaRules Process Commander

Responsible for designing the Database design and ER Diagram

Development of business rules in PRPC

Responsible for estimation and Scheduling for Development and review plans

Chrysler Financial Services, BRE (Business Rule Engine), Michigan, US

PRPC System Architect (October 2007 to January 2008)

Business Problem: Business Rules Engine (BRE) is the application which automates the process of evaluating the required forms list (RFL) for processing a deal received from dealers and for a verified transaction only, based on the governing rules. BRE is a subset of Contract Validation Management (CVM).

Environment: PRPC, Java, DB2 and IBM Websphere

Project Role: PRPC System Architect with the following responsibilities:

Responsible for understanding client requirements and delivery

Responsible for preparing design and Creation of process Flows using PegaRules Process Commander

Responsible for designing the Database design and ER Diagram

Development of business rules in PRPC

Responsible for estimation and Scheduling for Development and review plans

Responsible for collecting and maintaining Metrics for review defects and

AIG, A & H (Accident & Health)

PRPC System Architect (April 2007 to September 2007)

Business Problem: Group Plus requires a systems facility to process new business for 2 (new and existing) Group Plus products. Formerly, Group Plus have used AIG eXtra to process their business but because of the lead times involved in introducing new range of products plus and need to process ‘multi location’ business .It has been determined to develop the system called Group Plus, in tandem with the Pegasystems provider

Environment: PRPC, Java, Oracle, TOAD, IBM Web sphere

Project Role: PRPC System Architect with the following responsibilities:

Responsible for understanding client requirements and delivery

Responsible for preparing design and Creation of process Flows using PegaRules Process Commander

Responsible for designing the Database design and ER Diagram

Development of business rules in PRPC.

Responsible for estimation and Scheduling for Development and review plans

Responsible for collecting and maintaining Metrics for review defects and Testing defects

Responsible for providing technical and build support for development teams

AIG, EPLI

PRPC System Architect (Feb 2007 to March 2007)

Business Problem: The objective of this project is to implement the new product called EPLI in the existing application in Europe. This involves three major flows for the outer wrapper, product wrapper and policy wrapper. The outer wrapper involves producer, client searches and the product selection. Once product is selected premium is calculated using Product configuration based on the rater questionnaire. Then quote is generated and documents are sending for printing, using docucorp integration. The product and policy searches are using Estart tool, which also generates the submission number. Basically docucorp and Estart integrations are involved in this project. The concept of localization is also in focus for this project as this is deployed among two countries.

Environment: PRPC, Java, Oracle, TOAD, IBM Web sphere

Project Role: PRPC System Architect with the following responsibilities:

Responsible for understanding client requirements and delivery

Responsible for preparing design and Creation of process Flows using PegaRules Process Commander

Development of business rules in PRPC

Responsible for estimation and Scheduling for Development and review plans

Responsible for collecting and maintaining Metrics for review defects and Testing defects

Responsible for providing technical and build support for development teams

AIU, ABC [Agent Brand Customer]

PRPC System Architect (September 2006 to January 2007)

Business Problem: ABC Automation will be built to handle end to end policy life cycle of all lines of business (LOB). Policy Administration will all be done in PRPC. Class and ruleset definition will be designed in such a way that all these transaction types will be written with a generous amount of reuse across lines of business and country. LOB and country differences will be clearly defined and easily managed in a PRPC architectural perspective.

Environment: PRPC, Java, Oracle 8i, TOAD, Apache Tomcat 5.0

Project Role: PRPC System Architect with the following responsibilities:

Responsible for understanding client requirements and delivery

Responsible for preparing design and creation of process Flows using PegaRULES Process Commander

Development of business rules in PRPC

Responsible for estimation and Scheduling for Development and review plans

Responsible for collecting and maintaining Metrics for review defects and Testing defects

Responsible for providing technical and build support for development teams

Standard And Poor’s, Rating Process Management

PRPC System Architect (February 2006 to September 2006)

Business Problem: Standard & Poor's is the world's foremost provider of independent credit ratings, indices, risk evaluation, investment research and data. An essential part of the world's financial infrastructure, Standard & Poor's has played a leading role for more than 140 years in providing investors with the independent benchmarks they need to feel more confident about their investment and financial decisions.

Founded in 1888, The McGraw-Hill Companies is a leading global information services provider meeting worldwide needs in the financial services, education and business information markets through leading brands such as Standard & Poor's, McGraw-Hill Education, Business Week and J.D. Power and Associates.

Environment: PRPC, Java, Oracle 8i, TOAD, IBM Web Sphere

Project Role: PRPC System Architect with the following responsibilities:

Responsible for understanding client requirements and delivery

Responsible for preparing design and Creation of process Flows using PegaRULES Process Commander

Development of business rules in PRPC

Responsible for estimation and Scheduling for Development and review plans

Responsible for collecting and maintaining Metrics for review defects and Testing defects

Responsible for providing technical and build support for development teams

Pega System, PEGA Internal Application Development

PRPC System Architect (December 2005 to January 2006)

Business Problem: Purchase Order (PO) Application was redesigned and rebuild on PRPC Version 4. The existing processes were modified to cut across various functions like Purchase, HR, Finance, Stores etc. to facilitate information sharing and faster decision making. The newly built application integrates with “Solomon” and “HRIS” system to get the organization hierarchy and employee details for workflow routing. The application disseminates information through various means like e-mail correspondence and reports. The exception rules for the PO process have been incorporated into the application and the handoff between parties is monitored through predefined SLA’s. The users are authenticated using LDAP

Environment: PRPC, Java, DB2, IBM Web Sphere

Project Role: PRPC System Architect with the following responsibilities:

Analysis of the functional specifications & design

Analysis of the requirements and creation of use-cases.

Study of the existing system and software modules in terms of functional and technical perspectives

Developing the custom rules

Integration of the Modules

Suncorp, SMILE (Brisbane, Australia)

PRPC Workflow Architect (June 2005 to December 2005)

Business Problem: SUNCORP is a finance and insurance retail banking [SMILE] providing the various loans and credit card to the customer. It has various working operator [User] involving like approval types of activates for each kind of loan or the Credit card. The application for each customer flow through necessary step through operators to process the next step to get the loan or credit card approved. The application may get approved or declined from the operator based on status flag. The loan or card will be issued, once the applicant satisfies all required information from the operators. In this project [SMILE] entire flow of applicant’s application done by PEGAWORKS [CRM] tool.

Environment: PegaWorks, JavaScript, Oracle

Project Role: Workflow Architect with the following responsibilities:

Create HTML UI using GMENU rule files

Creating the work items

Creation of GDOORULE and GRSELECT for implementing core business logic

Extensively worked on flow rules to implement business logic

Implementation of ITable, GRDB

Preparation of test case and test reports for testing the application

Testing and debugging using tracer

Satyam, BSL (Business Solution Lab)

PRPC Programmer (February 2005 to March 2005)

Business Problem: To develop the client interaction and feedback project. The client could visit the business lab. While visiting user should be welcomed and can view the details and feedback for the past visitors. Once, user visit the lab, they could enroll their feedback like company details project information and domain experts. The feedback could be audio, Video or text. This data is being updated in the project admin part and displayed to the next visitors. It consists of three module like Customer Visit (Guest Book), Project History and Admin Part.

Environment: Java/J2EE, JavaScript, SQL Server, IBM Web sphere

Project Role: Programmer with the following responsibilities:

Responsible for coding and development of Project History and Admin part

Responsible for application unit testing and debugging

Responsible for system integration testing

IIPE, IIPE Information Management Architecture

PRPC Programmer (April 2003 to September 2003)

Business Problem: IIMA is a Web based distributed application developed to provide an optimal business model for IIPE’s entire corporate activity and student feasibility and flexibility. The system enables the administrative office to effectively administer their courses. The IIMA system comprises of a central server site that runs the Web server. Student personal details, Education qualification and Institute center preference data



Contact this candidate