Pain points in e-Governance – 8 : Non-Adoption of Master Data Management

  

 Non-Adoption of Master Data Management

India has 662538 villages, 283967 local bodies and 736 districts. Many villages have the same name. Have you ever wondered spelling of your district, city, village, wards, etc., are different in various records given by departments. 


Department uses a different naming convention for its administrative purpose. Some use Census code, a few uses Local Government codes and others use their code. Census code changes during each cenus. Data across departments becomes fragmented and duplicated 


Due to different codes for the same places, sharing data among programs and across systems is often impossible because of integration issues. This creates a huge roadblock in consolidated reporting. Many times it leads to dispute. Thereby reducing the chances of Improving service delivery, streamlining operations and efficient Decision Making.


Since data is stored in various databases, storage infrastructure is also more, which adds a huge cost to the state.
 
 The problem is not the lack of a system, but rather the lack of consistency in the various terminologies and methodologies employed by different departments.  


If Departments start using common/standard codes which are termed as master data, for the locality, this issue will be resolved. First departments have to start seeding standard code in their database. For example for locality LG code designed by GOI can be used ( https://lgdirectory.gov.in ). Here each locality has a unique ID. 


Similar stands can be used for citizens using the Aadhaar database using the e-KYC process. Where every individual has a unique ID, which avoids duplicates and also resolves identity crises. Government can identify or create such various master data sets and  make them mandatory across the department. 


This allows streamlining of data across all government applications creating a more productive process and provides a single, trusted view of data and keeps everyone on the same page. Then it makes ways for a holistic view of service consumption for more informed decisions
 
I am sure this exercise will bring ten-fold easiness in service delivery if adopted by all government domains.

While data integration using, MDM is not a silver bullet for all the issues of government but certainly eases the decision making. The big question as a system is ready to come out of confusion and chaos since most of us love chaos.

Disclaimer: Purely personal opinion. 


 

 

Comments

  1. I completely agree for common database across all deptments. Enforcement of the same will take us a long way in realising a robust service delivery system. Thanks for sharing this boss.

    ReplyDelete
  2. Dear Sir,
    What you have written is true and you have given good suggestion for this problem.

    ReplyDelete
  3. Good idea. Common data system I'll definitely save time & resources. It's one time excercise govt has to do with periodical upgradations which can give robust results in long run. But big issue here is, is departments are ready to accept this big challenge & come together to create common data system?

    ReplyDelete
    Replies
    1. Very true. There is high need of Change management before any thing else.

      Delete
  4. Yes sir it is right, Good suggestion sir, if Government implement this, it good for all sir.

    ReplyDelete
  5. Ultimate. ..someone would have to initiate. ..

    ReplyDelete
    Replies
    1. Dear Sir, each department wants it's autonomy!!!. For each problem government starts separating departments, offices, boards, corporations then try to accumulate data. In the name of streamlining again we struggle to integrate them. Then everyone thinks that they are being snatched away with their powers. I talking about generally what is done not with respect to change in name which is the topic. People like you need to be at power centre to set things right.

      Delete
    2. True, but some where it has to start.

      Delete

Post a Comment

Popular Post

Pain points in e-Governance - 3 : Resource Hopping

Good Governance Tool 1: Digilocker

Pain points in e-Governance - 1: "e"

Good Governance Application 1 : e-Office

Good Governance Tool 2: e-Sign

Pain points in e-Governance – 5 : Longer Decision/Approval Cycle

Pain points in e-Governance - 2 : Vendor Locking

Pain points in e-Governance – 4 : Reinventing Wheel

Good Governance Application 2 : Direct Benefit Transfer