Implementation Plan
Section 1: Executive Summary
Overview
The computerized and automatic urban modules offered by eGov facilitate citizens within any Urban Local Body with a transparent, speedy, hassle-free, user-friendly interaction with various applications. This section provides the phase-wise implementation plan for urban governance modules.
Implementation Methodology
Essentially, the implementation process is divided into seven distinctive stages. Each stage has predefined entry and exit criteria, roles & responsibilities to ensure objective monitoring and decision-making for the overall success of the engagement. The whole implementation lifecycle is typical of 38-42 weeks for the State, keeping in mind the entry and exit criteria defined at the beginning and end of each stage are met on time recommended.
Stage Zero is the program setup and onboarding phase which is a pre-requisite for the initiative to kick-off and requires setup of the governance model, implementation Team and decision regarding other significant elements of the initiative like funding and procurement process.
Stage One requires scoping of the initiative and decisions on the priorities for implementation by the State Implementation Team.
Stage Two is where the State Team identifies and finds solutions to the significant gaps in the product offered in response to the State's needs.
Stage Three involves the configuration and customization of the product offered. This involves working on various State-specific needs and incorporating them into the products.
Stage Four is about doing a pilot launch in UAT and including all the necessary feedback on the product.
Stage Five involves the product roll-out at the State level (Go Live) starting with a couple of ULBs to State-wide coverage in phases.
Stage Six is where sustenance and ongoing improvements are worked upon while the product is functional within the State. (For details on the implementation plan refer to Section 3)
Critical Success Factors For Implementation
The urban governance module implementation requires meticulous planning and close coordination between various stakeholders at the central and State levels. The success of the initiative is dependent upon many factors like strong Program governance, availability of trained resources, financial planning, targeted Implementation Team onboarding, focus on last-mile capacity building and ensuring necessary support to the Urban centre. Achievement of all these factors will provide the most effective and efficient roll-out and adoption of the Trade License System in the State.
Section 2: Product Suite Overview
The purpose of this section is to provide an overview of the Urban Governance Product Suite. This suite offers a digital interface, allowing citizens to apply for various municipal services and make payments online.
Key Benefits
Ease of Accessing Services: Citizens can apply for a range of services such as new licenses, renewals, amendments, and additional permits.
Regulatory Tracking: Administrators can efficiently track and manage regulatory processes.
Shorter Timelines: Streamlined and automated processes for municipal services facilitate quicker approvals and service delivery.
Data-Driven Decision-Making: The application gathers valuable data on economic activity and employment opportunities within a ULB, supporting informed decision-making.
Features
The Urban Governance Product Suite features can be broadly classified into the following modules:
Registration, Login, and Creation of User Profile
Applying for Services
Issuance of Permits and Licenses
Modifications to Permits and Licenses
Renewal of Permits and Licenses
Payments and Fees
Dashboards and Reports
General Features
Section 3: Implementation Approach
This section provides an overview of the methodology for State-wide implementation of urban product suites. The Implementation is distributed across seven distinct stages. Each stage has predefined entry & exit criteria and roles & responsibilities. This is to ensure objective monitoring and decision-making for the overall success of the program. Details of each stage are defined in this section.
Note: This plan is specific for States having more than 30 ULBs.
The implementation program is expected to be completed in 38- 42 weeks approximately with the resource deployment by the State and System Integrator (SI) Team (as defined below). However, activities and exit criteria set for each stage must be achieved to adhere to this timeline.
Seven Stages of Implementation
Stage 0 - Program Setup/Onboarding
This is a set of initial critical activities undertaken on receiving a letter of Enrolment or MOU from the State. Successful completion of these activities assures that the program is started with crucial personnel, System Integrator (SI) Teams, and funds.
Stage 0 - Program Setup/ On-Boarding | Details |
---|---|
Duration | 4-6 weeks |
Entry Criteria | Acceptance Letter/MoU by State |
Exit Criteria |
|
*Details of department cells are mentioned in section 4 of this handbook.
System Integrator (SI) Sign-up:
System Integrator and state will agree on program scope, program timelines, and budgeting & resourcing.
Stage 1 - Program Kick-Off
This stage envisages the in-person interaction of crucial State officials and implementation System Integrator (SI) Teams to kick-start the program. This stage may require multiple interactions/meetings with different interest groups. The principal objective of these interactions is to identify scope and planning strategies for phasing/ rollout, create an active collaboration & Governance approach and agree on a high-level timeline for the engagement.
Stage 1 - Program kick-off | Details |
---|---|
Duration | 4-6 weeks |
Entry Criteria |
|
Key Activities |
|
Exit Criteria |
|
*Exploration is required to understand the Inter and Intra Departmental Jurisdictions of Local Governments with respect to Trade License.
#Details of TL cell is mentioned in section 4 of this handbook
State Baseline Data: A Baseline Template is provided to collect certain vital information like no. of transactions, revenue collected in the last FYs, collection mode, budget data, etc. This data must be collected pre-rollout
Stage 2 - Solution Design
During the Solution design stage, key State officials and members, who are subject matter experts, are expected to share State acts and policies and help interpret the same for the System Integrator (SI) Team. This stage baselines the State-specific product features in the Product Configuration report.
Stage 2 - Solution Design | |
---|---|
Duration | 4-6 weeks |
Entry Criteria |
|
Key Activities |
|
Exit Criteria |
|
Pilot ULBs Specific Product Data Configuration: Master data is required from the Product Perspective for go live. For e.g.: Boundary Data, List of Employees etc. A Master Data Template will be provided for the collection of this particular data type.
Stage 3 - Configuration & Customization
This stage consists of a series of developments in accordance with the detailed project plan to ensure the smooth functioning of the customised product. Master Data Collection & Environment Setup will be achieved in this phase. Further monitoring and maintenance strategies are put in place.
Stage 3 – Configuration & Customization | |
---|---|
Duration | 6-8 weeks |
Entry Criteria |
|
Key Activities |
|
Exit Criteria |
|
Stage 4 - UAT & Go Live
During this stage, a demonstration of the product followed by a hands-on session is conducted for the ULB officials. Necessary training of ULB officials and resources required for UAT is conducted and identified respectively. The establishment of the State Support Team and required processes are initiated in this stage.
Stage 4 – UAT & Go Live | |
---|---|
Duration | 2-3 weeks |
Entry Criteria |
|
Key Activities |
|
Exit Criteria |
|
Note: The Nodal Officer is responsible to identify the ULB officials who are associated with the TL process on the ground and will be working with the technological Product in the respective ULBs
Stage 5 – Rollout
On successful Go-Live in the Pilot ULBs, and further fine-tuning to stabilize the product, the solution will be rolled out to the rest of the ULBs in phases. Guidance and support from the State Team will be required to create the rollout plans and assure the necessary infrastructure for training and deployment is available at each ULB.
Note: The rollout phase needs to be detailed for iterative activities of onboarding ULBs in batches.
Stage 5 – Rollout | |
---|---|
Duration | 5-6 weeks |
Entry Criteria |
|
Key Activities |
|
Exit Criteria | State-wide Rollout in batches:
|
Note: Only once all the stages are complete in one batch of the rollout of around 30 ULBs, the next batch begins. There are multiple phases of rollout. The second batch begins after the first batch has successfully fulfilled all the criteria of the Rollout Phase. A typical timeline for the closure of rollout in each batch is 5-6 weeks (in a batch of 30 ULBs)
Stage 6 – Sustenance and Ongoing Improvement
The final stage consists of strategies to ensure the sustenance of the product in the State. Systems are put in place to ensure the continuous tracking of data and provisions are made to improve the product if new data suggest.
Stage 6- Sustenance and Ongoing Improvement | |
---|---|
Duration | Ongoing process |
Entry Criteria |
|
Key Ongoing Activities |
|
Section 4: Roles and Responsibilities - TL Cell, eGov Team & System Integrator (SI)Team
This section outlines the activities involved in each stage of the implementation along with the responsibility and accountability of critical stakeholders - State, eGov Team and System Integrator Team onboard.
TL Cell: TL Cell is the government-appointed body chaired by the Principal Secretary/Secretary, Urban Development Department with members from Urban Development Department etc.
Resource requirements for the TL cell required to be formed by the State
Resource Name | No. Of Resources |
---|---|
Project Head | 1 |
Domain Expert | 2 |
District Nodal Officer | 1 per district |
MIS Expert | 4 |
Note:
Designations mentioned above are as per designations already driving TLs implementation at the State level.
The description of each designation is explained below.
These are the preferred figures. In the case of Domain Expert, 2 people are subject to the availability
Description of resource persons:
Project Head: Is the Head of the TL Cell who will drive the project from the State’s Side
Domain Expert: A person who is well aware of the on-ground scenario, well versed with the act, GOs passed, Prevalent Business processes, Deviations from the acts, TL Rates/ slabs applicable
Nodal officer (EO/Commissioner/ Senior Official): the project coordinator in each district to drive the project centrally. Monitor usage post Go Live- point of escalation for Implementation Team, Seasoned and worked in Multiple ULBs on various modules and has a good understanding of TL, Facilitates and Tracks data collection Post Go Live, Monitors and facilitates the adoption of the application. point of contact for eGov, SI and at the HQ level.
MIS Expert: Day-to-day tracking of the data specific to ULBs, data entry, reporting and review to senior officials
eGOv Team: eGov Team is the technical partner of the project which will provide all necessary support to the State concerning the implementation, Program Designing etc.
System Integrator (SI)Team: SI Team will be responsible for consulting, program management and the implementation of products in the ULBs in close collaboration with the TL cell, technical partner (eGov) and various other stakeholders.
Guidelines to read the tables below:
Execute - One who owns the accountability to complete the activity
Consult - One who may initiate, guide and in the process, handhold the execution of the activity
Stage 0 - Program Setup/ On-Boarding | ||
---|---|---|
Task/Activity | eGov | State Leadership |
Appoint of TL Cell | Consult | Execute |
Finalise funding for the program | Consult | Execute |
Define state -specific procurement process | Consult | Execute |
System Integrator(SI) Team sign-up/onboarding | Consult | Execute |
Finalise Trade License Program Vision | Consult | Execute |
Note: Stage 0 is where the TL cell and SI team is formed, hence there are only two entities playing a role which are that of eGov and the state leadership. Once the TL cell and SI team are finalised, their role begins in the following stages.
Stage 1 - Program kick-off | |||
---|---|---|---|
Task/Activity | eGov | TL Cell | SI Team |
Identify & agree on scope and exclusions | Consult | Consult | Execute |
Identify pilot ULBs | Execute | Consult | |
Project Kickoff - Implementation Methodology Presentation | Consult | Consult | Execute |
Product Walkthroughs | Consult | Execute | |
Define Project Steering Committee structure and Project Governance process | Consult | Consult | Execute |
Define phases of deployment/ rollout | Consult | Execute | |
Agreement on Deployment Priorities and high-level delivery timelines | Consult | Execute | |
Identify and study all TL process | Consult | Execute | |
Finalize Program Success Metrics for Adoption and Governance adhering to the vision of the program | Consult | Consult | Execute |
Stage 1 - Program kick-off | |||
Task/Activity | eGov | TL Cell | SI Team |
Internal Capacity Building, program logistics at State and ULBs, as per the current scenario | Execute | Consult | |
Collection of baseline data to measure end line target for the product (Revenue generated, total properties in ULBs etc.) | Consult | Execute | Consult |
Circulation of baseline data collection templates to the state/SI Team | Execute | Consult |
Stage 2 - Solution Design | |||
---|---|---|---|
Task/Activity | eGov | TL Cell | SI Team |
Standardisation of all TL processes | Consult | Execute | |
Define criteria for success | Execute | Consult | |
Initiate policy change, if needed based on Processes defined | Consult | Execute | Consult |
Conduct Product familiarisation workshop | Consult | Execute | |
Initiate collection of master data from pilot ULBs | Consult | Execute | |
Finalise data migration/collection/sync-up approach | Consult | Execute | |
Finalise data validation approach | Execute | Consult | |
Capacity Building for making state team aware about basic usage of tools like MS Office, mails etc. | Execute | Consult | |
Dashboard design finalisation for Program Tracking | Execute | Consult |
Stage 3 – Configuration & Customization | |||
---|---|---|---|
Task/Activity | eGov | TL Cell | SI Team |
Setting up development environments | Consult | Execute | |
Development/customisation of reports and dashboards | Consult | Execute | |
Development/Integration of portal | Consult | Execute | |
Third-Party Integrations (Payment gateway, Handheld/pos device) | Consult | Execute | |
Updation of user manuals and other key documents | Consult | Execute | |
Preparation & execution of Test Cases | Consult | Execute | |
Setup monitoring, support & maintenance processes, tools and dashboards | Consult | Execute | |
TL legacy data collection from Pilot ULBs (at least) | Consult | Execute | |
Capacity Building for making state team aware about basic usage of tools like MS Office, mails etc. | Execute | Consult | |
Verification and Migration of Pilot ULB data | Consult | Execute | |
Identification of participants for UAT session | Execute | Consult |
Stage 4 – UAT & Go Live | |||
---|---|---|---|
Task/Activity | eGov | TL Cell | SI Team |
UAT Environment Setup | Consult | Consult | Execute |
Issues/bug identification and resolution | Consult | Execute | |
Regression UAT and sign off from Pilot ULBs/ State | Execute | Consult | |
Setting up the Production environment | Consult | Execute | |
Setting up Support Centre & processes (Help Desk) | Execute | Consult | |
Training user | Execute | Consult | |
Training Trainer | Consult | Execute | |
Stage 4 – UAT & Go Live | |||
Task/Activity | eGov | TL Cell | SI Team |
Training the Support Resources | Consult | Execute | |
Marketing & promotion activities | Execute | Consult | |
Go Live & launch event | Consult | Execute | Execute |
Setup of review and monitoring cadence/team | Execute | Consult |
Stage 5: Rollout | |||
---|---|---|---|
Task/Activity | eGov | TL Cell | SI Team |
ULB configurations phase wise as per the Project Plan | Consult | Execute | |
Verification and Migration of ULB data phase wise as per the Data Agreement Sign Off provided by the State | Execute | Consult | |
Establishment of bug ticketing tool for resolving ground level issues by the state team | Consult | Execute | |
Training the Users at the district level | Execute | Consult | |
Pan State Roll Out – Phase wise | Consult | Execute | Execute |
Stabilise product | Consult | Execute |
Stage 6- Sustenance and Ongoing Improvement | |||
---|---|---|---|
Task/Activity | eGov | TL Cell | SI Team |
Adoption Review Meetings as per the vision defined for the program | Consult | Execute | Consult |
TL Cell Focuses on Using data for:
| Execute | Consult | |
Plans of ongoing Sustenance in Place with respect to:
| Consult | Execute | Consult |
Section 5: Overall Program Assumptions
Areas | Assumptions |
---|---|
Infrastructure |
|
Project Scope |
|
State Team |
|
Documentation |
|
Training |
|
Implementation |
|
Glossary
Vision: Defining the time frame to go live, the time frame to scale it pan state, the value proposition of the programme for the state and year-on-year financial targets and adoption targets
Project Plan: A detailed plan of Program schedule/timelines, implementation phases, team structure and ongoing support and maintenance is required.
System Integrator: The Entity/Company collates all the subsystems required for the project and integrates them to achieve the program objective
Program Charter: Outline of implementation plan agreement with priority applications and broad timelines, program governance model, program success metrics and capacity building.
Acceptance Letter/MOU: Formal Acceptance/Sign Off of the Client State with a clear mandate of the Program
Program Success Metrics: Defining the parameters (which are measurable) prior to the program, on which the success of the program is to be measured on the completion of the program
Project steering committee: The key body within the governance structure is responsible for the business issues associated with the project that are essential in ensuring the delivery of the project outputs and the attainment of project outcomes.
Project governance: Set of policies, regulations, functions, processes, procedures and responsibilities that define the establishment, management and control of projects, programmes and portfolios.
Scoping: List of activities measured against the time taken to complete them in accordance with the project goals
Baseline data: Set of information that serves as a foundation to compare other data acquired afterwards
Project Kick-off meeting: Meeting with the project team and the client of the project. This meeting would follow the definition of the base elements for the project and other project planning activities
Fitment Study: GAP Study of the Existing/Required Field Process Vs Product
Data migration: Existing Records of the functional activities need to be moved into the Database of the newly released Application
Data collection: Required data for the roll-out of the applications, which needs to be collected from the existing functional process
Data validation approach: This approach enables the sanctity of the Data with built-in validation by the Design
Data synchronization: The process of establishing consistency among data from a source to a target data storage and vice versa and the continuous harmonization of the data over time.
Pilot Implementation: Any new process is tested out as a pilot in one or two instances before pan implementation
Pilot ULB: The ULBs selected for the pilot implementation are called pilot ULBs.
Roll out: On successful clearance of the Pilot, the Process/Application/Services are implemented across all Offices/ULBs
Deployment: Deployment defines the complete package of Software components set up in a particular environment
Customization: Details of changes to be made in the Product to comply with the needed field process
Configuration: Defining existing content such as Options and Variables based on the requirements on the ground
Product walkthrough: Explaining to the users step-by-step through a set of actions that they need to take to achieve a specific outcome