Ali Baig

Back-end Developer

Front-end Developer

Mobile Apps Developer

Ali Baig
Ali Baig
Ali Baig
Ali Baig

Back-end Developer

Front-end Developer

Mobile Apps Developer

MicroInsurance System (MIMS)

MicroInsurance management system (MIMS) was developed to entertain the insurance business which included modules like Policy Management, Claims management, Amount component calculations (Interest, Charges and Premiums), Monthend windows service, Reports (Account statement, Financial reports, Claims reports which were further divided into 4 claim statements), Role based logins where each role had different privileges, Notification center for sending SMS notices to customers all over and Import/Export of huge amount of data.

 

Details of each module developed in this exercise is as follows:

 

1) Policy Management: In this module, the logged in user (if has enough rights) used to create/import/edit/remove the policy data, beneficiary and secondary lives data which were related to policies and all premiums (backdated + current).

 

2) Claims Management: In this module, the logged in user (if has enough rights) used to process any of the following claims: I) Partial Withdrawal: YY amount of XX% of amount valid of withdrawal after first 6 months or an year after the first withdrawal. II) Maturity Claim: Option of maturity claim was only available if policy’s first payment date was 5 years ago, all amount was available for withdrawal after 5 years with any deduction. III) Surrender Claim: Option available on demand of customer upto 5 years from his first payment date. Each year (from 0-4) there was a penalty amount which was deducted from policy’s statement depending upon the year plus the surrender charges. IV) Death Claim: Two types of death claims were available i.e Primary and Secondary, in both cases either beneficiaries or secondary lives were entitled for the benefit depending upon which death claim was processed.

 

3) Amount Component Module: This module contained all the necessary calculations of different amount components available in the system and were responsible for any type of transactions. Amount component mainly included INTEREST calculations, CHARGES calculations based on the EVENT and the SUB EVENT configured and lastly the PREMIUMS which were credited into the accounts of policies each day/week/month. All these amount component calculations were available for backdated transactions too which was the hardest thing to achieve in the system.

 

4) Windows Service (Month End): Special service was designed to entertain the need of continuous running calculation function behind the scenes which was invoked on monthend and was responsible for carrying out interest and charges calculations configured in SETUP’s module.

 

5) Crystal Reporting: Reporting is the key part of any system, same went for this one where i had to develop different kind of reports. Some of them are Account statement, Financial reports and Claims reports. Account statement included all types of transactions (CREDITS + DEBITS) against any policy between any two dates. Financial reports were given based on amount component (INTEREST, CHARGES, PREMIUM) chosen between any two dates. Lastly claims reporting which included reports based on any type of claim.

 

6) Role Based Logins: Role based logins were given to entertain the user where SUPER ADMIN used to create new roles and later assign privileges to them and assign the role to the users which were effective as soon as they were saved.

 

7) Notification Center: It was given for sending SMS alerts to the policies when the MONTHEND service used to run after exactly 1 month. A notification was sent containing the updates done for this month which included the transaction summary against the policy.