Project Developer

Subhransu Sekhar Panda Capgemini, USA

Subhransu Sekhar Panda

Lead Consultant, Capgemini

Washington D.C.

Email: **************@*****.***

Phone: +1-202-***-****

Subhransu Sekhar Panda Capgemini, USA

Experience Summary

• 10+ years of work experience in Software Industry includes experience in Analysis,

Design, Development, Implementation using Java, J2EE, Messaging & EAI in BFSI domain.

• 4 years of Experience in Leading Teams and coordinating between onshore and

offshore developers.

• 3 years of onsite experience.

• 2 years of Guidewire ClaimCenter experience

• 6 months of Guidewire PolicyCenter experience.

Technical Expertise

• Guidewire Claimcenter 7.0

(i) Worked in configuration & integration

(ii) Reflection, postonchange, list view, detail view, Datamodel

(iii) Rules, Enhancements, Gosu

(iv) GX Models, Messaging, WS-I Webservices, Plugins, Batchprocess

(v) Workflows, Activity Patterns

• Guidewire PolicyCenter 8.0

(i) Worked on integration

(ii) GX Models, Messaging, Webservices

(iii) Gosu, Rules, Enhancements, GUnits

• TIBCO Activematrix Businessworks

(i) Designing process flows with various palettes in TIBCO Designer like XML, JDBC, File,

JMS, SOAP Webservices, Schema, XPath, XSD etc.

(ii) Error handling, Debugging and testing process flows

(iii) Deploying and production support including certificate implementation.

• TIBCO Administrator

(i) Deploying process flows & managing global variables

(ii) Maintaining and monitoring process flows.

• IProcess

(i) IProcess modeler

(ii) IProcess workspace browser

• TIBCO Rendezvous

(i) Creating messages through Java & FIX. Pub/sub messages.

• Core Java

(ii) Collection framework, Executor framework, Multithreading & Synchronization

(iii) JDBC, annotations, generics, memory management & Garbage collection

(iv) Exception handling, Serialization, Cloning

(v) Design patterns like Singleton, Factory, and Observer etc.

(vi) OOAD, UML using starUML

• MQ Series

(i) Creating and administering MQ Objects

(ii) Sending receiving messages to and from queues

• Message Broker

(i) Creating message structures and message flows with ESQL

(ii) Build and deploy message flows

• Java J2EE

(i) Experience on JSP, Servlets, struts & Javascript

Subhransu Sekhar Panda Capgemini, USA

(ii) Tomcat, weblogic application servers

• Database

(i) Oracle, Sybase

(ii) SQL, stored procedures, triggers

• Other technologies, tools, protocol etc

(i) FIX 4.4 protocol

(ii) Trading application & FIX Engine

(iii) Straight through processing

(iv) JCharts API, DRools

(v) SVN, CVS, Perforce version control

(vi) Junit, ANT, Maven build tools

Professional Experience

• Capgemini USA, from Aug 2014 to till date

• HCL Technologies, Bangalore, from Feb 2009 to Aug 2014

• Tata Consultancy Services, Kolkata, from Aug 2004 to Jan 2009

• ITER, Bhubaneswar, from June 2002 to August 2004

On-Site Experience

• 2 years in Tokyo, Japan – Nov, 2006 to Oct, 2008

• 0.6 years in USA – Feb, 2012 to July, 2012

• 1.4 years in USA – Jan, 2014 to till date

Customer Worked For

• The Hartford

• GEICO

• Deutsche Bank

• Citi Bank

• SMBC Bank, Japan

• GE

Domains Worked For

• Insurance using Guidewire ClaimCenter & PolicyCenter

• Banking Straight Through Processing using TIBCO Businessworks, IProcess

• FX Currency Trading using FIX Protocol

• Banking New Account Opening using MQ Series and Message Broker

• Banking GE Money dashboard.

Certifications, Training & Achievement

• Basics Of Banking certification

• Java training from IIT Kanpur, india

• Attended ACM IC/PC International Programming contest at IIT Kanpur, india

Education

• Bachelor of Engineering in Computer Sc & Engineering at VSSUT(formerly known as

UCE Burla) in 2001

Subhransu Sekhar Panda Capgemini, USA

Professional Experience

Project # 1

Client: The Hartford

Location: Hartford, CT

Period: Aug 2014 – till date

Position: Integration Developer

Project: ComPAS (Guidewire PolicyCenter Implementation)

The project ComPAS is an implementation of Guidewire PolicyCenter. The Hartford has so many legacy

applications to support the Policy Administration and because of which they have encountered huge system

complexity and data inconsistency. The new project ComPAS is designed to resolve the issues for The

Hartford.

The project ComPAS is in solution development phase. I belong to integration team. Our team is doing the

development work for all the integration requirements starting from Account, Submission, Claim to Billing

systems. I have been part of Account and Document integration. And I have got opportunity to develop

various webservices publishing and consuming. Also I have worked on GX Models, sending the GX Model

messages to down stream by Request/Reply/Transport plugins.

Responsibilities:

● Interaction with customer for gathering the requirements

● Converting the requirements to High Level Design Documents

● Converting the requirements in Detailed Design Documents. Detailed design includes –

• Flow diagram

• Sequence diagram

• Component diagram

• Testing strategy, Testing scenarios etc.

• Environment & other documentation

● Developing the following components –

• Webservice APIs,

• Webservice client,

• GX Model for webservice input/output.

• Request/Reply/Transport messaging plugins, Startable Plugins

• Pogo Classes, Enhancements.

● Testing the service

Solution Environment

Guidewire PolicyCenter 8.0, VISIO, SOAPUI, XMLSpy, SVN

Project # 2

Subhransu Sekhar Panda Capgemini, USA

Client: GEICO

Location: Washington D.C.

Period: Sep 2013 – Aug 2014

Position: Integration Developer

Project: ATLAS (Guidewire ClaimCenter Implementation)

The project is an implementation of Guidewire Claimcenter. GEICO has done customization of all the major

functionalities and I am associated with the Salvage functionality. There are basically two types of changes

we are handling -

1. Generating transactional message

2. Implementing change requests for Salvage module.

Generating Transactional Message: This part of work mainly associated with creating XML payload using

GX Models and sending the payload to the desired destination. The payload generation mainly happens on

event messaging. We write rules to trigger the payload creation which intern creates the XML Payload using

GX Models. Examples of transaction includes: Salvage charge, Vehicle location, yard pick up etc.

Implementing Change Requests: Implemented various change requests w.r.t Salvage in UI and code

changes. Example is creating an activity 3 days from the input release date. This is a preupdate rule and

workflow implementation.

Responsibilities:

● Analysis of requirements, Work estimation.

● Coding in Guidewire that includes

1. Gosu scripts, Enhancements

2. Workflow, Activity Patterns

3. PCF Files

4. Rules, Event Messaging, Webservices

5. Plugins, GX Models, Batch Process

6. Datamodel etc.

● Debugging and Testing

● Client Interaction, Offshore co-ordination.

Solution Environment

Guidewire Claimcenter 7.0, Star UML, SOAPUI, XMLSpy, Perforce

Project # 3

Client: Pohjola, Finland

Location: Bangalore

Period: June 2012 – Sep 2013

Position: Integration Developer

Project: Pohjola Claim Center

The project is an implementation of Guidewire Claimcenter. Worked on integration for Address

Standardzation and Doument management system. The address standardization was a webservice

synchronous integration. And I have used Gosu templates to create the input/output xml data.

Subhransu Sekhar Panda Capgemini, USA

1. Consuming webservices for address standardization from various screens.

2. Consuming webservices for Document services.

Responsibilities:

● Analysis of requirements, Work estimation.

● Coding in Guidewire that includes

1. Gosu, Gosu templates

2. Webservice collection

3. PCF Files

4. Event messaging

5. Datamodel etc.

● Debugging and Testing

● Client Interaction.

Solution Environment

Guidewire Claimcenter 7.0, Star UML, SOAPUI, XMLSpy, Perforce

Project # 4

Client: Deutsche Bank - PWM

Location: Jersey City, NJ

Period: March 2010 – May 2012

Position: Technical Lead

Project: STP Banking – Straight through processing

This project deals with automation of banking transaction tickets. There are three types of tickets ICT, CD &

BIB

Tickets are submitted by CFP and are transacted automatically. In some scenarios tickets are rejected or

routed to manual queue. If all goes well tickets are processed STP, means the debit and credit happens and

the ticket status is updated.

Tickets are submitted through Salesforce and are routed to java application server, where various validations

are done. Then the ticket is submitted to JMS queue where it is submitted to TIBCO BW application. BW

application creates a workflow for the ticket in Iprocess. Then the ticket goes through various validations and

then transactions. At last the status of the ticket is updated. If the ticket is not processed STP, then it moves

to manual queue.

In case of any failures in processing an error email is generated.

Responsibilities:

● Analysis of requirements, Work estimation.

● Coding in TIBCO, Iprocess & Java, build and deployment.

● Debugging and Testing

● Client Interaction, Offshore co-ordination.

Solution Environment

Subhransu Sekhar Panda Capgemini, USA

TIBCO Businessworks, IProcess, TIBCO Administrator, Database, Salesforce

Project # 5

Client: CITI Bank – Foreign Exchange

Location: Bangalore

Period: Feb 2009 – Feb 2010

Position: Technical Lead

Project: FIX Engine – Custom Scheduler

FIX Engine is the interface between CITI and its client and it facilitates connections for FX trading between

CITI and its client. FIX Engine do have its own scheduler provided by a third party vendor which schedules

the connection between CITI and its clients.

But the existing scheduler can schedule a connection at minute level(HH:MM). So we developed a custom

scheduler which schedules the connection at seconds level(HH:MM:SS).

In addition to that the custom scheduler has time zone, on/off, connection reset functionalities.

Most importantly, the custom scheduler is developed as a template so that different scheduler template can

be created. And different client connections can be associated with different types of scheduler templates.

Responsibilities

● Analysis of requirements, Work estimation.

● Build, Deploy, Coding, Debugging, Testing.

● Client Interaction

Solution Environment

TIBCO RV, FIX 4.4, Core Java, Executor framework, JMS, log4J

Project # 6

Client: CITI Bank – Foreign Exchange

Location: Bangalore

Period: Feb 2009 – May 2010

Position: Technical Lead

Project: AutoResponse – BatchPricing

Responsibilities

● Analysis of requirements, Work estimation.

● Build, Deploy, Coding, Debugging, Testing.

● Client Interaction

Solution Environment

Core Java, TIBCO RV, JMS, FIX 4.4, SVN

Project # 7

Client: SMBC Bank, Japan

Location: Tokyo, Japan

Period: Sep-2006 to Jan-2009

Position: Senior Developer

Subhransu Sekhar Panda Capgemini, USA

Project: EAI MQ Series Project

This is an integration project. All the legacy systems are integrated to a common platform. There are about

20 interfaces which uses MQ/Broker for data interchange asynchronously. The application is to integrate

Metavante system and NAO applications data.

Custom adapters developed in MQ Java are used to fetch/upload data from DB/queues interchangeably.

The messages are sent to Broker through MQ for further processing. Broker returns the messages to MQ

and then messages are fetched from the respective queues as per their message ID and proceeds with any

of the following like –

● sent to different Queue managers

● uploaded to DB

● create custom format file.

● FTP-ed to different server.

Along with this we have developed certain monitoring tools to keep track the status of Channels, Listeners,

Queue depths and all other servers. These monitoring tools shows different elements and their status as

“OK”, “Warn” or “Down”. If one particular queue depth surpass the warning level the specific component color

changes, it beeps and sends an SMS too.

Responsibilities

● Analysis of requirements, Work estimation.

● Setting up production environment.

● Coding, Stored Procedures, Triggers & Optimization.

● Writing Message flows, message Sets, TDS, CWF.

● Monitoring, Implementation Support.

● Client Interaction, Offshore co-ordination.

Solution Environment

IBM MQ Series, Message Broker, MQ Java, JGroups, SQL, Triggers, JDBC, Shell Script, log4J,

JavaMail, Tomcat

Project # 8

Client: GE Money – Global

Location: Kolkata

Period: Aug - 2004 to Aug 2006

Position: Software Engineer

Project: Vision+ Dashboard

The Dashboard is an intranet application, which shows status of different SLAs of various countries for a

selected period of time.

The Dashboard has 4 stages mainly –

1. Login Stage [User Authentication]

2. Dashboard Stage[Showing weekly status of SLAs with smilys]

3. Dashboard Graph Stage [Shows status graphically, either bar chart, line chart, bar-group chart or Pie

chart]

4. Dashboard detail stage [Shows detail data in tabular structure and with pages. The records could be

sorted on clicking the header, also displayed with colors as per their severity]

Subhransu Sekhar Panda Capgemini, USA

The Advantages are –

- For easy data uploading

- For easy status analysis

- User friendly

- Better control in terms of data security.

- Highly scalable, it is easy to replicate for new countries.

- Stage 2 shows the status of all the SLA’s with simileys. There are 10 SLA’s, and as of now we are

maintaining it for 4 countries like Hungary / Australia / India / Mexico of Vision Plus.

- Stage 3 shows the status either in BarChart or LineChart or Pie Chart. The first four SLAs show data in

BarGraph, and the rest four SLAs display the status in LineChart. JCharts is mainly used to draw customized

graphs with different parameters. (e.g. date range, Severity)

-By clicking on the graph at level-2 it takes the corresponding x-axis value and fetches records based on that

and displays it tabular format in the next level.

We have designed separate macros to upload the data.

1. Data is uploaded in the template and Validated.

2. And the file is saved with *.csv extension.

A particular SLA is selected from the drop down as shown below. And then the file is uploaded.

Responsibilities

1. Analysis of Requirement, Work Estimation

2. Development and Production server Migration.

3. Stored Procedures & Optimization.

4. Coding, Testing and Implementation.

Solution Environment

JCharts, Java, Servlets, JSP, Struts, JDBC, Java Script, Stored Procedure, NetBeans IDE, PLSQL

Developer, JBoss

Personal Interest

• Developing computer games in my spare time.

• I love teaching people.

Contact this candidate