How to Speed Up Finacle? Suggestions to M/s Infosys

HOW TO SPEEEED UP FINACLE BY INFOSYS

Some suggestions / expectations to M/S Infosys.

I humbly submitting the following points to scrutinize whether it is worthy / silly for your opinion.

1. After the Login, FINCORE should be loaded automatically to improve the performance. Disable the automatic loading of Left side Menus after the FINCORE LOADING. If we want to access the Menu provide a ICON, like password icon (key icon) on the top of the screen. Loading of menus in the First Screen may be the reason for Finacle slowness and in-accessibility.
2. Even at the time of Fincore Loading failure the User Credential management ( Password) Screen and Time Zone Changing and Logout options working fine. If the server is busy these will not work. If you close the Screen without Logout from the Fincore Loading failure screen, “User already login” error will not be raised by Finacle. Kindly check the scenario.
3. Automatic Logout time should be extended upto 1 hours or it should be user specific. Most of the problem occurs at the time of concurrent user logouts & Logins all over India. If it is not possible, don’t logout the user provide option for locking the screen after that the user may use the screen by typing password ( Not user name) to reuse the screen. This will improve the Finacle performance. Thousands of un-necessary logout requests/ responses to the Server will affect the server performance.
4. After submitting the screen (CTM / CXFER / CRDP) last entered screen should be automatically open. If we enter the CXFER - Bank Induced- this screen should be automatically loaded after each transaction until another menu selected to quickly complete the transaction and close the SOL within reasonable time. In CXFER Now we are selecting as ADD – BANK INDUCED – SUBMIT. After submitting the SUBMIT request will go to the server and transaction screen retrieved from the server. If we reduce the unnecessary traffic Finacle will be work better than before.
5. RD Verification should be extended above Rs.1000- . Finacle getting slow at the time of Verification by all the users and posting have been done concurrently after verification. This may be the reason for the Finacle slowness.
6. Now we are connecting through dop domain. Most of the times system is getting slow even open a folder from the system and to close any window other than Finacle. For testing purpose at the time of Finacle slow connectivity Infosys may test with normal login in the windows.
7. Transaction numbers should be generated SOL wise. Now the method is as IN123, IN 3455455 nation wise.If all the offices are migrated into CBS kindly imagine the Transaction (IN )Numbers. All the IN numbers should be written by the PA and authorized by the Supervisor. If the IN numbers in Lakhs Counter PA should write legibly 10 characters and the Supervisor should type the 10 digit numbers to verify.For one account Counter PA should type the 10 digit account numbers + write the 10 digit Transaction Numbers + Type the 10 digit IN numbers to verify. For each and every transaction we have to type and write 30 characters correctly apart from the transaction amount.If the Transaction Numbers generated for every SOL i.e., (IN60930401-123, IN60930401-457) transaction Nos will be generated within thousands. We can easily write the suffix nos and verify them quickly by copying and pasting the prefix numbers without mis-quote. We can easily confirm the transaction from where it was entered.
8. New account Numbers should be generated with prefix SOL ID + ACCOUNT NO. i.e (60930401-1567, 60930401-1789 , etc) like some other Banks. In the passbook printing Barcode should be generated to easily scan the Account Numbers to easily transact without typing the Account Nos.If the above method is used users gets the benefit of easy typing and writing of account numbers without confusing. If we quickly transact and submit the screen all the users will be quickly able to access the instance of the screen and speedy handling.
9. Reporting mechanisms should be improved. After creating the Report in HFINRPT system should automatically show the report without going to the HPR Menu. This may be the reason for the slowness in the evening , while all are trying to generate (HFINRPT) and view(HPR) the reports.
10. At the time of middle of the month ( 15th ) and the end of the month server getting hang due to the heavy Agents bulk lists posting.Now In the bulk list posting every transaction having a separate Transaction Nos. If only one Transaction Number is generated for each bulk lists it will be much better to improve the server speed.
11. In the RD New account opening a skeleton has been created for 60 transactions and created at the time of Account opening. If more number of users are opening RD Accounts server will go slowdown due to this problem. For the New accounts opened, such skeleton may be created at the time of anterior or posterior to DC Closure.
12. If a cheque payment has been made now we are giving the office account ID as 609304010340 ( postmaster Account ). If we issue the cheque the above accound ID is correct. If we receive and paid the cheque from H.O the account ID should be as 609001010340 ( Head office SOLID 60900101). If we give the HO Account ID this will helpful to reconcile the accounts from where the cheques has been issued and where it has been paid.
13. Apart from all of the above, a Balance sheet should be generated before or after HISCOD , showing the account head wise debit and credit and advance received and amount remitted and amount posted in office accounts and head wise summary in office accounts for that working date. This will be helpful to tally / cross tally the accounts by SOLS , HO and SBCO by accompanying the printouts with Sub Office Daily Accounts.

Humble Submission by 

S. THIYAGARAJAN

SPM, KILAIYUR S.O 609304

MAYILADUTHURAI DIVISION, T.N. Circle.

raajansankaran@gmail.com