1 ANDHRA PRAGATHI GRAMEENA BANK HEAD OFFICE: KADAPA Cir. No.14-2012-BC-CSRD Date: 17.01.2012 CENTRAL REGISTRY – RELEASE OF NEW VERSION OF REGISTRATION SYSTEM As branches are aware, online registration of Security Transactions as prescribed in the SARFAESI Act 2002 is being carried out through CERSAI‟s portal at http://www.cersai.org.in from March 31, 2011. Further, as this registration is a new phenomenon, CERSAI after receiving suggestions from various lending institutions, has developed revised version of the Registration System which is now ready for live operations. This revision brings out two major changes namely the use of digital certificates for authentication of transactions as prescribed under the SARFAESI (Central Registry) Rules, 2011, and availability of maker checker mechanism to provide control over the process of registration. Besides this, the system has also been modified to allow multiple co-borrowers, mortgagors, facilities, lenders etc., for a single transaction as required in Form I. A brief technical note on key features of the new system is available at Annexure-I. 2. Consequent to the changes, the data structure of batch file has been suitably modified to accommodate additional information. The data structure of the revised batch file is provided in the following files in excel format which can be downloaded from the CERSAI portal. 1. Format for Creation of Security Interest.xls 2. Format for Satisfaction of Security Interest.xls 3. Format for Search Financial Asset.xls 4. State Master.xls 5. Data Dictionary.xls 3. Personnel interacting with CERSAI require a little planning to prepare themselves for working with the revised system. The first major task in the preparation is the acquisition of digital certificates for the users if they do not have the required digital certificates. The digital certificates will be required for the administrators and all those users who will finally submit the registration data/batch files to the CERSAI Registration System. Those users who are just makers and store data on the Registration System for final submission by some other authorized users will not require the digital certificates. Further, the revised system has a few new roles defined to manage functions like accounting, MIS report generation etc. The structure of the roles in the revised system along with their digital certificate requirement is explained in Annexure-I: Section 4:Table#3.
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
1
ANDHRA PRAGATHI GRAMEENA BANK HEAD OFFICE: KADAPA
Cir. No.14-2012-BC-CSRD Date: 17.01.2012
CENTRAL REGISTRY – RELEASE OF NEW VERSION OF REGISTRATION SYSTEM
As branches are aware, online registration of Security Transactions as prescribed in the SARFAESI Act 2002 is being carried out through CERSAI‟s portal at http://www.cersai.org.in from March 31, 2011. Further, as this registration is a new phenomenon, CERSAI after receiving suggestions from various lending institutions, has developed revised version of the Registration System which is now ready for live
operations. This revision brings out two major changes namely the use of digital certificates for authentication of transactions as prescribed under the SARFAESI (Central Registry) Rules, 2011, and availability of maker checker mechanism to provide control over the process of registration. Besides this, the system has also been modified to allow multiple co-borrowers, mortgagors, facilities, lenders etc., for a single transaction as required in Form I. A brief technical note on key features of the new system is available at Annexure-I.
2. Consequent to the changes, the data structure of batch file has been suitably modified to accommodate additional information. The data structure of the revised batch file is provided in the following files in excel format which can be downloaded from the CERSAI portal.
1. Format for Creation of Security Interest.xls 2. Format for Satisfaction of Security Interest.xls 3. Format for Search Financial Asset.xls 4. State Master.xls 5. Data Dictionary.xls
3. Personnel interacting with CERSAI require a little planning to prepare themselves for working with the revised system. The first major task in the preparation is the acquisition of digital certificates for the users if they do not have the required digital certificates. The digital certificates will be required for the administrators and all
those users who will finally submit the registration data/batch files to the CERSAI Registration System. Those users who are just makers and store data on the Registration System for final submission by some other authorized users will not require the digital certificates. Further, the revised system has a few new roles defined to manage functions like accounting, MIS report generation etc. The structure of the roles in the revised system along with their digital certificate requirement is explained in Annexure-I: Section 4:Table#3.
2
4. The digital certificates are issued by Certifying Authorities (CA) licensed by the Government of India. A list of CAs in India along with a write up on Digital Certificates is also enclosed at Annexure-II.
5. A requirement of the User Management in the revised system is to have an additional Primary User Administrator other than the present Primary User Administrator. All the institutions are, therefore, also advised by the CERSAI to submit FORM-B (available at the website) for creation of the additional Primary User Administrator. Our Bank will initiate necessary steps in this regard shortly. 6. In addition to the acquisition of digital certificates for users, all the institutions will also have to prepare for the changes that will take place on the day of migration to the new system. The training material will also be made available shortly by the CERSAI on the website for imparting training to staff responsible for interaction with the Central Registry.
7.The CBS software services provider has created BGL and CGL for “CENTRAL REGISTRY FEES” account under income head of account as below.
Description: CENTRAL REGISTRY FEES BGL Code: 91912 CGL Code : 7423505034
The above code has been effective from 10.12.2011. Regional Offices are advised to credit the fee received so far from branches to the above said account. From now, branches are advised to credit the fee received to the above said account immediately and send confirmation to the RO along with the details of loan for registration. 8. Government of India vide order dated December 21,2011, has now advised that the institutions notified under SARFAESI Act, 2002 and the secured creditors should file with the Central Registry before March 31, 2012, particulars of transaction of security interest over property created on or before March 31, 2011 and still subsisting. Government has also decided that no fee for registration of subsisting transaction will be charged. All branches/Regional Offices are advised to initiate necessary steps to capture the past data and register such transactions on the Central Registry System at the earliest and ensure completion of the exercise before March 31, 2012.
3
9. To facilitate Banks, CERSAI has shifted its HELP DESK from Mumbai to New Delhi and the Contact Address and Telephone numbers are as under: Central Registry of Securitization Asset Reconstruction And Security Interest of India (CERSAI), 5th Floor, MTNL Telephone Exchange Building, 8, Bhikaji Cama Place, New Delhi-110066. Telephone Nos: 011-26176847, 26176855, 26176856 eMail ID : [email protected] 10. The CERSAI has sent a technical note on key features of the CERSAI Help Desk web tool (Help Desk User Management Policy Document) and the same is enclosed as Annexure-III. The Regional Offices may be guided by the said policy document. 10. Further, there are some areas of concern in the registration with CERSAI and the possible remedial measures are furnished in the Annexure-IV. Branches/offices are advised to note the above and act accordingly. Clarifications required, if any, on this Circular may be sought from Chairman‟s Secretariat & Recoveries department at Head office, through respective Regional Office, as per extant guidelines. (S.P.KULKARNI)
GENERAL MANAGER
4
CENTRAL REGISTRY OF SECURITISATION ASSET RECONSTRUCTION AND
SECURITY INTEREST OF INDIA (CERSAI)
ANNEXURE-1
TATA CONSULTANCY SERVICES
5
ANNEXURE-I
Table of Contents
1. Brief Background 2. New features of the CERSAI Phase II system 3. Comparison of Features – Existing and CERSAI Phase II web system 4. Re-grouping of Existing Users & Digital Certificate Requirement 5. Various steps to be taken by all registered institutions 6. Maker checker Enablement for all Institutions 7. Helpdesk/Ticket Lodgement Web Tool 8. User Guide and Training for the Users 9. New Batch Upload Formats 10. Summary on tasks for transition from CERSAI Phase – I to CERSAI Phase – II
web system
6
ANNEXURE-I
1. Brief Background
Central Registry Web System (www.cersai.org.in) is operating from March 31st 2011. Based on the various feedback points from various participating banks/HFCs, the new CERSAI Phase II web system is now customized. This document enlists the various aspects of the newly customized changes in the CERSAI web system and the activities which are to be executed at banks/HFCs/Other Institutions end as a pre-requisite for smooth transition from CERSAI Phase-I to CERSAI phase-II web system. This document would address the following areas.
New features in the CERSAI Phase II web system
Comparison of features of the existing (Phase-I) and revised (Phase-II) system.
Identification/re-grouping of existing users registered in Phase-I. (Re-grouping of transition & usage in CERSAI Phase-II web system by banks/HCFs)
New user role(s) introduced in the revised CERSAI Phase-II web system.
Various steps need to be taken by Banks/HFCs/Other Institutions in view of transition
Introduction of Maker/Checker facility
Revised batch file formats
Introduction of Digital Certificate based Authentication.
User Guide & Training for users
2. New features of the CERSAI Phase II system
This below are some of the major customizations which will be getting introduced in the CERSAI Phase II web system:
Changes in the Add security interest screen to accept scenarios like multiple TPM, multiple documents, multiple facility, multiple borrowers
Introduction of maker/checker feature
Introduction of Digital Certificate based authentication of transactions
Introduction of new user roles for usage in maker/checker facility
Introduction of new roles like “Accountant” to generate various
fees/charges/chalan reports.
Intermediately user role & functionary introduced.
7
ANNEXURE-I 3. Comparison of Features – Existing and CERSAI Phase II web system
Below table (Table#1) depicts the changes in the revised CERSAI Phase II web system. TABLE#1
Sl. No.
Function/Module Name
Existing Revised Description of Enhancement/ Upgrade
1. Online Registration of Security interest record
√ √ Tab based modular screens for the Entire form I for ease in usage.
Provision for adding multiple borrower, multiple TPM, multiple loan details.
2. Online search of Registered Security Interest records
√ √ Different search criteria template for searching PLOT and/or DWELLING units.
Tile wise display of Percentage based match results.
3. User Administration √ √ Maker/checker feature for all member banks/HFC.
Introduction of new user Roles
e.g. Account Role
4. User Registration Report
√ √ Same as before
5. Report for Daily Security Interest registered
√ √ Same as before
6. Batch upload mode for bulk registration of security interest records
√ √ New batch formats for capturing all the relevant & multiple data.
Provision for adding multiple borrower, multiple TPM, multiple loan details.
7. Satisfaction of Security interest
√ √ Display of full details of the security interest record, before submission of satisfaction request.
8. Correction of security interest
√ √ Tab based modular screens for the entire form I for ease in usage
Display of full details of the security interest record, before
8
submission of data correction request.
9. Modification of
Security Interest √ √ Display of full details of the
security interest record, before submission of modification request
Provision to add new loan/extension of facility details.
10. Digital Certificate based authorization & authentication
--- √ User wise registration of Digital Certificate
User authentication based on digital Certificate at the time of login & Data authorization.
11. Online statement of Account & Online Revenue MANAGEMENT System
-- √
12. Adhoc MIS reporting tool (for CERSAI International users only)
--- √
13. Batch Upload mode for Bulk satisfaction of Security Interest records.
--- √
14. Batch Upload mode for Bulk search of
Security interest records
--- √
15. Intermediatery (agency) User management & intermediatery (agency) based security interest Registration
--- √
16. Request acceptance for satisfaction of security interest by intermediatery (agency) on behalf of General Public/Citizen.
--- √
9
17.
Web based online Helpdesk tool for lodgment of tickets by Bank/HFC User Administrators
--- √
18. Maker/checker --- √
19. Asset reconstruction & securitization
--- ---
20. Search by General Public (Citizens) after Online payment via Payment Gateway
--- ---
10
ANNEXURE-I 4. Re-grouping of Existing Users & Digital Certificate Requirement
Below two table(s) i.e. table#2 & table#3 illustrate the existing user role types in Phase I and the new user role types which will be introduced in the CERSAI Phase II web system upgrade. The table#3 also depicts whether the “Digital Certificates” are required or not required for users of a particular role(s). TABLE#2
Existing User Role types in CERSAI web system (Phase I)
Role Code
Role name
R02 Primary/Secondary User Administrator
R03 Data Collection User
R04 Data Search User
R05 MIS/Report User
R06 Multifunction user TABLE#3
New User Role types in revised CERSAI Phase II web system
Role code
Role Name Digital Certificate
applicable for performing
transaction on the web system
Key functions performed by the role
R02 Primary User Administrator
Required
Create & Maintain sub-users of the institution
Create secondary user Administrators.
Add security interest records
Amened/Modification of Security Interest records
Search for asset records in registry
Satisfaction of Security Interest.
Grant Satisfaction of Security
Interest to a request made by General public.
Account statements (fees deductions) & reports download.
Batch upload & batch reports
11
M03 Data
Collection – Maker
Not Required
Data entry of Security Interest details.
Amend/modification of security interest records.
Satisfaction of Security Interest.
Batch uploads.
R04 Data search
user Not required
Search of Asset records in registry
R05 MIS/ Report
User Required
Online reports download.
M06 Multifunction user – Maker
Not required
Add security interest records
Amend/ modification of security interest records
Search of asset records in registry
Satisfaction of security interest
R07 Secondary
User Administrator
Required
Create & Maintain sub-users of the institution
Add security interest records
Amend/ modification of security
interest records
Search of asset records in registry
Satisfaction of security interest
Reports download.
Batch upload & batch reports
R08 Accountant Required Account statements & reports
download.
Account enquiry
M09 Intermediary Type User -
Maker Not Required
Add security interest records on behalf of the Bank/HFC.
Amend/ modification of security interest records on behalf of the Bank/HFC.
Search of asset records in registry on behalf of the Bank/HFC.
Raise request for satisfaction on behalf of General Public.
C03
Data Collection –
Checker Required
Data entry of security interest details
Amend/ modification of security interest records
Satisfaction of security interest
Batch uploads
Authorizations of Transactions made by maker
Online and batch reports download
12
C06 Multifunction
user – Checker
Required
Add security interest records
Amend/ modification of security interest records
Search of asset records in registry
Satisfaction of security interest
Authorizations of Transactions made by user
Online and batch reports download
C09 Intermediary Type User –
Checker Required
Add security interest records on behalf of the Bank/HFC.
Amend/ modification of security interest records on behalf of the Bank/HFC.
Search of asset records in registry on behalf of the Bank/HFC.
Raise request for satisfaction on behalf of General Public & check its status in registry on behalf of the Bank/HFC.
Authorizations of Transactions made by intermediary maker in registry on behalf of the bank/HFC.
5. Various Steps to be taken by all registered institutions
In order to achieve a smooth user ID transition from Phase I system to Phase II system, all registered institutions & their corresponding User Administrators are required to note and perform the below tasks. The tasks are very important and would avoid implementation issues after the system rollover to Phase II.
1. Generate an internal excel sheet based list of all the registered users in CERSAI web system. This can be done by the primary user administrator of the institution using the „Reports‟ side-link option.
2. Internally re-classify the users as either maker or checker or other new roles. This new classification is to be recorded in the internally maintained excel sheet made as per above point-1. Table#3 could be used for this user type re-classification. The task in point-1 & 2 should be immediately commenced upon receiving this circular by the Primary user Administrator of the respective institution.
3. All institutions are required to send one more duly filled Form-B for creation of 2nd Primary user administrator in view of maker/checker feature in Phase-II
web system. From then on, both these primary user administrators in Phase II web system will have authorization capability for data entered by each other. The duly filled FORM-B for the 2nd Primary user administrator should be couriered to CERSAI‟s address within 7 working days of receipt of this note.
13
4. All institutions are required to arrange the Digital Certificates well in advance for users reclassified into particular roles for which Digital Certificate is mandatorily required in Phase II CERSAI web system for performing authorizations. Please refer Table # 3 to know the various roles of user for which Digital certificate is required. The digital certificates should be arranged latest by 30th November 2011.
5. The Digital certificate specification should be “Digital Signature Certificate Class III with Token. (CERSAI strongly recommends Digital Certificate with Token).
6. On the eve of turn over to Phase II web system, Maker/checker feature will be enabled & will become applicable to all the institutions and their corresponding users.
7. On the eve of turn over to the new Phase II web system, all the users will be re-mapped & migrated centrally at CERSAI Datacenter as per below role migration-mapping table#4. TABLE # 4
Mapping of Role types at the time of Migration
Old Role code
Old Role Name New Role Code
New Role name
RO2
Primary User Administrator
RO2 Primary User Administrator
Secondary User Administrator
RO7 Secondary User Administrator
RO3 Data Collection User MO3 Data Collection – Maker
RO4 Data Search User RO4 Data Search User
RO5 MIS / Report User RO5 MIS / Report User
RO6 Multifunction User MO6 Multifunction User - Maker
8. On the 1st & 2nd day after rollover to new web system the Primary User
Administrators or the Secondary User Administrators will have to modify the user roles as pre-identified in excel sheet in point-2 above. This can be done via the „Amend User‟ side-link.
9. After the new role alignment is authorised by the two primary user administrators or secondary user administrators using maker/checker facility, the users will be able to login to CERSAI system along with their own digital certificates.
10. On first login (post rollover to Phase II web system) the individual users for whom Digital certificate is mandatory as per their newly assigned roles, CERSAI web system will prompt for uploading & registration of their respective digital certificate. Utmost care should be taken that the users assign & register their own digital certificates correctly at this stage.
14
11. After the registration of Digital certificate the users can operate and perform the various transactions (including authorization of transactions made by maker).
12. A daily exception report will be available to the Primary User Administrators/Secondary User Administrators for checking the correctness and mapping of the Digital Certificate registration vis a vis the individual user member names. This is to ensure that every user has registered their own respective digital certificate, any discrepancy would be reported in the above said report. This report would be available with Primary User Administrators for monitoring purposes.
6. Maker Checker Enablement for all Institutions
In the new CERSAI Phase II rollover, maker / checker facility would be introduced & enabled. Hence, it would be required to have at-least two Primary User Administrators for each institution to further perform their member user administration activities. All Institutions are required to fill and submit additional Form B. (FORM B is also available as a download under the „Downloads‟ tab in http:// cersai.org.in). Institutions can also provide the details of an existing Secondary User Administrator as part of FORM B and submit to CERSAI for elevation to Primary User Administrator. The duly filled FORM-B should be couriered to CERSAI‟s address as provided on the website (www.cersai.org.in) within 7 working days of receipt of this note. 7. Helpdesk / Ticket Lodgement Web Tool
Along with the existing mode(s) for raising central registry related queries i.e. 1) Helpdesk email ID and 2) Helpdesk telephone lines, a Web based Helpdesk tool would also be available to lodge tickets related to queries arising on the aspects of central registry web system. Access & login to this web based helpdesk ticket system will provide to the Primary / Secondary User Administrators of all the registered Banks/ HFCs. The user id and password to login into Helpdesk ticket system will be communicated separately via system email. This system generated email will be sent to the currently registered email ids of corresponding Primary / Secondary user administrators. 8. User Guide and Training for the Users
In view of CERSAI phase-II launch with several new features, User Guide document would be circulated separately by CERSAI by 25th Nov 2011.
15
Two rounds of training for Bank/HFC users would be arranged to familiarize the users with the new Phase II system. These trainings would happen in the first/second week of December 2011 and will be communicated later by CERSAI. 9. New Batch Upload Formats
In CERSAI phase-II upgrade of central registry web system, the feature to capture the multiple borrowers, multiple loan details and multiple third party mortgagees‟ details against the same security interest record is now customized; the batch format for bulk upload of registration of Security Interest is changed accordingly. This new batch format will be informed for reference & any further internal customization on the side of Banks/HFCs/Other Institutions. It is important that the institutions complete any internal customization on their internally customised batch upload tool by 10th December 2011. As part of the Phase II upgrade two new batch upload features will also be getting introduced, a) Batch for – Bulk Security Interest Search and b) Batch for – Bulk Security Interest Satisfaction. These revised batch formats will be circulated separately by us on 15th Nov 2011 via email to all the Primary User Administrators / Secondary User Administrators. The revised batch formats will also be put up on the existing web site (www.cersai.org.in) under Download tab.
16
ANNEXURE-I 10.Summary on tasks for transition from CERSAI Phase – I to CERSAI Phase – II web system
Prepare the excel sheet list of all users with their respective role codes, user_ID etc.
Send one more Form B for creation of 2nd Primary User Administrator for your institution.
Classify the existing users as Makers or Checkers with the proposed new role codes as per table # 3.
Arrange Digital Certificates for all the users where the Digital Certificate is required as per table # 3.
The Digital certificate specification is “Digital Signature Certificate Class III with Token. (CERSAI strongly recommends Digital Certificate with Token).
On the day of migration to the Phase II web system, all the users will be re-mapped & migrated centrally at CERSAI Datacenter as per table # 4.
Primary / Secondary User Administrators have to modify the user roles as per their internal classification as mentioned above in the CERSAI system on 1st
and 2nd day after migration to & launch of Phase II web system.
After migration to Phase-II system, users which require Digital Certificate to perform the transactions will be prompted by system to register their Digital certificate at the time of first login post rollover to Phase II web system.
17
ANNEXURE – II
List of Certificate Authorities (CAs) in India
Sl No. Name Address
1. Sify Communication Ltd. Sify Communications Ltd, III Floor, Tidel Park. 4 Canal Bank Road Taramani, Chennai – 600 113.
2. National Informatics Centre
A-Block CGO Complex, Lodhi Road, New Delhi – 110 003.
3. IDRBT IDRBT, Castle Hills, Road No.1, Masab Tank, Hyderabad, Andhra Pradesh – 500 057 (India)
4. Tata Consultancy Services Ltd.
Tata Consultancy Services Ltd., 11th Floor. Air India Building, Nariman Point, Mumbai – 400 021.
5. MTNL O/o DGM (IT-CA), 5515, 5th Floor, Core – V Mahanagar Doorsanchar Sadan, CGO Complex, MTNL, Delhi – 110003.
6. Code Solutions n)Code solutions (A Division of Gujarat Narmada Valley Fertilisers Company Limited), 301, GNFC Tower, Bodak Dev, Ahmedabad – 380 054, Gujarat, INDIA
7. e-Mudhra CA 3i infotech Consumer Servises Ltd., 3rd Floore, Sai Arcade, Outer Ring Road, Devarabeesamahalli, Bangalore – 560 036. Karnataka, India
Digital Certificate:
Digital Certificates are the electronic counterparts to driver licenses passports and membership cards. The digital certificate can be presented electronically to improve ones' identity or the right to access information or services online.
Digital Certificates bind an identity to a pair of electronic keys that can be used to encrypt and sign digital information. A Digital certificate makes it possible to verify someone's claim that they have the right to use a given key, helping to prevent people from using phony keys to impersonate other users. Used in conjunction with encryption, Digital Certificates provide a more complete security solution, assuring the identity of all parties involved in a transaction.
A digital Certificate is issued y a Certification Authority (CA) and signed with the CA's private key.
18
Digital Signatures associated with a unique pair of credentials - the public key and the private key. Only the owner of a Digital Certificate has access to the private key and can use it to digitally sign and encrypt any digital information such as emails, forms, files etc.
Digital Signature:
A Digital Signature functions for electronic documents like a hand written signature does for printed documents. The Signature is an unforgeable piece of data that asserts that a named person wrote or otherwise agreed to the document to which the signature is attached.
A Digital Signature actually provides a greater degree of security than a handwritten signature. The recipient of a digitally signed message can verify both the message originated from the person whose signature is attached and that the message has not been altered either intentionally or accidentally since it was signed. Furthermore, Digital Signatures cannot be repudiated; the signer of a document cannot later disown by claiming the signature is forged.
Digital Signatures enable “authentication” of digital messages, assuring the recipient of a Digital Message of both the identity of the sender and the integrity of the message.
Transactions through usage of Digital Signature can be traced & identify of the user can be proven. Class III digital signatures are legally recognized digital signatures as per the IT Act, 2000.
Public Key & Private Key
A public key is a value provided by some designated authority as an encryption key that, combined with a private key derived from the public key, can be used to effectively encrypt messages and digital signatures. The use of combined public and private keys is known as asymmetric cryptography. A System for using public keys is called a public key infrastructure (PKI).
Certificate Authority (CA)
A Certificate Authority or certification authority (CA) is an entity which issues digital certificate for use by other parties. It is an example of a trusted third party. CAs are characteristic of many public key infrastructure (PKI) schemes.
A CA issues digital certificates which contain a public key and the identity of the owner. The matching private key is not similarly made available publicly, by kept secret by the end user who generates the key pair. The certificate is also an attestation by the CA that the public key contained in the certificate belongs to the person, organization, server or other entity noted in the certificate. A CA‟s obligation in such schemes is to verify an applicant‟s
credentials, so that users and relying parties can trust the information in the CA‟s certificates. CAs uses a variety of standards and tests to do so.
Detailed guideline on the process of obtaining digital certificate is available on http://cca.gov.in.
19
ANNEXURE-III
CENTRAL REGISTRY OF SECURITISATION ASSET RECONSTRUCTION AND
SECURITY INTEREST OF INDIA (CERSAI)
CENTRAL REGISTRY SYSTEM
Help desk user Management Policy Document
Version 1.0
TATA CONSULTANCY SERVICES
20
Annexure – III 1. Introduction
Help desk tool has been implemented wherein user administrators of registered entities can raise issues faced by them/member user while accessing Central Registry Web site. The purpose of this document is to describe the methodology adopted for creation of new users, Deactivation of existing users & Password reset for Help Desk Tool users.
2. Process detail description
This section explains detailed methods adopted for below mentioned processes:
Creation of new users
Deactivation of existing users
Password reset policy
2.1 Creation of New Users
Help desk tool can only be accessed by user administrators (Primary/Secondary) of registered entity. So when ever new user administrator is created at central Registry web system. It will also be created in Help Desk Tool in offline fashion as a part of batch job.
Whenever new user administrator is created in CERSAI, same user will be created internally within help desk Tool through batch processing within next 4 hours. This activity will be done as a part of scheduled job on every day. This is an automated process & does not require any manual intervention.
2.2 Deactivation of existing users
Whenever existing administrator gets deactivated in CERSAI, same user will also get deactivated internally within Help Desk Tool through batch processing within next 4 hours. This activity will be done as a part of scheduled job on every day. This is an automated process & does not require any manual intervention.
2.3 Reset Password/ Change own Password
Existing user administrator may change their own password in CERSAI system. In such scenario, whenever existing user administrator changes his password in CERSAI, same password will be updated internally within Help Desk Tool through batch processing within next 4 hours. This activity will be done as a part of scheduled job on every day. This is an automated process & does not require any manual intervention.
2.4 Synchronization of Passwords with CERSAI’s web system
Since, the users of new Help Desk ticket lodgement tool will be using the same user-ID and Password provided in CERSAI‟s web system. It is necessary to synchronize the passwords of both the system 2 days prior to launch of Help Desk ticket lodgement tool. This can be done by making the “First time Login” flag as “yes” so that all primary/Secondary User administrators would be prompted for “Change Password” in CERSAI web system and on this event system will synchronize the password between CERSAI web system and help desk ticket lodgement tool.
21
ANNEXURE-IV
Sl. No.
Areas of Concern Suggested remedial measure
1 Internet Connection not available PC not compatible with Internet Explorer version 7 or 8.
ROs may take up with IT Department, HO for supply of a PC compatible with IE 7 or 8 which is mandatory for online registrations with CERSAI
2 Many Branches have either not collected applicable Fee or have kept the same in suspense account.
Branches are directed to transfer any Fee amount collected from the customers to the Regional Office for crediting the same to the Central Registry fees. Many Branches have written SB A/c numbers instead of LOAN A/c number which should be avoided.
3 Branches are collecting Fee in advance and the actual Registration takes place on a later date OR Branches do the registration and collect the fee on a later date.
Branches shall make sure that the Fee is collected immediately on the date of Registration and credit the same to CENTRAL Registry Fee. The confirmation and the details shall be forwarded to the respective RO for registration with CERSAI..
4 ROs have done SATISFACTION OF CHARGE immediately after the Charge is registered.
SATISFACTION OF CHARGE is applicable only when the Loan account is closed and the Asset is RELEASED. Hence if Satisfaction of Charge is made immediately after the Charge is created, it nullifies the Charge created. Further, CERSAI charges Rs.250/-per Satisfaction irrespective of the reason for doing so. Hence ROs shall use the system judiciously and not to EXPLORE the system unnecessarily. It may be even SEARCH option is charged.
5
Printing of the Registration details not available in the system
Presently the System does not provide for printing of the Registration details. It is understood that the options will be made available in coming days. However ROs shall only note the ASSET ID in the EM register and documents and keep the FORM I which they have filled in before the Registration for future reference.
6 PASSWORDS
Initially, to avoid delay in Registrations, passwords were either sent to respective ROs or personal email of one of the applicant. ROs have to be careful about the Passwords and any unauthorized use of the System should be avoided. ROs should not use outside agencies and public Internet parlors for Registration.
7 Registrations done by RO
Branches have sent the data to the respective RO for Registration but have no information regarding the Registration or otherwise. Branches may be advised to follow up and get the Asset ID to be recorded in their EM register/documents. RO. shall ensure that the charges for these Registrations are recovered and credited to CERSAI fees paid account by the Branches without fail.
Related Documents
