W&S Implementation Guide
Last updated
Last updated
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
Access to clean and safe water is one of the basic needs of citizens. Each Urban local body has been mandated with catering to the water and sanitation needs of its citizens. The computerized and automatic Water and Sewerage system offered by eGov enables citizens who seek to apply and pay for water and sewerage connections within any Urban Local Body with a transparent, speedy, hassle-free and user-friendly procedure. The ULB officials can now sanction connections, generate bills and collect payments for water and sewerage connections more efficiently. (For details on product features refer to Section-2)
For the offered product, the implementation process can be divided into six major distinctive stages. Each stage has predefined entry and exit criteria, roles & responsibilities to assure objective monitoring and decision making for the overall success of the engagement. The whole implementation lifecycle is typical of 23-27 weeks for the State/UT keeping in mind the entry, and exit criteria defined at the beginning and end of each stage are met on time recommended.
Stage Zero-program setup and onboarding 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 of the initiative requires scoping of the initiative and decide on the priorities for implementation by the State/UT implementation Team. In Stage Two, the W&S team is appointed and its processes are standardized. In Stage Three, the State/UT Team will work upon identifying and finding solutions to the significant gaps in the product offered w.r.t. to the need of the State/UT. Configuration and customization of the product offered in the primary objective of stage four. This involves working on various aspects of UT-specific needs and incorporating them into the product suite offered. In Stage Four and Five, post doing UAT and including all the necessary feedback on the product, the roll-out of the product is done at the State/UT level(Go Live) from a couple of ULBs to pan State/UT coverage. In Stage Six of sustenance and ongoing improvement, key activities are adoption and governance tracking with the planning of ongoing sustenance. (For details on implementation plan refer to Section-3).
Implementation of Water and Sewerage (W&S) requires meticulous planning and close coordination between various stakeholders at the centre and State/UT level. The success of the initiative is dependent upon many factors like strong Program governance, availability of the trained resource, 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 Water and Sewerage Implementation System in the UT.
The Water and Sewerage (W&S) module provides a digital interface to apply for water and sewerage connections and pay the water and sewerage charges for connection/s. It can be used by the citizens, Urban Local Body (ULB) counter employees and field employees, and ULB Administrators to accomplish their specific tasks. It is available as a mobile and web-based application. The W&S product features can be broadly classified as the following modules:
Registration, Login and Creation of User Profile
Application for new Water/Sewerage connection
Searching for a Connection
Modifications to a Connection
Entering meter reading of metered connections
Generate Demand
Payments collection and Receipts
Dashboards and Reports
This module provides enables the following capabilities:
OTP Based Login for Citizen via Web/Mobile App
OTP Based Login for Employee via Web/Mobile App
Provision for language selection during first time registration for both Employee and
citizens
Provision of creating a personalized Profile for Citizens and employees on Web App
Login Credentials for the various hierarchy of employees
Role-based access for performing different actions relating to the W&S module
The system allows the Citizen / ULB user (with an appropriate role in the system) to apply for a New Water/Sewerage connection. The application goes through an approval workflow before it is available for various transactions in the system. The workflow to be followed for a new water/sewerage connection is configurable. In the workflow, the ULB official will generate the estimation notice. Once the payment is made, a work order will be generated.
Every time there is a change in the status of an application, the citizen will be intimated through in-app notifications, SMS and email. The citizen and employee can view the history of the various states that an application has been in and the comments added by the employee in each state of the application.
Only employees from the W&S department will be able to access the feature, to search for water and sewerage connections. They can search for any connection based on parameters such as:
Consumer number
Application number
Owner mobile number
Application status
From date
To date
The search result contains the Application number, Consumer number, Owner name, Status, Due amount and the Pay now option. The Employee can make payment for a connection on the citizen’s behalf using the ‘Pay Now’ option.
Citizens can also search for their connection in the portal. They can search using the Owners mobile number, Property ID, Consumer number etc. The search result yields, Owner’s Name, Address, Due amount and Pay option.
The system facilitates the title transfer of water tap connection from one person to the other person. Title transfer of water tap connection directly depends upon Property tax. If title transfer is done in the property tax module then at the time of final approval, the changes will reflect in the W&S module automatically. After the title transfer has been completed successfully, subsequent bills will be generated with the details of the new owner/s.
Water tap change in usage happens when property type is changed from residential to Non-residential or from Non-residential to residential. Change in usage directly depends on the property tax module. If the property type is changed in the Property tax system then it will automatically reflect in the W&S system. When there is a change in the usage type, the subsequent bills will reflect the rates as per the updated usage category. When there is a change in the usage category in the middle of the billing cycle, pro-rata charges will be applied in the next billing period.
The change in connection category from non-metered to metered and vice-versa is also possible in the W&S system with the appropriate workflow configured to intimate all stakeholders of the change and collect any charges (if applicable) from the citizen.
On the W&S billing screen, there is a card called ‘Meter reading’. An employee can click on Meter reading which redirects the employee to the meter reading landing screen. The employee can search based on the following criteria:
ULB
Boundary Type
Boundary Value
Billing Year
Billing Period
Billing Period Value
Consumer No.
This feature facilitates the employee to search for all results based on desired criteria. The search result yields the following values: consumer number, owner name, meter status, last reading, current reading, date and consumption.
The employee can edit meter status, current reading, date and consumption under certain conditions. Based on this information the employee can generate the bills for connections.
In the system, there is a feature to generate demand under the billing section. Generate demand has a search feature in which the connections can be searched for which demand has been already generated. An employee can view, also edit those demands based on certain conditions.
The system has the capability to configure the demand generation as an automatic or a manual process. In the automatic process, the demand generation for non-metered connections is automatically done periodically. For metered connection as soon as the employee enters the meter reading and clicks on ‘SAVE’, the demand is generated.
Any success/ failure to generate demand triggers an automatic notification to the concerned ULB officials via email. Also, the demand generation cycle, demand generation date and officials who should receive the notifications can be configured.
The citizen can pay for dues by searching his/her connection. In search results, the citizen can click on pay, which redirects to the summary page of the dues. After this, the citizen can pay for dues online. An employee can also collect the payment on the citizen’s behalf. After searching for the desired connection, clicking on pay will redirect the employee to the common payment page. The employee can print the receipt after the payment is successfully collected. The citizen is also notified and gets a download receipt link in the notification.
If the Water tap owner has got his own water source then the water tap owner can initiate for Water tap connection closure permanently. So, that tap will be closed permanently and demand would not be generated for the connection. Application for the closing of water tap connection is accepted only with the latest water charges receipt and clearing of old dues.
The state-level administrator can keep track of relevant metrics by using dashboards. Dashboards for W&S can be accessed by a state-level user under login.
The dashboard has these components:
Financial Indicators
W&S Total collections YTD
Water Collection
Sewerage Collection
Water - Demand vs Collection (Monthly trend)
Sewerage - Demand vs Collection (Monthly trend)
Municipal Adoption
W & S: No. Of ULBs Live
W & S: Total Number of ULBs
Water Consumers by Connection Type
W & S Consumers by Usage Type
Total Collections by Source
Total Collections by Mode
W & S Adoption : ULB Wise
Today’s Collections
W&S Total collections: Today
Water Charges - Total collections: Today
Sewerage Charges - Total collections: Today
W&S - Total No. of Receipts: Today
Water - Total No. of Receipts: Today
Sewerage - Total No. of Receipts: Today
Mode wise W&S collections: Today
W&S ULB wise collections: Today
This section provides an overview of the methodology for State-wide implementation of W&S. The Implementation of W&S 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 document is specific for States that have more than 30 ULBs.
W&S implementation program is expected to be completed approximately between 38- 42 weeks with the resource deployment by the State and System Integrator (SI) Team (as defined below). However, it is critical that activities and exit criteria set for each stage are achieved to adhere to this timeline.
There is a set of initial critical activities that are undertaken on receiving a letter of Enrollment from the State/Union Territory. 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
Duration
4-6 weeks
Entry Criteria
Acceptance Letter/MoU by State
Exit Criteria
Finalize Water and Sewerage Program Vision
Finalize funding for the program
Define State/Union Territory -specific procurement process
Water and Sewerage Cell appointment. Consisting of :
Domain expert
Nodal officer (EO/ Commissioner/ Senior Official)
Program Head
System Integrator(SI) Team sign-up/onboarding
Define the value proposition of the programme for the state
Define the time frame within which the state needs to:
Go live
Scale pan-state
Define Year-on-Year(YoY) Financial Targets
System Integrator(SI) Sign-up:
System Integrator and state will agree on program scope, program timelines, and budgeting & resourcing.
This stage envisages the in-person interaction of crucial State/UT officials and implementation System Integrator(SI) Teams to kick-start the program. This stage may require multiple interactions/meetings with different stakeholders. The principal objective of these interactions is to identify scope, plan strategies for phasing/rollout (in pilot ULBs/Pan State) and create an active collaboration & Governance approach and agree on a high-level timeline for the engagement.
Stage 1 - Program kick-off
Duration
4-6 weeks
Entry Criteria
Program setup (Stage 0) is complete
SI Team signed-up
Key Activities
Project kick-off meeting and stakeholders consultation
Identify & agree on scope and exclusions
Finalize the approach on obtaining the W&S Connection Legacy Data (At least from the Pilot ULBs)
Identify pilot ULBs
Product Walkthroughs
Define Project Steering Committee Structure and Project Governance process
Define phases of rollout/ deployment
State Baseline Data (As per the Module)
Pilot ULBs Specific Product Data Configuration
Agreement on Product Feature Priorities and high-level delivery timelines
Assessment of all on ground W&S process along (1) citizen services/channels around it (2) Integration with other Department process
Finalize Program Success Metrics for Rollout and Adoption and Governance adhering to the vision of the program
Internal Capacity Building, program logistics at State and ULBs, as per the current scenario
Exit Criteria
Publish the program charter
Implementation plan agreement with priority applications and broad timelines
Program Governance Model
Program Success Metrics
Capacity Building
W&S Cell formation and appointment
Finalizing the strategy for W&S Connections Legacy Data
Master Data preparation/collection kickoff from Pilot ULBs
Cloud Infrastructure procured
Project Office Space allocated
Program Branding( Name, Logo, Tagline etc.)
Note
1) State Baseline Data (As per the Module): 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 is vital for various analysis at the state level. This data must be collected pre-rollout. The baseline data collection templates will be provided to the state/SI Team.
2) ULBs Specific Product Data Configuration: This Master data is required from the Product Perspective to go live. For eg: Connection Legacy Data, Boundary Data, List of Employees, Rates etc. Master Data Template will be provided for the collection of this particular data type.
During the Solution design stage, key State/UT officials and members, who are subject matter experts, are expected to share State/UT acts and policies and help interpret the same for the System Integrator (SI) Team. This stage baselines the State/UT-specific product features in the Product Configuration report.
Stage 2 - Solution Design
Duration
4-6 weeks
Entry Criteria
Program Charter
W&S Cell appointment
Key Activities
Standardization of all W&S processes, if needed
Initiate policy change and Process Re-engineering, if needed based on identified improvements
Conduct Product familiarization workshop
Initiate collection of Master Data (Legacy & Product Based) from pilot ULBs
Finalize data migration/collection/sync-up approach (State needs to provide a signoff)
Finalize data validation approach (State needs to provide a signoff)
Building capacity for basic understanding of resources and tools required to be used
Exit Criteria
Publish the W&S processes, data template/workflows (State needs to provide a signoff)
Finalization of Roll-out plan(in different phases)
Solution agreement for required state/UT-specific customisations
Finalization of Initial Reporting and Design (State needs to provide a signoff)
Finalization of Dashboard KPIs (State needs to provide a signoff)
Sign-off on data approach( Data collection/migration/correction/sync-up/validation) from the state
Detailed project plan
This stage consists of a series of developments in accordance with the detailed project plan to ensure the smooth functioning of the customised product. Preparation for the testing and data collection of the product UAT is complete. Further monitoring and maintenance strategies are put in place.
Stage 3 – Configuration & Customization
Duration
6-8 weeks
Entry Criteria
Product Configuration Report has been Signed Off by the State/UT
Detailed Project Plan set up in accordance with master data collection and environment setup
Key Activities
Setting up development environments
Development/customization of reports and dashboards
Development/Integration of portal
Third-Party Integrations (Payment gateway, Handheld/pos device)
Updation of user manuals and other key documents
Preparation & execution of Test Cases
Setup monitoring, support & maintenance processes and tools
W&S and Legacy data collection from Pilot ULBs (at least)
Training for basic understanding of resources and tools required to be used (system-related)
identify ULB level nodal officers for day to day support
Legacy Data Validation signoff from the state on Data Validation
Post this migration exercise will be taken up for water/sewerage connections
Migration and verification of Pilot ULB data as per data provided by the State
Exit Criteria
Data Validation Signoff by the state, post which the Legacy Data will be uploaded to UAT
Configured/Customized product that is ready for UAT
Monitoring, support & maintenance of Dashboards
finalization of Initial Reporting and Dashboard KPIs
During this stage, a demonstration of the product followed by a hand 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/UT support Team and required processes are initiated in this stage.
Stage 4 – UAT & Go Live
Duration
2-3 weeks
Entry Criteria
Configured/Customized product ready for UAT
Pilot ULB Officials (Associated with W&S) are available for UAT & Training
Key Activities
UAT Environment Setup
Sign off from Pilot ULBs on the Migrated Connection Legacy Data during UAT
Issues/bug identification and resolution
Regression UAT and Sign off from Pilot ULBs/ State
Setting up the Production environment
Setting up Support Center & processes (Help Desk)
Training (Users, trainer)
master trainers identified from the ground for simultaneous training
Training the Support Resources
Marketing & promotion activities
Go Live & launch event
Setup of review and monitoring cadence/team
Usage/review/Dashboard/Field Visits
Exit Criteria
UAT Sign-off & Go Live for Pilot ULBs
Setup of review and monitoring cadence
On successful Go-Live in the Pilot ULBs, after further configurations to stabilize the product, the solution will be rolled out to the rest of the ULBs in multiple phases. Guidance and support from the State/UT 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 out for iterative activities of onboarding ULBs in batches.
Stage 5 – Rollout
Duration
5-6 weeks
Entry Criteria
The pilot has been successful in the State/UT
there are less than 3 open critical incidents (issues) with respect to product, implementation and data
Key Activities
ULB configurations phase-wise as per the Project Plan
Phase wise migration and verification of ULB data (as per the Data Agreement signoff, provided by the State)
Logistics planning for training
Establishment of bug ticketing tool for resolving ground-level issues by the state team
Training the Users at the district level
Pan State Roll-Out - Phase wise
Stabilise product
Exit Criteria
State/UT wide Rollout in batches:
Adoption tracking & Review Cadence operational
Help Desk Effectiveness assured
Critical Bugs fixed
Program Success Metrics Tracking Kick-started
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. Typical timelines for closure of rollout in each batch is 5-6 weeks (in a batch of 30 ULBs).
The final stage consists of strategies to ensure the sustenance of the product in the State/UT. 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
Rollout Phase 1( First set of 30 ULBs where rollout will happen after Pilot)
Key Ongoing Activities
Adoption Review Meetings as per the vision defined for the program
W&S Cell Focuses on Using data for:
tracking field issues and performance data to identify improvements
identify additional Integrations around W&S to make processes more robust towards enhancing W&S revenues (e.g Upstream and downstream Processes)
Conduct Weekly Review Meeting between ULBs, State Team for feedback on the system, which must be chaired by the Program Head
Plans of ongoing Sustenance in Place with respect to :
Funding
IT support (infra, helpdesk, ongoing enhancements)
Process Effectiveness and Improvements
This section outlines the activities involved in each stage of the implementation along with the responsibility and accountability of critical stakeholders - UT, NUS Team and System Integrator Team onboard.
W&S Cell: W&S 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 W&S cell required to be formed by the UT
Resource Name
No. Of Resources
Project Head
1
Domain Expert
2
Nodal Officer
2
MIS Expert
4
Note: Designation mentioned above are as per designations known driving W&S implementation at the State/UT level as explained below. (These are the preferred figures in the case of Domain Expert, 2 people are subject to availability)
Project Head: Is the Head of the W&S Cell who will drive the project from the State/UT Side
Domain Expert: Person who is well aware of the on-ground scenario, well versed with the act, GOs passed, Prevalent Business processes, Deviations from the acts, Rates/ slabs applicable
Nodal officer (EO/Commissioner/ Senior Official): the product coordinator 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 W&S, Facilitate and Track 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 program, 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/UT concerning the implementation, Program Designing etc.
System Integrator (SI) Team: SI Team will be responsible for the rollout of the initiative in the UT, providing end to end support to the State/UT w.r.t. The implementation of the products in the ULBs.
Guidelines to read the table are mentioned on the next page:
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 W&S Cell
Consult
Execute
Finalize funding for the program
Consult
Execute
Define state/UT-specific procurement process
Consult
Execute
System Integrator(SI) Team sign-up/onboarding
Consult
Execute
Finalize Water and Sewerage Program Vision
Consult
Execute
Note: Stage 0 is where the W&S cell and SI team are formed, hence there are only two entities playing a role which is that of eGov and the state leadership. Once the W&S cell and SI team are finalized, their role begins in the following stages.
Stage 1 - Program kick-off
Task/Activity
eGov
W&S Cell
SI Team
Identify & agree on scope and exclusions
Consult
Consult
Consult
Identify pilot ULBs
Execute
Consult
Project kick-off meeting and stakeholders consultation
Execute
Consult
Product Walkthroughs
Consult
Execute
Define Project Steering Committee structure and Project Governance process
Consult
Consult
Execute
Define phases of deployment/ rollout
Consult
Consult
Execute
Agreement on Product Feature Priorities and high-level delivery timelines
Consult
Execute
Assessment of all W&S process along
(1) citizen services/channels around it
(2) Integration with other department processes
Consult
Execute
Finalize Program Success Metrics for Adoption and Governance adhering to the vision of the program
Consult
Execute
Internal Capacity Building, program logistics at State and ULBs, as per the current scenario
Execute
Consult
Stage 2 - Solution Design
Task/Activity
eGov
W&S Cell
SI Team
Standardisation of all W&S processes, if needed
Consult
Execute
Initiate policy change and Process Re-engineering, if needed based on identified improvements
Consult
Execute
Consult
Conduct Product familiarization workshop
Consult
Consult
Execute
Initiate collection of master data from pilot ULBs
Consult
Execute
Finalize data migration/collection/sync-up approach
Consult
Execute
Finalize data validation approach
Execute
Consult
Building capacity for basic understanding of resources and tools required to be used
Execute
Consult
Stage 3 – Configuration & Customization
Task/Activity
eGov
W&S Cell
SI Team
Setting up development environments
Consult
Execute
Development/customization 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
Data Migration for Pilot ULBs(at least)
Consult
Execute
Training for basic understanding of resources and tools required to be used (system-related)
Execute
Consult
Legacy Data Validation signoff from the state on Data Validation
Execute
Consult
Stage 4 – UAT & Go Live
Task/Activity
eGov
W&S Cell
SI Team
UAT Environment Setup
Consult
Consult
Execute
UAT Testing
Consult
Execute
Issues/bug resolution
Consult
Execute
UAT Sign off from Pilot ULBs
Execute
Consult
Setting up the Production environment
Consult
Execute
Setting up Support Center & processes (Help Desk)
Execute
Consult
Training (Users, trainer)
Execute
Consult
Training the Support Resources
Consult
Execute
Marketing & promotion activities
Execute
Consult
Go Live & launch event
Execute
Consult
Setup of review and monitoring cadence/team Usage/ review/Dashboard/Field Visits
Execute
Consult
Stage 5: Rollout
Task/Activity
eGov
W&S Cell
SI Team
ULB configurations
Consult
Execute
Phase wise Migration and verification of ULB data
Execute
Consult
Logistics planning for training
Execute
Consult
Training the Users at the district level
Execute
Consult
Roll Out - All Locations
Consult
Execute
Execute
Stabilize product
Consult
Execute
Stage 6- Sustenance and Ongoing Improvement
Task/Activity
eGov
W&S Cell
SI Team
Adoption Review Meetings as per the vision defined for the program
Consult
Execute
Consult
W&S Cell Focuses on Using data for:
tracking field issues and performance data to identify improvements
identify additional Integrations around W&S to make processes more robust towards enhancing W&S revenues (e.g Upstream and downstream Processes)
Execute
Consult
Conduct Weekly Review Meeting between ULBs, State Team for feedback on the system, which must be chaired by the Program Head
Execute
Consult
Plans of ongoing Sustenance in Place with respect to :
Funding
IT support
Process Effectiveness and Improvements
Consult
Execute
Consult
Areas
Assumptions
Infrastructure
The actual Infra will be provided based on the questionnaire inputs received from the state
The state will take care of providing necessary project infrastructure and office facilities during the program for all on-site project Team members, which will be confirmed during the initiation phase. This includes workspace, office equipment (e.g., telephone with STD, fax machine, photocopy machine, etc.), stationery, PC/workstation, project LAN and internet access, etc.
The state will provide the necessary administrative support staff to carry out day-to-day project administration tasks, e.g., meeting rooms, Videoconferencing, etc.
The state should provide a Project Office and at least one conference room with a speaker phone throughout the Project Duration.
Project Scope
Any new requirements received from the State during the implementation phase will be handled through a change management process
State Team
The state will nominate a reasonably sized multifunctional Team from various departments of the State to be responsible for the implementation. The state Team would be required for information, validation, and execution through the implementation cycle and the Team members should be reasonably empowered to take decisions. Any delay in the decision-making process and the non-availability of the State Team may have an impact on the schedule.
The participants from State are expected to have a thorough understanding of the State’s internal processes.
The state will engage internal and external stakeholders required for this engagement and ensure their availability whenever needed.
Documentation
User education and training documentation will be delivered as per the default product documentation of the identified product versions.
The product manuals are expected to be shared with the State as part of the user manual.
All documentation would be in English only.
Training
Training to the end-users will be driven by the state Team.
The state will be responsible for providing the necessary infrastructure required for the Training, which includes the following readiness.
Training Rooms (Parallel Training Sessions) with Projector, White Board, Markers, Internet Connection, sufficient seating capacity, Desktop/Laptop for each participant and availability of Network for Trainees to connect to the server.
Implementation
The scope of the implementation will be limited to the services mentioned in Section 2.
eGov Team will have an identified SPOC for handling the first level of communication with the client unless discussed and agreed upon.
eGov Team will not be involved in defining the test cases or executing the test cases.
Necessary signoff would be provided by the state upon completion of the defined milestones.
PROGRAM
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 required.
System Integrator: The Entity/Company which collates all the subsystem 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 which 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.
IMPLEMENTATION
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 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 ULB.
Roll out: On successful clearance of the Pilot, the Process/Application/Services are implemented across all Offices/ULB's
Deployment: Deployment defines the complete package of Software components set up in a particular environment
PRODUCT
Customisation: 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 the users step-by-step through a set of actions that they need to take to achieve a specific outcome
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.
