The document summarizes several projects the author worked on at Fidelity, including implementing fee disclosure requirements, computing revenue sharing distributions, tracking loan withdrawals across vendors, and modifying systems to handle an alternative bank. It also describes the author's role in all phases of the projects from requirements analysis to post-production support.

1. Following are brief descriptions of projects I worked on in Fidelity. I have given the
number of programs I coded in these projects just to give an idea of the scope and size of
my involvement.
• Fee Disclosure project: 11/2010 to 02/2012. Implement legal requirement to inform
participants of the fees being charged to them by Fidelity for their financial transactions.
Coded and modified 6 programs.
• Revenue Sharing project Phase I & Phase II: 02/2012 to 05/2013. Compute and
distribute a portion of Fidelity’s revenue to participants through plan sponsors to stay
competitive. Coded and modified 5 programs,.
• Cross-Vendor Suspension Tracking project: 05/2013 to 12/2013. Track participants
withdrawing loans from their accounts through outside vendors. Coded 8 programs.
• Canadian Remediation project: 12/2013 to 06/2014. Identify Canadian participants
and implement the legal requirement that they be denied access to certain information in
Netbenefits. Coded 10 programs.
• Bank Resiliency project: 06/2014 to 06/2015. Make our system capable of handling an
alternative bank to the Deutsche Bank with which our whole system is oriented. Modified
8 programs and performed unit testing.
• Small Market Enhancement project. 06/2015 - Present. Did extensive eanalysis to
enable conversion of present CICS/Mainframe system into ODM/Java-on-mainframe
techonology. Modified IOM to add more error validations.
In all these projects I was a member of a team involved in all the following phases of the
project:
• Determining ARL with business,
• Do extensive analysis of existing systems and data-mining for tailoring to the
requirements;
• Create process design after considering various alternatives;
• Produce System Design Specification for walk through with the users and get their
approval;
• Create Technical Specification Document for detailed coding and get it approved;
• Code programs, screens, JCLs, PROCs, move them through ENDEVOR Design DB2
tables, interface with DBAs, create INFOPAC reports.
• Unit testing of all modules by creating live production data as well as creating my
own test data.
• Interface with Quality Assurance team in their end-to-end testing and get their
approval;
• Follow Fidelity formalities of Release Management for moving the system to
Production ;
• Final installation of the project in Production;
• Provide post-production warranty service.