Overview

The Process Quality Management (PQM) service will help users to create, update, and search for process quality monitoring tests. The service will evaluate the uploaded test values against benchmarks and produce result (FAIL/PASS) status. Test results will be further processed for anomaly analysis. The service can perform two types of test: Manual Test (Lab), and Automatic Test (IoT-based).

Plant User Mapping

The service enables mapping plant codes to operators and ULB admins, ensuring that each is only authorised to manage plants linked to their account, enhancing control and accountability. In the mapping process need to check below mention things

• PlantCode : Unique plant code which is configured in the mdms

• PlantUserType : User type will be either plant-operation or the ulb-admin

• PlantUserUuid : Unique user id of the employee which have the type of ulb-admin or the plant-operator.

Service Dependencies:

List of services that PQM service depends on:

• MDMS

• Workflow

• Notification

• Localisation

• Access Control

• User

• IDGen

Master Data

The following masters need to be created as part of this module:

• Plant

• PlantType

• PlantConfig

• Process

• ProcessType

• ProcessSubType

• Stage

• Material

• Parameter

• Unit

• BenchmarkRule

• TestingStandard

• QualityCriteria

• Device

• DeviceDetails

• DeviceConfig

Kafka Topic Details

Postman-Collection

PQM- Api collection

Plant User Mapping- Api collection

API Specification

PQM Swagger Link

Data Model

Sequence Diagrams

Create New

Update - new

Search

Reference Docs

Doc Links

API List

Here are the articles in this section:

Overview

This pqm scheduler is a cronjob scheduler for scheduling tests. It runs based on environment configuration. It triggers multiple the schedule API from PQM-Service to generate the Tests on the basis of Test Standards present in MDMS.

Dependency

• MDMS

• User

• PQM-Service

Key Functionalities

• It creates tests based on MDMS Test Standards using pqm-service /v1/_scheduler API.

Sequence Diagram

Create Lab Test (CronJob)

Here are the articles in this section:

Services

Process Quality Management (PQM) is a service that will be responsible for Treatment Quality Monitoring. It will improve the quality of processes, such as waste treatment process, water treatment process, etc. We are building these services on top of the existing building blocks of DIGIT.

Core Components

To develop a new service, one needs to create a micro-service and make it available through the API gateway. The API gateway calls the User Service for authentication and the Access Service for authorisation.

Implementation users and service developers can configure the roles and map the roles, actions, plants, treatment process, stages, and testing standards will be created using the Master Data Management Service.

Citizen Dashboard: The service user interface can be developed as part of the Citizen Dashboard or can be an independent solution. The citizen can log in using a mobile number and OTP. They can apply for a new service using the service UI. The File Store Service allows users to upload relevant documentation.

The Persister Service stores the submitted application asynchronously into the registry. The PII data is encrypted using the Encryption Service before storing. All changes are digitally signed and logged using the Signed Audit Service (ongoing). The Indexer Service transforms and enriches the application data. The Indexer Service also strips the PII data and sends it to the Analytics Data Store(ElasticSearch).

The Dashboard Backend Service executes configured queries on the stripped data and makes the aggregated data available to the Dashboard Frontend for the administrator or employee view. The views are in accordance with the user role access which is also configurable.

The Employee Service allows employee registrations and enables them to log in using the employee dashboard. The dashboard displays the list of pending applications as per the employee's role. The employee can perform actions on these applications using the employee UI for the service. As the status changes or actions are taken on the applications, the relevant SMS and Email Notification Service sends the updates to the plant operator and lab collectors. Once the test is completed, the lab/urban local body (ULB) employee can upload and download the test results submitted.

DIGIT has multi-tenant configuration capabilities. The Location Service allows the configuration of the tenant hierarchy and maps multiple tenants like country, state, district, or state, department, and sub-department. Each tenant can have their own configurations for service, roles, workflows etc. This allows for variations across different agencies in tune with the local context. The Language Service facilitates the support of multiple languages in DIGIT. This service stores the translations in multiple languages.

PQM Components

The PQM Service schedules and manages recurring test to evaluate the quality of a process. This can read sensor devices if assigned for a process stage. It can update the treatment quality workflow status based on the results submitted manually or collected through IoT devices. Provides APIs for creating ad-hoc tests, update results, search for results, and anomalies identified.

The PQM Anomaly Finder service finds anomalies in the process quality and raises notifications/alerts based on the defined anomaly check configurations.

ER Diagram

Sequence Diagram

Create Manual Tests (Cron Job)

Create IoT Tests (Cron Job)

Create Test (Ad-hoc)

Update Test

Search Tests

Find Anomaly

Overview

The Process Quality Management (PQM) anomaly finder service helps in monitoring anomalies in process quality and notifies the concerned user groups.

Master Data Types

The following masters need to be created as part of this module:

• Plant

• PlantConfig

Dependencies

List of services that PQM service depends on:

User-Event Service

User-event service api will get the notification for the anomaly .

Deploy the latest build if the service is not there in the environment “egov-user-event-db:v1.2.0-32caf0d992-25” .

Add the changes which are required . For this kindly refer the below pr.

Path: deploy-as-code/helm/charts/core-services/egov-user-event/Chart.yaml

File: Refer the pr for the changes

Notification

Note: For the test not submitted notification, the notification will only be sent when the frequency of a test standard is greater than the manualTestPendingEscalationDays from Plant Config Master

Localisation

Alert notification format needs to add in localisation.

[
  {
    "code": "NOTIF_TEST_RESULT_NOT_SUBMITTED",
    "message": "Lab results for plant {Plant Name} for {Output} of {Stage} stage scheduled on {Test Scheduled Date} has not yet been submitted.",
    "module": "rainmaker-tqm",
    "locale": "en_IN"
  },
  {
    "code": "NOTIF_TEST_RESULT_NOT_AS_PER_BENCHMARK",
    "message": "Lab results submitted for plant {Plant Name} for {Output} of {Stage} stage submitted on {Test Submitted Date} is not as per benchmark values.",
    "module": "rainmaker-tqm",
    "locale": "en_IN"
  }
]

Postman Collection

Link to collection

API Specification

PQM Anomaly Swagger Link

Kafka Topic Details

ER Diagram

Sequence Diagram

Find Anomaly

Reference Docs

Doc Links

API List