Impacted Service:

Process Quality Management (PQM):

Introduced three new services: PQM Service, PQM Anomaly Service, and PQM Scheduler Service.

PQM Service

• Create, update, and search for process quality monitoring tests.

• Record test results gradually for a test and submit from evaluation when all the test results available

• Evaluation of test values against benchmarks configured in MDMS, for producing a test result (FAIL/PASS) status.

• Test results undergo anomaly analysis for comprehensive insights.

• Plant performance related charts.

PQM Anomaly Finder Service

• Actively monitors anomalies in process quality.

• Added notification for relevant user groups promptly for proactive anomaly management.

PQM Scheduler (CronJob Scheduler)

• Automation of test scheduling based on environment configuration and MDMS test standard configurations.

• Triggers schedule APIs from PQM-Scheduler to generate tests at defined frequency.

• Efficiently runs tests at specified intervals, ensuring a configurable approach.

Sanitation Worker:

A new worker registry concept has been introduced. Creating a worker, updating details, searching and tagging a worker for different operations on sanitation programmes. Sanitation workers' creation, updation, and search operations are performed using the individual registry.

• Added functionality for creating, updating, and searching for sanitation workers.

• Deprecated the drivers tab and added the driver concept from the FSM registry.

• Introduced the sanitation workers tab to the FSM registry.

Vendor:

• Added functionality for assigning. a sanitation worker to a vendor.

• Migration of existing drivers to sanitation workers.

• Deprecation of delinking of a driver with vendors introduced in v1.3.

FSM:

• Tag sanitation workers (drivers and helpers) to an FSM application for capturing the workers' activities.

• The inbox for FSM has been upgraded from V1 to V2.

No core services have been modified. Workflow details, flow diagram, and API details are given in confluence.

API List (Modified and New):

About Water-Sanitation

Enabling Samaaj (society), Sarkar (government), & Bazaar (industry/market) partners with a digital platform that would help ensure zero deaths, disease, and environmental contamination resulting from poor sanitation - a reality for every citizen across the Global South.

Water-Sanitation aims to ensure zero untreated waste by catalysing open digital ecosystems.

Useful Links

Contact Us

Release Summary

Introducing New Services for Enhanced Process Quality Management

1. Process Quality Management (PQM) Service.

2. Process Quality Management (PQM) Anomaly Finder Service.

3. PQM Scheduler (CronJob Scheduler).

Enhancements

1. Sanitation Worker Welfare feature

2. Driver-Individual migrate feature

3. FSM inbox V2

New ‌Feature Additions

Enhancements

Document Resources & Links

Overview of Faecal Sludge Management

The waste we flush down the toilet does not always go into a sewer. Approximately 70% of the households in India have toilets connected to septic tanks or soak pits, technically known as on-site containment systems. They accumulate and store faecal matter over a long period. In sewers, the faecal matter travels daily with a lot of water through long concrete pipes. But in the case of on-site systems, it stays stored for about 3-5 years. Once the storage is full, the waste is emptied and transported to the treatment plant through vacuum trucks. The end-to-end value chain of safe storage, collection, transport, treatment, and end-use or disposal of faecal matter is called Faecal Sludge and Septage Management or FSSM. ‘Faecal Sludge’ and ’Septage’ are used to describe faecal matter in a specific physical and chemical state after prolonged storage.

Why FSM matters - It is the way forward in sanitation

FSSM has emerged as a cost-efficient population scale alternative to the networked sewer, which has been the traditional method of wastewater management.

1. Cost-effective: FSSM is 10 times cheaper than sewer systems.

2. Coverage: Less than one-third of urban toilet users are connected to sewer systems. The rest are more or less dependent on FSSM systems. Targeting FSSM will help us impact the maximum number of citizens.

3. Scale: In India's Swachh Bharat mission, 11 crore toilets were constructed across the country. Most are connected to on-site systems, which again increases the need for FSSM.

Our current understanding of the problems in septage management is based on our interactions with stakeholders and thorough published reports, and whitepapers. We are aware that FSSM systems have interdependent parts, and each stage of the FSSM value chain impacts how effectively the next stage functions. For instance, if the septic tanks do not have proper access, they will add to the cost of emptying, adding time and cost burden on desludging operators (DSOs). Similarly, it becomes unviable for the DSOs to dump the waste at the treatment plant if it is far from the city which is often the case.

While the linear sanitation value chain provides an understanding of the flow of faecal sludge, it does not capture all stakeholders in the process that control and influence the current effectiveness of sanitation systems.

Systems Map

We will use a systems mapping approach to outline the different factors and interactions within the sanitation value chain. We will explore systemic challenges at each part of the value chain that result in poor sanitation outcomes.

Part 1 - Toilets and containment units

Problems faced by key stakeholders

City managers, central/state governments

While sanitation is a priority of the central and state governments, city administrators have been strapped due to deficiencies in standards, building codes, municipal processes, and contracting and monitoring capabilities. These make it difficult to ensure the adequacy, usability, and safety of the toilets provisioned by public funds.

Masons

Masons are fundamental in proper construction of toilets and containment units. But a majority of masons currently lack the necessary training on construction standards. They are rarely employed using formal contracts, contributinb to the lack of traceability and accountability during the construction of toilets.

Citizens

Lack of awareness of the impact of improper construction of toilets and containment tanks, or constraints of affordability and space, leads citizens to influence masons to build containment units that do not follow technical standards. It is difficult to identify trained masons and services are procured through social networks and word of mouth.

Part 2 - Emptying and transport

Problems faced by key stakeholders

Desludging operators

• Lack of proper access to the containment systems adds time-cost to service.

• Treatment plants are located far from the city, making safe dumping unviable.

• While the payment from citizens is a clear incentive for emptying the tanks or pits, there are no incentives to ensure the safe transport of the faecal sludge to the treatment plant.

• Operations remain inefficient without timely and useful information for service delivery. Working conditions are risky, but provisions for personal protection equipment and emergency healthcare services are rare.

Citizens

• It is difficult to identify and book desludging services and service delivery is not reliable.

• Low-income households are denied service since they are not able to afford the full cost.

City managers, central/state governments

• Challenging to regulate the market for safe dumping without compromising service delivery.

• Lack of clear and actionable information in terms of safe or unsafe dumping of faecal sludge.

• Lack of pricing policies, infrastructure standards, licensing processes, and contracting and monitoring capacity limit the ability of decision-makers to take action.

Part 3 - Treatment

City managers, centre/state governments

• Difficult to regulate the market across various stages of construction and operations.

• Operational data of the treatment plant and process is often recorded offline and used for post-facto auditing. There is a pervasive lack of actionable information.

• Lack of rational pricing policies, comprehensive service benchmarks and infrastructure standards, contracting and monitoring tools hamper corrective action.

Plant operators

• The supply of desludging load varies in an unreliable and unpredictable manner, and over time, leads to system failure.

• Treatment plant management and maintenance is difficult and costly, and the payments are often not linked to performance.

• The performance is not directly causally linked to the environmental impact.

• Operations are not monitored to facilitate preventive action within the plant, and lack any binding linkages with standard operating procedures and service level agreements.

Part 4 - Ecosystem

Civil society and academia

• In the absence of data, researchers struggle to create new knowledge around the failures, risks, and opportunities, as well as give recommendations for improvement.

• Since policy and standards are not mapped to operational data, it is difficult for the ecosystem to translate knowledge to action, impact and access.

Government

• Inability to trace the impact and proper usage of grants and subsidies for sanitation.

• Limited state capacity in terms of budget, skilled human resources, tools, and technology. Coordination across multiple functions, such as standard-setting, policy-making, contracting, audit, monitoring, is needed to keep sanitation systems functional.

• Limited penetration of technology, innovation, and competition in the sanitation sector, makes it difficult for the government to enforce accountability across internal processes and market interactions.

Critical Problems in FSSM

At the core of all systemic challenges, there are problems that hinder a systemic change, limit stakeholders from implementing changes, or even cause the system to collapse. The identified problems are explained below:

Absence of well-defined standards for sanitation

• Current standards do not cover all aspects of sanitation and service delivery - such as standards of treated human waste, treatment plant technologies, and benchmarks, among others.

• The ecosystem has created many standards, which are not formally notified or enforced.

• Where standards exist, awareness and compliance are dismal for the following reasons:

1. Many actors in the value chain do not have the necessary knowledge, skills, or standard operating procedures.

2. Complexities in service delivery result in incomplete or improper service.

3. Poor requirement specifications in the Request for Proposals (RFPs) documents.

4. Model contracts exist but are not followed.

5. Delays in corrective action since contracts are not tightly coupled with monitoring.

Broken chain of custody from waste generation to reuse

• Systemic data either does not exist or remains disjointed to understand how much waste exists, where, when, with whom, and why.

• Feacal sludge tends to drop out of the value chain, untreated.The unavailability of the information - who dropped it, when, how, or where it ended up polluting the environment - hampers the process of taking corrective and preventive measures

Lack of verifiable, trusted data at various levels

• Data around faceal sludge (how much, where, when, who is responsible) is too little.

• Required data is not created, available, or shared across relevant ecosystem actors. As a result, the performance of sanitation systems remains opaque and unobservable.

Inability to convert waste to value

• Current systems are not structured to maximise the value from faceal sludge and related services.

• The policy framework may not recognise treated human excreta as compost. Unclear and fragmented demand for treated waste contributes to lax operations upstream.

Water-Sanitation is an open-source web and mobile-enabled platform designed to digitise operations in the waste management value chain, from collection to treatment. It provides the ability to drive coordination across multiple independent and disconnected stakeholders, ensuring a continued chain of custody of waste throughout.

According to a United Nations (UN) report, only 54% of the world population has access to safe sanitation. We believe that at the heart of the problems in sanitation are ineffective systems that fail to deliver. Hence, systems must be progressively reformed. To move habitats towards zero untreated waste, we will leverage the capabilities built by the Digital Infrastructure for Governance, Impact & Transformation (DIGIT), and ensure the traceability of waste by enabling the ecosystem with the following features:

• Chain of custody: We will ensure a seamless and traceable chain of custody for waste. This will enable stakeholders to track waste from its source to its final destination, ensuring accountability and transparency in the waste management process.

• Actionable data: Our system will provide actionable data on waste management operations, which will enable stakeholders to make informed decisions. This data will be used to optimise waste collection and treatment processes, identify areas for improvement, and drive evidence-based decision-making.

• Code for innovation: We will foster innovation by providing a digital platform that encourages collaboration among stakeholders. Our system will facilitate the sharing of ideas, best practices, and innovative solutions for sanitation challenges, driving continuous improvement in the waste management ecosystem.

Need for Water-Sanitation

Current digital efforts across geographies do not take a “whole of system view” and do not solve the cost of coordination and duplication issues. Such siloed, solution-centric approaches and tools create a new set of problems and inefficiencies for countries:

• Higher costs and time: This is incurred on creating or procuring and maintaining these systems, including the onboarding cost of the same actors in each programme.

• Data exists in multiple systems: They are not interoperable, leading to duplication, inconsistencies, poor adoption by on-ground workers, and sub-optimal decision-making.

• Limited reusability and innovation: Data and capabilities are intertwined and ‘locked,’ making it extremely hard for the wider ecosystem to innovate and build upon.

• Sub-scale: The tools are not able to scale for the national population and across waste streams.

Scope

Water-Sanitation solutions are built on the principles of societal platforms, envisioning a space where sanitation is supported by shared resources, curated knowledge, and evolving solutions that address the needs of the community. We recognise that the challenges of sanitation are systemic and require the collective efforts of all stakeholders to be effectively addressed. Drawing from the insights gained from our urban mission, we embrace the triple helix model, which emphasises partnerships among different stakeholders, including civil society (samaaj), government (sarkaar), and industry/market (bazaar), to generate innovation through synergistic collaboration. Leveraging our experience in building large-scale public digital infrastructure, we are well-positioned to create the foundation for this ecosystem and drive progress in solving the most pressing sanitation issues. We believe that by fostering cooperation and collaboration among all stakeholders, we can create sustainable solutions that meet the needs of communities and contribute to the transformation of the sanitation landscape.

While sanitation requirements and solutions may vary among local governments, there are commonalities in the value chain of sanitation waste streams, such as faecal sludge management, solid waste management, plastic waste management, etc. These value chains typically involve steps such as generation, containment, collection, transport, treatment, and disposal/reuse. These similarities provide an opportunity to abstract and digitise various components of the service value chain, with the potential to encode standards and enable data-driven visibility into sanitation services.

The Water-Sanitation solution is specifically designed to allow for the contextualisation and reuse of components across different waste streams and geographies. By incorporating standards into the platform and leveraging data registries and reusable building blocks in the technology stack, applications can be developed more efficiently and quickly at the solution layer, resulting in lower costs and faster implementation. This approach enables flexibility and scalability in addressing diverse sanitation needs, while also promoting interoperability and consistency in the digital solutions deployed. By leveraging the Water-Sanitation solutions, stakeholders can build innovative applications tailored to local contexts, while adhering to standardised components and data structures, leading to more effective and sustainable sanitation services.

Following is a glimpse of how this would work:

The above image illustrates the core infrastructure services, and the enabling services that are built/configured for a Faecal Sludge Management (FSM) solution with the following functionality:

1. Allowing citizens to request septic tank desludging services

2. Scheduling desludging services for a certain set of property types/localities, etc.

3. Automated or manual assignment of vendors to perform requests

4. Tracking sludge from collection to disposal at a treatment plant using the Internet of Things (IoT)

5. Notifications to stakeholders at each point in the workflow

6. Dashboards and reports

Now, consider that instead of FSM, a solution needs to be built for Solid Waste Management:

The same set of infrastructure and enabling services could be used to configure the following functionalities:

1. Scheduling the collection of waste based on different categories

2. Automated or manual assignment of vendors to perform requests

3. Tracking adherence to the schedule

4. Tracking waste movement from pickup to disposal at a treatment facility

5. Notifications to stakeholders at each point in the workflow

6. Dashboards and reports

Further, only an additional service for segregation monitoring would have to be built.

To illustrate this further, imagine building a solution for sanitation worker welfare:

1. Service Request Management

• Define pricing

• Record service requests

• Assign and manage service requests

• Provide subsidies

• Calculate service fees

• Track status

• Collect feedback

1. Transport Management

• Schedule pickup

• Assign vehicles and drivers

• Track status

1. Billing and Payments

• Generate demand

• Generate receipts

• Online payment gateway

1. Notifications

• SMS

• In app

1. Service Delivery Monitoring

• Dashboards

• Reports

QA Test Cases for PQM:

QA Test Cases for Sanitation Worker Welfare:

Release Summary

The release provides the functionality of tagging the gram panchayat (GP) and villages via urban local bodies (ULBs). The ULB will be servicing desludging requests for households in the respective GP.

Release Highlights

The functionality included are:

• Adding GPs while creating an application.

• Make the amount per trip field editable for GPs.

New Feature Additions

Document Resources and Link

PQM Business Service Request

Instructions for Production execution:

1. Replace the tenant id for production environment

2. Replace the request info object with production user info details

3. For PQM new Business service PQM has been created

   Create businessService (workflow configuration) using the /businessservice/_create. Following is the product configuration for PQM

```postman_json
{
    "RequestInfo": {
        "apiId": "Rainmaker",
        "action": "",
        "did": 1,
        "key": "",
        "msgId": "20170310130900|en_IN",
        "requesterId": "",
        "ts": 1513579888683,
        "ver": ".01",
        "authToken": "71fc8bf6-4c3f-4bb3-af74-bc2fabf6252e",
        "userInfo": {{adduserInfo}}
    },
    "BusinessServices": [
        {
            "tenantId": "pg",
            "businessService": "PQM",
            "business": "pqm",
            "businessServiceSla": 432000000,
            "states": [
                {
                    "sla": null,
                    "state": null,
                    "applicationStatus": null,
                    "docUploadRequired": true,
                    "isStartState": true,
                    "isTerminateState": false,
                    "isStateUpdatable": true,
                    "actions": [
                        {
                            "action": "SCHEDULE",
                            "nextState": "SCHEDULED",
                            "roles": [
                                "PQM_ADMIN",
                                "PQM_TP_OPERATOR",
                                "PQM_CRONJOB_SCHEDULER"
                            ]
                        }
                    ]
                },
                {
                    "sla": null,
                    "state": "SCHEDULED",
                    "applicationStatus": "SCHEDULED",
                    "docUploadRequired": false,
                    "isStartState": false,
                    "isTerminateState": false,
                    "isStateUpdatable": true,
                    "actions": [
                        {
                            "action": "SUBMIT_SAMPLE",
                            "nextState": "PENDINGRESULTS",
                            "roles": [
                              "PQM_ADMIN",
                                "PQM_TP_OPERATOR"
                            ]
                        }
                    ]
                },
                {
                    "sla": null,
                    "state": "PENDINGRESULTS",
                    "applicationStatus": "PENDINGRESULTS",
                    "docUploadRequired": false,
                    "isStartState": false,
                    "isTerminateState": false,
                    "isStateUpdatable": false,
                    "actions": [
                        {
                            "action": "UPDATE_RESULT",
                            "nextState": "SUBMITTED",
                            "roles": [
                                "PQM_ADMIN",
                                "PQM_TP_OPERATOR"
                            ]
                        },
                        {
                            "action": "SAVE_AS_DRAFT",
                            "nextState": "DRAFTED",
                            "roles": [
                                "PQM_ADMIN",
                                "PQM_TP_OPERATOR"
                            ],
                            "active": true
                        }
                    ]
                },
                {
                    "sla": null,
                    "state": "DRAFTED",
                    "applicationStatus": "DRAFTED",
                    "docUploadRequired": false,
                    "isStartState": false,
                    "isTerminateState": false,
                    "isStateUpdatable": true,
                    "actions": [
                        {
                            "action": "UPDATE_RESULT",
                            "nextState": "SUBMITTED",
                            "roles": [
                                "PQM_ADMIN",
                                "PQM_TP_OPERATOR"
                            ],
                            "active": true
                        },
                        {
                            "action": "SAVE_AS_DRAFT",
                            "nextState": "DRAFTED",
                            "roles": [
                                "PQM_ADMIN",
                                "PQM_TP_OPERATOR"
                            ],
                            "active": true
                        }
                    ]
                },
                {
                    "sla": null,
                    "state": "SUBMITTED",
                    "applicationStatus": "SUBMITTED",
                    "docUploadRequired": false,
                    "isStartState": false,
                    "isTerminateState": true,
                    "isStateUpdatable": false,
                    "actions": null
                }
            ]
        }
    ]
}
```

Overview

The Driver-Individual Migration Scripts is responsible for fetching all existing drivers in the system and subsequently generating creates corresponding individuals in the system.

Build

The data migration has been implemented in Vendor Service with latest stable build -

vendor:develop-fc828adcbe-31

API Spec

MDMS Roleaction Mapping

File Path -

 {
      "id": 376,
      "name": "Migrate Driver Data to Individual",
      "url": "/vendor/v1/_migrate",
      "displayName": "Migrate Driver Data to Individual",
      "orderNumber": 0,
      "enabled": false,
      "serviceCode": "vendor",
      "code": "null",
      "path": ""
    }

File Path -

{
      "rolecode": "FSM_ADMIN",
      "actionid": 376,
      "actioncode": "",
      "tenantId": "pg"
    }

Please use FSM_ADMIN credentials for accessing this API.

TQM is an independent UI module which only depends on the core UI libraries.

Here are the articles in this section:

Overview

The following MDMS changes were done as part of the FSM v1.4 release:

MDMS Changes

For MDMS-V2 changes, refer to the below table for the sequence in which MDMS schema and data needs to be added for the PQM service:

UI-Related MDMS Files

Role-Action Mapping

data/pg/ACCESSCONTROL-ACTIONS-TEST/actions-test.json

data/pg/ACCESSCONTROL-ACTIONS-TEST/actions-test.json:

PQM.Benchmark

PQM.QualityTestLab

PQM.Material

PQM.Parameter

PQM.PlantConfig

PQM.PlantType

PQM.ProcessType

PQM.Unit

PQM.WasteType

PQM.SourceType

PQM.Stage

PQM.Process

PQM.Plant

PQM.QualityCriteria

PQM.TestStandard

Overview

This page contains the changes related to Process Quality Management-related services (PQM) and Sanitation Worker Welfare along with the MDMS, DevOps and configuration setups required to accommodate these features.

Migration Steps

PQM Service

The PQM service is required to create, update, search and evaluate tests against benchmarks. Follow the steps given below:

4. Configure the build.

1. Make the role action-mapping changes in the MDMS.

Master Data for PQM

1. Click on the Job-builder once the above steps are complete.

2. Restart the following services: egov-accesscontrol, egov-mdms-service, egov-persister

PQM Scheduler

3. Configure the build.

1. Make the role action-mapping changes in the MDMS.

1. Click on the Job-builder once the above steps are complete.

2. Restart the following services: egov-accesscontrol, egov-mdms-service.

PQM Anomaly Finder Service

3. Configure the build.

Sanitation Worker Welfare

6. Deploy the latest build of individual service refer link#

UI Migration Changes

4. Code PRs for referenceL