PROJECT PROFILE:

#1(a) Project Name: CMI Applications- RETAIL.

RETAIL is an application where customers first lands when he visits citimortgage.com everything he can
do there without the need of logging in, is in scope of RETAIL

This application is to provide information on Mortgage loans for the customer. The main functionality of this
application is comparing the loans between the different type of loans offering from Citi Mortgage,
Refinancing a Home and customer to apply online for any loan.
This application provides the Customer with an approximation of how much they can afford for a mortgage

Environment: Struts 1.1, Tiles, XML, Velocity Framework, Servlets.

Database : Oracle 9I
Tools : RAD 6.0 integrated with Websphere 5.1 App Server.
Client : Citibank - St. Louis USA.
Role : Development & Support Team Member
Team Size : Onsite (2) Offshore (1)
Type : Major Enhancements & Bug Fixing and Performance Tuning.
Model : Onsite- Offshore Model

Responsibilities :
• Responsible for preparation of System Appreciation Document.
• Implementing the functionality of the new Change Control’s in the project releases.
• Performing Unit Testing of the implemented functionality.
• Fixing the bugs if raised in Integration, System Testing, and User Acceptance Testing.
• Providing the production support and resolving the tickets.

#1(b). Project Name : CMI Applications – Correspondent Lending

Correspondent Lending is a key initiative of CitiGroup intended to implement a user-friendly, “self-help”

enabled, web based front-end system to be accessible to its correspondents. This is one of its applications
in Real Estate Lending (REL) domain. Correspondent Lending’s process involves independent mortgage
correspondents who are not employed by a specific lending institution. These correspondents “shop”
various lending institutions to find the best loan for their client. The independent mortgage correspondents
uses the lender’s, like CitiMortgage, funds to close loans in either their own name or the lenders name. The
mortgage correspondent is typically responsible for completing the mortgage application and ordering the
title search, appraisal, and flood certification. All other processing is usually completed by the lender on the
lender’s origination system. CMI’s correspondent Lending division is comprised of regional branches

Environment: Struts 1.1, Tiles, Filters, JSP, Servlets, Hibernate, Ajax, SOAP.
Database : Oracle 9i
Tools : RAD 6.0 integrated with Websphere 5.1 App Server.
Client : Citibank - St. Louis USA.
Role : Development & Support Team Member
Team Size : Onsite (4) Offshore (1)
Type : Major Enhancements & Bug Fixing and Performance Tuning.
Model : Onsite- Offshore Model

Responsibilities :
• Responsible for preparation of System Appreciation Document.
• Implementing the functionality of the new Change Control’s in the project releases.
• Performing Unit Testing of the implemented functionality.
• Fixing the bugs if raised in Integration, System Testing, and User Acceptance Testing.
• Providing the production support and resolving the tickets.

#2. Project Name : Build-It

The project build-it is developed for meeting the needs of Home Loans, Home Improvement Loans and
Home Mortgages. There are 3 portals under this project that have been developed to meet the home
mortgages LOB for Citibank.

1) Citi home equity portal for Brokers

2) My home equity portal for Consumers
3) Admin Module for administering both portals.

1) Citi home equity portal for Brokers

Citi home equity portal (www.citihomeequity.com) is basically developed for brokers who operate in
designated area assigned by citigroup for handling customers who require home mortgage loans. Each
broker is assigned a source code and channel when he registers himself with citigroup and he can operate
in that area for the customers who require the loan.
A broker needs to obtain the information required by citibank for obtaining a decision for approval or
rejection of the loan from the customer and fill it in the application along with his commission details. The
application would be reviewed by citigroup designated authority and the decision will be made to accept the
application or reject it.
This portal can be used by the brokers who are registered with citigroup only and
can operate only in the area that has been assigned to them while registering with citigroup.

2) My home equity portal for Consumers

My home equity portal (www.myhomeequity.com) is basically developed for consumers who can directly
access the portal and fill the personal details, loan details, property details and repayment amount details,
repayment term details etc.
Each consumer will be given a login id and password on registration and henceforth the consumer can
track his loan status by directly logging to the application.
As soon as the application is reviewed by citigroup designated authority, the status of whether the loan has
been sanctioned or rejected is updated against the login id of consumer given at the time of filing the
application, which can be used for tracking the status of application by the consumer.

3) Admin Module for administering both portals

The admin module controls both the websites for the dynamic data that is displayed
E.g.:
1) Latest offers given by citi against home loans
2) Updated interest rates etc.
3) Online application forms in PDF formats.
The core functionality of this portal is to allow easy customization of the citi home equity and my home
equity for displaying the latest offers given by citigroup w.r.t home loans and also to change the images that
are displayed in the website from time to time depending upon the instruction by citigroup stakeholders for
this project.

Environment: Struts, Tiles, XML, EJB, JSP, Servlets, Filters and JavaScript.
Database : Oracle 9I
Tools : WSAD 5.1 integrated with Websphere 5.1 App Server.
Client : Citibank - St. Louis USA.
Team Size : Onsite (5) Offshore (4)
Type : Major Enhancements & Bug Fixing and Performance Tuning.
Model : Onsite- Offshore Model

Responsibilities:
• Key member for Browser Compatibility of both the portals.
• Impact Analysis
• Searching for Best fit Solution
• Coding
• Unit Testing and System Testing.
• Responsible for preparation of Unit Test Cases.
• SCMA Role for this Project.

# 3. BACS-VOCA REF DATA, Voca Group, UK

VOCA Ltd is an automated clearinghouse responsible for bulk clearing of electronic payments between
bank accounts, processing direct credits, direct debits and standing orders. Established in 1968, VOCA is
owned by UK’s major banks and building societies. On a peak day it handles around 41 million electronic
payments. It has 15 direct members, some of whom offer sponsorship arrangements to around 35,000
other institutions, which allow non-banks to send transactions directly to BACS for clearing. Over 100,000
companies are currently registered users of the BACS 3 Day service, including all of the FTSE 100
companies.
VOCA started developing a new solution to replace the legacy REFT system with the new solution
designed to re-engineer VOCA services and the underlying technology to provide its members and users
with a payments service, which would provide superior levels of service. These improvements include a
much higher degree of flexibility in the core business processing, higher capacity, and a quicker turnaround
on payments as required.
Reference Data is one of the key applications of the new solution, which manages the bank and
customer reference data.

Environment : J2EE, EJB, Struts, Oracle, WebLogic

Client : VOCA, UK
Team Size : 10

Responsibilities :
• Implementation of Change Requests
• Defect Tracking and Fixing.
• Preparing the checklists for code reviews for manual audit changes in the code base.
• Communicating with Testing Team.

# 4. Includix, Includix Corporation, US.

Includix is an organization, which deals with attending customer requirements. This site provides
online solutions for their customer’s. Once the customer is registered with the organization he can get the
services provided by the site with in valid period. The following modules support customers to keep track.
Registration module, Customer module, Sales module, Support module, Sub Manager Module, Super
Manager module and Transaction module.

Environment : Java, EJB, Servlets, JDBC, JSP, Oracle and WebLogic.

Client : Includix Corporation, US.
Team Size :6

Responsibilities:
• Responsible for coding.
• Responsible for preparation Unit Test Cases.
• Responsible for Unit Testing.

# 5. HIL Enterprise Sales and Distribution System, Hyderabad Industries Ltd.

Hyderabad Industries Limited, leading manufacturers of Asbestos Sheets, Home and Office
furniture has a very large Distribution Network and Sales force all over India.
The distribution Network includes Manufacturing Plants, Depots, Distributors, Zonal Offices,
Retailers, Marketing offices, Sales offices. They have Single digit Manufacturing plants, Depots and double
digit number Zonal offices, Marketing offices, sales offices.
The sales force includes General Manager, regional Sales Manager, Area Sales Manager, Field
force. The application should integrate all the processes of HIL Distribution related and provide up-to-date
online information to all the positions.
The systems department needs a MIS to generate reports automatically for Manager. Top
management needs a Decision Support system to help to take effective decision on the basis of real time
data.

Environment : Servlets, JSP, JDBC, Oracle, Web Logic

Client : Hyderabad Industries Ltd.,
Team Size :5

Responsibilities:
• Responsible for coding.
• Responsible for preparation of user entry screens.
• Responsible for Unit Testing.
• -----------------------------------------------------------------------------------------------
Project Summary

#6: Clinical Operating System

Software : Swings, EJB, Servlets, jdk1.4.2_10

Operating System : Windows
Application Server : Web Logic
Databases & tools : MSSQL
Team Size : 20
Duration : 10 Months

The Medplexus Application serves the medical community by developing robust administrative,
financial, and clinical solutions. Physicians across the US are using our software and services not just to
enhance patient care, but also to improve practice efficiency, reduce costs, and strengthen information
exchange with other healthcare entities and patients. This Application has 4 different modules namely -
POMS (Practice Management), EHR (Electronic Health Records), EDI (Electronic Data Interpreter) and
Reports.

The Reports module deals with generating reports for the user according to his requirement. The
application maily deals with developing itext (PDF, HTML etc) and excel reports. As per the requirement
from the clients and the scope of the application the reports goes on changing for each release. All the
User Interface forms are designed using Swings application. And internally these forms are communicated
using EJB servlets.

#5: Affiliate Management System

Software : Struts, JSP, JDBC, JavaScript

Operating System : Linux
Application Server : jboss-4.0.2
Databases & tools : MSSQL
Team Size : 15
Duration : 2 Year

The Affiliate Management System is a web based Application developed for the Affiliates to make
their product sales online. The company has basically 4 different types of products - Ink cartridges, Diabetic
products, Mortgage lead, Diabetic leads for sale. The actual procedure involves the process of affiliates
signing up and becoming a vendor for selling all the products or may be one or two products as they wish.
And they will get the commission for each product sale. All the reports of the affiliates sales, hits,
commission for orders, etc are maintained in the backend.

Responsibilities

• Development Mother sites for the products

• Development of the Affiliate reports for Commission, payouts, hits etc.
• Extensively used JavaScript for client side validation.
• Integration and maintenance of the application
• Engrossed in testing the application.
• Documentation of LLDs and Unit test Cases.

#4: CLINIX

Software : JSP, Servlets, JDBC, JavaScript

Operating System : Windows 2000
Application Server : jboss-4.0.2
Databases & tools : Oracle 8i
Team Size : 12
Duration : 6 Months

CLINIX is user friendly software designed to meet the needs of hospitals. This project checks the
Inpatient, Outpatient details, Diagnosis, Treatment, Billing and pharmacy. Also accounts of the hospital are
consolidated and the cashbook id generated at any interval that the user wishes. To maintain the personnel
matters inventory, indents and billing is also available in the system. The pharmacy module deals with all
aspects of indents placing and follow-up of orders, payments, sale and supply of medicines as well as
stock checking is possible with the different criteria

Responsibilities

• Development of Inventory, Billing and Pharmacy Modules

• Responsible for resolving issues/bugs reported by the testing team
• Extensively used JavaScript for client side validation.
• Integration and maintenance of the application
• Engrossed in testing the application.
• Documentation of LLDs and Unit test Cases.

#3: Debit Card System

Software : JSP, Servlets, JDBC

Operating System : Windows NT
Application Server : jboss-4.0.2
Databases & tools : Oracle 8i
Team Size :8
Duration : 3 Months

The Application facilitates the club members to use smart cards for their transactions
(Debit/Credit) in the club for various services offered by the Club. The use of the system brings in the
comfort of not to carry cash/cash coupons and provides a centralized transaction repository for the
Members and the Club respectively.

Responsibilities:

• As a Team member I am responsible for development of Admin-User and

Transaction functions
• Involved in developing user interfaces using JSP/HTML/JavaScript.
• Involved in Integration of modules.

Project Title : Workflow automation system.

Hardware : Pentium PC.
Operating System : Win’95, WinNT.
Client : Cyberkorp Inc., Madras.
Software : Java, Swings, JDBC, and Oracle 7.3.
Team Size :8
Role : Analyzing, Development, Testing

Description : This is meant to automate the goings on in any company by taking care of all aspects of it
like name of company, locations, employees, designations, departments, work groups, master document,
sub document's, processes, validations/decisions, stages etc. This reduces paper work and eliminates
communication gaps while at the same time making the entire flow of work faster and efficient.
Module 1
Master data generation: In this module, the entire data and documents are generated by admin.There is
provision for creation, modification and deletion of each and every aspect. Validations implies allotting
accept, reject, postpone etc. to processes with a combinatorial direction like forward, backward or
exception. Employees are registered here. For every aspect there is a program generated ID/number.
Module 2
Configuration module: Master document is generated containing all
fields required from which sub documents are generated. First time, the sub documents are in stage one
until passed on to next client to be in second stage and so on. To each process, sub documents are
allocated. Work group implies all employees using a particular sub document. A group of validations are
marked as forward, backward or exception in the next stage action option. Exception implies the sub
document goes to a given employee outside of the work group.
Module 3
Client side module: This involves swing, iostreams and sockets/mail for communication of documents
across the Internet from client to client. There is an inbox, forms, main and background outbox. But all four
are created and visible in the client machines file folder system. The documents, which are in forms, are
filled up in the first stage and on submit they go to inbox for validations and remarks. From here they go to
 the outbox while at the same time a back up is stored in main folder. Then they go from client outbox to
work flow engine inbox at server end from where after admin validations and remarks to outbox and then to
inbox of next client. The user interface folders are like RAM and system folders are non-volatile.
Module 4
Document Mapping System: The Objective of the above System is to show the status of the various
documents handled by a particular employee who is logging into the system and also status of other
employees who are involved in that document process.

Projects:
Project: Pex (Process Express)
Client: St. George Bank, Sydney
Lynx is a multi tiered enterprise application, gone live with St. George bank Sydney, for online automation of services
like LS (Loan Servicing), BSS (Business support and services) etc. Having made an effective use of CE and PE api, the
project's technical design has given it a high degree of reusability and made it extendable. Use of OOPs, java reflection
api and smart algorithms made it quite generic. A core component made it possible to create and run multiple
applications on the same core architecture, and all those applications may have different functionality specific to them.
This core component is actually the backbone of project and has three sub components, Mimic (hierarchy of java
classes representing structure of CE classes), Guide acts as guide, information provider to service layers, while Service
does the whole transactions and manipulations. For any requirement change, only the mimic and guide has to be
modified, service component will automatically recognize the changes and will act accordingly. Some more applications
have also been created using the same core component, a few to name are RNC, OAF, SAS etc.

Position: Technical Consultant and Analyst Program

Environment : Windows 2000 Server, FileNet P8 BPM Suite, Image Services 4.0, Image Services
Resource Adapter (ISRA3.1), LDAP, Web sphere 5.0.2, Java, JSP.

Project: eQuip
Client: FileNet P8 Framework

The framework has been developed as a generic bridge between client’s existing system on one side to interact with
different functional units on other side across the bridge using their APIs and servers, like LDAP server, Oracle server,
CE-PE servers and Image Server etc.
Has two sub layers – thin interface layer (contain interfaces exposed to the client) and service layer (contain
implementation for the interfaces, not exposed to the client) and this layer interact with other servers using their API.
Once the frame work is ready, only the required interfaces (in thin layer) and their implementations in form of services
and business logic (in services layer) is required to put in the bridge layer and the entire system begins functioning and
the client can then interact and get the intended services from the servers on the other side.
The Bridging framework is aimed at :
• Providing best possible implementation of J2EE architecture, especially in case of filenet products.
• Avoiding the excess of those functionalities which are immaterial to the client.
• Extensibility of bridge as more interfaces and their implementations can be attached and vice versa easily
whenever required and the system will be ready to use with new/modified functionality.

Position: Architect and Sr. Developer

Environment: Windows 2000 Server, FileNet P8 BPM Suite, Image Services 4.0, Image Services Resource Adapter
(ISRA3.1), LDAP, Web sphere 5.0.2, Java, JSP & Oracle 9i.

Project: Maroochy Shire Council (MSC)

Client: The BPA Group (Brisbane, Australia)

COM Proxy, a module developed and attached to an already existing component called Proclaim, to cater the
requirements of Proclaim to interact with FileNet P8 suite of enterprise content management. Developed completely in
C#. Provides various levels of functionality, including use of windows shell commands along with FileNet content engine
services via FileNet COM API.

Position: Technical Consultant and Sr. Developer

Environment: FileNet P8 BPM Suite 3.0, Windows 2000 Server, Visual Studio .NET (C#), Java,
Proclaim

Project: Imaging and Workflow

Client: Superpartners Pty. Ltd. (Melbourne, Australia)
 Imaging and Workflow serves the need to automate the processing of scanned document. The scanned file along with
its corresponding xml file (which stores xml format data related to the scanned image) is processed and accordingly
stored in content engine as an object (CE object) based on their portfolio or category which decides their storage type,
class to which the document should belong, storage folder/location, media type etc. A workflow is launched via Filenet
process engine (PE) and the launching process depends on the event to which it is programmed.

Position: Business Analyst cum Sr. Developer

Environment:Windows 2000 Server, FileNet P8 BPM Suite, Image Services 4.0, Image Services
Resource Adapter (ISRA3.1), LDAP, Web sphere 5.0.2, Java, JSP & Oracle 9i.
Project: InsurePro
Client: FileNet P8 Framework For Auto Insurance

InsurePro Solution is designed as a reusable P8 based component to address the typical needs of insurance industry.
Scope has been limited to Personal Auto, Property and Causality Insurance. This application is developed keeping in
mind scalability and extensibility needed to address other lines of business within insurance industry.

It caters to following two basic functions:

• Generation of a Quote based on an inquiry for Personal Auto Insurance.
• Issuing of a policy based on the Quote.

InsurePro is integrated with FileNet P8 product suite. It is an add-on to P8’s existing functionality for catering to
Insurance vertical. It utilizes existing features of FileNet Workplace to manage logical flow of work within the system.
Customizations or upgrades that are made at server side get automatically reflected at client side when client logs on
using the browser.
InsurePro is aimed at introducing tools of Enterprise Content Management that FileNet provides to address the problem
presented. Two roles are involved in the system. Agent, who generates new quotes based on an inquiry, and
Underwriter who issues or rejects these quotes. Application provides extensibility for configuring number of users or
participants involved in a step of workflow, number of steps in a workflow and the workflow to be launched.

Position: Developer
Environment:FileNet P8 BPM Suite, Java, JSP, HTML/DHTML, JavaScript, MS SQL Server 2000, WebSphere Studio
Application Developer, Windows 2000 Server

Project: Invoice Manager

Client: Technofab Enterprise Private Limited

This was an invoice management desktop application running on windows 98 / 2000. Application was designed to
maintain and manage company’s invoices. It holds all detailed information for every invoice made and is flexible to
accommodate fix values like rates of excise and sales tax etc. Authentication and rule management is configurable at
the time of installation and can be reconfigured by the authorized user.

Position: Developer
Environment: Windows 2000 Server, Developer 6i, Oracle 8i

Responsibilities:
• Customer Interaction.
• Requirements Gathering and Analysis.
• Feasibility Study and Gap Analysis.
• Team co-ordination, Production Support.
• Process design, logic design and application development.
• Involved in unit testing and integration testing.
• Creation of High Level Design (HLD) Documents.
• Project Off shoring analysis and management.