eFerfar Release Notes DATE 10.6.2020

                                  eFerfar Release Notes

                                                                                                                               10-June-2020

Module Name : eFerfar

1. Multiple Village Document Registration 

The Land Records and Sub Registrar Offices are integrated in Maharashtra where in LR data is used for property document registration. In turn, post registration, the registration data is sent to LR for initiation of mutation process for change of Record of Rights. As part of this, one of the major new development initiated is about the registration of multiple properties of a seller across different villages / talukas / districts. For example, a person has properties in districts A, B, C, then the person can register for selling all his properties at one sub registrar office. On completion of the registration, the data will be mutated by each of the concerned village officer in the different districts allowing data for mutation as per their work jurisdiction. Currently, this is not supported in Linkage for handling of multiple village document registration, in terms of such documents to be taken ahead in mutation flow and complete the changes on Record of Rights. There fore, it was decided to develop necessary mechansim to allow for  Multiple Village Document Registration.vis-a-vis Mutation Completion

Accordingly, at LR side, we have developed necessary software to allow for management of  Multiple Village Document Registration. eFerfar will now handle documents registered at SRO for

After such a registration done at SRO, the necessary registration details will be pushed at eFerfar side, which eFerfar will be capable to process  so as to

Circle Officer after due process (manual case file verification, online checking of VF VI, Notice, Preview etc) - Certify or Reject the mutation.

This will enable mutation process for  Multiple Village Document Registration

2.  Mutation Number Generation Service

Earlier, on receipt of SRO registration data, mutation number was returned to SRO for showing in SMS. With multiple village document registration, it is now necessary to return multiple mutation numbers of diferent villages (which may be of diferent tahsils and or districts). So necessary development in service architecture has been done to acomplish the same.

3. PDE Service change verification

iSarita (Registration Software) has now allowed for Public Data Entry – by citizens for document registration entry called as  PDE using property details from LR data. In this regard, after making a PDE entry by citizen, when it is being IMPORTED in iSarita, there is a requirement to check if the data using which the PDE entry was made is in fact intact at the time of registration of document or not. So iSarita will get the confirmation from LR side during the PDE import on change status and decide if to Import the PDE entry or not. The service will return a True or False flag for the PDE data based on request from iSarita using the details of PDE entry such as census code, survey number and date-time of PDE entry

4. Returning of Khata Number List 

List of khata numbers available on selected 7/12 is sent to SRO so that SRO can select (and not type manually), the khata number which is the Seller person's khata in current transaction. This was a suggestion  from your side and has been developed.

5. Tahsildar to mark a survey number for Correction (as per request from citizens / talathi)

New facility is provided to Tahsildar, to mark a survey number for correction as per received request from Talathi or citizen having observed some correction required before the record of rights can be mutated. Such marked survey number is then blocked for any mutation till the necessary correction is completed.

6. Record of Rights on Mobile

Delivery of RoR on mobile is done by LR PDE team. For this the necessary processed data in form of a DLL Service has been developed where in free format the RoR is displayed on mobile. This service will be launched soon.

7. Development of a special mutation under Section-155 of Maharashtra Land Revenue Code (MLRC) – Confirmation of Higher Mutation Numbers than the Online Mutation Numbers present in the village

This mutation is developed for Confirmation of mutation numbers which are higher than the mutation numbers taken in online mutation work so that when the real online mutation reaches the higher mutation number already available in manual record, then the 2 can be identified. The approval of Tahsildar is required for confirmation of the same. This development has been based on the Approved CRF-56 – Higher Mutation Numbers

8.          NA Order Cancellation Facility :

Allowed to handle NA Aadesh Cancel Mutation to re-allot areas in to cultivable and potkharab areas as NA Cancellation Order is received from Tahsildar. This flow or requirement was not envisaged earlier, and there fore has to be incorporated to re-instate the position of area of 7/12 with NA area now again available as cultivable plus potkharab areas.

 9.        Cancellation of entry of Close Existing 7/12 and Create New Sub-Divisions

Developed a new option "आदेशाने जुना ७/१२ बंद व नवीन पोट हिस्सा तयार करण्यासाठी केलेले काम रद्द करणे" to cancel work done of mutattion type "आदेशाने जुना ७/१२ बंद व नवीन पोट हिस्सा तयार करणे" prior to start of ferfar entry of creating new 712. User have reported such  cases from Nagpur , Chandrapur, Jaagaon and Ratanagiri.

10.          KDM Entry Cancellation facility

Developement of canceling work of Sec-155 Khata Durusti Ferfar type, in two cases.

11.          Restriction on Ahwal-I Durusti

Restriced Ahwal-I durusti ("कलम १५५ च्या आदेशाने अहवाल १ ची दुरुस्ती करणे" mutation which is with Tahsilar Approval)  limited to change in area of owner section only to be in sync with area of VF VII. VF VII area can not be changed. The same was discussed with State Coordinator. For area change on both sides, new mutation under Sec-155 called as “"आदेशाने ७/१२ वरील क्षेत्राची दुरुस्ती करणे" with Tahsildar Approval exists.

12.          DSD Signing for current mutation

To speed up DSD signing, now it is allowed to sign a survey number, whose earlier mutation was not signed.  Thus if for any reason Digital Signing of  previous mutation on the survey  is pending then also now it is  allowed to DSD for current mutation as any way, the data that would be signed in both cases is going to be the same. So it would be prudent to sign with the latest mutation number which would also include changes of the previous mutation number.

13.          Skipping Ahwal Checks for Closed 7/12 Signing

All ahwal checks for Closed 7/12s for First Time Signing are bypassed as these 7/12s are closed and so are un available to talathis for doing any correction. Non Signing of these 7/12s would lead to showing of incomplete work in the DSD Dashboard and so as per the feedback and suggestions received from the SC Team, it was decided to allow signing such closed 7/12s on as is condition.

15-A           Data Signing post Mutation in eFerfar

Post Mutation Certification, necessary changes have been made to push data now to ESDS in place of earlier NDC.

15-B           Ferfar Register Durusti

If Tahsildar disapproves the Sec-155 Ferfar Register Durusti, then it is now again available for another mutation request from talathi end which eas not available earlier

Module Name : User Creation

16.     Talathi Sajja and Circle -Mandal Creation Facility

As part of the process of payment of challans through Banks, it was found necessary that all the talathi Sajja and circle officer-mandal creation has to be completed so as tonot leavebehind any villagewhich may escape the ambit of coverage of challan payments. Accordingly State Coordinator and NIC Team devised mechanism to allot unique Virtual Account Number (VAN)  for each village by mapping the LR village census codes with Local Government (LG) directory’s village codes (6 digits) and thus the VAN was formed with the format “REVZXXXYYY999999” where REVZ is fixed suffix, followed by first 3 characters of district name, next 3 characters of taluka name and followed by 6 digit LG village code. Further, a village may be assigned to a particular person who may temporarily hold the charge of the village in absence of regular talathi, sevarth id is also considered internally to identify the person who currently distribute the LR documents through DDM and make the current charge holder to pay the documents fees in bank.

17.          Facility for Re-Certification of Sajja and Mandal Creation

As per discssuions and change request suggested by State Coordinator, eFerfar, in Mahrashtra there are 2500 additional Sajjas created and they are to be handled by existing talathis. So to allow for allocation of villages to new sajjas, a facility was required, to make changes in sajja – village allocations so as to accommodate the new sajjas. Accordingly, a new facility for revertion (allowing for re-declaration) of a tahsil’s Sajja and Mandal Creation has been provided in the User Creation module for Naib Tahsildar-eFerfar role.

Module Name : DDM Module

18.          Development for New Design of RoR – 7/12

A need was felt by the department to have a relook at the very important document of land records – the Record of Rights i.e. 7/12 to incorporate the GoM Logo, eMahabhumi Logo, to be made more appealing with re-formatting of the presentation, removing of unused columns, making appearance more thorough and also developing a English version for the benefit of the citizens at large specially the non Marathi speaking populace.  After 2-3 round of discussions chaired by Hon SC Sir and participated by State Coordinator and NIC team, the final formats were decided and changes enlisted. Accordingly, the development team has worked on the entire changes which needed to be done for HTML RoR that is used in DDM and PDF format which is used in Digitally Signed Database Record (DSDR) based RoR delivered from eMahabumi portal online with Payment Gateway. The CRF for the same : CRF-64-eFerfar - 7-12 Changes as per GR Plus Format Changes has already been submitted and is pending for approval.  

19. Reconciliation of Virtual Account Number (VAN) payments made by Village Officers for the amount collected for distribution of land records documents

A Centralized Processing System (CPS) has been developed for Reconciliation of amount received by different village officers (12500 officers) for collection of cash of RoR documents distributed to citizens. The system generates a challan demand for each officer at the end of the month and payments are made in Bank of Baroda which is designated as Nodal Bank by the LR department to recive the amounts with each village officer assigned a Virtual Account Number which actually points to the  department’s physicall bank account number. Reconciliation is made after details of payments are received from bank at the end of a month and the CPS process the payments gainst the corresponding challan demands and reconciles the demand vis-à-vis payment.

This module has facility to declare the work completion for Tahsil by the Naib Tahsildar eFerfar (NT-eF)  – earlier designated as DBA where in all the sajjas and mandals will have to be created first and only then the NT-eF can declare the work as completed. The software will check internally that no village is unassigned for either the sajja assignement or mandal assignment. SO far about 11245 Sajjas have been created in the State.

Facilities for viewing the Sajjas and Mandals along with the villages assigned has been provided. The Work Completion Certification is generated by the System to be endorsed by the NT-eF.

20.          Changes in DDM module with respect to Challan and Reconciliation

Consolidated Challan Generation :

After going through the detailed requirement and as directed by Hon SC Sir in the VC, the challan is now generated for a month considering the earlier backlog of payments and including the pending payments if any – a single challan is now generated by the syste,. Example, while generating the challan for a sajja in May for the month of April 2020, if the pament due in March was unpaid, then the challan for April will be generated considering the amounts of March and April 2020 – both the months (Single Challan).

Automated Reconciliation: The Reconciliation of all challan’s of the entire State as suggested by Hon SC Sir has been complied with and now a system is developed which allows for Reconciliation of all payments received from the Bank vis-à-vis Challans generated. This will enable the department what the demand was, what the collection is and what is the balance payments yet to be made. A detailed report of challan amounts and their payments is available in the system

Module Name : DSD Module

21.          Shifting of Portal for Digitally Signed Data basd 7/12 (DSD) 

The  AapleAbhilekh Portal (https://aapleabhilekh.mahabhumi.gov.in/) has been successfully migrated from  NDC to ESDS by way of migrating all DSD data and application portal

As per decisions made in the Project Review metting, the long pending decision of shifting DSD 7/12 database and application from NDC to ESDS has been completed. It may be noted that the existing Database and Application Servers of eFerfar have been shared for this citizen portal where citizens can on payment basis download the DSD 7/12. The databases of DSD 7/12 have been restored on respective DB Servers and 3 Application Servers from existing 15 of eFerfar have been dedicated for the DSD Portal.

22.          DSD Module is now made live on ESDS after shifting from NDC

Necessary changes have been made to make DSD application live from ESDS for data transfer which earlier used to happen at NDC

23.         Reduction of Resources

Servers which were provided by Cloud Hosting Agency for temporary basis for carrying out huge work of Online Data Correction, Digital Signing of RoR Records etc were reduced (3 Master + 3 Slave Servers) + 2 additional Servers which did not have much usage were adjusted among other servers and also released.  Thus 8 DB Servers from existing in use servers are reduced.

The Digitally Signed Database (DSD) 7/12 application and Databases hosted on NDC are shifted to ESDS. The existing infrastrucre of DB Servers will be used to accommodate the DSD 7/12 databases of NDC. The Application Servers of eFerfar will be shared (3 web servers out of 15) for the DSD application. On actual usage, resources utilization will be monitored and will be tuned as per need.

24.          Support Issues

Development team did solve support issues coming their way from NIC Support Team, SC Office Help Desk Teams and also from the State Coordinator.