Professional Documents
Culture Documents
E-Governance & Erp Challenges and Strategies
E-Governance & Erp Challenges and Strategies
E-Governance & Erp Challenges and Strategies
CHALLENGES AND
STRATEGIES
Presented by:
Kushal A. Shah (417)
Ankit Poddar (115)
Yeshi Chaudhary (406)
Manish Kumar (111)
Ishavasyam Dash (423)
E-READINESS- INDIAN STATES
Leader
Expectants
Standardize
HR
information
Integrate
Reduce
Financial
inventory
Information
Standardize
Integrate
and speed up
operational Customer order
information
processes
E-Governance in Employment Directorate
Architecture Awareness
Re-engineering
Standards Capacity Building
Improvement
Technology Training Staff
Reforms
Components Skill Development
Optimisation
HW, SW, NW
Connectivity
Publish
Interact
Transact
Good Governance- Components
Rule of law Effectiveness & efficiency
Transparency Equity and inclusiveness
Accountability Consensus orientation
Responsiveness Participation
Process Re-engineering
Fiscal Reforms
Good Governance
Outside Vendors
Chairman IT Consultants
Committee
Hon’ble High Court
Software IT Consultant Software Consultants
Developer
Analysis
Pre-Development
Design
BPR Tech Evaluations
Technical
Training
Admin Reforms
Development SW Project
Manager IT consultant Financial Planning
Testing Project
Co-ordinator Legal
Data Creation/
Entry/ Validation
Personnel
Deptt. IT
Manager
ISP
Implementation on
actual data and Site Preparation
Supervision
Networking
Systems Management Hardware
1. Citizen
2. Locations
Citizen 3. Products/Information
Government
4. Rating/ Itinerary
5. Order
6. Order Status
7. Citizen
Oracle System – Order Release Screen
Key Benefits of Integrated Order
Management System
• Improved Citizen Service
• Single Source of Truth for Citizen Profiles
• Lower Total Cost of Ownership (TCO)
• Service, Cost and Price synchronization
• Order Evaluation
• Integrated Order Management – Generation
of Sales Order, Initiate billing and creation of
CRM assets
Standardize and Speed Up Operational
Process
• Operational Analysis
22
Before ERP
This is Tenant continues
usually to default further
verbal
Currently rent is Attachment Notice
paid by cash is issued
Tenant
Tenant
Tenant
Rent collector
visits tenements &
collection begins MHADA sends
reminder to
Written tenant for
Rent Bill notification is payment
issued
MHADA/Rent collector
Yes
Rent Collector
Entry in
Start: MHADA issues
Rent receipt is the field
rent bill to tenant
issued to tenant rent
register
Rent Collector
Outputn1: Remittance
Generation Report
Name & Total
of daily
Input: Address of Rent
remittance
the tenant collected
Rent collector report
1. Details of Tenement
deposits the rent
2. Dues to be collected
in bank
Output 2: Receipt
Voucher System of
generated database
$
for rent collection
Bank
23
After ERP
Cash/Cheque Payment
Bill + Payment
Cheques
Tenant Cheque deposits $
Drop Box
Courier - Snail Mail Cheques BANK
Read-Receipt
confirmation on view
Receipt Cheque deposits
E-mail
SMS
Fund Transfer
Card Payment
VISA/MCI
Personal computer
Customer Service
Generation of
A/C Statement
Entry of data to
MHADA Database
Server
Report generation of Rent
MHADA
Details
Name Address Rent Due
Personal computer
SUCCESS STORY OF
DEPARTMENT OF PLANNING
MAHARSHTRA GOVERNMENT
CASE BACKGROUND
• Maharashtra - 3rd largest state in India by area and the second
largest by population
• Richest state with highest Per Capita Income
• State's administrative machinery runs many infrastructure projects
– both social and industrial
• Respective government departments are responsible for the
execution of projects
• Lot of planning involved in running entire government machinery
and handling the massive amounts of data collected
CASE BACKGROUND
●
DISTRICT LEVEL SURVEYS AND CENSUS POLLS
●
DATA COLLECTION
ANALYSIS REQUIREMENT
GATHERING PHASE
REQUIREMENT FOR DATA ENTRY
GATHERING APPLICATION
HARDWARE SERVER
DEPLOYMENT AT INSTALLATION
DISTRICT LEVEL AT DATA CENTRE
TRAINING OF 120
TRAINING OF DISTRICT
STATISTICAL
EDP TEAM OFFICERS
BENEFITS
• Reduction in RTI Query Response Time by routing to
DES
• Customization of RTI reports for responding to queries
related to different departments.
• Blue Star team will carry out big projects like conducting
a census survey etc in the future.
• Better disbursement of funds for development
BENEFITS
• Improved Operational efficiency and improved data
quality
• Improve process of Annual State Budget planning
• Reduction in processing and publishing NSS results
• Shorter time lag between decision making and execution
- policy decisions are taken in a certain number of days
but operational decisions take years to be finalized.
Failed implementation case
LOOPHOLES IN IMPLEMENTATIONS
• E-governance in India has miserably failed. The reason why e-governance is a
big failure is because neither our political parties nor our elected governments take
e-governance seriously.
• The problem is due to “lack of accountability” among the Government Departments. The National E-
Governance Plan (NEGP) and E-governance in India have failed to achieve their motives. In short,
there is a complete “ICT Failure in India”.
• At the International level, India lacks the basic prerequisites of e-governance, i.e. e-readiness, public-
governmental interaction, public services, etc and hence mirrors the incompetency of bureaucrat and
Government
• Adding to the misery is reports by Symantec, security research firm that confirms India may emerge
as the leader in Malware activities if the cyber security norms are not established for future e-
governance initiatives of India.
• It is high time that Indians should peep outside the “Indian Shining Syndrome”. The call of the hour is
to understand the real meaning of e-governance and its implications.
.
FACTS OF THE CASE :
PROJECT NAME : MANDALS ONLINE IN ANDHRA PRADESH
• Andhra Pradesh has 1,124 administrative units known as mandals. Each of the Mandal Revenue
Offices (MROs) was computerized under this project.
• Approximately $20 million is devoted annually to the program, which provides free education,
books, scholarships, subsidized medical facilities, and support for land and house purchases.
• A cast certificate is necessary to access these program benefits , which are issued by the MROs.
• Total cost of the project was $13 million. 70% of the funding was provided by the World Bank
BEFORE IMPLEMENTATION:
• Previously, a person requiring a certificate of his/her caste or date of birth would
apply in writing to the MRO with a specified form.
• The application would be marked to the Revenue Inspector (RI) and sent to the
Village Administrative Officer (VAO) for inquiry. If the VAO was satisfied concerning
the claim of the applicant, he would recommend issuance of the certificate.
• The RI countersigned this recommendation. The MRO then would route the
application to the clerk concerned, who filled in the relevant columns in the pre-
printed certificate.
• This certificate was numbered, entered in a register, and sent to the Revenue
Officer for his signature.
• Finally, once the Revenue Officer signed the certificate and affixed his seal, the
certificate would be given to the applicant. This process took between 20 and 30
days to complete.
AFTER IMPLEMENTATION:
• Now all of AP's 1,124 MROs have been computerized. A citizen interface counter
was created to receive applications for the integrated certificate in the prescribed
format.
• The Junior Assistant/Operator numbers it, and validates the information against the
certified database created from the 1995 Statewide Multi-Purpose Household
Survey (MPHS).
• The certificate is printed out with a bar code, and the whole process is done in less
than 15 minutes.
• The system is also designed to maintain a record of land holdings in the area, and
can issue a patta (certificate of land holding) and assist in land transfers and
management of government lands.
• Each person in the database has a unique Social Security Identification (SSID)
number.
• Once all mandal offices are connected to a statewide network, the SSID will be
transferred electronically from one mandal to another if an individual shifts his/her
residence within the state.
IMPLEMENTATION
Challenges :
• Co-ordination with various departments
• Problems related to data
• Poor infrastructure facilities
• Lack of trained human resources
KEY LESSONS
• The current level of use of the new systems does not justify the investments that
were required at each of the centers.
• Government should have a clear, coherent rationale and plan for choosing a
particular E-Government application.
• Nine years have already passed since the project implementation began. By the time
the system truly begins to deliver, the hardware and software may become obsolete.
• A better approach might have been to ready an initial one hundred centers to deliver
all the related applications. The same support team could then have rotated to new
locations.
• Factor Model
External pressure Drive for reform from outside government, e.g. from civil society
Internal political desire Drive from key government officials for reform and for achievement of e-government goals
Overall vision and Overall vision and master plan for good governance and for e-government, identifying 'where
strategy we want to get to', seeing IT as the means not the end, and integrating IT with broader reform
objectives
Effective project Including clear responsibilities, good planning and consideration of risk, good monitoring and
management control, good organisation of resources, and well-managed partnerships between public
agencies, and public-private
Effective change Including leadership with a project champion, use of incentives to create commitment to and
management ownership of e-gov project, and stakeholder involvement to build support and minimise
resistance
Effective design An incremental/piloting approach with feasible objectives and quick, scalable outcomes;
participatory involvement of all stakeholders, leading to designs that meet real user needs
and match real user contexts
Requisite competencies Presence of the necessary skills and knowledge, especially within government itself; need
both management and IT skills and knowledge
infrastructure For example, encouraged through appropriate telecoms policies
Factor
CRITICAL FAILURE FACTORS
Explanation
Lack of internal drivers Pressures only from IT vendors, with no internal ownership (or understanding of e-gov
Lack of vision & strategy Lack of any long-term view, lack of guidance, and lack of link between ends and means; may
be caused by ever-shifting senior staff and/or ever-changing policy and political environment
Poor project Dispersed responsibilities due to multiple ownership of project; absence or weakness of
management controls; ineffective procurement
Poor change Lack of support from senior officials (causing lack of resource allocation, and negative
management message to other groups); lack of stakeholder involvement (causing lack of owner
Dominance of politics and Focus of key players on personal needs and goals, often related to 'playing politics', with
self-interest symptoms like infighting, resistance where loss of power is feared, 'me too' copying of e-gov
solutions for image purposes, obsession with electoral impacts and short-term kudos, and
corruption
Poor/unrealistic design Caused particularly by lack of inputs from key local stakeholders, leading to designs that are
over-technical, over-ambitious, or mismatched to local environment (culture, values) and
needs; occurs particularly where foreign donors, firms and consultants are involved. Other
design problems: lack of piloting, lack of fit to organisational structure
Lack of requisite Lack of IT knowledge and skills among developers, officials and users/operators; lack of local
competencies knowledge among developers
• The Unique Identification Authority of India (UIDAI) : February 2009, attached to the Planning
Commission.
• The purpose of the UIDAI is to issue a unique identification number (UID) to all Indian residents
that is
– (a) robust enough to eliminate duplicate and fake identities, and
– (b) can be verified and authenticated in an easy, cost effective way.
• The law : stipulate rules, regulations, processes and protocols to be followed by different
agencies partnering with the Authority in issuing and verifying unique identity numbers.
• Budget 2010-2011 presented in Parliament - Rs 1,900 crore allocated for Unique Identification
Authority of India
The Central ID Data Repository (CIDR)
• central data repository
• core services– it will store resident records, issue unique identification numbers, and verify,
authenticate and amend resident data.
• The CIDR will only hold the minimum information required to identify the resident and
ensure no duplicates.
• This will include:
• i) Unique Identity Number: unique across all 1.2 billion residents in India.
• ( number will not contain intelligence : susceptible to fraud and theft, and migration of
• the resident makes location details out of date) The UID will be a random number.
• ii) Identity fields: The fields associated with the UID number will be:
• Name Date of birth Gender
• Father’s name Father’s UID number (optional for adult residents)
• Mother’s name Mother’s UID number (optional for adult residents)
• Address (Permanent and Present)
• Expiry date
• Photograph Finger prints
The UniqueID Agencies
Registrars –state governments or central government agencies such as the Oil Ministry and
LIC/private sector participants such as banks and insurance firms.
• The Registrars : need to make changes to their processes : UIDready.
• The UIDAI will support them : linking to the CIDR : connecting to the UID system : UID
fields to their databases.
• The UIDAI : some Registrars :use the CIDR solely for authentication purposes.
Enrolling Agencies –directly interact with and enrol residents into the CIDR. For example,
the hospital would be the ‘enrolling agency’ : report to the municipality sub-registrar.
Outreach Groups – The UIDAI : also partner with civil society groups and community
networks which will promote the UID number and provide information on enrolment
for hard to reach populations such as rural women, tribals and others.
UID enrolment strategy
in rural and urban India
1) Adoption risks: Without critical mass among key demographic groups (the rural and the poor) the number will
not be successful in the long term.
2) Political risks: The UID project will require support from state governments / individual government
departments, especially in linking public services to the UID, and from service providers joining as Registrars.
3) Enrolment risks: address risks : creating sufficient touch points in rural areas, enabling and motivating
Registrars, ensuring that documentary requirements don’t derail enrolment in disadvantaged communities –
as well as managing difficulties in address verification, name standards, lack of information on date of birth,
and hard to record fingerprints.
4) Risks of scale: The project will have to handle records that approach one billion in number. This creates
significant risks in administration, storage, and continued expansion of infrastructure.
5) Technology risks: The authority will have to address the risks carefully – by choosing the right technology in the
architecture, biometrics, and data management tools; managing obsolescence and data quality; designing the
transaction services model and innovating towards the best possible result.
6) Privacy and security risks: The UIDAI will have to ensure that resident data is not shared or compromised.
7) Sustainability risks: The economic model : sustainable in the long-term, and ensure that the project can adhere
to the standards mandated by the Authority.
REFERENCES
• E-GOVERNANCE & ERP CHALLENGES AND STRATEGIES – Gita Kumta
• http://
biztech2.in.com/india/casestudies/enterprise-solutions/hpcl-refines-busine
ss-processes-with-erp-implementation/28091/0
• http://egovindia.wordpress.com/2006/06/23/when-are-we-ready-for-erp/
• www.ewubd.edu/ewu
• www.erpwire.com/erp-articles/india-and-erp.html
• www.erp-india.com/
THANK YOU